Proxmox Backup of HA OS crashes Zigbee2MQTT Addon with coordinator SLZB-06U

Configuration Zigbee
, ,
1

Hi,
I am running a daily backup (mode snapshot) of my HA OS instance.
During that timeframe some days (not every night) the Zigbee2MQTT Addon running with a SLZB-06U coordinator is stopping. In the morning the Addon is deactivated and hence all Zigbee devices are non-functional. A manual start of the Addon works.

I recently moved from SONOFF Zigbee 3.0 USB Dongle to SLZB-06U. Before I was not facing that issue.

This is the backup schedule:

INFO: Starting Backup of VM 100 (qemu)
INFO: Backup started at 2026-03-11 02:00:09
INFO: Finished Backup of VM 100 (00:21:56)
INFO: Backup finished at 2026-03-11 02:21:59

Corresponing relevant Log of Zigbee2MQTT:

[2026-03-11 02:21:24] info: 	z2m: Connecting to MQTT server at mqtt://core-mosquitto:1883
[2026-03-11 02:21:25] info: 	z2m: Connected to MQTT server
[2026-03-11 02:21:28] info: 	z2m: Started frontend on port 8099
[2026-03-11 02:21:28] info: 	z2m: Zigbee2MQTT started!
[2026-03-11 02:24:36] error: 	zh:zstack:znp: Socket error Error: read ETIMEDOUT
[2026-03-11 02:24:36] info: 	zh:zstack:znp: Port closed
[2026-03-11 02:24:36] info: 	zh:zstack:znp: closing
[2026-03-11 02:24:36] error: 	z2m: Adapter disconnected, stopping
[2026-03-11 02:24:36] info: 	z2m: Stopping Zigbee2MQTT (restart=false, code=2, signal=undefined)
[2026-03-11 02:24:36] info: 	z2m: Disconnecting from MQTT server
[2026-03-11 02:24:36] info: 	z2m: Stopping zigbee-herdsman...
[2026-03-11 02:24:36] info: 	z2m: Stopped zigbee-herdsman
[2026-03-11 02:24:36] info: 	z2m: Stopped Zigbee2MQTT
[02:24:37] INFO: Preparing to start...
[02:24:37] INFO: Socat not enabled
[02:24:37] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2026-03-11 02:24:38] info: 	z2m: Logging to console, file (filename: log.log)
[2026-03-11 02:24:38] info: 	z2m: Starting Zigbee2MQTT version 2.9.1 (commit #unknown)
[2026-03-11 02:24:38] info: 	z2m: Starting zigbee-herdsman (9.0.9)
[2026-03-11 02:24:39] info: 	zh:zstack:znp: Opening TCP socket with 192.168.178.120:6638
[2026-03-11 02:24:44] error: 	zh:zstack:znp: Socket error Error: connect EHOSTUNREACH 192.168.178.120:6638
[2026-03-11 02:24:44] error: 	z2m: Error while starting zigbee-herdsman
[2026-03-11 02:24:44] error: 	z2m: Failed to start zigbee-herdsman
[2026-03-11 02:24:44] error: 	z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[2026-03-11 02:24:44] error: 	z2m: Exiting...
[2026-03-11 02:24:44] error: 	z2m: Error: Error while opening socket
    at Socket.<anonymous> (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:160:24)
    at Socket.emit (node:events:531:35)
    at emitErrorNT (node:internal/streams/destroy:170:8)
    at emitErrorCloseNT (node:internal/streams/destroy:129:3)
    at processTicksAndRejections (node:internal/process/task_queues:90:21)
[2026-03-11 02:24:44] info: 	zh:zstack:znp: Port closed
/app/node_modules/.pnpm/[email protected]/node_modules/readable-stream/lib/_stream_writable.js:264
  var er = new ERR_STREAM_WRITE_AFTER_END();
           ^
Error: write after end
    at writeAfterEnd (/app/node_modules/.pnpm/[email protected]/node_modules/readable-stream/lib/_stream_writable.js:264:12)
    at File.Writable.write (/app/node_modules/.pnpm/[email protected]/node_modules/readable-stream/lib/_stream_writable.js:300:21)
    at DerivedLogger.ondata (/app/node_modules/.pnpm/[email protected]/node_modules/readable-stream/lib/_stream_readable.js:629:20)
    at DerivedLogger.emit (node:events:531:35)
    at addChunk (/app/node_modules/.pnpm/[email protected]/node_modules/readable-stream/lib/_stream_readable.js:279:12)
    at readableAddChunk (/app/node_modules/.pnpm/[email protected]/node_modules/readable-stream/lib/_stream_readable.js:262:11)
    at DerivedLogger.Readable.push (/app/node_modules/.pnpm/[email protected]/node_modules/readable-stream/lib/_stream_readable.js:228:10)
    at DerivedLogger.Transform.push (/app/node_modules/.pnpm/[email protected]/node_modules/readable-stream/lib/_stream_transform.js:132:32)
    at DerivedLogger._transform (/app/node_modules/.pnpm/[email protected]/node_modules/winston/lib/winston/logger.js:337:12)
    at DerivedLogger.Transform._read (/app/node_modules/.pnpm/[email protected]/node_modules/readable-stream/lib/_stream_transform.js:166:10)

Seems to be a socket error.
Does anyone facing the same? How can this be avoided?

Best regards, Bastian

2

Is 192.168.178.120 your dongle ? Seems to be not yet re-connected after the backup job.
Try to restart Z2M via automation with a bit of delay after the backup.

3

Yes, thats the SLZB-06U coordinator, connetced via ethernet.
Yes, an automation to restart might be a solution.
However, I am wondering if somone with a simlar setup is facing the same.

4

I am doing a weekly backup of my HA VM within Proxmox and never experienced such a behavior with my SLZB-06 (connected via WIFI).
Only after upgrading/restarting the SLZB-06 I need to reboot Z2M.

5

Same as @nightfever, I do 12 hour snapshot backups on Proxmox (SLZB-06p7) and never had any issue. Before you figure out the reason, you could enable the watchdog for the app. Remember to fill out the checking intervals (in minutes):

image
image1320×788 24.3 KB

6

Oh, I was not aware of that enhanced watchdog setting, I’ve used only the normal Watchdog switch of the Addon - sorry, App - which is geeting deactivated after certain numer of failures.

With the Setting 1,5,15,30,60 I can come over the backup time. Z2M is starting afterwards properly.

1 Like