A new one since this version - now getting the error shown in the pic on occasion. The lock is definitely not on charge.
(Image removed by Administrator)
The battery drain is significant with my Nuki 4 Pro (only used with Thread), too. After 7 days of normal usage (ca. 2 locking & unlocking procedures per day) the battery pack has lost 14%.
The lock was relatively stable recently, sometime around last week it started to disconnect from wifi much more often. Is there any solution to this? I am getting tired of fiddling with this lock.
Running latest beta firmware, MQTT to Home Assistant. Will a hub/thread/whatever fix this for me? I want it to work, thatās all.
1 Like
Yes, I still have the same problem after updating firmware to beta 4.3.7. I have noticed the same instability than ever. The Smart lock connects when the device is restarted. The DHCP at the router provides an IP address (I have tried to associate a fixed IP to the smart lock MAC address. This address is noted correctly by the App (as I can confirm with the 7x clicks in the network setting in the App). After a few minutes, the connection is lost, and the ARP table at the router seems to have lost the MAC address corresponding to the IP i reserved. (see the picture attached. The IP reserved is 192.168.1.99)
Now after 2 weeks of normal operation with my SL4P and MQTT via WiFi to Home Assistant, i can say that it worked flawlessly with 4.3.7. Before this beta i think i had almost every problem discussed here, except battery problems. i use a USB-C charger permanentely connected to the SL4P, and battery setting set to fast.
please do not try to save battery on setting āfastā in the future!
Iām trying to find a pattern to the issues Iām experiencing. These issues are occasional disconnects, usually no longer than 30 seconds and occasional erratic battery drain.
Iām currently on holiday but have the lock connected over MQTT. All was fine for a week until I remotely powered on the Harmony Hub (for some other reason). Directly after it the lock went offline again and hasnāt come online anymore.
Iām now wondering if the Nuki issues are perhaps related to the XMPP server on the Harmony Hub or something. Anyone of you guys have this device and is so have it connected to a home automation system like Home Assistant?
I eventually forced a reconnect from the UniFi controller and it was online again instantly. Weird stuff.
Iāve got a very similar setup. My 4.0 pro lock is running the 4.3.7 beta and speaks to HA via MQTT over wifi. It is connected to a USB charger. I also have the Harmony Hub connected to HA.
I see short disconnects, usually 10 seconds before some action (locking or unlocking). Interestingly, if I see the status āLockingā then it doesnāt disconnect:
Hereās what I see in the MQTT logs:
The battery of the lock also shows these temporary low (21%) battery statuses for a few minutes every now and again. Interestingly, I see that it isnāt charging at the moment even though it is plugged in.
Iām also on holiday at the moment so I canāt try disconnecting Harmony.
Follow up: after a week with the Bridge turned off I didnāt experience the problem of completely losing the BT connection again. So it seems to be only an issue in the constellation Lock + Bridge (maybe + Door Sensor).
This is most likely due to an erroneous battery detection. If you use a Power Pack itās best to also set it to āPower Packā in the settings and not leave it with āAutomaticā.
1 Like
Original post has been updated with release notes for the Smart Lock (4th generation) Beta 4.3.8
- This Beta reduces the power consumption in āfastā mode.
- We did fix a few cases in which the remote access via Thread lost the connection and did reconnect afterwards.
- WiFi reconnects are now more aggressively reconnecting to the WiFi network when a new connection to a server could not be established anymore over the existing uplink.
- The Smart Lock now properly reports the unlatched state via Matter to supported Smart Home Hubs (Mainly Home Assistant)
- And finally we did include several smaller bugfixes.
Known problems:
For some users the Smart Lock becomes unresponsive from time to time either from remote or locally via Bluetooth. If you experience this problem, please retry reaching it several times. The Smart Lock should detect the problem and restore the original state and work again after 3 failed attempts. If you run into this issue, please let us know here in the forum or via DM. Thank you!
1 Like
Ok, sounds greatā¦hm, not really great, but ar least we found the pattern. Hope @Juergen will be able to solve it
I still have to check BT freeze issue while using Brig/Hub with 4.3.8, but even before the Nuki 4.0 Pro could already unfreeze by itself. The problem is, this could take 2-3 hours until it is back to life, or something it didnāt unfreeze at all.
I would say, the nuki lock BT logic should be quite straightforward: if it could not connect/ping Bridge/Hub for 1 min or some really short time frame, it should restart BT stack or reboot itself completely(but for a god sake, without unlocking a door as part of lock positioning process).
I know, it is rather a workaround than fixing the issue, but as for now Nuki lock is completely unreliable while connected to the Bridge. Like you itās not possible to leave an apartment or house without a real key, otherwise if Nukiās BT is stuck, you canāt get home at all. So I would say it should have a higher priority that even any of MQTT related issues
2 Likes
Iāve just updated my nuki smartlock to 4.3.8 and battery level increased from 44 to 62%
1 Like
@JeyKey Experiencing the same Nuki 4 pro freeze like you. Iām still on stable firmware 4.2.8 and no beta installed. However what I noticed is that the lock does still response to HomeKit / matter and I am able to lock / unlock it. But that doesnāt help because you cannot open the door via HomeKit at the moment.
The only solution for me to get the lock back to connect to the Nuki app is to remove the batteries and reboot it.
@discostur try pressing the button until the LED is permanently on (~5 sec), see my video above Smart Lock (4th generation) Firmware Beta 4.3.x - #193 by jho
Hello. Since 4.3.8, the Matter Remote Access for Amazon Alexa seems to work.
What was from the beginning on not working (with no firmware) is the optimization of the movements.
My lock is closing counterclockwise. And the logic in the Programm is somehow done for clockwise closing. The movements are getting in my case longer than shorterā¦
Hi. It would be great if there can be added a feature that the movement of pulling the latch is programmable.
In my case the motor is always turning until the end again a hard stop which should be not the best for battery and motor.
Thx
Hi JĆ¼rgen, one question, if I update to the latest beta version and it doesnāt work well, can I go back to factory settings?
I believe I have an interesting case regarding a connectivity issue.
I have a Nuki 4 Pro installed on both my front and back doors. Both locks are currently connected via Matter/Thread.
My back door has been stable for days and has no issues, but the front door loses connection multiple times a day.
Front Door:
- Connected via Matter/Thread, distance to the hub approximately 2-3 meters
- Nuki Keypad 2 connected
- Button or bar handle
- Firmware version 4.3.8
Back Door:
- Connected via Matter/Thread, distance to the hub approximately 15 meters
- No accessories connected
- Lever-operated multi-point lock
- Firmware version 4.3.8
Could the issue be related to the keypad? I also tried WiFi instead of thread, but experienced the exact same issue then.