Fixed with 4.2.5 Beta
It seems to work with 4.2.5âŚ
In the last two days no issueâŚ
I have the issue again with 4.2.5.
Can you explain this a bit more please? In this|my Thread various problems I had where discussed and also fixed all the time.
(From my side there is, BTW, only one last minor problem existing: Sometimes there is a delay of handling MQTT LockActions, which a) can be seen in an traffic capture and seems to be related with the MQTT KeepAlive process and b) is also already under investigation by Nuki)
still have MQTT trouble with 4.2.5
What problem exactly?
â
First problem, I have a raspberry PI 3B+ near to the nuki (~50cm) ; WiFi is perfect on my raspberry (RTT 5ms) but signal is medium/poor with my SL4 (RTT ~900ms).
I manage my SL4 via MQTT by sending the payload 1 or 2 to the topic nuki/XXXXXXXX/lockAction
Second problem, The SL4 randomly disconnects from the broker (mosquitto) and very often. Moreover, and there is a lag between the MQTT command and the lock action (sometimes my request is even lost).
After some days i can say that with 4.2.5 mqtt seems to work âŚ
RTT of a ping is not a proper measure of WiFi quality. The Smart Lock runs on batteries and RTT times >1.000ms are normal. If you have problems with frequent reconnects follow the steps described here: Smart Lock WiFi/Thread/MQTT connection troubleshooting / FAQ
Update from my side:
After the latest updates to 4.2.6 and the beta version 4.3.1 it is still not stable.
It is beter then before the update, but still not good enough.
Best regards,
Jacob
Give 4.3.2 a try:
Done, Letâs hope it is the final fix, for this.
Since three days not a single delay - Seems to be fixed with 4.3.2
A possible new âtypeâ of issue with 4.2.6 that I didnât have with 4.1.8.
I can unlock via MQTT almost always, but locking almost never works. The lock blinks, indicating itâs unlocked, I issue the MQTT command to lock it and it flashes white once, but doesnât lock. After this, it doesnât blink anymore, possibly indicating it âthinksâ itâs locked now?
If I rotate the lock manually (as to unlock it) it starts blinking again and I can then lock it with MQTT.
This doesnât happen if I lock with the app, so pretty weird.
Looking forward to 4.3.2 (waiting for stable though). For me, 4.1.8 was better than 4.2.6.
Thanks everyone
Then please open a new thread for it and do not write in the 4.1.8 thread.
You could check what the Activity log of the Smart Lock says to this lock commands.
Update: Today, one of the locks was disconnected from the WIFI. After repower hem, it was back.
I have the same issue
The smart lock is not always online.
I connected it to a guest network 2.4 ghz and battery medium but it is still unstable.
I am using a mesh network in the house.
Any idea what else I can do to improve the connection stability ?
Thanks
update:
On 18 april. One of the locks on my backdoor became unavailable in Home Assistant (MQTT), but the lock still works with the app and WIFI, (Disabled the Blue Tooth)
So it is more stable, but not 100% jet.
Best regards,
Jacob
Update:
Today again, one of the locks is not availible in MQTT, the WIFI is still working and the lock is responding with the Nuki app.
Best regards,
Jacob
Update:
The beta firmware 4.3.4 is looking good.
The firmware 4.2.8 is still giving MQTT unavailable issues.
It is less frequent as a few months ago.
Best regards,
Jacob