Maintain stable state across HomeAssistant reboots

[TippyLion28]

Hi,

It would be helpful if the device state could remain stable across HA reboots. Currently, whenever HA is rebooted, the state is updated even if there has been no real world change.

The effect of this is that automations which trigger on device state changes will run when HA is rebooted, even though the device has not moved.

For instance, I have an automation which turns on my bedroom light when my phone arrives home. This triggered at 2am this morning because my HA machine rebooted to do some automatic updates, and the integration marked that event as a state change.

[TippyLion28]

Another way this could be solved is by changing the default state after a reboot from ‘Away’ to something more appropriate like ‘Unavailable’ or ‘Unknown’

[tomlut]

First of all you should rarely need to reboot the host machine. Did you perhaps just mean restarting Home Assistant?

Two very different things. Either way you can easily fix this yourself.

Change your trigger or add a condition. i.e. instead of just "to home" use "from away to home" and/or "not_ from: unavailable/unknown" also you can add an uptime condition to not trigger until 30s after a restart/reboot.

[TippyLion28]

you should rarely need to reboot the host machine

Says who? :D

Change your trigger or add a condition. i.e. instead of just "to home" use "from away to home" and/or "not_ from: unavailable/unknown“

I tried this approach. Unfortunately, the default state after a reboot seems to be “away”. This makes a reboot indistinguishable from my phone phone “arriving” home. If the default post-reboot state was “unavailable” or “unknown” then yes, this would be possible and would be a nice solution :)

also you can add an uptime condition to not trigger until 30s after a restart/reboot.

That’s one workaround, and if this issue doesn’t generate a response, it’s probably going to be the approach I go for :)

Thanks