Error communicating with local bluetooth adapter (RPi3) #30147
Comments
|
Could be related to this issue #30116 |
|
I think it might be. Failed to update to 0.103.4. Bluetooth trackers were dead and error communicating with local bluetooth adapter in logs. Rebooted, bluetooth trackers started working again, updated to 0.103.4 just fine. Just waiting for Bluetooth to die again now....... |
|
Having the same issue. |
|
This relates to why I'm getting unavailable with my miflora. I've also noticed that this issue came about with 0.103. Some findings:
workaround in cli:
See here for the workaround: https://docs.ubuntu.com/core/en/stacks/bluetooth/bluez/docs/troubleshoot/faq I'm facing this issue on Hassio 0.103.4 on a Raspberry Pi 3b. |
|
I have this issue too, same error in logs and it repeats hundreds of time.. So at this moment I have no bluetooth presence working. |
|
We use Bluetooth exclusively but ended up installing HACS and this little gem so now we track using both Wifi and Bluetooth until this is fixed |
|
Issue still here with 0.103.6. |
|
It looks like a problem with HassOS 3.7 - I've no problems with Bluetooth with versions 0.103.x till OS update… (I've had HassOS 2.12 before and BT was working normal) |
|
Has anyone tried this with the latest beta release? |
|
Same issue on 0.104.0b3. It works for a few minutes, then I need to reboot the PI. |
|
running HassOS 3.8 and 0.101.2 worked for about 9 hours, at least once. |
|
Same here. |
|
same here, tried just now with 3.8 |
|
Same here, on 0.104.2 and HassOS 3.8. Is it possible that something is trying to use this serial port, and that's why bluetooth is failing? I've think I've read (although, I can't find the source now) that somewhere between version 0.90 and 0.100 the docker image of homeassistant switched from using Debian to Alpine as it's base - maybe that image is trying to access console for some reason? I'm not well versed in Docker or Linux, so I can't really verify anything on my own... I tried modifying the cmdline.txt file, and removing the "console=tty1" part. It didn't help. I also tried disablind the SSH Add-on (based on a wild guess, that it might be using the serial port), but it didn't help either. |
|
No traction on this? |
|
I have the same problem. It may a problem with the UART's of the Pi 3. For what I now understand the Pi 3 has two UART's. There is the primary UART ttyAMA0 ( a PL011 chip) and the ttyS0 ( miniUART ). "dtoverlay=pi3-miniuart-bt" changes the UART used by bluetooth to the miniUART so that ttyAMA0 could provided at GPIOs 14 and 15. But it have now a changing baud rate cause governor changing the core frequency according to the needed performance. Bluetooth don't like a changing baut rate. "enable_uart=1" enable the mini UART and provide ttyS0 at GPIOs 14 and 15. If I set only the pi3-miniuart-bt flag ttyS0 and ttyAMA0 both working. So I guess that pi3-miniuart-bt sets enable_uart. According to some websites enable_uart set core_freq=250 what stabilises the baud rate of the mini UART. But everywhere is stated that you should set core_freq=250 manually. Alternatively you could set force_turbo=1 what locks the core frequency to 400MHz and may better the performance of the mini UART. Most of this information could found here: https://www.raspberrypi.org/documentation/configuration/uart.md A other thing I discovered is that as I reflashed HassOS with the new version the default config.txt is completly different from the updated HassOS. Relevant? I discoverd so far that bluetooth work with this set of options in config.txt (at least a 24h testing) And I deleted the console part in the cmdline.txt. Now I'm testing this settings And switched HomeMatic CCU to ttyS0. So bluetooth is on ttyAMA0. That works very well for one hour now. I really don't know whether this could be a thing, but if I set force_turbo my ConBee stick seems to have problems. I know that the stick uses a own UART over USB. May it is affected from force turbo? Update: |
|
Do you have these errors in dmesg? As far as these appear bluetooth communication is interrupted. |
|
I have a lot of errors connected to hci0 After setting |
|
So here is the original issue probably: |
|
My bluetooth sadly stopped working today... After reboot I've got only 5 working minutes. So the behavior is like before. |
|
HassOS 3.9 seems to have fixed this issue for me, miflora sensors haven’t failed yet. |
|
I re-added my bluetooth device tracking after your message but unfortunately after updating to HassOS 3.9 and 0.105.1 core |
|
Raspberry Pi 3B+ and bluetoothctl just freezes |
|
This issue has been mentioned on Home Assistant Community. There might be relevant details there: https://community.home-assistant.io/t/bluetooth-stops-tracking-in-the-middle-of-the-night/123710/9 |
|
I continue to keep having this issue with BT tracking crashing with any version of HassOS 3.x on a RP3b. BT tracking is solid on HassOS 2.12. I have a wired network connection and wifi not configured. To easily roll back to HassOS 2.12, run the following command from SSH. |
|
HassOS 3.10 Still having issues. |
|
HassOS 3.11 Still having issues. |
|
Is there any update on this ? |
Only thing that worked for me was to downgrade to 2.12 as mentioned above. |
This problem is referenced in many different issues, some of them: Bluetooth: hci0: Frame reassembly failed (-84) raspberrypi/firmware#1150 Error communicating with local bluetooth adapter (RPi3) home-assistant/core#30147 Xiaomi BLE Temperature and Humidity sensor no longer working after update from 0.95.4 to .096.5 home-assistant/core#25704 Xiaomi BLE Temperature and Humidity sensor home-assistant/core#24313 (comment) Solution seemed to reeduce the boud rate of the serial connection to BT on rpi3b where flow control is missing. The patch to the original btuart file is to reduce the baudrate only for rpi3b models where flow control is missing: - $HCIATTACH /dev/serial1 bcm43xx 921600 noflow - $BDADDR + $HCIATTACH /dev/serial1 bcm43xx 460800 noflow - $BDADDR I'm not a buildroot expert but the best way seemed to move the upstream btuart download in a PRE_PATCH_HOOK so that standard buildroot way of patching can be applied.
This problem is referenced in many different issues, some of them: Bluetooth: hci0: Frame reassembly failed (-84) raspberrypi/firmware#1150 Error communicating with local bluetooth adapter (RPi3) home-assistant/core#30147 Xiaomi BLE Temperature and Humidity sensor no longer working after update from 0.95.4 to .096.5 home-assistant/core#25704 Xiaomi BLE Temperature and Humidity sensor home-assistant/core#24313 (comment) Solution seemed to reeduce the boud rate of the serial connection to BT on rpi3b where flow control is missing. The patch to the original btuart file is to reduce the baudrate only for rpi3b models where flow control is missing: - $HCIATTACH /dev/serial1 bcm43xx 921600 noflow - $BDADDR + $HCIATTACH /dev/serial1 bcm43xx 460800 noflow - $BDADDR I'm not a buildroot expert but the best way seemed to move the upstream btuart download in a PRE_PATCH_HOOK so that standard buildroot way of patching can be applied.
|
I ended up upgrading to RPi4b, for other reasons, and that "solved" this problem for me. |
Great to know that a raspberry pi 4 works with the new Bluetooth libraries. Did you find any new issues / capability problems with the raspberry pi 4 (eg with other hardware links or integrations?) |
|
No, not at all. Everything works perfectly with the RPi4, and I push it quite hard (Hassio, Node-RED, NGINX rev. proxy, AdGuard, MariaDB, several MB of config, loads of template sensors, and so on). A problem with the RPi3 that was a bit annoying, was that restarting Home Assistant didn't work; I had to restart the host (reboot). Trying a restart of Hone Assistant from the GUI always resulted in hanging just before the startup was finished. Never figured out why. This too went away with changing to RPi4, without changing anything in the config. I just flashed the 32-bit image for RPi4 onto a new MicroSD, installed Samba, uploaded my latest config and made a "Wipe & Restore". The only HW-problem you might face is if you use a Aeotec Z-Stick, because it does not comply properly with the USB-standard, which creates problems on USB3. It does not help plugging it into one of the USB2-ports on the RPi4, but you need to get a little USB2-hub (NOT USB3), which acts as an isolator for the non-compliant USB-signalling going on with the Z-Stick at startup. |
This problem is referenced in many different issues, some of them: Bluetooth: hci0: Frame reassembly failed (-84) raspberrypi/firmware#1150 Error communicating with local bluetooth adapter (RPi3) home-assistant/core#30147 Xiaomi BLE Temperature and Humidity sensor no longer working after update from 0.95.4 to .096.5 home-assistant/core#25704 Xiaomi BLE Temperature and Humidity sensor home-assistant/core#24313 (comment) Solution seemed to reeduce the boud rate of the serial connection to BT on rpi3b where flow control is missing. The patch to the original btuart file is to reduce the baudrate only for rpi3b models where flow control is missing: - $HCIATTACH /dev/serial1 bcm43xx 921600 noflow - $BDADDR + $HCIATTACH /dev/serial1 bcm43xx 460800 noflow - $BDADDR I'm not a buildroot expert but the best way seemed to move the upstream btuart download in a PRE_PATCH_HOOK so that standard buildroot way of patching can be applied.
|
Hi all, I've just finished to install on my rpi3b an image I've built with a possible fix. It's an unofficial version built from development branch. |
|
I've installed your image and it's working so far. But it usually works a few days after reflashing any image. So I will report then again. |
|
thank you @wraith11 for your help let me know!! |
|
We running: On a Pi 4. Using the bluetooth to track our iPhones and only get "home" / "away" alternating throughout the day. Have been following various threads with no luck. Though upgrading to the latest might have a firmware fix. See people are having luck with the Pi 4? |
This problem is referenced in many different issues, some of them: Bluetooth: hci0: Frame reassembly failed (-84) raspberrypi/firmware#1150 Error communicating with local bluetooth adapter (RPi3) home-assistant/core#30147 Xiaomi BLE Temperature and Humidity sensor no longer working after update from 0.95.4 to .096.5 home-assistant/core#25704 Xiaomi BLE Temperature and Humidity sensor home-assistant/core#24313 (comment) Solution seemed to reeduce the boud rate of the serial connection to BT on rpi3b where flow control is missing. The patch to the original btuart file is to reduce the baudrate only for rpi3b models where flow control is missing: - $HCIATTACH /dev/serial1 bcm43xx 921600 noflow - $BDADDR + $HCIATTACH /dev/serial1 bcm43xx 460800 noflow - $BDADDR I'm not a buildroot expert but the best way seemed to move the upstream btuart download in a PRE_PATCH_HOOK so that standard buildroot way of patching can be applied.
|
I have been running 3.13 now for a day and for me it has been working without any issue, no error logs, no dropout of bluetooth. HassOS 3.13 |
|
In the meantime, I've migrated to the amd64 platform, but I specifically implemented an additional Raspberry HA installation to confirm this patch, so I can also confirm working fix in version 3.13, but on different hardware: RPi 3B+ HassOS 3.13 |
|
Okay, since I have @lucagiove 's unofficial build running I had a few bluetooth problems. But they always gone after a reboot. I might have too much going on on my bluetooth device. |
|
Same for me, I'm glad to say that it seems I managed to fix this. |
|
Same here, I would agree that it looks like the bluetooth issue has been fixed with 3.13 for RP3B after running it for a few days. Thank you!! HassOS 3.13 |
|
Same ! Issue seems to be fixed with OS 3.13 on my RP3B. |
|
I've upgraded to a rpi4 since I opened this issue, so can't comment personally, but thank you very much @lucagiove |
|
same issue here in 0.116.4 |
|
I'm also facing this issue since the last HassOS update to 4.14 |
|
You can revert to 4.13 with |
core 0.116.2 here, my system was indeed on 4.14 and update to 4.15 finally ended/solved this "Error during Bluetooth LE scan: No BLE adapter found" issue. (tagging for search) Thanks for information and fix! |
and others
Home Assistant release with the issue:
0.103.2 & 0.103.3
Last working Home Assistant release (if known):
0.103.1
Operating environment (Hass.io/Docker/Windows/etc.):
Integration:
https://www.home-assistant.io/integrations/device_tracker/
Description of problem:
This might be due the recent upgrade of HassOS to v3 but I don't understand enough about these things!
My bluetooth device trackers are currently all broken and stuck on away. They sometimes work for a while after a reboot, but will fail at some point
Problem-relevant
configuration.yamlentries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information:
The text was updated successfully, but these errors were encountered: