Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Bluetooth dongle docker issues

Featured Replies

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

  • Author

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

 

  • 3 weeks later...

Unraid does not have the drivers for BT dongles. See below

PS: i saw you posted there already. Just making more people aware of the problem by posting a followup here as well.

Edited by lewio

  • 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?

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.