Fix a Matter device that will not finish Google Home setup
Verify the Matter mark, hub, Thread border router when required, IPv6, phone permissions, pairing window, and primary-platform state before resetting the accessory.
Direct answer
The shortest reliable path.
Confirm the accessory is Matter-certified and in its active pairing window, the phone has Bluetooth and local-network access, Google Home has a compatible Matter hub, and IPv6 is enabled on the home network. Thread accessories also need a Thread border router. Restart the accessory and phone, reopen Google Home, and rescan the code; factory-reset only after preserving the original platform and sharing state.
System view
Check the whole path.
- 01Matter-certified device
- 02Phone permissions
- 03Matter hub
- 04IPv6 / Wi-Fi or Thread
- 05Google Home fabric
Scope before steps.
Third-party Matter accessories being added directly to Google Home or shared from a manufacturer or another Matter-certified platform.
Works with Google Home cloud integrations, non-Matter Nest products, router-specific IPv6 menus, electrical installation, or a universal reset sequence.
Procedure
Do this in order.
- 01
Confirm this is the Matter path
Check the packaging, manual, or manufacturer page for Matter certification and the exact commissioning procedure.
- 02
Prove the required infrastructure
Confirm a compatible Google Home Matter hub is online, IPv6 is enabled, and a Thread border router is present when the accessory uses Thread.
- 03
Prepare the phone and pairing window
Update Google Home, enable Bluetooth and local-network permission, connect the phone to home Wi-Fi, wake the accessory, and place it in pairing mode.
- 04
Restart without erasing ownership
Restart the accessory, close Google Home, restart the phone, reopen the app, and scan the original code again.
- 05
Choose add-new versus share-existing
If the device already works in a manufacturer or Matter app, generate a new temporary sharing code there instead of reusing the original onboarding code.
Diagnostic matrix
Read the result, not the guess.
| What you see | Check next | What it means |
|---|---|---|
| Device is not found at all | Check pairing mode, Bluetooth, local-network permission, distance, and phone Wi-Fi. | Discovery is failing before the Matter network join. |
| Setup begins then fails | Verify hub, IPv6, Wi-Fi or Thread path, and restart both phone and accessory. | Discovery succeeded; commissioning or operational-network attachment failed. |
| Works in manufacturer app only | Use that app’s Share or Link Matter apps flow and a fresh temporary code. | The device already belongs to a Matter fabric and should be shared, not added as new. |
| Thread device pairs but later goes offline | Confirm an active border router and IPv6 remain available. | Commissioning completed but the operational Thread path is not stable. |
Stop conditions
Know when not to keep changing things.
- Do not discard the original Matter code or factory-reset a working primary-platform setup before recording it.
- Do not disable network security broadly to force pairing.
- Contact the accessory maker when current firmware and required Google infrastructure are present but its documented commissioning still fails.