My setup (hassio in docker on nuc) was running without hiccup for 4 month. Then I was updating. First HA, then, one by one the addons. Everything still working.
Next I updated Ubuntu packages. For that I had to reboot.
Hassio was no longer starting. Not knowing what to do (and needing the system running again), I reinstalled hassio. Now the hassio-supervisor.service was restarting every few seconds. Nothing was written to the homeassistant log.
Ultimately I renamed the configuration. Now hassio started from scratch (new user, etc) and I could reinstall from a backup (surprisingly that worked without changes to the configuration).
Differences:
- The configuration is now at
/root/snap/docker/common/hassio
. Before it was at /usr/share/hassio
. Unfortunately the new folder is readable only as root.
- Some addons (e.g. log viewer and visual studio code) are no longer working (fails with
nginx: [emerg] open() "/proc/1/fd/1" failed (13: Permission denied)
. Apparently that’s because my system now is not running the correct version of docker. Not sure why this is, as before the upgrade it was working. Perhaps updating the Ubuntu packages changed the docker (reinstalling docker per Be sure to install the official Docker-CE from the above listed URL did not help).
- Samba is no longer working.
- The configuration checker no longer works (prints the same warning endlessly):
[15:41:36] INFO: Please be patient, this might take a few minutes...
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x7fbb3fb81610>: Failed to establish a new connection: [Errno -3] Try again')': /simple/homeassistant/
All of these issues are doubtlessly due me making mistakes in the upgrade process. But, after all, clicking the update button in hassio seems like a rather logical (and innocent) action and should not break homeassistant. BTW: the process is surprisingly “un-automated”: run the configuration checker, do a backup, finally click the update button. And even then bad things can happen.
Maybe HassOS is more foolproof? E.g. since I cannot even install any software I cannot install (apparently that’s what I did?) the wrong version of docker!
Homeassistant has incredible features. It’s easy to start relying on it, once it’s configured.
Unfortunately I seem incapable of keeping the system running reliably. Since HassOS is touted as the easiest way of running homeassistant it is also foolproof (against fools like me)? However, from your responses I gather I’d need a dedicated computer just for HassOS.
Thanks and sorry for the rambling. I am a little frustrated and torn between awe and rm -f *
.