SLZB-06 stopped working - HELP!

Suddenly a stable and working HA system has stopped being able to see/use my SLZB-06.
It claims it can’t ping it, but I can ping it from HA SSH UI and my PC.

There is mention of a new version of firmware for the SLZB and I’ve tried it and reverted without effect. I’ve restore a HA full backup to prior to the problem, no effect.

Anyone any ideas?
Running HA 2025.7.3 (also tried 2025.8.2)
Running SLZB 2.8.7 (tried 2.9.8 and reverted)

zigbee2mqtt log says this…

[17:15:46] INFO: Preparing to start…
[17:15:46] INFO: Socat not enabled
[17:15:47] INFO: Starting Zigbee2MQTT…
Starting Zigbee2MQTT without watchdog.
[2025-08-19 17:15:53] info: z2m: Logging to console, file (filename: log.log)
[2025-08-19 17:15:53] info: z2m: Starting Zigbee2MQTT version 2.6.0 (commit #unknown)
[2025-08-19 17:15:53] info: z2m: Starting zigbee-herdsman (5.0.4)
[2025-08-19 17:15:53] info: zh:zstack:znp: Opening TCP socket with 192.168.0.53:6638
[2025-08-19 17:15:53] info: zh:zstack:znp: Socket connected
[2025-08-19 17:15:53] info: zh:zstack:znp: Socket ready
[2025-08-19 17:15:53] info: zh:zstack:znp: Writing CC2530/CC2531 skip bootloader payload
[2025-08-19 17:15:54] info: zh:zstack:znp: Skip bootloader for CC2652/CC1352
[2025-08-19 17:16:13] error: z2m: Error while starting zigbee-herdsman
[2025-08-19 17:16:13] error: z2m: Failed to start zigbee-herdsman
[2025-08-19 17:16:13] error: z2m: Check Zigbee2MQTT fails to start/crashes runtime | Zigbee2MQTT for possible solutions
[2025-08-19 17:16:13] error: z2m: Exiting…
[2025-08-19 17:16:13] error: z2m: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
at ZStackAdapter.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:114:27)
at Controller.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/controller.ts:134:29)
at Zigbee.start (/app/lib/zigbee.ts:67:27)
at Controller.start (/app/lib/controller.ts:101:13)
at start (/app/index.js:149:5)

Can you access the SLZB-06 via SLZB-06/ or the device IP?

http://192.168.xx.xx

Yes, no problem accessing its ui via its static ip.

This is SMLIGHT’s OS :arrow_up:

What firmware is active for the SLZB? It’s listed in the Dashboard

Should look be similar to this current firmware revision: 20250325

It’s connecting to the device so check your broker log too

Silly question, did you try physically powering down the SLZB stick and powering it back up?

You radio firmware is the issue. Try re-flashing via the SLZB UI under Setting and Tools / Firmware Update

Select the menu with CC2652P

Ok, so i gone back to the latest 2.9.8 to start with as this seems mandatory to do anything else. Then done the update and it shows…


However, no change in HA, zigbee2mqtt still shows the same log errors.
Thanks for your ongoing help.

Progress for sure. The device is online but HA isn’t communicating with the dongle.

A few more questions:

What install method are you using?

An Example

  • Installation method Home Assistant OS
  • Core 2025.8.2
  • Supervisor 2025.08.1
  • Operating System 16.1
  • Frontend 20250811.0

After the SLBZ update, did you reboot the system( not the restart option)?

So, the slzb is connected to my router powered by poe not dongling off pi.
I have rebooted the pi not just restarted ha.
Current pi config is…

Is your Z2M Serial config set to:

baudrate: 115200
adapter: zstack

Yes

1000015071|281x500

I’m in OZ and its bed time for me, thanks so much for your efforts.

I hope you find an inspirational solution for me !

I am too, review this Zigbee2MQTT fails to start/crashes runtime | Zigbee2MQTT

Feel free to DM me tomorrow to work through this. We will figure this out!

Hi again

I can’t see anything helpful in this big list, the ping item makes no sense since I can ping the ip of the slzb-06 from pi or pc

Should coordinator be ‘installed’ ?

Yes sir! That is probably the source of your issues

The router option is for ZigBee networks with multiple dongles. You can only have one main coordinator unless you make changes explained here :arrow_down:

Ok, so I have picked the most recent version not indicated to mess with the pan-id.
It installed fine.

A reboot and we are back in action.

I wonder what happened?

Thank you so much for your help.

1 Like

Not the first time I have seen that settings on the SLZB have changed after an update of the ESP32 firmware.