#Voice PE triggers Button Press event on boot

1 messages · Page 1 of 1 (latest)

regal glacier
#

Don't know if anyone else has figured out a good way around this yet, but it seems that the Voice PE triggers the button press event when it's powered back on and connects to HA.

This means that the automation for whatever the last button press event type was (double_press, long_press, triple_press) is triggering every time I unplug the device and plug it back in again.

My automations are set up in the way recommended by the Voice PE Docs:

entity_id:
  - event.bedside_voice_button_press```

```condition: state
entity_id: event.bedside_voice_button_press
attribute: event_type
state: double_press
................```
compact sierra
# regal glacier Don't know if anyone else has figured out a good way around this yet, but it see...

this is a known issue. its because when the "event" entity comes up it fires its last known event without checking if its stale.
you can check if its stale in your automation.
there is an issue open HERE

first comment is an example on checking if its stale by seeing if the event is older than 10 seconds

GitHub

The problem If you unplug Voice PE and restore power, when it re-connects, HA will execute the long press automation if one is configured. This has also been observed in brief connection outages (i...

#

so adding this condition should work for you i think:

  - condition: template
    value_template: >-
      {{ (now() - as_datetime(states('event.bedside_voice_button_press')) ) <
      timedelta(seconds=10) }}