Bluetooth Probleme

dietzi · December 30, 2023, 4:28pm

Hello. I use an Intel NUC with Bluetooth onboard. However, I have problems with the Delonghi integration. It seems as if the data is split over Bluetooth and therefore not processed correctly by the integration. Can/must I set something somewhere so that the data arrives properly?

This integration is used via HACS: GitHub - Arbuzov/home_assistant_delonghi_primadonna: Home assistant integration for the Delonghi coffee machine

boheme61 · December 30, 2023, 4:29pm

dietzi · December 31, 2023, 10:12am

Hello. I use an Intel NUC with Bluetooth onboard. However, I have problems with the Delonghi integration. It seems as if the data is split over Bluetooth and therefore not processed correctly by the integration. Can/must I set something somewhere so that the data arrives properly?

This integration is used via HACS: GitHub - Arbuzov/home_assistant_delonghi_primadonna: Home assistant integration for the Delonghi coffee machine

Edwin_D · December 31, 2023, 10:28am

Maybe bluetooth reception isn’t that good and it is dropping information because of it? My suggestion would be to spend €10 to €15 to create an ESP bluetooth proxy that you can place nearby:

dietzi · December 31, 2023, 10:35am

The coffee machine is 2m away from the NUC

Edwin_D · December 31, 2023, 10:56am

And how much interference is around it, such as USB3 and other devices? Does it have a separate antenna for bluetooth or is it sharing with wifi?

Edwin_D · December 31, 2023, 11:23am

Seems there are problems with newer linux kernels on NUC, maybe related?

github.com/home-assistant/core

bluetooth integration constant state of initializing / retrying setup (bluetooth is broken with some adapters on newer linux kernels, kernel must be manually patched, workaround is to switch to ESPHome proxies instead)

opened 10:55PM - 02 May 23 UTC

vlape

waiting-for-upstream integration: bluetooth

# Mod Issue Summary - Read First See https://lore.kernel.org/linux-bluetooth/…[email protected]/T/#mb094e06d495879436ce9a8722ad7ad87527ea74b A summary: - Bluetooth initialization is unreliable/broken on newer linux kernels for a large sample of adapters - No fixes are available without patching the kernel and it will likely be a LONG time before debian updates the kernel, if you want to manually compile and patch your kernel, see https://lore.kernel.org/linux-bluetooth/CABBYNZ+5RMqNVMyYKi+gOVaV+K6k8Z-C37KnfGa=qRUORc3dWg@mail.gmail.com/ https://github.com/home-assistant/operating-system/pull/2714 - Newer Home Assistant OS has some patches that solves the problem for some adapters so be sure you have the latest HAOS: https://github.com/home-assistant/operating-system/issues/2485 https://github.com/home-assistant/operating-system/issues/2535 - The recommended workaround if you can't run HAOS or patch the kernel manually is to use an ESPHome proxy instead https://esphome.github.io/bluetooth-proxies/ --- ### The problem Bluetooth integration in perpetual state of initializing / retrying setup. Deleting integration, restarting HA and configuring after auto discovered, several times, does not resolve. ### What version of Home Assistant Core has the issue? core-2023.4.6 ### 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 [home-assistant_bluetooth_2023-05-02T22-28-03.303Z.log](https://github.com/home-assistant/core/files/11378180/home-assistant_bluetooth_2023-05-02T22-28-03.303Z.log) ### Example YAML snippet _No response_ ### Anything in the logs that might be useful for us? ```txt Retrying setup: hci0 (XXXXX): Failed to start Bluetooth: [org.bluez.Error.InProgress] Operation already in progress Logger: bluetooth_auto_recovery.recover Source: components/bluetooth/util.py:78 First occurred: 5:36:41 PM (28 occurrences) Last logged: 5:52:42 PM Bluetooth adapter hci0 [XXXXXXXX] could not be reset due to timeout Logger: homeassistant.config_entries Source: config_entries.py:1242 First occurred: 5:44:58 PM (4 occurrences) Last logged: 5:51:51 PM Config entry 'XXXXX' for bluetooth integration not ready yet: hci0 (XXXXX): Failed to start Bluetooth: [org.bluez.Error.InProgress] Operation already in progress; Retrying in background ``` ### Additional information Home Assistant Yellow ## System Information version | core-2023.4.6 -- | -- installation_type | Home Assistant OS dev | false hassio | true docker | true user | root virtualenv | false python_version | 3.10.10 os_name | Linux os_version | 6.1.21-v8 arch | aarch64 timezone | America/Chicago config_dir | /config <details><summary>Home Assistant Community Store</summary> GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4929 Installed Version | 1.32.1 Stage | running Available Repositories | 1278 Downloaded Repositories | 10 </details> <details><summary>Home Assistant Cloud</summary> logged_in | true -- | -- subscription_expiration | May 3, 2023 at 7:00 PM relayer_connected | true relayer_region | us-east-1 remote_enabled | true remote_connected | true alexa_enabled | false google_enabled | false remote_server | us-east-1-7.ui.nabu.casa can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok </details> <details><summary>Home Assistant Supervisor</summary> host_os | Home Assistant OS 10.1 -- | -- update_channel | stable supervisor_version | supervisor-2023.04.1 agent_version | 1.5.1 docker_version | 23.0.3 disk_total | 234.0 GB disk_used | 9.6 GB healthy | true supported | true board | yellow supervisor_api | ok version_api | ok installed_addons | Mosquitto broker (6.2.1), Studio Code Server (5.5.7), Terminal & SSH (9.7.0), Network UPS Tools (0.11.2) </details> <details><summary>Dashboards</summary> dashboards | 3 -- | -- resources | 6 views | 6 mode | storage </details> <details><summary>Recorder</summary> oldest_recorder_run | April 24, 2023 at 3:54 AM -- | -- current_recorder_run | May 2, 2023 at 5:36 PM estimated_db_size | 652.32 MiB database_engine | sqlite database_version | 3.38.5 </details>

dietzi · December 31, 2023, 11:41am

I dont know if it is a shared antenna. Other USB devices not present. All other Bluetooth Integrations work fine. Only the delonghi integration makes the problem.

dietzi · December 31, 2023, 11:41am

I dont think its related. All other thigns work fine with bluetooth

dietzi · December 31, 2023, 5:03pm

I’ve tested with a raspberry and it’s the same behavior. The data is split. So I think I have to change somwthing on HA. But what to change?

Edwin_D · January 1, 2024, 10:45am

Then it could either be the delonghi itself close to interference or shielding (I don’t think a phone is a good reference because I think it usually has a way better antenna, and the rpi’s is not very good), or the delonghi integration builder needs to implement an entirely different api. This does not look like what you’d expect from the delonghi, not even split.

Another thing: are you absolutely sure you are talking to the right device? Using a ble scanner can be tricky, maybe you looked for the closest thing and found your smartwatch on the hand holding the scanner instead?

dietzi · January 1, 2024, 10:51am

I’m sure talking the right device. I can turn on the machine and cook coffee from HA. Maybe I have to sniff the data from my mobile phone to see wheter the data is split or not.

Edwin_D · January 1, 2024, 10:52am

It could be a different api where each command has a different data length.