I am currently using the Nuki Keypad 2 in combination with a Nuki Smartlock 4 Pro.
I have set up for my keypad, using the Nuki App, certain Code IDs (“Berechtigungen”) with associated codes without the permission to lock (“ohne Sperr-Erlaubnis”).
I am using these codes to exclusively trigger things other than the lock in my smart home, e.g. a garage door. To do so, I currently listen for the corresponding MQTT lockActionEvent messages. For the Code ID without lock permission I get “3,0,<>,<<Code-ID 1>>,1”, while the Nuki Smartlock does nothing (and correctly so!). For the “regular” codes with lock-permission (say Code-ID 2), which trigger my Nuki Smartlock directly, I get “3,0,<>,<<Code-ID 2>>,1”.
I have read somewhere, that this behaviour is supposed to be a bug that will be fixed soon (https://developer.nuki.io/t/lockactionevent-tiggered-even-in-case-of-wrong-code-input-on-keypad/37326). Is that true? I would then no longer be able to use the keypad for non-lock events in my smart home, which would be a pitty! I love this feature!
Would I be able, after a firmware upgrade some time in the future breaks my setup, to revert back to my current nuki firmware?
In the MQTT specification document, https://developer.nuki.io/t/mqtt-api-specification-v1-3/17626, I read that it should be possible to: “Trigger something when a specific keypad code was used”. How would that work without lock-actions if the above avenue would be blocked?
Thank you!