Fixing unreliable Thread networks and border router problems

The short version

• Find which link failed before changing anything. A Thread accessory reaches your phone through three links: its radio path to a Thread router, the mesh to a border router, and your home network from the border router to your phone or hub. One accessory failing points at the first; every Thread accessory failing at once points at the border router or your router's settings.
• Several Thread networks in one home is normal, and it costs you. Home Assistant's documentation says each vendor "forms their own Thread network when you start using their products", and devices "can't roam between the Thread networks". A border router from another brand only adds coverage or redundancy if it's on the same network as your accessories.
• Thread 1.4 is the fix on paper, and it's arriving unevenly. Samsung documents Thread 1.4 with credential sharing on its SmartThings hubs, and Amazon lists exactly one Echo on 1.4. Apple and Google don't state a version in their support pages. Press reports (on Apple TV beta software in 2025, and on Google's TV Streamer and, from user posts, Nest devices in 2026) say 1.4 is arriving; neither company has confirmed it.
• Two or more border routers on the same network, near the accessories, plus mains-powered Thread devices between them. Battery-powered devices never extend the mesh.
• You can look. Home Assistant's Thread panel groups every border router it finds by network, the Eve and Nanoleaf apps show their own devices' Thread network, and a DNS-SD browser lists the border routers on your Wi-Fi, with each one's network name on OpenThread-based models.

This is the diagnosis companion to our Apple Home, Matter and Thread setup guide, which covers how Thread works, which Apple devices are border routers and the router settings that cause "No Response". This article applies to Google Home, Alexa, SmartThings and Home Assistant as well.

The three links between your phone and a Thread accessory

Our Apple Home guide explains what a border router does. The detail that matters for troubleshooting is in the Thread Group's border router white paper: accessories register with a border router, and border routers on the same mesh "respond on behalf of all the devices on the mesh" when your phone looks for them.

Diagnosis order: symptom, cause, check, fix

Read across for your symptom. The checks are ordered so the free, fast ones come first. Where a fix is a maker's own instruction, the maker is named.

If you'd rather follow a sequence, test after each step: update the phone, border routers and accessory firmware (Nanoleaf starts with border router firmware); confirm the hub (one active under Home Hubs & Bridges in Apple Home; elsewhere, a model on the maker's list in the ecosystem table); check the network (same network name, no guest network, isolation or VPN); restart in Apple's order (modem and router, then hubs and border routers, then accessories) and wait; look at the mesh with the tools below; and only then change hardware, with a mains-powered Thread device near the weak spot or a second border router on the same network.

Why you have more than one Thread network

A Thread network is defined by its credentials, not its brand. Home Assistant's documentation says "you can end up having a Home Assistant, an Apple, and a Google Thread network in your home", each with its own credentials. The Thread Group's Thread 1.4 white paper explains the mechanism. A new border router can only join an existing network if the app setting it up can get that network's credentials. When it can't, "setting up a new Thread Border Router is possible but would typically cause the forming of an entirely new Thread network, in a home where one already exists." It names the cost: "This fragmentation of Thread devices over multiple networks could weaken the overall mesh network resilience and connectivity."

What that means for reliability:

• Each network has fewer routers. Your Apple accessories can't relay through a plug that sits on the Google network, so each mesh is thinner than the devices in the house suggest.
• Redundancy is per network. Two HomePods on Apple's network and a Nest Hub on Google's is one backup for the Apple accessories, not two.
• Moving a device between networks usually means re-adding it. eero's support article says that to move to a new eero Thread network "you'll need to reset any third-party devices and reconfigure" them. Google warns that if your credentials are kept only on a phone you lose or replace, "a factory reset might be needed" to set devices up again.

Home Assistant states the goal plainly: "In theory, it would be better to join all Thread networks into a single network to increase the size of the mesh network."

What Thread 1.4 changes, and who has shipped it

Thread 1.4, released September 4, 2024, adds standard credential sharing, which the white paper lists under "Avoiding Network Fragmentation". When a user starts it on a 1.4 border router (or its app), the border router shows a one-time QR code or nine-digit code that gives another app temporary access to the network's credentials, so a new border router or device joins instead of starting a new network. Our Apple Home guide summarizes the other 1.4 features.

Credential sharing only helps when the border router you already have supports it. Here's what each maker documents, checked November 7, 2026:

Getting back to one network

1. See what you have. Use the tools below to list each border router and the network it's on.
2. Pick the network to keep. Usually your main ecosystem's network, the one with the most mains-powered Thread devices on it. Everything else joins that one.
3. Bring the other border routers over, using each maker's join path. Nanoleaf controllers use credentials already on the phone. In Home Assistant, follow its "existing network" steps to join another vendor's network and make it preferred. SmartThings hubs on 0.58.10 use Manage Thread network to unify with a nearby network. Before you start, make sure the phone you use has the kept network's credentials: Home Assistant notes that "the preferred network of the mobile device is being used" when you add devices.
4. Re-add accessories stranded on the old network, one at a time: reset each by the maker's instructions and add it again. Espressif's write-up of a SmartThings migration notes one exception: devices already on the SmartThings hub's own network are told to move automatically when the hub migrates.
5. Don't regenerate credentials to tidy up. eero says regenerating "creates a new Thread network", and that devices on the old one "may continue to use the old network details".

Where a brand can't join (an Echo on 1.3, for example, if Nanoleaf's account of Alexa above is current), it's often simpler to leave that border router alone and add accessories to the network you kept. A second network costs coverage only if accessories are on it.

Your router: IPv6, multicast and the same network

This is where Thread trouble that looks like a radio problem often turns out to be a Wi-Fi setting. The last link rests on two things that stay on one network segment, as our Apple Home guide explains: the border router's IPv6 Router Advertisements, which carry the route to the Thread network as a Route Information Option (RFC 4191), and mDNS discovery. Three consequences:

• IPv6 inside the home, not from your provider. If no router on your network is advertising an IPv6 prefix, OpenThread's documentation says the border router "generates a ULA on-link prefix" (a local-only one) and advertises it, so an IPv4-only internet connection doesn't stop Thread. What breaks it is anything that drops IPv6 between devices on your network. Nanoleaf's checklist still asks you to make sure IPv6 is enabled on the router, which is a harmless step to take.
• Multicast must flow. Home Assistant warns that "Some mesh Wi-Fi systems aggressively filter multicast traffic on Wi-Fi", which "can prevent your phone from discovering the border router via mDNS", and says to check settings "related to multicast, IGMP snooping, or mDNS."
• One flat network. Home Assistant's Matter documentation says to keep the network "as simple and flat as possible" and to keep border routers on the same VLAN as the Home Assistant host. An mDNS proxy between VLANs relays discovery but not the Router Advertisements; our VLAN guide for HomeKit and Matter covers why.

The setting-by-setting table (guest networks, client isolation, VLANs, multicast optimization, double NAT, VPN apps) is in our Apple Home guide, and double NAT has its own fix. Home Assistant users have one more case: if Thread devices "join the network but cannot be reached", its troubleshooting points at missing IPv6 support in the host, any hypervisor or Docker layer, or the router.

The mesh itself: routers, sleepy devices and channels

Which devices extend the mesh

Google's Thread page puts it simply: always-on devices "plugged into power, like smart plugs or speakers" act as mesh extenders, while battery-powered devices "can 'sleep'" and don't. Eve says mains-powered devices such as Eve Energy "can act as router nodes within your Thread network and relay data packets", while battery devices "represent endpoints". Google adds that if a device goes offline, "the network automatically heals itself by finding a new path", but not instantly: that's why makers give waiting times after restarts (see the last row of the diagnosis table).

Thread and 2.4 GHz Wi-Fi channels

Thread uses IEEE 802.15.4 channels 11 to 26 in the 2.4 GHz band, the same band as 2.4 GHz Wi-Fi. Silicon Labs, which makes Thread chips, describes "16 non-overlapping 2 MHz bandwidth channels at 5 MHz spacing", and notes that in the US, channels 25 and 26 "require reduced transmit power levels". Home Assistant's Thread documentation says "Thread channels 11 through 24 can overlap with 2.4 GHz Wi-Fi, including common Wi-Fi channels like 1, 6, and 11", and "Thread channel 26 is the least likely to experience Wi-Fi interference."

RouterHaus's calculation of where each Thread channel falls, from the published center frequencies (Thread channel k at 2,405 + 5(k − 11) MHz, as in OpenThread's source; Wi-Fi channel n at 2,407 + 5 × n MHz) and a 20 MHz-wide Wi-Fi channel:

The gap channels are neighbors, not refuges. Silicon Labs measured its own 802.15.4 chip (running Zigbee, which uses the same radio as Thread) against Wi-Fi transmitting nonstop on channel 1: with Wi-Fi arriving at −30 dBm, it could still receive signals down to −87 dBm on channel 15, against −96 dBm on channels 17 to 26. It adds that strong Wi-Fi can also block an 802.15.4 radio from transmitting by making the channel look busy. A 40 MHz Wi-Fi channel on 2.4 GHz covers twice as much of the band; Apple recommends 20 MHz on 2.4 GHz to avoid problems "near other Wi-Fi networks and 2.4 GHz devices".

What you can change depends on the border router. Home Assistant's OpenThread border router has a Change channel option (Settings, Connectivity, Thread, then the border router's menu); it schedules the switch "approximately five minutes later" and warns that "Some Thread devices might not move to the new channel automatically." We found no documented way to choose the channel on Apple, Google or Amazon border routers. On those, the lever you control is your Wi-Fi: keep 2.4 GHz at 20 MHz, and if your Thread network's channel is known (Home Assistant shows it under Network information when it has the credentials), pick whichever of Wi-Fi channels 1, 6 and 11 is farthest from it; Silicon Labs says 802.15.4 performance improves with more frequency separation from Wi-Fi.

How many border routers, and where

We found no maker that publishes a number of border routers per home size. This table is RouterHaus guidance built on three documented points: the Thread Group's statement that border routers on a shared mesh back each other up if one fails (quoted in our Apple Home guide), Home Assistant's advice to have a border router "nearby" the Thread devices, and the fact that only border routers on the same network count.

More isn't always better on older firmware. The Thread 1.4 white paper says 1.4 reduces the size of the mesh's routing data to prevent "routing issues caused by the network data reaching its size limit when the number of Border Routers increases." We found no published figure for how many border routers is too many on a 1.3 network, so add them for coverage where accessories are, not by habit.

If you're replacing your Wi-Fi anyway, some mesh systems put a border router in every unit: eero says "Each Thread-capable eero acts as a border router" (Thread 1.3.0, per eero and Amazon) on models such as the eero 7 and eero Pro 7, and Google lists the Nest Wifi Pro. Like other brands' border routers, they typically start their own network unless you bring them onto yours, so they help most when the mesh router's network is the one your accessories use. Don't buy a router to fix Thread: a border router on the right network, in the right room, does the same job.

Tools to see your Thread network

Apple's Home app shows which hub is active, but we found no Apple documentation of a Thread network view in Home. These tools fill the gap: