SLZB-06 problems with zigbee2MQTT?

[u/Beginning_Storage_35]

Hi all,

I’m running into a strange issue with my SLZB‑06. I used to run Zigbee2MQTT on my SLZB‑MR3 (now: ZHA + Matter) without any problems. Recently I moved Z2M back to my SLZB‑06, but now I consistently get Zigbee Herdsman errors during initialization.

Same host, same Z2M version, same config. The only change is switching the coordinator from the MR3 back to the SLZB‑06. Changed configuration aswell.

Before I start digging deeper: is the SLZB‑06 known to have compatibility issues with Zigbee2MQTT, or are there specific things I should check (firmware version, adapter settings, baud rate, etc.)? I use both slzb trough Ethernet.

Any insights or similar experiences would be really helpful.

Thanks in advanced.

[u/Running_Marc_nl]

No issues for me. Been running the slzb-06 rocksollid with z2m for a couple years.

[u/tvoided → u/Running_Marc_nl]

Which firmware for os and zigbee you use ?

[u/Beginning_Storage_35 → u/tvoided]

For me all the latest.

[u/heosmeuekdheidm]

sometimes i need to powercycle the adapter, shows in the logs exactly like your problem.

happens especially when i restart z2m

[u/Beginning_Storage_35 → u/heosmeuekdheidm]

Powercycle the adapter? You mean remove power supply and reconnect it? If so, that is the solution I am doing now. Playing with the idea to add a powerplug to the power adapter.

But was hoping for a more stable solution.

[u/heosmeuekdheidm → u/Beginning_Storage_35]

yeah

im using mine with poe so I can remotely shut it off via the switch webinterface

[u/GVDub2 → u/Beginning_Storage_35]

You should be able to reboot from the WebUI for the SL-ZB06. Sometimes firmware update will knock Z2M offline until you reboot, or such has been my experience.

[u/Mandrutz]

Probably the configuration is wrong. Otherwise follow the link in the error message. 

[u/Beginning_Storage_35 → u/Mandrutz]

Ow thanks. Missed that link.

[u/Early_Mongoose_8758]

I uad this where the app wouldnt start. Mine is on a VM so I have to tell the vertual machine not to pass through the usb save it then pass it through again. I can then boot the app.

For me this only happens on HA updates

Unsure how you pass the data through on ethernet but assume you do. So maybe just try unpacking it then passing it again.

[u/ginandbaconFU → u/Early_Mongoose_8758]

You just point it to the IP and port under serial like below instead of the zigbee USB adapter. Unless you have a complicated VLAN setup with complicated rules of what can talk to what then there should be zero issues. Key word being should

tcp://192.168.0.22:6638

[u/Early_Mongoose_8758 → u/ginandbaconFU]

Not sure how hes got his network set up but yes being ethernet he could be blocking it with a rule there for not allowing the app to boot as it cant see the adapter.

[u/hotapple002]

Mine is rock solid. Logs also clearly state the issue (ping that gets no response after 6000 ms).

As that points to a network issue you should start with restarting adapter and Z2M. After that look further into network issues.

[u/funkystay]

Double-check the IP address of the new coordinator.

[u/proxyerror101]

I had this error and corrected it by updating the IP address in the configuration. This is also when I discovered the current Motorola router issues lol.

[u/ginandbaconFU]

What's your config look like in yaml for Z2M. Should be similar to the below with different username/password. Both the person/user needs to exist, just limit to local access only.

data_path: /config/zigbee2mqtt socat: enabled: false master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777 slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5 options: -d -d log: false mqtt: server: mqtt://core-mosquitto:1883 user: auser password: apassword base_topic: zigbee2mqtt serial: port: tcp://192.168.0.22:6638 baudrate: 115200 adapter: zstack rtscts: false force_onboarding: false

[u/Shute789]

Make sure you’re not at one of the beta firmware’s. The current active firmware is actually kinda old at this point (2025 I think?), but I accidentally got put on one of the beta or Dev upgrade list by mistake and that was really giving me a lot of issues with herdsman

[u/Beginning_Storage_35 → u/Shute789]

I am (as far as I know) not on the beta. Saw the beta for the slzb but decided not to install it.

[u/i_jon_h]

Are you able to access the SLZB web UI? I eventually realised mine was on a recent beta zigbee coordinator firmware that caused compatibility issues with Z2M. Rolled back to the most recent stable release and haven’t had a problem since.

[u/Beginning_Storage_35 → u/i_jon_h]

I am only when it works. As soon as I have that herdsman problem. I can not access the web ui

I will extra check this. Someone else suggested that aswell

[u/kevdogger]

Is z2m service up and running without any issue?

[u/Beginning_Storage_35 → u/kevdogger]

No. The app gives the error msg.

[u/kevdogger → u/Beginning_Storage_35]

Are you using z2m add on within HA or running independent installation?

[u/SnooOranges9983]

I was need to stop using Smlight buggy products. I was need move to other coordinator from there stick. After 8 months of testing there continious bugs.

[u/Agile_Nectarine4109]

same for me.. tryed every type of configuration.

web ui accessible zigbee2mqtt has herdmann error (no response for ping after 60000)

only solution for me was to powercycle OR schedule an automation with zigbee restart in homeassistant..

SLZB06 was rock solid even in direct zigbee until Homeassistant moved to 2026 release.

[u/wonderedwonderer]

I had a similar problem when I did a backup restore. What I ended up doing was restarting everything from scratch, recreating my VM and installing HAOS again. Once it's set, it's been rock solid. Be sure not to use any of the dev firmwares too.

[u/route66por]

I had a lot of problems with new firmwares, so i downgraded to the last official firmware. Had to pair everything but the errors stopped there. No beta / dev firmware again.