Any how, I can’t get my BT-500 Adapter passed to the docker of home assistant. While it works fine for the zigbee dongle, I can’t see any device in /dev for the BT stick…
This stuff should work by default, and if you care about risk, then create an option for it to be able to detect BT devices…
Is there a any normal way of adding BT to a container then? I want to add plenty of BT sensors to HA and this helds me back, I dont want to create a VM, I want to keep using the docker…
How did you get it to work for the zigbee dongle???
In general VMs and LXC (instances) provide better access to physical resources…
The zigbee device is detected and listed with /Dev/ttyUSB0
The BT dongle only shows on lsusb.
As far as I know, this devices are not initialized due to missing components, basic Bluetooth stuff. Else it should show up in /dev
I bought BT sticks which should be supported in Debian by default, so I think that’s a made decision. Only passing to a VM may work, but that’s no option.
That also means I need to try a BT proxy in HA…
Yes, TrueNAS doesn’t include BT or Wifi drivers… it would have to be done at the App in Home Assistant. That may be why a LXC or VM is needed.
HAOS is recommended over container based deployment, anyway.
might be but the container with all shared resources working superb. No issues at all and the update and all is way more easy than the rather bad VM stuff on Truenas Scale.
well that should change in my eyes, at least by an option to enable the same. I think plenty users will only use their Nas even with Wifi… even I thought about it and I do 2500Mbit = 281MB/s over wifi 7 between my Nas and my workstation
so… if it wants to be close to customers, Wifi and BT is a must, at least to be enabled … same as SSH root access can be enabled
I run it on CORE in a VM and we use only the HAOS updater. No problem with that setup so far.
Isn’t SCALE/CE’s virtualisation supposed to be superior to FreeBSD’s? 
