Hello,
We’ve encountered again this issue last week on one of our smart locks.
Here are the logs (reverse chronological order). The lock appeared online, and the API returned a successful response (204 No Content ) when creating an access code. However, the customer later confirmed that the code was never actually created on the lock.
2026-05-18T14:18:28Z info ResponseReasonPhrase: No Content
2026-05-18T14:18:28Z info ResponseStatusCode: 204
2026-05-18T14:18:28Z info ResponseBody:
2026-05-18T14:18:28Z info Parameters: {"json":{"name":"XXXX","accountUserId":"REDACTED","allowedFromDate":"2026-05-22T16:00:00+02:00","allowedUntilDate":"2026-05-26T11:00:00+02:00","allowedWeekDays":127,"type":13,"code":"HIDDEN"}}
2026-05-18T14:18:28Z info Request: PUT /smartlock/<redacted>/auth
2026-05-18T14:18:28Z info Status code 204
2026-05-18T14:18:28Z info Request to PUT https://api.nuki.io/smartlock/<redacted>/auth
2026-05-18T14:18:28Z info Status code 200
2026-05-18T14:18:28Z info Request to GET https://api.nuki.io/smartlock/<redacted>/auth
2026-05-18T14:18:28Z info State: ok (0)
2026-05-18T14:18:28Z info Status code 200
2026-05-18T14:18:28Z info Request to GET https://api.nuki.io/smartlock/<redacted>
2026-05-18T14:18:28Z info Checking whether the smartlock is online...
As put it the logs, we check that the smartlock is online, and it was.
How to definitely avoid this?
Thanks!