Same anoyning issue here !
After almost a day with the new firmware, on HA indeed looks better regarding availability but it’s not working fine.
When I issue commands via MQTT, 90% of them just never happen and the rest, they may do with random delay from couple of seconds up to minutes.
Imaging arriving at home, try to open with nuki, doesn’t work so you use your key. After couple of minutes when you’re in the bathroom, nuki opens the door letting the cats out. 
(true story, waf is about to end on divorce. Pablo, you can ping me when read this)
Complaining doesn’t help, but what else I can do?
I do not have any access to see what’s going on, and it happens to a subset of user, widely and variant subset, not just one with a crappy conection. It’s not me, my device or my setup.
Is there any template to fill with useful info to help development to fix this?
Is there any way to downgrade to old firmware? It was working flawless until firmware upgrade.
To be honest, I bought a product, not a position as nuki beta tester 
I think I recognize Home Assistant.
Do you track your phone with Companion ?
I am currently on 3.10.0 and want to update to 3.10.1. But always when I try to update I get the message, that I need to be within bluetooth range. I am only 1 meter next to the lock but it does not connect via bluetooth. Also the connection view shows no direct connection between my phone and my smartlock.
Try the steps mentioned in the FAQ if you have not done that yet:
For me it does not matter which battery preference I use. With FAST I have the identical outages. Before 3.9.5 I had no WiFi connection errors and also no MQTT problems.
Yeah, I did follow all those steps, plus some more provided by customer service such us use another access point or even my phone etc, etc…
That was months ago already.
I even tested to have nuki wall powered all time, didn’t work.
To be honest, I’m pretty sure that there is some casuistic between nuki and particular wifi/network flag. But when all my other devices, ranging from crappy chiniese stuffs to firs class brands, work totally fine, I cannot look to another direction but the lock.
Even more, when it worked fine until firmware upgrade
And I also think it is more a WiFi connection problem then a MQTT problem.
Few seconds ago both of my locks had a WiFi connection. Now one of my locks is gone…
Edit:
On my router device I can see several disconnection log’s like [MAC]@WiFi-SSID disconnected, connection lost, signal strength -57
agreed
I do not check anymore, but I saw that when nuki was unavailable on HA, it was too via NukiWeb.
I will try to setup a kurma monitor, just to have that info
Try to use the IP-Adress of your mqtt and not the DNS-name to minimize dns-routing delays or failures. Since 3.9.5 it works pretty stable and commands are always within 1 Second executed. The only thing is the long delay for mqtt-reconnection after a wlan-reconnect .
Good point, but I was always using local IP as MQTT address.
Now, after some time monitoring the nukilock ping responses, I can see it is still disconnecting randomly.
Something I noticed is that the shorter is the cycle (now on every 20s) the less times it fails. Keeping pinging the lock every 20s makes it almost usable.
So as we all suspected, must be something with the wifi energy savings.
Could be posible to release a beta with the option to totally disable energy savings? for testing purposes.
Good evening everybody,
today was a very rainy sunday and because the WiFi/MQTT problem really annoys me, I set-up a clean and tiny test environment:
- 2x NUKI Pro 3.0 locks with battery option FAST
- 1x clean Home Assistant instance for testing the MQTT connection (NUKI connected via IP) and also observing the availability of the two locks. I also setup the Nuki Lock integration for connecting to the devices via NUKI WEB API.
- 1x clean network with direct internet connection. In this network we only have the Access Point, the two NUKI locks and the Home Assistant instance as physical device.
What I got:
The same annoying WiFI and MQTT non-availability as in my normal network. Everytime the device were shown as not available in Home Assistant, no communication was possible (not via MQTT and not via NUKI WEB API). Via iPhone App it was possible to see the connection status: Bluetooth. That means that all your energy saving functions or improvements are useless and causes all the problems we have since software version 3.9.5. With my test environment of today, I also can’t trust all the statements here in the forum that speak of a flawless uptime since software version 3.10.1 - either these statements are not true, or they use some kind of magic, which I as a software developer do not believe in.
So dear NUKI developer team: what specific information do you need for bug-fixing these issues. Is a rollback to the old software functionality imaginable? With this, we could test all your “energy saving functions and improvements” step by step?
Otherwise I’ll have to start believing in magic and contact Nuki support. Apparently both of my locks are broken, since there are devices that work flawless with 3.10.1.
Regards,
Kevin
PS: Using the Home Assistant NUKI Lock integration for using the NUKI WEB API is totally useless. Since there is always the last status shown - with this you never can see when the device was not available. 
3 Likes
It´s still not working with this latest firmware for me either, maybe who says it was fixed, share the info to compare. The problem is, Nuki don´t allow us to know much.
btw, I did a very similar scenario (not so clean tbh) but with the same results.
Could you try to add something else?
Add a machine/HA/vm/something, pinging nuki local ip every second. Check if with that active the whole time, it changes something
I have setup a ping every second to both of my devices. Tomorrow I will share the results.
1 Like
Here we go… with pinging the NUKI lock it is not possible to keep it online. It is also nice to sse that the MQTT status still exists for some time (few minutes) before it is reset by timeouts.
This corresponds to my previous finding from the WiFi log, that it seems that the NUKI lock does not log off correctly before going into some kind of sleep mode to save battery. I think the NUKI lock does not send any association request frame when saving battery to the WiFi AP to keep its authenticated status before its authentication timeout expires - or the timings are to tough for saving more battery as in the previous software versions (earlier as 3.9.5).
This is not what’s going on. I’ll send you a DM with more informations.
There was no change in regards to this from 3.8.x to 3.9.x or 3.10.x.
I am still not able to update from 3.10.0 to 3.10.1
I enabled the auto update and it does not work and I also tried directly to trigger the update and it does not work. I klick on “update now” and then I get: “Um die Firmware deines Smart Locks zu aktualisieren, musst du dich in Bluetooth-Reichweite befinden.”
Why is it not possible to update my smart lock?
hello,
Is there some known issue between FOB and 3.10.1?
My FOB seems to be connected (as per the Nuki Android app) but pressing the button do nothing…
Hi,
any idea, when a Fixed Firmware will be released?
It is now more than one month ago, when the MQTT problems appeard for near all (perhaps all) NUKI 3 Pros.
I hope that it will be solved soon, because the trust in Firmware upgrades is near gone for me.
I was asked to upgrade Firmware of Keypad. But I have not installed immediately, because I somehow didn’t trust the Firmware updates anymore 100%.
As we see, the problem is, that problems, which will come in, will not immediately be solved 
, which show, that it would be better to wait several month, before installing Firmware update.
I have seen, that question was already raised. Why it is not possible to roll back to previous version before 3.9.5? Everything was fine with older Firmware.
Is there any way to rollback?
BR
Thomas
3 Likes