Bluetooth stops working

[louis993546]

The problem

My HA on Intel NUC's Bluetooth (Intel Corporate 07dc) stops working

No logs, nothing, just "Failed setup, will retry: Bluetooth adapter None with address (address) not found)"

I don't know the exact version this started, but my data from Bluetooth stops coming in on April 18th. Is there some way to check what did I updated on that day?

What version of Home Assistant Core has the issue?

core-2025.4.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Bluetooth

Link to integration documentation on our website

https://www.home-assistant.io/integrations/bluetooth/

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant[bot]]

Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration (bluetooth) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of bluetooth can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign bluetooth Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

bluetooth documentation bluetooth source _{^{(message by IssueLinks)}}

[RanTheLab]

Similar issue on a HA Yellow with Raspberry Pi CM4 with wireless (including bluetooth). Seems like it just stopped working out of the blue (I don't remember doing an update of anything). There were some power outages in the area around the time this stopped working...maybe a glitch? It is like the board went bad.

Logger: bluetooth_auto_recovery.recover Source: config_entries.py:751 First occurred: May 6, 2025 at 7:25:08 AM (2617 occurrences) Last logged: 8:19:10 AM

Could not determine the power state of the Bluetooth adapter hci0 [00:00:00:00:00:00] (0) due to timeout after 5 seconds Could not reset the power state of the Bluetooth adapter hci0 [00:00:00:00:00:00] (0) due to timeout after 5 seconds Closing Bluetooth adapter hci0 [00:00:00:00:00:00] failed: [Errno 9] Bad file descriptor

Logger: bluetooth_auto_recovery.recover Source: runner.py:154 First occurred: May 6, 2025 at 7:25:29 AM (872 occurrences) Last logged: 8:17:39 AM

Bluetooth management socket connection lost: [Errno 22] Invalid argument Logger: bluetooth_auto_recovery.recover Source: components/bluetooth/init.py:382 First occurred: May 6, 2025 at 7:25:29 AM (872 occurrences) Last logged: 8:17:39 AM

Could not cycle the Bluetooth adapter hci0 [00:00:00:00:00:00] (0): [Errno 110] Operation timed out

[Redram49RUS]

RK3318 TV BOX same problem, comand hciconfig in armbian show nothing.

UPD: working if don't use armbian-config options in device tree overlay.

I am used rk3318-config, Bluetooth start working

[bencolemann]

Same issue, would really appreciate a fix

[RanTheLab]

Aaaaand mine started working again...the CM4 b/t adapter was recognized after a reboot of the system. Weird.

[obegorka]

Realtek Bluetooth Radio on Firebat AK2 (Intel N150) same problem.

[LaurentRx]

Hello, I have the same Issue with HA bluetooth hardware. I hard-reboot everyday but bluetooth stop sometimes. The only way is to delete bluetooth config, hard-restart and add the bluetooth as new device.

I send you config before bluetooth crash, and after. The error log is the debug file. It was activated before last crash and stopped after.

thanks in adavance.

config_entry-bluetooth-01JTQ647454YF889NAK1YM746F.json config_entry-bluetooth-01JTSE5TQ54Q3S4C9WRCX66BGB.json error_log.txt

Core 2025.5.1 Supervisor 2025.04.1 Operating System 15.2 Interface utilisateur 20250509.0

[lateparty]

Very similar if not identical issue. Intel NUC running proxmox, BT in HA craps itself regularly.

[bdraco]

It sounds like you're experiencing issues with your Bluetooth adapter not being detected. Unfortunately, this is sometimes caused by hardware quirks or driver instability at the kernel level. When an adapter gets stuck like this, the only options are typically to reset it or, if that fails, unplug and replug it. These issues are managed at the OS and driver level, so they're outside of the application’s control.

I understand how frustrating this can be. To avoid these types of problems entirely, I recommend looking into the ESPHome Bluetooth Proxy. It eliminates the dependency on vendor drivers and kernel support, offering a much more reliable experience.

[louis993546]

These issues are managed at the OS and driver level, so they're outside of the application’s control.

Follow-up question: since I am using Home Assistant OS, would you suggest I ask in the operating-system repo to see maybe if some recent changes they can look into?

[mauroc78]

Unplugging and replugging my Asus USB-BT500 solved Bluetooth stops working; I'm using Home Assistant OS 2025.5.3.

Thanks bdraco

It sounds like you're experiencing issues with your Bluetooth adapter not being detected. Unfortunately, this is sometimes caused by hardware quirks or driver instability at the kernel level. When an adapter gets stuck like this, the only options are typically to reset it or, if that fails, unplug and replug it. These issues are managed at the OS and driver level, so they're outside of the application’s control.

I understand how frustrating this can be. To avoid these types of problems entirely, I recommend looking into the ESPHome Bluetooth Proxy. It eliminates the dependency on vendor drivers and kernel support, offering a much more reliable experience.

[spartyparty00]

Same issue on Yellow CM4 2025.7.4 and 2025.07.3 supervisor.

[ashthespy]

An old issue (https://github.com/home-assistant/core/issues/98523) has resurfaced for me after a recent update. My AX101 is no longer recognized with lsusb either in the VM. I have no issues with other VMs with pass through, so not sure what changed recently?

Installation method Home Assistant OS
Core 2025.8.2
Supervisor 2025.08.1
Operating System 16.1
Frontend 20250811.0

[MichaelMKKelly]

I spent some time on it today and I have resolved the issue on my EQ14:

The problem: when proxmox boots it loads the BT drivers which puts the BT adaptor into its loaded state which is not reset when it is moved to the VM via passthrough. so when the VM tries to set it up its in the wrong state.

the solution: prevent proxmox from loading the BT drivers so that that the adaptor stays in its non-loaded state which can then be "loaded" by the guest OS (in this case HAOS)

the method: on proxmox shell open /etc/modprobe.d/blacklist.conf with your preferred text editor (create the file if needed) add the following lines

blacklist btusb
blacklist bluetooth
install bluetooth /bin/true

reboot the host system.

HAOS should now be able to see the device correctly.

theory on why it started happening: a proxmox/kernel update somewhere that changed how stuff is loaded.

warning: This assumes you dont ever want to use a bluetooth adaptor on your host OS for any reason though. i feel its unlikly someone might have multiple bluetooth adaptors and sues one on the host for a different purpose but its theoretically a possible issue to look out for

NB: This does not seem to be a core issue.

[ashthespy]

Did something change in HASOS recently. I see https://github.com/home-assistant/operating-system/issues/4060 that suggests blacklisting, but I didn't have to previously? But thanks, this blacklisting does the trick for me :-)

[MichaelMKKelly]

Did something change in HASOS recently. I see home-assistant/operating-system#4060 that suggests blacklisting, but I didn't have to previously? But thanks, this blacklisting does the trick for me :-)

I think its possibly something to do with a kernel update rather than HAOS itself but i am not 100% sure.

[PinoQuack]

Ho un problema con Realtek Bluetooth 5.1 Adapter riesco a installare l'integrazione Bluetooth sul mio HAOS montato su VM della Oracle (Metodo di installazione Home Assistant OS Core 2025.10.2 Supervisor 2025.10.0 Operating System 16.2 Frontend 20251001.2) L'integrazione rileva una numerosa serie di dispositivi nel suo raggio di rilevazione m; ma non ne rileva nessuno attivo. Nell'hardware non figura nessuna voce corrispondente a hci e perdo la gestione bluetooth nel sistema host. Non ci capisco nulla!!!!

[worldgod13]

I spent some time on it today and I have resolved the issue on my EQ14:

The problem: when proxmox boots it loads the BT drivers which puts the BT adaptor into its loaded state which is not reset when it is moved to the VM via passthrough. so when the VM tries to set it up its in the wrong state.

the solution: prevent proxmox from loading the BT drivers so that that the adaptor stays in its non-loaded state which can then be "loaded" by the guest OS (in this case HAOS)

the method: on proxmox shell open /etc/modprobe.d/blacklist.conf with your preferred text editor (create the file if needed) add the following lines

blacklist btusb
blacklist bluetooth
install bluetooth /bin/true

reboot the host system.

HAOS should now be able to see the device correctly.

theory on why it started happening: a proxmox/kernel update somewhere that changed how stuff is loaded.

warning: This assumes you dont ever want to use a bluetooth adaptor on your host OS for any reason though. i feel its unlikly someone might have multiple bluetooth adaptors and sues one on the host for a different purpose but its theoretically a possible issue to look out for

NB: This does not seem to be a core issue.

Worked for me...thanks!