Confirmed - My SL4P is now again not reachable via MQTT but it is sending state changes to my MQTT Server. Also noticing the malformed packages again, in the Mosquitto Log:
I have noticed that this is only the case until the MQTT Connection is flaged as not working any longer in the Nuki App.
Do you also have the malformed packages on your Broker?
root@loxberry:/opt/loxberry# grep Nuki_3 /var/log/mosquitto/mosquitto.log | grep 17:08
2024-03-01T17:08:16: New client connected from 192.168.1.103:52339 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-01T17:08:17: Client Nuki_39C748EC disconnected due to malformed packet.
In terms of Wifi/Network there is no general problem until the Broker receives the malformed packet from the Nuki. Then the Broker is sending an TCP RST|Reset to the Nuki to cancel the MQTT Setup/Connection attempt:
In this Context this is interesting for me to learn why the Nuki is Publishing so many Topics after the Basic TCP Network Reconnect:
I have this issue with sl4p: if i restart my server, mqtt doesn’t reconnect. I have to unplug and replug the battery.
Instead, with sl3p, mqtt reconnect automatcly (in about 1 hour).
We’re looking into the issue. Unfortunately we have not been able to reproduce it yet. We’ll keep you posted once we have updates.
Having the same issue. (Two SL4P’s).MQTT has never been stable for me. Randomly loses connection. Sometimes it loses connection when operating the lock. I have setup face recognition which then triggers a unlock cmd to the lock. Sometimes the command works, but it loses connection right after that.
Do you also have the malformed packages error log on your Broker?
root@loxberry:/opt/loxberry# grep Nuki_3 /var/log/mosquitto/mosquitto.log | grep 17:08
2024-03-01T17:08:16: New client connected from 192.168.1.103:52339 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-01T17:08:17: Client Nuki_39C748EC disconnected due to malformed packet.
Do you know if this issue Is present in beta fw?
Yesterday i was locked out of my house 
I have a finger print Reader that call home assistant script to open the Door… Luckily my wife was in the area and she had the Key in her bag.
It was my fault for forgetting my cell phone at home otherways i was able to open with Nuki app
No, I don’t see malformed packages. It just disconnects.
I‘m having the same issue with the latest firmware using Mosquitto MQTT Broker. Unfortunately this breaks all my automations with my KNX home. So any hint on the timeline of a fix would be highly appreciated.
Hi, this morning another disconnection.
The log of mosquitto mqtt broker reports:
1709881823: Client Nuki_XXXX closed its connection.
Remove and replug the battery pack make mqtt working for about 48hours
Hi, I have the same problem!
How to activate mosquitto log? I don’t have any logs under /var/log
I use HA 2024.3.0 and 6.4.0 broker
thanks
Luca
We’ve been able to observe the issue with one of our systems too and have a potential fix for it, which is included in todays 4.2.1 beta.
Please update your Smart Lock and test it and report back if the problem still occurs for you.
Installed beta fw. I Will report you in next days
Installed 4.2.1 Beta today and after the Update it first didnt connected to my Broker until I have removed the Battery. Since then no new malformed package errors in the Mosquitto Log:
2024-03-08T16:06:58: New client connected from 192.168.1.103:51951 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-08T16:06:59: Client Nuki_39C748EC disconnected due to malformed packet.
2024-03-08T16:07:51: New client connected from 192.168.1.103:49867 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-08T16:08:26: Client Nuki_39C748EC already connected, closing old connection.
2024-03-08T16:08:26: New client connected from 192.168.1.103:51601 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
root@loxberry:/opt/loxberry
I don’t have new 4.2.1 firmware! The check report the 4.2.0 beta Is the last firmware. Any suggestioni?
Thanks
I forst had to update to 4.2.0 and then the 4.2.1 showed up.
I already have 4.2.0
Luca metti la 4.20 e dopo ti trova la 4.2.1, da me ha funzionato…