Ok i got it, the problem is , if you set the api token with high case letters, it will fail. For example e had the token set as 12345TesT, and it didnt work.
I changed to lower case letters, 12345test and the lock apeared on ST.
Hope it helps
1 Like
I’ve already released an update to lowercase the token. Maybe you had the old version 
Anyway, good to know that it works
1 Like
Quick question , how do i update drivers? Is a command? Or a action in app?
Sorry im very new to edge
In theory it automatically gets the updates (but there’s a delay)
Hi
It’s working with Nuki Pro?
@Liran1115 you should test because I don’t have one unfortunately…
unfortunately I couldn’t find the APIs permissions in nuki app.
1 Like
Is it normal that the led on the nuki bridge stays always on after adding to Smartthings?
I don’t think this is related. Mine it’s now off
Is there an update done on the driver for the 3 states of the lock?
Not yet because I have some issues with the custom capabilities (which are also not so well documented…)
I just need more time to dedicate on it
1 Like
Hiii
When will the Opener be supported?
1 Like
I unfortunately do not own an Opener 
Nuki 2.0 here. All working fine
Thank you so much for your time and effort!
Hi Daniele, thanks for making this. I managed to connect everything up easy enough. But whenever I try to lock or unlock i just get “an error has occurred”.
I have the Nuki 3 with the bridge.
Edit: I’ve worked out how to get the logs. Will send to you
Hey @Gokul_Gopakumar i see you have the Nuki 3.0 - so do I.
It looks like this integration doesn’t work for me because the lock/unlock actions require deviceType=4 to be passed to it for the Nuki 3. Ive tested this theory locally and it seems to be the case - if i don’t include the device type the unlock/lock don’t work - as soon as i do it works.
I’m assuming you’ve not seen the same?
Edit: scrap that. It was consistently not working for me without the device type… then i post this message and tried it again and it works. 
i seem to be getting 503s regularly though. I’ll keep digging.
2 Likes
Yes I do have the Nuki 3.0 (not pro though).
Lock and Unlock works but i also need unlatch action for usability. Hence I have not tested the driver since end of September '22; waiting for an update
Edit: I just went around looking at devicetypes. I see the following.
0 … smartlock - Nuki Smart Lock 1.0/2.0
2 … opener - Nuki Opener
3 … smartdoor - Nuki Smart Door
4 … smartlock3 - Nuki Smart Lock 3.0 (Pro)
Source: Nuki Developers
So we both do have devicetype 4. unlock and lock actions worked fine. will check again and report.
Thank you for your work, this worked perfectly for me.
Thank you for your work on this - it installed into Smartthings easily.
What i have noticed is that the led on the bridge is on/blinking almost constantly now (this has been previously identified in this thread) and the Nuki app is taking along time to get the lock status (minutes) whereas before it was almost instant.
Do you have any idea as to why and what I can do to remedy these symptoms?
As a test I’ve just severed the link between ST and my Nuki Bridge by putting an incorrect IP into the Smartthings device settings for the bridge. The nuki app started behaving as expected immediately. When i reinstate the connection the Nuki app slows again. Hope that’s useful.
1 Like
Hi
I can see the same happening to me.
I had to “disable” the driver to allow for a smoother NUKI app.
How can we get to the logs, as I think the driver is keeping multiple connections to the bridge causing the network issues.
1 Like