#OTBR in docker - Failed to connect?
1 messages · Page 1 of 1 (latest)
I'm only getting the "Failed to connect" message, and I'm unable to find any documentation which could help me point to what I'm doing wrong
Are you using the upstream docker image?
Yes
# OpenThread Border Router
otbr:
container_name: otbr
image: openthread/otbr:latest
privileged: yes
# - IPC_LOCK
# - NET_ADMIN
sysctls:
- net.ipv6.conf.all.disable_ipv6=0
- net.ipv4.conf.all.forwarding=1
- net.ipv6.conf.all.forwarding=1
ports:
- 20180:80
dns:
- 127.0.0.1
volumes:
- /dev/ttyAMA1:/dev/ttyAMA1
command:
- --radio-url
- spinel+hdlc+uart:///dev/ttyAMA1
The otbr integration is written for the OTBR builds that are packaged for HAOS
There are eg at least 3 patches to the REST API in this one https://github.com/home-assistant/addons-development/tree/master/openthread_border_router
While not probably the root cause of the error, what you are doing is hard mode and multiple steps away from working
…that should probably be documented somewhere, none of the documentation implies upstream won't work, or even mentions any patches
Ive seen core members say that running this stack without haos is not supported
Because there are so many moving pieces
Haos even carries kernel patches to make thread work reliably
…thread radio on the yellow is a dud then.
I thought the yellow was designed for the appliance use case (ie haos)
…or just a Pi with a M.2 slot and integrated Thread/ZigBee radio?
My main reason for switching to the Yellow was getting rid of the noisy USB3 SSD for a M.2 disk in stead, and also the nice case. The Thread/ZigBee radio was a nice bonus, but I've already got a ZigBee stick running with zigbee2mqtt, so I figured it'd be fun to get started with Thread, as the ESP32-C6 looks interesting, and getting it, and the nRF52 chips connected and working ESPHome would've been fun
I’m sorry that isn’t going to work out for you. Right now (from watching discord, I’m no better off than you other than having been in this channel for a year, I’m not staff) the preference is to run thread from HomePods or the google equivalent. The (not stock) thread firmware for the SkyConnect and Yellow being “preview” or experimental.
There are patches for the kernel, network manager, OTBR, etc. many of these have been sent upstream but eg no one even acked the network manager ones yet.
None haos systems running systemd-networkd may have thread problems too. And none-systemd, none-network-manager systems need to have kernels built with certain ipv6 features. And sysctls fiddled with.
Because of all of that and not being Apple or google in terms of dev power the priority seems to be haos
I would've been quite content with a warning on the integration page, pointing at the patches, because currently the docs don't mention any special requirements other than an "open thread border router"
That would've pointed me in the right direction, or saved me from wasting time on even attempting.