Nuki Opener: Different Smartlock ID in Bridge API compared to Web API

Nuki APIs Web API
1

Retrieving the Nuki Opener from the Bridge API returns a different Smartlock ID compared to the Web API (retrieving from /smartlock).

For the Nuki Smartlock, both IDs are the same. Only the Nuki Opener is affected for me.

2

There are some differences how devices are handled with the Bridge API and the Web API. That’s why for the Bridge API we just had to add the deviceType while for the Web API we needed to use the deviceType also as a prefix for the HEX value-ID which is calculated into the DEC one to be 100% sure there can be no issue with not-unique IDs in any calls.

So e.g. for a Opener ID 1A2B3C4D we use 21A2B3C4D to get the DEC 9028975693.

I will see that this is added to the documentation as soon as possible.

1 Like
3

Isn’t it possible to add the actual nukiId to the Web API as well only for the information purpose? I do understand that the smartlockId is necessary to have a unique identifier, but the nukiId would be helpful to easy match the entries in both APIs in any program.

4

Go to your deviceID and copy this HEX put a 4 in-front of it and transform it to decimal → hextodecimal)
–example: nuki 1 or 2, needs a ‘0’, Nuki box needs ‘1’, Nuki Opener needs ‘2’, Nuki Smartdoor needs ‘3’, Nuki 3+4 needs a ‘4’.
Example: ID in HEX ‘1A2B3C4D’ → add the prefix 41A2B3C4D → convert HEX to decimal 17618910285

5

This topic was automatically closed 60 minutes after the last reply. New replies are no longer allowed.