SMLIGHT SLZB-MR1 configured as router won’t connect to Zigbee network

Hi everyone,

I’m struggling to connect an SMLIGHT SLZB-MR1, configured as a router, to my existing Zigbee network managed by another SLZB-MR1 set up as coordinator.

My current setup:

  • Coordinator: 1x SMLIGHT SLZB-MR1 working flawlessly, managing several Zigbee sensors.
  • Router: 1x additional SMLIGHT SLZB-MR1 configured specifically as a router. Unfortunately, I haven’t managed to make it join my existing network.

What I’ve tried so far without success:

  • Factory resetting the router device multiple times.
  • Attempting pairing while placing the router very close to the coordinator.
  • Ensuring both devices have up-to-date firmware.
  • Checking logs in ZHA — the router doesn’t even show up during the pairing attempts.

Has anyone had success or encountered similar issues setting up an SLZB-MR1 as a Zigbee router?

Any guidance or tips would be greatly appreciated.

Thanks in advance!

I had it working as a router. I’m using the sky connect dongle as the coordinator. I added the slzb device and it was working for a few weeks. Redid my entire network. New router, APs, everything. Now I can’t get it connect. Thread connects. Still working on the Zigbee side but I have a lot of devices to repair now so I’ll get to it soon. Hopefully someone will post an answer. But I can confirm that it does operate properly as a router.

I have the same issue.

Coordinator is the SLZB-06P7 and want to add the SLZB-MR1 as a router.
Nothing happens.

Did you get any further?

The SLZB-MR1 has a TI CC2652P7 + SiLabs EFR32MG2. What did you use as router ?

I used the CC2652P7 as a router. Firmware: 20240716

I wanted to use the EFR32MG2 for Matter with firmware: 20241105

You can try 20250403, should pair immediately after flashing

The latest firmware in the web interface is 20250325.
That does not work either.

I am trying to figure out, where I can get the 20250403 from.
When I download from the releases, I just get a hex file instead of a binary.

Do I need to compile that myself or am I missing something?

I always flash the hex file

If I try the hex it says:

Firmware file format is not supported

I am trying to flash the 20250403 hex file to the mr1 running slzb-os without sucess.

I am using linux.
I tried building the bin file with objcopy or python's IntelHex module and both error with Firmware file format is not supported.

I tried to flash directly (usb mode to cc2652p7 and the zigbee flash mode) using cc2538_bsl, and while it reports a successful flash and verified, the slzb-os ui still shows 20250325.

The issue that I have is that the mr1 in router mode does not join an existing zigbee network (z2m does not report a new device type router joining).

Anyone has experienced something similar?

Got the same issue, SLZB-MR4U router won’t join network hosted by second SLZB-MR4U coordinator

Setup:

  • 2x SLZB-MR4U (CC2674P10 + EFR32MG26)
  • Coordinator unit CC2674P10 in “Zigbee Coordinator” mode, radio firmware 20260311, connected to zigbee2mqtt 2.13.0 over TCP
  • Router unit CC2674P10 in “Zigbee Router” mode, radio firmware 20250325
  • SLZB-OS firmware: v3.3.1

The router never joins the network hosted by the coordinator, despite:

  • Permit join enabled on the coordinator (confirmed via zigbee2mqtt debug logs and tried with other devices)
  • “Router reconnect” clicked multiple times on the router’s SLZB-OS UI
  • A full physical power-cycle of the router unit
  • Tried across two different router radio firmware versions (20240716 and 20250325)

In every case, zigbee2mqtt’s debug-level logs show zero incoming RF traffic from the routern No join request, no interview, nothing, even though other existing devices on the same network report normally in the same logs. The router’s own SLZB-OS system log shows the “Router reconnect” API call being received and processed, but nothing beyond that.

Apparently, complaining about it on the internet helps. After leaving my network alone for an hour, I tried again, and this time the router paired without any problems. So, never mind :sweat_smile: