Matter Device Paired but Not Showing Up? How to Fix It
If your Matter device finished commissioning — you scanned the code, saw a success message, maybe even heard a chime — but it never appeared in your app's device list, the pairing almost always did work. What usually breaks is the step after the secure handshake: the device joins your fabric but fails to reach the controller (your hub or phone) over the network, so the app has nothing to display. The good news is that the fix is rarely a re-pair from scratch. Most of the time it's a network, cache, or multi-admin issue you can clear in a few minutes.
First, confirm what "commissioned" actually means
Commissioning is the Matter term for the secure onboarding process: your controller verifies the device's certificate, hands it Wi-Fi or Thread credentials, and adds it to a fabric (the trusted group of devices managed by one platform). If you got a success screen, that part is done — the device now holds valid credentials for your account. The reason it isn't visible is that the app populates its list from live network discovery (using mDNS/DNS-SD on Wi-Fi, or the Thread mesh), and something is blocking that discovery. Understanding this saves you from needlessly wiping a device that's actually paired correctly.
The quick fixes that resolve most cases
Work through these in order. Each one targets a common, documented cause, from least to most disruptive.
- 1Force-quit and reopen the app, then pull-to-refresh the device list
- 2Reboot your controller/hub (Echo, Nest, HomePod, or SmartThings Station) and wait 1–2 minutes for it to re-scan
- 3Confirm the phone, hub, and device are all on the same Wi-Fi network and subnet
- 4For Thread devices, verify a border router is online and healthy
- 5Only if all else fails, factory-reset the device and re-commission
- Restart the app and refresh. Controllers cache the device list, and the app sometimes doesn't redraw a device that arrived seconds after the screen loaded. Fully close the app (not just background it), reopen it, and use the pull-to-refresh gesture on the device list.
- Reboot the hub. Your Matter controller — an Echo, Nest Hub, HomePod, Apple TV, or SmartThings hub — maintains the fabric and does the discovery. A reboot forces a fresh network scan and clears a stalled mDNS responder. Give it a full minute or two afterward.
- Check the network path. For Matter-over-Wi-Fi, the device and the controller must sit on the same subnet. A guest network, a separate IoT SSID, or a mesh system that isolates bands can silently break discovery even though the device is "online." See Matter over Thread vs Matter over Wi-Fi for why the transport changes what you troubleshoot.
- For Thread, check the border router. A Matter-over-Thread device is only reachable if a Thread border router is online and the mesh is healthy. If your border router recently rebooted or lost internet, the device can be commissioned yet unreachable. Our guides on checking Thread network health and border routers you may already own walk through this.
- Factory reset as a last resort. If nothing surfaces the device, wipe it and start clean. Follow how to factory reset and re-pair a Matter device so the old fabric credentials are fully cleared first — re-pairing over stale credentials is a common repeat failure.
Common causes by symptom
| What you're seeing | Likely cause | First thing to try |
|---|---|---|
| Success screen, then nothing in the list | App cached an old list; discovery finished late | Force-quit and refresh the app |
| Device shows "offline" or "unreachable" | Wrong subnet, IoT/guest SSID, or Thread border router down | Put phone, hub, device on one network; check border router |
| "Already commissioned" error on retry | Device is on another fabric or was partially added | Factory reset, then re-commission cleanly |
| Appears in one app but not another | Multi-admin sharing not completed | Generate a new sharing code from the first app |
When it's a multi-admin (sharing) problem
If the device shows up fine in the app you originally paired it with but is missing from a second one, this isn't a failed commissioning at all — it's incomplete sharing. Matter lets one device belong to several platforms at once, but each platform must be added deliberately through a fresh pairing code generated by the first controller. If you tried to scan the original code again in the second app, it won't work, because that code is single-use. Our guides on Matter multi-admin and sharing a Matter device across Alexa, Google & Apple Home explain how to produce that second code from within the app that already controls the device.
Frequently asked questions
Does "commissioned" mean the device is fully set up?
It means the secure pairing and credential exchange succeeded and the device joined your fabric. It does not guarantee the app can currently reach it over the network. That last-mile discovery step is where a commissioned-but-missing device gets stuck.
How long should I wait before assuming it failed?
Give it one to two minutes after the success screen, and refresh the app once. Thread devices and busy meshes can take a little longer to propagate. If it's still absent after a hub reboot and a refresh, then move on to the network and reset steps.
Why does it show up in Alexa but not Google Home (or vice versa)?
That's a multi-admin sharing gap, not a pairing failure. Each platform needs its own pairing code generated from the controller that already has the device. Re-scanning the original box code won't add it to a second app.
Could my Wi-Fi setup be the problem even though the device is "online"?
Yes. A device can be online on your network yet undiscoverable if it's on a different subnet, a guest or IoT SSID, or a network with IPv6 or multicast disabled. Consolidating everything onto one network is the most reliable fix. Matter also needs local connectivity to function — see do Matter devices need the internet to work.