SLZB-MR1 with Gladys

[prohand]

Good evening everyone,

As promised, here’s a short feedback regarding the integration of the SLZB-MR1.
I received it today and I’ve just finished integrating it

My config before upgrade :

1 * Gladys virtual machine on a Proxmox server
1 * MQTT virtual machine on a Proxmox server
1 * Zigbee2mqtt virtual machine version 1.42.0 on a Proxmox server
1 * ZBDongle-P dongle with CC2652P radio plugged directly into the Proxmox server

My config after upgrade :

1 * Gladys virtual machine on a Proxmox server
1 * MQTT virtual machine on a Proxmox server
1 * Zigbee2mqtt virtual machine on a Proxmox server
1 * SLZB-MR1 dongle with CC2652P7 radio for Zigbee connected over the network

Small points of attention :

1. Not having a PoE switch, I had to power the SLZB-MR1 via its USB-C port which I plugged into one of the Proxmox server’s USB ports.
   I’ll see later if I can do the power differently but for the moment this suits me
   Note: The USB cable is not included in the box

2. Gladys is currently not compatible with network connection but only in USB mode.
   So you simply need to plug the USB like your old dongle and check the USB Connection box instead of Ethernet Connection:

Migration

For my part, having an external Zigbee2Mqtt and MQTT, I first configured the network part of the SLZB-MR1 and then performed the SLZB OS update as recommended in the Domo-Blog article, which I thank for the write-up

Test du contrôleur Smlight multi radio SLZB-MR1 Matter et Zigbee, EFR32 et...

So on my side it looks like this:

I will look into whether it’s worth changing the Core version to v2.8.7 as well as the CC2652P7 version, but there seem to be issues with the latest CC2652P7 versions. (zigbee coordinator 20250325 update on slzb-06 broke my entire network · Issue #27560 · Koenkk/zigbee2mqtt · GitHub).
By the way, if anyone has info on stable versions, I’m interested

Regarding the migration, I simply had to unplug the ZBDongle-P from my Proxmox server and remove the USB configuration from the virtual machine.

I then modified the configuration.yaml file to include the following:

serial:
# Location of SLZB-MR1
  port: tcp://xx.xx.xx.xx:7638
  baudrate: 460800
  adapter: zstack
# Disable the green LED?
  disable_led: false
# Set the output power to 20 maximum
advanced:
  transmit_power: 20

You can see it directly in the web interface:

Of course replace xx.xx.xx.xx with the IP of your controller.

I then restarted my Zigbee2Mqtt docker and checked that I had no errors in docker.
I encountered no issues; otherwise I invite you to check the Domo-Blog article which indicates steps to take in case of problems.

Once Zigbee2Mqtt was accessible I saw a module reappear by itself.
For some modules, I had to wake them up to see them appear online again.
I saw quite a few modules reappear when I cut and restored power to mains-powered modules.
I would surely have been more patient, the modules would certainly have come back online without my actions, but I was impatient

Tips

I was able to set up a login/password on the web interface

Bug

So far only one small bug encountered: the web interface login/password is requested fairly often.
We’ll see if the problem is resolved by upgrading to 2.8.7

If you have any questions, don’t hesitate

[mutmut]

Thanks @prohand for this great feedback!

I see that you have a CC2652P chipset in both cases which allows you not to have to re-pair everything during the switch (my case at the time of my change from Conbee II to SLZB-06M).

I updated to 2.8.7 recently and no issues so far, I was on 2.8.4dev12 just before.
As for the password, I had enabled it at one point but removed it afterwards, and I don’t recall your bug. Besides, you don’t go on the SLZB every day

For the POE injector, you can take the one from SMLIGHT which is not expensive at all (while waiting for a POE switch if you upgrade your infra).

And we’re looking forward to your feedback with Matter-over-Thread

[prohand]

I’ll see about upgrading to 2.8.7 then

On the CC2652P side, which firmware are you on?

About the PoE injector, I saw it and thanks for the info I just need to free up an outlet on my power strip

Indeed, as for the password issue, it’s not a bothersome bug

Regarding Matter-over-Thread, it won’t be for a while, but I’ll keep you informed of course

[mutmut]

@prohand

On the CC2652P side, which firmware are you on?

I’m using an EFR32MG21 chipset with firmware 20250220, I don’t have a CC2652P on the SLZB-06M.

[prohand]

Thanks for the feedback

I just upgraded to v2.8.7 :

To fix the temperature issue (see my 1st post where you can see temperatures above 80°C) I had to perform a temperature calibration :

[prohand]

For your information I have just upgraded Z2M to version 2.3.0: (See: [Z2M] Tests en zigbee2mqtt 1.42.0 > 2.1.3 >..> 2.4.0 >..> 2.6.1 - #5 par prohand )

And CC2652P7 is on version 20240710, which appears to be the latest stable version:

Releases · Koenkk/Z-Stack-firmware

And which is also included in the download link in the Z2M documentation:

I will report back on the stability within a few days

[prohand]

I upgraded to 2.4.0 on Z2M with this key without any problems

[prohand]

Core updated to 2.9.2 without issues:

[prohand]

Core updated to 2.9.4 without any problems :

[prohand]

I upgraded to 2.6.0 on Z2M without any problem using this key
I also configured the new interface

If I have any problems I’ll let you know

[prohand]

I switched to 2.6.1 on Z2M without any problem with this key

If I have any problems I’ll give you feedback

[pierre-gilles]

I submitted a PR to update the native Gladys Zigbee2mqtt installation to 2.6.1:

Upgrade Zigbee2mqtt to 2.6.1

Tested on my setup, it works perfectly
I’ll keep it for several days and if all is good, release next week!

@prohand have you tested the new « Windfront » interface? Starting in October it will be the default frontend

[prohand]

Yes, I tested it and it works pretty well.
Except when updating devices, the progress bar doesn’t appear even though the update starts properly; I haven’t encountered any other problems

[prohand]

I upgraded to 2.6.2 on Z2M without any problems using this key

If I have any problems I’ll let you know

[prohand]

Core update to 2.9.8 without issues I had to do the update manually by downloading the file.

I did not update to 3.0.6 given the issues reported on Reddit:

https://www.reddit.com/r/homeassistant/comments/1ns2n44/warning_slzb_306_firmware_seems_to_have_a_bug/?tl=fr

[mutmut]

I’ve been on 3.0.6 on my SLZB-06M for 9 days and haven’t had any operational issues.

However, it seems that mDNS no longer works for me even though it’s still enabled in the UI — something to keep an eye on with the next update.

[l.dolle]

Hello @prohand

Why didn’t you install it on the network? That’s actually the big advantage of this product. You can place it wherever you want on your network.

I placed mine on the network and it works very well.

However, I’ll probably have some questions to ask you about Proxmox, but I’ll open another thread.

[prohand]

@prohand

1 * dongle SLZB-MR1 with radio based on CC2652P7 for Zigbee connected to the network

Hello,

As stated in my 1st post it is indeed connected to the network

No problem with your other questions about Proxmox

[l.dolle]

Sorry. I must have misinterpreted point 2 of your first post.

[prohand]

No worries