lockActionEvent tiggered even in case of wrong code input on keypad

Nuki APIs MQTT
1

Hello together,

  1. The lockActionEvent delivers in my case (when a wrong code is entered in the keypad): “1,0,1921XX,0,1” .

  2. When I reed the documentation (MQTT API Specification v1.3) then “Only lock actions that are attempted to be executed are reported. E.g. unsuccessful Keypad code entries or lock commands outside of a time window are not published.”

  3. And especially to log then the LockAction 1 = unlock I think is not correct. Background-Info: I use the home assistant MQTT integration and listen to the lockActionEvent to then also trigger some automations and I though that the first digit in the coma separated list is the LockAction and 1 is unlock.

Is this only happening to me and/or is this even correct (and I understood maybe the documentation wrong)?

Thanks Michael