June 1, 20179 yr Hey guys! I have a docker instance of "Home-Assistant" where I'm already passing an USB device: /dev/ttyACM0 As you can see it creates the device above. However I have a USB Bluetooth device which it gets listed in lsusb (It's the Broadcom one) while the other is the Z-wave Z-Stick root@unBeast:~# lsusb Bus 003 Device 005: ID 0a5c:21ec Broadcom Corp. Bus 003 Device 002: ID 0658:0200 Sigma Designs, Inc. But for this bluetooth device I'm not getting an appropriate "/dev" device. I've tried passing the bus and device ID to docker but it seems to not work or I'm not doing it correctly. Can anyone point me out in the right direction? Maybe it's not possible to pass it unless unRaid creates a "/dev" device and has the appropriate drivers to support it? Doing a `dmesg | grep Broadcom` is not showing up anything either. Connecting this USB bluetooth to a Raspberry Pi2 with Raspbian recognizes it without problems so it's clear that at least it works on Linux. Maybe I'm just doing wrong the passthrough thing to Docker Thanks for any help! Edited June 1, 20179 yr by bluepr0
June 1, 20179 yr Author Is this better suited for Docker forum? not sure if it should be moved there or need to be considered like something related to unRaid itself?
June 8, 20179 yr Drivers must be available for the host also to make it work in a docker container. If the device is listed in lsusb does not mean drivers are installed. Does the USB get a /dev entry on the RPI?
July 15, 20178 yr Did anyone figured out how to install bluetooth drivers to unRaid for using a BT Dongle in a Docker container?
August 9, 20187 yr I've been trying to figure out the same issue. Looking around, it looks like the primary issue is that there's not a Bluetooth driver for the Bluetooth dongle. Running usb-devices shows that the Broadcom device doesn't have drivers: Quote usb-devices T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 D : Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0a5c ProdID=21e8 Rev=01.12 S: Manufacturer=Broadcom Corp S: Product=BCM20702A0 S: SerialNumber=5CF3708ECDE6 C :#Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#=0x0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=(none) I: If#=0x1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=(none) I: If#=0x2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) I: If#=0x3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none) I've seen it suggested that btusb needs to be loaded, but there's no btusb module to load: Quote modprobe -v btusb modprobe: FATAL: Module btusb not found in directory /lib/modules/4.14.49-unRAID So, until Unraid supports Bluetooth on the host, there's no way to pass the device through to a docker container like Home Assistant. At least, that's as far as I've gotten. Anyone else have any better luck I"d love to know how you got it working. Edited August 9, 20187 yr by kmwoley
August 9, 20187 yr I've just been banging my head against the same issue for a few days, thank god I found your post @kmwoley, it gives me the exact answer that I was looking for! T: Bus=03 Lev=02 Prnt=03 Port=02 Cnt=01 Dev#= 10 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0a12 ProdID=0001 Rev=88.91 S: Product=CSR8510 A10 C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=(none) I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=(none) root@Sven:/dev# modprobe -v btusb modprobe: FATAL: Module btusb not found in directory /lib/modules/4.14.13-unRAID Now we just need some smart cookie to come up with a solution to the issue.
August 10, 20187 yr @limetechi - is there any way to install bluetooth drivers on the unRAID host? Any hope of getting them included as part of a future release.?This is blocking one of the larger scenarios I intended to use my unRAID server for (Home Assistant using a Bluetooth dongle to detect who's home/away).
August 13, 20187 yr You should add it as a feature request or else it's lost in the forum. In the mean time, you could make a VM and pass through the USB.
Archived
This topic is now archived and is closed to further replies.