Auto Unlock is already blocked for a few minutes after an unlock/open action happened.
But at the same time we can not filter out those extreme cases on Smart Lock side by too extreme filters, as this could decrease user experience with AU again.
So for unwanted openings it is very important to send log files from the Nuki App to our support to check the root-cause on the smartphone (which handles most of the logic).
Thanks for your feedback Stephan.
So for unwanted openings it is very important to send log files from the Nuki App to our support to check the root-cause on the smartphone (which handles most of the logic).
I already did that twice. I guess it’s obvious that it’s a phone releated problem (deep sleep / slow location update or sth likek this regardless of battery optimisation being turned off).
I can collect logs again and send them in, but the result will most likely be the same
Auto Unlock is already blocked for a few minutes after an unlock/open action happened.
But at the same time we can not filter out those extreme cases on Smart Lock side by too extreme filters, as this could decrease user experience with AU again.
The easiest solution would be to add an expert settings to configure the timeout for AU after the door was unlocked (regardles of how and by whom). I understand that changing the default value to a higher one makes the usecase worse for other users, but making this configurable would solve the problem, as I (and probably others) don’t mind setting it to 1h or 30mins or sth like this to prevent the door from randomly opening
Edit –
It’s also clear for me that such a filter timeout is set on the SL and not on the phone, thus affecting all users. Still it’s a better option, at least when it’s configurable.
The easiest solution would be to add an expert settings to configure the timeout for AU after the door was unlocked (regardles of how and by whom). I understand that changing the default value to a higher one makes the usecase worse for other users, but making this configurable would solve the problem, as I (and probably others) don’t mind setting it to 1h or 30mins or sth like this to prevent the door from randomly opening
This! The smart lock should register when the door is opened by others means than the smart lock itself. And this
Auto Unlock is already blocked for a few minutes after an unlock/open action happened.
Is clearly not the case for us atm. Otherwise Auto Unlock wouldn’t open the door a few minutes after we opened it with a regular key.
I rechecked the exact current value. It is 2 minutes; see also Auto Unlock – Nuki unlocks your door automatically – Nuki Support
But this isn’t what we are trying to describe.
If I open the door without any involvement of the Nuki app (reason doesn’t matter) and then Nuki registers me inside the geofence it shouldn’t open the door again. And currently it does.
In example: What behauvior do you expect when I activate flight mode before entering the geofence, open the door with a key, close it again and deactivate the flight mode? Auto unlock will open the door, right? Now I want a setting where it doesn’t. It should register the manual door opening and then deactivate Auto Unlock, because obviously I’m now inside and don’t want the door to open again.
Hi Stephan, just as I wanted to send a log , it happened again some mins ago. Sent a request (ticket id 81695). 2 mins just are not enough. Pls make this time configurable.
Same here. Door opened with a key (21:23), three minutes thereafter (21:26) Nuki registers the phone and Auto Unlock opens the door again. We need something to prevent this from happening, this is a potential security risk when one doesn’t notice it!
One more here with same behaviour. This cannot continue like this. I have 3 small kids at home and the door opens alone! fix this please
It’s really sad how long developers and support staff need to address this request properly.
As I can’t update the 1st post:
All I want is a setting for the smartlock where i can set the timeout after the door was opened.
The Timeout is there already, but too short. Just make it a slider between 0 (or 1) and 240 minutes or something like this. Or 5 fixed values, 2, 5, 10, 60 and 200 minutes or so. Should not be that hard and solves all the mentioned problems
Push …
Several months later, still nothing.
I’m not sure what you are waiting for?
If you want to file a feature request, please do so in the feature requests section and collect votes for it.
Hm, I dunno … MAYBE A SOLUTION TO THE NOW MULTIPLE TIMES DESCRIPTED PROBLEM?!
Several users reported the same problem, provided logs, screenshots and even suggested solutions. And the only reaction we got so far was Stephan, who appearantly didn’t understand what the problem was and then several months of no reaction at all.
It’s a potential security problem and you just see to be oblivious to it or don’t want to fix it.
- There are multiple problems described in this thread. Stephans reaction was perfectly accurate to the problem that was discussed at this point.
- If it were that easy it would have been already fixed. The Nuki Auto-Unlock feature does already use several filters and inputs in order to fix too late or inaccurate Geofence events created by your phone, still there are some cases that can not be eliminated. → If you do the Auto-Unlock function does not work in your setting, you better not use it and use “Smart Notifications” instead.
P.S.: Often increasing the geofence size helps to trigger the Geofence earlier and reduce the likeliness of a too late geofence event.
I voted for feature request, I think the below is pretty ridiculous, I opened the door via the app (the alert didn’t come up as it usually does, doesn’t really matter why), just to have it (auto) unlocked again 3 minutes later?
Hi @Juergen, to your 2nd point:
Partly true, as Nuki just can’t know the phone has location/geofencing on powersafe in some scenarios. But also, there is a very easy solution which has been mentioned multiple times:
Make the 2min timeout configurable (2, 5, 10, 15, 30, 45, 60, 90, 120 min or freetext).
Up to an hour is probably fine for most usecases.
You already have the logic for filtering auto unlocks for two minutes, so it’s literally just making that value configurable.
This is not a feature request, it just makes the auto unlock feature usable in everyday scenarios, so it is a bugfix, or a feature enabling enhancement, if you want to call it that.
Thanks & BR
Leo
In terms of implemenation yes. The problem is that implementing a new feature is just a small part of a “new feature”. It also needs to be integrated in the full ecosystem, explained and - which is in this case the biggest problem - customer care needs to be briefed and deal with all the (non tech) people that change the setting without knowing or understanding the side effects. Thus adding a new feature could create more unhappy customers than happy ones, which is one of the trade offs the product team has to take care of when putting together the roadmap.
Which is understandable. What is not understandable that it took several months for the first kind of useful answers by a dev.
As described before this could be potential security risk. Imagine this scenario:
- Auto Unlock doens’t work for reasons unknown, doesn’t matter. Maybe the phone is turned off or in power saving, really doesn’t matter. And btw. I’m perfectly fine with it if it doesn’t work 100 % or takes a few seconds extra, no big deal.
- I open the door by other means, so manually via the app or via a key or keypad or somebody else opens it from inside.
- Now a couple of minutes later suddenly Auto Unlock opens the door and nobody recognizes it, because nobody is close enough to the door. Now we have a potential security risk. This could be overnight, kids could be at home alone …
The problem seems to be, that Auto Unlock isn’t deactivated once the door sensor registers that the door was opened and closed again. And for this we need some settings or adjustments in order to prevent the scenario described above. We had this several times now when Auto Unlock was too slow for our liking and we opened the door with a key only to realize an hour later that Auto Unlock opened the door again after we already were inside.