Equiva TRV not working with esphome bluetooth proxy

[ChristianRomberg]

The problem

On a blank HA installation, the eq3btsmart integration doesn't appear to be finding TRVs that can be connected to via an ESPhome bt proxy.
Using the onboard bluetooth of my PC works, but on my real installation the PC is too far away and I would like to use ESPhome bluetooth proxies.

From the log file, you can see that the packets are received and relayed to home assistant, and even if I try to manually add a TRV by the exact mac address, it says that the device can't be found and nothing related appears in the debug log.

What version of Home Assistant Core has the issue?

core-2025.1.2

What was the last working version of Home Assistant Core?

No response

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

home-assistant_eq3btsmart_2025-01-14T12-35-43.928Z.log

Example YAML snippet

Anything in the logs that might be useful for us?

2025-01-14 13:35:31.868 DEBUG (MainThread) [aioesphomeapi.connection] chris_piepser @ 192.168.178.202: Got message of type BluetoothLERawAdvertisementsResponse: advertisements {
  address: 112241428567
  rssi: -71
  data: "\002\001\005\021\007Fp\267[\377\246J\023\220\220OeBQ\023>\n\tCC-RT-BLE\014\377\000\000\000\000\000\000\000\000\000\000\000"
}

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)}}

[ChristianRomberg]

The TRV has firmware version 120 (which should work without explicitly pairing) and the ESP32 was set up with the bluetooth_proxy as instructed in the manual.

What's weird is that it was working until a few days ago, when all the sudden all of the TRVs became unavailable. There was no update at the time, just some playing around with a totally unrelated vacuum robot integration that doesn't even use bluetooth at all