So I installed a new Nuki Ultra on my main door (after installing several Nuki 2 and 3 throughout the years).
Installation was a bit challenging due to the door’s mechanism but eventually I managed to overcome all the issues and the Nuki works perfect… well, almost…
Wherever I go into my apartment, after the Nuki auto unlocks itself or after manually unlocking it, I have to turn it a bit counter clockwise or it won’t lock itself when the sensor recognizes the door is closed. Only then - the Nuki actually locks itself.
If I don’t do this little turn - the sensor recognizes the door is closed and reports it’s locked, when in fact it remains unlocked.
You can see this in the attached video:
This isn’t consistent though, as sometimes I forget to do this little turn and the Nuki does lock it, so honestly I have no explanation to what could cause this - a hardware (lock or sensor) or software issue?
Would highly appreciate a solution as this is a bit frustrating.
Thanks for your reply!
I tried running a calibration several times… it didn’t help of course…
Is it a known bug?
Is there a beta version with a fix I could try?
One more question…
What should I do next after emailing my smart lock ID yesterday?
Am I supposed to see the beta firmware when trying to update to a newer firmware (at the moment I still don’t see any beta one)?
So I installed the beta firmware 5.52 as suggested, did a new calibration to the door and to the sensor and at first I thought that the problem has been resolved.
Today, 20 hours after installing the firmware, the initial problem returned…
Any more suggestions would be highly appreciated.
When was the last time you’ve applied lubricant - like Ballistol and/or WD40 - to the actual lock (not the Nuki lock)?
Before I installed the Nuki Ultra, I figuratively soaked the door lock in lubricant and was wondering why I haven’t done that before. Couldn’t believe how smooth a lock can be.
We are following up on this topic and we are currently narrowing it down to a possible issue with the Door Sensor.
In order to keep this thread clean and ordered and since I am already in touch with Omri for details, please let us know if anyone else experienced something similar or manages to reproduce the mentioned behavior.