NUKI status not updated

[chrisboer]

I think due to the difference in EN and NL , Nuki flow don't give any status on lock changes with Homey language on NL

[jordenc]

It has been working for weeks for me. I use the English version but that shouldn't matter.

Perhaps you can show the flows that don't work?

[chrisboer]

[jordenc]

Strange. Could it be that the action in the last column is giving problems?

This one works well for me, I notice it daily

[chrisboer]

Why would the action in the last column be a problem it simply sends a message to my phone.

[jordenc]

Just want to rule out that the problem is not in push message function.

[chrisboer]

Ok do you want me something to check ? or do, are you still on slack ?

[jordenc]

Please try if it works if you let Homey say something, like my example. We can then see if it works or not.

If it doesn't work, please double check that the Nuki has the URL for your Homey set correctly:

In a browser, open: http://:8080/callback/list?token=

Please make sure that there is 1 URL linking to the IP of Homey. You can paste the output here, there is not any "sensitive" info in there.

[chrisboer]

Does not work

[chrisboer]

you mean http://192.168.2.27:8084/callback/list?token=mytoken it gives

callbacks
0
id	0
url	"http://192.168.2.18:80/api/app/io.nuki.smartlock/webhook"
1
id	1
url	"http://192.168.2.18:80/api/app/io.nuki.smartlock/webhook"
2
id	2
url	"http://192.168.2.30:80/api/app/io.nuki.smartlock/webhook"

[jordenc]

Okay, you are still suffering from an old bug.

You can execute: http://192.168.2.27:8084/callback/remove?id=2&token=mytoken http://192.168.2.27:8084/callback/remove?id=1&token=mytoken

and I advise you to: http://192.168.2.27:8084/callback/remove?id=0&token=mytoken Then restart the Nuki app on Homey (Via settings, go to the Nuki app and press the restart button) so it will restart.

Big tip from my site: Give Homey a static IP address in your router, because the Nuki app will only report correctly if the Homey IP doesn't change. Sadly, this is the only way that it is possible currently, because if I use the static Homey cloud URL https is required, and the Nuki bridge does not support posting to https.

[chrisboer]

Ok homey has a static IP, and I have restarted the Nuki App but now I get

HTTP 503 Unavailable nothing... on callback list.

I will restart nuki bridge and Nuki and homey

[chrisboer]

Still no callback IP from Homey

[jordenc]

Does http://192.168.2.27:8084/callback/list?token=mytoken show the correct IP? Otherwise your Bridge probably also responded 503 to Homey. Sadly, the bridge is a rubbish piece of hardware that times out a lot.

You can manually do this: http://192.168.2.27:8084/callback/add?token=mytoken&url=http://192.168.2.30:80/api/app/io.nuki.smartlock/webhook

(make sure 192.168.1.30 is the correct IP)

[chrisboer]

Ok

callbacks
0
id	0
url	"http://192.168.2.20:80/api/app/io.nuki.smartlock/webhook"

and status also works perfect now.

Many thanks jorden... ;-)

[CAvE72]

I had exactly the same issues as Chris and solved the problem with the instructions above. Can you please put the instructions into a FAQ, with more detailed instructions which IP address to use (NUKI bridge or Homey) AND point instruct to give Homey also a fixed IP (next to the NUKI bridge)?

[jordenc]

Good point. Will update the README.