975  Zigbee Application Profiles

ZHA, ZLL, ZBA, and the unified Zigbee 3.0 standard for device interoperability

975.1 Learning Objectives

By the end of this chapter, you will be able to:

  • Explain the purpose of Zigbee application profiles
  • Distinguish between ZHA, ZLL, ZBA, and other legacy profiles
  • Understand how Zigbee 3.0 unifies fragmented profiles
  • Identify interoperability challenges between different profile versions
  • Make informed decisions about profile selection for new deployments

975.2 Introduction

Zigbee application profiles define how devices communicate at the application layer. They specify device types, clusters, and behaviors that enable interoperability between devices from different manufacturers. Understanding profiles is essential for building systems where a sensor from one vendor can control a light from another.

Think of application profiles like languages: - ZHA (Home Automation) is like English - ZLL (Light Link) is like Spanish - ZBA (Building Automation) is like French

Devices speaking the same “language” understand each other perfectly. Devices with different profiles might not communicate directly, even if they’re on the same network.

Zigbee 3.0 is like creating a universal translator - it defines a common language so all devices can work together.

975.3 Legacy Profiles

Before Zigbee 3.0 (pre-2016), multiple application profiles existed for different use cases:

975.3.1 Zigbee Home Automation (ZHA)

ZHA was the primary profile for residential smart home devices:

Target Applications: - Smart switches and dimmers - Door/window sensors - Motion detectors - Thermostats - Smart locks

Key Characteristics:

Feature ZHA Specification
Profile ID 0x0104
Commissioning Trust Center, Install Codes
Security High security mode mandatory
Device Types 50+ standard types
Clusters Home automation focused

Common ZHA Clusters:

Cluster ID Name Function
0x0000 Basic Device info (manufacturer, model)
0x0006 On/Off Toggle, on, off commands
0x0008 Level Control Dimming
0x0101 Door Lock Lock/unlock
0x0402 Temperature Measurement Sensor data
0x0500 IAS Zone Security sensors

975.3.3 Zigbee Building Automation (ZBA)

ZBA targeted commercial building management:

Target Applications: - HVAC control - Lighting management - Occupancy sensing - Energy metering - Access control

Key Characteristics:

Feature ZBA Specification
Profile ID 0x0105
Commissioning Installer tools
Security Extended security
Device Types Commercial-focused
Scalability Large buildings

975.3.4 Zigbee Smart Energy (ZSE)

ZSE focused on utility metering and demand response:

Target Applications: - Smart meters - In-home displays - Load control devices - Price signaling

Key Characteristics:

Feature ZSE Specification
Profile ID 0x0109
Security Utility-grade certificates
Metering kWh, demand, TOU pricing
Grid Integration Demand response support

975.4 Profile Interoperability Problem

The multiple profiles created fragmentation:

%%{init: {'theme': 'base', 'themeVariables': { 'primaryColor': '#2C3E50', 'primaryTextColor': '#fff', 'primaryBorderColor': '#16A085', 'lineColor': '#E67E22', 'secondaryColor': '#7F8C8D', 'tertiaryColor': '#ECF0F1', 'fontSize': '12px'}}}%%
graph TB
    subgraph Problem["Profile Fragmentation (Pre-2016)"]
        ZHA["ZHA Devices<br/>(SmartThings sensors)"]
        ZLL["ZLL Devices<br/>(Philips Hue bulbs)"]
        ZBA["ZBA Devices<br/>(Commercial HVAC)"]
        ZSE["ZSE Devices<br/>(Smart meters)"]
    end

    ZHA -.->|"Limited<br/>interop"| ZLL
    ZHA -.->|"No direct<br/>interop"| ZBA
    ZLL -.->|"No direct<br/>interop"| ZSE

    HUB["Hub Required<br/>for Translation"]

    ZHA --> HUB
    ZLL --> HUB
    ZBA --> HUB
    ZSE --> HUB

    style ZHA fill:#2C3E50,stroke:#16A085,stroke-width:2px,color:#fff
    style ZLL fill:#E67E22,stroke:#2C3E50,stroke-width:2px,color:#fff
    style ZBA fill:#16A085,stroke:#2C3E50,stroke-width:2px,color:#fff
    style ZSE fill:#7F8C8D,stroke:#2C3E50,stroke-width:2px,color:#fff
    style HUB fill:#E67E22,stroke:#2C3E50,stroke-width:3px,color:#fff

Figure 975.1: Legacy profile fragmentation requiring hub translation between device types

Example Problem:

Scenario: ZHA motion sensor + ZLL bulb

User expectation:
- Motion detected → Bulb turns on

Reality (without hub):
- ZHA sensor sends ZHA On/Off command
- ZLL bulb expects ZLL On/Off command
- Different cluster implementations
- Direct binding fails

Solution:
- Hub receives ZHA motion event
- Hub translates to ZLL command
- Hub sends to ZLL bulb
- Works, but requires hub always

975.5 Zigbee 3.0: The Unified Standard

Released in 2016, Zigbee 3.0 unifies all profiles under a single standard:

975.5.1 Key Improvements

Aspect Legacy Profiles Zigbee 3.0
Profile ID Multiple (0x0104, 0xC05E, etc.) Single (0x0104 base)
Clusters Profile-specific Unified ZCL
Commissioning Profile-specific BDB (Base Device Behavior)
Security Varied Standardized, improved
Interoperability Limited Guaranteed

975.5.2 Base Device Behavior (BDB)

BDB standardizes how all Zigbee 3.0 devices join networks:

BDB Commissioning Options:
1. Touchlink (from ZLL) - proximity pairing
2. Network Steering - join existing network
3. Network Formation - create new network
4. Finding & Binding - automatic endpoint matching

Any Zigbee 3.0 device supports all methods

975.5.3 Unified Cluster Library

Zigbee 3.0 consolidates clusters from all legacy profiles:

%%{init: {'theme': 'base', 'themeVariables': { 'primaryColor': '#2C3E50', 'primaryTextColor': '#fff', 'primaryBorderColor': '#16A085', 'lineColor': '#16A085', 'secondaryColor': '#E67E22', 'tertiaryColor': '#7F8C8D', 'fontSize': '12px'}}}%%
flowchart TB
    subgraph ZCL3["Zigbee 3.0 Cluster Library"]
        GEN["General Clusters<br/>Basic, On/Off, Level"]
        LIGHT["Lighting Clusters<br/>Color Control, Scenes"]
        HVAC["HVAC Clusters<br/>Thermostat, Fan"]
        SENSE["Sensing Clusters<br/>Temperature, Humidity"]
        SEC["Security Clusters<br/>IAS Zone, IAS ACE"]
        METER["Metering Clusters<br/>Energy, Demand"]
    end

    ZHA2["Former ZHA"] --> GEN
    ZHA2 --> SENSE
    ZHA2 --> SEC

    ZLL2["Former ZLL"] --> GEN
    ZLL2 --> LIGHT

    ZBA2["Former ZBA"] --> GEN
    ZBA2 --> HVAC

    ZSE2["Former ZSE"] --> GEN
    ZSE2 --> METER

    style ZCL3 fill:#16A085,stroke:#2C3E50,stroke-width:3px,color:#fff

Figure 975.2: Zigbee 3.0 unified cluster library incorporating all legacy profile features

975.5.4 Green Power Integration

Zigbee 3.0 includes Green Power for battery-free devices:

Energy Harvesting Sources: - Piezoelectric (button presses) - Photovoltaic (solar cells) - Electromagnetic (motion) - Thermoelectric (temperature differential)

Green Power Architecture:

Battery-Free Switch (GPD)
    ↓ [Green Power Frame]
Green Power Proxy (Router)
    ↓ [Translated Zigbee Command]
Light Bulb (GP Sink)

Benefits: - Zero battery maintenance - Environmentally sustainable - Install anywhere (no wiring) - Lifetime operation

Limitations: - Unidirectional communication - Simplified frame format - Limited range (10-30m typical)

975.6 Migration and Backward Compatibility

975.6.1 Zigbee 3.0 with Legacy Devices

Zigbee 3.0 maintains backward compatibility:

Compatibility Matrix:

Zigbee 3.0 device → ZHA network: ✅ Works (uses ZHA mode)
Zigbee 3.0 device → ZLL network: ✅ Works (uses ZLL mode)
ZHA device → Zigbee 3.0 network: ✅ Works (hub translates)
ZLL device → Zigbee 3.0 network: ✅ Works (hub translates)
ZHA device → ZLL device (direct): ⚠️ Via hub only

975.6.2 Migration Strategy

For existing deployments:

Phase 1: Add Zigbee 3.0 Hub
- Replace or upgrade coordinator
- Existing devices continue working
- New devices get full interoperability

Phase 2: Gradual Device Replacement
- Replace legacy devices as they fail
- Choose Zigbee 3.0 certified replacements
- Direct binding becomes possible

Phase 3: Full Zigbee 3.0
- All devices Zigbee 3.0 certified
- Hub translation no longer needed
- Direct device-to-device binding works

975.7 Certification and Labels

975.7.1 Identifying Zigbee Versions

Look for these certifications when purchasing:

Label Meaning Interoperability
“Zigbee Certified” (pre-2016) Legacy profile (ZHA/ZLL) Profile-specific
“Zigbee 3.0 Certified” Unified standard Universal
“Works with Zigbee” May be certified Check details
“Zigbee Compatible” No certification Unknown

Recommendation: For new deployments, only purchase “Zigbee 3.0 Certified” devices.

975.7.2 Certification Process

Devices undergo testing at authorized labs:

Certification Testing:
1. Protocol conformance (stack behavior)
2. Cluster implementation (command support)
3. Interoperability (works with reference devices)
4. Security (encryption, key handling)
5. RF performance (range, power)

Result:
- Certified devices added to Zigbee Alliance database
- Permitted to use Zigbee 3.0 logo
- Guaranteed interoperability

975.8 Zigbee vs Matter

Matter (formerly Project CHIP) is the newer unified standard backed by Apple, Google, Amazon, and the Connectivity Standards Alliance:

975.8.1 Comparison

Aspect Zigbee 3.0 Matter
Transport Zigbee NWK (proprietary) IPv6 (Thread, Wi-Fi, Ethernet)
Addressing 16-bit proprietary Full IPv6
Ecosystem Zigbee Alliance Apple, Google, Amazon, CSA
Cloud connectivity Requires gateway Native IP
Established devices Billions deployed New (2022+)

975.8.2 When to Choose Each

Choose Zigbee 3.0: - Extending existing Zigbee deployments - Proven, mature technology - Large installed base of devices - Cost-sensitive applications

Choose Matter (over Thread): - New greenfield deployments - Multi-ecosystem support required - Direct cloud connectivity needed - Future-proofing priority

975.8.3 Thread as Transport

Matter can run over Thread (which uses IEEE 802.15.4 like Zigbee):

Protocol Comparison:

Zigbee: 802.15.4 → Zigbee NWK → ZCL
Thread: 802.15.4 → 6LoWPAN → IPv6 → Matter
                            ↓
                        CoAP/UDP

Some devices support both Zigbee and Thread (dual-protocol chips), enabling migration paths.

975.9 Summary

This chapter covered Zigbee application profiles:

  • Legacy Profiles: ZHA, ZLL, ZBA, ZSE served different markets but created fragmentation
  • Interoperability Problem: Devices with different profiles couldn’t directly communicate
  • Zigbee 3.0: Unified standard with BDB commissioning and consolidated ZCL
  • Green Power: Battery-free devices using energy harvesting
  • Backward Compatibility: Zigbee 3.0 works with legacy devices via hub translation
  • Matter Competition: Newer IP-based standard, but Zigbee 3.0 has larger installed base

Key Recommendations: - For new deployments: Choose Zigbee 3.0 Certified devices - For existing deployments: Upgrade hub first, then devices gradually - For interoperability: Hub-based translation bridges profile differences - For future-proofing: Consider Matter/Thread for new projects

975.10 What’s Next

In the next chapter, Zigbee Network Formation, we explore how Zigbee networks are created, how devices join, and the commissioning process in detail.