Bridge HTTP Callback sends wrong state

Nuki APIs Bridge HTTP-API
1

Hello,

i’m using a Smart Lock 4.0 Pro together with the fingerprint sensor and a Nuki Bridge.

My problem is, that even when an unrecognized / unregistered finger is detected, the Bridge always sends an “unlocked” event to my callback.

[deviceType] => 4
[nukiId] => xxxxxxxx
[mode] => 2
[state] => 3
[stateName] => unlocked
[batteryCritical] =>
[batteryCharging] =>
[batteryChargeState] => 80
[keypadBatteryCritical] =>

This probably is because my lock already was “unlocked” (i use the Nuki to open the door, not to lock it).
Is there any way to distinguish this or get more detailed events here?

2

Hi Daniel,

There are no further options/details when using the Bridge-API.
Since you’re using the Pro variant you can activate WiFi on the Smart Lock directly and enable the MQTT API, which will give you mode detailed information about the lock action (i.e. also show the “unlatched” state if the open door action is performed).