Presence Detection change triggering at Home Assistant Reboot?

I have a few automations that start when I arrive home. I use OpenWRT to assess if a phone connects to the WiFi router. Thus, an individual moves from “not_home” to “home.” This works well for the most part, however it annoyingly is triggered each time HA is rebooted. How do I write a condition that limits the automation when proximate to a reboot?

Example:

alias: Alerts when Arrive Home - Vacuum, Windows, Dog, Washer, Dryer
description: "Alerts when arrive home"
trigger:
  - platform: state
    entity_id:
      - person.user
    from: not_home
    to: home
    for:
      hours: 0
      minutes: 1
      seconds: 0
condition: []
action:
  - ...
1 Like

Show your automation.

See above. I’m not sure how it will help, but at least you may understand what I’m talking about.

Grave digging here, but has anyone managed to understand this?

image

I was never detected as away, so I don’t understand why does this trigger the automation?

platform: state
entity_id:
  - person.x
id: X Came Home
to: home
from: not_home

Grave digging is sometimes rewarded! I was able to block many automations triggered by a change from the unknown state at reboot using a template binary sensor for startup as a condition for the automation (“Starting Up” must be off). Although I can’t find it, I think it used to be an example on this page of the home assistant documentation years ago.

#binary_sensors
template:
  - trigger:
      - platform: homeassistant
        event: start
    binary_sensor:
      - name: "Starting Up"
        state: "true"
        auto_off:
          seconds: 250

Very nice!

Any ideas how to create it via GUI? This doesn’t seem to be working:

Edit: baah screw it, it can sit in the templates.yaml file.

1 Like