Recently purchased SLZB-MR4 - trying to connect Matter-over-Thread to HA

Recently purchased an SMLight SLZB-MR4, set the SL radio to Matter-over-Thread, and the TI radio to ZigBee. Connected the SLZB-MR4 to my IoT VLAN via PoE (so not using USB - lets me position it anywhere I have a network port).

Installed Zigbee2MQTT, MQTT broker, and got ZigBee going without issues. I installed Thread and tried to install OpenThread Broker integration, but when I give it http URL of static IP and port of Matter-Over-Thread as shown by SLZB-MR4 web interface, it times out with an error…

Any ideas? Z2M’s working fine with Zigbee Coordinator.
HA can also detect the SLZB-MR4 itself and show its status (though I currently disabled this bit - have tried with it enabled and disabled - thought enabled maaaaybe it was holding session from MoT?).

SLZB-MR4 reports that it’s up to date, firmware wise.

Can you expand on where specifically you are trying to enter the IP and port combination?

As I understand it, you have to install the OTBR add-on separately, and then pass it your radio. You can then configure the Thread integration in Home Assistant to communicate with this OTBR instance.

A guide I found: Connecting Matter-over-Thread Device to Home Assistant | SLZB-06 * Series Manual

Hey @cadmium ,

I tried the following steps:

  1. HomeAssistant Hamburger menu
  2. Devices and Services screen
  3. Add Integration button
  4. Open Thread Border Router
    … at this point it launches a wizard
    Prompted for API URL: “Provide URL for OpenThread Border Router’s REST API”
  5. I provided http://192.168…:6638
  6. Dialog comes back with “Failed to connect”

The problem with the instructions provided in the smlight link you’ve provided, is that it seems rather than giving me access to configuration screens indicated, it launches a wizard which only gives me option to provide a URL.

Would you be able to explain what your current understanding of what the instructions are asking you to do, is?

As you have mentioned, the prompt is asking for the “OpenThread Border Router’s REST API” URL - have you deployed openthread border router? The instructions I linked above walk you through on how to do that.

The URL you are providing (http://...:6638) is not the OTBR URL.

I have the exact same issue (although with a Sonoff Dongle Max with the Thread RCP Mode firmware which I am trying to connect via PoE).

I wonder if our issue is not related to this discussion?
https://github.com/home-assistant/core/issues/153092

In any event, it if far from clear from the instruction at the SMLight site provided by @cadmium whether one needs to install a separate OBTR instance which the HomeAssistant integration would connect to. If

" The URL you are providing (http://...:6638 ) is not the OTBR URL."

because the dongle is only the Radio Co-Processor, then one needs to install a full OBTR instance in parallel to HA?

The prompt is the first and only option I get when trying to add the integration on my Home Assistant Container :

Or am I missing the plot?

So in HA, an integration is separate to an add-on.

Integrations are installed into Home Assistant itself; the open thread border router integration expects a URL to an open thread border router server.

An add-on is a separate app that spins up as a container, adjacent to your HA installation. The URL that the integration is asking for is the connection to the add-on.

That’s right. The OTBR add-on (the actual border router software) will ask you to provide the details of the radio it will use. Once you have that running, you can pass the details of the add-on to the integration.

This is helpful. Thanks for the quick response! And quite logically, if not explicit in the Sonoff and HA docs, that the functional scope of an Add-on and an integration with the same name were completely different.

So no Add-ons for me on a container install, so I have to weight the hassle of a) running a separate container for Docker Install  |  OpenThread b) moving everything to HAOS in a KWM on my current Pi 5, or c) running HAOS on a spare Pi 4 I have lying around somewhere.

a) may be simpler in the long run?

I think that’s fair enough - though, I do think that the website that I linked does spell it out quite clearly; however, I don’t blame you if you glossed over it and thought it referenced an integration instead.

Out of all the options you posted, I think just running the container is the easiest and least hassle :slightly_smiling_face: it’s well worth getting used to running extra containers so you become more aware of the moving parts required for your setup (and there will be more containers you have to run down the line anyway)

I can’t vouch for this one specifically (as it is the result of a cursory search), but there are a multitude of options out there to try make it easier to run the container: GitHub - ownbee/hass-otbr-docker: Stand-alone Home Assistant OpenThread Border Router docker container.

I wish you the best of luck :sparkler:

1 Like

Ahhhhhhhh… now it makes sense… thanks, all! Indeed, Add-on vs. Integration.