Yes
It was enabled all the time
In the logs I keep seeing “Nuki start pairing” but nothing happens…
Does the little blue light on the esp32 should blink at any point?
For example, when I’m using eapresense on the same board, there is a little blue light blinking all the time
The light is usually wired to the serial line … so it blinks when it outputs logs.
There’s already an issue on github:
I’ve uploaded a binary with more log outputs there, could you try and and give me logs (on github if possible please).
Thanks
I will upload later today.
Can u please share a link to the esp32 board you are using?
I’m using the one with the type c connector (CP2102)
I’m using this one.
1 Like
enabling BT pairing in the app did it for me… and all got back working - amazing
i m soooooooo pleased.
thank you guy - so happy to be a part of this community
What is the difference between register as an app or register as a bridge?
Bit late reaction. But the problem was in the type of cable. From usb to usb c cable. After I got another cable, everything worked perfectly.
Registered as an app you could use a bridge in parallel. So your friends and your wife could use the normal nuki app on smartphone und you can use homeassistant for your automations.
The functionality is the same as far as i see.
Oke clear. Thx!
@technyon Awesome project!!! Thanks for your great work. I am wondering if there is a way to use the keypad integration to controll automations (e.g. in my case it would be very usefull to have a code to open the roller blinds which covers my front door)
The keypad is directly connected to the lock. The code is transmitted and the lock decides wether or not to do a certain action. So to answer your question, no it’s not possible to trigger actions other than what the lock allows you to do.
1 Like
ok, thanks for that information!
First of all thanks for the great work! I managed to get it working in Home assistant (HA) quitte smooth. I own a V3 lock but im only able to lock, unlock the Nuki. I can’t find out a way to unlatch the door, my YAML looks like this (Sorry for the Dutch)
1:type: entities
2:entities:
3: - lock.voordeur
4:title: Voordeur
adding -unlatch.voordeur to the entities does not work…
any idea’s?
You need to use the lock.open service.
@technyon thank you man, your project is awesome 
took me few mins to flash ESP32, half an hour to get it boxed and in HA it appeared after 5 hours, probably some strange autodiscovery on my side… I am so excited that I’ll probably order second nuki lock, just wonder - would it be possible to pair more locks to one nuki_hub, or only way is to get ESP32 per each lock ?
And as someone mentioned before - remote syslog would be great, once hub is connected to wifi. But that is just refinement, you did great job 
Hi,
One Lock and one Opener per ESP. It would add a lot of complexity to support multiple locks, and considering the price of ESP32 modules, it’s easier to just have multiple ESPs. Plus you can place each ESP close to the lock it controls.
Hi, nice addition to the crappy nuki integration. I used nuki ng before but as i red that the dev will not longer support this and switched to your integration i also did that.
I have some questions about this:
for now i used nuki ng with the official bridge in combination with HA. lock and unlock action based on my location (coming/leaving) home and unlatching with bluetooth via nuki app.
as i see the most advantage is getting rid of the brdige isnt it? my esp is very close to the lock but triggering actions takes 5-10 seconds which is slower than bluetooth of the official bridge.
i configured nuki hub as an app and use the bridge a long side with nuki ng so i can compare better.
maybe this makes it slower?
also what i would like to do is to unlatch when the door is closed and not after the delay (10sec for me) is there any way to check this with nuki hub?
door sensor is not a nuki one but i want to unlatch the lock after door is closed again. but only if the action comes from auto unlock via bluetooth from the ios app.
i did not find any info in mqtt that this state is available. is there anything i can do or can you implement this?
I think you mean “lock”, not “unlatch”. Unlatching means withdrawing the latch so that the door can be pushed open from outside.
Locking the door again after a door sensor indicates it is closed is certainly possible via HA and NukiHub. Have you looked whether anyone has written a blueprint yet? NukiHub supports all the standard lock services via HA auto-discovery.
Not really. I mean latch and unlatch.
Unlatching happens due to Auto Unlock function via iPhone. But after the door is closed again it should latch instantly and not after the time which is set up in the Nuki app (10 seconds)
I couldn’t see a difference in state change while the door is latched or unlatched.