English is currently available.
Zigbee, Thread & Matter DISCUSSION
I am planning a few DIY sensors and switches around nRF52840 and ESP32-C6 boards, both of which advertise support for Zigbee, Thread and Matter. I cannot work out whether these are three competing standards or layers of one stack. Some articles say Matter replaces Zigbee, others say Matter runs on Thread.
How do the three fit together, and what does each one require in terms of hubs or border routers?
They sit at different layers. Zigbee and Thread are both low-power mesh networks using the IEEE 802.15.4 radio at 2.4 GHz (250 kbit/s, channels 11 to 26), which is why the same chip can run either. Zigbee is a complete stack: its own network layer plus an application layer, the Zigbee Cluster Library, that defines what an on/off light or a temperature sensor looks like. Thread is only a network layer, but an IPv6 one: every node has an IP address, and it says nothing about lights or sensors.
Matter is an application layer that runs over IP. It can use Wi-Fi, Ethernet or Thread underneath, and uses Bluetooth LE only for commissioning a new device.
So the accurate statements are: Matter runs on Thread (and on Wi-Fi and Ethernet), and Matter does not run on Zigbee, because Zigbee is not an IP network. Zigbee devices can still appear in a Matter system through a bridge, a hub that speaks Zigbee on one side and presents each device as a Matter endpoint on the other.
The family resemblance is real. Matter's data model of endpoints, clusters, attributes and commands was derived from the Zigbee Cluster Library, and the same organisation, the Connectivity Standards Alliance (formerly the Zigbee Alliance), maintains both. Thread is maintained separately by the Thread Group.
Infrastructure for each: a Zigbee network needs one coordinator, usually a USB dongle or a hub, plus software that translates Zigbee to whatever your controller speaks. A Thread network needs a border router to pass IPv6 packets between the 802.15.4 mesh and your Wi-Fi or Ethernet network; many recent smart speakers and hubs include one. Matter over Wi-Fi needs only the access point. In every Matter case you also need a Matter controller (a phone ecosystem or a home automation server) that commissions devices and holds the fabric credentials.
One practical advantage of Matter is multi-admin: a device can be joined to several controllers' fabrics at once, so it is not locked to a single ecosystem.
For DIY work the choice is mostly about tooling and battery life. Zigbee is mature, and open-source coordinators accept custom devices, so it is a comfortable path for battery sensors today. Thread with Matter is the direction new commercial products are taking, but the firmware is much larger and commissioning involves certificates and test vendor IDs, which adds friction for hobby projects.
A sleepy Zigbee or Thread end device wakes for a few milliseconds to poll its parent and can run for years on a small battery. A Wi-Fi Matter device is simpler to get going on an ESP32 but suits mains-powered things like plugs and lights. On the ESP32-C6 and nRF52840 you can try both and decide per device.
