tree 04eea6a0f3465464fe32947a3f9cc59df4501872
parent e1d34eac33e78632883eb8f02ba5dd3edccac5bd
author Arkadiusz Bałys <arkadiusz.balys@nordicsemi.no> 1697736526 +0200
committer GitHub <noreply@github.com> 1697736526 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJlMWdOCRBK7hj4Ov3rIwAAnccIAAgSepUmIRB4f2Adt328hK6E
 SQ+k8nK+2/V+bKiYnOyvzTVIhUWCJsJc5cSikZDiI95mmx9DE3WL8HNcQTO/v6lT
 Y87Pz7zrzp9fPcU4w6tqLC3jyzdTww0YqAPhSvEuycRSs+UgZl988yVr9oHAdo8K
 2b6TpQkHNnF0qFzx85/kIHcE+8NBnc+xAt7ZdyyddXyB+nRGFP3HdfgYFC1oyATZ
 BqKFZ6ZRJ5xebkoV2VjvYi3KDcygcQk/CnMhuKKPi9Zz2g5qK2cC1MoL9fozf5ar
 Uoifi2IDjUSTx6T8BbTHcRURCMI5Wxjf2VxFioX20gYtsU7jbVk3Xkw3M+c3zfw=
 =xyoC
 -----END PGP SIGNATURE-----
 

Add handling a local lock operation error to door-lock-server (#29857)

The current implementation of the door-lock server supports emitting
the LockOperationEvent only if the credential has been provided remotely.
In case we use a custom handling lock credential in the application
code the event is emitted only on the correct credential, but we also
need a mechanism that allows the door lock server to handle a lock
operation error when the wrong credential has been provided.

Added handling local lock operation error to emit LockOperationEvent
and call HandleWrongCodeEntry.