Thread diagnostics
Start with the missing role
A Thread accessory needs a Thread mesh and, for communication with devices and controllers on the home’s Wi-Fi or Ethernet network, a Thread border router. Matter administration also needs a compatible Matter controller. One product may combine those roles; never infer both from a generic “hub” label.
Thread diagnostics
Use the failure pattern
| Pattern | Likely layer | Next test |
|---|---|---|
| One accessory fails | Power, range, device state, or commissioning. | Test a nearby Thread accessory and direct platform control. |
| Thread devices in one area fail | Mesh reach or a removed mains-powered routing device. | Restore recent placement/power changes. |
| All Thread devices fail across platforms | Border-router or adjacent-LAN path. | Confirm border routers are powered and locally reachable. |
| One platform fails | Controller, fabric, account, or platform state. | Test the same shared device in another commissioned platform. |
Thread diagnostics
Multiple border routers can help—but verify the actual state
Thread supports multiple border routers and can provide redundant paths. Thread Group also documents homes with more than one Thread mesh. That does not mean every platform exposes topology or shares credentials identically. Treat current app diagnostics as platform behavior, and confirm exact models, software, and ecosystem support.
Thread diagnostics
Preserve the mesh while diagnosing
- Note recent power, router, controller, and placement changes.
- Restore power to known border routers and mains-powered Thread devices.
- Test a nearby device, then one at the affected edge.
- Confirm the phone/controller is on the intended adjacent LAN.
- Reboot one infrastructure device only when its maker supports that step.
- Recommission or reset a single accessory only after the failed layer is isolated.
Evidence boundary
Network behavior depends on the exact setup
Router, mesh, platform, model, software, and region behavior can change. Confirm current documentation before changing network security or resetting a device. Never expose devices directly to the internet merely to restore discovery.
Primary sources
Official documentation behind the network boundaries
Continue the diagnosis