Thanks, that works after one more failure. I will check 3.7.1 now.
Since the update to 3.7.1 sometimes the locker make the opposite action.
I have set the automatic closure at 22:00, two days ago it opened the door instead.
In the recent activities it says that the door was closed but unfurtunately I found it open. Not a smart move
1 Like
Actions are ok (Door still close at 10pm), but
door status is opposite as in reality. Means it shows Closed, however it is open
Since Smart Lock 3.0 Beta 3.7.0 I am getting Error Codes 0x01 (Motor blockiert) from time to time.
Recalibration fixed it and I dont see any physical changes on the door.
Coincidence or maybe Beta FW related?
This can only happen, when you calibrate it the wrong way around. i.e. you start the calibration from locked state instead of unlocked. Recalibrate it and observe if you see the behaviour again.
There are no changes in 3.7.1 that could create such a behaviour. Do you have debug mode of the Smart Lock turned on or off?
Just turned on
I just wanted to know if it’s turned on or not. Please leave it turned off.
I am doing the re-calibration after every update.
I just repeated it and will monitor
Ok thanks
Anyway, this morning after I left and moved far from home it went crazy.
It locked and unlocked the door several times
There is any way to opt-out from the beta?
Looks more like the App triggered these commands and not the Smart Lock itself. Please create a support ticket from the Nuki App > Menu > Help > Contact customer care and DM me the ticket ID.
Yes, you can opt out of the beta through the same form that you signed up. However, the opt-out will only become effective when a higher firmware version than you have actively installed is available in a public release.
According to the logs of your Nuki App you use Auto-Unlock Expert settings which lock and unlock when you leave and enter the geofence. During the mentioned time period the iOS location tracking noticed several exits and enters (and therefore locked and unlocked the door). I.e. it is not related to the beta firmware of the Smart Lock and looks like a malfunction of iOS (which triggered “geofence enter events” despite you moving away).
Original post has been updated with release notes for the Smart Lock 3.0 Beta 3.7.2
Please install this beta and provide your feedback via this channel - thank you!
Original post has been updated with release notes for the Smart Lock 3.0 Beta 3.7.3
Please install this beta and provide your feedback via this channel - thank you!
Good morning, no change in bad behavior since 3.7.1. The 3.7.3 is worse since the lock Pro is almost ever not reachable. Only shortly after reboot. Best way of access is still via the bridge than via WLAN.
The door was open this night at 00:23 - the lock was closed/locked and no Info warning about this unusual state from the door sensor (open door and lock locked). Nothing in the protocol.
hi is this the fix for the nuki web + airbnb feature where the battery would drain in about 10 days?
Can you elaborate what you exactly mean with this?
when the nuki 3.0 pro is connected to the wifi the battery lasts a long time, a few months.
As soon as we enable the nuki web in connection with the airbnb, then there is some bug that will drain the battery in just 10 days or less.
I contacted support about this issue, it was acknowledged and now im waiting for a bug fix. Meanwhile im using the nuki bridge as it wont drain the battery as fast as using wifi.
My suspicion is that the nuki web is constantly asking something to the nuki.
Hey,
im on 3.73 Beta with a SL3P. First of all I really love the mqtt feature and the auto discovery feature with home-assistant. It is set up instantly and the latency for door lock / unlock actions are awesome.
I just noticed that when I disable internet access for the smart lock (to use it fully autonomously) it seems to trigger a wifi reconnect when it cannot reach sse api. I set up a Rpi to act as gateway for the nuki and I can see DNS requests for A / AAAA records and I assume after two or three failed attempts the wifi gets reconnected (also I use Unifi APs and read about disconnects in earlier firmware versions, but Im not experiencing those so I think this is unrelated).
Maybe this is expected but I would really appreciate to use the Smart Lock with MQTT but without internet.
Regards
1 Like
Original post has been updated with release notes for the Smart Lock 3.0 Beta 3.7.4
This beta version has two relevant changes for Smart Lock 3.0 Pro owners:
- A Fritz!Box 7590AX is automatically detected and the workaround for the reported problems with firmware 7.5x with this box is automatically applied. For more details follow this thread: FRITZbox 7590 ax issue with Wi-Fi smart lock 3.0 pro
- By changing the Smart Lock > Settings > Features & Configuration > Battery > Energy-saving mode to “Medium” the WiFi power saving mechanisms the Smart Lock uses are reduced (similar to what the workaround for Fritz!Box 7590AX does). This can have a positive impact on the stability of the WiFi connection of a Smart Lock 3.0 Pro.
Please test the new functionalities and let us know if they have any impact on your Smart Lock setup.
1 Like