Short answer
Wrong Thread network problems happen when Google Nest, Home Assistant OTBR, and the commissioning phone each know about different Thread credentials. The fix is to identify the active network owner before adding or resetting devices.
Next step
Symptoms this page covers
- Phone chooses wrong Thread network
- Nest network exists but Home Assistant cannot use it
- OTBR and Nest credentials differ
Likely causes
- Google Home created one Thread network and Home Assistant OTBR created another.
- The commissioning phone has credentials for one network but the target controller expects another.
- Home Assistant is running in a network mode that complicates OTBR or discovery.
- The user is trying to move Thread devices between networks without re-commissioning.
Fix checklist
- List which Thread networks are visible in Home Assistant.
- Identify whether Google Nest or Home Assistant OTBR should own the target Thread network.
- Use the same phone and ecosystem path consistently during commissioning.
- Avoid adding a second OTBR path until the first Thread network is understood.
- Document which devices are attached to each Thread network before resetting anything.
Avoid these mistakes
- Do not create another Thread network just to test pairing.
- Do not assume Google Nest Thread credentials are automatically available to Home Assistant.
- Do not reset the OTBR without understanding which devices depend on it.
FAQ
Should I factory reset Google Nest Hub first?
Usually no. First confirm the controller, hub, network, and integration path. Resetting too early can remove useful evidence about which ecosystem or Thread network currently owns the device.
Do I need a Thread Border Router?
You need a Thread Border Router when the device is Matter over Thread or otherwise uses Thread. A Matter Controller is not always a Thread Border Router, so verify the exact hub role before pairing.
What should I check before buying another hub?
Check whether you already have the required Matter Controller, Thread Border Router, vendor hub, Zigbee coordinator, and Home Assistant service. Use the linked calculator or diagnostic tool before purchasing extra hardware.
Can SmartHomeCompat guarantee this fix for Home Assistant?
No. These pages are based on official docs, product information, public compatibility data, and community issue patterns. They are designed to narrow the likely setup path and reveal missing pieces.
Feedback
Help improve this compatibility data
Smart home compatibility changes quickly. Send a report, request a missing device, or flag information that needs another review.
Save the setup path, missing hubs, limitations, and next steps for later.
Tell us which device, hub, or ecosystem should be added to the compatibility library.
Flag outdated, incomplete, or unclear setup guidance so it can be reviewed.
Get a practical checklist for hubs, Thread border routers, Matter pairing, and fallback paths.