Bluetooth dongle docker issues


Recommended Posts

I'm having big issues trying to pass through my bluetooth dongle to docker containers, I'm using homeassistant and it spits a nice error for me:

Error setting up platform bluetooth_tracker
Traceback (most recent call last):
  File "/usr/src/app/homeassistant/components/device_tracker/__init__.py", line 183, in async_setup_platform
    disc_info)
  File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/app/homeassistant/components/device_tracker/bluetooth_tracker.py", line 72, in setup_scanner
    for dev in discover_devices():
  File "/usr/src/app/homeassistant/components/device_tracker/bluetooth_tracker.py", line 50, in discover_devices
    lookup_class=False)
  File "/config/deps/lib/python3.6/site-packages/bluetooth/bluez.py", line 26, in discover_devices
    device_id = _bt.hci_get_route()
OSError: [Errno 97] Address family not supported by protocol

 

I have --net=host as a an extra parameter which I understand should just pass through all usb devices. 

 

Does anyone have suggestions on how I could test whether or not the dongle is actually being passed to all dockers or not?

 

Thanks

Link to comment

After a bit more digging I've done the following:


root@Sven:~# lsusb
Bus 003 Device 010: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

added 

--device=/dev/bus/usb/003/010

to my extra parameters, no change.

 

From within the docker container

root@Sven:/usr/src/app# bluetoothd -n
bluetoothd[133]: Bluetooth daemon 5.43
D-Bus setup failed: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
bluetoothd[133]: Unable to get on D-Bus

Not sure what that means

root@Sven:/usr/src/app# lsmod | grep bt
ebtable_filter         16384  0
ebtables               32768  1 ebtable_filter

This shows there is a lack of BT devices?

 

root@Sven:/usr/src/app# hcitool scan
Device is not available: Address family not supported by protocol

 

Link to comment
  • 3 weeks later...
  • 8 months later...

I got the same problem with a VM running home assistant (hassio). Can't figure out if its a unraid or hassio problem. If its a VM with the dongle passed trough, it should not matter if unraid has drivers?
I also tried the current beta of unraid.

Any ideas?

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.