I got to about 9 months in lubuntu, but there were about 200 updates waiting when I checked. I’ve since moved across to debian. Currently I’m at 19 days 22 hours on debian. That was when I had to power down everything to tidy some cabling. Debian has been rock solid, there’s a docker update waiting so at some point I’ll run an update and probably reboot
Yes Proxmox is the base OS and you can then create whatever VM’s you want. You could install a VM and then HA supervised on that or you could even just create a HA OS VM which runs buildroot (instead of debian) just like if you installed HA OS on a RPi. Then if you needed it you could also add a Windows 10 VM… Pretty flexible.
Just so you know even with a docker update you don’t HAVE to reboot. I never do. I only reboot my NUC if I install a bios update or if there is a debian kernel update which requires a reboot to load.
I have a NUC running debian + HA supervised as well as a cheap chinese XCY mini PC I play with proxmox on it.
If you update docker you need to manually restart the supervisor service which will then start HA again. WHat doesn’t automatically restart is your addons so if you use MariaDB it can get tricky if you don’t reboot. (I edit my recorder config to comment out the url for mariadb, then I have a script to restart all my addons in HA, edit the url line and restart HA again then delete the database created). So it’s a few steps and maybe easier to just reboot the NUC but you don’t have to do this… (and on my system rebooting has it’s own issues with docker containers unrelated to HA starting up before a usb disk has been initialised and mapped to a share so restarting HA is my preferred option)
I found it easier to reboot as the ha containers don’t seem to start themselves back up. Doesn’t hurt to have the occasional reboot, only takes a few seconds.
Yeah it just causes issues with a USB HDD for me so I avoid doing that. I was just pointing out you don’t HAVE TO reboot to make it work again and I use a script to restart the addons in HA (a button on the desktop) so much simpler than having to unplug and replug USB map the drive etc, but whatever works for you
No worries. I’m glad I have mine running on an internal ssd. Is there anything you can do to get the usb drive to mount automatically?
Well it’s in fstab and should but doesn’t. I do use an ssd for HA etc but that external drive gets backups written too it. For some reason debian doesn’t see it on boot and then I have to physically unplug it and plug it in again and then it sees it and I can map it as per normal.
Your HA reboots each time it even thinks to have an update. 
So is your SLA requirements with the app or the hardware?
With hardware I went with an i7 quad-core, 8gb memory and SSD drive. I am running Windows 10 with HA running as 1 of 4 of my VMs on that machine as a headless box.
Last year stats:
- Windows 10 downtime hours (scheduled updates and 1 power loss for 30 min) - 8 hours
- HA downtime hours (updates, unexpected break changes and stability issues due to updates) - 8 days
You don’t need to reboot your computer, or a vm, for a home assistant update.
You have to reboot HA itself which is basically rebooting the VM. The amount of time for HA to come up from a VM start or a reboot is very much the same on my system.
Just no. You only have to restart home assistant.
2 Likes
Ugh apparently you don’t understand SLAs and what the term uptime means. Rebooting (or restarting as you say) results in downtime resulting in your system is not running.
restarting </> rebooting
My system continues to run, it is just home assistant that restarts. That is not the same as rebooting the machine (or restarting a VM).
I am not sure what you are asking, but the thread is about the wish to have a system that does not require rebooting.
Home assistant itself will run as long as you wish, but as I update to new versions of HA as they are released, there is a few seconds downtime for HA not the operating system when I update. Similarly if I change something in the setup which requires an HA restart. Those “things” are ever decreasing (which is a good reason to update, as they decrease in almost every release).
1 Like
Hi,
Anyone can advise how to install HA OS on Zotac ZBOX AD02? trying for a few days with no luck…
It just won’t boot from the SSD!!
I tried on the same PC and never got it to work.
I once used and old Zotac nettop, I’ve moved to a nuc about a year ago or so.
How are you trying to install?
Don’t try to install it with an sd card to the HD/SSD.
You well need to plug the Hass install drive in another machine and write the image haos_generic-x86-64-7.5.img.xz To the drive.
If you are doing this. . never mind =)
Hope it’s of help.
Thanks for your replies. 
I tried all ways on the net with no luck, the last status now is Debian with HA but HA Supervisor keeps saying “unsupported version…”
I am not an IT expert, mainly rely on YouTube videos to setup things, but I would like to have a stable low maintenance environment without the complications of networking and firewalls hassle of docker images having different IP addresses etc…
Currently I have 2 HA systems running on 2 VMs over Synology RS818+ (one for testing and one for production) but before I move to the clean production I would like to know which is better so I don’t do the moving again which requires time that I don’t have.
I moved from Rpi 4 to NUC one year ago.
My configuration (I have two similar instances for two different sites):
- NUC 8i5BEK2
- Samsung 860 Evo M.2
- memory: 8GB
- RfxTrx box
- Modem E3531 for SMS (in and out)
Reboot only when there is a new version of the HassOS… so about once a month… (keeping the OS up to date): HassOS 7.5
Restart HA when there is a new version (I am keeping HA up to date)…: HA 2022.3.7