Difference in Smartlock ID and Nuki-ID for usage in Web-API

Hello, we have implemented the Nuki Web API for our clients, and we provide instructions how to get the Smartlock ID tο connect each lock with our system.
Basically we tell them to go to Nuki Web → Devices → Click on device and then on ‘Manage Device’.

However, a client reported that there were errors like:
"The supplied value XYZ for parameter ‘smartlockId’ is not valid’

Looking into it we saw that the Smartlock ID he had entered was missing the device type at the start, so it was “377…” instead of “4377…”.

They showed us a photo of the smartlock and their Nuki Web to compare, and everywhere it is listed without the 4 at the start.
How can we direct our clients to find the correct full Smartlock ID to be used with Web-API?

smartlock_id

I’ve found these similar threads (about Bridge) but I do not see a solution to this:

Thank you

Hello Vasilis,

The Web API expects the device ID in decimal format, but before converting from Hex to Decimal, it needs a prefix based on the type of the device. This is explained in the Web API documentation here.

Please ensure to convert the device ID from Hex to decimal with a prefix, before using the ID in the Web API.

Our requirement is that we want an easy way for our clients (the locks’ owners) to find their Smartlock IDs for use with the Web API on their own and add them to our platform’s panel.

It seems our only option is to inform them to look up their Device Type in order to add the correct prefix to the ID.

Thank you.

Yes, based on the type of the device, they need to prefix it to their Smart Lock Hex ID displayed on the device.