-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bluetooth HCI reset failed #3725
Comments
same issue on beelink MiniPC. Service bluetoothd gets hung for several minutes on bare metal and ProxMox forwarded internal BT controller. |
@Terikos You say the NUC (which model is it exactly?) doesn't have Bluetooth but the kernel very much thinks so. Can you post the logs of the boot, i.e. the part of the host logs which start with something like "Linux version 6.6.63-haos" and the following ~10 seconds of logs. Alternatively, if you don't want to use the integrated Bluetooth, there's usually option for disabling it somewhere in the BIOS menu. @jonpaterson How come is this the same issue? Do you see the same (meaning exactly the same) messages? Proxmox OR bare metal install? At least please share more details about the hardware and symptoms. |
Same here. Oracle VM Virtual Box, on ThinkPad T450s. Bluetooth is the one integrated to the laptop. No usb dongle whatsoever. |
@sairon I saw the EXACT same issue on both hardware and Proxmox. The serivice took around 5 mins to kill (likely the systemd timeout). Here is the dmesg items that might be interesting on the hardware type (13.2) [ 2.424914] Bluetooth: hci0: Firmware timestamp 2023.48 buildtype 1 build 75324 |
This is old NUC hardware without Bluetooth. Intel BOXNUC5CPYH, N3050, DDR3L-1600, SATA3, HDMI, SDXC slot, USB 3.0, BOX I’ve already checked in BIOS and there is no any option for Bluetooth :( |
Describe the issue you are experiencing
Since upgrade core to version 14.0 on the console of my Intel NUC I have repeating message:
Bluetooth: hci: sending initial HCI reset failed (-19).
My NUC doesn’t have build Bluetooth. I tried to disable service but systemd file system is read only, so it is not possible.
What operating system image do you use?
generic-x86-64 (Generic UEFI capable x86-64 systems)
What version of Home Assistant Operating System is installed?
6.6.63-haos
Did the problem occur after upgrading the Operating System?
Yes
Hardware details
X86 based hardware
Steps to reproduce the issue
After start HAOS
Anything in the Supervisor logs that might be useful for us?
Anything in the Host logs that might be useful for us?
System information
Version core-2024.12.1
Installation type Home Assistant OS
Development false
Supervisor true
Docker true
User root
Virtual environment false
Python version 3.13.0
Operating system family Linux
Operating system version 6.6.63-haos
CPU architecture x86_64
Additional information
N/a
The text was updated successfully, but these errors were encountered: