[Notes for wiki] behaviour of HomeKey with Nuki lock

[rhamblen]

To use a Nuki lock you use the custom state option in MQTT.
using nuki//lockAction and nuki//state

Using the tables from the nuki dev guide (and notes in several issues here) we set as follows...
Lock states
unlocking 2
Locking 4
unlocked 3
locked 1
jammed 254
unknown 255

with the commands
unlock 1
lock 2

This means the default settings as above are not the correct settings in the scenario where the lock has two locked stated.
Locked, and Deadbolt Locked.

These states are known in Nuki as
Locked (locked both inside and outside deadbolts fired)
Unlocked (locked from outside and secure but not deadbolted)
Unlatched door has no locking mechanism active (time limit and auto closes its state)

This is totally different to how doors in USA work and are used.

So if you dont want the deadbolt and the 3 turns to lock and unlatch the door, you need to set the actions and setting differently.

Lock states
unlocking 7
Locking 4
unlocked 5
locked 3
jammed 254
unknown 255

with the commands
unlock 3
lock 1

this then treats unlocked as the lock state; unlatched as the unlocked state. With locked not used.
Its sounds counter intuitive but it works!

[Johnmat777]

Hello, do you think to integrate the git nuki hub, in homekey ? This will permet to use 1 esp for 2 git.