Host OS Support for Bluetooth Devices


Recommended Posts

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

  • Thanks 1
Link to comment
  • 5 months later...
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? 

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.