It is not yet possible to do that through the app. There is only a fixed credentials mode in the firmware, but there is a tutorial in the MQTT api docs how to set this up:
hi! i also have some drain issues with my SL3.0 PRO.
Im using the web connection to manage the airbnb. I know it is not what you are doing, but did it solve the issue after you disabled the web interface?
im planning to disable the web connection if this would solve the battery drain issues
In the lock itself I left the web connection enabled, just to be able to control the lock from the internet with the app. But I disabled the Openhab binding and removed the API connection from the web API. I went from 1,5 week battery to about 3 to 6 months I estimated, with MQTT enabled. Both my locks are still not empty so itâs a rough guessđ
1 Like
ok, in my case it sounds like i need to disable the nuki web and also the airbnb connection to achieve a similar battery improvement then. I will try for a few weeks to disable it to see if it improves the battery drain issue. To bad cause they even sell this airbnb connection as a 69âŹ/ year and it is buggyâŠ
Yeah, I think thatâs the only option. The Web API does poll a lot and keeps the lock awake.
I also had another problem, couple of days I suddenly had massive drain (40% in 2 days). Problem was with my Wifi. I own 2 Asus mesh routers. I linked one of the locks to one of the routers, but forgot the other one. At first this wasnât a problem but suddenly it drained, I think the lock began to switch between the two routers and was waking up all the time because of this. I linked the lock to one of the routers and the problem was gone. Web API was disabled on both locks when this happened.
Must say, MQTT is perfect and causes no drain. Maybe itâs not an option for you, but if itâs possible, I would look in to it. The Android beta app now has the option to configure MQTT from the app. And I think iOS also has this option available.
I do have 2 routers with the same SSID. Mine are both Apple airport extreme. One of the routers is 1meter from the lock while the other is around 15meters.
The battery on my nuki drains 100% in around 5 days, it started 1 month after i enabled the airbnb management.
What is super annoying in my case is that when the battery is drained for letâs say 5 days, the NUKI will loose some of the configuration. Eg: the name is gone, the PIN wonât work anymore ant it thinks it is connected to a door sensor.
the solution is to factory reset and make a new setup with new PIN, new users, setup the keypad again. Such a pain.
I have posted a configuration example using MQTT with a Pro lock without a bridge. Maybe this is relevant for you all: Configuration example for Nuki 3.0 Pro Lock working with the MQTT API (no bridge)
Hi everyone,
after the Nuki Cloud failed yesterday,
I became painfully aware that the Nuki 3.0 Pro with MQTT is not a complete local solution so far. :-/
The Nuki reconnects wifi all the time if it canât connect to the cloud, to âfixâ possible network problems.
As a result, the MQTT connection (which should actually be a completely local control solution) no longer works.
This doesnât just affect cloud outages at Nuki.
You also have this problem if you have internet disruptions or if disable internet access for the smart lock in the router.
Anyone who is affected (or simply bored ;D) is therfore very welcome to vote on this feature request in the Nuki forum:
In addition, you are also invited to leave a comment that this behavior is really annoying 
.
I really hope that the problem will be addressed if enough âattentionâ is paid to it.
They had the same problems with the bridge at the beginning, where the local HTTP API also caused problems.
The Wifi reconnecting was replaced by a check to see if the default gateway (which is likely to be the router / DHCP server for most people) is reachable iirc.
If the default gateway is reachable, the bridge is happy and does not reconnect wildly.
Hopefully this will be solved similarly for the 3.0 Pro âŠ
2 Likes