PVE 7.4 + Home Assistant: Intel AX200 Bluetooth issues

A

andy_e

New Member
Apr 18, 2023
2
0
1
I recently set up a mini PC to run Home Assistant and it's my first time running Proxmox. Everything appears to be working well except when I boot the machine from a cold start (doesn't happen very often). Proxmox and Home Assistant start, but the AX200 Bluetooth looks like it has problems starting immediately. Here's the relevant dmesg -T output:

Code: 
[Tue Apr 18 07:36:20 2023] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
[Tue Apr 18 07:36:20 2023] Bluetooth: hci0: Device revision is 1
[Tue Apr 18 07:36:20 2023] Bluetooth: hci0: Secure boot is enabled
[Tue Apr 18 07:36:20 2023] Bluetooth: hci0: OTP lock is enabled
[Tue Apr 18 07:36:20 2023] Bluetooth: hci0: API lock is enabled
[Tue Apr 18 07:36:20 2023] Bluetooth: hci0: Debug lock is disabled
[Tue Apr 18 07:36:20 2023] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[Tue Apr 18 07:36:20 2023] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[Tue Apr 18 07:36:22 2023] Bluetooth: hci0: Waiting for firmware download to complete
[Tue Apr 18 07:36:22 2023] Bluetooth: hci0: Firmware loaded in 1388574 usecs
[Tue Apr 18 07:36:22 2023] Bluetooth: hci0: Waiting for device to boot
[Tue Apr 18 07:36:22 2023] Bluetooth: hci0: Device booted in 14885 usecs
[Tue Apr 18 07:36:22 2023] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc
[Tue Apr 18 07:36:22 2023] Bluetooth: hci0: Applying Intel DDC parameters completed
[Tue Apr 18 07:36:22 2023] Bluetooth: hci0: Firmware revision 0.3 build 15 week 45 2022
[Tue Apr 18 07:36:30 2023] usb 3-3: reset full-speed USB device number 3 using xhci_hcd
[Tue Apr 18 07:36:30 2023] usb 3-3: USB disconnect, device number 3
[Tue Apr 18 07:36:31 2023] usb 3-3: new full-speed USB device number 4 using xhci_hcd
[Tue Apr 18 07:36:31 2023] usb 3-3: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
[Tue Apr 18 07:36:31 2023] usb 3-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[Tue Apr 18 07:36:31 2023] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
[Tue Apr 18 07:36:31 2023] Bluetooth: hci0: Device revision is 1
[Tue Apr 18 07:36:31 2023] Bluetooth: hci0: Secure boot is enabled
[Tue Apr 18 07:36:31 2023] Bluetooth: hci0: OTP lock is enabled
[Tue Apr 18 07:36:31 2023] Bluetooth: hci0: API lock is enabled
[Tue Apr 18 07:36:31 2023] Bluetooth: hci0: Debug lock is disabled
[Tue Apr 18 07:36:31 2023] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[Tue Apr 18 07:36:31 2023] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[Tue Apr 18 07:36:32 2023] Bluetooth: hci0: Waiting for firmware download to complete
[Tue Apr 18 07:36:38 2023] Bluetooth: hci0: Firmware loading timeout
[Tue Apr 18 07:36:38 2023] Bluetooth: hci0: Intel reset sent to retry FW download
[Tue Apr 18 07:36:38 2023] usb 3-3: USB disconnect, device number 4
[Tue Apr 18 07:36:38 2023] Bluetooth: hci0: sending frame failed (-19)
[Tue Apr 18 07:36:40 2023] Bluetooth: hci0: Failed to read MSFT supported features (-110)
[Tue Apr 18 07:36:40 2023] Bluetooth: hci0: command 0xfc1e tx timeout
[Tue Apr 18 07:36:40 2023] usb 3-3: new full-speed USB device number 5 using xhci_hcd
[Tue Apr 18 07:36:40 2023] usb 3-3: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
[Tue Apr 18 07:36:40 2023] usb 3-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[Tue Apr 18 07:36:40 2023] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
[Tue Apr 18 07:36:40 2023] Bluetooth: hci0: Device revision is 1
[Tue Apr 18 07:36:40 2023] Bluetooth: hci0: Secure boot is enabled
[Tue Apr 18 07:36:40 2023] Bluetooth: hci0: OTP lock is enabled
[Tue Apr 18 07:36:40 2023] Bluetooth: hci0: API lock is enabled
[Tue Apr 18 07:36:40 2023] Bluetooth: hci0: Debug lock is disabled
[Tue Apr 18 07:36:40 2023] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[Tue Apr 18 07:36:40 2023] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[Tue Apr 18 07:36:41 2023] Bluetooth: hci0: urb 0000000024e295b6 submission failed (2)
[Tue Apr 18 07:36:41 2023] Bluetooth: hci0: sending frame failed (-2)
[Tue Apr 18 07:36:43 2023] Bluetooth: hci0: command 0xfc09 tx timeout
[Tue Apr 18 07:36:51 2023] Bluetooth: hci0: Failed to send firmware data (-110)
[Tue Apr 18 07:36:51 2023] Bluetooth: hci0: Intel reset sent to retry FW download
[Tue Apr 18 07:36:53 2023] Bluetooth: hci0: command 0xfc1e tx timeout
[Tue Apr 18 07:36:53 2023] Bluetooth: hci0: Failed to read MSFT supported features (-110)

Home Assistant will start, but sees problems with the bluetooth adaptor:

Screenshot 2023-04-18 at 07.40.52.png

Home Assistant won't be able to use its bluetooth integration or talk to any bluetooth devices until after a full shutdown and restart.

From the logs, it appears that the AX200 initially boots fine, firmware loads but then the device is reset and it fails subsequently. Does anyone know what the problem could be here? Failing that, is there a way to delay starting the HA VM until after the AX200 is working properly?
 
Absolutely same situation for Intel AX210

Code: 
# dmesg | egrep -i 'blue|firm'
[    0.343245] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    6.794934] Bluetooth: Core ver 2.22
[    6.807846] NET: Registered PF_BLUETOOTH protocol family
[    6.808394] Bluetooth: HCI device and connection manager initialized
[    6.809594] Bluetooth: HCI socket layer initialized
[    6.810340] Bluetooth: L2CAP socket layer initialized
[    6.811049] Bluetooth: SCO socket layer initialized
[    6.871164] Bluetooth: hci0: Firmware timestamp 2023.6 buildtype 1 build 59564
[    6.936395] Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi
[    6.937108] Bluetooth: hci0: Boot Address: 0x100800
[    6.937658] Bluetooth: hci0: Firmware Version: 172-6.23
[    6.938208] Bluetooth: hci0: Firmware already loaded
[    7.221097] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/skl_dmc_ver1_27.bin (v1.27)
[    7.241051] iwlwifi 0000:01:00.0: loaded firmware version 72.a764baac.0 ty-a0-gf-a0-72.ucode op_mode iwlmvm
[   31.137169] Bluetooth: hci0: Device revision is 0
[   31.137275] Bluetooth: hci0: Secure boot is enabled
[   31.137382] Bluetooth: hci0: OTP lock is enabled
[   31.137482] Bluetooth: hci0: API lock is enabled
[   31.137583] Bluetooth: hci0: Debug lock is disabled
[   31.137689] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   31.137823] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38
[   31.184286] Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi
[   31.184562] Bluetooth: hci0: Boot Address: 0x100800
[   31.184669] Bluetooth: hci0: Firmware Version: 172-6.23
[   32.545444] Bluetooth: hci0: Waiting for firmware download to complete
[   32.546172] Bluetooth: hci0: Firmware loaded in 1329809 usecs
[   32.546341] Bluetooth: hci0: Waiting for device to boot
[   33.576490] Bluetooth: hci0: Device boot timeout
[   33.576636] Bluetooth: hci0: Intel reset sent to retry FW download
[   33.736691] Bluetooth: hci0: Failed to read MSFT supported features (-71)

CPU(s) 4 x Intel(R) Core(TM) i5-6400T CPU @ 2.20GHz (1 Socket)
Kernel Version Linux 6.0.19-edge #1 SMP PREEMPT_DYNAMIC PVE Edge 6.0.19-1 (2023-01-13)
PVE Manager Version pve-manager/7.4-3/9002ab8a

Bluetooth working after cold start and stops working after rebooting. Device disappears from list:
1683295647208.png
 
Same for me with the AX200 chip.
Anyone find any solution to this?

Code: 
1241.385692] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
[ 1241.390694] Bluetooth: hci0: Device revision is 1
[ 1241.390700] Bluetooth: hci0: Secure boot is enabled
[ 1241.390701] Bluetooth: hci0: OTP lock is enabled
[ 1241.390702] Bluetooth: hci0: API lock is enabled
[ 1241.390703] Bluetooth: hci0: Debug lock is disabled
[ 1241.390703] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 1241.425801] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[ 1244.582407] Bluetooth: hci0: command 0xfc09 tx timeout
[ 1252.678415] Bluetooth: hci0: Failed to send firmware data (-110)
[ 1252.678487] Bluetooth: hci0: Intel reset sent to retry FW download
[ 1254.854411] Bluetooth: hci0: command 0xfc1e tx timeout
[ 1254.854412] Bluetooth: hci0: Failed to read MSFT supported features (-110)
[86984.463692] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[86984.463696] Bluetooth: BNEP filters: protocol multicast
[86984.463699] Bluetooth: BNEP socket layer initialized
 
I seem to have the same problem.
PVE 7.3-3 and Bluetooth 9460/9560 Jefferson Peak (JfP).
Still no solution?

Code: 
[   22.761609] usb 1-10: New USB device found, idVendor=8087, idProduct=0aaa, bcdDevice= 0.02
[   22.761615] usb 1-10: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[   22.764347] Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015
[   22.765383] Bluetooth: hci0: Device revision is 2
[   22.765386] Bluetooth: hci0: Secure boot is enabled
[   22.765387] Bluetooth: hci0: OTP lock is enabled
[   22.765388] Bluetooth: hci0: API lock is enabled
[   22.765389] Bluetooth: hci0: Debug lock is disabled
[   22.765391] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   22.796932] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi
[   26.176048] Bluetooth: hci0: command 0xfc09 tx timeout
[   34.303795] Bluetooth: hci0: Failed to send firmware data (-110)
[   34.303898] Bluetooth: hci0: Intel reset sent to retry FW download
[   36.479535] Bluetooth: hci0: command 0xfc1e tx timeout
[   36.479536] Bluetooth: hci0: Failed to read MSFT supported features (-110)
[   36.720418] usb 1-10: reset full-speed USB device number 5 using xhci_hcd
[   37.249356] usb 1-10: USB disconnect, device number 5
[   37.555352] usb 1-10: new full-speed USB device number 6 using xhci_hcd
[   37.704334] usb 1-10: New USB device found, idVendor=8087, idProduct=0aaa, bcdDevice= 0.02
[   37.704338] usb 1-10: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[   37.706312] Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015
[   37.707334] Bluetooth: hci0: Device revision is 2
[   37.707337] Bluetooth: hci0: Secure boot is enabled
[   37.707338] Bluetooth: hci0: OTP lock is enabled
[   37.707339] Bluetooth: hci0: API lock is enabled
[   37.707340] Bluetooth: hci0: Debug lock is disabled
[   37.707341] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   37.741136] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi
[   39.209981] Bluetooth: hci0: Waiting for firmware download to complete
[   39.210348] Bluetooth: hci0: Firmware loaded in 1434820 usecs
[   39.210452] Bluetooth: hci0: Waiting for device to boot
[   39.224370] Bluetooth: hci0: Device booted in 13680 usecs
[   39.225466] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-17-16-1.ddc
[   39.227326] Bluetooth: hci0: Applying Intel DDC parameters completed
[   39.230356] Bluetooth: hci0: Firmware revision 0.1 build 214 week 6 2022
[   41.279242] Bluetooth: hci0: command 0x1002 tx timeout
[   43.295475] Bluetooth: hci0: command 0x0c52 tx timeout
[   45.311111] Bluetooth: hci0: command 0x0c45 tx timeout
[   47.327129] Bluetooth: hci0: command 0x0c58 tx timeout
[   49.343006] Bluetooth: hci0: command 0x1004 tx timeout
[   49.343012] Bluetooth: hci0: No way to reset. Ignoring and continuing
[   51.422959] Bluetooth: hci0: command 0xfc1e tx timeout
[   51.422960] Bluetooth: hci0: Failed to read MSFT supported features (-110)
[   51.422964] Bluetooth: hci0: No way to reset. Ignoring and continuing
[   51.659281] usb 1-10: reset full-speed USB device number 6 using xhci_hcd
[   52.065886] usb 1-10: USB disconnect, device number 6
[   52.530922] usb 1-10: new full-speed USB device number 7 using xhci_hcd
[   52.680123] usb 1-10: New USB device found, idVendor=8087, idProduct=0aaa, bcdDevice= 0.02
[   52.680127] usb 1-10: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[   52.682359] Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015
[   52.683332] Bluetooth: hci0: Device revision is 2
[   52.683334] Bluetooth: hci0: Secure boot is enabled
[   52.683335] Bluetooth: hci0: OTP lock is enabled
[   52.683336] Bluetooth: hci0: API lock is enabled
[   52.683336] Bluetooth: hci0: Debug lock is disabled
[   52.683337] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   52.714822] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi
[   54.147343] Bluetooth: hci0: Waiting for firmware download to complete
[   54.148332] Bluetooth: hci0: Firmware loaded in 1399944 usecs
[   54.148426] Bluetooth: hci0: Waiting for device to boot
[   54.162337] Bluetooth: hci0: Device booted in 13663 usecs
[   54.163457] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-17-16-1.ddc
[   54.165338] Bluetooth: hci0: Applying Intel DDC parameters completed
[   54.168314] Bluetooth: hci0: Firmware revision 0.1 build 214 week 6 2022
 
I had the same adapter and Home Assistant work for almost a year, and it just started to silently fail the last week (December 2023) where there was no update to anything. Only a node reboot fixes it, which is supremely annoying. No fix so far.
 
I think I've finally solved this. Bluetooth on Home Assistant has survived several reboots where it would normally fail over 50% of the time.

The errors in the `dmesg` output are all red herrings. Those errors are present even when it works. The problem comes from the host (Proxmox) fighting Home Assistant for control of the bluetooth USB device, even though it has been marked as a passthrough device. If Home Assistant OS is able to get control of the bluetooth device, it retains it until the next OS reboot. Otherwise, Proxmox has control and Home Assistant OS cannot access it.

The solution is to disable Bluetooth-related modules on the host operating system. Go into the shell for the host and check the `lsmod` output to see something like the following:

Code: 
root@proxmox:~# lsmod | grep btusb
Module                  Size  Used by
btusb                  57344  0
btrtl                  20480  1 btusb
btbcm                  16384  1 btusb
btintel                28672  1 btusb
bluetooth             577536  5 btrtl,btintel,btbcm,btusb

From here, you can blacklist btusb to stop Proxmox initializing the device before Home Assistant OS. Add a the line blacklist btusb to /etc/modprobe.d/pve-blacklist.conf. Finally, reboot and bluetooth should work perfectly from now on.
 
andy_e said:
I think I've finally solved this. Bluetooth on Home Assistant has survived several reboots where it would normally fail over 50% of the time.
...
From here, you can blacklist btusb to stop Proxmox initializing the device before Home Assistant OS. Add a the line blacklist btusb to /etc/modprobe.d/pve-blacklist.conf. Finally, reboot and bluetooth should work perfectly from now on.
Click to expand...

Thanks, this really helped me! I was having trouble getting the integrated BT to work in NUC10FNH for Home Assistant running in a VM. :) Finally it works! Thx!
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back