I go the container route, and have only had one issue: allowing HA to access my system's Bluetooth adapter. I had some ESP32s lying around, so I used ESPHome to make a Bluetooth proxy, which solved that issue.

I don't run addons though, which might be part of it.

▲

ryukoposting 2 hours ago | parent | next [-]

Interesting. I also run HA in a container and getting it to pick up my Zigbee dongle was so easy I don't even remember how I did it.

I haven't tried BT, but my HA box lives underneath a couch with a big steel pull-out bed so I don't imagine it would work very well anyway.

	▲	paranoidrobot 2 hours ago \| parent \| next [-]
		I haven't done it either. But it should just be a case of passing the device to the container. You might need to disable the host from using it and pass admin rights to the container too. But it was also quite easy to pass a USB device to the HAOS VM in Proxmox.
	▲	93n 2 hours ago \| parent \| prev [-]
		The host I run HA on is Ubuntu server. If memory serves me right, the Bluetooth issue was related to apparmor and dbus restrictions on docker

▲

paranoidrobot 2 hours ago | parent | prev [-]

Add-ons (now apps) can't be done without HAOS. It's one of those non-obvious things.

There's other things I forget which are also more difficult/annoying to manage on the container version.

I have a rather large docker compose stack so my first experiments with HA were as running it there.

That lasted maybe a week before I went and ran it as a VM instead.

▲

tjoff an hour ago | parent [-]

Apps/add-ons is just another container, so you can add them manually in the compose file.

	▲	93n an hour ago \| parent [-]
		Yep, I run esphome in a separate stack w/o issues.