Skip to content

Expand on Thread diagnostics to leverage troubleshooting options if needed #112

Description

@mkerstner

Problem statement

wip https://docs.google.com/document/d/1LkJjv6aJgf4PlKI-Hz5SFmlDTm5RmhGR4ZAb70btXJo/edit?tab=t.0#heading=h.wi76e4wh04n9


Thread is becoming another foundational protocol in Home Assistant's stack, powering a growing number of Matter and native Thread devices. Yet when things go wrong like devices not being able to be added, dropping off the mesh, border routers losing connectivity, or latency spikes affecting responsiveness users have limited actionable visibility into what's happening at the network level.

Home Assistant collects Thread diagnostic data through its border router integrations, but it's largely surfaced in raw, developer-facing forms: buried in logs or requiring comfort with OpenThread dataset outputs.

Having easier access to structured diagnostic signals that would make root-cause analysis faster.

Quite recently, CSA released the Thread Analysis App which aims to bridge this support gap and also clearly shows demand for a more user-friendly approach of surfacing contextual analytics data.

Community signals

No response

Scope & Boundaries

In scope

Not in scope

Foreseen solution

No response

Risks & open questions

No response

Appetite

No response

Execution issues

No response

Decision log

Date Decision Outcome

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions