With the new Settings, I can’ find where to simply reboot Core vs rebooting the entire host OS. This was a very hadny way to fix a lot of little “issues” much more quickly than rebooting the host machine.
Was this removed, or am I just missing it somewhere in the new settings?
and it automatically triggers a check configuration before it does… That said i prefer to go to dev tools (where the yaml reload moved to) and check configuration myself before hitting restart
I don’t understand what’s gone on with HA OS since the last time I used it. Made things harder to find not simplifying it. This along with moving the YAML check had me scratching my head! What’s the point of the Hardware system menu just to hide one of the most common features of any OS like reboot and shutdown!
I didn’t read this whole thread, so I’m sorry if this is repeated information.
In case anyone is having trouble in version 2022.12.2 (frontend version 20221208.0)…
NOOOOOW, it’s Settings → System → Hardware and then the hotdog menu in the top-right has a “reboot system” and a “shutdown system” option.
Like so many other people I am getting tired of how quickly they are changing the interface. If we aren’t looking at the management interface ALL THE TIME, we have to relearn it.
Ideally, you set these things up and rarely touch the backend when you add the occasional device. Unfortunately, Home Assistant, or one random device or service flakes out for no reason and has to be reconnected, readded, reconfigured or something fairly regularly (seems like I’m logging in to fix something about once a month or better…
It’s frustrating enough to have to login and delete and re-add all of my ring devices and rebuild every automation that uses them because I had a power failure. It’s far worse when I have to find everything in a new interface that hasn’t added anything, but just relocated everything.
These are still there in my case. However I will mention that I just recently switched from a Python Venv installation to a full blown HA (HassOS, etc.) installation, and the Python venv installation did not have the reboot options.