Border router disappears randomly from home assistant thread network #2216
Comments
|
The border router list shown in Home Assistant is based on mDNS/DNS-SD Anything in the logs of the otbr container ( |
|
@agners i copy only the relevants sections of otbr container logs
### and then... board router get out at 08:27:25, this is logs:
|
|
Uh, I am a bit confused, is that container running It does seem to me that something with the OTBR container is wrong, as it has this It doesn't look like the official docs on how to use the Docker container use a bridged setup, maybe the container is not designed to be used that way? I'd suggest to monitor/track mDNS announcements from the outside to see if there are remove announcements. That would explain the behavior you see in Home Assistant. Then the question becomes why is the OTBR sending remove announcements? If you want a easy and just works setup: I can recommend using Home Assistant OS. It offers the OpenThread border router add-on, which is built from upstream OpenThread repositories (see https://github.com/home-assistant/addons/tree/master/openthread_border_router). The whole stack of Home Assistant OS + Home Assistant Core + OTBR add-on is well tested and known to be working well. |
|
It all depends on the type of your installation. Can you write something more. You have typical symptoms for OTBR in bridge mode and Home Assitant in host mode. In such a configuration you need to build a completely new OTBR image. What on the host is responsible for mdns? Without major problems, OTBR works in host mode but, as I mentioned, you need to prepare it for this. Below you will find a dockerfile to build OTBR in host mode. I personally use Avahi instead of mDNSResponder. My Dockerfile. ARG BASE_IMAGE=ubuntu:bionic ARG INFRA_IF_NAME ENV INFRA_IF_NAME=${INFRA_IF_NAME:-eth0} RUN env ENV OTBR_DOCKER_REQS sudo python3 ENV OTBR_DOCKER_DEPS git ca-certificates ENV OTBR_BUILD_DEPS apt-utils build-essential psmisc ninja-build cmake wget ca-certificates ENV OTBR_OT_BACKBONE_CI_DEPS curl lcov wget build-essential python3-dbus python3-zeroconf ENV OTBR_NORELEASE_DEPS RUN apt-get update COPY ./script /app/script RUN ./script/bootstrap RUN ([ "${DNS64}" = "0" ] || chmod 644 /etc/bind/named.conf.options) ENTRYPOINT ["/app/etc/docker/docker_entrypoint.sh"] EXPOSE 80 My Docker Compose. version: "3.4"
|
|
Closing stale issue. |
I'm trying the last official openthread docker image with a sonoff-e dongle flashed with the last openthread fw (2.4.1)
I've activated the otbr integration in homeassistant (http://my-ip:8081) and it connects well.
The Thread integration is auto discovered from home assistant and it creates a network with a name like "ha-thread-XXXX" as you can see in the image below:
After a few minutes (random, about 5), the border router disappears from the thread network with this error "no border routers were found" as you can see in the image below:
If i "click" on "reset boarder router", home assistant makes a new thread network with another name (ha-thread-YYYY) and after a few minutes i get the same problem: the border router disappares again etc etc etc
The border router web page is always reachable.
The logs doesnt help beacuse i dont see any error.
this is my compose yaml
` otbr:
container_name: otbr
image: openthread/otbr:latest
ports:
- "8086:80"
- "8081:8081"
volumes:
- /dev/ttyACM0:/dev/ttyUSB0
- /home/paolo/docker/thread:/var/lib/thread
privileged: true
cap_add:
- SYS_ADMIN
- NET_ADMIN
command: --radio-url spinel+hdlc+uart:///dev/ttyUSB0?uart-baudrate=460800
sysctls:
- net.ipv6.conf.all.disable_ipv6=0
- net.ipv4.conf.all.forwarding=1
- net.ipv6.conf.all.forwarding=1
dns:
- 127.0.0.1
networks:
- rete_otbr
ulimits: #THIS IS NECESSARY otherways rsyslog takes a long time to start. with this start in few seconds. bug?
nofile:
soft: "65536"
hard: "65536"
networks:
rete_otbr:
driver: bridge
driver_opts:
com.docker.network.bridge.name: "otbr0"
enable_ipv6: true
ipam:
config:
- subnet: fd11:db8:1::/64
`
The text was updated successfully, but these errors were encountered: