Gardene Bluetooth Intgration - Setup doesn't work

verhoevendanny commented 2 months ago

The problem

The Integration find itself the "Water Control Bluetooth" equipment. But it always ends with an error : No devices or entities found

What version of Home Assistant Core has the issue?

core-2024.6.0

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

home-assistant_gardena_bluetooth_2024-06-06T10-04-28.477Z.log home-assistant_gardena_bluetooth_2024-06-06T10-04-28.477Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: homeassistant.config_entries
Bron: config_entries.py:594
Eerst voorgekomen: 11:57:01 (1 gebeurtenissen)
Laatst gelogd: 11:57:01

Error setting up entry Gardena Water Computer for gardena_bluetooth
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/gardena_bluetooth/__init__.py", line 55, in async_setup_entry
    sw_version = await client.read_char(DeviceInformation.firmware_version, None)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/gardena_bluetooth/client.py", line 180, in read_char
    return char.decode(await self.read_char_raw(char.uuid))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/gardena_bluetooth/parse.py", line 82, in decode
    return data.decode("ASCII")
           ^^^^^^^^^^^^^^^^^^^^
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 3: ordinal not in range(128)

Additional information

No response

home-assistant[bot] commented 2 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)}}

elupus commented 2 months ago

Can you tell me what equipment this is? Link to product page? Also what firmware version does the official application report?

verhoevendanny commented 2 months ago

Hello,

The product is : https://www.gardena.com/nl/producten/bewateren/besproeiingscomputers/water-control-bluetooth/970481101.html?gad_source=1&gclid=CjwKCAjwvIWzBhAlEiwAHHWgvYVeD3RE6Gjl1GY_T9RGzOPap0-4bNhuaxeMRB6jZZyE4u1cG_nE3BoCZUAQAvD_BwE

Latest firmware available : 1.7.23.29

greetz Danny

Op do 6 jun 2024 om 12:26 schreef Joakim Plate @.***>:

Can you tell me what equipment this is? Link to product page? Also what firmware version does the official application report?

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

-- Danny Verhoeven Berouw 143 b301 9000 Gent (0471) 18 39 72

elupus commented 2 months ago

Okey. I think this is related to some changes in esp gateway's.

elupus commented 2 months ago

@verhoevendanny How do you connect to the device. Are you using an esp ble gateway?

verhoevendanny commented 2 months ago

Yes, via esp32-bluetooth-proxy-7edb7c

Greetz Danny

Op do 6 jun 2024 16:19 schreef Joakim Plate @.***>:

@verhoevendanny https://github.com/verhoevendanny How do you connect to the device. Are you using an esp ble gateway?

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/118956#issuecomment-2152664081, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIXSC3VYJCBCIHN3SIY5X4DZGBVYRAVCNFSM6AAAAABI4MVW2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJSGY3DIMBYGE . You are receiving this because you were mentioned.Message ID: @.***>

elupus commented 2 months ago

Can you try an restart the gateway and see if the device is accepted?

elupus commented 2 months ago

Do you have more than one gateway btw?

verhoevendanny commented 2 months ago

Hello,

No, their is a bluetooth connection on the mini PC where HA is running on.

But i tested the link with your add-on in a room far from the PC also.

Greetz

Op do 6 jun 2024 16:36 schreef Joakim Plate @.***>:

Do you have more than one gateway btw?

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/118956#issuecomment-2152701156, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIXSC3RRKLHGGYOXQKBQVATZGBXWDAVCNFSM6AAAAABI4MVW2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJSG4YDCMJVGY . You are receiving this because you were mentioned.Message ID: @.***>

verhoevendanny commented 2 months ago

Later this evening when i'm home

Op do 6 jun 2024 16:33 schreef Joakim Plate @.***>:

Can you try an restart the gateway and see if the device is accepted?

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/118956#issuecomment-2152695167, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIXSC3S3FBOEHYMTQYOLNFLZGBXLXAVCNFSM6AAAAABI4MVW2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJSGY4TKMJWG4 . You are receiving this because you were mentioned.Message ID: @.***>

frontside76 commented 2 months ago

Same problem here. Have 3 M5Stack Atom bluetooth proxys for 3 gardena valves. Get same error on 1 Proxy, so 1 valve is down. It occured after last HA Update and restart, i did on Sunday. Today i did the 2024.06 Update, but no change. Firmware at Gardena Valve is the newest. ESP Home and proxys have newest updates.

elupus commented 2 months ago

Same problem here. Have 3 M5Stack Atom bluetooth proxys for 3 gardena valves. Get same error on 1 Proxy, so 1 valve is down. It occured after last HA Update and restart, i did on Sunday. Today i did the 2024.06 Update, but no change. Firmware at Gardena Valve is the newest. ESP Home and proxys have newest updates.

Can you restart all of your proxies and see if that changes which device it fails to connect to?

frontside76 commented 2 months ago

I have disconnected all 3 Proxys. Then i completely, restarted HA. Then alle 3 valves were offline. Now I have pluged in Proxy 2 and 3 and got the same Error - only for valve 1.

Logger: homeassistant.config_entries Quelle: config_entries.py:594 Erstmals aufgetreten: 18:17:51 (1 Vorkommnisse) Zuletzt protokolliert: 18:17:51

Error setting up entry Gardena Ventil 1 for gardena_bluetooth Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup result = await component.async_setup_entry(hass, self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/gardena_bluetooth/init.py", line 55, in async_setup_entry sw_version = await client.read_char(DeviceInformation.firmware_version, None) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/gardena_bluetooth/client.py", line 180, in read_char return char.decode(await self.read_char_raw(char.uuid)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/gardena_bluetooth/parse.py", line 82, in decode return data.decode("ASCII") ^^^^^^^^^^^^^^^^^^^^ UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 3: ordinal not in range(128)

elupus commented 2 months ago

Can you check if its always same valve or if it depends on the proxy. Disconnect the proxies. Plug one in, check for error. If you get the error disconnect it again. Borrow another proxy and connect it at that location.

frontside76 commented 2 months ago

The last months I had Problems with all 3 valves. Always 1 of them was offline. Then there were same changes in ESP home in May and then it worked. I was on vacation from May 14th til June 2nd and everything worked. I did no changes in this time. After I returned, rhere were some Updates (HA, ESP Home, ESP bluetooth proxy,...). After Update and restart I got this error. Maybe it is a problem with the ESP proxy config? I compare all 3 and send an update here.

frontside76 commented 2 months ago

Update: Config is the same at all 3 proxys. So I took off the battery of valve 1, inserted it again. Then I did a HA restart. Now all 3 valves are working again.

So it is still a problem with the connection, when you restart the whole HA system. I think the valve still thinks there is a Connecticut, but HA tries again and again and doesn't get a handshake.

elupus commented 2 months ago

I wish you would have done as i asked. Its not a a connection issue. It is connected when the error in the log occurs. It is getting invalid data. Im trying to figure out where that data is from.

frontside76 commented 2 months ago

I did what you have asked, sorry I forgot to write. I have disconnected all 3 proxys, then I have connected Proxy1 -> valve 1 offline, valve 2 and 3 online.

Then I have disconnected Proxy1 again and connected Proxy2. -> valve 1 offline, valve 2 and 3 online.

Then I have disconnected Proxy2 again and connected Proxy3. -> valve 1 offline, valve 2 and 3 online.

Everytime the same problem with valve 1. All 3 valves have the same actual firmware. When 1 take out the battery and put it in again, it works.

frontside76 commented 2 months ago

And now I got 2 Errors (I know them, because I get them every day), but the valves still work.

NO.1########: Logger: homeassistant.components.gardena_bluetooth Quelle: helpers/update_coordinator.py:344 Integration: Gardena Bluetooth (Dokumentation, Probleme) Erstmals aufgetreten: 19:34:34 (1 Vorkommnisse) Zuletzt protokolliert: 19:34:34

Error fetching Gardena Bluetooth Data Update Coordinator data: Unable to update data for 98bd0011-0b0e-421a-84e5-ddbf75dc6de4 due to Communcation failed with device: Gardena Bluetooth - B0:D2:78:99:E1:80: Failed to connect after 9 attempt(s): Error ESP_GATT_CONN_FAIL_ESTABLISH while connecting: Connection failed to establish: Interference/range; External Bluetooth adapter w/extension may help; Extension cables reduce USB 3 port interference

NO.2########: Logger: homeassistant.components.gardena_bluetooth Quelle: helpers/update_coordinator.py:318 Integration: Gardena Bluetooth (Dokumentation, Probleme) Erstmals aufgetreten: 19:17:24 (3 Vorkommnisse) Zuletzt protokolliert: 19:36:55

Timeout fetching Gardena Bluetooth Data Update Coordinator data

elupus commented 2 months ago

Thanks! That confirms its something is odd with the state of that specific device. We have by that ruled out the esphome internal device caches.

So, i wonder if we have lingering connections on home assistant restarts that places the devices in some odd state. So if the restart happen right when a device is connected it goes wonky and does not recover.

@verhoevendanny can you confirm that removing the device batteries let it get added in home assistant?

verhoevendanny commented 2 months ago

Hello, It is already in HA but in a wrong state... Setup failed. Removing batteries does not do anything within HA.

Question... Do I have to perform setup first via the app and then HA OR do I have to perform a reset and connect it then to HA?

Danny

Op do 6 jun. 2024 20:36 schreef Joakim Plate @.***>:

Thanks! That confirms its something is odd with the state of that specific device. We have by that ruled out the esphome internal device caches.

So, i wonder if we have lingering connections on home assistant restarts that places the devices in some odd state. So if the restart happen right when a device is connected it goes wonky and does not recover.

@verhoevendanny https://github.com/verhoevendanny can you confirm that removing the device batteries let it get added in home assistant?

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/118956#issuecomment-2153159961, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIXSC3R6M7K7WZ27GWIE3J3ZGCT2HAVCNFSM6AAAAABI4MVW2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJTGE2TSOJWGE . You are receiving this because you were mentioned.Message ID: @.***>

frontside76 commented 2 months ago

You only need the App for firmware update. Better you reset it and integrate it directly in HA.

Question: after you removed the battery and inserted again, did you restart HA (yellow button)?

elupus commented 2 months ago

Those are different errors @frontside76 lets keep this issue for the setup exceptions.

verhoevendanny commented 2 months ago

Is a solution possible? It is still not working!

elupus commented 2 months ago

@verhoevendanny we don't know yet. When 2024.6.2 is out please try again. It should handle the exception you reported. But its not sure if that solve your issue yet.

frontside76 commented 2 months ago

Mine is working since 5 days, when i put out the battery, inserted again and started HA

verhoevendanny commented 2 months ago

Installed 2024.6.2, then reinstalled the integration. Found it but still mentioning No devices or entities found. Nothing in the log. So it is not yet solved.

elupus commented 2 months ago

Well. The exception is solved. Your device is likely in bootloader mode as was reported in another ticket.

Enable debug logging on the integration, reload it and disable debug logging. Then post that file here

verhoevendanny commented 2 months ago

error_log-2.txt

elupus commented 2 months ago

Doesnt look like you reloaded the integration?

verhoevendanny commented 2 months ago

I did now a restart HA, and then debug error_log-3.txt

elupus commented 2 months ago

I think you misunderstood. I dont want you to restart home assistant. I want you to reload just the gardena integration while debug is turned on. That way it reinitialize and i get its startup information in the logs.

verhoevendanny commented 2 months ago

No I did it correct! This morning I reloaded the integration 3 time and this is what comes out in the log: 2024-06-12 08:37:13.770 DEBUG (MainThread) [homeassistant.components.gardena_bluetooth] Finished fetching Gardena Bluetooth Data Update Coordinator data in 0.000 seconds (success: True) 2024-06-12 08:37:18.570 DEBUG (MainThread) [homeassistant.components.gardena_bluetooth] Finished fetching Gardena Bluetooth Data Update Coordinator data in 0.000 seconds (success: True) 2024-06-12 08:37:25.143 DEBUG (MainThread) [homeassistant.components.gardena_bluetooth] Finished fetching Gardena Bluetooth Data Update Coordinator data in 0.000 seconds (success: True)

elupus commented 2 months ago

Ok. I was sure it would log the setup process. Crap, i need to add bluetooth logging to the log settings for that integration

verhoevendanny commented 2 months ago

Hello, this morning nu version, tested it but same result. Debugging is now available

Op wo 12 jun. 2024 09:18 schreef Joakim Plate @.***>:

Ok. I was sure it would log the setup process. Crap, i need to add bluetooth logging to the log settings for that integration

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/118956#issuecomment-2162285764, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIXSC3RDLFD76VRZ7PG7YU3ZG7Y3RAVCNFSM6AAAAABI4MVW2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRSGI4DKNZWGQ . You are receiving this because you were mentioned.Message ID: @.***>

2024-06-16 08:12:56.597 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration myenergy which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2024-06-16 08:12:56.602 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration kamstrup_403 which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2024-06-16 08:12:56.606 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration oralb_ble which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2024-06-16 08:12:56.610 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration bibliotheek_be which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2024-06-16 08:12:56.615 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2024-06-16 08:12:56.619 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration tplink_deco which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2024-06-16 08:12:56.622 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration garmin_connect which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2024-06-16 08:12:56.626 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration average which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2024-06-16 08:12:56.630 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration tahoma which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2024-06-16 08:12:56.632 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration comfoconnect which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2024-06-16 08:12:56.635 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration nodered which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2024-06-16 08:12:56.638 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration afvalbeheer which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2024-06-16 08:13:06.762 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/hacs/frontend.py, line 68: hass.components.frontend.async_register_built_in_panel(, please create a bug report at https://github.com/hacs/integration/issues 2024-06-16 08:13:11.621 WARNING (MainThread) [custom_components.comfoconnect] Alarm received for Node 1:

77: The filters of the Ventilation Unit must be replaced now

2024-06-16 08:13:12.517 WARNING (ImportExecutor_0) [homeassistant.helpers.typing] HomeAssistantType was used from nodered, this is a deprecated alias which will be removed in HA Core 2025.5. Use homeassistant.core.HomeAssistant instead, please report it to the author of the 'nodered' custom integration 2024-06-16 08:13:12.536 WARNING (ImportExecutor_0) [homeassistant.helpers.typing] HomeAssistantType was used from nodered, this is a deprecated alias which will be removed in HA Core 2025.5. Use homeassistant.core.HomeAssistant instead, please report it to the author of the 'nodered' custom integration 2024-06-16 08:13:25.026 WARNING (zeroconf-ServiceBrowser-_googlecast._tcp-124) [pychromecast.dial] Failed to determine cast type for host (HTTP Error 403: Forbidden) (services:{MDNSServiceInfo(name='decoder-b19af40a40e8051703dc1d3c463a84b1._googlecast._tcp.local.')}) 2024-06-16 08:13:27.459 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up tplink_deco platform for sensor Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 366, in _async_setup_platform await asyncio.shield(awaitable) File "/config/custom_components/tplink_deco/sensor.py", line 87, in async_setup_entry add_sensors_for_deco(None) # Total ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/tplink_deco/sensor.py", line 42, in add_sensors_for_deco f"{coordinator_decos.data.master_deco.mac}_total" ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: 'NoneType' object has no attribute 'mac' 2024-06-16 08:13:27.573 ERROR (MainThread) [homeassistant.components.device_tracker] Platform tplink_deco does not generate unique IDs. ID 70-4F-57-8A-2C-28 already exists - ignoring device_tracker.salon_deco 2024-06-16 08:13:31.287 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for esp @ 192.168.129.138: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.129.138', port=6053))]: [Errno 113] Connect call failed ('192.168.129.138', 6053) (SocketAPIError) 2024-06-16 08:13:31.475 ERROR (MainThread) [custom_components.average.sensor] Unable to find an entity "sensor.zon_temperature" 2024-06-16 08:13:39.095 WARNING (MainThread) [zigpy.application] Zigbee channel 15 utilization is 96.64%! 2024-06-16 08:13:39.096 WARNING (MainThread) [zigpy.application] If you are having problems joining new devices, are missing sensor updates, or have issues keeping devices joined, ensure your coordinator is away from interference sources such as USB 3.0 devices, SSDs, WiFi routers, etc. 2024-06-16 08:13:39.342 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.helpers.event. This is deprecated and will stop working in Home Assistant 2024.11, it should be updated to import functions used from event directly at custom_components/hacs/base.py, line 630: self.hass.helpers.event.async_track_time_interval(, please create a bug report at https://github.com/hacs/integration/issues 2024-06-16 08:13:50.792 WARNING (Recorder) [homeassistant.components.sensor.recorder] The unit of sensor.gent_precipitation (mm/h) cannot be converted to the unit of previously compiled statistics (mm). Generation of long term statistics will be suppressed unless the unit changes back to mm or a compatible unit. Go to https://my.home-assistant.io/redirect/developer_statistics to fix this 2024-06-16 08:14:42.954 DEBUG (MainThread) [gardena_bluetooth.client] Connecting to 30:AF:7E:D4:26:D1 2024-06-16 08:14:42.955 DEBUG (MainThread) [bleak_esphome.connect] esp32-bluetooth-proxy-7edb7c [78:21:84:7E:DB:7C]: Checking can connect, available=True, ble_connections_free=3 result=True 2024-06-16 08:14:42.974 DEBUG (MainThread) [bleak_esphome.backend.device] esp32-bluetooth-proxy-7edb7c [78:21:84:7E:DB:7C]: BLE connection limits: used=1 free=2 limit=3 2024-06-16 08:14:52.386 DEBUG (MainThread) [bleak_esphome.backend.client] esp32-bluetooth-proxy-7edb7c [78:21:84:7E:DB:7C]: Timer - 30:AF:7E:D4:26:D1: Connection state changed to connected=True mtu=247 error=0 2024-06-16 08:14:52.386 DEBUG (MainThread) [bleak_esphome.backend.client] esp32-bluetooth-proxy-7edb7c [78:21:84:7E:DB:7C]: Timer - 30:AF:7E:D4:26:D1: connected, registering for disconnected callbacks 2024-06-16 08:14:52.388 DEBUG (MainThread) [bleak_esphome.backend.device] esp32-bluetooth-proxy-7edb7c [78:21:84:7E:DB:7C]: BLE connection limits: used=1 free=2 limit=3 2024-06-16 08:14:52.390 DEBUG (MainThread) [bleak_esphome.backend.client] esp32-bluetooth-proxy-7edb7c [78:21:84:7E:DB:7C]: Timer - 30:AF:7E:D4:26:D1: Cached services hit 2024-06-16 08:14:52.391 DEBUG (MainThread) [gardena_bluetooth.client] Connected to 30:AF:7E:D4:26:D1 2024-06-16 08:14:52.676 DEBUG (MainThread) [gardena_bluetooth.client] Characteristics: {'00002a01-0000-1000-8000-00805f9b34fb', '00002a29-0000-1000-8000-00805f9b34fb', '00002a25-0000-1000-8000-00805f9b34fb', '00002a2a-0000-1000-8000-00805f9b34fb', '00002a50-0000-1000-8000-00805f9b34fb', '00002aa6-0000-1000-8000-00805f9b34fb', '00002a23-0000-1000-8000-00805f9b34fb', '00002ac9-0000-1000-8000-00805f9b34fb', '00002a27-0000-1000-8000-00805f9b34fb', '00002a24-0000-1000-8000-00805f9b34fb', '00002a04-0000-1000-8000-00805f9b34fb', 'f000ffc2-0451-4000-b000-000000000000', 'f000ffc1-0451-4000-b000-000000000000', '00002a28-0000-1000-8000-00805f9b34fb', '00002a00-0000-1000-8000-00805f9b34fb', 'f000ffc5-0451-4000-b000-000000000000', '00002a05-0000-1000-8000-00805f9b34fb', '00002a26-0000-1000-8000-00805f9b34fb'} 2024-06-16 08:14:52.677 DEBUG (MainThread) [gardena_bluetooth.client] No timestamp defined for device 2024-06-16 08:14:52.684 DEBUG (MainThread) [homeassistant.components.gardena_bluetooth] Finished fetching Gardena Bluetooth Data Update Coordinator data in 0.000 seconds (success: True)

elupus commented 2 months ago

This device is as expected not listing the characteristics expected. Looks to be in boot mode.

Does your bluetooth proxy ha have service cache enabled "cache_services: true"?

verhoevendanny commented 2 months ago

no idea, where do i have to check that?

I can only find: substitutions: name: esp32-bluetooth-proxy-7edb7c friendly_name: Bluetooth Proxy 7edb7c packages: esphome.bluetooth-proxy: @.* esphome: name: ${name} name_add_mac_suffix: false friendly_name: ${friendly_name} api: encryption: key: **

wifi: ssid: !secret wifi_ssid password: !secret wifi_password

web_server:

Op zo 16 jun 2024 om 10:30 schreef Joakim Plate @.***>:

This device is as expected not listing the characteristics expected. Looks to be in boot mode.

Does your bluetooth proxy ha have service cache enabled "cache_services: true"?

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/118956#issuecomment-2171235088, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIXSC3TMQ7KJCNMOJ2NFINLZHVEJLAVCNFSM6AAAAABI4MVW2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZRGIZTKMBYHA . You are receiving this because you were mentioned.Message ID: @.***>

-- Danny Verhoeven Berouw 143 b301 9000 Gent (0471) 18 39 72

elupus commented 2 months ago

Ok. Then it should not be active. Could you try the factory reset of the device. Take out batteries, hold down button, insert batteries, wait around 3 seconds before releasing.

For some reason it seem to not start the main firmware

verhoevendanny commented 2 months ago

Sorry, the same result.

Op zo 16 jun. 2024 11:09 schreef Joakim Plate @.***>:

Ok. Then it should not be active. Could you try the factory reset of the device. Take out batteries, hold down button, insert batteries, wait around 3 seconds before releasing.

For some reason it seem to not start the main firmware

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/118956#issuecomment-2171275094, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIXSC3S67NSVIC2HFQVWMH3ZHVI4BAVCNFSM6AAAAABI4MVW2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZRGI3TKMBZGQ . You are receiving this because you were mentioned.Message ID: @.***>

MrFreezeman commented 1 month ago

Nothing new on this issue? I have the same constant disconnects with the Gardena Water Computer but without esp. normal Intel NUC Bluetooth device.

elupus commented 1 month ago

The built-in Bluetooth is generally worse. But this issue is about not being able to setup the device. So sounds unrelated. Look in the other issue.

verhoevendanny commented 1 week ago

Today it worked suddenly!

home-assistant / core