Zigbee is a low-power wireless mesh network standard used by hundreds of millions of smart bulbs, switches, sensors, locks and thermostats. If a smart home device runs on a coin cell and talks to a hub rather than directly to Wi-Fi, there is a good chance it is Zigbee. It is also widely used in commercial lighting, building automation and utility metering.
The standard has been around for two decades and has gone through several revisions, which is why older devices and newer ones do not always get along. This guide explains the layers that make up Zigbee, the roles devices play in a mesh, how the application layer lets a switch from one vendor control a bulb from another, how security and commissioning work, and how it compares with Thread, the newer standard built on the same radio.
The radio: IEEE 802.15.4
Zigbee’s physical and medium access layers are IEEE 802.15.4, a standard for low-rate, low-power personal area networks. The common deployment is the 2.4 GHz band, which is available worldwide and offers sixteen channels at a raw data rate of 250 kbit/s. Sub-GHz variants exist for specific regions and for utility use. The 802.15.4 frame is small, with a maximum of 127 bytes including headers, which keeps transmissions short and cheap.
2.4 GHz is shared with Wi-Fi and Bluetooth. Zigbee channels overlap with Wi-Fi channels, and a busy Wi-Fi network on the same frequency will degrade a Zigbee mesh. Choosing a Zigbee channel that sits between the local Wi-Fi channels is a standard installation step.
Mesh roles
A Zigbee network has three device roles.
The coordinator forms the network, chooses the channel and network identifier, and acts as the Trust Center that manages security keys. There is exactly one per network, and in a smart home it is the hub.
Routers are mains-powered devices that relay traffic for others and allow new devices to join through them. Every bulb, smart plug and wired switch is normally a router. Adding routers extends coverage and adds redundant paths.
End devices do not route. They are usually battery powered, sleep most of the time, and depend on a parent router that buffers messages for them until they wake and poll. A door sensor or a battery thermostat is an end device.
Routing uses an on-demand distance-vector algorithm: when a device needs to reach another, it discovers a route and caches it, and the mesh heals around failed nodes by rediscovering. Network layer addresses are 16-bit, assigned at join, with 64-bit IEEE addresses as permanent identifiers.
The practical consequence is that a Zigbee network needs enough mains-powered routers to carry the battery devices; a home with twenty sensors and only a hub will be unreliable.
The application layer: clusters and profiles
The part of Zigbee that makes interoperability possible is the Zigbee Cluster Library (ZCL). A cluster is a standardized set of attributes and commands for one function. The On/Off cluster has an attribute for the current state and commands for on, off and toggle. The Level Control cluster handles dimming. Temperature Measurement, Occupancy Sensing, Door Lock and Color Control are others. A device exposes one or more endpoints, each implementing a set of clusters as a server (holding the state) or a client (sending commands).
A switch binds its On/Off client to a bulb’s On/Off server, after which pressing the switch sends a toggle command directly to the bulb, without the hub in the path. Groups let one command address many bulbs at once, which is why Zigbee lighting responds to scene changes simultaneously rather than in a visible ripple.
Earlier versions of the standard had separate application profiles (Home Automation, Light Link, Smart Energy) that defined which clusters a device type used, and devices from different profiles often could not interoperate. Zigbee 3.0, released in 2016, unified the profiles into a single specification with mandatory commissioning behavior, which is why devices certified under Zigbee 3.0 generally work with any Zigbee 3.0 hub.
Zigbee Green Power extends this to batteryless devices, such as switches powered by the energy of the button press.
Security and commissioning
All Zigbee traffic is encrypted with AES-128 using a network key shared by every device on the network. Devices receive the network key when they join, encrypted with a link key. In the past the link key was often a well-known default, which meant anyone listening at the moment of joining could capture the network key. Zigbee 3.0 addressed this with install codes: a device-specific code printed on the product or packaging that the installer enters into the hub, from which a unique link key is derived, so the network key is never exposed. Devices can also establish unique link keys with the Trust Center after joining.
Joining is initiated by putting the hub into a permit-join window and powering or resetting the device. Zigbee 3.0 standardized the steps so that a device searches channels, finds an open network and joins without vendor-specific tricks.
Where Zigbee is used
Smart home lighting and sensors remain the largest category, including the ecosystems of major bulb and hub vendors and the open-source hubs built on Home Assistant with a USB coordinator. Commercial smart lighting in offices and warehouses uses Zigbee for its group control and mesh coverage. Utility smart meters in some countries use Zigbee Smart Energy to talk to in-home displays.
Zigbee and Thread
Thread uses the same 802.15.4 radio and a similar mesh, so the two are frequently compared. The differences are in the upper layers. Thread carries native IPv6 through 6LoWPAN, so every Thread device is an IP endpoint reachable from the rest of the network through a border router, and any number of border routers can serve a network. Zigbee has its own network layer and a single coordinator, and reaching a Zigbee device from the internet always goes through the hub’s software translation.
Thread defines no application layer; Matter supplies one. Zigbee defines its own, the ZCL, which Matter’s data model was partly derived from. The Connectivity Standards Alliance, formerly the Zigbee Alliance, maintains both Zigbee and Matter, and many hubs bridge Zigbee devices into Matter.
For new consumer devices, Thread plus Matter is where the ecosystem investment is going. For existing installations, lighting systems with established ZCL tooling, and markets where Zigbee certification and supply chains are mature, Zigbee remains a sound choice with a far larger installed base. The Thread guide covers the other side of this comparison.
When to use Zigbee
Choose Zigbee for battery-powered sensors and mains-powered actuators inside a building where a hub is acceptable, where you want proven interoperability through Zigbee 3.0, and where group-addressed lighting control matters. Avoid it for devices that need high bandwidth, for sites without enough mains-powered routers, in environments with heavy 2.4 GHz interference, and for outdoor or wide-area deployments where LoRaWAN or cellular fit better.
Where to go next
- Thread explained covers the IP-based mesh built on the same radio.
- Matter explained describes the application layer that bridges both.
- The smart home, explained places Zigbee among the home ecosystems.
- IoT connectivity overview compares all the radio options.
Topics: Zigbee, mesh, smart home, IEEE 802.15.4, protocols