It should gte picked up from there I expect and if any more info is needed I’m more than happy to help if I can.
This issue became a problem for me this morning. I checked the logs and saw the link in the error message which lead me to updating my configuration.yaml file. That got my server back up and running and then I noticed half my devices (I’ve got 60) weren’t working. I rebooted HA and the zigbee2mqtt container, that didn’t solve the issue. Then I saw this post and read the suggestion to reboot the host so I rebooted my NUC and viola! My motion sensors are working!
Now my issue is that my Aqara Mini Switches show up in zigbee2mqtt and HA but in HA the click entity shows as unavailable. This caused me to look at my contact sensors…these all seem to work fine. I will check the water leak sensors later. For now, I’m trying to figure out how to get the click entity to become available in HA. I held the pairing button on one of the mini switches and it leaves the network…then I hold it again and it interviews back onto the network and retains the name I had previously given it. But alas, no click entity in HA. Can anyone suggest a solution here? Thanks!
Use the event.xxx entity now instead of sensor.xxx.
Thanks! Based on your comment and the link I added the following to the homeassistant section of my zigbee2mqtt docker container’s configuration.yaml file:
homeassistant:
legacy_triggers: false # Disable old method if not needed
experimental_event_entities: true # Enable new method
I then restart the zigbee2mqtt container and the home assistant container and changed the automations that are driven by the aqara mini switches to utilize the action event instead of the click event.This seems to have fixed 99% of my issues.
I still have one aqara mini switch that isn’t responding (the action event status is set to unknown). Any suggestions on fixing that up?
Try pairing it again.
Yep, I had tried that to no avail. However, I just kept trying and on the 7th go around it worked itself out. Thanks again! First world problems all solved in a day. What a time to be alive! 
Thank you kind sir! This has resolved my issue!
Thank you for sharing.
Likewise, on the very latest nabu casa dongle I’ve had to specify ezsp. it won’t work with ember. That single parameter makes it or breaks it.
I have not had to modify the “UI of MQTT add-on”. Nevertheless, would you mind specifying? Not quite sure I understand that last modification.
I suspect a glitch too, logs clearly indicate ezsp is depecrated but add-on won’t boot with ember.
Likewise I’ve had to reboot HA after add-on update for the switches and sensors to become functional again.
Thank you again for sharing.
Just ass a note of this, I do get this warning in z@M on startup:
[2025-01-06 12:43:08] warning: zh:ezsp: 'ezsp' driver is deprecated and will only remain to provide support for older firmware (pre 7.4.x). Migration to 'ember' is recommended. If using Zigbee2MQTT see https://github.com/Koenkk/zigbee2mqtt/discussions/21462
But, if I change it to ember, it breaks.
As I managed to solve my own problem, I deleted my question here.
This is the only thing, and nothing else, that I finally had to do to make Zigbee2MQTT on a Home Assistant Green and a Nabu Casa ZBT-1 dongle to work, and that is adding this in the Serial section of the Configuration of the Zigbee2MQTT Addon:
adapter: ezsp
All other lines were breaking it. Configuration.yaml is still untouched, that is to say no manual alterations after the initial start of using the unit. Thanks anyway for pointing out this line to be added!
Thanks for all the information provided along the thread. I did change the adapter to ezsp and Z2M worked but got the warning you’re seeing. So, it happens that your coordinator should be on a version below 7.4 because the current driver only supports EmberZNet firmware 7.4.x (EZSP 13).
What you have to do is flash your coordinator to the newest firmware version. I’m using the Connect ZBT-1 and did update it from Version 7.1.X to 7.4.X and changed again the adapter to ember and now my Z2M instance is up and running without any errors.
Hope this helps!
See: Improved Ember (EZSP) driver (experimental) · Koenkk/zigbee2mqtt · Discussion #21462 · GitHub
See: Home Assistant Connect ZBT-1