If I am not mistaken the tradeoff is losing add-ons but being able to install other services.
So… what is your experience? Are add-ons useful/common for your use case?
I’m running the docker version as I’m also using the rpi for other things, like imageview and pi hole. I don’t really miss addons, the only annoying thing is that most documentation assumes you’re running ha os.
But if you don’t plan to use it for anything else than HA, I’d go for HA OS.
I run my own a VM.
I was sceptical about running in a OS that I can’t run my normal updates and automations on but HA OS has been rock solid and easy. Plus you get a few more features
I second that, I just put it in a VM on my proxmox host. zero issues so far.
I used a ton of AddOns, really practical because they also embed themselves easily into the rest of Home Assistant. I would go for the HA OS. But I also do wish there was a AddOn to install random docker images.
You can go supervised! You still have most of the operating system available to your needs and you can still use add-ons. I use it for years and it works like a charm
HA OS is the way to go.
You don’t want to have to think about it. HA OS just works. You set it up and let it run.
There’s no sense in trying to kerfuffle other things into it. You don’t want to do too much on the Pi anyway because it’ll lower the responsiveness of Home Assistant slightly. If you want a server that does things, buy a separate NAS and run it alongside HA OS.
This is what I do with a Pi running HAOS and a Synology ds920+ running backups and everything else. It’s been rock solid, gives me a decent backup solution, my home automation is stable and responsive and no-fuss, and plenty of options for tinkering. Highly recommend.
home assistant in docker is definitely not for the feint of heart! the networking requirements are actually quite intense, and really don’t map well to virtual networks like dockers uses
… among other issues
HAOS on a pi; i’ve tried the docker thing time and time again, and the next chance i get in blowing it all away and starting on real hardware again
I’ve run both, and the OS version is much more stable and easier to keep running. Whether you use an rpi or a VM, use the dedicated OS and save yourself the heartache of trying to get your hardware working with docker.
I recommend HA OS. What happened to me is that I used docker, got everything set up how I liked it, then had to move over to HA OS when I needed a specific add on and didn’t have any other solution.
If you don’t already have a plan for other services, might not make sense to use docker, too.
I definitely prefer HA in a VM, that way it can do its own thing and I won’t accidentally break something.
Home assistant OS is also my recommendation. Add-ons are pretty important IMO. Plus for something I am planning to try and have 100% uptime and controlling my home smart devices I don’t want it containerized and at the mercy of docker.
Currently using 15 add-ons myself.
I started out running HA in a docker container on a NUC (everything configured in a docker compose file). Documentation around everything was pretty poor at the time (I’m not sure if this has improved since then), so I ended up feeling too confused on where to even begin expanding from vanilla HA.
I ended up picking up a RPi 4 (and SSD and enclosure) and have been happily running HA OS since then on the Pi. If that ever fails on me, I may go back to a docker instance.
I’d recommend you try whichever is the most convenient first (probably the docker approach, unless you already have the Pi on hand). Give it a month or two, try to setup up a few things you’re interested in, and then decide if you’re satisfied with that setup or want to try the other option.
I run HA OS and from my experience updating and installing add-ons is seamless. Creating backups and restoring (had to replace a corrupt SD Card a while ago) was also no issue.
Add-ons I have installed- Advanced SSH Terminal
- ESP Home
- Home Assistant Google Drive Backup
- VS Code Server
- Maria DB
HACS for a few integrations:
- YT Music Player
- Waste Collection Schedule
nothing too fancy.
I run a second Pi with an SSD for docker containers or native OS installs (gitea, drone-ci, pi-hole, etc.)
I’m running Supervised in Docker. I don’t know how I managed to do it but it wasn’t hard. I use addons, and also have other things running on my Pi
There’s nothing that you can’t do with docker that you can do with addons, but many things you can do with docker that you can’t do with addons.
Addons are marginally easier to setup but if you have technical skills, docker is also not a lot of work. You can use something like Portainer to get a similar easy interface. So I think it’s down to if you have the technical skills for docker.
I run ha supervised and I do both, but the system does complain that I do that.
I have HA running in docker on a Pi 3 and Z-wave JS running in another on the same Pi. Added a purpleair integration for outdoor air quality, national weather service, some local sensors, and sql to get data from another node. People have made me paranoid about SD card failures, so I regularly image it to my main server. I mostly use HA to visualize environmental data, but it also runs the lights in a hydroponic farm and the house during vacations, via z-wave outlets. Have not tried to integrate it with google or amazon.
The only inconveniences I’ve found with docker is that you can’t restart HA from its web interface and, if you update regularly, old images quickly fill a smaller card, so you have to remember to purge.
It’s now possible to restart HA from the web interface. P
I pulled the latest HA version based on you comment in this old thread, and you’re right! There is a restart button now. Thanks.