OpenThread Border Router | Addon no longer starts

Configuration Matter/Thread
1

I got off yesterday, since then I can’t start it anymore, does anyone have an idea? I have not changed anything in the system.
Uninstallation did not help.

Thank you very much

Add-on: OpenThread Border Router
OpenThread Border Router add-on

Add-on version: 2.9.0
You are running the latest version of this add-on.
System: Home Assistant OS 12.4 (amd64 / generic-x86-64)
Home Assistant Core: 2024.7.4
Home Assistant Supervisor: 2024.06.2

Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.

s6-rc: info: service banner successfully started
s6-rc: info: service universal-silabs-flasher: starting
[13:45:23] INFO: Flashing firmware is disabled
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service otbr-agent: starting
[13:45:24] INFO: Setup OTBR firewall…
[13:45:24] INFO: Starting otbr-agent…
[NOTE]-AGENT—: Running 0.3.0-41474ce-dirty
[NOTE]-AGENT—: Thread version: 1.3.0
[NOTE]-AGENT—: Thread interface: wpan0
[NOTE]-AGENT—: Radio URL: spinel+hdlc+uart:///dev/ttyACM0?uart-baudrate=460800
[NOTE]-AGENT—: Radio URL: trel://eno1
[NOTE]-ILS-----: Infra link selected: eno1
68d.19:06:25.750 [W] P-SpinelDrive-: Wait for response timeout
68d.19:06:27.753 [W] P-SpinelDrive-: Wait for response timeout
68d.19:06:29.755 [W] P-SpinelDrive-: Wait for response timeout
68d.19:06:29.755 [C] Platform------: Init() at spinel_driver.cpp:82: Failure
68d.19:06:31.757 [W] P-SpinelDrive-: Wait for response timeout
[13:45:32] WARNING: otbr-agent exited with code 1 (by signal 0).
Chain OTBR_FORWARD_INGRESS (0 references)
target prot opt source destination
DROP all – anywhere anywhere PKTTYPE = unicast
DROP all – anywhere anywhere match-set otbr-ingress-deny-src src
ACCEPT all – anywhere anywhere match-set otbr-ingress-allow-dst dst
DROP all – anywhere anywhere PKTTYPE = unicast
ACCEPT all – anywhere anywhere
otbr-ingress-deny-src
otbr-ingress-deny-src-swap
otbr-ingress-allow-dst
otbr-ingress-allow-dst-swap
Chain OTBR_FORWARD_EGRESS (0 references)
target prot opt source destination
ACCEPT all – anywhere anywhere
[13:45:32] INFO: OTBR firewall teardown completed.
s6-svlisten1: fatal: /run/s6-rc/servicedirs/otbr-agent failed permanently or its supervisor died
s6-rc: warning: unable to start service otbr-agent: command exited 1
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service universal-silabs-flasher: stopping
s6-rc: info: service mdns: stopping
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
Default: mDNSResponder (Engineering Build) (Jul 2 2024 09:04:20) stopping
s6-rc: info: service universal-silabs-flasher successfully stopped
s6-rc: info: service banner: stopping
s6-rc: info: service banner successfully stopped
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
[13:45:32] INFO: mDNS ended with exit code 4 (signal 0)…
s6-rc: info: service mdns successfully stopped

2

What radio are you using ?

3

@francisp SONOFF Zigbee Gateway, ZBDongle-E 3.0 USB Dongle Plus

4

Maybe use /dev/serial/by-id/… instead of ttyACM0

5

@francisp

I have been using this for about 2 months, isn’t that right?

Device
/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2

6

That seems correct.

Other thing to try: remove the dongle and plug it back in.

7

I can only test this on Friday, I’m not on site at the moment.

8

@francisp

I disconnected the HomeAssistant from the power supply and now everything is working again, presumably the USB stick has hung up.

Thank you

1 Like