SL4P MQTT Problems since Nuki FW Update 4.1.8

[Jan_Stepanek (Jan Štěpánek)]

Installed beta 4.2.1, but after 24h or so the lock doesn’t respond to the MQTT orders from Home Assistant. The auto discovery is on. The only difference with new fw is, I can open the MQTT settings, enter the password and it works again for 24h. So fw 4.2.1 doesn’t fix the issue for me.

[Jacob]

Update:
The second lock is not available in HA anymore.
Also in the Nuki app offline.

Best regards,
Jacob

[SchmuFoo (Jan S.)]

@SchmuFoo

I reconnected it manually (this time with “Home Assistant auto discovery” is turned on, even when I dont need this) and this time this immediately worked and MQTT commands worked again.

Same procedure, now it lastet arround ten hours until I noticed, that MQTT Commands are not working and I had to manually reconnect my Broker again.

[paolo1983]

I’m note sure but…i have to report this.
I assigned into my router settings a static ip to my Nuki smart lock and It Is 3 days that i havent issue…
I Will update you if i get a disconnection or not in next hours/days

[Juergen (Jürgen Pansy)]

@SchmuFoo

Same procedure

Yes, same problem as last time. And …

@Juergen

we found the problem and are currently testing it. Will be included in the next beta.

[SchmuFoo (Jan S.)]

@Juergen

We think we found the problem and are currently testing it. Will be included in the next beta. There is no workaround for the time beeing.

Smart Lock (4th generation) Firmware Beta 4.2.x

Original post has been updated with release notes for the Smart Lock Beta 4.2.3 This Beta includes the update to Matter 1.2, which opens up the capabilities to differentiate between unlatch and unlock. For now the this new feature is only available in case Home Assistant is used as Matter Hub. Next to that further improvements and bugfixes are included in terms of Auto Lock, the detection of manual unlatch actions as well as on the overall power consumption of the Pro version. Additionally a …

[SchmuFoo (Jan S.)]

@Juergen

Yes, same problem as last time. And …

@Juergen

we found the problem and are currently testing it. Will be included in the next beta.

I have installed the brand new 4.2.3 beta this morning and during the day, I noticed a few times that my SL4P was not responding - My Broker also noticed this and I had again to reconfigure the MQTT Connection within the Nuki App: After that everything was fine again for a unknown amount of time.

Will Monitor it and update this Thread accordingly.

root@loxberry:/opt/loxberry# grep Nuki_3 /var/log/mosquitto/mosquitto.log
2024-03-15T13:02:56: Client Nuki_39C748EC already connected, closing old connection.
2024-03-15T13:02:56: New client connected from 192.168.1.103:52434 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-15T13:25:44: Client Nuki_39C748EC has exceeded timeout, disconnecting.
2024-03-15T13:35:46: New client connected from 192.168.1.103:52434 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-15T14:48:26: Client Nuki_39C748EC has exceeded timeout, disconnecting.
2024-03-15T15:46:56: New client connected from 192.168.1.103:52433 as Nuki_39C748EC (p2, c1, k300, u'loxberry').

UniFi WiFi Report:

[SchmuFoo (Jan S.)]

@SchmuFoo

Will Monitor it and update this Thread accordingly.

root@loxberry:/opt/loxberry# grep Nuki_3 /var/log/mosquitto/mosquitto.log
2024-03-15T13:02:56: Client Nuki_39C748EC already connected, closing old connection.
2024-03-15T13:02:56: New client connected from 192.168.1.103:52434 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-15T13:25:44: Client Nuki_39C748EC has exceeded timeout, disconnecting.
2024-03-15T13:35:46: New client connected from 192.168.1.103:52434 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-15T14:48:26: Client Nuki_39C748EC has exceeded timeout, disconnecting.
2024-03-15T15:46:56: New client connected from 192.168.1.103:52433 as Nuki_39C748EC (p2, c1, k300, u'loxberry').

2024-03-15T16:05:15: Client Nuki_39C748EC already connected, closing old connection.
2024-03-15T16:05:15: New client connected from 192.168.1.103:52434 as Nuki_39C748EC (p2, c1, k300, u'loxberry').

[SchmuFoo (Jan S.)]

And again:

root@loxberry:/opt/loxberry# grep Nuki /var/log/mosquitto/mosquitto.log
2024-03-15T13:02:56: Client Nuki_39C748EC already connected, closing old connection.
2024-03-15T13:02:56: New client connected from 192.168.1.103:52434 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-15T13:25:44: Client Nuki_39C748EC has exceeded timeout, disconnecting.
2024-03-15T13:35:46: New client connected from 192.168.1.103:52434 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-15T14:48:26: Client Nuki_39C748EC has exceeded timeout, disconnecting.
2024-03-15T15:46:56: New client connected from 192.168.1.103:52433 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-15T16:05:15: Client Nuki_39C748EC already connected, closing old connection.
2024-03-15T16:05:15: New client connected from 192.168.1.103:52434 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-15T16:38:32: Client Nuki_39C748EC has exceeded timeout, disconnecting.
root@loxberry:/opt/loxberry#

[Juergen (Jürgen Pansy)]

@SchmuFoo

Will Monitor it and update this Thread accordingly.

Thanks. Please do not send any more updates. From looking at the logs it’s pretty clear why you are seeing the reconnects (and it’s most likely not coming from changes on MQTT side, but the many updates that happened in this build for Matter 1.2 support). This requires an investigation by our team which will not happen over the weekend.

[Jan_Stepanek (Jan Štěpánek)]

I have also the issue with fw 4.2.3. It happened, while the lock stops responding to the command from Home Assistant, it executes the command, when I open the Nuki App and keeps working for some time, until it stops again…

[paolo1983]

The same here

[hecho (Luca)]

Same issue for me

[paolo1983]

This morning i got update to 4.24. i Hope that this fw Is able to solve the issue

[Der (der_nasse@web.de)]

How did you install this Version? My Nuki still shows me: 4.2.0 without any Beta

[SchmuFoo (Jan S.)]

@Juergen

From looking at the logs it’s pretty clear why you are seeing the reconnects (and it’s most likely not coming from changes on MQTT side, but the many updates that happened in this build for Matter 1.2 support). This requires an investigation by our team which will not happen over the weekend.

FYI that I have installed firmware 4.2.4 beta on 22.03.2024 and since then I see a bunch reconnects after the Nuki has closed the TCP Connection to the Broker.

root@loxberry:/opt/loxberry# grep -i Nuki /var/log/mosquitto/mosquitto.log
2024-03-19T16:10:59: New client connected from 192.168.1.103:52442 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-19T19:32:02: Client Nuki_39C748EC already connected, closing old connection.
2024-03-19T19:32:02: New client connected from 192.168.1.103:52445 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-19T19:32:53: Client Nuki_39C748EC closed its connection.
2024-03-19T19:32:58: New client connected from 192.168.1.103:52446 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-22T10:41:16: Client Nuki_39C748EC already connected, closing old connection.
2024-03-22T10:41:16: New client connected from 192.168.1.103:52433 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-22T11:06:57: Client Nuki_39C748EC closed its connection.
2024-03-22T11:07:03: New client connected from 192.168.1.103:52435 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-22T11:12:36: Client Nuki_39C748EC closed its connection.
2024-03-22T11:12:42: New client connected from 192.168.1.103:52436 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-22T11:42:25: Client Nuki_39C748EC closed its connection.
2024-03-22T11:42:31: New client connected from 192.168.1.103:52437 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-22T12:02:49: Client Nuki_39C748EC closed its connection.
2024-03-22T12:02:55: New client connected from 192.168.1.103:52438 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-22T12:11:55: Client Nuki_39C748EC closed its connection.
2024-03-22T12:12:01: New client connected from 192.168.1.103:52439 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-22T12:17:35: Client Nuki_39C748EC closed its connection.
2024-03-22T12:17:41: New client connected from 192.168.1.103:52440 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-22T15:44:20: Client Nuki_39C748EC closed its connection.
2024-03-22T15:44:26: New client connected from 192.168.1.103:52441 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-22T16:15:48: Client Nuki_39C748EC closed its connection.
2024-03-22T16:15:54: New client connected from 192.168.1.103:52442 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-22T16:31:32: Client Nuki_39C748EC closed its connection.
2024-03-22T16:31:38: New client connected from 192.168.1.103:52443 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-22T22:02:44: Client Nuki_39C748EC closed its connection.
2024-03-22T22:02:50: New client connected from 192.168.1.103:52444 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-23T10:45:50: Client Nuki_39C748EC closed its connection.
2024-03-23T10:45:56: New client connected from 192.168.1.103:52445 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-23T12:50:19: Client Nuki_39C748EC closed its connection.
2024-03-23T12:50:25: New client connected from 192.168.1.103:52446 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-23T12:55:59: Client Nuki_39C748EC closed its connection.
2024-03-23T12:56:05: New client connected from 192.168.1.103:52447 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-23T13:42:19: Client Nuki_39C748EC closed its connection.
2024-03-23T13:42:25: New client connected from 192.168.1.103:52448 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-23T16:26:29: Client Nuki_39C748EC closed its connection.
2024-03-23T16:26:35: New client connected from 192.168.1.103:52449 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-23T16:45:57: Client Nuki_39C748EC closed its connection.
2024-03-23T16:46:03: New client connected from 192.168.1.103:52450 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-23T16:56:39: Client Nuki_39C748EC closed its connection.
2024-03-23T16:56:45: New client connected from 192.168.1.103:52451 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-23T17:02:29: Client Nuki_39C748EC closed its connection.
2024-03-23T17:02:35: New client connected from 192.168.1.103:52452 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-23T17:09:51: Client Nuki_39C748EC closed its connection.
2024-03-23T17:09:57: New client connected from 192.168.1.103:52453 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-23T17:17:48: Client Nuki_39C748EC closed its connection.
2024-03-23T17:17:54: New client connected from 192.168.1.103:52454 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
2024-03-23T17:28:32: Client Nuki_39C748EC closed its connection.
2024-03-23T17:28:38: New client connected from 192.168.1.103:52455 as Nuki_39C748EC (p2, c1, k300, u'loxberry').
root@loxberry:/opt/loxberry#

[Der (der_nasse@web.de)]

I applyed for the beta firmware program and installed the latest beta. It seems that it is working now with mqtt and homeassistant perfectly.

[tired (Stephan Njo)]

Same for me. Works with the latest beta since release date.

[jvcsw (Jordi V.)]

How many days working without disconnections?

[tired (Stephan Njo)]

Since 22.03.23 - 16:58