SLZB-MR1 - Open Thread Border Router

So I just got my SLZB-MR1 in and would like to use one antenna for zigbee and the other for matter over thread, for which I need help setting it up and understanding the problem.
My HA is a VM in Proxmox, and I’m able to connect the antenna using PoE and USB. HA, OTBR and the antenna are all updated to the latest versions.
I’ve also tried older versions of the firmware, tried uninstalling all elements involving matter and/or thread, trying to install it with only USB,

I’ve followed several tutorials for setting this up based on previous models, but keep getting at least some form of error, with my latest attempt resulting in the log/error below.

[01:49:03] INFO: The otbr-web is disabled.

[01:49:03] 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

[01:49:03] INFO: Starting mDNS Responder...

Default: mDNSResponder (Engineering Build) (Jan 14 2025 21:04:03) starting

[01:49:03] INFO: Starting socat TCP client for OTBR daemon...

-----------------------------------------------------------

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 15.2 (amd64 / qemux86-64)

Home Assistant Core: 2025.5.3

Home Assistant Supervisor: 2025.05.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

[01:49:04] INFO: Flashing firmware is disabled

s6-rc: info: service universal-silabs-flasher successfully started

s6-rc: info: service socat-otbr-tcp successfully started

s6-rc: info: service otbr-agent: starting

[01:49:04] INFO: Setup OTBR firewall...

[01:49:04] 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://enp0s18

[NOTE]-ILS-----: Infra link selected: enp0s18

tiocmbic: Inappropriate ioctl for device

49d.20:11:16.087 [C] P-SpinelDrive-: Software reset co-processor successfully

00:00:00.110 [N] RoutingManager: No valid /48 BR ULA prefix found in settings, generating new one

00:00:00.115 [N] RoutingManager: BR ULA prefix: fd62:7e28:bd28::/48 (generated)

00:00:00.115 [N] RoutingManager: Local on-link prefix: fdde:ad00:beef:cafe::/64

00:00:00.126 [W] P-Netif-------: Failed to process request#2: No such process

s6-rc: info: service otbr-agent successfully started

s6-rc: info: service otbr-agent-configure: starting

Done

s6-rc: info: service otbr-agent-configure successfully started

s6-rc: info: service otbr-agent-rest-discovery: starting

00:00:00.555 [N] RoutingManager: Local on-link prefix: fd00:bd91:bc72:f722::/64

[01:49:05] 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

00:00:00.577 [N] Mle-----------: Role disabled -> detached

00:00:00.589 [N] P-Netif-------: Changing interface state to up.

00:00:00.605 [W] P-Netif-------: Failed to process request#5: No such process

s6-rc: info: service legacy-services successfully started

00:00:00.904 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset

00:00:07.404 [N] RouterTable---: Allocate router id 47

00:00:07.404 [N] Mle-----------: RLOC16 fffe -> bc00

00:00:07.412 [N] Mle-----------: Role detached -> leader

00:00:07.412 [N] Mle-----------: Partition ID 0x4043ee0

[NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!

00:00:08.874 [W] DuaManager----: Failed to perform next registration: NotFound

The error below is something I had in the past

[01:28:03] INFO: The otbr-web is disabled.
[01:28:03] 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 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
[01:28:03] INFO: Starting mDNS Responder...
Default: mDNSResponder (Engineering Build) (Jan 14 2025 21:04:03) starting
s6-rc: info: service legacy-cont-init successfully started
[01:28:03] INFO: Starting socat TCP client for OTBR daemon...
2025/06/11 01:28:03 socat[77] W recvmsg(): Resource temporarily unavailable
2025/06/11 01:28:03 socat[77] E connect(7, AF=2 192.168.68.197:6638, 16): Connection refused
-----------------------------------------------------------
 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 15.2  (amd64 / qemux86-64)
 Home Assistant Core: 2025.5.3
 Home Assistant Supervisor: 2025.05.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
[01:28:04] INFO: Flashing firmware is disabled
s6-rc: info: service universal-silabs-flasher successfully started
[01:28:04] INFO: Starting socat TCP client for OTBR daemon...
2025/06/11 01:28:04 socat[186] W recvmsg(): Resource temporarily unavailable
2025/06/11 01:28:04 socat[186] E connect(7, AF=2 192.168.68.197:6638, 16): Connection refused
[01:28:05] INFO: Starting socat TCP client for OTBR daemon...
2025/06/11 01:28:05 socat[200] W recvmsg(): Resource temporarily unavailable
2025/06/11 01:28:05 socat[200] E connect(7, AF=2 192.168.68.197:6638, 16): Connection refused
[01:28:06] INFO: Starting socat TCP client for OTBR daemon...
2025/06/11 01:28:06 socat[214] W recvmsg(): Resource temporarily unavailable
2025/06/11 01:28:06 socat[214] E connect(7, AF=2 192.168.68.197:6638, 16): Connection refused

I don’t use a device like this, but just looking at your first set of logs, I don’t see anything particularly wrong. OTBR just happens to have a fair number of errors, even when working properly.

This part looks a little unusual to me, as usually the RADIO_URL is a path to /dev (usb device) or a IP address (network device).

It would help to know what is working, and what isn’t? Does your border router show up in the Thread Integration CONFIGURE page? If so, does it have the three-dot menu to reset it?

Hi,

Having similar problem starting OTBR for SLZB-MR1.
A week ago it worked. Now is not starting anymore.

[18:59:41] INFO: The otbr-web is disabled.
[18:59:42] 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 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
[18:59:42] INFO: Starting mDNS Responder...
Default: mDNSResponder (Engineering Build) (Jan 14 2025 21:08:25) starting
[18:59:43] INFO: Starting socat TCP client for OTBR daemon...
-----------------------------------------------------------
s6-rc: info: service socat-otbr-tcp successfully started
 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 15.2  (aarch64 / green)
 Home Assistant Core: 2025.6.1
 Home Assistant Supervisor: 2025.05.5
-----------------------------------------------------------
 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
[18:59:47] INFO: Flashing firmware is disabled
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service otbr-agent: starting
[18:59:50] INFO: Setup OTBR firewall...
[18:59:51] 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://end0
[NOTE]-ILS-----: Infra link selected: end0
[INFO]-RCP_HOS-: OpenThread log level changed to 5
tiocmbic: Inappropriate ioctl for device
50d.15:10:31.596 [D] P-SpinelDrive-: Sent spinel frame, flg:0x2, iid:0, tid:0, cmd:RESET
50d.15:10:31.596 [D] P-SpinelDrive-: Waiting response: key=0
50d.15:10:33.598 [W] P-SpinelDrive-: Wait for response timeout
50d.15:10:33.598 [I] P-SpinelDrive-: co-processor self reset successfully
50d.15:10:33.598 [D] P-SpinelDrive-: Sent spinel frame, flg:0x2, iid:0, tid:1, cmd:PROP_VALUE_GET, key:PROTOCOL_VERSION
50d.15:10:33.598 [D] P-SpinelDrive-: Waiting response: key=1
50d.15:10:35.600 [W] P-SpinelDrive-: Wait for response timeout
50d.15:10:35.601 [D] P-SpinelDrive-: Sent spinel frame, flg:0x2, iid:0, tid:1, cmd:PROP_VALUE_GET, key:PROTOCOL_VERSION
50d.15:10:35.601 [D] P-SpinelDrive-: Waiting response: key=1
50d.15:10:37.603 [W] P-SpinelDrive-: Wait for response timeout
50d.15:10:37.603 [C] Platform------: Init() at spinel_driver.cpp:83: Failure
50d.15:10:37.603 [D] P-SpinelDrive-: Sent spinel frame, flg:0x2, iid:0, tid:1, cmd:PROP_VALUE_GET, key:PROTOCOL_VERSION
50d.15:10:37.603 [D] P-SpinelDrive-: Waiting response: key=1
50d.15:10:39.605 [W] P-SpinelDrive-: Wait for response timeout
[18:59: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            
[19:00:00] 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 socat-otbr-tcp: stopping
s6-rc: info: service mdns: stopping
2025/06/14 19:00:00 socat[76] W exiting on signal 15
/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 successfully stopped
Default: mDNSResponder (Engineering Build) (Jan 14 2025 21:08:25) stopping
s6-rc: info: service banner: stopping
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 banner successfully stopped
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
[19:00:00] INFO: mDNS ended with exit code 4 (signal 0)...
s6-rc: info: service mdns successfully stopped

Kind Regards,
Martin