Bluetooth failing after upgrade to HAOS 10 on Intel Bluetooth hardware #2535
Comments
agners
added
bug
board/generic-x86-64
|
Before: Immediately after updating (same as before I guess because the host hasn't restarted?): After poweroff, unplugging, leaving for a bit and powering on again: |
|
After boot is everything working for me and i have a clean log like on 9.5. But after some time, it will stop working. |
|
FWIW, it doesn't appear to consistently break on boot. Sometimes it's fine, Bluetooth works for a bit, then stops working entirely: (I edited the above logs because I think I c&p'd the wrong thing) |
|
As suggested in the other thread I’m downgrading to OS 9.5 via command Terminal (ha os update --version 9.5) |
|
Just seen this appear in my logs, I've not seen it before, don't know if it's a red-herring: and |
Downgrade done with success and all devices are detected and working as intended. At the moment no issues detected on OS 9.5 |
Same on my side. |
|
Fails for me on HAOS 10 as well. H/W Intel NUC. ➜ ~ ha host logs -t kernel -n 1000000 -b 0 | grep Bluetooth | head -n 100
May 07 19:58:14 homeassistant kernel: Bluetooth: Core ver 2.22
May 07 19:58:14 homeassistant kernel: Bluetooth: HCI device and connection manager initialized
May 07 19:58:14 homeassistant kernel: Bluetooth: HCI socket layer initialized
May 07 19:58:14 homeassistant kernel: Bluetooth: L2CAP socket layer initialized
May 07 19:58:14 homeassistant kernel: Bluetooth: SCO socket layer initialized
May 07 19:58:16 homeassistant kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
May 07 19:58:16 homeassistant kernel: Bluetooth: BNEP filters: protocol multicast
May 07 19:58:16 homeassistant kernel: Bluetooth: BNEP socket layer initialized
May 07 19:58:16 homeassistant kernel: Bluetooth: hci0: command 0xfc05 tx timeout
May 07 19:58:16 homeassistant kernel: Bluetooth: hci0: Reading Intel version command failed (-110)The tx timeout is also mentioned in kernel bug https://bugzilla.kernel.org/show_bug.cgi?id=215167 |
|
I have INTEL NUC, and I have problem with bluetooth too with HAOS 10.
|
@d-d your case seems to be a bit different as there are errors. The one I see (and others too I think) doesn't show anything in the logs. The error you linked mentions the problem appears on Linux 5.15 as well. Did your hardware work reliably with HAOS 9.5? |
|
I also have same problem with HAOS v10.1 on Intel(R) Atom(TM) x5-Z8500 system. I've downgraded to 9.5 and everything is working fine in BT side. |
|
@yildiraymeric can you check the logs using |
|
I also experience Bluetooth issues on two Intel NUC installations with internal Bluetooth. Both NUC 10. As a workaround I created an automation which reloads the Bluetooth integration when a couple of sensors (to prevent empty batteries reloading Bluetooth constantly) report unavailable. I also have made an automation for my SwitchBot bot which reloads the Bluetooth integration before toggling the actual bot. |
|
same issue here. |
|
Intel NUC Kit NUC6i7KYK Intel i7-6770HQ No config changes |
|
Just instal HAOS bare metal on a mini pc using Intel Wireless-AC 3165 - Can't even get the OS to recognise there is a bluetooth device connected |
|
The problem still not solved, bluetooth device restoring connection after couple of hours. But it working not good with HAOS 10.
|
|
I recently bought one of the certified bluetooth dongles (the Sabrent BT-UB40). Weird thing is that a roll back to 9.5 does not fix the problem - both for the onboard and the Sabrent. Minisforum GK41 with onboard bluetooth and Sabrent BT-UB40 |
|
I tried 10.2 today and it still does not work. Specifically my Inkbird IBS-TH2 sensors are unavailable. Rolling back to 9.5 and everything is working again. |
Same for me on my NUC11 (RNUC11PAHi50000). |
|
@agners I'd to ask if you are trying to make that change upstream to the kernel, I know that it's not a problem for HAOS anymore but there are many HA running on different distributions affected by this bug. |
|
So far, yes. The locks are very responsive and seem to work all the time with no drop outs. I guess I'll break it one more time for the cause! |
|
I opened a new bug in OS I didn't see much in Host logs though. Do I need to enable some more advanced logging? |
|
I can confirm some issues remain on (at least) NUC it seems. I have a NUC 10, have 2 different bluetooth devices both with simultaneous connection issues at random moments and random duration.. See below screenshot for example. HAOS 9.5 -> 10.1 (issues began) Has another ticket been opened somewhere for this? (Edit: Sorry, misread your previous comment. There has, i`ll join you there) Happy to provide more input if needed.
|
I've brought it up on the Bluetooth Linux kernel mailing list, see: However, no progress so far. On what OS do you observe the issue? |
|
I run Proxmox 7.4-3 on my Intel Nuc. Proxmox is shipped on top of Debian (version 11). Executed on the NUC (debian): |
|
Several days without any issue, so fixed for me!, thanks a lot @agners |
my home assistant server is also HTPC it's a small Asus pn52 box running Ubuntu 22.04 after upgrading to 23.04 I see the same problem with BLE connection dropouts |
|
I upgraded my Supervised installation from Debian 11 to Debian 12, and now facing the same issue with my Intel bluetooth adapter. Definitely something to do with kernel 6.1 I would say. |
agners
added
the
stable-kernel-regression
|
@yannpub as I see proper fix was merged to linux-next so when I get it right Linux kernel 6.6 should be working again for us ... |
|
Hi, @Sorien! Does this mean it will be fixed in the next (or any upcoming) HASS OS release? I see 10.5 currently uses 6.1.45..? |
|
@bjornarfjelldal HAOS is patching kernel so it should be fixed with any version newer than Aug 30. |
|
@yannpub @Sorien I've noticed that the Bluetooth fix |
|
Note that with HAOS 11.0 the |
|
Hi! I really appreciate your efforts in trying to resolve bluetooth in HAOS 11.0, since it has been especially buggy and variable over the past year. However, after updating from 10.5 to 11.0 (on an Intel NUC using Proxmox) bluetooth seemingly has become even worse than before. I have tried to delete the BT integration, toggle passive scanning on and off and physically reboot host. Running "bluetoothctl" in terminal addon produced a lof devices logs, but doesn't help much on stability. The console reports "Bluetooth: hci0 opcode 0x200e failed -16". Anything I should try to do - or logs I should provide? |
|
Hi all, I am also running HAOS 11.0 on Intel NUC (NUC10i3FNH2) using Proxmox and so far (16 hour) so good ! I must admit that it was running ok-ish on 10.x with only 2 or 3 short bluetooth gaps per day. Let us know how that worked! Edit: some days later it turns out I still experience a +- daily disconnect for some hours so for me HAOS 11.0 (and later 11.1) did not fix the issue... |
|
I updated my HTPC to Ubuntu 23.10 and kernel 6.5.7 and I can confirm Bluetooth devices are working again |
|
This STARTED happening after upgrading HA OS to 11.2. I haven't had a single BT failure since installing the machine a year ago. |
|
seems Same issue for me. can we get a kernel upgrade instead of downgrading the os? I have other new hardware and only kernel 6.6 fixes issues. note kernel 6.1 is way behind current LTS of 6.6 |
|
home-assistant/core#92379 (comment) Kernel 6.6 is now LTS. I have lots of hardware bought in the last few months that have issue with various subsystems with anything less that 6.6. Now that 6.6 is LTS hassos should be upgraded (maybe a major upgrade). |
6.1 was the last LTS, and 6.6 was announced a couple weeks ago, not sure if I would label that as "way behind". But, yes, upgrading to 6.6 LTS is on our todo list. A PR with patches rebased and validated on all supported platforms is of course very welcome 😉 |
|
FYI, I have just installed HA OS version 12.0rc1. The RPi controller has connected without the passive mode, and my device has been reporting without issues for a few hours now. 🤞 |
|
I still have this issue. Just installed Uniraid on my Asus NUC and running HA through a VM on Uniraid. When I try to pass the Intel Chip through as an USB I get this in the HA logs:
Any other known solutions? |
and others
@agners This is the result of the command
I don't know if this is related but In Home Assistant System>Logs> Host is full of messages like this:
May 03 20:09:04 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-799946efbb48db91e285d1e93f36945c7175e095d2a5a9fe838fde71f8e6ffdf-runc.jJmMvJ.mount: Deactivated successfully.
May 03 20:09:20 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-7aee883888a9e7d1b71b97ddbc2b231c2763cc47b14b2c728d6d0de7ab1c2e00-runc.RpO30d.mount: Deactivated successfully.
May 03 20:09:34 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-799946efbb48db91e285d1e93f36945c7175e095d2a5a9fe838fde71f8e6ffdf-runc.sMXYc7.mount: Deactivated successfully.
May 03 20:09:50 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-7aee883888a9e7d1b71b97ddbc2b231c2763cc47b14b2c728d6d0de7ab1c2e00-runc.QivMYX.mount: Deactivated successfully.
May 03 20:10:04 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-799946efbb48db91e285d1e93f36945c7175e095d2a5a9fe838fde71f8e6ffdf-runc.ypP5rP.mount: Deactivated successfully.
May 03 20:10:20 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-7aee883888a9e7d1b71b97ddbc2b231c2763cc47b14b2c728d6d0de7ab1c2e00-runc.r9dWM5.mount: Deactivated successfully.
Originally posted by @SrBurner in #2485 (comment)
The text was updated successfully, but these errors were encountered: