Bridge seems to not support "secure" tokens

[bhuebschen]

I have a Nuki-Lock and a Nuki-Bridge connected to Home Assistant.

{
   "bridgeType":1,
   "ids":{
      "hardwareId": ####,
      "serverId": ####
   },
   "versions":{
      "firmwareVersion":"2.14.0",
      "wifiFirmwareVersion":"2.3.0"
   },
   "uptime":43432,
   "currentTime":"2022-07-30T06:35:40+00:00",
   "wlanConnected":true,
   "serverConnected":true,
   "scanResults":[
      {
         "deviceType":4,
         "nukiId": ####,
         "name":"Nuki_####",
         "rssi":-50,
         "paired":true
      }
   ]
}

But at some time, pynuki wasnt able to call the api due to an invalid token... after some investigation i found out, that the line:

pynuki/pynuki/bridge.py

Line 94 in 22433b3

get_params = hash_token(self.token)

causes the error ... using the plaintext-token as in

pynuki/pynuki/bridge.py

Line 96 in 22433b3

get_params = {"token": self.token}

works fine.

Unfortunately i cannot disable "secure"-tokens via Home Assistant.. but on the other hand it would be fine if i know why hased tokens don't work on my setup (and how i can fix that)... now everytime pynuki get's updated, i need to "patch" it to get my setup work again.

Thanks in advance,
Benedikt

[bhuebschen]

Ich habe aktualisiere normalerweise immer alle firmware's recht zeitnah ... es dürfte also nicht an einer alten Version liegen

[phm46]

I have this issue for a long time. In my case it was caused because of wrong date/time on nuki bridge (few hours difference). That's why hash token fails and why I needed to use plaintext token.

[bhuebschen]

i checked date and time.. everything is fine.. but my bridge still dont want to accept the hashed token