I’ve been searching this issue and apparently the zigbee2mqtt 2025 update breaks several folks aqara buttons, Ikea stuff, etc. (I didn’t do my research before updating… been a few months.) I’ve seen the solution for some is to add “Home assistant legacy action sensors” to zigbee2mqtt but I don’t think I know where to find that using docker compose and portainer. Here’s what they are talking about: https://github.com/home-assistant/core/issues/134739 where they also mention configuring device triggers.
I did try adding
homeassistant:
legacy_action_sensor: true
to my zigbee2mqtt config file, but that seemed to break everything, so I reverted it back to what it was before.
I haven’t found a zigbee2mqtt Ui under settings. I have an Mqtt under Devices & Services, and also a Zigbee Home Automation there that shows the correct socket ip address for the slzb-06 coordinator I’m using. If I hit configure on either of those, there is no legacy setting. Perhaps I’m looking in the wrong spot?
I tried to be smart/diligent/proactive before I upgraded to Z2M 2.0 and set up all my Aqara and IKEA buttons to run und Z2M 1.4 based on the ‘new’ event trigger like this:
- entity_id: event.xa_btn_02_action
to: single
attribute: action
trigger: state
Worked fine in Z2M 1.4 but when I upgraded to Z2M 2.0 it all fell apart. Neither the Aqara nor the IKEA buttons triggered anything.
I ended up going with the MQTT trigger because I saw it work in a blueprint for my Hue TapDialSwitch like this:
- trigger: mqtt
topic: zigbee2mqtt/XA_BTN_02/action
payload: single