Lately restarts of HA are not reliable. When I SSH into the host I see the logs there are no entries past:
If I reboot the host entirely everything comes up.
Lately restarts of HA are not reliable. When I SSH into the host I see the logs there are no entries past:
If I reboot the host entirely everything comes up.
I think restart of HA from within HA has always been a little hit or miss.
It may have gotten better but I ultimatlly prefer host reboot for RasPi/Hass.io. If docker I would restart container(s).
In Hass.io you may reboot server host from side panel>>Hass.io>>“system” tab>>“Host System” panel>>{reboot}
if reboot of host is OK maybe use that.
Someone on these forums once told me that a reboot of the host should be a rarity, not a regular occurrence, I was operating on that mindset.
Not sure how to restart a container from HassCLI (i though that’s that the restart did)
this is pi or linux server?
Pi3+ /extracharacterssoIcanreply
no need restart container. just restart host from within HA GUI
EDIT
the restart issue you have may be component/integration dependant.
I have (2) RasPis and restart all the time without issue but these only control <3 devices or sensors. I run large install on linux server in docker and restart works mostly but occasionally not so this I just restart container.
Unplugging power to reboot RasPi is likely what you refer to before and how most people reboot those and that WILL cause an issue for you. Rebooting RasPi properly does not cause error in my experience.
When I have issues, I SSH into the host (the ssh add-on allows connection even when HASS is hung or restarting) and issue the hassio host reboot command.