I am currently trying to change the connection to the NUKI Bridge API from token to hashed token.
All calls with TOKEN work.
Unfortunately when I use the hashed token I always get a response with the status code: 401.
I have a function to generate the sha key which generates the same key with the parameters from the API description.
sha256(“2019-03-05T01:06:53Z,4711,123456”) = f52eb5ce382e356c4239f8fb4d0a87402bb95b7b3124f0762b806ad7d0d01cb6
Therefore I exclude an error in the function to generate the SHA key.
I have the assumption that it can be the TimeStamp.
I tried the following values, but no success.
timeStamp “2022-03-14T17:11:21Z” the local time is UTC: Mon, 14 Mar 2022 18:11:21 GMT".
timeStamp “2022-03-14T18:11:21Z” the local time is UTC: Mon, 14 Mar 2022 18:11:21 GMT"
The second try doesn’t make sense from my point of view either, it’s not ZULU time (UTC +0).
This is how the URL for hashed tokens looks like:
http://192.168.178.107:8080/unlock?nukiid=xxxx&deviceType=4&ts=2022-03-14T17:11:21Z&rnr=16&hash=xyz………
And this is the URL for tokens:
http://192.168.178.107:8080/unlock?nukiid=xxxx&deviceType=4&token=xyz
Maybe it is something else.
Who can help me here?
Ralf
My hardware
Nuki Smart Lock 3 Firmware Version 3.1.10
Nuki BridgeFirmware Version 2.12.0