HA Docker with OTBR docker

[D34DC3N73R]

@agners

is your OTBR routing correctly? Can you ping devices on the Thread network from other devices? There are a few sysctrls you need to take care of yourself to get IPv6 routing etc. going.

It seems to be working correctly. It makes a wpan0 network on the host, I see very few errors in the logs (just grabbed a tail) but it’s hard to tell with it being so chatty. I can ping any public ipv6, public temp ipv6, link-local ipv6 (fe80), but get some weird errors when trying to ping fd88. Maybe I’m doing that wrong? My bad it’s late here and the info panel 2 line stacks the ipv6 address. The fd88 ipv6 address also resolves.

Edit: I’ll also add that once the OTBR integration is set, the thread integration is auto-discovered by HA, and HA can reset/create a new thread network without any trouble.

$ ping fd88:7ccb:7e99:1:2f17:5ac7:4d23:e174
PING fd88:7ccb:7e99:1:2f17:5ac7:4d23:e174(fd88:7ccb:7e99:1:2f17:5ac7:4d23:e174) 56 data bytes
64 bytes from fd88:7ccb:7e99:1:2f17:5ac7:4d23:e174: icmp_seq=1 ttl=64 time=1737 ms
64 bytes from fd88:7ccb:7e99:1:2f17:5ac7:4d23:e174: icmp_seq=2 ttl=64 time=733 ms

I do have sysctls set on the host system, at least all that I could find since much of this is undocumented. Please let me know if I’m missing any.

@D34DC3N73R

host system sysctls are set as:

$ sysctl net.ipv6.conf.all.disable_ipv6 net.ipv4.conf.all.forwarding net.ipv6.conf.all.forwarding net.ipv6.conf.all.accept_ra_rt_info_max_plen net.ipv6.conf.all.accept_ra
net.ipv6.conf.all.disable_ipv6 = 0
net.ipv4.conf.all.forwarding = 1
net.ipv6.conf.all.forwarding = 1
net.ipv6.conf.all.accept_ra_rt_info_max_plen = 64
net.ipv6.conf.all.accept_ra = 2

The only thread device I currently have is that Aqara P2 contact sensor. I wanted to get that working before spending money on other devices.

@agners

You can do the same from the frontend directly from the hidden panel at /config/matter/dashboard.

This is absolutely huge and I wish I had known about this much earlier. It does rely on BT, which I do have available on my server but don’t use it for anything. I assume that is why the matter server volume mounts the dbus to begin with.

@agners

In the end, phone based commissioning is just more practical

I’m kinda bummed neither of the android phones I have worked for commissioning and would like to figure out why. Maybe I’ll look into adb logs and see what I can find out. One of the phones is rooted, so I hope I can access what I need.