failed to start zigbee-herdsman with remote smlight slzb-06 - hardware issue?

[alesti]

Hi,

i run homeassistant with two zigbee integrations, one in the main house with zha (on a ha yellow hardware onbord adapter) and one remote in a different building with z2m and smlight slzb-06 with some devices which are not reachable from zha.
That worked since 4 months now flawlessly.

Since today the z2m integration does not start anymore with:

[11:20:50] INFO: Preparing to start...
[11:20:50] INFO: Socat not enabled
[11:20:50] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2026-03-12 11:20:51] info: 	z2m: Logging to console, file (filename: log.log)
[2026-03-12 11:20:52] info: 	z2m: Starting Zigbee2MQTT version 2.9.1 (commit #unknown)
[2026-03-12 11:20:52] info: 	z2m: Starting zigbee-herdsman (9.0.9)
[2026-03-12 11:20:52] info: 	zh:zstack:znp: Opening TCP socket with 192.168.1.13:6638
[2026-03-12 11:20:52] info: 	zh:zstack:znp: Socket connected
[2026-03-12 11:20:52] info: 	zh:zstack:znp: Socket ready
[2026-03-12 11:20:52] info: 	zh:zstack:znp: Writing CC2530/CC2531 skip bootloader payload
[2026-03-12 11:20:53] info: 	zh:zstack:znp: Skip bootloader for CC2652/CC1352
[2026-03-12 11:21:11] error: 	z2m: Error while starting zigbee-herdsman
[2026-03-12 11:21:11] error: 	z2m: Failed to start zigbee-herdsman
[2026-03-12 11:21:11] error: 	z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[2026-03-12 11:21:11] error: 	z2m: Exiting...
[2026-03-12 11:21:11] error: 	z2m: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
    at ZStackAdapter.start (/app/node_modules/.pnpm/zigbee-herdsman@9.0.9/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:107:27)
    at Controller.start (/app/node_modules/.pnpm/zigbee-herdsman@9.0.9/node_modules/zigbee-herdsman/src/controller/controller.ts:145:29)
    at Zigbee.start (/app/lib/zigbee.ts:70:27)
    at Controller.start (/app/lib/controller.ts:111:29)
    at start (/app/index.js:156:5)

Versions (and last updates)

• z2m 2.9.1-1 (last week, i do updates if they appear, but i'm pretty sure i did nothing yesterday or today)
• HA Core 2026.3.1 (also some days running)

The slzb-06 runs on poe. I rebooted it, i rebooted the switch which is the poe source. Port 6638 is reachable.
I read the z2m fails to start runtime faq.

This thing is based on cc2652, but I flashed it to v3.2.4 (latest non dev release) from https://smlight.tech/flasher/#SLZB-06 (for good messure), and the log (after the flashing which went fine) looks like there is an hardware issue with its filesystem:

[01.01.1970 00:00:00] setup | Starting firmware: v3.2.4
[01.01.1970 00:00:00] getDevType | using SLZB
E (19) esp_littlefs: ./managed_components/joltwallet__littlefs/src/littlefs/lfs.c:1382:error: Corrupted dir pair at {0x0, 0x1}

E (26) esp_littlefs: mount failed,  (-84)
E (30) esp_littlefs: Failed to initialize LittleFS
[01.01.1970 00:00:00] setup | FS mounted
[01.01.1970 00:00:01] ConfigHelper | load config
[01.01.1970 00:00:01] ConfigHelper | config open: InvalidInput
[01.01.1970 00:00:01] ConfigHelper | config open err
[01.01.1970 00:00:01] initConfig | Creating a new config
[01.01.1970 00:00:01] ConfigHelper | write config
[01.01.1970 00:00:01] ConfigHelper | config saved
[01.01.1970 00:00:01] ConfigHelper | load config
[01.01.1970 00:00:01] ConfigHelper | config open: Ok
[01.01.1970 00:00:01] setup | Reboot reason: POWERON
[01.01.1970 00:00:01] setup | starting ZB1 serial on: 115200 baud. HW Flow: off
[01.01.1970 00:00:01] setup | Coordinator mode: LAN
[01.01.1970 00:00:01] setup | Device: 'SLZB-06' PCB revision: 170
[01.01.1970 00:00:01] setup | Radio mode: "Unknown" Radio FW version: -1 Radio FW CH: Unknown
[01.01.1970 00:00:01] Network | init
[01.01.1970 00:00:01] taskAP | start task
[01.01.1970 00:00:02] [LEDs init] | done
[01.01.1970 00:00:02] [LEDs init] | Heap: 1236
[01.01.1970 00:00:03] Network | EVENT: 1 - ETH_START
[01.01.1970 00:00:03] Network | EVENT: 3 - ETH_CONNECTED
[01.01.1970 00:00:03] Network | ETH init: OK
[01.01.1970 00:00:03] setup | Filesystem size: 3456
[01.01.1970 00:00:03] setup | Filesystem used: 12
[01.01.1970 00:00:03] setup | SM Console started
[01.01.1970 00:00:03] setup | done
[01.01.1970 00:00:07] Network | EVENT: 5 - ETH_GOT_IP
[01.01.1970 00:00:07] Network | ETH MAC: 4C:C3:82:CE:50:EF IPv4: 192.168.1.13 GW: 192.168.1.1 Speed: 100Mbps DNS1: 192.168.1.2 DNS2: 0.0.0.0
[01.01.1970 00:00:07] Network | AP task deleted
[01.01.1970 00:00:07] Network | Network up
[01.01.1970 00:00:07] SocketServer | [CC2652P] Setup done
[01.01.1970 00:00:07] SocketServer | [CC2652P] Task started
[01.01.1970 00:00:07] SocketServer | [CC2652P] Started server on port: 6638
[01.01.1970 00:00:07] Network | [mDNS] Started
[01.01.1970 00:00:07] loadMqttConfig | config does not exist! Using defaults
[01.01.1970 00:00:07] Web | Web services init done
[01.01.1970 00:00:07] time | time sync start
[01.01.1970 00:00:07] internet | connected
[01.01.1970 02:00:08] Network | [POST] result: 200
[01.01.1970 02:00:08] stats | Statistics sent
[01.01.1970 02:00:08] stats | Heap: 3772
[12.03.2026 13:16:39] time | timezone: EET-2EEST,M3.5.0/3,M10.5.0/4
[12.03.2026 13:16:39] time | Thursday, March 12 2026 13:16:39
[12.03.2026 13:16:39] taskTimeSync | Heap: 2076
[12.03.2026 13:16:39] time | stop task
[12.03.2026 13:16:39] time | Heap: 2076
ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:4744
load:0x40078000,len:15712
load:0x40080400,len:3164
entry 0x4008059c

I have little to no experience with this type of hardware - do i need to replace the coordinator, or is there another (software) problem i do not get?

Do you need other logs, versions to get a better picture?

[alesti]

Hmm, weird.

I read more docs and found the web interface of the slzb-06 and played with it.

As it did not know the firmware version of the CC2652P but for the SLZB OS (v3.2.4 from above) i did a ota update on CC2652P to 20240710.

And now it works (again).
The radio mode in its log is now changed from "unknown" to [12.03.2026 12:44:29] setup | Radio mode: "ZB COORD" Radio FW version: 20240710 Radio FW CH: PROD (dont take the times in account, it was in GMT+3 in the first log, i fixed that to GMT).

Logs in HA Z2M looking good, i will walk it back to its natural living area.
But i am still interested in ideas to the root cause of this failure...

[milesoft]

Great bit of investigative work, I had the same issue this week. I've tried deleting and reinstalling Z2M. Ive tried corrupting the config file to make it rebuild itself. Everything and finally I read your post, reflashed the XX2652P and it works. Thank you, Thank you, Thank you.
Now just wait for it to update itself again and everything will stop working again. lol

[cnuma]

Hello

Thanks a lot for your post.
I've exactly same error and need to flash again my CC2674P10 !!!
I don't know why i need to do it but, it solved my problem ;-)
For information, i've just reflash same Revision: 20260307 !!!

lol