#Away Automation didn't trigger because not_home condition didn't match.

1 messages · Page 1 of 1 (latest)

lavish raven
#

I have a state trigger for an away automation, but it failed to trigger because one of us was in a "Work" zone and it didn't match "not_home" condition. Do I have this misconfigured?

Here is the step from the trace:

Executed: December 4, 2024 at 9:16:23 AM
Result:

result: false
state: Work - Larry
wanted_state: not_home

alias: Away Automation
description: ''
triggers:
  - trigger: state
    entity_id:
      - person.larry
      - person.moe
      - person.curly
    from: home
    to: not_home
    for:
      hours: 0
      minutes: 3
      seconds: 0
conditions:
  - condition: state
    entity_id: person.larry
    state: not_home
  - condition: state
    entity_id: person.moe
    state: not_home
  - condition: state
    entity_id: person.curly
    state: not_home
storm blade
#

Yes, not_home is badly named. It really means "not in any defined zone"

lavish raven
#

Is there a proper state I should use? not_home is what was applied when using "Away" on the automation gui.

storm blade
#

You probably want:

conditions:
  not:
    - condition: state
      entity_id: person.larry
      state: home
    - condition: state
      entity_id: person.moe
      state: home
    - condition: state
      entity_id: person.curly
      state: home
lavish raven
#

I'll give that a shot

lavish raven
#

how can I do the same for the trigger "to: (anywhere but home)"

#

is it not_to: home?

storm blade