Home Assistant button triggers broke in `1.40.2`

[alec-pinson]

What happened?

This appeared as Unknown, rolling back to 1.40.1 fixed the issue.

I'm using a Aqara WXKG11LM button

What did you expect to happen?

It should show single, double etc.

How to reproduce it (minimal and precise)

Upgrade 1.40.1 -> 1.40.2 and it breaks the button

Zigbee2MQTT version

1.40.2

Adapter firmware version

na

Adapter

na

Setup

Home Assistant

Debug log

No response

[Koenkk]

Could you provide the debug log when generating actions on the device?

See this on how to enable debug logging.

[djurny]

Hi there, One question; I had similar experience with home assistant, for example I would not see a certain action in that drop-down, but after actually triggering the action from the device, it started showing in HASS. Is it the same with your situation? Do all the actions show in the drop-down after performing the action on the device itself? (Not saying that's the way it is supposed to work by the way, just checking it that can help you along right now.) Groetjes,

[Skynetnexus]

I had the same issue, all my button actions became unavailable after installing Home Assistant Core 2024.10.1, revered to 2024.9.3 and all good again - I tried updating twice, both times the same issue ( running Zigbee2MQTT version 1.40.0-dev commit Coordinator revision 20240710

[antbarney]

I also noticed this after just updating to 2024.10.1, Button Actions all work tho but show an unknown status, when HA used to list them as "None" according to history. I think It might be some change of handling in HA from when the action is published as null/blank but that is just a guess. Stuff works fine tho, if I did not have an automation that shows me unknown/unavailable I would have never noticed an issue.

[Skynetnexus]

I also noticed this after just updating to 2024.10.1, Button Actions all work tho but show an unknown status, when HA used to list them as "None" according to history. I think It might be some change of handling in HA from when the action is published as null/blank but that is just a guess. Stuff works fine tho, if I did not have an automation that shows me unknown/unavailable I would have never noticed an issue.

Thank you for pointing this out, I am running a template sensor ( [unavailable-entities-sensor] ) (https://github.com/jazzyisj/unavailable-entities-sensor) and it picked up the button click sensors as being unavailable. Initially I was upgrading remotely from work, so I upgraded whilst I was home and able to test the buttons. Yes the button still work after the upgrade.