#Home Assistant Voice PE Follows Long Press Automation if Power or Internet is Removed

1 messages · Page 1 of 1 (latest)

nocturne geyser
#

I've been on Home Assistant PE for a while now (9 devices) and I've noticed a strange behavior that I can now easily reproduce. I believe it's a bug but I can't find anybody else talking about it. It happens on all my Home Assistant PE devices consistently. Here's my observation:

Background: All my Home Assistant PEs have a long press automation. In every room, the long press automation turns off all the lights and in some cases also closes shades/curtains.

Observation: If I unplug a Home Assistant PE and plug it back in, as soon as it connects, it follows the long press automation path. I discovered this when I was tidying wires after initial install and the lights kept turning off without explanation. It's consistent every time across all the devices that have a long press automation configured. This has been happening for weeks but I didn't report it because how often am I really unplugging these devices.

Yesterday, I observed a different behavior. NOT during a home assistant reboot, the red ring flashed only briefly (like when it can't communicate with HA) and then it shut off everything in the room. My guess is the connection was briefly interrupted (indicated by the brief red ring) and then followed the long press automation path when the connection was restored. I had noticed this happening before yesterday but yesterday was the first time I was actually looking at the device when it behaved this way and I can confirm that's what's going on.

The net of both these scenarios is that whenever Home Assistant PE connection is restored (either by internet or power) it's choosing to follow the long press automation path and I don't know why. When I reboot Home Assistant, this behavior is NOT observed and it's likely because Home Assistant isn't completely up and can't execute the long press automation.

Is there somewhere I should report this bug to?

ornate yacht
#

Did you alter the default firmware on PE? E.g. adopted it and changed YAML?

umbral silo
nocturne geyser
ornate yacht
nocturne geyser
umbral silo
#

i am trying to work out if its the voice-pe or if its core thats the problem

#

I think its core actually

umbral silo
ornate yacht
umbral silo
#

there is an event recognised but the time on the event is old

#

i have a work around

#

if you add a templated condition to check to see if the event that triggered is younger than 10 seconds it solves the issue

# 
description: ""
triggers:
  - trigger: state
    entity_id:
      - event.mk_room_voice_button_press
conditions:
  - condition: state
    entity_id: event.mk_room_voice_button_press
    attribute: event_type
    state: long_press
    enabled: true
  - condition: template
    value_template: >-
      {{ (now() - as_datetime(states('event.mk_room_voice_button_press')) ) <
      timedelta(seconds=10) }}
actions:
  - action: tts.speak
    metadata: {}
    data:
      cache: true
      media_player_entity_id: media_player.mk_room_voice_media_player
      message: long press
    target:
      entity_id: tts.piper
mode: single
#

i think its home assistant seeing the event entity be "active" when it comes up and treats it as an event even though its old

ornate yacht
umbral silo
#

@ornate yacht maybe it could be fixed in firmware by the PE setting to a blank event when it comes up but it feels like the event should not be triggering.
@nocturne geyser if you make an issue in core ill post my findings there

nocturne geyser
#

i'm working on the issue now

nocturne geyser
umbral silo
nocturne geyser
#

Thanks for your help, gents!