search

kvj / hass_nuki_ng

Better support for Nuki devices in the Home Assistant
MIT License
185 stars 36 forks source link

Last unlock user Bug and feature reqest #117

Open milansim opened 2 years ago

milansim commented 2 years ago

I use Nuki lock 3 + bridge + web Api integration When opening a lock by pressing a button on a lock then "Last unlock user" is empty

While solving this bug I propose a different kind of features instead, exposing the following as entity or attribute for use in automation:

  1. Lock state
  2. Trigger device
  3. trigger user

In my case I would like to do some action when Lock goes to "locked" state, triggered by "keypad" or "Manually (Button) - Lock n go". Fairly reasonable I think as such triggers would assume "nobody at home" if standard operation is unlatch only, and then I can switch off climate, TV, lighting..... Trigger user might be usefull for others, my use case is renting apartment so users change all the time

I know you are working on ESP32 BLE hub which will solve it better, unfortunatelyt existing project keeps my ESP32 in restart loop (https://github.com/technyon/nuki_hub)

Thanks up front for solving my problem :-)

milansim commented 2 years ago

Also, if user with expired authorisation (on keypad) try to unlock he is being reported as last unlock user (action-unlatch) despite the fact he WAS UNABLE TO OPEN DOOR !