You buy a smart sensor advertised as working with Matter. You open the app, scan the code, and it fails — or connects and then drops off a day later. Nothing in the box mentioned needing anything else, and the troubleshooting guide suggests moving it closer to your router, which does not help because your router is not what it needs to reach.
The missing component is a Thread border router. It is not obscure hardware, and there is a good chance you already own one. It is just poorly explained by nearly everyone selling these devices.
What changed in 2026
- Border routers became common by accident. Smart speakers, displays, streaming boxes, and hubs increasingly ship with Thread radios, so many households have the capability without knowing it.
- Cross-vendor credential sharing improved. Border routers from different manufacturers coordinating into one Thread network moved from a known pain point to mostly working.
- Matter certification matured. Early interoperability problems settled down, though Matter-over-Thread versus Matter-over-Wi-Fi remains a distinction buyers are not told about clearly.
- Battery life claims got realistic. Multi-year figures for Thread sensors held up in practice, which is the main reason to care about the protocol at all.
What Thread is, and what the border router does
Thread is a low-power mesh networking protocol for small devices — sensors, locks, buttons, bulbs. It exists because Wi-Fi is a poor fit for a battery-powered door sensor: too power-hungry, too much overhead for sending three bytes twice a day.
Thread devices form a mesh among themselves. They can talk to each other but not, by themselves, to your Wi-Fi network, your phone, or the internet. Those are different networks speaking a different language.
A border router is the translator. It has a Thread radio on one side and your normal network on the other, and it routes traffic between them. Without one, a Thread mesh is an island.
|
Thread |
Wi-Fi |
Zigbee |
| Power draw |
Very low |
High |
Very low |
| Mesh |
Yes, self-healing |
No |
Yes |
| Needs a bridge |
Yes — border router |
No |
Yes — hub |
| IP-native |
Yes |
Yes |
No |
| Typical use |
Sensors, locks, buttons |
Cameras, speakers |
Older sensor ecosystems |
The row that makes Thread interesting is IP-native. Zigbee devices need a hub that translates their protocol entirely; Thread devices have real IP addresses, so a border router routes rather than translates. That is why several border routers from different vendors can coexist on one network in a way Zigbee hubs generally cannot — Zigbee vs Z-Wave covers the older ecosystems.
Do you already have one?
Very likely. Check the specifications of any recent smart speaker, smart display, streaming device, or hub in your home for a Thread radio. Many products added it in recent generations without making it a selling point, because "border router" means nothing to most buyers.
If you have one, it is probably already active. Adding a Matter-over-Thread device should find it automatically during setup.
If setup fails, the usual causes are ordinary: the border router is too far from the device you are adding, it is on a different network segment from your phone, or your router has IPv6 disabled. That last one catches people — Thread is IPv6-based, and border routers need IPv6 working on your local network. Some routers ship with it off or with settings that interfere.
Building a mesh that holds up
The characteristic that makes Thread pleasant is that mains-powered devices become routers automatically. A plugged-in smart plug or bulb relays traffic for battery-powered neighbours, so the mesh gets stronger as you add powered devices.
The practical consequence: coverage problems are usually solved by adding a cheap mains-powered Thread device in the gap, not by buying more border routers. A smart plug in the hallway between your hub and a distant sensor often fixes a connection that no amount of border router upgrading would.
Battery-powered devices deliberately do not route — that is what keeps them running for years. So a home consisting entirely of battery sensors has no mesh to speak of; each one talks directly to the border router and coverage is whatever that single radio reaches.
Multiple border routers are fine and generally beneficial, adding redundancy so the mesh survives one going offline. The requirement is that they share the same Thread credentials, which modern ecosystems mostly handle automatically. Where they do not, you get two separate Thread networks and devices that appear in one app but not another — the most common cause of the confusing multi-ecosystem problems people report.
Common mistakes
- Buying a border router when you already have one. Check your existing devices first.
- Disabling IPv6 on your router. Thread depends on it, and this breaks things in ways the app will not explain.
- Assuming all Matter devices use Thread. Matter runs over Wi-Fi too. A Matter-over-Wi-Fi device does not need a border router at all, and this distinction is rarely labelled clearly on packaging.
- Adding border routers to fix range. Add a mains-powered Thread device instead; it extends the mesh where a second bridge does not.
- Expecting battery devices to relay. They do not, by design.
- Putting the border router in a cupboard. It is a radio. Enclosed metal spaces are not helpful.
FAQ
Do I need a hub if I have a border router?
Not necessarily — a border router handles connectivity, and Matter handles device control, so a phone can often manage devices directly. A hub becomes useful for automations that should run when your phone is elsewhere, and for local control when the internet is down.
Can I have border routers from different brands?
Yes, and it is common. They should join the same Thread network by sharing credentials. Where an ecosystem does not participate in sharing, you end up with parallel networks, which is worth checking if devices appear inconsistently across apps.
Does Thread work without internet?
The local mesh does, and locally-executed automations keep working. Anything routing through a cloud service does not. This is a genuine reliability advantage over cloud-dependent Wi-Fi devices — see the Matter smart home guide.
Should I replace my Zigbee devices?
Not on principle. Working Zigbee devices with a functioning hub are fine. Thread is the better answer for new purchases, mostly for IP-native routing and multi-ecosystem support rather than any dramatic day-to-day difference.
Where to go next
For the standard that sits on top of Thread, read the Matter smart home guide. For comparing the older mesh protocols, Zigbee vs Z-Wave, and for choosing the device that will act as your border router, the best smart home hubs.