Cannot connect to the smartlock about nuki_hub HOT 107 CLOSED

Hi,

thanks for feedback. Maybe it's time to compile a list of recommended hardware ... still I have no explanation really and without being able to reproduce the issue it's really hard to fix. At least I can give the advice to try a different board now.

from nuki_hub.

Again, with DEVKITV1, for me, was not possible to pair with Nuki...but with my new ESP32-WROOM-32D DEVKITV4 it works good, at least lock, unlock and door state......Now I have to try open

Finally, I could link ESP32 with Home Assistant...I had to install again and put homeassistant in "Home Assistant discovery topic" before to pair the first time...I don't know why when Nuki was paired without homeassistant link and tried to configure it didn't work...

Hello Sergio, could you send exactly the model of the working board please

Hi, yes...at the beginning I was trying with ESP-WROOM32...Now with ESP32-WROOM-32D DEVKITV4

Do you have a link?

https://es.aliexpress.com/item/4000089201026.html?spm=a2g0o.order_list.0.0.21ef194db9a7f7&gatewayAdapt=glo2esp

from nuki_hub.

Only the Nuki Pro has built-in WiFi, for anything else you need some kind of bridge (official, Nuki Hub, ...).

Let's please keep the conversation on-topic.

from nuki_hub.

Now I have a working Nuki. Pairing is done.

Yesterday I resetted the Nuki multiple times with and without pairing with the app first.
Today I paired my Nuki again with the app, checked "Settings --> Features & Configuration --> Button & LED --> Bluetooth Pairing", disabled the paring option, reenabled it again and then I tried to pair my Nuki with nukihub running on my DevKitC_V4 ESP32 device. Worked well immediately.

Nuki start pairing
Nuki start pairing
Nuki paired
Nuki lock state: unlocked
Reading config. Result: 1
Reading advanced config. Result: 1

So for me it is working. And I can confirme ESP32-WROOM-32D (DevKitC_V4) is a working ESP device.
But it's not clear for me if it was the disabled/enabled pairing option or the pairing with the app itself.
Is it a requirement to connect the Nuki first to an app or the bridge before pairing with nukihub?

from nuki_hub.

I tried to register as an app (I was using bridge mode first) but the issue persists.

from nuki_hub.

Did you pair your smartphone already?

from nuki_hub.

First yes the smartphone was paired to the smartlock
It was not after the factory reset

from nuki_hub.

ok, just asking to make sure pairing in general is working.

It's hard to tell, usually it just works. How close is the ESP to the lock?

from nuki_hub.

They are literally separated by 5cm, I unmounted the doorlock from the door to put in just near the ESP32
I was using this ESP32 to control an other doorlock just before so the ESP32 bluetooth should be working
I tried also:

• A previous version of nuki hub (5.15)
• A second ESP32
• A second Nuki 2.0 which has not been updated for at least 1 year ago

It still won't connect sadly.

from nuki_hub.

I'm somewhat out of ideas ... I'd have to add some log messages to see what's really going on.

from nuki_hub.

Ok, thank you.
From my side, I ordered a different model of my current ESPs to see if it can the responsible of this issue.

from nuki_hub.

Please try with the attached firmware and send logs. When flashed the version string is "6.0-dbg-connect".

nuki_hub-dbg-connect.zip

from nuki_hub.

Thank you
This log in loop mode:

Nuki start pairing
[ 90784][D][NukiBle.cpp:102] pairNuki(): No nuki in pairing mode found
[ 90785][D][NukiBle.cpp:107] pairNuki(): pairing result 0

Nuki is in pairing mode (and it connects to my smartphone or to my FOB within second when I enable the pairing mode on Nuki smartlock, the smartlock bluetooth works fine)

Some info from my current ESP:

Detecting chip type... ESP32
Chip is ESP32-D0WD-V3 (revision 3)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz

from nuki_hub.

Oh, new logs:

[289304][D][NukiBle.cpp:102] pairNuki(): No nuki in pairing mode found
[289305][D][NukiBle.cpp:107] pairNuki(): pairing result 0
[294285][D][NukiBle.cpp:229] onResult(): Found nuki in pairing state:  addr: xx:xx:xx:xx:xx:xx
Nuki start pairing
lld_pdu_get_tx_flush_nb HCI packet count mismatch (1, 2)
[302732][W][NukiBle.cpp:138] connectBle(): BLE Connect failed, retrying
[332746][W][NukiBle.cpp:138] connectBle(): BLE Connect failed, retrying
[362759][W][NukiBle.cpp:138] connectBle(): BLE Connect failed, retrying

I already saw this error "lld_pdu_get_tx_flush_nb HCI packet count mismatch (1, 2)", it was related to the poor bluetooth connection.
Did you max the bluetooth range power currently from the ESP32?

I cannot make the ESP32 closer to the smartlock, they are already together...

from nuki_hub.

The error packet count mismatch comes from the bluetooth stack, but is normal, it happens sometimes.

Your ESP somehow has problems though with bluetooth communication. In the first log, it didn't receive the iBeacon from the lock, in the second it tried to connect but failed, so the pairing process wasn't initiated.

Why this is happening is hard to tell. I'd try another ESP as you suggested. No point in meddling with bluetooth parameters, the first log is about receiving a beacon, and there's no way to improve reception from software side, you'd need to change the antenna ... that's not the problem here.

from nuki_hub.

Had the same Problem ... I paired it with the App, selected Configure Bridge, powered on the ESP32 and pushed the button for 10 seconds (The light started after about 5 seconds) ... The App told "success" and the Web Interface of the ESP32 told "Paired"

from nuki_hub.

@technyon here are my logs
esp-web-tools-logs.txt

I set my lock to paring mode, and the esp just got stuck in a Nuki start pairing loop

from nuki_hub.

It's very strange ... I just unpaired my lock and paring worked immediately. I've compiled the latest firmware with enhanced logging, can you give it a try? When successfully flashed, the versions reads "6.0-dbg-1".

nuki_hub-dbg.zip

from nuki_hub.

It's very strange ... I just unpaired my lock and paring worked immediately. I've compiled the latest firmware with enhanced logging, can you give it a try? When successfully flashed, the versions reads "6.0-dbg-1".

nuki_hub-dbg.zip

how do I flash this ver?

from nuki_hub.

Same issue here, can't pair.

• Previously I have been using RaspiNukiBridge (https://github.com/dauden1184/RaspiNukiBridge) in a RPI for a long time.
• Nuki Smart Lock firmware 3.3.5 on Nuki Smart Lock 3.0 device.
• Tested with 2 ESP32 devices with same result.
• Tested with nukihub 6.0, 6.0-dbg-1 and 5.15.
• Tested with "register as app" on and off.
• Restored to factory settings the Nuki smart lock.
• Chip is ESP32-D0WD-V3 (revision 3) (from esptool).
• Tested with nuki_hub-dbg-connect.zip from this issue @technyon:

Attempting MQTT connection
MQTT: Connecting without credentials
MQTT connect failed, rc=-2
Free Heap: 112864
Nuki start pairing
[963732][D][NukiBle.cpp:102] pairNuki(): No nuki in pairing mode found
[963733][D][NukiBle.cpp:107] pairNuki(): pairing result 0

(in loop)

• nuki/presence/devices in MQTT is always empty.
• Distance between ESP32 and Nuki about 10 centimetres.
• After a lot of tries, I get this pressing about 30 seconds the Nuki button.

[603449][D][NukiBle.cpp:102] pairNuki(): No nuki in pairing mode found
[603449][D][NukiBle.cpp:107] pairNuki(): pairing result 0
Attempting MQTT connection
MQTT: Connecting without credentials
MQTT connect failed, rc=-2
Free Heap: 112352
[608429][D][NukiBle.cpp:229] onResult(): Found nuki in pairing state:  addr: 54:d2:72:86:2d:ec

But ended with:

[758727][W][NukiBle.cpp:138] connectBle(): BLE Connect failed, retrying

from nuki_hub.

Same as with the logs before, for some reason the ESP isn't picking up the beacon from the lock, so it doesn't initiate the pairing procedure. I have no explanation really, here it just works. I'm on firmware 3.3.5 on a NUKI 3.0 too.

Can you try to enable the presence detection and see if it's reporting anything? If it doesn't wobk try my other firmware:

https://github.com/technyon/blescanner

This just reports beacons from devices in the area. Just to make sure your ESP receives any beacons at all and that bluetooth is working.

P.S.: Just saw that it worked after a lot of tries. Something's up with the bluetooth communication. Using the app on the smartphone works without problems?

from nuki_hub.

how do I flash this ver?

• download a release and unzip it
• replace the nuki_hub.bin in the unpacked release with the debug bin
• follow the instructions in the readme

from nuki_hub.

Same as with the logs before, for some reason the ESP isn't picking up the beacon from the lock, so it doesn't initiate the pairing procedure. I have no explanation really, here it just works. I'm on firmware 3.3.5 on a NUKI 3.0 too.

Can you try to enable the presence detection and see if it's reporting anything? If it doesn't wobk try my other firmware:

https://github.com/technyon/blescanner

This just reports beacons from devices in the area. Just to make sure your ESP receives any beacons at all and that bluetooth is working.

P.S.: Just saw that it worked after a lot of tries. Something's up with the bluetooth communication. Using the app on the smartphone works without problems?

Hi,

Yes, the lock works over bluetooth, I use every day from 2 smartphone and from Raspinuk (https://github.com/dauden1184/RaspiNukiBridge).

I have tested blescanner and the ESP32 doesn't show the Nuki Lock device, but I can see other devices, is strange because with hcitool lescan from a RPI I always receive the beacons from the Nuki.

Thanks!

from nuki_hub.

With this script https://gist.github.com/elliotlarson/1e637da6613dbe3e777c (ibeacon-scan.bash) I can see a lot of beacons every second from a Tesla car ... could be this too much beacons for an ESP32 an is ignoring the Nuki beacons?

Tested the same ESP32 devices with esphome (ble_scanner) and I cannon't find the Nuki lock.

from nuki_hub.

Tested today with other ESP32 boards and worked an paired at the first try:

Nuki start pairing
Nuki paired
Nuki lock state: locked
Reading config. Result: 1
Reading advanced config. Result: 1

The new board is from az-Delivery and the older one with bluetooth problems from DUBEUYEW:

Thanks for your support @technyon, finally was a hardware problem with the ESP32 boards.

from nuki_hub.

Hi, a question...where is the option "register as an app"?

from nuki_hub.

In the configuration portal go to NUKI Configuration, in the advanced section enable the first checkmark.

from nuki_hub.

Thanks...I can not pair with my Nuky 2.o....I have the same broad marked witd "X" in picture above swowed...it is frustrating for me

from nuki_hub.

I have seen logs and it is always showing
Nuki start pairing
Nuki start pairing
Nuki start pairing
Nuki start pairing
Nuki start pairing
Nuki start pairing

from nuki_hub.

@gonzalezcalleja Do you have a link to the DUBEUYEW board? I'd like to add it to the readme as an incompatible board.

@SergioWarriorPeru Try a different board. It seems this one in particular has some issue.

from nuki_hub.

Yeah...but, I would like know why...Maybe it could be the chip ESP32-D0WDQ6....I was surfing to know what is the chip used az-Delivery board...but I have not been successful

from nuki_hub.

Doing a quick google check, it's at least listed as "Not recommended for new designs", which means as far as I understand that there newer revisions available that address potential hardware bugs:

https://www.italki.com/en/teacher/7737037/englishhttps://www.espressif.com/sites/default/files/documentation/esp32_datasheet_en.pdf

Maybe pick one that's not listed as "NRND".

from nuki_hub.

@gonzalezcalleja Do you have a link to the DUBEUYEW board? I'd like to add it to the readme as an incompatible board.

Hi, I only have this amazon link: https://www.amazon.es/gp/product/B0B55MS33L

The board is labeled as "ESP32 DEVKIT V1"

from nuki_hub.

Yeah..I have the same DEVKITV1...I have just ordered a ESP32-WROOM-32D DEVKITV4 ...I will test when it arrive....

from nuki_hub.

@SergioWarriorPeru Please let me know if it works with the new ESP. If you can confirm it works, I'll mention DUBEUYEW boards as not recommended in the readme.

from nuki_hub.

@technyon ...Yeap..but, here (in Peru) orders from Ali Express can take 2 months..so i will be patient...I believe that problem is the version V1...

from nuki_hub.

I got the DevKitV1 board as well, can't pair the lock. I even have 2 of the same unfortunately..
Ordered one with ESP32-WROOM-32E, will report back if it works.

from nuki_hub.

Ok thanks, I'll add it to the readme.

from nuki_hub.

Hello there, I just bought 3 Az Delivery ESP32 WROOM32. Trying on 2 different esp32 and the result is the same: loop on pairing and not found the smartlock.
I have a SmartLock V3. Nothing more with the debug version

from nuki_hub.

Oh, new logs:

[289304][D][NukiBle.cpp:102] pairNuki(): No nuki in pairing mode found
[289305][D][NukiBle.cpp:107] pairNuki(): pairing result 0
[294285][D][NukiBle.cpp:229] onResult(): Found nuki in pairing state:  addr: xx:xx:xx:xx:xx:xx
Nuki start pairing
lld_pdu_get_tx_flush_nb HCI packet count mismatch (1, 2)
[302732][W][NukiBle.cpp:138] connectBle(): BLE Connect failed, retrying
[332746][W][NukiBle.cpp:138] connectBle(): BLE Connect failed, retrying
[362759][W][NukiBle.cpp:138] connectBle(): BLE Connect failed, retrying

I already saw this error "lld_pdu_get_tx_flush_nb HCI packet count mismatch (1, 2)", it was related to the poor bluetooth connection. Did you max the bluetooth range power currently from the ESP32?

I cannot make the ESP32 closer to the smartlock, they are already together...

Did you solve the problem ? I have exactly the same scenario, sometimes I have nuki detected but BLE connect failed after

from nuki_hub.

New ESP32 have arrived today and I have paired with Nuki (ESP32-WROOM-32D DEVKITV4)...but, I can not to integrate with Home Assistant...I have put homeassistant in Home Assistant discovery topic...but my HA can;t see it

Logs are:

Restarting
*wm:[2] [EVENT] WIFI_REASON: 8
ets Jun 8 2016 00:22:57

rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0030,len:1344
load:0x40078000,len:13516
load:0x40080400,len:3604
entry 0x400805f0
Network device: Builtin WiFi
MQTT without TLS.
*wm:[1] AutoConnect
*wm:[2] ESP32 event handler enabled
*wm:[2] Setting Hostnames: nukihub
*wm:[2] Setting WiFi hostname
*wm:[2] Connecting as wifi client...
*wm:[2] setSTAConfig static ip not set, skipping
*wm:[1] Connecting to SAVED AP: GWIFI
*wm:[1] connectTimeout not set, ESP waitForConnectResult...
*wm:[2] Connection result: WL_CONNECTED
*wm:[1] AutoConnect: SUCCESS
*wm:[2] Connected in 1034 ms
*wm:[1] STA IP Address: 192.168.86.66
WiFi connected: 192.168.86.66
Host name: nukihub
MQTT Broker: 192.168.86.27:1883
NUKI Lock enabled
Lock state interval: 1800 | Battery interval: 1800 | Publish auth data: no
NUKI Opener disabled
Presence detection timeout (ms): 60000
Attempting MQTT connection
MQTT: Connecting with user: sergio
MQTT connected
Nuki start pairing
Nuki paired
lld_pdu_get_tx_flush_nb HCI packet count mismatch (1, 2)
lld_pdu_get_tx_flush_nb HCI packet count mismatch (1, 2)
Unable to setup HASS. Invalid config received.
lld_pdu_get_tx_flush_nb HCI packet count mismatch (1, 2)
Reading config. Result: lld_pdu_get_tx_flush_nb HCI packet count mismatch (1, 2)
3
Reading advanced config. Result: lld_pdu_get_tx_flush_nb HCI packet count mismatch (1, 2)
lld_pdu_get_tx_flush_nb HCI packet count mismatch (1, 2)

from nuki_hub.

New ESP32 have arrived today and I have paired with Nuki (ESP32-WROOM-32D DEVKITV4)...but, I can not to integrate with Home Assistant...I have put homeassistant in Home Assistant discovery topic...but my HA can;t see it

Logs are:

Restarting

*wm:[2] [EVENT] WIFI_REASON: 8

ets Jun 8 2016 00:22:57

rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)

configsip: 0, SPIWP:0xee

clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00

mode:DIO, clock div:1

load:0x3fff0030,len:1344

load:0x40078000,len:13516

load:0x40080400,len:3604

entry 0x400805f0

Network device: Builtin WiFi

MQTT without TLS.

*wm:[1] AutoConnect

*wm:[2] ESP32 event handler enabled

*wm:[2] Setting Hostnames: nukihub

*wm:[2] Setting WiFi hostname

*wm:[2] Connecting as wifi client...

*wm:[2] setSTAConfig static ip not set, skipping

*wm:[1] Connecting to SAVED AP: GWIFI

*wm:[1] connectTimeout not set, ESP waitForConnectResult...

*wm:[2] Connection result: WL_CONNECTED

*wm:[1] AutoConnect: SUCCESS

*wm:[2] Connected in 1034 ms

*wm:[1] STA IP Address: 192.168.86.66

WiFi connected: 192.168.86.66

Host name: nukihub

MQTT Broker: 192.168.86.27:1883

NUKI Lock enabled

Lock state interval: 1800 | Battery interval: 1800 | Publish auth data: no

NUKI Opener disabled

Presence detection timeout (ms): 60000

Attempting MQTT connection

MQTT: Connecting with user: sergio

MQTT connected

Nuki start pairing

Nuki paired

lld_pdu_get_tx_flush_nb HCI packet count mismatch (1, 2)

lld_pdu_get_tx_flush_nb HCI packet count mismatch (1, 2)

Unable to setup HASS. Invalid config received.

lld_pdu_get_tx_flush_nb HCI packet count mismatch (1, 2)

Reading config. Result: lld_pdu_get_tx_flush_nb HCI packet count mismatch (1, 2)

3

Reading advanced config. Result: lld_pdu_get_tx_flush_nb HCI packet count mismatch (1, 2)

lld_pdu_get_tx_flush_nb HCI packet count mismatch (1, 2)

I was thinking the same but if you go on entities you must find it if you set autodiscover.

from nuki_hub.

@mironalessandro I have looked to entities and I can't find something like nukihub or similar...
I do not understand why "Unable to setup HASS. Invalid config received"...I have reviewed Mqtt client and discovery topic is homeassistant the same I put in ESP32...

from nuki_hub.

Finally, I could link ESP32 with Home Assistant...I had to install again and put homeassistant in "Home Assistant discovery topic" before to pair the first time...I don't know why when Nuki was paired without homeassistant link and tried to configure it didn't work...

from nuki_hub.

Finally, I could link ESP32 with Home Assistant...I had to install again and put homeassistant in "Home Assistant discovery topic" before to pair the first time...I don't know why when Nuki was paired without homeassistant link and tried to configure it didn't work...

Hello Sergio, could you send exactly the model of the working board please

from nuki_hub.

Finally, I could link ESP32 with Home Assistant...I had to install again and put homeassistant in "Home Assistant discovery topic" before to pair the first time...I don't know why when Nuki was paired without homeassistant link and tried to configure it didn't work...

Hello Sergio, could you send exactly the model of the working board please

Hi, yes...at the beginning I was trying with ESP-WROOM32...Now with ESP32-WROOM-32D DEVKITV4

from nuki_hub.

Finally, I could link ESP32 with Home Assistant...I had to install again and put homeassistant in "Home Assistant discovery topic" before to pair the first time...I don't know why when Nuki was paired without homeassistant link and tried to configure it didn't work...

Hello Sergio, could you send exactly the model of the working board please

Hi, yes...at the beginning I was trying with ESP-WROOM32...Now with ESP32-WROOM-32D DEVKITV4

Do you have a link?

from nuki_hub.

Hi,

Although it works now, the error "Unable to setup HASS. Invalid config received." means the configuration couldn't be retreived from the Lock, meaning something went wrong with the bluetooth communication ... not sure though why.

from nuki_hub.

Hi,
Just reveived new board (with ESP32-WROOM-32D chip) and everything work like a charm. So I return my AZ delivery with WROOM-32, I think this chip is not compatible.
NB: My Az delivery board is devkit v2, it would be interesting to know if the devKit v4 is compatible

from nuki_hub.

Hi, Just reveived new board (with ESP32-WROOM-32D chip) and everything work like a charm. So I return my AZ delivery with WROOM-32, I think this chip is not compatible. NB: My Az delivery board is devkit v2, it would be interesting to know if the devKit v4 is compatible

Hi, yes, my ESP32-WROO.-32D is devkit V4 and work well...the only thing that I noted is when I open door in manual way, sometimes doorsensor does not shoew open but closed...I

from nuki_hub.

Well, I ordered ESP32-WROOM-32D DevKit V4 and ESP32-WROOM-32E NodeMCU. 32D did not work at all, 32E did work.
It just may be that either these ESP32 SIP's are the issue or the board manufacturer is the issue, IDK anymore lol

from nuki_hub.

Unfortunately I also have a DEVKITV1 that doesn't connect to the lock :-(
I'm ordering a new one, any suggestions? Thank you

Ps how can I recycle the unused DEVKITV1?

from nuki_hub.

from nuki_hub.

I got the WROOM32-E and it seemed to work
…
On Fri, Nov 25, 2022 at 2:07 PM amastrogiacomo1968 @.> wrote: Unfortunately I also have a DEVKITV1 that doesn't connect to the lock :-( I'm ordering a new one, any suggestions? Thank you Ps how can I recycle the unused DEVKITV1? — Reply to this email directly, view it on GitHub <#39 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB7UYWT5SXU6QOILDQCPPNDWKCTX5ANCNFSM6AAAAAAQX534EY . You are receiving this because you commented.Message ID: @.>

Thank's

from nuki_hub.

I've updated the readme to include known bad boards (devkit v1) and known working boards (32d and 32e).

from nuki_hub.

Az-delivery V2 (photos), not working for me. Some Bluetooth devices not found (Nuki 3.0 with firmware 3.4.10 too). I'm now waiting for the new version (V4) by Az-delivery nex days. Fingers crossed.

Davide

P.s. @gonzalezcalleja can you tell me what is your working (Az-delivery) version? Thank you.

from nuki_hub.

Hi @davide93,

Is V2:

from nuki_hub.

Really strange situation. Same version, but mine doesn't work and stays in the "Nuki start pairing" state. @technyon any advice?
@gonzalezcalleja are you using the 3.4.10 firmware on Nuki 3.0?

Ty.

from nuki_hub.

Can anyone ship a non-working ESP to a german address? Best way to fix it if I can debug where the pairing gets stuck.

from nuki_hub.

Morning all,
Finally I switched from Nuki 2.0 to Nuki 3.0 Pro, this is something I suggest to consider.
I suscribed to the nuki beta program (open to all, you just have to contact the Nuki support and they add you to the program within less than 24H)
With the beta firmware, the smartlock is able to communicate through a local MQTT server using built-in Wifi.
It's super fast compared to the bluetooth version (I'm now able to see the full workflow in real time in my personal app : locked -> unlocking -> unlocked in real time), thanks to push events.
You don't need to have a bridge anymore (official bridge or ESP32 DIY).
I will not go back on a bluetooth-based solution

from nuki_hub.

Morning all, Finally I switched from Nuki 2.0 to Nuki 3.0 Pro, this is something I suggest to consider. I suscribed to the nuki beta program (open to all, you just have to contact the Nuki support and they add you to the program within less than 24H) With the beta firmware, the smartlock is able to communicate through a local MQTT server using built-in Wifi. It's super fast compared to the bluetooth version (I'm now able to see the full workflow in real time in my personal app : locked -> unlocking -> unlocked in real time), thanks to push events. You don't need to have a bridge anymore (official bridge or ESP32 DIY). I will not go back on a bluetooth-based solution

But within a combination of Nuki 3.0 (non-pro) and Nuki Opener you would still need a bridge because neither has built-in wifi, correct?

from nuki_hub.

Hey 👋 I have tested multiple esp's with my nuki 2.0

• 🔴 esp-s2 is not supported
• 🔴 esp-c3 is not supported
• 🔴 esp-wroom-32 (devkitv1) doesn't work (unable to pair lock)
• 🟢 esp32-wroom-32UE works (paired with lock)
• 🟢 esp32-wroom-32E works

from nuki_hub.

Hi there.
I got two more different "ESP" and the result is very strange and doesn't support the hypothesis that V1 doesn't work.

On my side:

🔴 AZ-Delivery V2 doesn't work | Amazon | Photos: card - box | Product page

🔴 newest AZ-Delivery V4 doesn't work | Amazon | Photos: card - box | Product page

🟢 the oldest JZK "V1" (which requires the "boot" button to be pressed when uploading code) worked right away | Amazon | Photos: card - box | Product page

(I may be wrong, but JZK resells DOIT brand products even though neither the JZK nor DOIT brand is listed on the board.)

... but someone has confirmed that AZ-Delivery V2 works.
I almost think there are defective batches? I was surprised that even the new v. 4 did not work and instead v. 1 worked right away.

@technyon I'm sorry but right now I am not able personally to send one of these to you. Anyway, thank you for your amazin work.

from nuki_hub.

Hi,

I tested 3 different ESPs, non is working:

• Espressif ESP32-WROOM-32, Chip is ESP32-D0WD-V3 (revision 3)
  Labeled with "ESP32S" at bottom
  Link

• AZ Delivery ESP32-WROOM-32, Chip is ESP32-D0WD-V3 (revision 3)
  No other labels at board but box was labeled with "DevKitC V2" like here
  Link

• Espressif ESP32-WROOM-32D, Chip is ESP32-D0WDQ6 (revision 1)
  Labeled with "ESP32_DevKitC_V4" at bottom.
  Link

Non of them is working with my Nuki 3.0.
Tested with nukihub 6.0, 6.0-dbg-1, 6.1 and 5.8, 5.15 and a very old 2.6 release.
Tested with "register as app" on and off.
Restored to factory settings the Nuki smart lock.

@technyon: I can send some devices, if needed.

Next I will try on of the posted links here or a 32U.

from nuki_hub.

@Stilzchen Can you pair with the smartphone app?

from nuki_hub.

@Stilzchen Can you pair with the smartphone app?

I tried it yesterday. Yes, connection with app is possible. App made a software upgrade automatically to version 3.4.0 for my Nuki 3.0

from nuki_hub.

Hi,

I tested 3 different ESPs, non is working:

* Espressif ESP32-WROOM-32, Chip is ESP32-D0WD-V3 (revision 3)
  Labeled with "ESP32S" at bottom
  [Link](https://www.amazon.de/gp/product/B07S1GGM35)

* AZ Delivery ESP32-WROOM-32, Chip is ESP32-D0WD-V3 (revision 3)
  No other labels at board but box was labeled with "DevKitC V2" like [here](https://github.com/technyon/nuki_hub/issues/39#issuecomment-1333490521)
  [Link](https://www.amazon.de/gp/product/B071P98VTG)

* Espressif ESP32-WROOM-32D, Chip is ESP32-D0WDQ6 (revision 1)
  Labeled with "ESP32_DevKitC_V4" at bottom.
  [Link](https://www.amazon.de/gp/product/B09LS6SCF7)

Non of them is working with my Nuki 3.0. Tested with nukihub 6.0, 6.0-dbg-1, 6.1 and 5.8, 5.15 and a very old 2.6 release. Tested with "register as app" on and off. Restored to factory settings the Nuki smart lock.

@technyon: I can send some devices, if needed.

Next I will try on of the posted links here or a 32U.

I'm confused.
I tested a while around with my 2 pieces Espressif ESP32-WROOM-32D and all nukihub versions since 5.8.
After having a Wifi connection I always connected my FHEM server via MQTT first. And some seconds later I always get a new reading "devices" where I can see my nuki. Nuki is not in peering mode.

======================================
|devices | 54:d2:72:b8:a0:4d;Nuki_XXXXXXXX;-54 |  <- XXXXXXXX is my confirmed Nuki serial
======================================

So Nuki is there. I can move my ESP32 and then the signal (-54 above) is updated every few seconds.
(Reading "devices" is not coming up in FHEM if I use the other to ESP32).

Starting pairing mode at Nuki I get no Pairing effort. :/

from nuki_hub.

That's at least a good sign, it does receive beacons from the lock. There are two kind of beacons though, to initiate pairing it needs to receive beacons from the "pairing service", which are only sent when the lock is in pairing mode.

Stupid question, but did you double check you're doing everything right? It's possible to disable pairing via the button from the app, can you double check it's not set. When you long-press the button on the lock to start pairing, the LED ring turns on?

I can build a version for debugging to have a look what's in the beacons ... first we have to make sure those pairing service beacons are there.

from nuki_hub.

Domanda stupida, ma hai ricontrollato che stai facendo tutto bene? È possibile disabilitare l'accoppiamento tramite il pulsante dall'app, puoi ricontrollare che non sia impostato.
Where is this entry in the app? I can't find it. Thank you

from nuki_hub.

Settings --> Features & Configuration --> Button & LED --> Bluetooth Pairing

from nuki_hub.

Settings --> Features & Configuration --> Button & LED --> Bluetooth Pairing

Bluetooth Pairing

Thanks

from nuki_hub.

Following the same steps (enabled/disabled Bluetooth pairing/reset) doesn't resolved the pairing issue with all devices I've been tested on my side.

from nuki_hub.

Following the same steps (enabled/disabled Bluetooth pairing/reset) doesn't resolved the pairing issue with all devices I've been tested on my side.

Are you able to find out the exact chip on your AZ-Delivery V4? My working chip is a ESP32-D0WDQ6 (ESP32D).
Your AZ-Delivery V2 should be an ESP32S, I think.

My full steps after resetting my Nuki device:

1. esptool.py erase_flash
2. flash ESP with esptool like described in readme.txt
3. configure Wifi settings
4. configure MQTT settings
5. pairing Nuki first with app
6. diasble pairing in app (Settings --> Features & Configuration --> Button & LED --> Bluetooth Pairing)
7. enable pairing in app
8. bring Nuki device in paring mode

I never tried "register as app" in nukihub Advanced NUKI Configuration, because I do not own more than one Nuki - no bridge or something else.

from nuki_hub.

As I said in previous posts (#39 (comment)), unfortunately only the oldest v.1 (CPU: MCU LX6) worked for me. The other versions (v. 2/v.4 Az-delivery both with CPU: Tensilica LX6) do not detect the beam (not only from the lock but also from "some other" devices). So I really don't know why some version works for someone and don't for someone else with the same hardware version.

from nuki_hub.

I've release version 6.2, which has some updated libraries. There's a chance this fixes some of the pairing issues.

from nuki_hub.

I've release version 6.2, which has some updated libraries. There's a chance this fixes some of the pairing issues.

Hi, I have reinstalled with new version and opened the door....but door sensor is still closed.

from nuki_hub.

Hi, I just rechecked with my door sensor and it works. Dour your sensor work otherwise?

from nuki_hub.

Hi, I just rechecked with my door sensor and it works. Dour your sensor work otherwise?

Yes, I have checked with Nuki app. I have seen that sometimes door sensor start to work after a lock...other timed it last 2 or 3 minutes to update but other times it not update...I use Nuki 2.0 with ESP32-WROOM-32D DevKit V4

from nuki_hub.

@SergioWarriorPeru Please create a seperate issue

from nuki_hub.

Morning all, Finally I switched from Nuki 2.0 to Nuki 3.0 Pro, this is something I suggest to consider. I suscribed to the nuki beta program (open to all, you just have to contact the Nuki support and they add you to the program within less than 24H) With the beta firmware, the smartlock is able to communicate through a local MQTT server using built-in Wifi. It's super fast compared to the bluetooth version (I'm now able to see the full workflow in real time in my personal app : locked -> unlocking -> unlocked in real time), thanks to push events. You don't need to have a bridge anymore (official bridge or ESP32 DIY). I will not go back on a bluetooth-based solution

Sorry to be slighly off topic but what's your experience with the beta firmware ? I also have an SL3P and I've been reading the battery drain is much bigger with the MQTT feature.

from nuki_hub.

I've release version 6.2, which has some updated libraries. There's a chance this fixes some of the pairing issues.

Good evening, I tried to update to 6.2 but unfortunately my ESP-WEOOM-32 still doesn't connect to the lock

from nuki_hub.

Same issue, always showing "Nuki start pairing". It's the HiLetgo ESP-WROOM-32 ESP32 ESP-32D (Chip is ESP32DOWDQ6 (revision 1) from what i can read on amazon comment). Any idea ?

Edit: firmware 6.7

from nuki_hub.

Hi,

I am having the same problem. Got a new ESP32 device today from Amazon (AZ-Delivery ESP32 DevKitC V2, ESP32-WROOM-32) but I think this is a device which is not working yet?!

After flashing with Nuki Hub via Web the MQTT connection was not a big deal but the pairing is not working after I pressed the button on my Nuki 3.0 pro lock.
Anything else I can do or just unsupported device?

from nuki_hub.

I've sent back mine, gonna try with the AZ Delivery V4.

Anyone got an esp32 model that is 100% compatible ?

from nuki_hub.

I'm using this:

https://www.amazon.de/-/en/gp/product/B093GQGJCV/

Although I think it's not guaranteed that you get the exact same product. They could use whatever chip they could get at the time.

from nuki_hub.

I've sent back mine, gonna try with the AZ Delivery V4.

Anyone got an esp32 model that is 100% compatible ?

#39 (comment)

from nuki_hub.

Do you think that this - AZ-Delivery ESP32 DevKitC V2, ESP32-WROOM-32 - will be compatible via another firmware or version or is there no chance to make it work?

hat's your experience with the beta firmware ? I also have an SL3P and I've b

Same question from my side: any experience with battery drain in the beta firmware while MQTT is activated?

from nuki_hub.

Maybe another suggestion from amazon germany which ESP is a working one?

from nuki_hub.

AZDelivery Dev kit V4 not working too... :(

from nuki_hub.

Mine failed too.
almost seems like there are more boards that don't work than those that work. Is that perhaps due to the Nukihub code rather than the ESP32 itself?

from nuki_hub.

for those who are still looking: https://www.amazon.de/gp/product/B0811LGWY2/

This ESP32 works.

from nuki_hub.

That is my working one: https://www.amazon.de/gp/product/B09LS6SCF7

from nuki_hub.

Following the same steps (enabled/disabled Bluetooth pairing/reset) doesn't resolved the pairing issue with all devices I've been tested on my side.

Are you able to find out the exact chip on your AZ-Delivery V4? My working chip is a ESP32-D0WDQ6 (ESP32D). Your AZ-Delivery V2 should be an ESP32S, I think.

My full steps after resetting my Nuki device:

1. esptool.py erase_flash
2. flash ESP with esptool like described in readme.txt
3. configure Wifi settings
4. configure MQTT settings
5. pairing Nuki first with app
6. diasble pairing in app (Settings --> Features & Configuration --> Button & LED --> Bluetooth Pairing)
7. enable pairing in app
8. bring Nuki device in paring mode

I never tried "register as app" in nukihub Advanced NUKI Configuration, because I do not own more than one Nuki - no bridge or something else.

Hey guys, I have the DevKitV1 and I was just able to pair using the steps above. At first it didn't pair at all, but after trying the steps outlined here it worked all of the sudden. I'm not sure what's the reason.

The one I have is the "ESP32-CH9102X" version, ordered from here: https://www.aliexpress.com/item/32959541446.html?spm=a2g0o.order_list.order_list_main.43.6a991802bAp4Y8

from nuki_hub.

@shlomki
Nice it worked for you. Tried several ESP32 and none of them worked with those steps.

As stated as "working" on the mainpage, i really recommend everyone to get an ESP32D to get away from any difficulties. Those ESP32D just work out of the box, and it seems like, it doesnt matter what kind of board it is as long it got a ESP32D.
myself tried 3 differend ESP32D boards now and everyone worked out of the box.
But sure, if you like lottery, you can try ESP32. You may have luck, but mostly you dont.

from nuki_hub.

This works 100% https://it.aliexpress.com/item/32864722159.html

from nuki_hub.

I have bought this and work fine
https://a.aliexpress.com/_mqSdNjU

from nuki_hub.

This works 100% https://it.aliexpress.com/item/32864722159.html

Wich one ? The 32D ?

from nuki_hub.

This works 100% https://it.aliexpress.com/item/32864722159.html

Wich one ? The 32D ?

Yes

from nuki_hub.

This works 100% https://it.aliexpress.com/item/32864722159.html

Wich one ? The 32D ?

Yes

I'm getting it. Can you tell the model of your smartlock (3 or 3 pro), firmware version and nuki_hub integration version for futur comparaison ?

from nuki_hub.

I have more reports that erasing the ESP and then (re-)flashing does help pairing problems. If it doesn't work for you, you can use the espressif download tool (or esptool.py) to erase the flash. Then try flashing a new firmware.

from nuki_hub.