This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
doorlock
Comments
What am I doing wrong??
Locking and Unlocking works when controlling via Homey.
And see if you can open http://<ip of Nuki bridge>:<port of Nuki bridge>/callback/list?token=<token here> to see if it lists the IP of your Homey there. Otherwise you can fix it manually and I might have to fix the app
Thanks,
Stopping and starting the app does refresh the actual lockstate. But after that the status isn't refreshed anymore.
Opening the callback list returns:
{"callbacks": [ ] }
http://<ip of Nuki bridge>:<port of Nuki bridge>/callback/add?url=http://<HOMEY IP>/api/app/io.nuki.smartlock/webhook&token=<token here>
Hope that works for you
Added this manually, still doesn't work.
I've added the token which I found after going to maintain bridge in the Nuki app. So this is correct?
When I navigate to the url http://<HOMEY IP>/api/app/io.nuki.smartlock/webhook&token=<token here> it returns an error 404.
I will try to fix the Nuki app ASAP but will have to do that at home, I don't have a Nuki here at the office.
Yes I know, but tried wat happens when I navigate to the api url itself.
How can I delete the token from the callback page of the bridge?
I will temporarily delete the smartlock from Homey because I don't want unplanned actions ;-)
The app is not yet approved in the appstore, but it is coming (version 0.1.8)
I've have version 0.1.8 installed on Homey but I have the same problem that @LJSVV had.
Only restarting the app in Homey will refresh the lock status.
Could you help me?
Since you changed polling to callbacks I have not been able to get any notifications from my Nuki lock to Homey anymore.
When I check the callback entries-list in Nuki, I see 3, all to my Homey.
And each time I restart the Nuki app, 1 entry is added.
But no notifications when the lock state changes.
When I change the lock state in the Homey device, my flows run, but I don't know how these notifications get to my flows (directly from Homey because it changed the state itself? or?)
Do you have any hints as to why it does not work for me?
Thx
Forgot to mention: sometimes Homey executes the flows that says that 'the door is locked/unlocked' while there is no action on the lock at all - very strange; seems like a very delayed action? I don't understand why this happens
Great to hear...
You need to check:
http://192.168.1.xxx:8080/callback/list?token=<token>
Make sure to input the IP of the Nuki bridge, as well as your token in the end.
It should show something like:
http://192.168.1.xxx:8080/callback/remove?id=<id>&token=<token>
Make sure to only leave the first entry.
I have tested it and it now works with the webhook.
FYI: just a few minutes ago Homey said out of the blue: 'De voordeur is open' (frontdoor is open) while nothing happened at the lock at all, it is still locked.
@swttt I guess I need to adjust some code so it gets updated inside Homey 'realtime'. Will try to do that next weekend.
Latest app version installed, even updated the lock's firmware on the go.
Nuki reports a single callback url, but still nothing happens in Homey when lock is operated.
Only when I restart the Nuki app in Homey I get a triggered flow that says 'The door is locked' while it is unlocked in reality
I can operate the lock from within Homey and also get feedback then.
Hope you get this fixed soon.
I've also installed the latest app version and removed callback entry but one.
Now if I check the device status in Homey it says that it's locked but actually Nuki is unlocked.
Could please fix this?
http://192.168.1.xxx:8080/callback/list?token=<token>
Please make sure it is the IP of your Nuki bridge and the correct token. Probably, the Nuki lock is listed 3 times in there because of a bug in the previous version.
If you then run:
http://192.168.1.xxx:8080/callback/remove?id=1&token=<token>
and
http://192.168.1.xxx:8080/callback/remove?id=2&token=<token>
Then it should only return the status once.
Sorry for the inconvenience!
The status is returned in Englsh when for example adding the tag to a speech card, but I use an extra flow for translation