The Nuki API supports five actions: unlock, lock, unlatch, lock 'n' go, lock 'n' go with unlatch.
Are there plans to support the full set of endpoints (so: add lock, unlock and lock 'n' go with unlatch)?
The nuki api also supports Notifications now.
This would be a great addition for the new nuki opener.
For example when sombody rings the bell I Could Sent a picture of my door camera to my phone.
Or when I Open the door when I was away I could start my music.
Here is a link to the api
Same for me. Would like to see a deeper integration of the Nuki lock as it integrates with AirBnB reservation services now. But it seems that nobody is working on the actual integration (as no response on our requests since months).
Hi, I am thinking about buying this smart lock or Danalock v3.
As always, the first thing I look for is its level of integration with HA. It doesnât seem to have much as per your comments. Can we use it for lock/unlock within homeassistant, and does it report its state in order to be able to integrate automations?. The documentation for the integration does not say much. Thanks!!
It seems the codeowner for nuki integration is @pvizeli, so we must pray to him for update of the API.
Currently it only supports open/close for the smartlock and opener errors out with 404.
According to the HA Nuki Smart Lock documentation âPlease note that the API token should be 6-20 characters long, even though the app allows you to set a longer one.â
How do you get/set an Nuki API token? Because when I use the Nuki web it generates an API token for you. Mine is 80 characters long! So it does not work for me with Home-Assistant.
Does anyone actually use Nuki Smart Lock 2.0 with Home-Assistant successfully?
Update:
Answers
1.Understood it wrong. You donât have to use Niku web apparently to get the API token. Via a HTTP API call with the Nuki Web API token e.g. http://(ip-address):8080/info?token=(Niku Web API Token 80 characters) a âHTTP 401 Unauthorizedâ message is returned ( ).
So reuse the Nuki Bridge API token. Retrieved it via the Android app. It is working now.
2. Not relevant anymore
If no one is up to updating the implementation, maybe itâs possible to create a template sensor that would be triggered viatwo IFTTT webhooks to show if the door is closed or opened.
The lock/unlock functionality is implemented and has been for years. When you set it up correctly you end up with a lock entity that you can lock and unlock
I havenât tried with a 2.0 device since I do not own one, but I am very confident itâll work just fine. If it does not, please open an issue on GitHub.
Regarding the opener, Iâve started working on it at the pynuki level (see https://github.com/pschmitt/pynuki/tree/api_v1.10) . I donât own one either. I need people to try it out. I can only code blindly.
I have tested the available 4 services on my Nuki Combo 2.0 today:
lock.lock <- seems to work fine
lock.unlock <- unlocks the lock, but does not open the door
lock.open <- unlocks the lock, but does not open the door
nuko.lock_n_go <- unlocks the lock, but does not open the door, after 20 sec. locks again.
If I use the Nuki app, I can open the door just fine.
I noticed that the nuki bridge doesnât support state checks? (If the door is closed or not, with the magnet sensor)
That only seems to work with the nuki web appu