I recently moved from the latest Home Assistant Supervised under Raspberry Pi with Debian 11 to the latest Home Assistant Operating System under a Proxmox Virtual Machine. The physical hardware is an HP MiniPC without internal wifi and without any bluetooth.
Previously I was using bluetooth classic and bluetooth low energy device trackers (with the Room Assistant addon, but I don’t think that matters).
So I get a TP-Link UB500 bluetooth USB adapter connected to the phisical machine and passed to the HassOS virtual machine.
The adapter seems somehow found but any scanning result in empty list.
Any experience with this product?
How to get it working, if possible?
If not, what is a usb bluetooth adapter supported in HassOS with my setup?
From what I understand the adapter user a Realtek Bluetooth 8761B radio.
Some info follow.
==========
Physical Machine
root@hub:~# uname -a
Linux hub 5.13.19-6-pve #1 SMP PVE 5.13.19-14 (Thu, 10 Mar 2022 16:24:52 +0100) x86_64 GNU/Linux
root@hub:~# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 1cf1:0030 Dresden Elektronik ZigBee gateway [ConBee II]
Bus 001 Device 002: ID 2357:0604 TP-Link TP-Link UB500 Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
==========
HassOS Virtual Machine
# uname -a
Linux homeassistant 5.10.103 #1 SMP Wed Mar 9 10:05:18 UTC 2022 x86_64 HAOS
# lsusb
Bus 003 Device 001: ID 1d6b:0003
Bus 002 Device 005: ID 1cf1:0030
Bus 001 Device 001: ID 1d6b:0001
Bus 001 Device 002: ID 0627:0001
Bus 002 Device 004: ID 2357:0604
Bus 002 Device 001: ID 1d6b:0002
==========
Home Assistant Container
bash-5.1# uname -a
Linux homeassistant 5.10.103 #1 SMP Wed Mar 9 10:05:18 UTC 2022 x86_64 Linux
bash-5.1# lsusb
Bus 002 Device 004: ID 2357:0604 TP-Link TP-Link UB500 Adapter
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 005: ID 1cf1:0030 Dresden Elektronik ZigBee gateway [ConBee II]
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
bash-5.1# hciconfig dev
hci0: Type: Primary Bus: USB
BD Address: E8:48:B8:C8:20:00 ACL MTU: 1021:6 SCO MTU: 255:12
UP RUNNING
RX bytes:151950 acl:0 sco:0 events:21152 errors:0
TX bytes:145892 acl:0 sco:0 commands:17636 errors:0
bash-5.1# hcitool scan
Scanning ...
bash-5.1#
bash-5.1# dmesg | grep -i blue
[ 0.344952] Bluetooth: Core ver 2.22
[ 0.345362] Bluetooth: HCI device and connection manager initialized
[ 0.345860] Bluetooth: HCI socket layer initialized
[ 0.346362] Bluetooth: L2CAP socket layer initialized
[ 0.346760] Bluetooth: SCO socket layer initialized
**[ 16.347796] Bluetooth: hci0: unexpected event for opcode 0x1001**
Hi, did you manage to solve it? I have the same issue. The adapter is found, but i don seem to find anny devices. I’m running Home Assistant OS btw on an HP T620 thin Client.
the annoying bit is everything is pretty hard to find since I need the ‘bu’ version and it constantly suggests ‘b’ so without the U.
Btw, my LSUSB:
pi@docker:~ $ lsusb
Bus 002 Device 002: ID 04e8:61f5 Samsung Electronics Co., Ltd Portable SSD T5
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 1cf1:0030 Dresden Elektronik ZigBee gateway [ConBee II]
Bus 001 Device 008: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 001 Device 007: ID 10c4:ea60 Silicon Labs CP210x UART Bridge
Bus 001 Device 006: ID 2357:0604 TP-Link TP-Link UB500 Adapter
Bus 001 Device 004: ID 2109:2813 VIA Labs, Inc. VL813 Hub
Bus 001 Device 003: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
So it is the same UB500, but with a newer chipset?
Is there maybe something else I can do? I’m using a Raspberry Pi 4. I soft blocked my onboard BLE device by executing sudo rfkill 2 command to disable the HCI1 adapter.
