Issue with Zigbee2MQTT 2.0.0-2 on Home Assistant – Loginovo ZG-101ZL and Tuya TS0044 Buttons Not Working

[voltkj]

Description of the issue

Problem:

In version 2.0.0-2, my Zigbee buttons do not work:
Loginovo ZG-101ZL
Tuya TS0044 (4-button switch)
Zigbee2MQTT detects button presses, but the action entity is missing in Home Assistant.
When I manually downgrade to version 1.42, the buttons work flawlessly.
However, Home Assistant automatically upgrades Zigbee2MQTT back to version 2.0.0-2, even though I tried to block the update.
Home Assistant displays a message saying that it is not possible to block the update, and the system forces the upgrade.
Questions:

How can I make the Loginovo ZG-101ZL and Tuya TS0044 buttons work correctly in version 2.0.0-2?
How can I block the automatic update of Zigbee2MQTT and stay on version 1.42?
I'm very disappointed with this situation. The new Zigbee2MQTT version breaks my setup, and the inability to stop the forced update prevents me from using a working configuration.

Any help would be greatly appreciated.

Addon version

Zigbee2MQTT version 2.0.0-2

Platform

Home Assistant Version: Core 2025.1.2, Supervisor 2024.12.3, Operating System 14.1

Logs of the issue (if applicable)

No response

[robi59italy]

same situation with:
Home Assistant 2025.1.2
Buttons Ikea model E2001/2002
Zigbee2mqtt shows the message from the button on the log so button is ok and zigbee network running

[CoolhappyDE]

Same for the Aqara WXKG11LM Button, Z2M is showing the Clicks but its not advertised through MQTT. Need help because now no one can ring the door :)

Home Assistant 2025.1.2
Zigbee2MQTT version 2.0.0

[voltkj]

Hi,

It seems we're dealing with the same issue in Zigbee2MQTT 2.0.0-2. The button actions are detected in the logs but aren't being sent through MQTT, which causes Home Assistant to not respond to the button presses.

🔧 What You Can Do:
Temporarily Roll Back to Version 1.42:
I recommend rolling back to Zigbee2MQTT 1.42, where the buttons worked correctly. You can also block automatic updates to prevent Zigbee2MQTT from upgrading to version 2.0.0-2 again.

Report the Issue on GitHub:
It looks like this is a global issue in the new version. You can check if it's already reported or create a new issue here:
👉 Zigbee2MQTT GitHub Issues
Be sure to include:

Your Zigbee2MQTT version (2.0.0-2)
The model of your button (Aqara WXKG11LM)
A description of the issue (actions detected in logs but not published via MQTT)
Wait for a Fix:
If this is a common issue, the developers will likely release a fix soon. Until then, using version 1.42 is the safest solution.

Let me know if you need help rolling back or blocking the update.

Good luck!

[MathiasMogensen]

I went into Zigbee2MQTT -> Settings -> Home Assistant Integration and enabled 'Home Assistant Legacy Sensors'. Restarted and changed the HA blueprint for my Hue Dimmer v2 to the new action and it works now :)

[garaig]

I went into Zigbee2MQTT -> Settings -> Home Assistant Integration and enabled 'Home Assistant Legacy Sensors'. Restarted and changed the HA blueprint for my Hue Dimmer v2 to the new action and it works now :)

this has worked me as well! thx!