That was a little confusing because it seemed like it didn’t work and I would just get little black square pop up in the lower left: Failed to call service hassio.host_shutdown. undefined.
Several minutes later and half of the web UI is broken, like Energy, Map, Media. Other options sit on loading forever. Notifications > Dismiss: Failed to call service persistent_notification/dismiss. undefined. Stuff on Overview still seems to work, but maybe it’s just cached.
Really it did work, there was just no good feedback that it had shutdown. Reloading the webpage and getting nothing proved it.
Is this the only way to power off a headless Home Assistant Operating System instance from the web UI?
I think that Settings > System > Shutdown/Reboot would make a lot of sense. And better feedback at the shutdown location that it is or seems to be shutdown.
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
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?
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.
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.
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.