Hi,
Probably stupid question but I’m running hass.io on docker with host an ubuntu server.
I guess the proper libraries for BT are not needed when installing hass.io on a raspberry pi with hassos as host. But in my setup docker, ubuntu in a NUC i should install them on host right? I’m trying to get Eddystone Beacons to work.
/D
I don’t know if they ever fixed Bluetooth on hassio, but assuming you have bluez and bluetoothctl installed and the device shows up, it will get passed through to the docker container. Bluetooth is a network adapter so when hassio is configured, it’s set to --network-mode=host which passes through all networking
Totally missed to enable my bluetooth in my host 
Now it is up and running, I’m not entirely sure how to make work with hass.io on docker.
If it’s working on the host and you’ve restarted hassio, it should just work as a Bluetooth tracker. Just enable it.
I run normal docker (not hassio) on my NUC and Bluetooth tracking works just fine.
Just tried to scan BT devices from the console and seems to work fine, I’m wondering if the problem is that eddystone is a ble device and that’s why the configuration in home assistant is not working. I’ll try the bt tracker to see if that one is working fine.
BT device tracking seems to work fine so it seems that I have trouble connecting to the eddystone beacon
HI There, can anyone lend a hand? I have hassio running in docker on open media vault for testing puposes. So far so good. I’ve just connected a bluetooth usb adapter and I can scan for devices from the command line from omv. But I cannot seem to get the adapter working with hassio. I’ve restarted the machine several time and it still says invaild config when hassio restarts, aftwr adding the bluetooth device tracker in the config. Is there something else I’m missing??
By default a docker container won’t be able to read any host devices unless they are exposed explicitly.
Try something like --device=/dev/ttyUSB0 when using a docker commandline or
devices:
- "/dev/ttyUSB0"
when using docker compose. Replace ttyUSB0 with the correct USB device mapping.
Thanks will give that a try