Homelab, Linux, JS & ABAP (~˘▾˘)~
 

[Home Assistant] Sonoff Dongle Plus MG24 crash during VM backup on Proxmox host

Recently I migrated my Zigbee network to a new controller. From my old Sonoff ZBDongle-P (Z-Stack) to a Sonoff Dongle Plus MG24 (Ember) I got for about 13€ from AliExpress. I was following this guide and everything went well. But a few days later, suddenly in the night, the new dongle crashed. These were the related Z2M logs:

[2026-11-21 02:20:13] error: 	zh:ember:ezsp: ERROR Transaction failure; status=ASH_ERROR_TIMEOUTS. Last Frame: [FRAME: ID=52:"SEND_UNICAST" Seq=53 Len=7].
[2026-11-21 02:20:13] error: 	zh:ember:ezsp: ERROR Transaction failure; status=NOT_CONNECTED. Last Frame: [FRAME: ID=52:"SEND_UNICAST" Seq=53 Len=7].
[2026-11-21 02:20:13] error: 	zh:ember:ezsp: ERROR Transaction failure; status=NOT_CONNECTED. Last Frame: [FRAME: ID=52:"SEND_UNICAST" Seq=53 Len=7].
[2026-11-21 02:20:13] error: 	z2m: Adapter disconnected, stopping
WATCHDOG: Waiting 0.03333333333333333min before next start try.
Starting Zigbee2MQTT with watchdog (2000,60000,300000,900000,1800000,3600000).
[2026-11-21 02:20:41] error: 	z2m: Error while starting zigbee-herdsman
[2026-11-21 02:20:41] error: 	z2m: Failed to start zigbee-herdsman
[2026-11-21 02:20:41] error: 	z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[2026-11-21 02:20:41] error: 	z2m: Exiting...
[2026-11-21 02:20:41] error: 	z2m: Error: Failed to start EZSP layer with status=HOST_FATAL_ERROR.
    at EmberAdapter.initEzsp (/app/node_modules/.pnpm/zigbee-herdsman@11.2.0_supports-color@7.2.0/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:677:19)
    at async EmberAdapter.start (/app/node_modules/.pnpm/zigbee-herdsman@11.2.0_supports-color@7.2.0/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1558:24)
    at async Controller.start (/app/node_modules/.pnpm/zigbee-herdsman@11.2.0_supports-color@7.2.0/node_modules/zigbee-herdsman/src/controller/controller.ts:146:29)
    at async Zigbee.start (/app/lib/zigbee.ts:70:27)
    at async Controller.start (/app/lib/controller.ts:117:29)
    at async start (/app/index.js:156:5)
    at async triggerWatchdog (/app/index.js:36:9)
    at async Controller.exit [as exitCallback] (/app/index.js:52:13)
    at async Controller.exit (/app/lib/controller.ts:379:16)
    at async Controller.stop (/app/lib/controller.ts:374:16)
WATCHDOG: Waiting 1min before next start try.

Turned out, the reason was a backup job on my Proxmox host on which my Home Assistant VM is running.

journalctl 
--since "2026-11-21 02:15:00" 
--until "2026-11-21 02:25:00" 
--no-pager 
| grep -Ei 'vzdump|backup|snapshot|freeze|thaw|qemu|usb|reset'

Nov 21 02:15:01 pve2 CRON: (root) CMD (which zfs-auto-snapshot > /dev/null || exit 0 ; zfs-auto-snapshot --quiet --syslog --label=frequent --keep=4 //)
Nov 21 02:16:33 pve2 pvescheduler: INFO: Finished Backup of VM 195 (00:04:28)
Nov 21 02:16:33 pve2 pvescheduler: INFO: Starting Backup of VM 196 (lxc)
Nov 21 02:18:40 pve2 pvescheduler: INFO: Finished Backup of VM 196 (00:02:07)
Nov 21 02:18:40 pve2 pvescheduler: INFO: Starting Backup of VM 204 (qemu)

VM 204 backup started at 02:18:40, which is my HA VM. A few minutes later, the MG24 dongle crashed. By doing another manual backup, I could reproduce the controller crash.
My backup job was using the following settings:

--mode snapshot
--storage TrueNAS
--compress zstd
--fleecing 0

AI suggested different solutions, one of it was to enable fleecing in the job configuration. This reduces guest-write delays caused by copying old blocks directly to the remote backup target. To be honest, I had never heard of this setting before, but after enabling it and running another backup, the MG24 dongle stopped crashing. I have no idea why my previous Dongle-P didn’t have this problem, but since it was a simple solution, I’ll just take it.

[Home Assistant] Update firmware on Sonoff Zigbee USB Dongle-P

Recently, I saw this video showing a super easy way to update the firmware of a SONOFF Zigbee Stick: https://www.youtube.com/watch?v=-_bE_PbZwO0

Just for reference, this was the way I did it previously: https://nocin.eu/home-assistant-update-firmware-on-sonoff-zigbee-usb-dongle-p/

Following just a few notes and screenshots, doing a firmware update using the SONOFF Dongle Flasher.

1. Optional: Check current firmware version

and compare with latest firmware version here

2. Do a backup

3. Stop Z2M and install the SONOFF Dongle Flasher

Install https://github.com/iHost-Open-Source-Project/hassio-ihost-addon

Start Add-on, open WebUI and hit the connect button. If your dongle is not found, simply manually add the device. The rest is pretty self-explanatory.

4. If flash was successful, stop SONOFF Dongle Flasher and Start Z2M again. Check new version in Z2M WebUI. And that’s it.

[Home Assistant] Update firmware on Sonoff Zigbee USB Dongle-P

Update 03.11.2025: There is now a much simpler way, check post here.

First, confirm that you have a Sonoff Zigbee 3.0 USB Dongle Plus. Go to Settings → Hardware → All Hardware → Search for Zigbee

Check your current firmware version:

Important: Stop Zigbee2Mqtt before flashing, as described in the docs!

Now let’s add the ZigStar repository: Settings → Add-ons → Add-on Store → Three dots → Repositories → Add https://github.com/mercenaruss/zigstar_addons

After that, install the Add-on for Texas Instruments CC2652P7 based radios.

Copy the firmware link from here: https://www.zigbee2mqtt.io/guide/adapters/

Got to the Configuration of the installed ZigStar Add-on and paste the firmware link and select the two radio buttons like bellow.

If you receive an error when saving the configuration, simply add 127.0.0.1 as Network Device and save again.

If the Configuration is successfully saved, start the Add-on and flashing will start immediately.

Switch to the Log tab and hit refresh until you see the “successfully stopped” message.

Now you can stop the ZigStar Add-on and start Zigbee2Mqtt again and check your new installed version.

Done.