technyon / nuki_hub

Use an ESP32 as a Hub between a NUKI Lock and your smarthome.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Keypad-initiated unlock events not logged

noohi opened this issue · comments

Hi,

is it expected that keypad unlocks (unlatch) are not tracked in the MQTT entries?
I tried to catch it, be it
nuki/maintenance/log
or
nuki/lock/action

But it is filled with useful unlatch entries only if using the Nuki itself directly, not if the unlatch is initiated via the Keypad (fingerprint in this case).
Is that normal, to not see if the door were unlatched via the Keypad?

These are the events I tried, and they work if unlatching the Nuki directly:
When Nuki Lock Action changes to unlatch
When Nuki Lock Log changes to Lock action received: unlatch
When Nuki Lock Log changes to Querying lock state: unlocking
When Nuki Lock Log changes to Querying lock state: unlatching
When Nuki Lock Log changes to Querying lock state: Lock action received: unlatch

None of this happens if using the Keypad.

Any ideas?

Thank you.

It should work, so much I can say. I don't have a setup at the moment to check this, will do once I get it.

It's i guess similar if you open it manually, sometimes it does register status, sometimes doesn't.

It should always register, no matter if the status changed by keypad or manual operation.

Closing as this issue has been stale for 4 months.

Furthermore the nuki/maintenance/log is for debugging purposes, not for tracking lock or keypad actions.
nuki/lock/action only shows commands sent using MQTT and is also not meant for tracking lock actions.

You should use the authorization log for this.