Gen5 and http call does not work from a shelly 1 gen3

[det (her)]

Hi there,

the Nuki Gen5 is a good device and i coupled it with a fingerprint system, with a shelly in between. The shelly calls the nuki via the “old” url, composing of the url found by descriptions regarding the “old” bridge used until ver.4.
http:///lockAction?nukiId=xxxxxxxxx&devicetype=0&action=3&token=xxxxxxx

The nukiid is clear, the token was generated within the web.nuki.io section API->API Token -click generate according one.
add this to the url, but did not trigger anything. I am wondering what is the difference between action=5 and action=3 -found both versions in web.

So is this approach still working for the 5’th generation, or not possible anymore? For the bridge it was mandatory to enable dev-api quick connections in the bridge, this i have not found in the app nor in web.nuki.

any idea?

Thank you

[Juergen (Jürgen Pansy)]

@det

http:///lockAction?nukiId=xxxxxxxxx&devicetype=0&action=3&token=xxxxxxx

This is a call to the bridge API (which is not available for 5th gen devices).

@det

The nukiid is clear, the token was generated within the web.nuki.io section API->API Token -click generate according one.

This is a token for the WebAPI.

You can not just mix this things. If you want to unlock your Nuki through the WebAPI you also need to call this API. See the webAPI documentation for an example of how to call it.