OpenThread
Replies: 2 comments
-
|
The following log output indicates that otbr-agent is not able to communicate with the RCP: Typical reasons are:
|
Beta Was this translation helpful? Give feedback.
-
|
I have now set the baud rate to 460800 and disabled hardware flow control and automatic updates. Now everything somehow works, and HA also recognizes the Thread router… I don’t understand it. I’m pretty sure I tried the same setup yesterday. However, I’m still getting other errors. Maybe someone can help me understand them and tell me if they’re critical?
Here’s what my log looks like now:
|
Beta Was this translation helpful? Give feedback.
-
Describe the bug A clear and concise description of what the bug is.
After flashing the OpenThread Firmware onto the dongle and connecting it to the Home Assistant (HA) server, the "OpenThread Border Router" add-on encounters an error. The logs repeatedly show a timeout issue ("[W] P-SpinelDrive-: Wait for response timeout" and "C] Platform------: Init() at spinel_driver.cpp:83: Failure"), causing the add-on to continuously restart.
To Reproduce Information to reproduce the behavior, including:
Expected behavior A clear and concise description of what you expected to happen.
The expected behavior is that the OpenThread Border Router add-on recognizes the dongle without any timeouts and operates normally.
Console/log output
`[15:50:20] INFO: The otbr-web is disabled.
s6-rc: info: service mdns: starting
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service mdns successfully started
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service banner: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
[15:50:20] INFO: Starting mDNS Responder...
Default: mDNSResponder (Engineering Build) (Jan 14 2025 21:04:03) starting
Add-on: OpenThread Border Router
OpenThread Border Router add-on
Add-on version: 2.13.0
You are running the latest version of this add-on.
System: Home Assistant OS 14.1 (amd64 / qemux86-64)
Home Assistant Core: 2025.1.2
Home Assistant Supervisor: 2024.12.3
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
[15:50:20] INFO: Flashing firmware is disabled
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service otbr-agent: starting
[15:50:21] INFO: Setup OTBR firewall...
[15:50:21] INFO: Starting otbr-agent...
[NOTE]-AGENT---: Running 0.3.0-b067e5ac-dirty
[NOTE]-AGENT---: Thread version: 1.3.0
[NOTE]-AGENT---: Thread interface: wpan0
[NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/ttyUSB1?uart-baudrate=460800&uart-flow-control
[NOTE]-AGENT---: Radio URL: trel://enp0s3
[NOTE]-ILS-----: Infra link selected: enp0s3
49d.17:08:40.888 [W] P-SpinelDrive-: Wait for response timeout
49d.17:08:42.890 [W] P-SpinelDrive-: Wait for response timeout
49d.17:08:44.893 [W] P-SpinelDrive-: Wait for response timeout
49d.17:08:44.893 [C] Platform------: Init() at spinel_driver.cpp:83: Failure
49d.17:08:46.895 [W] P-SpinelDrive-: Wait for response timeout
[15:50:59] 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
[15:50:59] 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
/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.
s6-rc: info: service universal-silabs-flasher: stopping
s6-rc: info: service mdns: stopping
Default: mDNSResponder (Engineering Build) (Jan 14 2025 21:04:03) 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
[15:50:59] INFO: mDNS ended with exit code 4 (signal 0)...
s6-rc: info: service mdns successfully stopped`
Additional context Add any other context about the problem here.
I am publishing the bug report here because I discovered a similar case here: openthread/ot-br-posix#2412
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions