- I have the button disabled, so that won’t work.
- I can try that the next time. So far I’ve been able to use MQTT to lock it again.
No. No and another time no.
There are about 12 different people in this discussion complaining about problems with MQTT and WIFI.
Do they all have probelms with the router?
In my case I have many devices connected in MQTT, but the only one that keeps getting unreachable is always just nuki.
In addition, I have connected the lock to the power (with cable) and set the power saving to FAST…
And it doesn’t change much, every once in a while the connection will drop and then NOT reconnect.
If I have problems with WIFI how come the only device to go unavailable is always only NUKI?
How come Nuki never tries to reconnect on its own?
How come Nuki when you enter MQTT settings then miraculously reconnects ?
1 Like
Dear Jürgen,
In my case:
-
No. The lock does not react by pushing the button or via the app. I keep stay in the unlatch/open position till I’ve removed the battery pack.
-
Yes, the lock and the app are reachable via Bluetooth. But as mentioned above, it doesn’t react on any command sent via the app.
Cheers,
Emanuel
- For me it works when you press the button
- Haven’t checked. Will do next time it happens
OK, new problems:
Some background: my Wifi network is based on TP-Link Omada; last week I upgraded my 3 EAP225 access points with one EAP653 and two EAP613 access points. The network configuration itself has not changed (SSIDs, Authentication etc). I have a few SSIDs and my Nuki was always connected to my “main” SSID, which is a 2.4G+5G mixed network. I’ve had no problems with the Wifi connection itself so far.
- Yesterday, Tuesday, morning my lock said it needed the battery recharged (after about 1.5 months)
- I removed it and charged it for several hours
- In the afternoon, I placed it back, only to find that the lock would not connect to the Wifi, no matter what I tried. I managed to connect it quite easily to a secondary SSID, which is 2.4G only, as opposed to my “main” network, which is mixed
- Since then, I’m having constant MQTT disconnections and even a few Wifi disconnections (where the lock shows as connected only via bluetooth in the app)
Why on earth did the lock’s behavior change, just because the battery was recharged and it stayed offline for a few hours?
P.S. I have 52 Tasmota devices in my network, as well as several others, none of which have this kind of problems
It jumps between APs (Channel 1, 6). Last week it was constantly on channel 1.
You might try to set battery saving to fast as suggested in the FAQ
I’ve already done that. Still disconnects every couple of minutes.
Where did you see this? My Omada logs don’t indicate anything like that.
Anyway, I just reset the lock to factory settings and set it up from scratch again. Seems better now. Will report back.
24h have gone by, no disconnects so far.
Since i installed last Fw and resetted the lock, It works well. Any issue. Wifi+mqtt. It Is working from 10-15 days.
I set a static ip in my router and i set the battery savigny to auto
For the second time now I have seen my battery go from 80% to 25% in one day. The unit is pretty much new, have only charged the battery once. Last time I charged it for a few minutes and the battery was back to 100%. Could this be the beta firmware? Or maybe a defective battery pack?
1 Like
Got this three times since I started using HomeAssistant this march even with the official 4.2.8 firmware. So this is not a beta problem. for me, it looks like a mqtt problem because this only started after I started using mqtt.
Here we go again. After some weeks of stability (no battery drain and no forever unlatched bug) suddenly these issues reappear. I had the forever unlatched issue three times in two days and the next day after that the battery started draining again. Nothing changed in my network or with the Nuki firmware which is still on Beta 4.3.4. I’m not experiencing other networking issues as described by other users in this thread. I have the device connected over MQTT which is working as expected.
A acknowledgement of Nuki regarding the forever unlatched and battery drain would be appreciated though.
And the same pattern repeats after this:
- I pull the battery and insert it again
- The battery level is much higher (now 47%)
- The first unlock after having pulled the battery results in the motor blocking during unlatch, similar to the forever unlatched issue but now because the motor blocks
- This block cant be resolved by re-opening the door which works as a work-around for the forever unlatched issue
- I need to manually adjust the button and recalibrate the lock to get it working again
- After this the percentage drops down to the value before I pulled the battery
I can reproduce this process.
Same here. Issues started since yesterday. Is this cloud related or just coincidence?
I mentioned already some time ago, that we’re looking into it. There is no update as of now, mainly because we still could not reproduce it (both the forever unlatch and the drain).
And here we go again. Today, my lock has gone offline, i.e. no wifi connection, twice. It came back online 7 hours later, by itself the first time.
THIS PRODUCT IS COMPLETELY UNRELIABLE.
1 Like
to reproduce it, you’ll have to enable MQTT, AND use MQTT to control the lock from time to time!
If you still cannot reproduce it, make it 10 test scenarios with 10 different systems.
Wifi offline again. Does Nuki care about this?
