Help request: Disconnect BLE when API client not connected

[user45876]

Dear digaus,

thank you so much for this. I was using a Zero 2 with several keyble for years and while it is great, this is looking to be more reliable and easier in the end. This has so much less moving parts than a zero with Node on it ;)

However, I am having two questiong and want to ask for help:

• it seems to stay connected forever despite me removing the 4 minute timer from the example. While this makes it instand, could you say what would need to be set to have it disconnect after some time?
• more importantly, you are having a condition, that it must be connected to wifi to start BLE scanning. How would I need to set it up to have it only scan when an API connection is established to HA? There is a condition api.connected (https://esphome.io/components/api) - but could you maybe put this into the example?

Thank you so much for your efforts, very much appreciated! Corwin

[user45876]

After reading and trying to think in this bedlam I came up with this. Should this work? Is it enough or too much? Desired behaviour is that it disconnects from the lock when the API is disconnected for whatever reason so the app can be used. (editing around...)

api:
  encryption:
    key: "..."

  on_client_disconnected:
    - while:
        condition:
          - not: api.connected
        then:
          - esp32_ble_tracker.stop_scan:
          - eqiva_key_ble.disconnect:

However, this does not seem to be working as intended. When the API is disconnected (e.g. temporarily shutting the HA switchport), the lock does not become available in the app.

[dlbogdan]

Yes, this is quite important in order to have redundancy of opening the door. example. HA crashes or wifi or whatever, you should be able to use the Eqiva App in your phone to open the door. If the ESP32 is constantly connected to the lock, you can't.

Help!