SL4P MQTT Problems since Nuki FW Update 4.1.8

Nuki pro 3.0 Firmware 4.2.8 - wifi very not stable. Also I noticed the Time Zone is defaulted to another region during updates which forces router to disallow connection (Starlink, Gen 2)

Major issue when not at property with potentially no way other way to gain entry.

I am noticing a similar behavior with my Nuki 4.0 pro connected to home assistant via MQTT.
The connection is stable, as long as there is no interaction with the lock. As soon as somebody locks or unlocks the door, it is 50/50. Locking/unlocking using the app works fine. The problem is, when interacting with it using home assistant.

  • Sometimes it works flawlessly and reacts correctly.
  • Oftentimes, it hangs in either “locking” or “unlocking” state, and becomes unavailable for around 5 minutes. After that, it comes back online and displays the correct status.

Below there are the MQTT logs. What I am noticing is that Nuki_3A10B07C is closing its connection (this is how I am seeing the bluetooth ID of the lock, even though bluetooth pairing is disabled).
192.168.0.107 is the IP address of the lock on my network. I am spotting a conflict between Nuki_3A10B07C and 192.168.0.107. Could this be the problem?

I am using FW version 4.2.8

2024-06-13 07:47:47: Client Nuki_3A10B07C closed its connection.
2024-06-13 07:47:59: New connection from 192.168.0.107:53740 on port 1883.
2024-06-13 07:48:00: New client connected from 192.168.0.107:53740 as Nuki_3A10B07C (p2, c1, k300, u'mqtt_user').
2024-06-13 07:48:09: New connection from 172.30.32.2:53420 on port 1883.
2024-06-13 07:48:09: Client <unknown> closed its connection.
2024-06-13 07:48:38: Client Nuki_3A10B07C closed its connection.
2024-06-13 07:50:01: New connection from 192.168.0.107:64573 on port 1883.
2024-06-13 07:50:02: New client connected from 192.168.0.107:64573 as Nuki_3A10B07C (p2, c1, k300, u'mqtt_user').
2024-06-13 07:50:09: New connection from 172.30.32.2:46164 on port 1883.
2024-06-13 07:50:09: Client <unknown> closed its connection.
2024-06-13 07:52:09: New connection from 172.30.32.2:39692 on port 1883.
2024-06-13 07:52:09: Client <unknown> closed its connection.
2024-06-13 07:54:09: New connection from 172.30.32.2:35256 on port 1883.
2024-06-13 07:54:09: Client <unknown> closed its connection.
2024-06-13 07:56:09: New connection from 172.30.32.2:51240 on port 1883.
2024-06-13 07:56:09: Client <unknown> closed its connection.
2024-06-13 07:58:09: New connection from 172.30.32.2:45258 on port 1883.
2024-06-13 07:58:09: Client <unknown> closed its connection.
2024-06-13 08:00:09: New connection from 172.30.32.2:41364 on port 1883.
2024-06-13 08:00:09: Client <unknown> closed its connection.
2024-06-13 08:02:09: New connection from 172.30.32.2:57868 on port 1883.
2024-06-13 08:02:09: Client <unknown> closed its connection.
2024-06-13 08:04:09: New connection from 172.30.32.2:45140 on port 1883.
2024-06-13 08:04:09: Client <unknown> closed its connection.
2024-06-13 08:05:38: New connection from 192.168.0.107:52043 on port 1883.
2024-06-13 08:05:38: Client Nuki_3A10B07C already connected, closing old connection.
2024-06-13 08:05:38: New client connected from 192.168.0.107:52043 as Nuki_3A10B07C (p2, c1, k300, u'mqtt_user').
2024-06-13 08:06:09: New connection from 172.30.32.2:50748 on port 1883.
2024-06-13 08:06:09: Client <unknown> closed its connection.
2024-06-13 08:08:09: New connection from 172.30.32.2:43378 on port 1883.
2024-06-13 08:08:09: Client <unknown> closed its connection.
2024-06-13 08:10:09: New connection from 172.30.32.2:60670 on port 1883.
2024-06-13 08:10:09: Client <unknown> closed its connection.
2024-06-13 08:11:13: Saving in-memory database to /data//mosquitto.db.
2024-06-13 08:12:09: New connection from 172.30.32.2:42752 on port 1883.
2024-06-13 08:12:09: Client <unknown> closed its connection.

I think the problem is not only with MQTT. I’ve now turned off wifi on both my Nuki doorlocks and connected them with Matter to HomeAssistant. My backdoor is running 4.2.8 and hasn’t lost connection once. My front door is still on the latest beta and that one is stilling losing connection to Matter even with wifi and MQTT turned off.

Thank you for the insights. This is interesting.
How did you manager to add it to HA via matter? I have matter enabled, already connected to google home.
Matter server running on HA and integration activated, however, when adding the device to HA from the google home app, it runs for one minute telling me that the device is being added, than it fails.
I am new to Matter, and it be that I am overseeing something. Do you have any advice?