Support Thread 1.4 Credential Sharing

[asucrews]

Describe the enhancement

Please add support for Thread 1.4 network sharing done with 9 digit code. Current Ikea Dirigera hub support this. this would allow easier integration between thread border routers and thread networks.

Device or feature details

Ikea Dirigera hub supports this with there push of Thread 1.4 firmware

Use cases

easier integration between thread border routers and thread networks.

Anything else?

https://www.notebookcheck.net/IKEA-Dirigera-smart-home-hub-now-Matter-1-4-certified.1152278.0.html

[tommyjlong]

May I ask for clarification, I think you are referring to Thread 1.4's Thread Credential Sharing feature (which uses a 9 digit code to gain access to the Thread credentials) and not Matter 1.4, right?

[asucrews]

Did not know thread had versions, thought is was matter.

[lboue]

Here’s a summary of the key changes (i.e. “changelog”) in Thread 1.3 and Thread 1.4, based on publicly available sources (Thread Group blog, white papers, spec, etc).

---

Thread 1.3 Changelog (What's new in 1.3)

Based on the Thread Group announcement for Thread 1.3.0: ([threadgroup.org][1])

1. Matter Enablement

   • Thread 1.3 is positioned as the foundation for Matter devices on Thread: it supports full IP routing and service discovery so that Matter (or other application layers) can interoperate over Thread, Ethernet, Wi-Fi, etc. ([threadgroup.org][1])
   • This makes it easier for Matter-enabled devices to join existing IP-based networks via a Thread Border Router. ([threadgroup.org][1])

2. Backward Compatibility

   • Thread 1.3 is fully backward compatible with earlier versions (e.g., Thread 1.1, 1.2). ([threadgroup.org][1])
   • This helps device makers: they can support 1.3 without breaking support for older Thread devices.

3. Border Router Improvements

   • Border Routers in 1.3 support bidirectional IPv6 connectivity.
   • They also support DNS-based service discovery (mDNS / DNS-SD).
   • Added IPv4 support (via NAT) to allow legacy IPv4 devices or integration.
   • “Thread-over-infrastructure”: support for non-802.15.4 links (i.e., Thread over IP) is part of the 1.3 spec. According to Silicon Labs app note.
   • To improve throughput, Thread 1.3 standardizes TCP as a protocol for communication.

---

Thread 1.4 Changelog (New in 1.4 / Enhancements)

Based on the Thread 1.4 White Paper from Thread Group and other sources.

Thread 1.4 introduces six major areas of enhancement. Here are the key changes:

1. Credential Sharing

   • Standardized mechanism to share credentials between Thread devices / border routers.
   • This enables a more seamless setup: e.g., when you add a Thread 1.4 Border Router, it can join an existing Thread network rather than creating a separate one. ([threadgroup.org][2])
   • This is very useful for multi-vendor or cross-ecosystem setups. ([threadgroup.org][2])

2. Improved Internet Connectivity (Cloud Connectivity)

   • Border routers now have a defined standard path to the internet. ([threadgroup.org][2])
   • Supports IPv4 (via NAT64 / DNS64) and IPv6 (via DHCPv6 Prefix Delegation) for internet access.
   • This allows devices to more reliably connect to cloud services, do remote updates, etc. ([threadgroup.org][2])

3. Enhanced Network Diagnostics

   • New diagnostic capabilities: Thread devices (especially routers) can report more detailed topology and network status.
   • This gives developers, installers, and users better visibility into the mesh and helps with troubleshooting. ([threadgroup.org][2])

4. Thread-over-Infrastructure

   • Full support for “Thread-over-infrastructure”: Thread messages over non-802.15.4 links (e.g., Ethernet or Wi-Fi).
   • This allows for extending a Thread mesh using existing IP infrastructure, improving reach and flexibility. ([threadgroup.org][3])

5. Secure Commissioning at Scale (TCAT)

   • Introduction of Thread Commissioning over Authenticated TLS (TCAT): more secure way to onboard devices using TLS.
   • This helps for professional / commercial deployments, especially where devices may be pre-installed, or need secure commissioning.

6. Mesh Robustness & Scalability Improvements

   • Several under-the-hood improvements to make the mesh more robust, scalable, and resilient.
   • These include optimizations and protocol-level enhancements targeted at large or dense networks.

---

Other Notes & Implications

• According to the Q3/Q4 2024 Thread newsletter, the Thread 1.4 release is seen as “pivotal,” with credential sharing, cloud connectivity, debugging, and more emphasized. ([threadgroup.org][3])
• Silicon Labs’ app note AN1499 provides guidance for configuring Thread 1.4 in OpenThread, confirming that many new features (credential sharing, diagnostics, DHCPv6 Prefix Delegation) are enabled / mandatory for 1.4 border routers. ([Silicon Labs][4])
• In code (OpenThread), version defines were updated: e.g., they define OT_THREAD_VERSION_1_4 = 5. ([android.googleid.googlesource.com][5])

---

[asucrews]

So is the major milestone is HA OBTR and HA would need to updated to support 1.4?

[lboue]

Yes, Thread 1.4 is prerequisite because Credential Sharing is defined in 1.4 version.

[Tobster77]

Dear all,
may we assume the Thread implementation will find its way to HA? I just bought a ZBT-2 in order to get my thread network running, now the coverage in my house would take advantage from a second border router (which I could connect to the Ethernet network). Repeaters help, but I assume a second border router would be better. If I got it right, this again needs Thread 1.4 Credential Sharing...

We had a discussion on the Thread versions here.

[asucrews]

Could be what border router do you have? Is it by apple, Ikea, or smartthings?

[Tobster77]

I have an IKEA TBR, offering Credential Sharing.

[asucrews]

Yep for sure then :( we have to wait on ha or another dev to make it happen.

[codersaur]

Just spent the day troubleshooting why my new 3rd party TBR won't discover and join my existing Thread network (run by HA OTBR). Disappointing to find that Home Assistant is so far behind compared to SmartThings/IKEA etc!

Is there at least a target date for when HA OTBR will be bumped to v1.4?

[asucrews]

Looks like @lboue has pending PR that help with HA OBTR on version 1.3 vs Ikea, smart things, and apple on 1.4. not sure if address everything but it a great start.

home-assistant/addons#4281

[kF13Ld]

It seems Thread 1.4 support was merged here:
home-assistant/addons#4323
I can enable "beta" here
http://:8123/config/app/core_openthread_border_router/config
But what do I do now? How can I merge the HA OTBR with an Echo Dot Max Thread network?

[NorbertHD]

You can only merge to a thread network that has version 1.4 or higher. But Amazon Echo devices currently have only Thread version 1.3.

[kF13Ld]

Ok, I get a code in that form 1234-567-8901, so it seems not to be Thread 1.4.

[p-rintz]

It doesnt look like we can get the network credentials as needed to input into a IKEA border router either, though.

Or is there any way?

I have the beta addon running, but I see no way to get the credentials.

[Tobster77]

It doesnt look like we can get the network credentials as needed to input into a IKEA border router either, though.

Or is there any way?

I have the beta addon running, but I see no way to get the credentials.

I lost the overview has we seem to have a "half-way Thread 1.4" if I got this right. There might be an option via command line, if I'm right. But this definitely has not been exposed to the GUI.

Maybe someone with better understanding can help!

[asucrews]

How I read that post, it doesn't implement network share. Looks like there more work needed for 1.4 :(

[codersaur]

You can use the ot-ctl command in the otbr shell to generate an ephemeralkey, which you then input into the other controller. See: home-assistant/addons#4373 (comment)

[asucrews]

Also there don't look like a implmentaion of 1.4 9 number network share code.

[agners]

This roadmap opportunity includes Thread credential sharing: OpenHomeFoundation/roadmap#91.

We working on making the current OTBR with Thread 1.4 the default which is a prerequisite of credential sharing indeed.