eq3btsmart - Connection issues since HA 2025.7+

[bm867002]

The problem

I am using the eq3btsmart for more than one year now (since HA release 2024.5) without bigger issues. I am controlling 15 TRVs via ESPHome BT proxy (in total 6 ESP32 with esp-idf platform).

Since release 2025.7 I am getting regular disconnects. After (latest) 3-4 hours the first TRV devices are disconnected, after 6-8 more than 50% are disconnected and within 24 hours nearly all are gone.

Rebooting HA will bring all devices back again until they are disconnected again after certain time.

This behavior can be reproduced with HA 2025.7+. It is not related to alternative ESPHome versions. (I have checked: Using ESPHome 2025.6.3 with recent HA 2025.6.3 works without issues. ESPHome 2025.6.2 does not work with HA 2025.7+.)

I noted that with HA 2025.7 the eq3btmsart integration has seen bigger changes (like moving to version 2.1.0) - obviously this could be related to the issues I am observing.

What version of Home Assistant Core has the issue?

core-2025.7.0 and core-2025.7.1

What was the last working version of Home Assistant Core?

core-2025.6.3

What type of installation are you running?

Home Assistant Container

Integration causing the issue

eq3btsmart

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

The following errors are related to eq3btsmart integration:
[MAC] eQ-3 device disconnected
[MAC] Error updating eQ-3 device: Already awaiting a status command response
[MAC] Error updating eQ-3 device: Timeout during write
[MAC] Failed setting HVAC mode

Additional information

No response

[home-assistant]

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

Code owner commands

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

---

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

[EuleMitKeule]

I'm on vacation until the ~20th, so not sure when exactly I'll have time to look at this. I do have some changes regarding implementing a Coordinator in the pipeline though, which might help with this.

[WNTLtd]

I’m getting a similar issue, where I used to have 9x EQ3's quite happily working, and being discovered.
Since updating to 25.7 of both HASS core and ESPHome, they are no longer seen by HASS.
I’ve tried going back to ESPHome v25.6.3 but to no avail.
I can see them in the Advertisement monitor, (apart from the one I’ve screwed up by trying to pair it again!) just not coming up as devices with entities anymore.

[EuleMitKeule]

I can now confirm that something seems to be broken. I can occasionally connect, but most of the time after providing bleak with the BLEDevice discovered by HA I get BleakError: Error 14 while connecting: Unlikely error.

[EuleMitKeule]

Same thing happens when using bluetooth.async_get_scanner instead of bluetooth.async_ble_device_from_address and when providing pair=True when initializing the BleakClient. Not sure what else to try.

[bm867002]

Thanks for looking at the issue!

I went back to Home Assistant 2025.6.3 and it worked for days without any problems. Today I switched to Home Assistant 2025.7.2 again, but I replaced the eq3btsmart core integration with the one of 2025.6.3.

Still getting timeout errors and disconnects. Could be a more global Home Assistant issue?

[bdraco]

I can now confirm that something seems to be broken. I can occasionally connect, but most of the time after providing bleak with the BLEDevice discovered by HA I get BleakError: Error 14 while connecting: Unlikely error.

Usually that means it disconnected in the middle of an operation. It might be a change in bleak itself. I don't think proxies can throw that error, only local adapters.

[EuleMitKeule]

I don't think proxies can throw that error, only local adapters

But this happens to me in a devcontainer that doesn't have access to a bluetooth adapter except for a single bluetooth proxy.
The log shows only a single connection path to the device, and that is using the proxy.

[bdraco]

Looks like it does exist aioesphomeapi/core.py: 14: "Unlikely error",. Sadly I've never seen it before on a proxy only local

[bdraco]

https://github.com/espressif/esp-idf/blob/bfe5caf58f742fd35c023335f475114a5b88761e/components/bt/host/bluedroid/api/include/api/esp_gatt_defs.h#L291

[bdraco]

Do you see anything else logged on the ESP when it happens?

[bdraco]

It looks like that error code is a deep internal error in the bluedroid ble stack on the device itself. Invalid internal state

[WNTLtd]

I'm also having issues with EQ3's not showing up as I said. AND, I'm also running HASS on Bluedroid hardware.
Is there any logs I can share that may help - let me know, and I'll see what I can do.....

[WNTLtd]

Hello guys - any update on this issue yet - anything I can do to help?