I gave up on the IFTTT thing.
It was a bit of a headache, but I solved it for me by just using the local Nuki Bridge HTTP API (developer.nuki.io) over my local WiFi. Not complicated, but the server I’m using just accepts https, the Nuki Bridge just does http. So a reverse Proxy was needed.
Hopefully it is now a bit more reliable than the IFTTT shit…
I understand you, unfortunately I have things setup, where I need ifttt, - and actually, it looks like that the issue comes not from ifttt side!? But when this keeps that way like it is now, then I have to think about other ways, to achieve what I want!?
Dont know if you heard it, but there was/is some issues with the services, where nuki&ifttt have investigated this issues and made a fix on 21.12. what really solved most of the issue, it works to 90% for me now, but still is not solved fully, and under investigation of nuki and ifttt!
Yeah. I still believe it is a general Nuki issue at the moment.
A similar problem seems to occur with the Amazon Alexa skill. Same symptoms. The service disconnects, and you have to reconnect manually.
I bet it’s the same bug.
Hello! No it’s not the same bug! I have the same, alexa still disconnects after a short while, but Google keeps it! I am in contact with nuki and ifttt for this, because this issue is just related to alexa now, Google and ifttt works now for me to 95% stable and reliable!
Update: It looks like we finally nailed down the remaining issue and the disconnection problem after 1 hour should be gone for all users. Please reconnect again and get back to me with your experience, if possible.
Very cool! Of course, I will do a bit testing, and let you know, how it goes! Thanks!