August 8, 20223 yr 1 hour ago, Jaburges said: @L0rdRaidenI've updated the firmware files, and the boot config - so the firmware and config files load. Added the Nerd-pack to get BlueZ and i'm able to run `hciconfig` on the host AND the docker. I'm passing the DBus & the device through /dev/bus/usb/XXX/XXX the error I get now is: Failed to start Bluetooth: [org.freedesktop.DBus.Error.ServiceUnknown] The name org.bluez was not provided by any .service files UGH - fixed it by simply restarting bluetooth on the host /etc/rc.d/rc.bluetooth start SO Bluetooth dongle is being passed through, and the integration works - range isnt great though I've tried increasing the range on the Lock side, but just ordered a USB extension cable
January 12, 20233 yr On 8/8/2022 at 10:59 PM, Jaburges said: @L0rdRaidenI've updated the firmware files, and the boot config - so the firmware and config files load. Added the Nerd-pack to get BlueZ and i'm able to run `hciconfig` on the host AND the docker. I'm passing the DBus & the device through /dev/bus/usb/XXX/XXX the error I get now is: Failed to start Bluetooth: [org.freedesktop.DBus.Error.ServiceUnknown] The name org.bluez was not provided by any .service files Is it required to pass both DBus and the device to the container or is passing DBus sufficient?
April 24, 20233 yr I buying my first home server and it will be my first time using unRaid. So is the challenge with Bluetooth with only USB dongles? It is also with chipsets that have WiFi that is plugged directly into the motherboard?
August 9, 20232 yr So, I've found solution: Download package from here on your host (unraid): https://slackware.pkgs.org/15.0/slackware-patches-x86_64/bluez-5.64-x86_64-1_slack15.0.txz.html Then install taht package: upgradepkg --install-new bluez-5.64-x86_64-1_slack15.0.txz Restart service: /etc/rc.d/rc.bluetooth restart Passthru 2 paths to your HomeAssistant container (get your ID of usb device with lsusb) /dev/bus/usb/003/002 /run/dbus Restart your HomeAssistant container... and VOILA, Bluetooth found and working! Have fun!
August 9, 20232 yr 1 minute ago, YaneonY said: So, I've found solution: Download package from here on your host (unraid): https://slackware.pkgs.org/15.0/slackware-patches-x86_64/bluez-5.64-x86_64-1_slack15.0.txz.html Then install taht package: upgradepkg --install-new bluez-5.64-x86_64-1_slack15.0.txz Restart service: /etc/rc.d/rc.bluetooth restart Passthru 2 paths to your HomeAssistant container (get your ID of usb device with lsusb) /dev/bus/usb/003/002 /run/dbus Restart your HomeAssistant container... and VOILA, Bluetooth found and working! Have fun! If you put in boot/extra and it will be installed at boot
August 30, 20232 yr On 8/9/2023 at 11:10 PM, SimonF said: If you put in boot/extra and it will be installed at boot That Did it for me. Perfect ! Thanks
November 5, 20232 yr On 8/9/2023 at 2:06 PM, YaneonY said: Passthru 2 paths to your HomeAssistant container (get your ID of usb device with lsusb) /dev/bus/usb/003/002 /run/dbus Communication is all done over DBUS, so you don't have to pass through the USB device itself (and in fact, that can be problematic as the path can change between reboots, which will cause your container to fail to start). Just passing through /run/dbus should be sufficient.
November 8, 20232 yr On 8/9/2023 at 10:06 PM, YaneonY said: So, I've found solution: Download package from here on your host (unraid): https://slackware.pkgs.org/15.0/slackware-patches-x86_64/bluez-5.64-x86_64-1_slack15.0.txz.html Then install taht package: upgradepkg --install-new bluez-5.64-x86_64-1_slack15.0.txz Restart service: /etc/rc.d/rc.bluetooth restart Passthru 2 paths to your HomeAssistant container (get your ID of usb device with lsusb) /dev/bus/usb/003/002 /run/dbus Restart your HomeAssistant container... and VOILA, Bluetooth found and working! Have fun! When you say 'passthrough' what does that mean? Options are extra parameters with --device='/dev/bus/usb/007/005' or can add a 'path' or 'device'? Thanks Edited November 8, 20232 yr by dopeytree
May 5, 20242 yr On 8/10/2023 at 1:10 AM, SimonF said: If you put in boot/extra and it will be installed at boot Do you know, however, correct way to autostart bluetooth on boot after? I'm sorry, UNRAID is still quite new for me. Should I use UserScripts plugin, or I can just add some config at /boot?
May 6, 20242 yr 11 hours ago, Drun said: Do you know, however, correct way to autostart bluetooth on boot after? I'm sorry, UNRAID is still quite new for me. Should I use UserScripts plugin, or I can just add some config at /boot? BT should start at boot if package installed via extra
May 6, 20242 yr 4 minutes ago, SimonF said: BT should start at boot if package installed via extra Thank you for clarification. I used UserScripts anyway, but now it seems redundant
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.