A few weeks ago there was an issue where Nuki webhooks didn’t arrive for a few hours, once they did it caused some unexpected behaviour for my home automation that is built on it so I decided to add a validation that the event took place in the last 60 seconds and ignore it otherwise.
Now in the NUKI webhooks we get the following (as example)
{
"headers": {
"X-Nuki-Signature-SHA256": "3xxx",
"X-Nuki-Signature": "xxx",
"Content-Type": "application/json; charset=UTF-8"
},
"body": {
"feature": "DEVICE_LOGS",
"smartlockLog": {
"id": "xxx",
"smartlockId": 1234,
"deviceType": 4,
"name": "",
"action": 1,
"trigger": 1,
"state": 0,
"autoUnlock": false,
"date": "2025-04-03T08:23:39.000Z",
"source": 0
}
},
"timestamp": "2025-04-03T08:23:34.847Z",
"path": "https://xxxx"
}
In this you can see a “smartlockLog” → “date” inside the body as well as a timestamp outside the body, I would expect the former to be the date that the lock logged the action and the latter the date which the webhook was sent by nuki server (it correlates with the very late events few weeks ago)
My problem is that the “date” logged by the smart lock is in the future, in the example above the message was received on my side at 08:23:34 so I know that part is correct.
Does it mean that the lock timestamp is not in sync? how do I check/fix that?