core icon indicating copy to clipboard operation
core copied to clipboard

Bluetooth stops working on 2025.5 intel nuc

Open bencolemann opened this issue 7 months ago • 4 comments

The problem

As others have reported, my Bluetooth has failed to load and doesn’t see the Bluetooth chip in my intel nuc. Logs attached. I’d really appreciate a fix as I rely on this to manage my home battery system. Thanks

What version of Home Assistant Core has the issue?

2025.5.0

What was the last working version of Home Assistant Core?

2025.4

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

home-assistant_2025-05-08T13-44-54.841Z.log

home-assistant_bluetooth_2025-05-08T13-38-20.022Z.log

Example YAML snippet


Anything in the logs that might be useful for us?


Additional information

Anything else let me know

bencolemann avatar May 08 '25 13:05 bencolemann

Image Image

bencolemann avatar May 08 '25 13:05 bencolemann

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)

home-assistant[bot] avatar May 08 '25 16:05 home-assistant[bot]

Facing the same issue, also on an intel NUC.

fedexultra avatar May 11 '25 07:05 fedexultra

Please check host and supervisor logs. I suspect there will be more information there.

bieniu avatar May 12 '25 07:05 bieniu

I also had this very same issue, However I got it working (HA 2025.5.2), I entered the BIOS of the NUC and disabled Bluetooth, ran HA and deleted the failed intel Bluetooth integration and did a restart. Then did a complete shutdown. Re-entered the BIOS and turned Bluetooth back on. When I restarted HA it had discovered the Bluetooth, I added the integration and now all is working fine.

Tadpole48 avatar May 17 '25 13:05 Tadpole48

I have the same issue on my older NUC

Nisbo avatar May 24 '25 06:05 Nisbo

I also had this very same issue, However I got it working (HA 2025.5.2), I entered the BIOS of the NUC and disabled Bluetooth, ran HA and deleted the failed intel Bluetooth integration and did a restart. Then did a complete shutdown. Re-entered the BIOS and turned Bluetooth back on. When I restarted HA it had discovered the Bluetooth, I added the integration and now all is working fine.


This worked PERFECTLY, thanks!

MHEAD666-DOT avatar Jun 17 '25 18:06 MHEAD666-DOT

I am using HA OS as VM on unraid, and I have the same issue. Tried to not pass through the BT device, restart, then pass it through again, no luck.

SuperMario86 avatar Jun 18 '25 18:06 SuperMario86

I have somewhat the same issue, I'm running proxmox with bluetooth passthrough on a NUC 15 Pro (i3).

Before enabling thunderbolt support it all worked fine, but I need this for my USB SSD to get recognized. After enabling that, the passthrough still works, I can also see the device appear in Home Assistent, but it does not get recognized as a bluetooth adapter anymore. Resulting with the same GUI message as OP.

Disabling in BIOS -> Start and remove in HA -> Enabling in BIOS as suggested here, did not work for me. I do see these log messages in Host:

2025-07-10 14:28:29.999 homeassistant kernel: Bluetooth: hci0: Firmware timestamp 2025.7 buildtype 1 build 76693
2025-07-10 14:28:29.999 homeassistant kernel: Bluetooth: hci0: Firmware SHA1: 0x9919f053
2025-07-10 14:28:30.000 homeassistant kernel: Bluetooth: hci0: Found device firmware: intel/ibt-0291-0291.sfi
2025-07-10 14:28:30.000 homeassistant kernel: Bluetooth: hci0: Boot Address: 0x100800
2025-07-10 14:28:30.000 homeassistant kernel: Bluetooth: hci0: Firmware Version: 17-49.24
2025-07-10 14:28:30.013 homeassistant kernel: Bluetooth: hci0: FW download error recovery failed (-19)
2025-07-10 14:28:30.023 homeassistant systemd[1]: Reached target Bluetooth Support.
2025-07-10 14:28:30.026 homeassistant systemd[1]: Stopped target Bluetooth Support.
2025-07-10 14:29:27.856 homeassistant kernel: Bluetooth: hci0: Firmware timestamp 2025.7 buildtype 1 build 76693
2025-07-10 14:29:27.856 homeassistant kernel: Bluetooth: hci0: Firmware SHA1: 0x9919f053
2025-07-10 14:29:27.859 homeassistant kernel: Bluetooth: hci0: Found device firmware: intel/ibt-0291-0291.sfi
2025-07-10 14:29:27.871 homeassistant kernel: Bluetooth: hci0: Boot Address: 0x100800
2025-07-10 14:29:27.871 homeassistant kernel: Bluetooth: hci0: Firmware Version: 17-49.24
2025-07-10 14:29:27.871 homeassistant kernel: Bluetooth: hci0: FW download error recovery failed (-19)
2025-07-10 14:29:27.871 homeassistant systemd[1]: Reached target Bluetooth Support.
2025-07-10 14:29:27.876 homeassistant systemd[1]: Stopped target Bluetooth Support.

Does anyone have an idea how to solve this?

EDIT: Solved it myself, in my case Proxmox was trying to use the device itself. Solved it with these commands in Proxmox:

echo "blacklist btusb" > /etc/modprobe.d/blacklist-btusb.conf
update-initramfs -u
reboot

Xitro01 avatar Jul 10 '25 14:07 Xitro01

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant 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.