It (should) automatically restart on its own.
I know that it should. The trouble is that I have no idea how to diagnose whatās wrong when it does not ā¦
I ended up reinstalling ubuntu and setting up everything from scratch. Rediculous but took less time than to figure out a fix (how?). Working for now and I can restart HA from the gui. Have not dared to reboot yet.
Itās terrific when it works, but a bit challenging when it does not. I am not ready to look at the code.
My next problem is āesphomeā. According to the log, it gets installed, but then it does not show up in the dashboard. I know, it should. And I have waited. All day ā¦
I did everything like OP but when i saw the instalation of hassio (this splash with 20min timer) after this It needs to create a user. When i type Name, login and password site reloaded and i type it again and again and it is not moving forward. What i need to do?
I actually no longer run hass.io Iāve switched over to home assistant running in a docker. I think itās better that way
Iāve got a really weird issue on my NUC.
When i restart hassio, my Ubuntu also suddenly reboots. Anyone else had this issue?
sure youre not restarting the host?
Hi David,
Maybe I am!
Iām just going to hass.io menu - System - Reboot (Host System) - does that actually cause ubuntu to restart? I just want to restart hassio to take on config changes, should I do something else to achieve this?
Thanks,
Mat.
well reboot HOST isā¦ surprise surprise going to REBOOT THE HOST!
you want to use the restart server option from configurationā¦ NOT hassio > systemā¦ go to configurationā¦
hahah sorry! I only ever used a RPi before this so didnāt realise this is what is does. Thankyou for correcting me
Generally the very last thing you want to do is reboot the host. As well as taking more time, if you made a tiny error in config yaml HA wonāt restart! With restart server, it wonāt restart and will put an error in the log if there is any error s you can correct that before you restart. My NUC has been up for 20 days currently and the last reboot was 70 days up. I only rebooted it because I loaded a bios upgrade and updated the debian distro. By contrast, Iāve restarted Home Assistant hundreds of timesā¦
Has anyone had issues with running low on disk space. I am running HASSIO in docker on Ubuntu 18.04 on Unraid VM. My HASSIO disk is showing over 90%. Has anyone tried the "docker system prune " command ?
I never realised this, and have had exactly that issue before on the Pi. Thanks for explaining this. Just migrated to a NUC now and am enjoying the performance already.
Please, excuse my ignorance, but why would one need 2 sshās to the same machine? One for hassio and one for Ubuntu? If I need to do something inside hassio, I can access the hassio CLI through portainer or I can use the docker exec
command, right? Or am I missing something?
BTW, I migrated from raspberry to docker running on my retired work laptop (Ubuntu server 18.4.2 LTS, Lenovo T61, C2D, 4 GB RAMM, 256 GB SSD). I run a standard home-assistant image, all the previous plugins are now separate containers (configurator, mosquitto, node-red, tasmoadmin, ESPhome, grafana, influxdbā¦). There are more than 15 containers running, no performace issues. As my āhome OSā is Linux, I ditched samba and use NFS instead, a huuuge improvement! All permanent storage volumes are redirected to one directory on the server, which is then shared via NFS to my /home directory. So convenientā¦
Package docker-ce is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package ādocker-ceā has no installation candidate
The stable version of docker for Ubuntu 19.04 doesnāt exist yet. You can use this guide to use the edge / test
version.
This command did not work for me (Unbuntu 18.04 on Minix Z83-4). Gave ema ānot foundā error of some sort.
But this command did:
curl -sL āhttps://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.shā | bash -s
I donāt recommend this method now.
I think itās better to install Ubuntu then docker then home assistant (rather than hass.io).
This does mean you canāt use the hass.io backup feature though, but you can manually back up or download another docker that does the backups and upgrading for you.
Why the change in approach? Whatās the benefits/downsides from your original recommendations - asking as I was planning to grab an old laptop and move my install into an Ubuntu environment (following Frencks simplified instruction set as heās written the bash script)
Could someone provide a bit more detail on Portainer upgrades using the GUI? Hereās what the doc says:
If youāre running Portainer as a container, itās simply a matter of Docker image version. Just stop your existing
Portainer container, pull the latest portainer/portainer image and create a new Portainer container (using the same
options you used to create the previous one).
I need more direction. Thanks.
Another conversation about this over here: My steps to success for Hass.io on Intel NUC
Hope it helps!