Thanks, that finally did the trick! Most of the stuff above was just not where it was supposed to be 
Iâm new to Home Assistant so it took me a minute looking for System to realize it was in the Settings (gear icon) menu.
Settings > System > Hardware (URL: /config/hardware)
Iâm using Home Assistant Operating System on Raspberry PI, Home Assistant Core version 2022.7.3.
Thank you! Much simpler than running the command.
3 Likes
Congratulations to the HA-Team!Under config/hardware it just show a picture of my RPi4 but no buttons.
So cant see how I shutdown HA safely?
Re Dave
Wow! I would never have thought to look in the expanded menu in the right-hand corner!
Thank you for showing us!!
-Todd
1 Like
I have installed Home assistant 3 times with the vmdk file from here:
As I could not find how to switch off correctly, I shut down the server with : host shutdown
And when I stated the VM again the host is shown but no connection in the browser.
Reason was somehow explained above.
So I donât want to set up the VM again and now
LOCKING for CORRECT way to shut this thing off and be able to restart it working
When I got intuitively to:
Settings > System > Hardware as described above, i have the following:
What to shut down first?
Following the above, it is nearly clear that it has to be:
shutdown core
â âcore stopâ
and after that
shutdown host
â âhost shutdownâ
But My screen shows
pls see above because of
new user can onlyâŚ
What NOW?
Pls help a newbie to shut down the HomeAssistent
PS: Ahh! During writing, I can assume from all above that the command for
shutdown core
â âcore stopâ
Is clearly not in this section but somewhere else in the menu structure where Iâm sure normal user will find it again intuitively
But as Iâm new with this server stuff I gladly ask to pls advise me newbie To the Steps for:
Shutting down Home Assistant
that it does not destroy the whole VM or maybe do much more harm on my PC or the whole network or Internet when I make a mistake doing the shut-down procedure incorrectly
Many THX
To shutdown the SYSTEM, you should be using shutdown host. The core will be automatically shutdown as part of that operation. I donât understand why someone would shutdown the core first - I donât think you can actually issue a command to shutdown the host (from the UI) after you have shutdown the core, because presumably the websocket connection is closed when the core is closed?
1 Like
THX, but I donât know how to
shutdown the core
Pls be so kind and tell me the secret
I can tell you a very easy way to shutdown the core, but be warned - once you have done it - the only way to restart it is to connect to the server with SSH, or connect a keyboard and monitor to the machine and type ha core start
The easiest way to stop the core, is to click on the Dashboard and press c on the keyboard and type stop and choose Stop Server
EDIT: I think we would ALL really like to know WHY you want to shutdown the core, but not the host machine.
PhuâŚ
Al I want is to be able to turn off my VM with Homeassistent. ( without destroying the whole machine as it happened in the last 3 times)
&
Be able to start it again and lock in with browser.
1 Like
Then you should probably file a bug report. I can shutdown my Home Assistant VM directly from Proxmox without having to do anything inside Home Assistant first. When you tell a machine (real or virtual) to shutdown, it will shutdown all the docker containers, before it actually properly shuts down. There is absolutely no reason it should be corrupting your disk image.
I Have it on VM Workstation without VM ware tools.
Following You, I simply should turn the VM OFF
Right
Yes, when you issue the shutdown guest command - you should see the Home Assistant VM respond by stating it is stopping services etc. âPower Offâ and âResetâ are the commands more likely to break things. But even then, the worst that should happen is that it could corrupt the sqlite database - nothing you do should actually break the machine to the extent that Home Assistant wonât boot up.
1 Like
WORX
Many THX
1 Like
An example of why, in the case of a Supervised install, is to carry out OS updates. Presumably this is better done when HA is not running. Restart HA after updates are complete which may involve a reboot.
For what itâs worth, when I was running a supervised install on a Proxmox machine -
I did updates of the VM running Home Assistant Supervised, and updates on Proxmox itself, without ever stopping Home Assistant.
If the VM update updated Docker, then Home Assistant would be stopped and restarted by the OS as part of the Docker update without me having to manually stop Home Assistant.
If the Proxmox update, updated the QMEU software, then Proxmox would gracefully stop all running machines before updating the software, and then restart them again afterwards.
I have rarely ever had to reboot the VM running Home Assistant.
Mineâs not running in VM so my take on this is that I am better off stopping HA before doing updates to ensure things donât get corrupted. YMMV.
I landed on this post because my Settings - System - Hardware screen is totally blank except for the 3-dot pull-down menu in the top right corner. That seems odd but at least I found the Shut Down Host button.
1 Like
That makes sense. You donât really have any hardware to show any information for (mine just says Iâm using OVA) and Iâd assume the CPU and Memory graphs rely on the OSAgent Dbus stuff, which you may need to check if itâs requiring an update.
Edit: see if you are up to date: Releases ¡ home-assistant/os-agent ¡ GitHub
1 Like
Thanks. Updated from 1.2 to 1.4 but no change to blank hardware screen so I guess thatâs the way it is.
Whenever I had any issues (the reason I ultimately moved to Home Assistant OS, was because I was fed up of continuously having to deal with âSystem not healthyâ) - I used to re-run the supervised install script. That would fix most issues.