Thread fragmentation: why your house has three meshes
Thread was designed as one self-healing mesh per home. In practice most multi-brand homes run several small ones that cannot see each other.
The finding#
A Thread network is defined by its credentials: a network key, a commissioning credential, a channel, a PAN ID and an extended PAN ID. Any border router that does not have those credentials cannot join that network. It can only create a new one.
Nothing in the original design made a border router ask its neighbors whether a network already existed. So the default behavior of plugging in a second brand's hub is not "the mesh gets bigger", it is "a second mesh appears". The Thread Group's own material describes the consequence plainly: setting up a new border router without access to existing credentials typically forms an entirely new Thread network in a home where one already exists, and fragmenting devices across several networks weakens the resilience of all of them.
Why fragmentation hurts more than it sounds like it should#
A split network is not just untidy. Each consequence is mechanical:
- Every mesh needs its own routers. Thread relies on mains-powered devices to relay for battery-powered ones. Split six mains-powered devices across three networks and each network has two relays instead of six, so coverage in each is worse than the coverage one network would have had.
- Battery devices cannot roam between networks. A sensor is joined to one network. If the routers on that network are the ones at the far end of the house, it does not matter that another network's router is in the next room.
- More networks means more radio traffic on the same channels. Each network beacons, maintains routes and repairs itself independently, and they all share the same 2.4 GHz spectrum. See 2.4 GHz interference for what that band already looks like.
- Diagnosis becomes very hard. Most consumer apps show no Thread topology at all, so the symptom presents as "this sensor is unreliable" with no visible cause.
Where each vendor stands#
| Ecosystem | Thread 1.4 hardware | Credential sharing in practice |
|---|---|---|
| Apple | Apple TV moved to Thread 1.4 around June 2026. HomePod mini and HomePod 2 had not, as of September 2026. | Apple syncs Thread credentials across your own devices through iCloud Keychain, and can hand them to another app on request. Cross-vendor merging is not a supported flow. |
| Nest Wifi Pro and the Google TV Streamer are on Thread 1.4. Nest Hub and Nest Hub Max were still on 1.3. | The Google TV Streamer can generate a QR code to share the network. Press testing in June 2026 reported the flow failing. | |
| Amazon | Most current Echo and eero border routers are documented at Thread 1.3, and Amazon committed to updating Echo devices during 2026. | No credential sharing available, and almost no Thread diagnostics exposed. |
| SmartThings | Station and Aeotec hub. | SmartThings hubs gained the ability to join an existing Thread network in October 2025, which makes SmartThings one of the better-behaved participants. |
| Home Assistant | OpenThread Border Router 1.4 left beta in Home Assistant 2026.6, June 2026. | The most transparent implementation: it shows you the networks it can see, lets you set a preferred one, and can push credentials to or pull them from a phone. |
The full border router hardware list, with the Thread version documented for each, is in the dataset and filterable in the border router finder.
How to tell how many networks you have#
Most platforms will not tell you. Home Assistant will, which is why it is worth installing on a spare computer purely as a diagnostic tool even if you do not intend to use it as your platform. Its Thread panel lists the networks it can discover on your LAN, along with the border routers advertising each one.
Two lighter-weight signals:
- Count your border routers, then count your ecosystems. If you own a HomePod, an Echo and a Nest Hub, you almost certainly have three Thread networks.
- Look at the extended PAN ID wherever your platform exposes it. Two border routers showing different extended PAN IDs are running different networks, full stop.
What actually fixes it#
In order of how much good it does:
- Standardize on one ecosystem's border routers. Unsatisfying, effective. Two Apple border routers share a network. An Apple and an Amazon border router almost certainly do not.
- Make the border router that commissioned your devices the well-placed one. If you cannot merge networks, at least make the network your devices are actually on the one with good coverage.
- Use Thread 1.4 hardware on both ends and run the sharing flow deliberately. It is a real mechanism when both sides support it. Details in why you have three Thread networks.
- Turn off the border routers you do not need, where the platform allows it. Several do not, which is a legitimate complaint about the current state of the ecosystem.
What is coming#
Thread Direct was announced in June 2026: commissioning a device from a phone with no border router present at all. It is expected in Thread 2.0 with no published timeline, and it addresses onboarding rather than merging.
The more consequential change would be Matter's Joint Fabric, which lets several controllers co-administer one fabric. That is a different layer of the stack and it does not merge Thread networks by itself, but it removes one of the reasons households end up running several ecosystems as peers in the first place. As of September 2026, no consumer platform has shipped it, and its simpler predecessor from Matter 1.4 was never shipped by anyone. The feature gap tracker follows both.
Method and updates#
This report is compiled from the Thread Group's published specification material, vendor documentation, platform release notes and the border router dataset we maintain. Where a claim rests on press testing rather than vendor documentation, it is described that way in the text. Vendor Thread versions are recorded from the newest publicly documented firmware, which is not always the firmware in the box.
Version 2026.09. Scheduled for review at least every six months, and immediately when a major vendor ships Thread 1.4 to hardware that currently lacks it. The border router data is published as JSON under CC BY 4.0.
How do I know if I have more than one Thread network?
Compare the extended PAN ID that each border router reports, if your platform shows it. If it does not, a Home Assistant installation on any spare machine will list the Thread networks visible on your LAN, including ones belonging to other ecosystems.
Can I merge two Thread networks?
Only through credential sharing, and only if both border routers support Thread 1.4 and expose the flow. There is no way to merge two established networks retroactively without re-commissioning devices onto one of them.
Does having several Thread networks break anything?
Nothing stops working, but everything gets weaker. Each network has fewer routers to relay through, battery devices cannot use routers on other networks, and all of them share the same radio spectrum. It shows up as unreliability rather than failure, which is what makes it hard to diagnose.
Should I buy a second Thread border router?
Yes if it is from the same ecosystem as your first, because that improves coverage and removes a single point of failure. Be careful about a border router from a different ecosystem, because it will most likely start a network of its own.
Is this Thread's fault or the platforms' fault?
Both, in different measures. The original design left merging out of scope, which is a standards problem. The standard fixed it in September 2024, and two years later the largest platforms still had not shipped it to their most common hardware, which is not a standards problem.
Primary sources
Specification and vendor documentation we checked while writing this page. Where a claim depends on firmware behaviour rather than a published spec, the page says so inline.