Problems creating a Thread network for Matter units

Hi,

With all likelyhood I’m lacking the necessary knowledge, but I really got stuck in this case. Been reading forum topics on the matter concerning Thread, Home Assistant and Ipv6 for a while but still cant solve the matter.

I’m trying to connect a Matter unit (IKEA Timmerflotte) to my Home Assistant configuration. I have since before used Wifi-based Matter units and the IKEA Timmerflotte is the first one where I need Thread, why I bought the ZBT-2 and migrated the Zigbee config to the new adapter.

Software:
Core 2026.1.0
Supervisor 2026.01.0
Operating System 16.3

Hardware:
Raspb Pi 5
ZBT-2 (Zigbee)
ZBT-1 (Thread)
Router TP-Link Archer AX55

I am running OpenThread Border Router.

The IKEA Timmerflotte is set in pairing mode and is found when using the QR code, but when connecting it only says “A thread border router is required for the unit” in a Google home screen fashion (looks like Googles loading screenin the Google Home app).

I did go in though my Android device on Google settings to “show available Thread networks” and I get nothing shown. My best guess is that the Thread network is not running properly.

Since people seem to be having ipv6 problems I went in to the router, but I’m all new to ipv6 so I cant tell if its correct.

Router Ipv6 config:

This is the log for my Open Thread Border Router, some of you can probably tell what the problem is from this:

ZBT-1:
Home Assistant SkyConnect
Firmware: OpenThread RCP 2.4.4.0
Serienummer: eefd610056b7ed11bb78955938a92db5

Any thoughts on where I should start or any more info I need to submit?

I’m going mad of hours into this matter, please internet, show me mercy.

//L

Is IPv6 enabled on your Home Assistant networking?

Yes.

Anything else anybody need to know just ask!

Although for a different device, and using iOS based HA companion app instead of Android, check the “prerequisites” section of this link to see if it helps.

1 Like

THANK YOU!

Did actually work on my first try.

Really strange that this bug isn’t fixed allready. Should definitely be flagged to devs.