Hi! Started having some issues in Zigbee2MQTT after updating Home Assistant Core to 2025.6. I believe I was in 2025.4 before.
It happens a couple times a day, like every 3 hours. I can access Z2M front-end and try to turn on and off devices by they won’t respond. After rebooting Z2M it will start working again immediately every time. I uploaded an image to show some of the errors I’m getting.
I’m not that used to checking logs, so if logs are needed for debugging, instructions on how to get logs are welcome.
My Setup Information
Zigbee2MQTT
Dongle: SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2
Coordinator type: EmberZNet
Coordinator revision: 7.4.2 [GA] (I’ve had the same issue on 7.4.5)
Well, I’m using ZHA and I noticed a similar issue. Hence I reverted to 2025.5.3 using my previous backup. I’m also working on a parallel test installation as I’ll move from HA core to Docker containers. And same issue here as well: ZHA network down with 2025.6.1 container while Z-Wave nw is OK
Thank you for your suggestions!
I am using a USB extension cable and keep the Dongle away from the mini PC.
Reading the Beelink T4 manual, it says my mini PC only has USB 3.0 ports.
Thank you for the resource, I’ll study it and see if there is anything I could improve that might solve my problem.
Thanks, will try this as well; now my Z-Wave dongle is on USB2.0 (and it works in the new HA version), while ZigBee (and the external NVMe device) are on the two RB 3.0 ports.
Will try this and let you know, thank you! Franco
Hello, I’ve solved this although I still do not have a solid answer for the root cause of this issue.
I noticed that starting from a fresh conteinerized installation of 2015.6.3 ZHA was back up and running. It was not after a traditional HA upgrade tested a couple of weeks ago while moving my HA core installation from 2025.5.3 to 2026.6.1. Hence I suspected the issue was in 2025.6.1 and not in 2025.6.3.
BTW, before doing this I moved USB connections but this was not the problem.
I did the upgrade for 2025.5.3 to 2026.6.3 and … ZHA broken again, and to me this was a nonsense. Before quitting and restart from the backup I did the following:
remove the /srv/homeassistant directory and recreate a new one (same permissions …)
sudo su -s /bin/bash homeassistant
cd /srv/homeassistant
python3 -m venv .
source bin/activate
python3 -m pip install wheel
pip3 install homeassistant
exit
This fixed the issue, and imho this alternative procedure downloads some updated package which fixes the issue.
I’ve tried this twice and it worked, anyway I’ll keep my original 2025.5.3 backups for a while before confirming this version …
Hope this helps and best regards,
Franco