Zigbee
Low-power mesh networking on the same 802.15.4 radio as Thread, with its own application layer and its own addressing rather than IP. Long established in building automation and consumer devices; a hub translates it into whatever the rest of the system speaks.
Small messages that either repeat constantly or fire once. Bandwidth is almost never the problem.
What kills it. Latency and loss on the messages that fire once. A repeating level survives a dropped packet; a GO does not.
Why this one, and not what the category suggests. Same: a mesh whose payload is control, usually lighting and sensors.
Multicast
- Group addressing within the Zigbee network, not IP multicast.
What goes wrong
What speaks Zigbee (1)
| Product | Direction | Notes |
|---|---|---|
| Home Assistant Open Home Foundation |
bidirectional | Via a coordinator. |
Typical use
- Installed sensor and control networks, often already present in a building.
- Consumer devices being brought into a venue system through a hub.
Sources
- Zigbee — Connectivity Standards Alliance primary
Known gaps on this entry: default_ports, implementations. If you can source one of them, that is a ten minute pull request.
Edit this entry on GitHub — one file, editable in your browser, and your handle goes on it permanently.
Work at Connectivity Standards Alliance? Confirm or correct this entry — it is free, it stays free, and nothing about it is for sale.