Thread/Matter Can't reach device (first installed device)

Configuration Matter/Thread
,
1

Running HA Green with HAOS 2026.5.4 and Samsung S20FE with companion app 2026.4.4-full. Using 2.4 Ghz Wifi. installed ZBT-2 for Thread.
Integrations list ZBT-2, Matter, OTBR and Thread. Google Play Services lists Matter (no devices) and thread with "ha-thread-1711" as available network. IPv6 is Automatic on HA.
Tried commissioning IKEA MYGGSPRAY motion detector. Connecting to device, then Generating matter credentials, then process hangs up on "Checking Connectivity to Thread network ha-thread-1711" and eventually says "Can't reach device. Make sure phone is connected to Wi-Fi."
Had the icon with the key in it, but that disappeared somewhere in the process. "Used for Android and IOS credentials" was used, it is now greyed out.
Using companion troubleshooting/Sync thread credentials results in "Home assistant and this device use the same network."
Removed everything and reinstalled back at the same place. Seem to be going in circles.

2

Are you using VLANs?

3

No. Lan is combination of 2.4 and 5 Ghz wireless devices and ethernet. Most of the existing HA setup is Zigbee.

4

Maybe the 2.4GHz and 5GHz WiFi networks are segregated, so make sure your phone is using the 2.4GHd WiFi network and have it set as the preferred one during commissioning.

5

Thanks Wally. Tried it both ways.

6

You have to run:

ha docker options --enable-ipv6=true

in Terminal to manually activate IPv6 forwarding in HA. Just setting IPv6 to auto isn't enough.
Afterwards restart HA!

7

Thanks, but I am not using docker, I have HA green.

8

Got nothing to do with running in a docker or not. HA. HA itself is running in its own docker, that's why you can e.g. update different "parts" of it, like core, ha os, and so on. Just try it!

9

Thanks. Bit of a newbie here so steep learning curve! Made the change, but still hung up in the same place both with 2.4Ghz and 5 Ghz cell connection. Times out to "Can't reach device. Make sure phone is connected to Wi-Fi." The good news is the OTBR consistently shows the box with a key and a 16 character hex code.

10

Connected. Finally. Used browser instead of companion app and connected instantly.
Thanks for the help.

1 Like