OpenThread Border Router via network stopped working (FIXED)

Configuration Matter/Thread
1

Hello,
I am running HAOS in a VM. I had a SLZB-06M working well with the OTBR addon, but it stopped working and I can’t get it to work again.
This is the log:

s6-rc: info: service socat-otbr-tcp: starting
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
[07:04:40] INFO: Starting mDNS Responder...
Default: mDNSResponder (Engineering Build) (Oct  7 2025 12:31:51) starting
[07:04:40] INFO: Starting socat TCP client for OTBR daemon...
-----------------------------------------------------------
 Add-on: OpenThread Border Router
 OpenThread Border Router add-on
-----------------------------------------------------------
 Add-on version: 2.14.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 16.2  (amd64 / qemux86-64)
 Home Assistant Core: 2025.10.4
 Home Assistant Supervisor: 2025.10.0
-----------------------------------------------------------
 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 socat-otbr-tcp successfully started
s6-rc: info: service otbr-agent: starting
[07:04:40] INFO: Setup OTBR firewall...
[07:04:40] 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:///tmp/ttyOTBR?uart-baudrate=460800&uart-init-deassert
[NOTE]-AGENT---: Radio URL: trel://enp1s0
[NOTE]-ILS-----: Infra link selected: enp1s0
tiocmbic: Inappropriate ioctl for device
58d.13:56:00.981 [W] P-SpinelDrive-: Wait for response timeout
58d.13:56:02.983 [W] P-SpinelDrive-: Wait for response timeout
58d.13:56:04.985 [W] P-SpinelDrive-: Wait for response timeout
58d.13:56:04.985 [C] Platform------: Init() at spinel_driver.cpp:83: Failure
58d.13:56:06.987 [W] P-SpinelDrive-: Wait for response timeout
[07:04:48] 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            
[07:04:48] 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 banner: stopping
s6-rc: info: service socat-otbr-tcp: stopping
s6-rc: info: service mdns: stopping
s6-rc: info: service banner successfully stopped
Default: mDNSResponder (Engineering Build) (Oct  7 2025 12:31:51) stopping
2025/10/27 07:04:48 socat[81] W exiting on signal 15
s6-rc: info: service socat-otbr-tcp 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
[07:04:48] INFO: mDNS ended with exit code 4 (signal 0)...
s6-rc: info: service mdns successfully stopped
s6-rc: info: service mdns successfully stopped

I am not sure if there is a correlation, but I only noticed the error after updating HA Core to 10.4.

Any ideas on how to fix this?

2

Doh. The fix was simple - I unplugged and plugged again the SLZB and it now works. A reboot (many reboots) request on the SLZB web interface wasn’t enough, it needed power off and now it responds.
It seems to be related to firmware updates on the SLZB, as I was able to repeat the issue by downgrading the firmware to 3.0.6 and then updating it back to 3.0.8. Needed a full power off restart to be able to fully connect to it with the OTBR addon.
The logs now are these:

[07:19:40] INFO: The otbr-web is disabled.
[07:19:40] INFO: Enabled socat-otbr-tcp.
s6-rc: info: service socat-otbr-tcp: starting
s6-rc: info: service mdns: starting
s6-rc: info: service s6rc-oneshot-runner: starting
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 mdns successfully started
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
[07:19:40] INFO: Starting mDNS Responder...
Default: mDNSResponder (Engineering Build) (Oct  7 2025 12:31:51) starting
[07:19:40] INFO: Starting socat TCP client for OTBR daemon...
-----------------------------------------------------------
 Add-on: OpenThread Border Router
 OpenThread Border Router add-on
-----------------------------------------------------------
 Add-on version: 2.14.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 16.2  (amd64 / qemux86-64)
 Home Assistant Core: 2025.10.4
 Home Assistant Supervisor: 2025.10.0
-----------------------------------------------------------
 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 socat-otbr-tcp successfully started
s6-rc: info: service otbr-agent: starting
[07:19:40] INFO: Setup OTBR firewall...
[07:19:40] 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:///tmp/ttyOTBR?uart-baudrate=460800&uart-init-deassert
tiocmbic: Inappropriate ioctl for device
[NOTE]-AGENT---: Radio URL: trel://enp1s0
[NOTE]-ILS-----: Infra link selected: enp1s0
58d.14:10:59.647 [C] P-SpinelDrive-: Software reset co-processor successfully
00:00:00.479 [N] RoutingManager: BR ULA prefix: fd7b:8a56:3693::/48 (loaded)
00:00:00.480 [N] RoutingManager: Local on-link prefix: fd67:73f8:514e:1ce4::/64
00:00:00.578 [N] Mle-----------: Role disabled -> detached
00:00:00.590 [N] P-Netif-------: Changing interface state to up.
00:00:00.620 [W] P-Netif-------: Failed to process request#2: No such process
00:00:00.620 [W] P-Netif-------: Failed to process request#6: No such process
s6-rc: info: service otbr-agent successfully started
s6-rc: info: service otbr-agent-configure: starting
[07:19:42] INFO: Enabling NAT64.
Done
00:00:00.818 [W] P-Netif-------: Failed to process request#7: No such process
Done
Done
s6-rc: info: service otbr-agent-configure successfully started
s6-rc: info: service otbr-agent-rest-discovery: starting
[07:19:42] INFO: Successfully sent discovery information to Home Assistant.
s6-rc: info: service otbr-agent-rest-discovery successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
00:00:28.043 [N] Mle-----------: RLOC16 9800 -> fffe
00:00:28.303 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
00:00:28.303 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
00:00:34.803 [N] RouterTable---: Allocate router id 38
00:00:34.803 [N] Mle-----------: RLOC16 fffe -> 9800
00:00:34.818 [N] Mle-----------: Role detached -> leader
00:00:34.819 [N] Mle-----------: Partition ID 0x10aa6355
[NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
00:00:39.705 [W] DuaManager----: Failed to perform next registration: NotFound
3

communication or permission issue accessing radio?

EDIT
glad you got it fixed.

4

Hello Bernardo Bandos,

If one of the suggestions listed solves your problem, please consider clicking the solution button to close the thread. (even your own…)
How to help us help you - or How to ask a good question.

5

Hello @Sir_Goodenough ,
Unfortunately I don’t see a “solution checkbox” when I click the three dots on any of the posts. This is what I see:

no solution button
no solution button1091×233 18 KB

6

This is what you are looking for.

image
image543×122 3.55 KB

You might need to post a bit more before it shows up as a new poster.