#Matter/Thread/Docker issues (advanced)

1 messages · Page 1 of 1 (latest)

wild saffron
#

Just coming here as a last resort after I've been scouring the internet for solutions.

I got a ZBT-1 and a custom NAS with custom everything running docker containers for everything. Also a Unifi networking setup (yes, I know), and a Pixel phone.

I get the dreaded "Can't reach device" error after being stuck on the "Checking network connectivity" part.

I'm using the ownbee/hass-otbr-docker docker image, which successfully seems to identify the devices.
Here's the logs I get when trying to pair a device:

otbr  | [INFO]-ADPROXY-: Advertise SRP service updates: host=D22E59DFAC305CD6.default.service.arpa.
otbr  | [INFO]-MDNS----: Registering service 30CAB34BEE7248C6-75BD18D92DA844CF._matter._tcp,_I30CAB34BEE7248C6
otbr  | [INFO]-MDNS----: Registering new host D22E59DFAC305CD6
otbr  | [INFO]-MDNS----: Successfully registered host D22E59DFAC305CD6 address fd4f:c2e6:3f7e:1:a0cb:283a:2272:631f
otbr  | [INFO]-MDNS----: Successfully registered all host D22E59DFAC305CD6 addresses
otbr  | [INFO]-ADPROXY-: Handle publish SRP host 'D22E59DFAC305CD6.default.service.arpa.': OK
otbr  | [INFO]-ADPROXY-: Waiting for more publishing callbacks 1
otbr  | [INFO]-MDNS----: Successfully registered service 30CAB34BEE7248C6-75BD18D92DA844CF._matter._tcp

I have mdns records for _matter._tcp, and the border router (as recieved by my PC, separate from the NAS)

+ enp5s0 IPv6 Home Assistant OpenThread Border Router #733A _meshcop._udp        local
+ enp5s0 IPv4 Home Assistant OpenThread Border Router #733A _meshcop._udp        local
...
+ enp5s0 IPv6 A59885CF5CAE6400-000000000001B669             _matter._tcp         local
+ enp5s0 IPv4 A59885CF5CAE6400-000000000001B669             _matter._tcp         local

Here's the logs from the matter server, running ghcr.io/home-assistant-libs/python-matter-server
https://pastebin.com/PdgGYKuJ
Note that there's a couple errors, and no further logs come from new devices.

Would anyone have any pointers?
(no I can't use a HAOS VM)

Pastebin
matter-server | 2025-02-24 21:44:13.095 (MainThread) INFO [matter_...

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

#
  • I'm on 2.4ghz
  • I've followed all the recommendations for unifi setup, including mdns related settings, ipv6, etc
  • The NAS has an associated ipv6 on the main network port
  • I tried clearing Google Home app cache, rebooting my phone, resetting the device
#

The thread device is an Eve smart plug

wild saffron
#

Some more investigation, running avahi-browse -r _matter._tcp

= enp5s0 IPv4 30CAB34BEE7248C6-C13D3CF886C2C0DF             _matter._tcp         local
   hostname = [7EE92B02D2875BF5.local]
   address = [fd4f:c2e6:3f7e:1:8e81:d3b6:f0f6:a94e]
   port = [5540]
   txt = ["T=0" "SAI=800" "SII=800"]
= enp5s0 IPv6 30CAB34BEE7248C6-C13D3CF886C2C0DF             _matter._tcp         local
   hostname = [7EE92B02D2875BF5.local]
   address = [fd4f:c2e6:3f7e:1:8e81:d3b6:f0f6:a94e]
   port = [5540]
   txt = ["T=0" "SAI=800" "SII=800"]

I can view the device address that gets created when I try to pair. I can ping it too.
It has about 20ms of ping latency, so I assume it's the eve hub itself
then it dies after a bit

wild saffron
#

ping me if anyone else is struggling (only if you know how to compile+run rust programs)

sage tulip
#

You could have make it yourself a whole lot easier by just using the webinterface of the matter server

wild saffron
#

but regardless, I think the BLE part did the trick

#

weirdly, even though I plugged in BLE and rebooted, matter-server was still refusing to use BLE for discovery. Only DNS-SD