Hi there,
I’m using the NUKI Pro 3.0 + Bridge to full satisfaction for over 6 months now. The smart lock is linked to Homey through the official app to trigger flows based on lock / unlock events. Think: lights on/off, arm/disarm security system, thermostat control, etc.
Lately I’ve noticed an significant delay in the relay of the event messages between the platform. For example: I’ve unlocked the NUKI through my phone and the lock responds within a second as designed. However, the “unlocked” trigger is send to NUKI Web (and thus Homey) with a delay anywhere between 30 seconds and 10 minutes. In my situation this triggers the burglar alarm which is pretty anoying. Based on my experience for the last month there no issue on “non peak moments” between 10:00 and 16:00 (response times <30 sec). Delays almost always occur between 17:00 - 19:00 on “peak times” when most people come home.
In my effort to troubleshoot the root cause I’ve found that the “unlock” event trigger is delayed between the NUKI lock / bridge and NUKI Web. When I log in to NUKI web after opening the door, the event is not listed and therefore no trigger is given to Homey. Checking back in after 10 minutes shows the event with a backdated timestamp. The Homey app shows the event listed with the actual timestamp, which is several minutes later. See screenshots below.
More people experiencing this problem? Any clues on how to fix it? Feels like it’s outside of my control due to a problem between the NUKI lock and NUKI Web. My best guess would be a throughput capacity problem somewhere in the platform, but I have no knowledge of the backend integration. All help is much appreciated.
Example: I’ve unlocked the lock on 17:25 and the event trigger was given to Homey on 17:29 (4 minute delay)
NUKI app listed as 17:25 seen directly after unlock (in-sync)
NUKI Web listed as 17:25, backdated timestamp - only visible after 10 min (out-of-sync, 4 min delay)
Homey app listed as 17:29 when event trigger was given to Homey (out-of-sync, 4 min)
Slack app showing triggering of unlock-flow on 17:29 (out-of-sync, 4 min)