For some reason HA just stopped connecting to my SLZB-06P7 with the following error code:
[22:56:38] INFO: Preparing to start...
[22:56:38] INFO: Socat not enabled
[22:56:38] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2025-04-24 22:56:39] info: z2m: Logging to console, file (filename: log.log)
[2025-04-24 22:56:39] info: z2m: Starting Zigbee2MQTT version 2.2.1 (commit #unknown)
[2025-04-24 22:56:39] info: z2m: Starting zigbee-herdsman (3.4.11)
[2025-04-24 22:56:39] info: zh:zstack:znp: Opening TCP socket with 192.168.1.14:6638
[2025-04-24 22:56:39] info: zh:zstack:znp: Socket connected
[2025-04-24 22:56:39] info: zh:zstack:znp: Socket ready
[2025-04-24 22:56:39] info: zh:zstack:znp: Writing CC2530/CC2531 skip bootloader payload
[2025-04-24 22:56:40] info: zh:zstack:znp: Skip bootloader for CC2652/CC1352
[2025-04-24 22:56:58] error: z2m: Error while starting zigbee-herdsman
[2025-04-24 22:56:58] error: z2m: Failed to start zigbee-herdsman
[2025-04-24 22:56:58] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[2025-04-24 22:56:58] error: z2m: Exiting...
[2025-04-24 22:56:58] 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:113:27)
at Controller.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/controller.ts:136:29)
at Zigbee.start (/app/lib/zigbee.ts:69:27)
at Controller.start (/app/lib/controller.ts:104:13)
at start (/app/index.js:149:5)
I’ve made sure that the SLZB-06P7 is on, it is reachable from the network, and is functioning well. I’ve restarted it, and I’ve re-flashed the firmware. I’ve also restarted HA, and I’ve restarted Z2M about a million times and it still has the same error. I’ve checked the configuration and it’s all correct but it’s still not working.
Here is my HA version
Core 2025.4.3
Supervisor 2025.04.0
Operating System 15.2
Frontend 20250411.0
And the SLZB-06P7 is on version 2.8.5.dev7.
Has anyone else encountered this error and know how to fix it?
Error: SRSP - SYS - ping after 6000ms is usually caused by the ZHA integration running after autodetecting your coordinator, but check the link in the error for other possible causes.
Any luck on this? I have the same issue, checked the config, restarted HA, Z2M or the Zigbee adapter itself, even tried a SLZB-06P7 firmware update after it failed. The update from Z2M 2.2.1 to 2.3.0 did not work either…
SLZB-06P7 logging shows the following constantly.
[23:54:42] taskZB | New client: 192.168.1.195 id: 0
[23:55:00] taskZB | Client disconnected, id: 0
Changing the adapter type from zstack to ember or ezsp and back to zstack does not make a difference
I’m running HA 2025.4.2 (or 2025.4.4), with Z2M 2.2.1 (or 2.3.0). I’m using HA in a Virtual Machine
Error:
[2025-05-06 23:54:59] error: z2m: Error while starting zigbee-herdsman
[2025-05-06 23:54:59] error: z2m: Failed to start zigbee-herdsman
[2025-05-06 23:54:59] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[2025-05-06 23:54:59] error: z2m: Exiting...
[2025-05-06 23:54:59] 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:133:29)
at Zigbee.start (/app/lib/zigbee.ts:70:27)
at Controller.start (/app/lib/controller.ts:104:13)
at start (/app/index.js:149:5)
at start (/app/index.js:149:5)
at start (/app/index.js:149:5)
at start (/app/index.js:149:5)
Sorry no, still experiencing a lot of instability with zigbee. Now the whole system seems to be going up in flames. I can barely get it to start the supervisor seems to be completely borked after the latest update.