#Problems triggering automations

1 messages · Page 1 of 1 (latest)

bronze shard
#

Hi there!
I'm (mostly) happy with my Home Assistant installation on my RPi 4 (originally RPi 3) since beginning of 2021. Although in the last weeks I've noticed a problem with my automations: I mostly use ZigBee devices with the deCONZ addon. When I press a ZigBee button, the event gets registered immediately (TRIGGERED text in automation editor/logbook entry), but the automation does not run (e.g. lights don't turn on) or run a few seconds late. If I press the run actions button, the actions work as configured.
I already added the systemmonitor CPU and memory usage integration and they both don't go over 30% at all, any ideas?
Or should I open an issue on GitHub for this?

verbal nova
#

When you push the button, check the automation trace

bronze shard
#

When the automation does not run, there isn't even a trace to look at. If it runs a few secons late, the trace states immediate action (even if it's not true)

verbal nova
#

I've never seen it where you get a Logbook entry but not automation running where that was the trigger shrug

bronze shard
#

That's my problem too 😅
But it happens apparently

#

Do you have any idea what I sould try?

verbal nova
#

What's the trigger you're using?

bronze shard
#

The buttons added to deCONZ are firing an event in Home Assistant, the configured trigger for automations is as shown in the screenshot

#

Can't send the screenshot, but the trigger type is Device, and the corresponding button with action

verbal nova
#

Well, when there's text in automations.yaml an image would be annoying 😉

#

Use a code share site instead

bronze shard
#

This would be one of my automations:

alias: Wohnzimmer an
description: ''
trigger:
  - device_id: 0f2d892b8bcf2c6e0c23cf23477b9e52
    domain: deconz
    platform: device
    type: remote_button_short_press
    subtype: turn_on
    id: '7654321'
condition: []
action:
  - service: script.wohnzimmer_an
    data: {}
mode: single

#

I've noticed automations from binary sensors work flawlessly (e.g. window opening), so your suggestion might work (hipefully)

#

I'll try that tomorrow and report back to you if it worked. Thank you to this point for reacting to my message : )

bronze shard
#

Hey there! I've just tried implementing your suggestion in one of my rooms and it seems to work!
Here's the config:

template:
  - trigger:
      - device_id: b4e227b58f6eae9d5e471eff06cc42a0
        domain: deconz
        platform: device
        type: remote_button_short_press
        subtype: turn_on
    binary_sensor:
      - name: "Schalter Tristan an kurz"
        state: 'on'
        auto_off: '0:00:01'
  - trigger:
      - device_id: b4e227b58f6eae9d5e471eff06cc42a0
        domain: deconz
        platform: device
        type: remote_button_short_press
        subtype: turn_off
    binary_sensor:
      - name: "Schalter Tristan aus kurz"
        state: 'on'
        auto_off: '0:00:01'
  - trigger:
      - device_id: b4e227b58f6eae9d5e471eff06cc42a0
        domain: deconz
        platform: device
        type: remote_button_long_press
        subtype: turn_on
    binary_sensor:
      - name: "Schalter Tristan an lang"
        state: 'on'
        auto_off: '0:00:01'
  - trigger:
      - device_id: b4e227b58f6eae9d5e471eff06cc42a0
        domain: deconz
        platform: device
        type: remote_button_long_press
        subtype: turn_off
    binary_sensor:
      - name: "Schalter Tristan aus lang"
        state: 'on'
        auto_off: '0:00:01'

I implemented the long and short press of my ikea button here. It seems to work much more instantaneous now (even if going through a template sensor is an additional step), thank you very much!