-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot connect to the smartlock #39
Comments
I tried to register as an app (I was using bridge mode first) but the issue persists. |
Did you pair your smartphone already? |
First yes the smartphone was paired to the smartlock |
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? |
They are literally separated by 5cm, I unmounted the doorlock from the door to put in just near the ESP32
It still won't connect sadly. |
I'm somewhat out of ideas ... I'd have to add some log messages to see what's really going on. |
Ok, thank you. |
Please try with the attached firmware and send logs. When flashed the version string is "6.0-dbg-connect". |
Thank you
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:
|
Oh, new logs:
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. I cannot make the ESP32 closer to the smartlock, they are already together... |
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. |
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" |
@technyon here are my logs I set my lock to paring mode, and the esp just got stuck in a Nuki start pairing loop |
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". |
how do I flash this ver? |
Same issue here, can't pair.
(in loop)
But ended with:
|
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! |
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. |
Tested today with other ESP32 boards and worked an paired at the first try: Nuki start pairing 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. |
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. |
Hi, a question...where is the option "register as an app"? |
In the configuration portal go to NUKI Configuration, in the advanced section enable the first checkmark. |
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 |
I have seen logs and it is always showing |
@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. |
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 |
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: Maybe pick one that's not listed as "NRND". |
Hi, I only have this amazon link: https://www.amazon.es/gp/product/B0B55MS33L The board is labeled as "ESP32 DEVKIT V1" |
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. |
I've sent back mine, gonna try with the AZ Delivery V4. Anyone got an esp32 model that is 100% compatible ? |
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. |
|
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?
Same question from my side: any experience with battery drain in the beta firmware while MQTT is activated? |
Maybe another suggestion from amazon germany which ESP is a working one? |
AZDelivery Dev kit V4 not working too... :( |
Mine failed too. |
for those who are still looking: https://www.amazon.de/gp/product/B0811LGWY2/ This ESP32 works. |
That is my working one: https://www.amazon.de/gp/product/B09LS6SCF7 |
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 |
@shlomki 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. |
This works 100% https://it.aliexpress.com/item/32864722159.html |
I have bought this and work fine |
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 ? |
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. |
I also had paring issues with my ESP32 until I upgraded to 8.2 with the downgraded BLE library. It paired after a few attempts. I bought this EPS32 MCU from Amazon Australia https://www.amazon.com.au/DIGISHUO-ESP-WROOM-32-Development-Microcontroller-Integrated/dp/B097DCN76N |
Same problem here; I have two different type of ESP32 boards, very similar: one is from AZ-Delivery, and the other one from an unknown manufacturer. Chip is ESP32-D0WD-V3 (revision v3.0) Do I need to buy another type, or is it possible to get one working? |
Since there's no activity here, I'll close this for now. If you still have issues, please try release the latest release, version 8.18 has a fix for pairing issues. |
I've added the M5Stack Atom Lite to the readme, which is known to work and is recommended due to its improved antenna. |
I can't pair my ESP32-WROOM 32U. I erased the firmware and reflashed with the ESP tool, without success... |
The external antenna is properly connected? |
I hadn't connected it!...it works now. |
Hello,
I cannot pair the smartlock
Nuki and ESP32 are separated by 5 centimeters.
I use the latest Nuki 2.0 firmware 2.12.4
Nuki is of course in pair mode (white circle)
I tried to factory reset the smartlock but still trying to pair without success.
Do you have an idea?
Thank you
The text was updated successfully, but these errors were encountered: