Thread border routers by platform

What a border router does

Phones, controllers and the internet live on Wi-Fi or Ethernet. Thread devices talk to each other over a low-power IPv6 mesh. A Thread border router connects the two and gives them two-way IP connectivity. The Thread Group says it makes Thread devices appear on the home network as IP devices, like Wi-Fi and Ethernet devices, with no separate hub or bridge. Home Assistant adds that it only routes packets between the local network and the Thread mesh and does not look at their content.[1][5–7]

This is the role a Matter over Thread device depends on. A Matter over Thread sensor, lock or bulb does nothing until something on the network can reach it, and the border router is that something. Philips Hue says so for its Matter-enabled bulbs: they need a Thread border router, and Hue names the HomePod mini and Google Nest Hub as examples.[8]

One border router is enough for a Thread network. Thread can use several border routers in a single network, which improves coverage and removes a single point of failure. The Thread Group notes the role can be built into smart speakers and smart TVs, so a typical home may have several. Google describes the same idea from the device side: Thread devices relay through mesh extenders, a home can have more than one, and the network keeps working when one goes offline.[3][5–7]

Devices that are Thread border routers

The table lists every device in the index that acts as a Thread border router, grouped by maker, with each device's Matter controller and Zigbee coordinator roles beside it. A cell reads unknown when the role is not stated either way. The note after a yes covers caveats, such as a radio that ships running Zigbee and needs Thread switched on.[1]

Platform requirements

• HomeKit: Thread accessories need a Thread-enabled home hub. Apple names the HomePod mini and the Apple TV 4K (3rd generation) Wi-Fi + Ethernet as examples, along with supported third-party border routers. A HomePod becomes a home hub automatically when it is set up. An Apple TV becomes one when an owner adds it to a room.[11]
• HomeKit without a hub: from iOS 18, Thread-enabled iPhones can pair and manage Thread accessories locally, and the iPhone 15 Pro and later can control them without a home hub. Apple still recommends a home hub, which is what provides remote control and automations.[9][11]
• Google Home: Google lists the Nest Hub (2nd gen), Nest Hub Max, Nest Wifi Pro (Wi-Fi 6E) and Google TV Streamer (4K) as having a built-in Thread border router. Its other speakers and displays, such as the Nest Audio and Nest Mini, handle Matter over Wi-Fi only.[3][74]
• Home Assistant: it can run its own border router through the OpenThread Border Router app on a supported radio. The Connect ZBT-2 adapter is dedicated to either Zigbee or Thread. It cannot do both at once, and it is not a standalone border router. Nabu Casa recommends a separate adapter per protocol.[5][33]
• Homey: Athom lists a Thread border router among the Homey Pro's radios, next to Matter, Zigbee 3.0, Z-Wave 700 series and Bluetooth Low Energy.[75]
• Aqara: the Hub M3 launched as a Matter controller and Thread border router. Later Aqara hubs in the table have the same role.[43]
• IKEA: the DIRIGERA hub gained its border router and Matter controller functions in a mid-2025 firmware update. Before that, its Thread radio was not used.[54]
• Amazon: Amazon names the Echo (4th Gen) as a Thread border router. Other Echo models list Thread without a stated border router role, so the role is unknown for those models.[4]

Mixing border routers from different brands

The Thread Group states that border routers sharing Thread credentials put all their devices on one mesh, with mains-powered devices extending range and a second router as backup. Border routers that do not share credentials each form their own mesh. Home Assistant describes the same result: each vendor forms its own Thread network when a household starts using its products, and these are separate networks with different credentials.[5][6]

Devices on separate Thread networks can still reach each other. The Thread Group says that because Thread is IPv6, a device on one network can see devices on another, and on Wi-Fi and Ethernet. It also says Thread is independent of any Matter fabric and that it is working with members toward a single mesh across ecosystems.[6]

Credential sharing is uneven across platforms. Home Assistant's Android app sends the phone's preferred Thread network to Home Assistant. Its iOS app sends the iPhone's preferred network plus any other Thread networks the app can access. A network can only be set as preferred once its credentials are known. Google stores the Thread credentials its border routers create in the Google Account, and a Google TV Streamer can create a new Thread network or join an existing one.[3][5]

Hubs that are not border routers

Many hubs are Zigbee hubs and do not route Thread. Some devices, like Google's Nest Learning Thermostat (4th gen), list Wi-Fi only in the maker's specification. 44 devices in the index are stated not to be border routers, against 46 that are. None of the no entries satisfies the Thread requirement of a Matter over Thread device.[1][76]

Notes on border router setups

• A HomePod mini, an Apple TV 4K (3rd generation) Wi-Fi + Ethernet, a Nest Hub (2nd gen), a Nest Hub Max, a Nest Wifi Pro or a Google TV Streamer (4K) already routes Thread for its platform.[3][11]
• Two or more border routers reduce the risk of a single point of failure, which matters for locks and other devices that must keep working.[5]
• Home Assistant needs a dedicated Thread radio rather than one adapter shared with Zigbee, because the ZBT-2 cannot run both protocols at the same time.[33]
• An unknown in the table means the maker does not state the role. It is not a yes.[1]