Gardena Water Computer constantly loosing connection via Bluetooth

MrFreezeman commented 4 months ago

The problem

I have installed the Water Computer from Gardena and successfully connected it to my HA running on Intel NUC 7 with the internal Bluetooth module. Unfortunately, ever since the device looses connection constantly every few minutes. Hence, automations do not work that are set a a fixed time as coincidentally the device is not connected at that moment. What can we do? The internal Bluetooth device works perfectly with other external devices.

What version of Home Assistant Core has the issue?

2024.7.1

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

Gardena Bluetooth

Link to integration documentation on our website

https://www.home-assistant.io/integrations/gardena_bluetooth

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: homeassistant.components.gardena_bluetooth
Quelle: helpers/update_coordinator.py:344
Integration: Gardena Bluetooth (Dokumentation, Probleme)
Erstmals aufgetreten: 5. Juli 2024 um 21:09:32 (70 Vorkommnisse)
Zuletzt protokolliert: 15:35:02

Error fetching Gardena Bluetooth Data Update Coordinator data: Unable to update data for 98bd0015-0b0e-421a-84e5-ddbf75dc6de4 due to Communcation failed with device: [org.bluez.Error.Failed] Operation failed with ATT error: 0x0e (Unlikely Error)
Error fetching Gardena Bluetooth Data Update Coordinator data: Unable to update data for 98bd0014-0b0e-421a-84e5-ddbf75dc6de4 due to Communcation failed with device: [org.bluez.Error.Failed] Operation failed with ATT error: 0x0e (Unlikely Error)
Error fetching Gardena Bluetooth Data Update Coordinator data: Unable to update data for 98bd2a19-0b0e-421a-84e5-ddbf75dc6de4 due to Communcation failed with device: [org.bluez.Error.Failed] Operation failed with ATT error: 0x0e (Unlikely Error)
Error fetching Gardena Bluetooth Data Update Coordinator data: Unable to update data for 98bd0b12-0b0e-421a-84e5-ddbf75dc6de4 due to Communcation failed with device: [org.bluez.Error.Failed] Operation failed with ATT error: 0x0e (Unlikely Error)
Error fetching Gardena Bluetooth Data Update Coordinator data: Unable to update data for 98bd0011-0b0e-421a-84e5-ddbf75dc6de4 due to Communcation failed with device: [org.bluez.Error.Failed] Operation failed with ATT error: 0x0e (Unlikely Error)

Additional information

No response

home-assistant[bot] commented 4 months ago

Hey there @elupus, mind taking a look at this issue as it has been labeled with an integration (gardena_bluetooth) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `gardena_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 gardena_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)}}

gardena_bluetooth documentation gardena_bluetooth source _{^{(message by IssueLinks)}}

DD05071980 commented 4 months ago

The same problem! After restarting home assistant and restarting the Bluetooth adapter it works again. But the problem comes back!

elupus commented 4 months ago

Likely a bluez problem, possible a driver issue with the adapter in linux. Not much we can do about that. In general we have more control over esp32.

Secondly old firmwares of the water computer are broken. Too old and it cant even be upgraded.

MrFreezeman commented 4 months ago

My firmware is 1.7.23.29. Pretty up-to-date I'd say. With that integration status it's pretty much useless then.

elupus commented 4 months ago

Run a esp32 bluetooth gateway....

tfischer4765 commented 4 months ago

I am experiencing the same behaviour and I do have two ESPhome bt proxies that should theoreticallly be in range, so the bluez issue should not affect me. The way I understand it, if the built-in adapter loses connecton for whatever reason, but one of the proxies is in range, that should take over. This, however, does not seem to happen.

elupus commented 4 months ago

I am experiencing the same behaviour and I do have two ESPhome bt proxies that should theoreticallly be in range, so the bluez issue should not affect me. The way I understand it, if the built-in adapter loses connecton for whatever reason, but one of the proxies is in range, that should take over. This, however, does not seem to happen.

Suggest you try and disable the built in adapter to see of that makes any difference.

MrFreezeman commented 4 months ago

If the built-in bluetooth module does not work reliably, isn't it possible to adjust the automation in a way that if the connection to the water computer wasn't possible to be established, the script waits for a couple of minutes to check again later?

elupus commented 4 months ago

It will check every minute or so

MrFreezeman commented 4 months ago

I don’t think so. The automation stops when there’s no connection. That’s why it doesn’t work. So, I’m wondering if I could implement a logic that waits for a couple of minutes before trying again to connect.

Joakim Plate @.***> schrieb am Sa. 20. Juli 2024 um 16:49:

It will check every minute or so

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/121375#issuecomment-2241173474, or unsubscribe https://github.com/notifications/unsubscribe-auth/AS6M3QCPL7Q3OFXHD7PZUGTZNJ2HZAVCNFSM6AAAAABKOOGFZKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBRGE3TGNBXGQ . You are receiving this because you authored the thread.Message ID: @.***>

elupus commented 4 months ago

The connection to the device will retry multiple times before failing.

MrFreezeman commented 4 months ago

Not long enough I think.

Joakim Plate @.***> schrieb am Sa. 20. Juli 2024 um 17:01:

The connection to the device will retry multiple times before failing.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/121375#issuecomment-2241176242, or unsubscribe https://github.com/notifications/unsubscribe-auth/AS6M3QATT5BED4RIJ6AZTVLZNJ3VBAVCNFSM6AAAAABKOOGFZKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBRGE3TMMRUGI . You are receiving this because you authored the thread.Message ID: @.***>

DrunkenHusky commented 4 months ago

Same issue here with ESPHome and ESP32 as bluetooth proxy. I need to restart ESP32 to bring it back to work again.

elupus commented 4 months ago

Right @DrunkenHusky . So something get messed up on the proxy if restarting it helps solve. I wonder if we can manage to ge debug logs right when it happens.

Im pretty sure its some type of disconnection failure.

DrunkenHusky commented 4 months ago

Let me know what kind of logs you need @elupus and I try to collect them :).

ambiman commented 3 months ago

Also happy to support here. I've the same issues with my two Gardena BT Water Controls (running the up-to-date firmware) once connected via ESP32 BT Proxy and the other via an external USB BT stick. What logs are needed?

NetFett commented 3 months ago

I had the same problem. Also with 2 x esp32 and 4 Gardena valves. I also tried a Shelly Bluetooth proxy. None of it helped. Then I reset the Gardena valves at their location. (Battery out, press button, battery in and wait 10 seconds until the lights all flash once. Then release the button). I also deleted the Bluetooth pairings from my mobile phone beforehand. Now it has been working for over 30 hours without any logout of the devices from Home Assistant.

elupus commented 3 months ago

My suspicious have always been that the devices have a limited number of paired devices and if your phone grabs one of them it can end inaccessible.

Pa. For example, my phone with official app cant access my computers once ive used them with HA.

DrunkenHusky commented 3 months ago

I had the same problem. Also with 2 x esp32 and 4 Gardena valves. I also tried a Shelly Bluetooth proxy. None of it helped. Then I reset the Gardena valves at their location. (Battery out, press button, battery in and wait 10 seconds until the lights all flash once. Then release the button). I also deleted the Bluetooth pairings from my mobile phone beforehand. Now it has been working for over 30 hours without any logout of the devices from Home Assistant.

I can‘t confirm that. I sit 1000 km away from home - only ESP32 Proxy will connect to the Gardena Devices and the Issue still exists. Worked also for me some hours in the beginnung but it will be worse as longer it runs.

NetFett commented 3 months ago

In my case it was actually the resetting of the valves. After that, everything was fine.

I can‘t confirm that. I sit 1000 km away from home - only ESP32 Proxy will connect to the Gardena Devices and the Issue still exists. Worked also for me some hours in the beginnung but it will be worse as longer it runs.

issue-triage-workflows[bot] commented 1 week ago

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.

DrunkenHusky commented 1 week ago

Hi all, the issue for me still exists. All Homeassistant Updates are installed. Does someone has a solution?

home-assistant / core