Thread border router: what it does, which devices have one, and whether you need one

A Thread border router is a device with a foot in two networks: a Thread radio that joins the low-power mesh used by battery sensors, locks and blinds, and a Wi-Fi or Ethernet connection to the rest of your home network. It passes IP packets between the two, so a phone, a smart home controller or a cloud service can reach a device on the mesh. Without one, Thread devices can still talk to each other, but nothing outside the mesh can talk to them. This article explains what a border router does, the other roles in a Thread network, which common devices include one, what happens when you own several from different brands, and how Thread compares with Zigbee, which uses the same radio.

What Thread is

Thread is a low-power wireless mesh protocol maintained by the Thread Group. It uses the IEEE 802.15.4 radio in the 2.4 GHz band, the same radio as Zigbee, with a raw data rate of 250 kbit/s. What sets it apart is that it carries IPv6. Every Thread device has an IPv6 address, and packets are squeezed into the small 802.15.4 frames by 6LoWPAN, an IETF adaptation layer that compresses IPv6 headers.

Thread defines the network: how devices join, how packets are routed across the mesh, and how the mesh repairs itself when a device disappears. It does not define what a light or a lock is. That job belongs to an application layer running on top, and in homes that layer is increasingly Matter, which the Matter article covers in detail.

Because Thread is IP, a sensor on the mesh and a phone on Wi-Fi are both ordinary IPv6 hosts. The only thing between them is a router, and that router is the border router.

What a Thread border router does

The job has three parts.

The first is routing. The border router forwards IPv6 packets between its Thread interface and its Wi-Fi or Ethernet interface. It announces a route to the Thread network on the home network, so other devices know where to send packets for the mesh, and it gives Thread devices a route out. It routes packets without rewriting them: a Matter command from a controller arrives at a lock as the same IP packet the controller sent, with only the radio framing changed. That is the practical difference from a Zigbee hub, which has to end Zigbee’s own protocol at the hub and represent each device again in some other form.

The second is service discovery. Home apps find devices on the local network with multicast DNS. Flooding multicast traffic across a low-power mesh would waste battery and airtime, so Thread devices register their services with the border router using the Service Registration Protocol, and the border router advertises them on the Wi-Fi side on their behalf. That is how a controller on Wi-Fi discovers a Matter device that lives on Thread.

The third is reaching the internet. Many home internet connections still run IPv4, and Thread devices speak only IPv6. Newer border routers can provide NAT64 translation so a Thread device can reach an IPv4 service. Plenty of Thread devices never talk to the internet at all, which suits a local-only smart home, so this part matters less than the first two.

A border router is a network device, and it does not have to be a controller. It holds no automations and does not need to know what the devices on the mesh are. In practice the same box often does both jobs, a speaker or hub that is also a Matter controller, which is why the two terms get mixed up.

The roles in a Thread network

Every Thread device takes on one or more roles, and the network assigns most of them automatically.

Routers relay packets for other devices and keep the mesh connected. They keep their radios on all the time, so they are mains-powered devices such as plugs, bulbs, wall switches and hubs. A Thread network caps the number of active routers at 32; mains-powered devices beyond that wait as router-eligible end devices and are promoted if a router drops out or the mesh needs more coverage.

End devices talk only to one parent router and do not relay traffic for anyone else. A mains-powered end device keeps its radio on; a sleepy end device switches its radio off most of the time to save battery. Its parent router holds messages for it until it wakes and asks for them, which is why a command to a battery blind or lock can take a moment to arrive. Door sensors, temperature sensors and remote buttons are typically sleepy end devices.

The leader is one of the routers, chosen automatically. It hands out router identities and keeps the shared network data, such as the prefixes and the list of border routers. If the leader disappears, another router takes over the role without anyone doing anything.

The border router is the role this article is about: any device that connects the mesh to another IP network. A network can have several, and devices will use whichever one is reachable. That redundancy is one of the design differences from Zigbee, where a single coordinator owns the network.

Which devices act as a Thread border router

Most of the big smart home ecosystems build a border router into some of their speakers, streaming boxes, displays and Wi-Fi routers. The table lists the models each company names in its own support pages. Not every model in a product line has a Thread radio, older generations often lack it, and the lists grow with new releases, so check the current page before buying for this reason.

Two details catch people out. The Wi-Fi-only Apple TV 4K (3rd generation) has no Thread radio; only the Wi-Fi + Ethernet model does. And a Thread-enabled iPhone (iPhone 15 Pro or later, on iOS 18 or later) can pair a Thread accessory directly, but it is not a border router: automations and remote control still need a Thread-enabled home hub.

Is a Google Home a Thread border router?

The original Google Home speaker, the Nest Mini and the Nest Audio are not. They can still control Matter devices that use Wi-Fi, but they have no Thread radio. In Google’s lineup the border routers are the Nest Hub (2nd gen), the Nest Hub Max, the Nest Wifi Pro, the Google TV Streamer and the Google Home Speaker released in 2026.

Other border routers

Some lighting, heating and smart home brands build border routers into their own hubs and products, among them Nanoleaf light panels, Aqara hubs and tado bridges, and some recent smart TVs and soundbars include one. These work with Thread devices, but not all of them act as a Matter controller, and how well they share one Thread network with an Apple, Google or Amazon border router varies. The open-source OpenThread Border Router also runs on a small single-board computer with an 802.15.4 radio attached, which suits people who already run their own home automation server.

One border router is enough for a working network. Adding a second, especially from the same ecosystem, gives the mesh a fallback if the first is unplugged or restarting. Place border routers on mains power, somewhere central, and let mains-powered Thread devices fill in the mesh around them.

Do you need a Thread border router for Matter?

For Matter over Thread, yes. When you add a Thread device, the phone app usually reaches it over Bluetooth LE, checks its certificate and hands it the credentials for your Thread network. The device then joins the mesh, and from then on the controller talks to it over IP, through the border router. Without a border router there is no Thread network on the controller’s side for the device to be handed into.

Matter over Wi-Fi and Matter over Ethernet devices join your normal home network directly and need no border router. The product box or listing should say which transport a Matter device uses.

Several border routers from different ecosystems

A Thread network is defined by its credentials, known as the operational dataset. It includes the network name, the PAN ID and extended PAN ID, the radio channel, the network key and the mesh-local prefix. Any border router configured with the same dataset joins the same network, and a Thread device belongs to one network at a time.

Border routers from one ecosystem share the dataset with each other automatically. Across ecosystems that has been less reliable. In many homes the first Apple, Google or Amazon border router each formed its own Thread network, so the house ended up with two or three separate meshes, possibly on different channels. Each one is smaller than a combined mesh would be, with fewer routers to relay traffic, and a device on one mesh cannot use the routers of another.

Control usually still works across the split. Matter lets several controllers manage the same device, and because every border router sits on the same home IP network, a controller from one ecosystem can reach a device on another ecosystem’s Thread network through that ecosystem’s border router. The cost is a weaker mesh and a dependency on that one brand’s border router staying online.

The fix is credential sharing. Apple and Google both give apps a way to read and share a home’s preferred Thread credentials, and version 1.4 of the Thread specification requires certified border routers to support joining an existing network. In practice, set up one ecosystem’s border router first, and when you add a border router from another brand, look for an option in its app to join the existing Thread network. Some apps show which Thread network each border router belongs to, which makes a split easy to spot.

Thread vs Zigbee

Thread and Zigbee share the physical radio. Both use IEEE 802.15.4 in the 2.4 GHz band, on the same channels, at the same 250 kbit/s, with similar range and similar power use. Many current 802.15.4 chips, such as the ESP32-C6, can run either protocol, and some hubs run both at once. The differences are all above the radio.

Zigbee defines the whole stack. Its network layer has its own addressing and routing, and its application layer, the Zigbee Cluster Library, describes what devices are and what they can do. A Zigbee network is formed and secured by one coordinator, usually inside a hub. Anything on the IP side reaches a Zigbee device only through that hub, which translates between Zigbee messages and whatever the hub exposes to apps.

Thread stops at the network. It carries IPv6 over the mesh and leaves the application to a separate standard, which is why Matter could adopt it without changing it. There is no single coordinator to fail, and several border routers can serve one mesh.

For a buyer, the table reduces to a few points. A Zigbee device needs a Zigbee hub or coordinator; a Thread device needs a Thread border router. The two cannot join each other’s networks even though the radios are the same, because the firmware speaks a different protocol. Both share the 2.4 GHz band with Wi-Fi, so channel choice matters for both. And a Thread device that supports Matter will work with any Matter controller, while a Zigbee device works with hubs that support its device type. The Zigbee, Z-Wave and Wi-Fi comparison covers how Zigbee fits alongside the other home radios, and the same placement advice for hubs and routers applies to Thread.