Just a Request

[wes1993]

There is a way to access the Smart Lock with Phone after i have configured and turned on the ESP32?
I'll try to explain better:
I have confugred the ESP and everything works very well but now i can't use the app from my mobile (For example if i can't access my HA instance) if the ESP32 is powerd on, my question is can we "open" the connection to smart lock only when we want to update sensor or open/close the door?

Thanks a lot
Stefano

[henfri]

Hello,

this is possible, but has drawbacks. The reaction time is ~10-15s then.

lock_action:
  - eqiva_key_ble.connect:
  - eqiva_key_ble.lock:
  - delay: 15s
  - eqiva_key_ble.disconnect:

(and similar for the other actions)

to get a status every four minutes:

Call Status every 4 minutes because lock seems to disconnect after 5 minutes of inactivity
need to watch battery consumption

time:
    - platform: sntp
      timezone: Europe/Berlin
      servers:
       - 0.pool.ntp.org
       - 1.pool.ntp.org
       - 2.pool.ntp.org
      on_time:
        # Every 4 minutes get Status, to ensure quick reaction
        - cron: '00 /4 21-23 * * *'
          then:
            - eqiva_key_ble.status:
            - eqiva_key_ble.disconnect:

[wes1993]

@henfri,
Thanks a lot :-D

[dlbogdan]

Hi,

So I tried doing this:

lock_action:
    - eqiva_key_ble.connect:
        mac_address: !lambda 'return id(mac_address).state;' 
        user_id: !lambda 'return id(user_id).state;'
        user_key: !lambda 'return id(user_key).state;'
    - eqiva_key_ble.lock:
    - eqiva_key_ble.disconnect:      
  unlock_action:
    - eqiva_key_ble.connect:
        mac_address: !lambda 'return id(mac_address).state;' 
        user_id: !lambda 'return id(user_id).state;'
        user_key: !lambda 'return id(user_key).state;'
    - eqiva_key_ble.unlock:
    - eqiva_key_ble.disconnect:  
  open_action:
    - eqiva_key_ble.connect:
        mac_address: !lambda 'return id(mac_address).state;' 
        user_id: !lambda 'return id(user_id).state;'
        user_key: !lambda 'return id(user_key).state;'    
    - eqiva_key_ble.open:
    - eqiva_key_ble.disconnect:

But it only works the first command after esp booting, then disconnects and somehow it cannot connect again, so any subsequent commands are not working until restarting the esp.

Help, pls.
Don't want any delay, other than the natural delay of connecting. I just want the esp to connect, make the action and then immediately disconnect.
Also, status polling every minute or so should suffice (even 2 or 4 minutes should be fine).

Thanks!

[digaus]

Hi,

So I tried doing this:

lock_action:
    - eqiva_key_ble.connect:
        mac_address: !lambda 'return id(mac_address).state;' 
        user_id: !lambda 'return id(user_id).state;'
        user_key: !lambda 'return id(user_key).state;'
    - eqiva_key_ble.lock:
    - eqiva_key_ble.disconnect:      
  unlock_action:
    - eqiva_key_ble.connect:
        mac_address: !lambda 'return id(mac_address).state;' 
        user_id: !lambda 'return id(user_id).state;'
        user_key: !lambda 'return id(user_key).state;'
    - eqiva_key_ble.unlock:
    - eqiva_key_ble.disconnect:  
  open_action:
    - eqiva_key_ble.connect:
        mac_address: !lambda 'return id(mac_address).state;' 
        user_id: !lambda 'return id(user_id).state;'
        user_key: !lambda 'return id(user_key).state;'    
    - eqiva_key_ble.open:
    - eqiva_key_ble.disconnect:

But it only works the first command after esp booting, then disconnects and somehow it cannot connect again, so any subsequent commands are not working until restarting the esp.

Help, pls. Don't want any delay, other than the natural delay of connecting. I just want the esp to connect, make the action and then immediately disconnect. Also, status polling every minute or so should suffice (even 2 or 4 minutes should be fine).

Thanks!

You need to add a delay before disconnecting.

Otherwise the command might not be send because it's already disconnected. See the comment above.

[dlbogdan]

Oh. I might have a look inside the code then.
In my opinion, the lock/unlock/open/get status action / command should be "blocking", at least for the disconnect function or even globally for any BLE related task.

[dlbogdan]

I've had a look at the code, and decided to give it another try with the yaml file :) It's not that it's something wrong with your code @digaus it's just that it's something wrong with my C++ skills. I can code all day in C, and ye old school C++ from my high school years (90s), but new stuff, never got around in learning that.

So, here's how my lock: part of the yaml file looks like now:

lock:
  - platform: template
    name: "Lock 1"
    lambda: |-
      if (id(lock_status).state == "LOCKED") {
        return LOCK_STATE_LOCKED;
      } else if (id(lock_status).state == "UNLOCKED" || id(lock_status).state == "OPENED") {
        return LOCK_STATE_UNLOCKED;
      } else if(id(lock_status).state == "MOVING") {
        return {};
      } else if (id(lock_status).state == "UNKNOWN") {
        return LOCK_STATE_JAMMED;
      } 
      return LOCK_STATE_LOCKED;
    lock_action:
      - eqiva_key_ble.connect:
          mac_address: !lambda 'return id(mac_address).state;' 
          user_id: !lambda 'return id(user_id).state;'
          user_key: !lambda 'return id(user_key).state;'
      - delay: 5s
      - eqiva_key_ble.lock:
      - delay: 7s
      - eqiva_key_ble.status:
      - delay: 5s
      - eqiva_key_ble.disconnect:      
    unlock_action:
      - eqiva_key_ble.connect:
          mac_address: !lambda 'return id(mac_address).state;' 
          user_id: !lambda 'return id(user_id).state;'
          user_key: !lambda 'return id(user_key).state;'
      - delay: 5s
      - eqiva_key_ble.unlock:
      - delay: 7s
      - eqiva_key_ble.status:
      - delay: 5s
      - eqiva_key_ble.disconnect:  
    open_action:
      - eqiva_key_ble.connect:
          mac_address: !lambda 'return id(mac_address).state;' 
          user_id: !lambda 'return id(user_id).state;'
          user_key: !lambda 'return id(user_key).state;'    
      - delay: 5s
      - eqiva_key_ble.open:
      - delay: 7s
      - eqiva_key_ble.status:
      - delay: 5s
      - eqiva_key_ble.disconnect:

For now, it seems to be working reliably enough, albeit with probably too much delay, but better have the action later than just skipped.

I'll probably have another go sometimes in the future at the code, but I'd need to read on about esphome components to understand the framework, and then try to understand the keyble component here.. Slim chance to have enough time for that with my focus split between the kids, household stuff and job.

Anyway, Thank you @digaus for your wonderful work.