note
Zigbee mesh stability and Thread border routers
Why the network starts dropping devices after a few weeks, and what Thread changes — on the same 2.4 GHz band.
The most common report is not “it does not work” but “it was fine for a while”. That is almost always a network design question, not a faulty device.
What makes a Zigbee mesh stable
- Enough mains-powered routers. Battery devices are end nodes: they do not forward traffic. If the network is almost all sensors, there is no mesh — just a star around the coordinator. Rule of thumb: at least one mains-powered device on every floor and behind every major wall run.
- A channel that does not collide with Wi-Fi. Both live on 2.4 GHz. Wi-Fi channels 1/6/11 are wide; the Zigbee channel has to sit between them, not on top of them.
- The coordinator moved away. 2.4 GHz noise from a USB 3.0 port right next to it measurably degrades reception. A short extension lead often helps more than any software setting.
- Patience while it re-learns. Mesh routes do not settle instantly. After moving devices, the network needs hours.
What Thread and the border router change
Thread is IPv6-based, so devices are part of the network directly rather than hanging off a gateway. The border router is where the Thread network meets the ordinary IP network — and there can be several at once, redundantly: if one drops out, the network keeps working. That is a real difference from Zigbee’s single coordinator.
What it does not solve: Thread runs on the same 2.4 GHz band. If Zigbee, Thread and Wi-Fi sit alongside each other, the band has to be planned as a whole. A newer standard does not create more room in the air.
The practical decision
Replacing a stable existing Zigbee network with Matter is not worth it today. In a new installation, though, it is worth designing in a Thread border router — not to replace Zigbee, but to leave somewhere to grow.
If your existing network keeps dropping devices, it can be surveyed remotely.