4 ms·

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

by 93n 7mo ago

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 7mo ago
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 7mo ago
  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 7mo ago
  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 7mo ago
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 7mo ago
  Apps/add-ons is just another container, so you can add them manually in the compose file.
  - 93n 7mo ago
    Yep, I run esphome in a separate stack w/o issues.
- rickypp 7mo ago
  Yeah, I ended up buying a dedicated mini PC ($100 refurb) to install HAOS on. HA is pretty much useless without being able to run add-ons. I run everything on k8s in my home server, I don't have a VM system set up and didn't want to bother just for HA. It's funny, the pattern of a central application that uses docker containers to add plugins seems like a perfect fit for a Kubernetes Operator. I suppose it still misses out on some of the advantages of running everything "on metal" for integrating with physical components like USB dongles.
- dawnerd 7mo ago
  It's kind of silly since they're just containers it runs anyways. I'm sure there's other reasons. At least running it as a VM isn't too hard. Pretty easy to use their image and run from that.
zimpenfish 7mo ago
> I go the container route, and have only had one issue: allowing HA to access my system's Bluetooth adapter Even without running in a container, I had huge problems with Bluetooth on Linux (it would just ... stop then not reappear or it would only talk to half the devices but a different set of devices every other day, etc.) (This isn't specifically a HASS problem, mind; I've had countless problems with Linux Bluetooth since 2003 over many different iterations of hardware, OS and dongle.) > I used ESPHome to make a Bluetooth proxy, which solved that issue. Same. It's a great solution.

by 93n 7mo ago

ryukoposting 7mo ago

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 7mo ago
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 7mo ago
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 7mo ago

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 7mo ago
Apps/add-ons is just another container, so you can add them manually in the compose file.
- 93n 7mo ago
  Yep, I run esphome in a separate stack w/o issues.
rickypp 7mo ago
Yeah, I ended up buying a dedicated mini PC ($100 refurb) to install HAOS on. HA is pretty much useless without being able to run add-ons. I run everything on k8s in my home server, I don't have a VM system set up and didn't want to bother just for HA. It's funny, the pattern of a central application that uses docker containers to add plugins seems like a perfect fit for a Kubernetes Operator. I suppose it still misses out on some of the advantages of running everything "on metal" for integrating with physical components like USB dongles.
dawnerd 7mo ago
It's kind of silly since they're just containers it runs anyways. I'm sure there's other reasons. At least running it as a VM isn't too hard. Pretty easy to use their image and run from that.

zimpenfish 7mo ago

> I go the container route, and have only had one issue: allowing HA to access my system's Bluetooth adapter Even without running in a container, I had huge problems with Bluetooth on Linux (it would just ... stop then not reappear or it would only talk to half the devices but a different set of devices every other day, etc.) (This isn't specifically a HASS problem, mind; I've had countless problems with Linux Bluetooth since 2003 over many different iterations of hardware, OS and dongle.) > I used ESPHome to make a Bluetooth proxy, which solved that issue. Same. It's a great solution.