Matter device not discovered: check the documented prerequisites in order, then retry only the affected path.
Start with these checks
A discovery failure can happen before any compatibility verdict is possible. Check whether the device is in its active commissioning window and whether the phone, controller and accessory can reach each other locally. If it was paired elsewhere, use the current administrator’s sharing flow instead of reusing an old box code.
- Correct model/protocol?
- Current pairing or sharing window?
- Phone permissions and local reachability?
- Controller and required TBR online?
Stop when you find the first unmet requirement. Fix it and try pairing again before changing the next variable.
How to interpret the outcome
Missing evidence stays UNKNOWN; missing required role becomes REQUIRES_HARDWARE.
A failed path does not prove every alternative path is unsupported. For example, a missing direct radio may still leave a separately documented bridge or cloud route.
Avoid these risky shortcuts
- Factory reset as first step
- Publicly upload QR code
Official references
- Home Assistant — Matter integration, network and controller requirements Reviewed 2026-10-30
- Apple — Pair and manage Matter accessories Reviewed 2026-10-30
- Google — Prepare your smart home for Matter Reviewed 2026-10-30
These are evidence-based editorial checks, not a diagnosis of your individual home network.