Adjacent question: is there a compelling reason to run HAOS? I run my HA setup in docker on a Proxmox CT, using Portainer/Watchtower to manage, so genuinely wondering if there would be benefits I’m missing out on.
The add-on store that’s managed and updated via the supervisor. It does the same thing as your setup, but integrates into HA nicer (automatic connectivity to HA for the containers, when they need it). If you’re happy with how your setup works then there’s no compelling reason to switch.
Ah, gotcha. Thanks for that.
You can’t restore a backed-up config in docker, also no add-ons.
Interesting about the backups bit. The functionality’s there in the UI to create backups, so kinda weird you can’t restore them. Like most docker containers, my HA config sits on a bind mount, and I just back that up nightly.
When you say add-ons, are there specific ones I’m missing out on? I have HACS, and frequently install all manner of integrations and front-end Lovelace add-ons.
“Add-ons” is a separate category of thing, and more substantial than integrations/Lovelace stuff. If you haven’t noticed any missing you’re probably fine. But some popular ones are DuckDNS and Mosquitto Broker.
Ah, got it. Thanks - this makes a lot of sense now. Looks like it’s so the HAOS Supervisor container can manage all the things that, in theory, I already handle myself with external tools.
Cheers!
Usually, the reason is HACS
Sorry - not sure what you mean? I use HACS in my setup. Are there extra features in HACS when running HAOS?
Not HACS - Addons. The ones that run in containers
Whew! I think I dodged the bullet. Upgraded today and it boots just fine. Running HAOS in a vm, so that might be the reason…
Same here.
HAOS on bare metal x86_64 here. No issues to report
I’m running 12.2 on “unsupported hardware” (x86 proxmox) without a problem.
So am I, no hiccups whatsoever.
How did the test suite miss this?
My guess is the massive amount of hardware variations, you would need a house full of devices to test all the different options
This is why we hear about this same thing happening with Linux distros all the time.
No problem here for either of mine - kvm for one, Raspberry pi 3b for the other.
Lol, and the project is slowly trying to force everyone to use it. I’ll continue to use core in a venv and manage my own OS, thanks.
