I have about 50 Zigbee devices since 4 years.
I’ve had a problem for 2 days. I thought it was due to an update to Home Assistant or Z2M, but even after restoring my backups, I still have the problem.
My devices that send back information seem to be working correctly (not all of them), for example: my Aqara temperature sensors, my Aqara opening sensors, but I can no longer control my other equipment, for example: connected sockets of different brands
In the logs I see timeouts with the following message: 'Error: ZCL command
Looking around a bit, I see that some people have solved the problem by adding a USB extension lead to their adapter, but I already have a 2m USB extension lead.
I haven’t made any particular changes recently except for updating HA and Z2M
I’m still running on a NUC in Proxmox, the adapter is still connected to the same USB socket and I haven’t added any new equipment to my Zigbee network.
Restarting Z2M doesn’t change anything, I’ve also tried changing the USB port or shifting my adapter but it’s no better.
I’ve tried a rollback to version 2-2 1.1 of Z2M but that doesn’t solve my problem
I’ve tried a rollback of Home Assistant to version 2025.4.3 but that’s no better either
Zigbee2MQTT version
2.3.0-1
Adapter firmware version
0x26660700
Adapter
ConBee2/RaspBee2
Setup
Z2m in module of Home Assistant
Version of Home Assistant :
Core 2025.5.1
Supervisor 2025.05.0
Operating System 15.2
Interface utilisateur 20250509.0
I don’t know if that’s the cause or if the problem is more general and the problems with Z2M are a consequence.
If anyone knows how to interpret these logs, thank you.
That looks like your entire Z2M configuration.yaml is corrupted or improperly formatted.
Can you paste the contents (properly formatted) of the file from HOMEASSISTANT\config\zigbee2mqtt\configuration.yaml? If you have Samba share or the File Editor addon installed, you can use those to find the file.
Remove/hide any passwords and your network key, but don’t touch anything else.
EDIT: Looks like even your Samba Share addon config is corrupted. Your log is complaining about an interface option which I can’t see listed in the addon docs. Did you edit its config recently?
devices:
- devices.yaml
groups:
- groups.yaml
homeassistant:
enabled: true
mqtt:
base_topic: zigbee2mqtt
user: addons
password: xxxxx
server: mqtt://core-mosquitto:1883
serial:
port: >-
/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2401495-if00
adapter: deconz
advanced:
adapter_delay: 200
log_level: error
pan_id: 6754
channel: 11
network_key:
- x
- x
- x
- x
- x
- x
- x
- x
- x
- x
- x
- x
- x
- x
- x
- x
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
enabled: true
port: 8099
availability:
enabled: false
version: 4
Yes, I saw that in the logs I also have a problem with Samba, although this module has been stopped for several months in my configuration.
I have no memory of having edited an interface recently or of having made any major changes to my configuration, apart from updating HA and Z2M.
Compared your file with mine and it’s mostly identical, however there are a couple of things which look off:
Your log is complaining about permit_join, but it’s not present in the extract you sent. How is it complaining about something in your file which doesn’t actually exist? Same goes for your samba share addon. In my mind, it shouldn’t be complaining about interface if it’s stopped.
Secondly, the only issue I see in your file is that version: 4 is misplaced. It should be under the MQTT section, like the below snippet. Note that you can leave that line out entirely, since version 4 is the default.
At this point, I’d be looking into issues either in the addons themselves, or the supervisor. If you have access to the HA command line, I’d run ha supervisor repair command, followed by a ha supervisor restart once it’s done.
I have the impression that these logs which refer to options are simply informative, it’s possible that they were already there before I had the problem with Z2M (I never looked at the Supervisor logs before).
I migrated to V4 following the change in the conf file, like yours.
I have run a Supervisor repair and a reboot but I still get the same errors.
At this level, here are the three options I see:
I must have an old backup of my complete HA virtual machine via Proxmox, I can try to restore one that’s more than 10 days old but I’ve never done it before.
Uninstall and reinstall Z2M completely (please tell me that I can keep the list of my devices - by copying/pasting the ‘devices.yaml’ for example? Or the ‘database.db’?)
I think I’ll still have to join all my devices.
Change my ConBee II key, but then I’d also have to join everything, and I don’t know if the problem is with the key, as some of my sensors are still working.
Doubt that. Even though they are warnings and not outright errors, I just restarted my addons and didn’t see those warnings.
Personally, at this point I suggest you uninstall and reinstall if a restore doesn’t work. Yes, you should definitely keep a copy of your database.db & devices.yaml files just in case, but odds are something might go wrong and you’re gonna need to re-pair.
Honestly, I’d start by attempting to fix the samba share addon first. Since you’re not currently using it, breaking it any further will not affect your current experience.
Best case scenario is that you manage to fix it, then can use that to transfer the backup Z2M files after restore/reinstall.
After uninstalling and reinstalling Samba Share, I no longer get any errors in the Supervisor logs.
I’ve recovered all the configuration files in the Zigbee2MQTT directory, and I’m going to attempt a complete uninstall and reinstall tomorrow.
Continuation of my adventures:
I uninstalled, deleted the entire Zigbee2MQTT folder in the HA conf directory (otherwise it wouldn’t work) and reinstalled Z2M.
I’m in the process of joining my equipment but it seems to be working again.
I don’t know the root cause of the problem though.
