I've searched, and it seems for my adapter (RTL8761BU based) the issue in the past was the driver wasn't installed on the system. Now, after upgrading to 6.11.1, it seems that the drivers are there (I see it listed in /lib/firmware/rtl_bt/) but it still doesn't show up in /dev/serial/by-id (lsusb shows it is connected however?).

 

How do I get the system to recognize the usb stick, so I can then pass it through to the home assistant container, or is this still not possible because of some limitation in the specific linux kernel version?

 

Thank you.

Hi, did you managed to get this sorted? My system recognizes the asus bt-500 adapter, it passes through to the HA vm but HA does seem to scan any devices...

On 10/10/2022 at 7:12 PM, God_TM said:

I've searched, and it seems for my adapter (RTL8761BU based) the issue in the past was the driver wasn't installed on the system. Now, after upgrading to 6.11.1, it seems that the drivers are there (I see it listed in /lib/firmware/rtl_bt/) but it still doesn't show up in /dev/serial/by-id (lsusb shows it is connected however?).

 

How do I get the system to recognize the usb stick, so I can then pass it through to the home assistant container, or is this still not possible because of some limitation in the specific linux kernel version?

 

Thank you.

 

On 12/5/2022 at 1:19 PM, renk1 said:

Hi, did you managed to get this sorted? My system recognizes the asus bt-500 adapter, it passes through to the HA vm but HA does seem to scan any devices...

TL;DR: (Possibly):

• Install un-get
• Install bluez through un-get
• start rc.bluetooth & passthrough dbus/bt-device
• Profit

 

Now for a more thorough explanation of everything I've tried:

I have basically thrown every available ball against the wall so a couple of steps I've done might not be of use.

I have a TP-Link UB500 whichs seems to be similiar, at least this thread came up when I googled the issue so I'll respond if any fellow UB500 purchaser ends up here while Googling.

 

 

What I've passed through to HA:

--device='/dev/bus/usb/001/003' --device='/dev/tty6'

001/003 being where I see the device being when I'm in the terminal in unRaid and doing `lsusb`. In one of the billions of google attempts I found a script that an unRaid user used to mention which tty* that was recently attached but I cant find it.

 

In extra properties I've shared this to the container.

/run/dbus

 

I am quite certain the way to solve my issue, if anyone tests is out please respond. Is this way:
Install https://github.com/ich777/un-get un-get from lovely ich777 and install bluez. Once you've installed bluez need to add this to /boot/config/go

/etc/rc.d/rc.bluetooth start

 

 

Edited January 14, 20233 yr by shunde

I am having issues, my device is here:

 

Bus 003 Device 002: ID 2357:0604 TP-Link TP-Link UB5A Adapter

But cannot pass this into HA container it seems

On 2/18/2023 at 11:18 AM, Tim Knowlden said:

I am having issues, my device is here:

 

Bus 003 Device 002: ID 2357:0604 TP-Link TP-Link UB5A Adapter

But cannot pass this into HA container it seems

Have you tried to pass /run/dbus to your HA container? Alongside installing bluez like my post mentioned.

 

I wonder if passing /run/dbus and using bluez is enough or if passing /run/dbus, installing bluez and passing the corresponding /dev/ttyX is enough.

On 2/21/2023 at 11:13 PM, shunde said:

Have you tried to pass /run/dbus to your HA container? Alongside installing bluez like my post mentioned.

 

I wonder if passing /run/dbus and using bluez is enough or if passing /run/dbus, installing bluez and passing the corresponding /dev/ttyX is enough.

I did indeed, tried both dbus and the device. No joy.

On 2/21/2023 at 11:13 PM, shunde said:

Have you tried to pass /run/dbus to your HA container? Alongside installing bluez like my post mentioned.

 

I wonder if passing /run/dbus and using bluez is enough or if passing /run/dbus, installing bluez and passing the corresponding /dev/ttyX is enough.

I also tried with the ttyX instead of /dev/bus/usb/001/007

To update this, i have now managed to get it working, no need to pass the device, i upgraded to the latest version of unraid, i installed bluez and started bluetooth service, then passed dbus into HA container. The device is now added, no devices found in Home assistant, but they can be seen in terminal

I am also having this issue, trying to forward /run/dbus causes the container to error out:


I have also tried to forward /dev/bus/usb/ to the container and it seems like it can see the devices but cannot utilize them:


From HA:

Edited March 7, 20233 yr by Deadpool1985

On 3/7/2023 at 7:51 PM, Deadpool1985 said:

I am also having this issue, trying to forward /run/dbus causes the container to error out:


I have also tried to forward /dev/bus/usb/ to the container and it seems like it can see the devices but cannot utilize them:


From HA:

 

I think you need to pass through '/run/dbus' as a path rather than as a device. I got mine working after installing bluez through un-get and then using the following docker command:

 

docker run
  -d
  --name='homeassistant'
  --net='host'
  -e TZ="Europe/London"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="my-server-name"
  -e HOST_CONTAINERNAME="homeassistant"
  -e 'TCP_PORT_8123'='8123'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -e 'UMASK'='022'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:8123]'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/homeassistant-logo.png'
  -v '/run/dbus':'/run/dbus':'rw'
  -v '/mnt/user/appdata/homeassistant':'/config':'rw'
  --device='/dev/bus/usb/007/005' 'lscr.io/linuxserver/homeassistant'

These settings worked for me:

• Install un-get on unraid - https://raw.githubusercontent.com/ich777/un-get/master/un-get.plg
• Install bluez on unraid via un-get:

  un-get update && un-get install bluez

• Start bluetooth service: 

  /etc/rc.d/rc.bluetooth start

   

• Mount /run/dbus readonly into the home assistant container

Once I did this and restarted the container, home assistant recognised the bluetooth adapter.

 

Note that my home assistant container runs in privileged mode (--privileged docker option). This is the default for the home assistant unraid app, but you'll likely need to mount the bluetooth USB device in if you aren't running in privileged mode. eg ---device='/dev/bus/usb/xxx/xxx'

How do you mount /run/dbus ?

 

In home assistant it's saying...

 

On 11/8/2023 at 7:12 PM, dopeytree said:

How do you mount /run/dbus ?

 

In home assistant it's saying...

 

Just add a path like that:

Works perfect for me:

What's your bluetooth device?

Mine is a combined intel ax200 module that is pcie but the Bluetooth appears on usb but the wifi side is on pcie.

I think this is the source of the issue & or maybe a driver issue.

I'll try getting a portable windows install going so I can update some firmwares

Edited January 23, 20242 yr by dopeytree

On 1/23/2024 at 10:01 AM, dopeytree said:

What's your bluetooth device?

Mine is a combined intel ax200 module that is pcie but the Bluetooth appears on usb but the wifi side is on pcie.

I think this is the source of the issue & or maybe a driver issue.

I'll try getting a portable windows install going so I can update some firmwares

this is my exact scenario.  any updates?

On 2/15/2025 at 8:44 AM, Uliphant said:

this is my exact scenario.  any updates?

I fixed mine using below method, just privileged mode was not necessary

On 7/22/2023 at 2:25 AM, gussy12 said:

These settings worked for me:

• Install un-get on unraid - https://raw.githubusercontent.com/ich777/un-get/master/un-get.plg

• Install bluez on unraid via un-get:

  un-get update && un-get install bluez

• Start bluetooth service: 

  /etc/rc.d/rc.bluetooth start

   

• Mount /run/dbus readonly into the home assistant container

Once I did this and restarted the container, home assistant recognised the bluetooth adapter.

 

Note that my home assistant container runs in privileged mode (--privileged docker option). This is the default for the home assistant unraid app, but you'll likely need to mount the bluetooth USB device in if you aren't running in privileged mode. eg ---device='/dev/bus/usb/xxx/xxx'