What is a Thread border router (and do you need one)?

Most people meet the phrase "Thread border router" at the worst moment: halfway through pairing a new Matter sensor, when the app stops and says one is required. The useful part of the answer is that plenty of Australian homes already have one sitting on the TV cabinet.

What a Thread border router does

Thread is a low-power mesh radio for small battery devices: sensors, buttons, locks, blinds. It uses the same 802.15.4 radio as Zigbee, with one big difference. Every Thread device gets its own IPv6 address, so it is a member of an IP network rather than something a hub has to translate for.

That is where the border router comes in. It sits on both sides at once: an 802.15.4 radio facing the Thread mesh, and Wi-Fi or Ethernet facing the rest of your network. It routes packets between the two and does nothing else with them. Home Assistant's documentation puts it plainly: the border router does not look at the content of these packets, it just forwards them.

So it is not a smart home hub, even though most of the devices that contain one are also hubs. Thread on its own cannot turn a light on. Control comes from a layer above it, which in practice means Matter or Apple's HomeKit. A border router carrying Matter traffic cannot read it either: that traffic is encrypted between your controller and the device. Using a Nest Hub as your border router does not put Google in charge of your devices.

The devices you may already own

Border routing is almost never the reason a device exists. It gets bundled into speakers, displays, streamers and mesh routers as a side function, which is why so many people have one and don't know it.

Two exclusions are worth naming. A Philips Hue Bridge is not a Thread border router: it is a Zigbee bridge, and Hue's own support pages say that connecting a Matter-badged Hue light without the Bridge needs a border router from somewhere else. A Matter controller is not automatically one either, because plenty of devices commission and control Matter over Wi-Fi with no 802.15.4 radio at all.

Every brand above sells into Australia, but not every model in every range does, and what is on shelves moves around. Check the model rather than the brand, and check it for the radio rather than for a Matter badge. Google's Matter hubs are worth a look device by device.

How to tell if you already have a Thread network

Nothing announces it. If you own one of the devices above, set it up in its app and left it powered on, there is a Thread network running in your house whether or not you have added a Thread device to it.

Home Assistant gives the clearest view. Go to Settings > Devices & services, add the Thread integration if it isn't there, then select Configure. The overview page lists every Thread network it can see, grouped by border router. Border routers advertise themselves over mDNS, so it will show an Apple or a Google network even though it holds no credentials for that network and cannot join it.

Apple Home and Google Home don't expose an equivalent list, so there the check is blunter: work backwards from the hardware you own. The table above is the list.

Several border routers is normal, and better

Thread is unusual here. Most mesh protocols run one coordinator, and that coordinator is a single point of failure. Thread expects several on the same network. Each one adds another way into the mesh and another patch of radio coverage, and if one drops off the others carry on.

So a HomePod mini in the bedroom and an Apple TV in the lounge room is two border routers on one network, working as intended. There is nothing to configure and nothing to turn off.

Two ecosystems usually means two Thread networks

This is the part that catches people out. Each vendor forms its own Thread network when you start using their gear. Run an Apple TV and a Nest Hub in the same house and you have two Thread networks with different credentials, on the same radio band, unable to share anything. A sensor commissioned onto the Apple network cannot roam to the Google one.

The Thread Group's answer is credential sharing, added in Thread 1.4, which lets one border router hand its credentials to another so the two join a single mesh instead of forming two. The specification has been public since 2024. The firmware has not kept pace: rollout is partial and vendor by vendor, so treat a unified network as something to verify on your own gear rather than count on.

Until it lands everywhere, pick one network and commission everything onto it. Home Assistant can import an existing Apple or Google network's credentials from the companion app and join that network rather than starting a third.

What breaks when the border router goes offline

The mesh itself survives. Thread devices keep talking to each other, and mains-powered Thread devices carry on routing for their neighbours. What you lose is the way in. Your phone, your controller and everything else on Wi-Fi can no longer reach the mesh, so devices show as unavailable in the app and any automation that runs through a controller stops.

That is the argument for a second border router. If your only one is the Apple TV in the lounge room and someone unplugs it to charge a phone, every Thread lock, sensor and blind in the house goes quiet at once. Two border routers on the same network and that stops being possible.

So do you actually need one?

Only if you are buying devices that run on Thread. That is the whole test. A Thread device with no border router in radio range is inert: it will not commission, and the app will say so.

None of this applies to Wi-Fi or Zigbee gear. For Thread gear, if you already own a HomePod mini, an Apple TV 4K, a Nest Hub or an Echo, you are done: a dedicated border router buys you nothing you need today. If you own none of those, one of them has to come first, so pick the one you would have found a use for anyway, a speaker or a streamer or a display, and take the border router as the part you were going to need.