After a ha restart some automation only work again after deactivation and activation

[hathon]

I have some automations that are triggered by the deconz integration that are working after a ha restart.

The event - in my case a higbee switch - arrives and is visible in the log. The automation also says that the tripper was triggered.
However, the action is not executed.
You don’t see anything in the trace either.

If you deactivate this automation and then activate it again, everything works again. Are there any ideas?

trigger:
  - device_id: 79513cd0044b025dce0d9a5748ee35ff
    domain: deconz
    platform: device
    type: remote_button_short_release
    subtype: dim_down
  - device_id: 93df1c8d60b84f73ad37500aa2984951
    domain: deconz
    platform: device
    type: remote_button_short_release
    subtype: dim_down
condition: []
action:
  - service: light.toggle
    metadata: {}
    data: {}
    target:
      device_id:
        - 914f722460305c3c30c27f9186965e64
mode: single

[francisp (Francis)]

Why and how to avoid device_ids in automations and scripts

Background When you start writing automations, a device trigger seems the obvious choice. Everybody knows what a device is and it comes at the top of the UI dropdown list. [image] It works… but it is certainly not a “great way to start” because it is storing up problems for the future. Far better to use an entity, with state or numeric_state. Device_id problems The yaml will be longer and harder to follow, which may make maintenance difficult, especially a few months down the line when y…

[hathon]

Thank you for the hind with the entity.

But it seems there is an other error. Maybe an unresolved dependency while starting hass?

ERROR (MainThread) [homeassistant.components.automation.light] Got error 'No deconz_event tied to device "Remote1" found' when setting up triggers for light

I can reproduce this behavior and after a disable an enable of this automation the will proceed in the automation