Many Actions do not provide Device Conditions in Home Assistant

[ejpenney]

What happened?

Saw the note that _action entities are going away, went to see how feasible this is in my environment. For example, I have an automation:

description: ""
mode: single
triggers:
  - trigger: state
    entity_id:
      - sensor.ikea_remote_action
    from: null
    to: brightness_up_hold
conditions: []
actions:
  - repeat:
      until:
        - condition: state
          entity_id: sensor.ikea_remote_action
          state: brightness_down_release
      sequence:
        - data:
            brightness_step_pct: 10
            transition: 1
          target: light.upstairs_all
          action: light.turn_on
        - delay: "1"

This automation might look something like this after removing the _action entities:

description: ""
mode: single
triggers:
  - domain: mqtt
    device_id: 91096acf4566eae62076c12c8803ff32
    type: action
    subtype: brightness_up_hold
    trigger: device
conditions: []
actions:
  - repeat:
      until:
        - ???
      sequence:
        - data:
            brightness_step_pct: 10
            transition: 1
          target: light.upstairs_all
          action: light.turn_on
        - delay: "1"

But the repeat condition has no equivalent:

Meaning this automation will break when the _action entities go away and I see no equivalent behavior with MQTT Device Triggers.

What did you expect to happen?

I expected that the events would be available as repeat conditions, but they are not.

How to reproduce it (minimal and precise)

Try to have an automation that triggers from a long-press event with (any?) Zigbee switch, and then repeats an event until a button-up event occurs on that same device.

I have confirmed this limitation for the following devices:

• TRADFRI remote control (E1524/E1810)
• 3 scene remote and dimmer (ZB-3008)
  by RGB Genie
• Wireless switch with 4 buttons (TS0044)
  by Tuya
• Hue dimmer switch (324131092621)
  by Philips

Zigbee2MQTT version

1.42.0

Adapter firmware version

20230507

Adapter

usb-Silicon_Labs_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0001-if00

Setup

Proxmox LXC (TTeck)

Debug log

No response

[fir3drag0n]

I can report this as well. Several Ikea and aqara devices are missing actions.

[ibimslawa]

I also have this problem with my TS0044 and TS0043 -- but there's a workaround for now...
In preparation of Z2M v2.0 the configuration option "homeassistant_legacy_triggers" supposedly was set to false. When this option is set to false the _action entities disappear.
So for now just set the following in Z2M configuration.yaml:

advanced:
  ...
  homeassistant_legacy_triggers: true

In future you are supposed to use MQTT device triggers for _action and _click.
I haven't figured out yet how to adapt my automation blueprints for my scene switches to use MQTT device triggers instead of the _action input...

Note: The subtype list for the device triggers will be updated and new subtypes added when new subtypes are send to Z2M. Meaning pressing all the buttons on your scene switch will fill the list.

https://www.zigbee2mqtt.io/guide/usage/integrations/home_assistant.html#via-mqtt-device-trigger-recommended

[ibimslawa]

I updated my Tuya scene switch blueprints I had to now utilize MQTT topic triggers.
Might want to have a look and adapt to your needs:
https://github.com/ibimslawa/ha-bp-scene-switch-mqtt/

[Koenkk]

The legacy action sensor will not be removed in 2.0.0 anymore (#24198 (comment)). So I will close this.