klogg
(Klogg)
January 28, 2022, 12:45pm
1
I decided to revisit the old Proxmox, NUC, Bluetooth issue.
I’ve done some research and it seems that many people are getting it working but I can’t work out if the steps are within my grasp (I know only the basics of Linux and am not a Proxmox expert by any means).
As with many of these things the advice/solutions seems to change with time.
But I have seen this on Reddit:
You should see USB 1.x device with no name listed, this is the bluetooth card. You can pass this through to the VM without passing through the PCI wifi device.
And this:
HA Github (closed) issue
Both from about Oct 2021.
So, if I try to add a USB device to my HA VM I have two options:
Am I on the right track? Will one of these make Bluetooth available to HA (If so which one)?
I know this is an old question but it seems to me that the NUC/Proxmox/HA setup is now quite popular so maybe there is a ‘simple’ solution now that I have missed.
Thanks.
2 Likes
@klogg indeed adding and normally should work. Recently no longer working here with same setup. So trying to understand what I’m missing.
Did you manage to get it working?
Currently reading this
opened 07:18PM - 12 May 22 UTC
closed 01:11PM - 14 May 22 UTC
bug
board/ova
### Describe the issue you are experiencing
Since installing OS8.0 the intern… al bluetooth chip of my Intel NUC is not working anymore in Home Assistant.
### What operating system image do you use?
ova (for Virtual Machines)
### What version of Home Assistant Operating System is installed?
8.0
### Did you upgrade the Operating System.
Yes
### Steps to reproduce the issue
Home Assistant OS can't seem to use the internal Bluetooth chip of my Intel NUC, since installing 8.0.
Tried disattaching the "USB" device from the Virtualbox VM and reattaching. This allways solved issues with the internal BT chip.
All firmware is up-to-date and the BT works fine locally on the Intel NUC.
### Anything in the Supervisor logs that might be useful for us?
```txt
Nothing related to BT issues
```
### Anything in the Host logs that might be useful for us?
```txt
[ 0.259527] Bluetooth: Core ver 2.22
[ 0.259534] NET: Registered PF_BLUETOOTH protocol family
[ 0.259537] Bluetooth: HCI device and connection manager initialized
[ 0.259539] Bluetooth: HCI socket layer initialized
[ 0.259542] Bluetooth: L2CAP socket layer initialized
[ 0.259545] Bluetooth: SCO socket layer initialized
[ 4.002661] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi
[ 4.002754] Bluetooth: hci0: Boot Address: 0x40800
[ 4.002757] Bluetooth: hci0: Firmware Version: 60-44.21
[ 6.035532] Bluetooth: hci0: command 0xfc01 tx timeout
[ 14.355434] Bluetooth: hci0: FW download error recovery failed (-110)
[ 306.696246] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi
[ 306.696284] Bluetooth: hci0: Boot Address: 0x40800
[ 306.696285] Bluetooth: hci0: Firmware Version: 60-44.21
[ 308.754237] Bluetooth: hci0: command 0xfc01 tx timeout
[ 316.946372] Bluetooth: hci0: FW download error recovery failed (-110)
```
### System Health information
## System Health
version | core-2022.5.3
-- | --
installation_type | Home Assistant OS
dev | false
hassio | true
docker | true
user | root
virtualenv | false
python_version | 3.9.9
os_name | Linux
os_version | 5.15.38
arch | x86_64
timezone | Europe/Amsterdam
<details><summary>Home Assistant Community Store</summary>
GitHub API | ok
-- | --
GitHub Content | ok
GitHub Web | ok
GitHub API Calls Remaining | 4247
Installed Version | 1.24.5
Stage | running
Available Repositories | 1103
Downloaded Repositories | 58
</details>
<details><summary>AccuWeather</summary>
can_reach_server | ok
-- | --
remaining_requests | 27
</details>
<details><summary>Home Assistant Cloud</summary>
logged_in | true
-- | --
subscription_expiration | 29 May 2022, 02:00
relayer_connected | true
remote_enabled | true
remote_connected | true
alexa_enabled | false
google_enabled | true
remote_server | eu-central-1-0.ui.nabu.casa
can_reach_cert_server | ok
can_reach_cloud_auth | ok
can_reach_cloud | ok
</details>
<details><summary>Home Assistant Supervisor</summary>
host_os | Home Assistant OS 8.0
-- | --
update_channel | beta
supervisor_version | supervisor-2022.05.2
docker_version | 20.10.14
disk_total | 73.1 GB
disk_used | 46.5 GB
healthy | true
supported | true
board | ova
supervisor_api | ok
version_api | ok
installed_addons | Samba share (9.6.1), Mosquitto broker (6.1.2), TasmoAdmin (0.17.0), AirCast (3.3.0), File editor (5.3.3), deCONZ (6.13.0), SSH & Web Terminal (10.1.3), Vaultwarden (Bitwarden) (0.16.0), phpMyAdmin (0.7.1), WireGuard (0.6.0), Glances (0.15.0), Node-RED (11.1.2), Home Assistant Google Drive Backup (0.107.2), AdGuard Home (4.5.1), Check Home Assistant configuration (3.10.0), Let's Encrypt (4.12.2), Nginx Proxy Manager (0.11.0), chrony (2.3.0), ESPHome (2022.3.1), TimescaleDB (2.0.1), pgAdmin4 (2.0.0), MariaDB (2.4.0), Studio Code Server (5.0.2), Zigbee2mqtt (1.25.1-1), Frigate NVR (3.1), UniFi Network Application (2.2.0), DSMR Reader (1.2.0), Genie (3.0.0)
</details>
<details><summary>Dashboards</summary>
dashboards | 4
-- | --
resources | 38
views | 33
mode | storage
</details>
### Additional information
_No response_
klogg
(Klogg)
July 26, 2022, 4:01pm
3
I never actually tried yet. I have a reason to want Bluetooth on a VM but it is just not pressing enough for me to have got round to it.
Can confirm!
In proxmox I went to the Homeassistant VM > hardware > add > USB Device > Use USB Vendor/device
Then selected the usb 1.x that had no name and after a reboot I was able to see the bluetooth integration as well as it found ibreacon tracker. However… getting my govee led strips to work may be a bit more difficult than clicking through next menus
8 Likes
dai80027
(Dave's not here, man!)
April 27, 2023, 3:53am
6
Fixed the problem for me too! Thanks for posting.
Jokerigno
(Jokerigno)
February 24, 2024, 4:24pm
7
Thanks! It worked also for me!
Landif
(yolandi)
October 31, 2024, 3:36pm
8
This solution still works!
Thanks for posting!