Thanks for the note! We are looking into this issue if it could be anything on our side.
Hey @MatthiasK !
Thank you for your reply!
Do you want me to send you my applet ID or anyhting of the sort so that you can take a look at the logs?
I wanted to check those out on the IFTTT side, but I could not find a way to access them unfortunately.
Hi @tows
It ist very important for me since I run an autolock when the door has been closed and some other security related applets for my security cams…
Yes, if you can send me your Applet version ID (not the general Applet ID but your personal one) via DM, I can check the IFTT Logs for the last 48 hours.
Click on my name and then on the “Message” Button.
1 Like
Well I hope there will be a solution, because it would be quite an issue for me too, if the error persisted like this.
I’ll keep you in the loop in case there is any update that could lead to a possible solution to the problem!
Hi, I’ve the same problem, since beginning of March, maybe due to firmware upgrade 2.10.8? Thanks in advance.
Also had this issue the last week too (Nuki Opener + IFTTT). Mine triggers eventually but it usually takes 5 minutes where as before it was less than a minute.
Hey @esoriani !
I don’t think that would be the issue, though I’m not sure of course, but the troubles on my side started before that update, so it does not seem related, though maybe there is a link to that, based on what changes happened in the backend maybe.
Let me know if you figured out any solutions to that!
Hey @Svenning !
I don’t think that that issue comes from the same cause than this one. Have you checked in the Nuki app under “Manage Smart Lock” - “Energy Saving Mode”, the frequency that is set?
I also was facing a similar issue some time ago, and changing that to a faster syncing between the bluetooth actions and the bridge registering those online fixed that. That is to say, a speedier synchronization fixed the incresing delay between the action and the trigger!
Let me know if that changed anything, I’m interested in knowing 
It’s set to automatic and I’m also in Debug mode… I can try to change it to fast as and see if that changes anything. In my experience what you are talking about is only having an effect on Nuki notifications are delayed or not showing up at all (which also delays IFTTT). That’s what’s been my issue in the past (I’ve had a couple of threads about this). Is that IFTTT not getting triggered at all and the only way I could get it to work was to activate Notifications that somehow forced the IFTTT to get triggered faster. But I haven’t experienced this where my Notifications are coming almost instantly but the IFTTT is not getting triggered. In general it feels like there’s some server side issues on Nuki side since a lot of threads I’ve seen are talking about delays.
I have as well the same issue here as initially described by David. It happened a couple of day ago I personally think after the upgrade to 2.10.8.
Hope a solution will be provided soon.
1 Like
@tows
In my opinion it could not be the firmwar update because I did mine after the triggers stopped working!
@tows @sfreek @esoriani @Svenning @Claudio_Granella
In coordination with IFTTT support we could track down and fix the issue and everything should be working as expected again.
EDIT: For clarification: It was not connected with the firmware update in any way.
2 Likes
Just wanted to let you know too that it is now fixed @Claudio_Granella !
I checked on my side, and it works again for me at least!
David
1 Like
Thanks!!
1 Like
Many thanks to all, it works again!!
1 Like