Matter over Thread in Home Assistant: border router setup and first devices

Your first Thread device should do something useful: keep a lamp on while you sit still, report the chilly room, or put an ordinary lamp on a sunset schedule. Start with that job, then build the network around it.

For an Android-and-Google setup with no existing border router, choose Google TV Streamer (4K). Pair it with Aqara FP300 for presence sensing or W100 for room climate, and Eve Energy Matter for a Thread-controlled plug. Already have a supported Apple or Google border router? Use it. Your next purchase can be the device you actually want to automate.

This research-based guide uses Home Assistant and maker documentation for setup and specifications.

Quick picks: a border router, a sensor and a useful plug

• Best Google-first border router: Google TV Streamer (4K). A Thread border router, Google Home setup and gigabit Ethernet make it a practical starting point for an Android household that also wants a TV streamer. Google account onboarding is part of this route.
• Best first Thread sensor: Aqara FP300. Presence sensing is an immediately useful upgrade from motion-only lighting. Its Matter-over-Thread mode also supplies temperature, humidity and light readings.
• Best first Thread plug: Eve Energy Matter, US version. Start with a plug-in lamp. The plug also acts as a powered router node within the Thread mesh; the border router connects that mesh to your LAN.
• For a dedicated climate sensor: Aqara W100. Choose temperature and humidity sensing without making presence detection the project. Our room-temperature guide covers placement and useful readings.

Using an iPhone? Start with a supported Apple border router or the Home Assistant OpenThread route below. Home Assistant’s iPhone commissioning prerequisites specify those routes. Choose the phone-and-network combination before buying a Google box solely for Thread.

The parts lists offer a host-side route and device choices; you don’t need both sensors. You also need a running Home Assistant installation and the Companion app on your phone.

Matter is the language; Thread is the network

Three jobs fit together:

Piece	Its job	In this guide
Matter controller	Adds devices and sends their commands	Home Assistant’s Matter Server and integration
Thread border router	Connects the low-power Thread mesh to your local Wi-Fi/Ethernet network	Google TV Streamer, a supported Apple hub, or Home Assistant OTBR
Matter-over-Thread device	Does the sensing or switching	FP300, W100 or Eve Energy

The border router forwards traffic. Home Assistant controls the device. Home Assistant’s Matter documentation explains that communication between its controller and the device is encrypted, including when a third-party border router carries it. Local Matter commands don’t need an internet connection after setup; your local network and border router still need to be running.

Matter can also use Wi-Fi. The standard Nest Thermostat in our local-thermostat guide uses Matter over Wi-Fi, not Thread. Look for Thread or Wi-Fi in the product specifications.

Thread and Zigbee are separate networks, too. Keep your existing Zigbee kit working while you add Thread.

Your situation	Start here
You already have Zigbee sensors and a working coordinator	Keep that network; add Thread for a device you want
You want these Matter-over-Thread devices in Home Assistant and another ecosystem	Build Thread and use Matter’s device-sharing flow
You want extensive model-specific Zigbee settings	Check the exact ZHA/Zigbee2MQTT support before choosing the sensor’s mode
You have a Matter-over-Wi-Fi product	Add it through Matter; it doesn’t need a Thread border router

Our Zigbee/Thread coordinator guide helps you choose the radio. The two protocols are alternatives on FP300 and W100; pick the mode before pairing.

Pick your border-router route

Android and Google: TV Streamer

Google’s specifications list both Matter and a Thread border router, plus an Ethernet port. Use the Google Home app for onboarding and keep the Streamer powered and connected.

Google’s Thread setup guide explains enabling Thread during setup. On the Streamer, open All Settings → Network and Internet and turn Thread network on. That setting matters even if streaming video already works.

This gives Home Assistant a route into the Thread mesh; it doesn’t replace Home Assistant’s Matter Server. Set up both sides, then commission the sensor or plug from the Companion app.

Apple: reuse the hub you have

Home Assistant’s supported border-router list includes HomePod mini, HomePod second generation, Apple TV 4K second generation, and the third-generation Apple TV 4K Wi-Fi + Ethernet model. The third-generation Wi-Fi-only model isn’t the listed Thread route.

Set up the supported hub in Apple Home, then use your iPhone for the credential and commissioning steps. Reusing that radio is a sensible way to get your first Thread device working without adding another hub.

Home Assistant: dedicate a Connect radio to OTBR

Home Assistant OS can provide its own border router with Connect ZBT-2, Connect ZBT-1/SkyConnect, or another supported Thread radio. The OpenThread Border Router integration guide links the model-specific setup procedures. They install/configure the OTBR app and the radio’s Thread route; the integration is added automatically with the app.

One USB radio, one role. Nabu Casa recommends dedicating each Connect adapter to Zigbee or Thread. Leave your working Zigbee coordinator on Zigbee and use a separate adapter for Thread. These Connect radios start with Zigbee firmware, so follow the Thread setup rather than assuming that plugging one in creates a border router.

Google and Apple border routers supply that radio role themselves. You use the OTBR app when Home Assistant is providing its own border router.

Get the Thread credentials onto the right phone

This is the step that makes the rest feel easy. A discovered border router tells Home Assistant that a network exists; the credentials let the phone put a new device on it. If Thread is missing from Settings → Connectivity, add the Thread integration under Settings → Devices & services.

If you already use Google or Apple Thread: use an Android phone for the Google network or an iPhone for the Apple network. In the Companion app, open Settings → Connectivity → Thread, select Send credentials to Home Assistant, then refresh. If Make preferred network appears for that network, select it.

If Home Assistant OTBR created your first network: open Settings → Connectivity → Thread and check that the Home Assistant network is preferred. Then send its credentials to your phone:

• Android: Settings → Companion app → Troubleshooting → Sync Thread credentials.
• iPhone: Settings → Connectivity → Thread → Send credentials to phone in the preferred-network box.

Home Assistant’s preferred network and the phone’s commissioning network are distinct settings. The Thread guide explains that the phone uses its own preferred network when commissioning.

Adding an OTBR radio alongside an existing Google or Apple mesh? Import that network’s credentials before setting up the fresh Home Assistant border router, following the guide’s existing-network procedure. Selecting a preferred network doesn’t merge already-created meshes with different credentials.

Add the first device with the Companion app

Use the supported updated, 64-bit Home Assistant OS and official Matter Server app route for this walkthrough. Keep your phone, Home Assistant and border router on a straightforward local network while you get started.

1. Prepare Home Assistant. In Settings → Devices & services, add Matter. Accept the official Matter Server app installation when prompted.
2. Prepare your phone. Update the Companion app and enable Bluetooth. Android uses the full Play Store app with Google Play services and the commissioning permissions listed in the Matter prerequisites.
3. Put the device into pairing mode. For FP300 or W100, choose Thread/Matter mode rather than Zigbee. Use the device’s instructions and keep its Matter QR/setup code.
4. Open the Companion app: Settings → Connectivity → Matter → Add device → No. It’s new. Scan the Matter QR code and follow the commissioning screens. Name the device and give it an area when it finishes.
5. Try the result. Toggle Eve Energy from its device page, or watch the sensor’s readings update. Then build an automation.

Bluetooth gets the device onto the network during commissioning; Thread carries its normal traffic afterward. An ESPHome Bluetooth proxy serves a different job and doesn’t replace a Thread border router.

Already added the device to Apple Home or Google Home? Choose Yes. It’s already in use. in the Add device flow and follow that platform’s sharing instructions. Use the new sharing code the platform supplies. This adds another Matter controller; it’s separate from sharing the Thread network credentials.

Give each device a job

Product	Radio for this project	What you use in Home Assistant
Aqara FP300	Matter over Thread; Zigbee is an alternative mode	Occupancy, light, temperature and humidity
Aqara W100	Matter over Thread; Zigbee is an alternative mode	Temperature and humidity
Eve Energy Matter US	Matter over Thread	Plug switching; a powered routing node in the mesh

Aqara’s FP300 page separates its protocol-dependent features. Aqara’s W100 introduction, written by AqaraOfficial, confirms Matter-over-Thread and climate sensing. Eve’s product documentation explains its Thread router-node role. Start with these core functions; add extra device features as your chosen integration exposes them.

Three recipes worth building tonight

Open Settings → Automations & scenes → Create automation → Create new automation. Treat these as separate projects: give each lamp one lighting routine, or use different plugs.

1. A desk lamp that stays on while you’re there

Use FP300 + Eve Energy + a plug-in lamp.

For the on routine, add two triggers: State changed for FP300 occupancy becoming detected, and Sunset. Under And if, require FP300 occupancy to be detected and add Sun is set. The action turns on Eve Energy. The sunset trigger covers the evening when you’re already sitting there; the occupancy trigger covers arriving after dark.

Create a separate off routine: State changed, occupancy becoming clear, For at least: 5 minutes, then turn off Eve Energy. Five minutes is a starting setting you can adjust. Our presence guide helps with placement and background movement.

The current docs cover State changed and Sun is set.

2. A cold-room check that catches an already-cold room

Use W100 and your phone’s Companion notification action.

Add a Time trigger for a convenient daily check-in. Add a Numeric state condition on W100 temperature, with Below: 18°C, or 64.4°F if that’s the entity’s displayed unit. The action sends your phone a message to check the room or adjust your existing thermostat.

Those are example comfort settings, not measurements. This routine checks the reading at the chosen time, so it also catches a room that was cold before you saved it. Follow the current Time trigger, Numeric state condition and Companion notification instructions.

3. A sunset lamp with a definite bedtime

Use Eve Energy + a lamp. Make one automation with the Sunset trigger and a turn-on action. Make another with a Time trigger at your chosen off time and a turn-off action. Save both.

The current Sunset trigger follows the changing season automatically. For energy readings and more plug projects, continue to our local smart-plug guide.

Test it, then enjoy the useful bit

Use Run actions to check the lamp or notification delivery, then test the actual triggers: walk into and out of FP300’s view, or temporarily set the daily Time trigger a little ahead and save. Check the automation trace afterward. Pending For at least waits are discarded on restart or automation reload; another qualifying state change is needed to start that trigger again.

If commissioning stalls, check the phone’s Thread credentials and the device’s pairing mode first. Keep local IPv6 and multicast working between Home Assistant and the border router. Home Assistant’s Matter docs recommend Settings → System → Network → IPv6: Automatic when you’re unsure; an IPv6-enabled internet connection isn’t required.

Start with the border router that fits your phone, FP300 or W100 for sensing, and Eve Energy for switching. Get one device paired and one automation working. That’s a far better first evening than collecting hubs and hoping the logos sort themselves out.

Using Google TV Streamer as your border router? Our streaming-box comparison covers its separate Android TV Remote controls and a movie-night automation.