Zigbee2mqtt update concerns

[123 (Taras)]

There’s an entite topic about using a State Trigger to monitor an event entity.

Using the new action events in Zigbee2MQTT 2.0

The new Zigbee2MQTT 2.0 introduces the new event based actions for things with buttons. And at the same time deprecates the old way of using action sensors. Note that you enable these new actions by setting the Zigbee2MQTT configuration “Home Assistant experimental event entities” to enabled (true) However, it seems the Zigbee2MQTT devs have pulled back on the plan to remove the legacy sensor based method, so for now users can start to play with the events but it may be best to keep things as …

Here’s my post in that topic.

Using the new action events in Zigbee2MQTT 2.0

Just finished converting one of my automations, that controls an IKEA E1743 device, from using the now deprecated sensor entity to an event entity. Here a few of my thoughts. It’s not a significant difference unless you employ wait_for_trigger in which case it becomes a bit more verbose. For example, here’s a snippet of the original automation that detects single and double presses of the device’s On button. A single press sets the light’s brightness to 128 whereas a double press sets it to 25…