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?
After each Core update, OTBR drops down, and could not be started.
After reflashing again with the only available firmware, it works again.
Not exactly reassuring…
To be honest I have no idea if my problem is related, but i have same issues. Thread worked for a day and now I can’t start OTBR in HA because I get this in log:
Tried to restart, reflash (that didnt work at first but i could flash the same Firmware today) and still can’t start OTBR.
Edit.
Powered down and up after the flash, turned ON then OFF Hardware flow and then restarted HA machine, and now it works, not a great device…
I’m also running a SLZB-MR1 setup, I also have to powercycle (POE restart) the radio after each FW update.
But in general, I find the Thread/Matter network really unstable. I have small appartment with a few devices:
5x Tado X thermostatic valves
1x IKEA ALPSTUGA
The connection drops randomly, and I still can’t figure out what fixes it, I restart OTBR and matter integration in HA, the radio sometimes the only thing that works is to re-pair the thermostats.
i am trying since 5h to get matter over thread running on my mr1-u
its just not working. docker is running via orbstack/docker
what works:
Stable Communication: The otbr-agent is successfully communicating with the EFR32 radio over the network (tcp://xxx:6638).
Hardware Parameters: Baud rate is stable at 460800. Flow control is OFF.
IPv6 Enabled: The SLZB-MR1U hardware now has IPv6 enabled in its network settings, which is mandatory for Thread.
mDNS Visibility (Native Proxy): A native macOS mDNS proxy is running on the host Mac to broadcast the _meshcop._udp service for OpenThread-7eae.
Home Assistant Alignment: The thread.datasets storage in HA has been patched to match the mobile app’s preferred network (Channel 20).
and this does not work:
Radio “Detached” State: The radio currently refuses to promote itself to “Leader” on the 7eae network. It is “hearing” beacons from neighbors (specifically a neighbor on Channel 11 with PAN 0x83d5) but is not forming its own partition.
OrbStack Network Isolation: Docker’s host mode on macOS is virtualized. The container advertises its internal bridge IP , which is unreachable for the phone. This is currently bypassed by the native dns-sd proxy on the Mac host.
Radio Resets: We observed several 0x301 (PIN) - Power-on Reset events. This could indicate either power instability in the MR1U or a crash in the radio firmware when hitting high traffic.
its a mystery for me.
some finding:
TREL Loop: Disabling the TREL (Thread Radio Encapsulation Link) was necessary to stop an infinite mDNS registration loop that was flooding the logs.
Channel Selection: Channel 11 is extremely busy in this environment. We attempted to move to Channel 20/26 to find “airtime” for the commissioning process.
Matter Hub Conflict: The user has an existing Matter/Thread network (likely Google/Nest). This network sends beacons that the MR1U “hears,” which might be preventing it from starting its own network to avoid interference.
I’m having similar challenges. I have HAOS on a Raspberry PI 4 and have the issue where I can’t expose any dummy serial ports, so I have the SLZB-MR1 connected to my network and then also directly to the Pi via USB.
I have migrated a mix of Ikea and Aqara Zigbee devices to the Zigbee radio (EFR32MG21) and that’s working really well.
However, I can’t seem to get the Matter-Over-Thread radio (CC2652P7) to be detected consistently when connected via USB and I’ve tried a number of things to get a dummy TTY to be enabled, but with no luck. (Editing config.txt and userconfig.txt)
I don’t have any other devices I could plug into the Pi (yet) to spoof the TTY, but I’m willing to buy something. The location of my Pi is not optimal for coverage by the SLZB if I have to have it plugged into the Pi with USB.
