Definition
Zigbee is a low-power mesh network protocol based on IEEE 802.15.4, operating at 2.4GHz, supporting self-organizing networks and multi-hop relays. It is suitable for short-range scenarios such as smart homes, building automation, and industrial sensors, complementing BLE and LoRa.
Technical Features
Zigbee uses a mesh topology, where nodes can relay multiple hops to extend coverage. The typical transmission distance is 10–100m, with a rate of 250kbps. It supports three roles: Coordinator, Router, and End Device. Zigbee 3.0 unifies different application layer specifications. Compared with BLE, Zigbee is suitable for multi-device mesh networking and low-power sensors; BLE has native mobile support and a mature ecosystem. Compared with LoRa, Zigbee is for short-distance, multi-node scenarios; LoRa is for long-distance, low-data scenarios.
Use Cases
Smart homes (lighting, curtains, temperature control, security); building automation (lighting, HVAC); industrial sensor networks; smart agriculture. Zigbee gateways can connect Zigbee devices to Wi-Fi/Ethernet, with data reported to cloud platforms. New standards such as Matter are integrating Zigbee, BLE, Thread, etc., promoting interconnectivity in smart homes.
Mesh Roles and Sharing the Channel
The coordinator forms the network, routers forward, end devices sleep
Three roles hold the network up. The coordinator chooses the channel and the network identifier and allows devices to join. A network needs it to exist first. A router stays awake, forwards for nodes farther away, and can carry a sensor of its own. An end device may sleep for a long time and wake only to report, or to collect data its parent has buffered, which suits a battery sensor. A sleeping node cannot forward for anyone else. Configure every node as an end device and the network shrinks to a small circle around the coordinator. Configure a battery node as a router and the battery is consumed at the current of continuous listening.
A mesh path is not a fixed wire. After one router loses power, neighbors look for a new route. Recovery time depends on the discovery pace the network allows. During that time reports are lost or slowed. The parent buffers downlink for a sleeping end device. The buffer is finite, and downlink that is too dense is discarded. A sleeping end device therefore suits waking itself to report. It does not suit receiving a long string of commands at any moment.
Many indoor points, at a low rate
It suits switches and sensors with many points and little data per point, inside a room, a floor, or part of a plant, where a delay from a few tenths of a second to several seconds is acceptable. A single hop is limited by walls and by other radios on 2.4 GHz. Coverage is extended hop by hop through routers. It is not extended by driving transmit power to the regulatory ceiling. Kilometer range, or a picture every second, is outside where it applies. A direct phone connection is not a default capability either. The phone side usually passes through a gateway that converts the protocol. The gateway itself should be a router or coordinator that is always on.
Plan the channel and the network identifier before use. If two systems in the same building use the same network identifier and leave joining open, a sensor attaches to someone else's coordinator and appears to drop at random. After installation, close casual joining and open it only in a maintenance window. Each router has a limit on how many children it can hold. Hanging every sensor in a corridor on the nearest router fills that router while a router farther away sits empty.
Channel, network identifier, and aged routes
Channel conflict is a common cause of indoor failure. Wireless LAN and Bluetooth also use 2.4 GHz. On an overlapping channel, retransmissions rise. The symptom is dropouts when the building is busy by day and recovery at night. Choose a channel where the energy on site is lower, and measure again after occupancy. Do not keep the factory channel. Second is an aged route. After a renovation moves a metal cabinet, or removes a router that was always powered, the old path fails. The end node still shows that it once joined, and the frames never reach the coordinator. Diagnose path and parent. Do not look only at the time of the last success.
Third is using a sleeping end device as a router, or allowing the coordinator to lose power. While the coordinator is absent for a long time, new devices cannot join, and some networks cannot even rebuild the neighbor table. Keep the coordinator on a fixed supply, and keep a backup of the configuration. After the network identifier is renamed, old nodes do not follow on their own. Each one has to join again. Finally, if the gateway application retransmits continuously without waiting for a mesh acknowledgement, it fills a channel that is already crowded. Limit retries, and let the device's own reporting period lead.
After the join window is closed, replacing a damaged node needs its own permit procedure. If joining is left open for convenience, a device from a neighboring network attaches when the signals overlap, and the point list gains a strange address that cannot be controlled. Maintenance records should keep the time and the operator of every time joining was opened.