Your home already has a border router, yet the app stops you with “Thread Border Router Required” because your phone does not hold the Thread network credentials that router created. The block is about a missing key on the commissioning phone, not missing hardware in the house.
That key is called the Active Dataset, and each ecosystem stores it in a different place — Apple in iCloud Keychain, Google in your Google Account, Home Assistant in its Thread integration and then pushed via the Companion app. If the phone’s credential store does not match the active Thread network, Matter over Thread cannot finish joining, even though a Thread border router is online and bridging Thread to Wi-Fi. Which credential path to check first depends on which device created your network, and the fix looks different for Home Assistant plus iPhone versus Android plus Google Home.
Why the alert fires even though you already own a border router
Thread does not use your Wi-Fi password. Every Thread mesh has its own Active Operational Dataset — network name, channel, network key, and border router credentials packed as a TLV. Your phone must already hold that dataset before it tries to commission a new device over Bluetooth LE.
When you tap Add in Apple Home, Google Home, or Home Assistant, the app asks the phone’s Thread credential store for a matching dataset. If the store is empty or holds a different network, the app shows “Thread Border Router Required” immediately and never talks to the border router at all. That is why Google Thread credentials sync notes a border router is required to set up a Thread device and credentials are generated and shared automatically to the phone and your Google Account or iCloud.
Genuine missing hardware looks the same on the surface but fails later. If no border router exists, the Thread integration would show no border routers discovered. If a border router exists but the phone lacks its dataset, the border router appears as present in your ecosystem yet commissioning still fails with the same alert.
A Matter controller role alone does not clear this check. A controller manages the Matter fabric, subscriptions, and automations, but only the border router role provides the Thread dataset and IPv6 routing. You can have a controller online and still get the error because the Thread part is missing on the phone.
Stage boxes showing border router holding dataset, phone credential check, and commissioning block when credentials do not match
Thread border router vs matter controller — why your app confuses them
The alert is about credentials, not just hardware presence, which is why the distinction between a Matter controller and a Thread border router matters so much here.
A Matter controller keeps the Matter fabric alive, holds subscriptions, and runs automations. A Thread border router does two different jobs: it bridges 802.15.4 Thread frames to your Wi-Fi or Ethernet as IPv6, and it holds the Thread Active Dataset that allows new devices to join. The Thread border router functions page describes this as providing IP routing and secure commissioning.
Some boxes do both. Others do not. Google’s own listing shows Google Thread border router device list includes Nest Hub 2nd gen, Nest Hub Max, and Nest Wifi Pro as border routers, while original Nest Hub and Nest Mini are Matter controllers only. If you try to add a Matter-over-Thread sensor to a controller-only hub, you will still see the required error because the Thread bridge and credentials are absent.
For Matter-over-Wi-Fi devices, the app never checks for a border router at all, because those devices already speak IP over Wi-Fi. For Matter-over-Thread devices, the app checks for a border router first, because without that bridge the phone cannot hand the Thread join payload to the new device.
Table comparing common hubs on Matter controller role and Thread border router role showing controller-only models that still trigger error
At the device area, look for: open your hub’s official spec page and confirm it lists both Matter controller and Thread border router on separate lines — controller alone will not clear a Thread device error. That quick check is covered in more detail in our sibling explainer on Matter hub vs border router explained, which lays out the role split this error builds on.
Does your current hub actually provide a thread border router
A controller-only hub is not enough for Thread, which is why listing what you actually own matters before you buy anything new.
Verified border routers as of this guide: Apple HomePod mini, HomePod 2nd gen, Apple TV 4K 2nd gen and 3rd gen Wi-Fi plus Ethernet; Google Nest Hub 2nd gen, Nest Hub Max, Nest Wifi Pro, Google TV Streamer 4K per Google’s own Nest Thread border router documentation (see the device list linked above); Amazon Echo 4th Gen and Echo Show 8 3rd gen; Home Assistant Connect ZBT-1 or SkyConnect running the OpenThread Border Router add-on which the Home Assistant Thread integration then shows as a discoverable border router with a preferred network selector.
First-gen Nest Hub and Nest Mini are frequently the culprit when people say why does it say thread border router required after buying a Thread sensor. They can be a Matter controller for Wi-Fi devices, but they cannot store or share a Thread dataset, so any Thread commissioning fails at the credential check.
On the Home Assistant side, a common report illustrates the credential gap. In the Home Assistant Community, an Eve Energy plug fails instantly with “You need a thread border router to use this device” despite SkyConnect paired as OTBR. As one poster described it, “You need a thread border router to use this device”. The fix that came up repeatedly was not adding hardware, but checking the Thread integration preferred network and using Companion app Sync Thread credentials to push the Active Dataset TLV to the phone, which works because the mechanism source for credentials — per Google’s own Nest Thread support documentation, cited above — requires the phone to hold the border router’s dataset before commissioning.
How many thread border routers do you need and why you might have two networks
Knowing which hubs provide a border router determines how many Thread networks you end up with, not just how many boxes you have.
Technically one border router is enough for connectivity. The how many border routers needed note says only one is technically needed but multiple add redundancy if they share the same network. Redundancy only works if they share the same Active Dataset. If they do not, devices on different datasets cannot mesh, even if they are in the same house.
Each ecosystem tends to create its own network if you never join them. A Google Home structure creates one dataset stored in your Google Account, Apple Home creates another stored in iCloud Keychain, and Home Assistant’s OpenThread Border Router add-on creates ha-thread with credentials stored locally until you explicitly sync. The multi-network credential sync behavior Google documents notes credentials sync automatically only within the same structure, so a Google-created network is invisible to an iPhone commissioning via Apple Home unless you merge them.
Amazon keeps its Thread credentials private to its own fabric and does not expose them for cross-ecosystem import, which is why adding an Echo to an Apple Home setup still leaves two separate Thread meshes. The Home Assistant OTBR preferred network documentation shows how Home Assistant lets you inspect and choose which network configuration becomes the preferred one, which is the merge point you control.
Interactive states showing single vs split Apple vs Google vs Home Assistant Thread networks and merge path when credentials are synced
Your device requires a thread border router — fix for Home Assistant + iPhone
Multiple networks explain why the credential is missing on this phone, which is where the Home Assistant plus iPhone case hits most users.
If you use Home Assistant with a SkyConnect or ZBT-1, the error almost always means the phone never received the preferred network dataset. The flow that resolves it in the community is consistent.
- In Home Assistant go to Settings, Devices and Services, Thread integration. Check that your border router appears under Thread border routers and that one network is marked Preferred Network. If none is preferred, no phone will have the correct dataset.
- Click the three dots on that preferred network and choose Use for Android and iOS credentials. This tells the Home Assistant Thread integration to make that dataset available for companion sync.
- On iPhone open Home Assistant Companion app, Settings, Companion App, Troubleshooting, Sync Thread Credentials. Wait for the confirmation that credentials were added to iOS Keychain. This step is the Home Assistant iOS credential sync fix that users report as the missing piece after setting preferred network.
- Now retry adding the device in Apple Home with the QR code. Commissioning should reach “Connecting” and then “Adding to network” instead of instantly failing.
Try this before you buy: in Home Assistant go Settings, Devices and Services, Thread and confirm your border router appears under Preferred Network — if not, no phone will have correct dataset and buying another border router will just create another isolated network.
Apple’s own documentation for Thread accessories notes the home hub must be set up as Apple Thread border router setup for Thread-enabled Matter accessories. iPhone 15 Pro and later have a Thread radio for direct control without a border router nearby, but that radio is not required for commissioning through a border router, so lack of Thread radio on the phone is not the cause of this error.
Your device requires a thread border router — fix for Android and Google Home
The iOS fix uses the iCloud Keychain path, while Android uses the Google Account path, which changes where you look.
On Android, Google’s Thread Border Router sync works automatically when your phone and border router are in the same Home structure and signed into the same Google Account — Android devices sync with Google border routers automatically and credentials become Preferred, per the same Nest Thread support documentation cited above.
If you opted out of cloud sync, Google’s Android Thread credential storage guidance notes credentials stay local on one phone and other phones in the house will not see the network. The fix is to enable cloud save: in Google Home app go to Settings, Google services, Thread networks, Network preferences, Save credentials to Google Account. If credentials were stored locally and the phone was reset, that dataset is lost and Thread devices already on that network may need re-commissioning, which is why a factory reset warning appears in Google’s help.
For Home Assistant plus Android, the same Companion app path applies: Thread integration set as preferred, then Companion app, Settings, Troubleshooting, Sync Thread Credentials to push the Active Dataset to Android’s Thread store.
Matter thread device won’t pair even after sync — what to check next
Credential sync resolves most cases, but not all pairing blocks come from credentials alone.
After sync, commissioning can still fail for network reasons. Matter over Thread devices stay in BLE pairing mode for approximately 15 minutes after power-up. Your phone, border router, and new device must be on the same primary Wi-Fi SSID and same VLAN, with IPv6 enabled on the router because Thread needs an IPv6 route to hand off. The device must not already be commissioned to another Matter fabric — if it is, remove it from the old app first or factory reset the accessory, not the border router.
A useful signal is the Matter Server log in Home Assistant. If the log shows no OpenThread Border Router activity after QR scan, the phone never handed the join payload to the border router, which points back to missing dataset on the phone rather than a radio issue. This pattern appears in reports where IKEA Bilresa fails after QR scan with Connecting then “Thread Border Router Required” and OTBR logs show no activity. As one poster described it, “Thread Border Router Required” after scanning QR code. The community fix that works is verifying phone, border router, and device are on same IP network and IPv6 enabled, then re-syncing preferred network credentials per the Home Assistant Thread integration docs.
Why you should not factory reset everything yet
Resetting the border router creates a brand new Active Dataset and invalidates every Thread device already on the old network, because the network key changes. That forces you to re-add all existing Thread sensors. It is less disruptive to add the existing border router’s network to the preferred set and sync that dataset to the phone, rather than wiping and starting over. Keep factory reset as a last step only if the Thread integration shows no border routers at all.
Making It Work
Set your intended Thread network as Preferred in its own ecosystem and then run Sync Thread Credentials on the phone you use to commission, because the error means the phone lacks the Active Dataset, not that you lack a border router. In Home Assistant that means Thread integration plus Companion app sync; in Google Home that means checking Save credentials to Google Account. Once the phone holds the matching dataset, the same sensor pairs without buying another border router and you avoid creating a second isolated Thread network that fragments your mesh.
Frequently Asked Questions
Does nest hub have a thread border router or do i need another hub?
Nest Hub 2nd gen, Nest Hub Max, Nest Wifi Pro, and Google TV Streamer 4K have a Thread border router and are also Matter controllers. Original Nest Hub and Nest Mini are controller only, so Thread devices still show the required error. Check the Nest Hub Thread border router list for your exact model.
What is the difference between thread border router vs matter controller?
A Matter controller manages the Matter fabric and automations, while a Thread border router bridges Thread 802.15.4 to Wi-Fi and holds the Active Dataset. One box like HomePod mini can do both, but the roles are distinct — apps check for border router only for Matter-over-Thread. See border router vs router distinction for role details.
How do i sync thread credentials to my iPhone or Android phone?
For Home Assistant set preferred network, then Companion app > Troubleshooting > Sync Thread Credentials. For Android Google Home enable Save credentials to Google Account in Thread networks settings. For Apple, credentials sync via iCloud Keychain automatically when using Apple border router. See sync Thread credentials steps.
How many thread border routers do i need in one house?
One is technically enough for Thread connectivity. Two or more adds redundancy and coverage if they share the same Thread credentials. If they create separate networks like Apple vs Google vs Home Assistant, adding more does not help — merge via preferred network instead. Multiple routers only help when using the same dataset.
