cosmetic defects nuki smart lock 3.0 pro?

[pilot1981]

Hi, I see two strange things:

• undefined NUKI LOCK state
• please configure PIN in credentials

these are related to some misconfiguration? I alreadey tried to insert PIN code, but warning don't go away....

unlock function seems to works fine...

[pilot1981]

After this adventure #176 today I'm also seeing this (randomly for two ESPs which have been erased and flashed with Nuki hub 8.22 and paired with different smart locks). PIN has been provided already plenty of times.

Are certain types of PINs problematic? Leading zeros or similar maybe? Just an idea.

Clearly a bug introduced somewhere between 8.8 and 8.22 😄

My problems seems related only to Bluetooth performance of ESP32 device

[bcutter]

My orange text is gone now. For now. Don't completely trust it yet, will have a look at it for few days.

[pilot1981]

I'm testing M5 Atom and for now all works fine!

[alexdelprete]

I'm testing M5 Atom and for now all works fine!

Not surprised. :)

[pilot1981]

I'm testing M5 Atom and for now all works fine!

Not surprised. :)

Hi, All worked fine for two days, but today problem come back!

I can flash again debug firmware 8.21 to capture detailed logs?

[alexdelprete]

I can flash again debug firmware 8.21 to capture detailed logs?

You don't need permission to produce a log. Do it. :)

[pilot1981]

ok, this is last info using M5 atom and debug firmware:

NUKI Hub version: 8.19-dbg-1 run: true deviceId: 2551311465 mqttbroker: 192.168.6.31 mqttport: 1883 mqttuser: mqttpass: mqttlog: true lockena: true mqttpath: ingresso openerena: false mqttoppath: maxkpad: opmaxkpad: mqttca: mqttcrt: mqttkey: hassdiscovery: homeassistant dhcpena: true ipaddr: ipsub: ipgtw: dnssrv: nwhw: 1 nwhwdt: 26 rssipb: 60 hostname: ingresso nettmout: -1 restdisc: true resttmr: -1 rstbcn: 60 lockStInterval: 1800 configInterval: 3600 batInterval: 1800 kpInterval: 1800 kpEnabled: false regAsApp: false nrRetry: 3 rtryDelay: 100 crdusr: crdpass: pubauth: false gpiolck: false pubdbg: false prdtimeout: 60 hasmac: false macb0: macb1: macb2: MQTT connected: Yes Lock firmware version: Lock hardware version: Lock paired: Yes Lock PIN set: Yes Lock has door sensor: No Lock has keypad: No Network device: Built-in Wifi Uptime: 0 minutes Heap: 90844 Stack watermarks: nw: 6072, nuki: 456, pd: 272 Restart reason FW: NotApplicable Restart reason ESP: ESP_RST_POWERON: Reset due to power-on event.

it worked fine for 2 days (only when NUKI smart lock PRO 3.0 WIFI was disconnect). log.txt

[pilot1981]

I have the same problem with 3.0 pro. It seems that the problem occurs when connecting wifi, otherwise it works.

Hi, I notice this firmware worked fine for me when NUKI SMART LOCK 3.0 PRO have WIFI disconnected.

I connected and disconnected again WIFI, but I’m unable to replicate the problem…you can help me? I suppose this isn’t related only to WIFI disconnection… @likeyou83

[pilot1981]

sorry for delay: I come back with some news.

Nuki support authorized an RMA: so now I installed a new Nuki smart lock 3.0 PRO! but nuki hub using ESP32 have same problem with bluteooth!

I can confirm what @likeyou83 said: NUKI SMART LOCK 3.0 PRO is unable to mantain both active connection with bluetooth nuki bridge and built WIFI connection. I go to investigate it with NUKI support.

Anyone here with NUKI SMART LOCK 3.0 PRO can share its experience?

@alexdelprete @technyon I see a strange behaviour; when Nuki smart lock 3.0 PRO is disconnected from WIFI network, I paired ESP32 nuki hub successful and it was able to lock/unlock my door, but I don't see it in user lists of my NUKI smart lock: how It's possibile? I only see my app user...how it's possibile? I don't think app registration mode can solve my problem...

regards

[technyon]

Hi,

"Register as app" isn't really recommended to use. I just wanted to if it fixes the problem of the lock loosing the ESP. If the ESP is registered as bridge (as in not "Registered as app"), it shouldn't appear in the smartphone app.

[pilot1981]

Hi,

"Register as app" isn't really recommended to use. I just wanted to if it fixes the problem of the lock loosing the ESP. If the ESP is registered as bridge (as in not "Registered as app"), it shouldn't appear in the smartphone app.

ok, thanks for explanation!

you can confirm NUKI SMART LOCK 3.0 PRO is unable to etablish correct communications with both nuki hub (via bluetooth with ESP32) and wifi network (via built-in WIFI interface) at the same moment? this could explain behaviour of my installation...

regards

[pilot1981]

there in answer from NUKI:

https://developer.nuki.io/t/problem-to-use-at-same-time-bluetooth-and-wifi-interface-of-nuki-smart-lock-3-0-pro/20981/3

so I can use Technyon with NUKI SMART LOCK 3.0 PRO only if I go to switch OFF built-in WIFI adpter!

@technyon you can find a workaround for this?

[alexdelprete]

so I can use Technyon with NUKI SMART LOCK 3.0 PRO only if I go to switch OFF built-in WIFI adpter!

No. Jurgen says the wifi turns off automatically when you pair the bridge. But it seems that's not happening with the SL3 Pro.

[mundschenk-at]

Also there are differences between the BLE API responses. This is an intentional part of their API. If you want to use Nuki Hub as a bridge, you need to register it as such.

[pilot1981]

Also there are differences between the BLE API responses. This is an intentional part of their API. If you want to use Nuki Hub as a bridge, you need to register it as such.

you are suggesting to use feature "registered as app " in nuki huib to solve it? already tried, not solve my problem!

[mundschenk-at]

No, I am suggesting that that setting causes problems and you should NOT use it.

(Apparently Nuki also does not want you to use the builtin WiFi together with their bridge, so it is likely that WiFi+NukiHub has issues too.)

[alexdelprete]

you are suggesting to use feature "registered as app " in nuki huib to solve it? already tried, not solve my problem!

Why do you have the wifi turned on? I still can't understand what you are trying to achieve. Please explain what you want to do.

I'm also suspecting that when you paired the ESP, wifi was turned automatically off (like Jurgen explained) but after 2 days you turned it on manually, and you started having problems again.

[alexdelprete]

You can't have both: either you use wifi or you use a bridge (that uses wifi on its own).

So the problems are most probably created by you, manually enabling wifi AFTER the pairing.

It makes NO SENSE having both. If you have a bridge, it is responsible to manage the lock through BLE. If you don't have the bridge, the SL3 Pro will use its internal wifi to be managed through the app.

These are your only options, period. Is it clear now? :)

[alexdelprete]

Official answer from Nuki devs:

So, keep the wifi turned off, or it won't work.

Issue can be closed now.

[pilot1981]

you are suggesting to use feature "registered as app " in nuki huib to solve it? already tried, not solve my problem!

Why do you have the wifi turned on? I still can't understand what you are trying to achieve. Please explain what you want to do.

I'm also suspecting that when you paired the ESP, wifi was turned automatically off (like Jurgen explained) but after 2 days you turned it on manually, and you started having problems again.

For reliability purpose I would obtain to have 2 way to control NUKI SMART LOCK 3.0 PRO:

• via Bluetooth using NUKI hub
• via WIFI using built in WIFI

So, if something fails I can use other way to control NUKI SMART 3.0 PRO!

[pilot1981]

Official answer from Nuki devs:

So, keep the wifi turned off, or it won't work.

Issue can be closed now.

Ok I suggest to add this information in wiki, so anyone can know it…

[technyon]

I'm glad NUKI finally clarified that this is by design. I've added the information to the readme, and I think the issue can be closed.