search

home-assistant / operating-system

:beginner: Home Assistant Operating System
Apache License 2.0
5.07k stars 992 forks source link

Bluetooth not working on virtualbox VM #2142

Open ZTHawk opened 2 years ago

ZTHawk commented 2 years ago

Describe the issue you are experiencing

Bluetooth is not working with HA. Using bluetoothctl scan on I get "No default controller available" In host console I see:

Bluetooth: hci0: command 0xfc01 tx timeout
Bluetooth: hci0: FW download error recovery failed (-110)

I tried an image with HAOS 7.6. Using the command bluetoothctl scan on there I get "Discovery started" followed by a list of all found devices.

Asus PN41 My bluetooth device (integrated in wireless module): Intel Wireless AC 9560

What operating system image do you use?

ova (for Virtual Machines)

What version of Home Assistant Operating System is installed?

9.0

Did you upgrade the Operating System.

Yes

Steps to reproduce the issue

Start a VM with attached Bluetooth device. In host console I get:

Bluetooth: hci0: FW download error recovery failed (-110)

When disabling the Bluetooth device and then reenabling it I get the following in host console:

Bluetooth: hci0: command 0xfc01 tx timeout
Bluetooth: hci0: FW download error recovery failed (-110)

Anything in the Supervisor logs that might be useful for us?

N/A

Anything in the Host logs that might be useful for us?

N/A

System Health information

N/A

Additional information

N/A

agners commented 2 years ago

What make/type of Bluetooth device are you using? You are saying 7.6 used to work still, did you try HAOS 8.5?

agners commented 2 years ago

-110 means timeout. It seems the device somehow does not respond. Maybe removing it and plugging back in helps?

ZTHawk commented 2 years ago

I just did some more tests: 1) HA OS 7.6 and Core 2022.6.7 -- Bluetooth scan bluetoothctl scan on is working (it can find devices) 2) HA OS 7.6 and Core 2022.9.5 -- Bluetooth scan is working 3) HA OS 8.0 and Core 2022.9.4 -- Bluetooth scan is NOT working (No default controller available) 4) HA OS 8.0 and Core 2022.6.7 (after downgrade) -- Bluetooth scan is NOT working 5) HA OS 8.5 and Core 2022.6.7 -- Bluetooth scan is NOT working

ZTHawk commented 2 years ago

Just for completness: My bluetooth device (integrated in wireless module): Intel Wireless AC 9560

ZTHawk commented 2 years ago

Update: HA OS 9.2 (an 9.3) + Core 2022.10.5 -- Bluetooth scan is NOT working

ZTHawk commented 1 year ago

I have bought a separate Bluetooth-Stick to fix this issue but this resulted in a weird behaviour. The moment I attached the Bluetooth-Stick to windows host, the integrated bluetooth module started to work within HA. Windows host had bluetooth via the new stick. So suddenly everthing was working fine. I have removed the bluetooth stick. HA was still fine. I have not reattached the stick.

I have then upgraded to OS 9.4 and also upgraded to 2022.12. Still everything was fine.

I have restarted the host and integrated bluetooth module is not working in HA anymore. Tried to reproduce the behaviour with the stick but with no luck.

If I unassign the bluetooth module (on Intel Wifi chip) and then I assign the stick to HA then it crashes. If I try to restart it, it will crash. Switching back to integrated bluetooth allows HA to start again but with no bluetooth.

PS: 7.6 is working but 8.0 RC1 is not.

ZTHawk commented 1 year ago

Update: HA OS 9.5 (an 9.4) + Core 2023.1.7 -- Bluetooth scan is NOT working

HA OS 7.6 is the last working version. Any vesion after that has bluetooth issues. Tested with clean installations.

ZTHawk commented 1 year ago

Update: HA OS 10.0 + Core 2023.4.4 -- Bluetooth scan is NOT working

ZTHawk commented 1 year ago

Update: HA OS 10.1 + Core 2023.4.6 -- Bluetooth scan is not working

grafik When Bluetooth device "(Intel Corp.) [0002]" is not selected in USB device filters (see screenshot above) and I then try to add the Bluetooth device (see screenshot below) grafik Then I get the error:

Bluetooth: hci0: FW download error recovery failed (-19)

When adding the tick in the first screenshot and then trying to add the Bluetooth device like in second screenshot, then I get the error:

Bluetooth: hci0: command 0xfc01 tx timeout
Bluetooth: hci0: FW download error recovery failed (-110)

PS: OS 7.6 has no issues.

ZTHawk commented 1 year ago

Update: HA OS 10.2 + Core 2023.5.3 Still not working

madbrain76 commented 1 year ago

I am seeing the same problem with an Intel 9260 Bluetooth controller on my X560 TUF Gaming Plus motherboard, Virtualbox 7.0.8 and latest HAOS 10.2 .

agners commented 1 year ago

Hardware initialization/firmware is something handled by the kernel. What would be interesting is if the same error appears on a different distribution (e.g. Arch Linux with the LTS kernel installated). If that is the case, you could try report this to the Linux kernel folks (e.g. via https://bugzilla.kernel.org/).

ZTHawk commented 1 year ago

Update: HA OS 10.2 + Core 2023.6.1

Still not working

Installed OS 10.3 + Core 2023.6.2 today. Had issues with system not responding. Did a hard reset. After everything started up I have added the bluetooth device. It is working now.

Device was not in USB filter

Next I have added it to USB filter and I have done a shutdown. Booted the VM: Bluetooth still working.

Rebooted host system. Result in HA: Bluetooth still working.

I will not yet see this as fixed untill a longer period of runtime/more restarts (see above comments where it was working once for a short time and then stopped again).

intercrypto commented 1 year ago

Hi, @ZTHawk.

I did my upgrade now and the bluetooth does not work. My versions are the same. I have tested with and without USB filter in Virtualbox.

I´m using a U59 Pro Intel mini computer. The bluetooth works in the Windows host but in VM HA does not work.

Please, some help.

ZTHawk commented 1 year ago

@intercrypto Unfortunately I cannot help. It just suddenly started to work. That is also the reason why I do not see it as fixed yet.

PS: My installed drivers are (Asus PN41): Wifi: 22.220.0.4 (date: 29.03.2023) BT: 22.220.1.1 (date: 18.04.2023)

remme123 commented 1 year ago

I have bought a separate Bluetooth-Stick to fix this issue but this resulted in a weird behaviour. The moment I attached the Bluetooth-Stick to windows host, the integrated bluetooth module started to work within HA. Windows host had bluetooth via the new stick. So suddenly everthing was working fine. I have removed the bluetooth stick. HA was still fine. I have not reattached the stick.

I have then upgraded to OS 9.4 and also upgraded to 2022.12. Still everything was fine.

I have restarted the host and integrated bluetooth module is not working in HA anymore. Tried to reproduce the behaviour with the stick but with no luck.

If I unassign the bluetooth module (on Intel Wifi chip) and then I assign the stick to HA then it crashes. If I try to restart it, it will crash. Switching back to integrated bluetooth allows HA to start again but with no bluetooth.

PS: 7.6 is working but 8.0 RC1 is not.

I successfully started Bluetooth in VBox using the same method. My environment is VBox running on Windows 10, with the virtual machine running ArchLinux.

I speculate that the issue is caused by Windows 10 occupying the Bluetooth device, which results in it being also occupied when assigned to VBox.

ZTHawk commented 1 year ago

Today (at least I noticed today) it stopped working. With a new additional error:

Bluetooth: hci0: command 0xfc01 tx timeout
Bluetooth: hci0: FW download error recovery failed (-110)
Bluetooth: hci0: Reading Intel version command failed (-32)
ZTHawk commented 1 year ago

Reverting back to HAOS 10.3 and driver 22.220.1 fixed the issue.

nnathan commented 1 year ago

Not a Home Assistant user, but I was trying to redirect my Intel AX210 Bluetooth USB device to a VM using virt-manager in a stock version of Ubuntu 22.04 Linux. It kept failing with the same error messages as OP posted.

The bandaid solution was to download the latest Linux firmware for iwlwifi which I think is used to transfer firmware to the AX210 BT device (I think). Just download the latest firmware from here and copy the extracted contents to /lib/firmware. Then I tried redirecting the USB device and it succeeded. In the case of OP you might need to either reboot or use a tool like usbreset to reset the device so that the firmware can load.

github-actions[bot] commented 12 months ago

There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant OS version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

ZTHawk commented 12 months ago

Still applicable

ZTHawk commented 10 months ago

New hardware with Intel AX200. Still applicable with latest OS.

bobvmierlo commented 10 months ago

Running into the same issue here. Running HAOS 11.4, Supervisor 2024.01.0 and Core 2024.1.5 inside a Virtualbox VM on an Intel NUC (NUC13ANHi5) and using this bluetooth dongle from Trust

Some lines from the host log:

Jan 28 20:03:52 homeassistant systemd[1]: Stopped target Bluetooth Support.
Jan 28 20:03:52 homeassistant kernel: usb 1-2: reset full-speed USB device number 5 using xhci_hcd
Jan 28 20:03:52 homeassistant kernel: usb 1-2: unable to get BOS descriptor or descriptor too short
Jan 28 20:03:52 homeassistant systemd[1]: Reached target Bluetooth Support.
Jan 28 20:03:52 homeassistant kernel: Bluetooth: hci0: Reading Intel version command failed (-32)
Jan 28 20:03:53 homeassistant kernel: Bluetooth: hci0: Reading Intel version command failed (-32)
Jan 28 20:03:58 homeassistant systemd[1]: Stopped target Bluetooth Support.
Jan 28 20:03:58 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-3639b5d244c015189d3d78972a017ba2d46ef650763710c2ed8db2d33b57e433-runc.AKRUYk.mount: Deactivated successfully.
Jan 28 20:03:58 homeassistant kernel: usb 1-2: reset full-speed USB device number 5 using xhci_hcd
Jan 28 20:03:58 homeassistant kernel: usb 1-2: unable to get BOS descriptor or descriptor too short
Jan 28 20:03:58 homeassistant systemd[1]: Reached target Bluetooth Support.
Jan 28 20:03:58 homeassistant kernel: Bluetooth: hci0: Reading Intel version command failed (-32)
txteclipse commented 9 months ago

I believe I am also experiencing this problem. Bluetooth device is a mobo-integrated Intel module. Host OS is Windows 10 v. 22H2. These are the errors when I use the usb device filter in VirtualBox. Screenshot 2024-02-19 221829

Pascal66 commented 8 months ago

Still applicable image

ZTHawk commented 6 months ago

Switched to Proxmox with HA as VM. Passed Bluetooth device to HA. Restored from backup. Bluetooth was working. Restarted HA virtual machine, Bluetooth is not working anymore.

ZTHawk commented 4 months ago

Test done with Proxmox:

  1. Removed bluetooth from HA
  2. Assigned to Windows 11 (VM in Proxmox)
  3. Bluetooth is working fine (devices can be found)
  4. Removed from Win11
  5. Assigned to HA
  6. Bluetooth is not working

I get this message the moment I connect the bluetooth device to HA: grafik

Pascal66 commented 4 months ago

image more detailled message :

2024-07-07 09:10:08.175 homeassistant kernel: usb 1-4: new full-speed USB device number 5 using xhci_hcd
2024-07-07 09:10:08.306 homeassistant kernel: usb 1-4: New USB device found, idVendor=8087, idProduct=0aaa, bcdDevice= 0.02
2024-07-07 09:10:08.307 homeassistant kernel: usb 1-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
2024-07-07 09:10:08.471 homeassistant kernel: usbcore: registered new interface driver btusb
2024-07-07 09:10:08.554 homeassistant systemd[1]: Reached target Bluetooth Support.
2024-07-07 09:10:08.603 homeassistant kernel: Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi
2024-07-07 09:10:08.604 homeassistant kernel: Bluetooth: hci0: Boot Address: 0x40800
2024-07-07 09:10:08.604 homeassistant kernel: Bluetooth: hci0: Firmware Version: 155-35.23
2024-07-07 09:10:09.134 homeassistant kernel: usb 1-4: USB disconnect, device number 5
2024-07-07 09:10:09.136 homeassistant kernel: Bluetooth: hci0: FW download error recovery failed (-19)
2024-07-07 09:10:09.137 homeassistant kernel: Bluetooth: hci0: sending frame failed (-19)
2024-07-07 09:10:09.138 homeassistant kernel: Bluetooth: hci0: Reading supported features failed (-19)
2024-07-07 09:10:09.140 homeassistant kernel: Bluetooth: hci0: Error reading debug features
2024-07-07 09:10:09.140 homeassistant kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
2024-07-07 09:10:09.156 homeassistant systemd[1]: Stopped target Bluetooth Support.
github-actions[bot] commented 1 month ago

There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant OS version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Pascal66 commented 1 month ago

Still not working with image

behold81 commented 1 month ago

I am having the same issue with the following BT module. it was working and now its not. 8087:0aaa Intel Corp. Bluetooth 9460/9560

Using Proxmox. BT is blacklisted in the host, VM is using q35 and the USB Passthrough added. I see the device in the VM but will not initialise with: image

I have tried alot to sort this with no hope. using 2024.10.0 and 13.1 OS.

mrdunu commented 2 days ago

Also having a similar issue with Home Assistant OS 13.2 and core-2024.11.3 using the onboard Intel NUC bluetooth:

Bluetooth: hci0: Reading Intel version command failed (-32)

fofyga commented 20 hours ago

same issue with bluetooth dongle on 13.1