Skip to content

Investigate the current state of Thread credential sharing to deduct potential improvements #137

@mkerstner

Description

@mkerstner

Problem statement

As outlined in the overarching opportunity #91, before Thread 1.4, cross-vendor Thread interoperability was a persistent pain point. When Matter first launched, the process for credential exchange was not fully defined. This led to one of the biggest construction sites in the standard: Thread Border Routers from different manufacturers couldn't talk to each other.

Instead of forming a shared Thread network, they sometimes spun up separate and parallel mesh networks (which be definition is not what a mesh network should be about). Workarounds via smartphone operating systems helped bridge the gap in some cases (ref Sync Thread credentials in the Home Assistant Companion App)

Thread 1.4, released in September 2024, standardises credential sharing. When a Thread 1.4 border router joins a home, it (generally) joins the existing Thread network instead of creating a new one, ideally resulting in one unified mesh across brands.

As outlined in the overarching opportunity #91 Home Assistant already now features certain ways for Thread credential sharing.

While these paths definitely make sense going into the direction of having

and thus establishing full Thread 1.4 compatibility Thread credential sharing is something that we can revisit and think about ways to make it even more approachable to our users.

Community signals

As outlined in #91

Scope & Boundaries

In scope

  • Revisit existing Thread credential sharing approach
  • Based on OTBR Thread 1.4 support clarify UX potentials (during setup / onboarding but also thereafter)
  • Document proposed improvements and future opportunities

Not in scope

Foreseen solution

  • Have an aligned and documented view on how to improve the existing Thread credential sharing theme

Risks & open questions

No response

Appetite

No response

Execution issues

No response

Decision log

Date Decision Outcome

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Status

Shaping

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions