I have half a dozen Zigbee buttons in my house; they have been working fine up until about a week ago.
In Zigbee2MQTT, if I go to one of the devices/buttons, and go to the “exposes” tab, it shows the battery, the link quality, and the action (e.g. button_1_single pressed, etc).
If I test the buttons, I can see the “action” changing on the “Exposes” tab within Z2M.
However, the entire “action” sensor has gone missing from within Home Assistant. Instead, all I get is the battery and the link quality.
I have attached screenshots of the Z2M Exposes tab and the MQTT device page.
This previously worked fine - the “action” would be available as an entity in Home Assistant, which I then used as triggers for my various automations. Now the action entity is missing entirely.
Any suggestions on why this might be happening, and how to fix it please?
(I realise the Linkquality is disabled in the Home Assistant device page; that’s fine. It’s the “action” that I care about, which isn’t even visible to be able to enable it.)
Could you please share new method that may exist if you have found any?
What I see is only ugly workarounds using mqtt events.
I support motivation to clean and neat code, kind of align with homeassistant, but what a regression for users.
Have a same issue about week ago with all my zigbee buttons, maybe after last update. Then I starting migration to Zigbee Home Automation (with SONOFF Zigbee 3.0 USB Dongle Plus V2), so workaround with zigbee2mqtt didn’t work for me. My automatons didn’t work with ZHA.
Is there a solution? Or I have to migrate all may zigbee stuff back from ZHA to Z2M?
I don’t know if this helps but I had a similar issue with a Sonoff smart button. Z2M just didn’t show it. I found a post on here that said to just go to the devices in MQTT integration, create an automation and choose device as action. I then had the options for single click and double click. This was way before the recent update so it was like this out of the box. So that doesn’t explain it working and stopping to work after the update unless the option mentioned above fixes it.
Thank you for this thread. I thought I was going crazy or unintentionally broke something, though I didn’t make any system changes. Going through the HA changelog didn’t show anything that would affect this. It was only when I noticed that this affected both my Aqara buttons AND my Moes 4-way buttons, that I realized this had to be something inside Z2M.
How does something like this get rolled through without a warning or alert or something? I love HA’s notification and repair function for stuff like this. I don’t recall anything in Z2M’s addon change log that clearly indicated such a breaking change. EDIT I think I see it in the changelog, but it’s totally unclear how this change would break people’s installations. Even other developers commenting on the changelog say they were blindsided. Very poor communication for such a major change in usability.
They clearly highlighted breaking changes right on the screen you have to click to update. You can’t accuse them of poor communication if you didn’t bother to read the release notes before updating.
