OpenThread Border Router Matter over Thread true USB connection SLZB-06

Configuration Matter/Thread
1

I have bought the SLZB-06 to be my new thread border router for Aqara devices (Aqara G4 doorbell & Aqara Doorlock U200).

I have connected the SLZB-06 with LAN and a USB directly connection with my Raspberry Pi 5 with HA core 2025.2.5 and operating system 14.1. Supervisor 2025.02.4

The control panel SLZB OS I have set the Mode to: Matter-over-Thread (beta).
And the connection mode to: USB connection
The firmware version: 20240727 v2.8.1.dev9

I have installed the add-on OpenThread Border Router but in the config the SLZB-06 is not recognized.
I have rebooted home assistant already a few times.

How can I get this to work?

2

First, you need to make sure that the device is recognized by the system. Settings - System - Equipment - All equipment button

3

Thanks!

I have found my other Sonoff_Zigbee_3.0_USB_Dongle, in the Settings > System > Equipment > All Equipment, but I can’t find the SLZB-06.
What do I need to do to recognize this device?

4

When connected via USB, it should be detected automatically, if this does not happen, unfortunately, I do not know what to do. Only banal things about the lack of power for the device come to mind. If via the Internet, then you need to register the interface address in the OpenThread Border Router add-on, by default this setting is hidden

1 Like
5

I have connected the device to the HA directly true usb. It’s now findable. But I get this error:

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 (aarch64 / raspberrypi5-64)
Home Assistant Core: 2025.3.0
Home Assistant Supervisor: 2025.03.2

I Get this message:

s6-rc: info: service banner successfully started
s6-rc: info: service universal-silabs-flasher: starting
[16:59:35] INFO: The selected serial port is not a USB device.
[16:59:35] WARNING: No firmware found for the selected device, assuming firmware is installed.
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service otbr-agent: starting
[16:59:35] INFO: Setup OTBR firewall…
[16:59:36] 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/ttyAMA10?uart-baudrate=460800&uart-flow-control
[NOTE]-AGENT—: Radio URL: trel://end0
[NOTE]-ILS-----: Infra link selected: end0
49d.17:59:02.453 [W] P-SpinelDrive-: Wait for response timeout
49d.17:59:04.455 [W] P-SpinelDrive-: Wait for response timeout
49d.17:59:06.457 [W] P-SpinelDrive-: Wait for response timeout
49d.17:59:06.457 [C] Platform------: Init() at spinel_driver.cpp:83: Failure
49d.17:59:08.460 [W] P-SpinelDrive-: Wait for response timeout
[16:59:45] 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
[16:59:45] 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.
s6-rc: info: service universal-silabs-flasher successfully stopped
s6-rc: info: service banner: stopping
Default: mDNSResponder (Engineering Build) (Jan 14 2025 21:08:25) 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
[16:59:45] INFO: mDNS ended with exit code 4 (signal 0)…
s6-rc: info: service mdns successfully stopped

1 Like
6

Turn off the “automatically flash firmware” option in the add-on. The SLZB-06 should be flashed via its own UI.

7

Interestingly enough, mine has started having similar issues…