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.

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

You can also run hass os in a vm then you still get add-ons, from what I understand

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.

@unknowing8343

I used the fanciest possible setup with HA running in a Kubernetes cluster and its helper services likewise, but that’s severe overkill for most people unless they’ve got compute to burn and need/want/enjoy customizing the heck out of everything.

A Pi, even a Pi 4, isn’t compute to burn but also isn’t expensive enough to need other services on it to justify it. For what it’s worth, I’d suggest HA OS and dedicating the Pi to it.

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

Running it on a bare Pi, HAOS, imho you get the most performance, and support if it goes wrong.

Running on more powerful hardware (x64 host), VM all the way. It’s so much easier when you can snapshot, move VMs around, and split out components when needed.

You can also run hass os in a vm then you still get add-ons, from what I understand

I’d always run HAOS. When you need Docker containers which are not available as add-ons I would look for a machine that can run Proxmox so you can run a Docker VM and a HAOS vm in parallel.

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.