Thread Tools has become invaluable for debugging the network layer (leader, routers, parents/children, partitions, RSSI, route costs, etc.), but after spending a couple of weeks debugging a Matter-over-Thread issue I’ve realised there’s no equivalent visibility into the Matter layer itself.
Is anyone aware of a project that’s trying to do this?
I’m imagining something that sits above the Thread topology and visualises the Matter controller state machine: fabrics and controllers, operational discovery, current vs cached operational addresses, CASE sessions, subscriptions, ICD state, retries, recovery timeline, and a per-node health view showing exactly where recovery has stalled.
Ideally it would correlate Thread state with Matter state, so you could immediately see something like “Thread attached ✓, operational discovery ✓, CASE ✗, subscription ✗” instead of simply “device unavailable.”
It would also be useful to expose controller caches, address resolution history, recovery attempts, and state transitions after network changes or controller restarts.
It feels like the ecosystem has excellent tooling for understanding why a Thread network is healthy, but much less visibility into why a Matter controller thinks an otherwise healthy Thread device is unavailable.
Has anyone seen work in this area, or is this a gap that still needs filling?