Intel BE200 Bluetooth (USB) unstable in HAOS 18.1 – HCI timeout / reset loop in VM environment

Installation
1

I am running Home Assistant OS 18.1 in a Proxmox virtual machine on an Intel Core Ultra 9 285H (Arrow Lake) system.

The system uses an Intel BE200 Bluetooth (integrated) adapter (USB device, VID:PID 8087:0036) passed through to the HAOS VM via USB passthrough.

The device is detected, but Bluetooth initialization fails with repeated timeouts and resets:

Bluetooth: hci0: Reading Intel version command failed (-110)
Bluetooth: hci0: command 0xfc05 tx timeout
Bluetooth: hci0: Resetting usb device.

This loop continues indefinitely and no functional HCI controller is exposed to Home Assistant.

Environment:

  • Home Assistant OS: 18.1
  • Host: Proxmox VE (latest stable)
  • CPU: Intel Core Ultra 9 285H (Arrow Lake)
  • Bluetooth device: Intel BE200 (USB, 8087:0036)
  • Connection method: USB passthrough to VM

Observations:

  • Device is visible in lsusb
  • No hci0 usable interface is available in Home Assistant
  • Kernel repeatedly resets the USB device due to command timeouts
  • Zigbee USB devices on same system work correctly (no USB issues in general)

Question

Is Intel BE200 currently supported in HAOS for Bluetooth LE in virtualized environments, or are there known limitations with this chipset (especially in USB passthrough scenarios)?

2

Hello guybrush262,

Are you using a bluetooth device that is on the Known to Work list.

Getting Bluetooth to work for HA is tricky.
I highly recommend setting up a couple of Bluetooth proxy's from the ESPHome project instead. Ready-Made Projects - ESPHome - Smart Home Made Simple

3

Thank you for the quick reply. Maybe I was not clear since I think that list is only for external adapters (if I correctly uderstood), while mine is internal to the pc

4

I can understand the desire to use the internal but suspect you will struggle. I have an external USB on my Proxmox host with no issues. I’d disable in BIOS or remove if in an M.2. slot. The other advantage with USB is you can put it on a long cable to improve range.

Another vote for Bluetooth proxies as well.

5

The list is the known to work ones. If it's on the list, internal/external/virtual/imaginary, it's known to work. Not on the list is not on the list.
BT proxys are tweaked to HA's needs, so in nearly every case they respond faster as well. Highly suggest a BT Proxy.

6

The same started to happen to me after upgrading HAOS.
I also use an Intel BT integrated chip shared on Proxmox.
This worked perfectly before the last update. So, this is not due to the hardware being incompatible.
Also, if I shut down the VM and the host and restart it, then everything works fine for a few hours.
The BT integrated adapter works on HA, and I use it to connect to my power station to get its stats.
Then, since HAOS update, it becomes unavailable on HA.
Checking on the console, it show:

ha > [52975.5688791 Bluetooth: hci0: Opcode 0x2005 failed: -110
[52975.569900] Bluetooth: hci0:
[52975.570380] Bluetooth: hci0: Resetting usb device.
17 Replication
[52975.570384] Bluetooth: hcio: Opcode
[52975.571273] Bluetooth: hci0: urb 00000000c5821d00 failed to resubmit (2)
Snapshots
[52975.571434] Bluetooth:
Firewall
Permissions
[52977.616920] Bluetooth:
command 0x2005 tx timeout
[52977.617936] Bluetooth: hci0: Resetting usb device.
[52977.617958] Bluetooth: hci0: Reset after hardware error failed (-110)
[52978.154470] Bluetooth: hci1: urb 00000000a7a0e2e4 failed to resubmit (2)

etc. this repeats until I reboot the host.