Nuki 4.0 PRO stops responding to MQTT

Hello fellow Nukers,

I have the same issue as reported by someone else with my Nuki 4 PRO and MQTT (After few days, my Nuki 4.0 PRO don't respond to MQTT command).

MQTT usually runs smoothly, however, very randomly and for no apparent reason, Nuki stops receiving any command via MQTT

If locked/unlocked via its native app, everything works with no issues.
However, I need this to be rock solid via HASS/MQTT due to home automation actions.

Nothing seems to restore the connection, but rebooting Nuki itself by reinserting the battery pack. What makes it even stranger is that SOMETIMES, it restores the MQTT connection randomly in the same way it stopped!

Nuki firmware 4.2.8

Thanks

This ist most likely caused by WiFi connectivity issues.

To troubleshoot the WiFi connection please follow this guide: Smart Lock WiFi/Thread/MQTT connection troubleshooting / FAQ

Based on what you’re making such a statement??

The site is served by a self healing Meraki infrastructure with 8 APs where the ONLY device with MQTT issues is Nuki and you’re suggesting that a 50K infrastructure is the problem? Laughable :rofl:

I have the same issue with mqtt and my SL4 Pro.
Using a Unify Network with controller, the Nuki has it‘s own VLAN (because of limiting the broadcast domain) routing the traffic over a firewall to the mqtt broker.
No connectivity issues, the wifi and all the other stuff working fine but at some point the mqtt connection tears down and nuki doesn‘t trigger a mqtt tcp reconnect on it‘s own.

@Mario:
As a certified network engineer i‘m allowed to say:
Go ahead, blame the network :rofl::rofl: (it‘s my daily business to handle these kind of incidents)

:rofl::rofl::rofl:
I cannot reveal what’s my role in networking but I’m with you brother, something’s broken? Just blame the network and you’ll get away with it!! :rofl::rofl::rofl:

Seriously now, Nuki needs to get their s@#t together and vet their code thoroughly. MQTT is a super simple yet robust protocol and it shall not be like finding an hairpin into the haystack for them to resolve this issue.

Without a reliable MQTT support, applications for this device are drastically reduced to single households.

#lackofbusinessvisionifyouaskme

Please give the latest beta firmware a try and post your findings in the topic for the firmware you are running. Please also DM me the Nuki ID of your lock once you have the beta up and running.

If you do not want to join the beta, please contact our support via the Nuki App (Menu > Help > Contact Customer Support) in order to report problems. They will be gathered and forwarded to the development team.

Being the OP, is this applicable to myself as well @Juergen ??

I don‘t have any issues for month.

Sure. Following the advices in the FAQ, running the beta and sending me the Nuki ID are both applicable for you as well.

hi,
same here, after a time ( 5-15mins or more or less) open / lock / unlock commands are delayed by up to 1 minute

Nuki firmware 4.2.8

keeps disconnecting from mqtt

1717758200: Client mqtt-explorer-026215a5 disconnected.

1717759024: Saving in-memory database to /mosquitto/data//mosquitto.db.

1717759113: Client Nuki_**** closed its connection.

1717759119: New connection from 10.10.1.214:55610 on port 1883.

1717759119: New client connected from 10.10.1.214:55610 as Nuki_**** (p2, c1, k300, u’mqtt’).

1717759474: Client Nuki_**** closed its connection.

1717759480: New connection from 10.10.1.214:51463 on port 1883.

1717759480: New client connected from 10.10.1.214:51463 as Nuki_**** (p2, c1, k300, u’mqtt’).

1717759834: Client Nuki_**** closed its connection.

1717759840: New connection from 10.10.1.214:55198 on port 1883.

1717759840: New client connected from 10.10.1.214:55198 as Nuki_**** (p2, c1, k300, u’mqtt’).

1717760194: Client Nuki_**** closed its connection.

1717760200: New connection from 10.10.1.214:59491 on port 1883.

1717760200: New client connected from 10.10.1.214:59491 as Nuki_**** (p2, c1, k300, u’mqtt’).

1 Like

same with 4.3.4 Beta… it took 1 Minute to open the door,
keeps disconnecting… and sometimes he stays disconnected…

Since i installed last beta, (about 1 month ago) i havent any issue.
Also i have:
1)resetted the lock
2)deleted the mosquitto log and db file
It works well, no issue, no problem, like a charm

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.