Zigbee2Mqtt buttons doesn't reports first press on automations as action

[123 (Taras)]

When using an event entity, if you want to detect two consecutive identical button events you have to make the State Trigger detect all button events and then use a choose to determine which button event occurred.

In other words, instead of doing this:

  - trigger: state
    entity_id:
      - event.przyciski_lazienka_action
    id: RADIO_NS
    to: 1_double
    attribute: event_type

You must do this:

  - trigger: state
    entity_id:
      - event.przyciski_lazienka_action
    not_from: unavailable 

Then use a choose in the automation’s actions to determine which button event occurred.

actions:
  - variables:
      event: "{{ trigger.to_state.attributes.event_type }}"
  - choose:
      - conditions: "{{ event == 'on' }}"
        sequence:
           ... etc ...
      - conditions: "{{ event == 'off' }}"
        sequence:
           ... etc ...
      - conditions: "{{ event == '1_double' }}"
        sequence:
           ... etc ...

I posted an example here and you find a detailed explanation with more examples here.

If you’re interested, I posted my observations on the process of converting one of my automations to detect consecutive identical button events in this post:

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…