Chuck Claunch

Thanks a ton @JorgeB the steps you outlined worked perfectly 👍

Ok thanks! will give this a try this evening

Ok so just so I'm clear, if I disable Docker/VM services I won't lose all that data? Will it just go over to the main pool?

Here ya go unraid-diagnostics-20210825-0707.zip

I used to run with two cache drives, a Samsung 830 and a PNY, both SSDs. I decided I didn't need both as cache devices anymore and removed the PNY drive as cache. It now shows up in unassigned devices (along with a busted jpg icon). If I physically remove the PNY drive from my system, my remaining Samsung cache drive says unreadable. If I physically put the PNY drive back in, the Samsung cache drive is readable again and the PNY drive still shows up in unassigned devices with the busted icon. See screenshot. How can I release this drive so I can remove it and not lose my cache contents? All of my docker and VM configs are on this and they're totally missing if I boot without the PNY drive (and Samsung cache drive says unreadable).

One note in my example above vs what I do now is I just pass the entire usb bus in. so instead of passing `/dev/bus/usb/001/006` or whatever I pass `/dev/bus/usb`. Makes it a lot easier and even works passing into multiple containers if you're brave enough (or at least only doing read only stuff).

If you just need to use the device in a docker or VM, you can just pass in the entire usb bus. No need to have the BT drivers in the main unraid instance. See my comment above: I've been using bluetooth in a docker for node-red for about six months with no issues.

For what it's worth, I verified that my post above does work. I built a Node-RED docker including Noble (a Bluetooth Low Energy scanning node) and was able to pass in the Bluetooth dongle using the instructions above, even without having the dongle's firmware on the host. That said, obviously it'd be nice to pass it by a proper name e.g. /dev/hci0 So it'd still be nice to add that large chunk of various manufacturer's firwmare I posted.

After messing with this for a bit I realized I could in fact pass the specific USB bluetooth device as yayitazale attempted above. The key was to pass it as a path. Instead of doing --device='/dev/bus/usb/001/006' Pass that device as a path with read/write access and make the container privileged. So under your docker container settings, add a path and enter the device path into both the host and container path values and make it read/write: More specific to the home assistant docker container, it did not start up with the device running so I had to start it. To do that, first run hciconfig (Bluetooth MAC addresses obscured to protect the innocent): # hciconfig hci0: Type: Primary Bus: USB BD Address: XX:XX:XX:XX:XX:XX ACL MTU: 1021:8 SCO MTU: 64:1 DOWN RX bytes:1609 acl:0 sco:0 events:74 errors:0 TX bytes:777 acl:0 sco:0 commands:70 errors:0 So we see hci0 is there but is down, so issue the up command: # hciconfig hci0 up # hciconfig hci0: Type: Primary Bus: USB BD Address: XX:XX:XX:XX:XX:XX ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING RX bytes:2183 acl:0 sco:0 events:104 errors:0 TX bytes:1145 acl:0 sco:0 commands:100 errors:0 And now with a subsequent hciconfig command see the device is running. So now we can do stuff like lescan: # hcitool lescan LE Scan ... XX:XX:XX:XX:XX:XX bhyve_XXXXXX XX:XX:XX:XX:XX:XX (unknown) XX:XX:XX:XX:XX:XX (unknown) XX:XX:XX:XX:XX:XX (unknown) I haven't gone as far as to get bluetooth devices reading in home assistant yet, but at least this proves that the device can be passed to the docker from unraid regardless of whether the firmware file is there.

I have the same missing firmware issue except it's BCM20702A1-0a5c-21ec.hcd Is there no way for me to manually get this file in there like a normal linux system? I found a repository of various broadcom firmware files here which has a huge chunk of them.