Zigbee is a low-power, low-data-rate wireless mesh networking standard built on the IEEE 802.15.4 physical and MAC layers, operating in the 2.4 GHz band globally (and 868/915 MHz in some regions), with application-layer profiles defined by the Zigbee Alliance (now the Connectivity Standards Alliance).
In practice
Zigbee is commonly used in home automation, building control, smart metering, and industrial sensor networks where battery-powered nodes must communicate over distances of 10-100 m and where a mesh topology is needed to extend range. Typical data rates are 250 kbps at 2.4 GHz, which is adequate for sensor readings, switch events, and short command packets but not for audio or video. A Zigbee network consists of at least one coordinator (which forms the network), optional routers (which can relay traffic and run from mains power), and end devices (which are typically battery-powered and sleep most of the time).
Frequently asked
How does Zigbee's mesh work in practice?
Routers maintain neighbor and routing tables and forward packets on behalf of sleeping end devices. End devices associate with a single parent router or coordinator; when they have data to send or receive, they wake, transact with their parent, and return to sleep. The mesh is self-forming and can self-heal by rerouting around failed nodes, though convergence time after a topology change can be tens of seconds in large networks.
What is the difference between Zigbee and Thread?
Both are IEEE 802.15.4-based mesh protocols, but they differ at the network layer. Zigbee defines its own network and application layers via published specifications from the Connectivity Standards Alliance. Thread uses IPv6 and 6LoWPAN, making each node a native IP device that can be addressed directly from a standard IP network without a translation gateway. Thread also serves as the network/transport substrate for one of Matter's transport paths, while Zigbee uses its own application profiles (e.g., Zigbee Cluster Library). For new designs targeting Matter ecosystems, Thread is generally preferred; Zigbee remains widely deployed in existing installations.
What hardware is typically needed to add Zigbee to an embedded design?
Most designs use an IEEE 802.15.4 radio SoC that includes an integrated
MCU, such as the Silicon Labs EFR32MG series, Texas Instruments CC2652, or NXP JN5189. These ship with vendor SDK stacks (Silicon Labs EmberZNet, TI Z-Stack) that handle the Zigbee network and application layers. Alternatively, a separate host MCU can drive a Zigbee network co-processor (NCP) over
UART or
SPI.
How does Zigbee's power consumption compare to Bluetooth Low Energy?
Both protocols are designed for low average power and can achieve coin-cell lifetimes of one to several years in typical sensor applications. The actual current budget depends heavily on duty cycle, packet frequency, and sleep current of the chosen SoC rather than on the protocol itself. Zigbee end devices spend most of their time in a deep sleep state, waking only to poll their parent or transmit.
BLE similarly uses short advertising or connection events. Neither protocol has a categorical power advantage; the application profile and hardware matter more.
Can Zigbee coexist with Wi-Fi in the 2.4 GHz band?
Coexistence is possible but requires attention to channel planning. The 2.4 GHz Wi-Fi channels 1, 6, and 11 (non-overlapping in North America) partially overlap with several Zigbee channels. Zigbee channels 25 and 26 are commonly chosen to minimize overlap with Wi-Fi channels 1 and 6, though channel 26 may have limited availability or reduced transmit power in some regulatory regions, so channel selection should be verified for the target market. Many radio SoCs also implement hardware coexistence mechanisms (PTA, packet traffic arbitration) for systems where both radios share the same board.
Differentiators vs similar concepts
Zigbee is often compared to Thread, Z-Wave, and
Bluetooth Low Energy for similar IoT use cases. Z-Wave operates in the sub-GHz band (868/908 MHz depending on region), avoids 2.4 GHz congestion, and has a stricter certification program, but its ecosystem is smaller. Thread shares the same IEEE 802.15.4 PHY/MAC as Zigbee but uses IPv6/6LoWPAN networking and is the network/transport substrate for one of Matter's transport paths. BLE mesh (Bluetooth Mesh) is another mesh option on the same 2.4 GHz band but uses a flooding-based publish/subscribe model rather than a routed mesh. Compared to these alternatives, Zigbee has a large installed base, a mature interoperability certification program (Zigbee Certified), and a broad set of off-the-shelf application profiles (lighting, HVAC, metering).