Zigbee
Zigbee is a low-power 2.4 GHz mesh protocol (IEEE 802.15.4) that has been the workhorse of affordable smart home devices for over a decade — Hue bulbs, IKEA and Aqara sensors, and thousands of others. Devices pair to a Zigbee coordinator (a hub or USB stick), not to Wi-Fi, and mains-powered devices extend the mesh as routers.
Zigbee 3.0, current since 2016, unified the earlier profile fragmentation (ZLL, ZHA) into one certifiable standard, and its cluster library became the basis for Matter’s data model. The ecosystem’s strength is sheer device breadth and price: our dataset tracks 5,405 Zigbee devices supported by the open-source Zigbee2MQTT project alone, from flagship brands down to very cheap Tuya-made hardware.
The catch is that Zigbee interoperability is real but imperfect: manufacturers extend the standard with private clusters, so a device may pair with any coordinator yet expose its full features only on the maker’s own hub or on community-maintained platforms (Zigbee2MQTT, ZHA) where those quirks have been reverse-engineered. Zigbee also shares the 2.4 GHz band with Wi-Fi, so channel planning matters in dense environments.
| Radio | IEEE 802.15.4 at 2.4 GHz, 250 kbit/s, channels 11–26 (2405–2480 MHz) |
|---|---|
| Zigbee 3.0 published | December 2016, unifying the older ZLL and ZHA application profiles |
| Governance | Connectivity Standards Alliance — the Zigbee Alliance until it renamed in May 2021 |
| Devices in this dataset | 5,405, from the Zigbee2MQTT supported-device list |
| Theoretical network size | Over 65,000 nodes from 16-bit addressing; real hubs cap far lower |
| Least Wi-Fi overlap | Zigbee channels 15, 20, and 25 sit in the gaps between Wi-Fi 1, 6, and 11 |
How much of the standard is actually standard
Zigbee 3.0 ended a genuinely messy period. Before it, a bulb built to the Zigbee Light Link profile and a sensor built to Zigbee Home Automation could sit on the same radio and refuse to acknowledge each other. The 2016 unification collapsed those profiles into one certifiable stack built on the Zigbee Cluster Library — the same clusters-and-attributes model Matter later adopted for its own data model.
What remains non-standard is everything manufacturers bolt on. The specification reserves a manufacturer-specific range, and vendors use it heavily: Tuya-derived hardware in particular routes most of its functionality through a single proprietary cluster (0xEF00) rather than standard ones, so a Tuya thermostat pairs anywhere and does almost nothing until somebody has reverse-engineered its datapoints. That reverse engineering is precisely what Zigbee2MQTT’s converters and ZHA’s quirks are.
The practical rule: standard capabilities — on/off, level, colour, contact, occupancy, temperature — work on any coordinator. Anything the marketing calls a feature is a coin flip until you check the device against a specific platform. That is what our per-device pages record.
Channels, Wi-Fi, and the interference that actually bites
Zigbee uses sixteen 2 MHz channels spaced 5 MHz apart across the 2.4 GHz band, numbered 11 through 26. Wi-Fi channels are 20 MHz wide, so a single busy Wi-Fi network sits on top of four or five Zigbee channels at once. If your Wi-Fi is on the conventional 1, 6, and 11, the quiet spots are Zigbee 15, 20, and 25 — and 25 or 26 above Wi-Fi 11 is often the calmest of the lot, with the caveat that some radios reduce transmit power on channel 26.
Changing the Zigbee channel is disruptive: on most coordinators, battery end devices do not follow the move and have to be re-paired. Pick a channel when you build the network, not after you have 40 devices on it. If you are already deployed and struggling, moving the Wi-Fi channel is usually the cheaper intervention.
The interference source people never suspect is USB 3.0. A coordinator dongle plugged directly into a USB 3 port on a NUC or a Raspberry Pi sits inside a cloud of 2.4 GHz broadband noise, and the symptom is devices dropping off at random distances. A one-metre USB extension cable, moving the dongle away from the machine and any SSD enclosure, fixes more Zigbee range complaints than any amount of channel planning.
Brand locks, and what “Zigbee compatible” means on a box
Zigbee is a standard; pairing policy is not. Several popular hubs run a perfectly ordinary Zigbee coordinator and simply refuse to admit devices that are not their own brand — the Philips Hue Bridge, IKEA DIRIGERA, Aqara hubs, and the Bosch Smart Home Controller II all behave this way to varying degrees. A third-party sensor that fails to join one of those is working exactly as designed.
Open coordinators are the opposite: Hubitat, SmartThings, Homey Pro, SONOFF iHost, and any USB dongle such as the SONOFF ZBDongle-E or SMLIGHT SLZB-06 running Zigbee2MQTT or ZHA will accept anything that speaks Zigbee. This is the fork in the road for anyone buying cheap sensors in volume.
Two more behaviours worth knowing. A Zigbee device remembers its last network and will ignore a new coordinator until it is factory reset — the single most common “broken on arrival” report for second-hand devices. And Zigbee Green Power covers battery-free, energy-harvesting switches such as Friends of Hue wall controls, which many coordinators support only partially.
Frequently asked questions
Is Zigbee still worth buying in 2026?
Yes, on price and breadth. Zigbee2MQTT supports 5,405 devices against 1,824 Matter certifications in the same dataset, and Zigbee sensors routinely cost a third of their Matter-over-Thread equivalents. The cost is that you must run a coordinator — a hub or a USB dongle — and accept that new ecosystems will reach those devices through a bridge rather than natively.
Do all Zigbee devices work with all Zigbee hubs?
For standard functions, mostly. For everything else, no. Two things break the expectation: hubs that deliberately only pair their own brand — Hue, IKEA DIRIGERA, Aqara, Bosch — and manufacturer-specific clusters that only some platforms decode. A device supported by Zigbee2MQTT or ZHA is the closest thing to a guarantee that its full feature set is reachable.
Does Zigbee interfere with Wi-Fi?
They share the 2.4 GHz band, so they interfere with each other. Wi-Fi wins, because it transmits at much higher power. Put your Zigbee network on channel 15, 20, or 25 depending on where your Wi-Fi sits, keep the coordinator away from the router and from USB 3.0 ports, and the two coexist fine in most homes. Congested apartment buildings are where Z-Wave’s sub-GHz band earns its premium.
How many Zigbee devices can one network handle?
The addressing allows over 65,000, which is irrelevant. Real ceilings come from the coordinator: the Hue Bridge allows 50 lights and 12 accessories, most consumer hubs land somewhere between 50 and 200, and Zigbee2MQTT installations of several hundred devices are routine given enough mains-powered routers. Router density, not the node count, is what limits real networks.
Is Matter replacing Zigbee?
Not on any near timeline. Matter borrowed Zigbee’s data model but runs on different radios, and the Zigbee catalogue is still roughly three times larger and considerably cheaper. What is happening instead is that Zigbee is increasingly reached through Matter bridges — the Hue Bridge, DIRIGERA, Aqara hubs — so Zigbee becomes the device layer and Matter the ecosystem layer.