Thread and the OpenThread border router in Home Assistant

What Home Assistant's Thread integration and OpenThread Border Router app do, how separate Thread networks arise, and what to know before you set it up.

By Jonas Ferris · · 5 min read · Comments

Thread is the low-power network many Matter sensors and switches use, and a Thread network needs a border router to reach the rest of your home. Home Assistant can use border routers from other companies and can also be one. This guide explains the pieces and the traps, drawing on Home Assistant's Thread documentation, read on 13 November 2026. The project's pages are the authority, and its Thread support is described there as still in progress.

Two integrations, one job each

Thread. Home Assistant's page says this integration keeps track of the Thread networks at home and holds their credentials, which it likens to a Wi-Fi password. You do not install it: it shows up once Home Assistant spots a border router.

OpenThread Border Router. This integration calls a border router's REST interface. It is installed alongside the app called OpenThread Border Router. A border router of your own can be added by hand, using the router's address on port 8081 over plain HTTP.

What OpenThread is and why it matters here

The Thread page describes OpenThread as Google's open-source implementation of Thread and says nearly every commercial border router builds on it. Setting a border router up lies outside the Thread standard, so Apple and Google configure theirs through their own platforms. Any border router will work as a connection, but Home Assistant can only configure OpenThread ones that expose the REST interface, and its own app is made from that code with the interface enabled.

Using a border router you already own

The page lists the border routers it knows are compatible: displays, a Wi-Fi router and a TV streamer from Google, HomePod and Apple TV models from Apple, plus devices from other companies such as Nanoleaf and Amazon. That list is a snapshot, and some of the devices may need a phone for setup. Check the prerequisites on the Matter page before buying one.

Making Home Assistant a border router

If you own the Yellow, the Connect ZBT-1 or the Connect ZBT-2, its Thread radio is available to you. The page says these run Zigbee out of the box, that enabling Thread takes manual steps, and that tying its own border router in with Matter is unfinished. It then splits the job into two cases:

  • A first Thread network. Home Assistant creates it.
  • An existing network. A border router from Home Assistant can join a network that another vendor created, so you do not end up with two.

Our Matter piece Matter in Home Assistant shows where this fits when you add a Thread device.

Why you may see several Thread networks

The Thread page says each vendor forms its own network when you start using its products, so Home Assistant may list an Apple network, a Google network and its own, with different credentials and no roaming between them. Home Assistant discovers every border router on the network because they announce themselves, but those announcements do not carry the credentials, so it can list a network without being able to use it.

To use someone else's network, import its credentials through the Companion app. On the phone, the Thread settings page has a button to send credentials to Home Assistant. The Android app sends the phone's preferred network and the iOS app sends that and any others it can reach. You can then make that network the preferred one in Home Assistant, though the page says the preferred network feature is not fully implemented, and that for Matter devices added from the Companion apps, it is the phone's preferred network that gets used.

The page explains that joining several networks into one should give better coverage and faster, more reliable links, and points to the steps for it.

Thread is not Matter

A Thread logo does not tell you the device speaks Matter. Home Assistant's Matter page says some Thread devices use Apple HomeKit or a maker's own protocol, and a few need a beta firmware update first. The Thread page makes the same split: a Matter logo means follow the Matter steps, and a HomeKit logo means follow the HomeKit ones. Look for the Matter logo as well as the Thread one.

When it goes wrong

The Thread page has sections for the common faults: IPv6 not working on the network, changing the Thread channel and pairing failures, and the Matter page has an entry for the error that a device requires a border router. Start there.

What to check before you start

  1. Whether a border router at home is already Home Assistant compatible, using the page's current list.
  2. Whether your Home Assistant hardware has a Thread-capable radio, and whether you are willing to follow the manual steps.
  3. How many Thread networks you already have, and whether you want one.
  4. That the devices you plan to buy carry the Matter logo.

This guide summarises documentation and is not based on testing. For any procedure, follow the project's own pages.

J
Jonas Ferris

Staff writer, Home Assistant

How we work
Latest news