-
Notifications
You must be signed in to change notification settings - Fork 19
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
Feature request: Keypad codes #7
Comments
My use case would be (amongst other things) to create temporary pincodes that expire after a certain timeout, now that I have looked at the code a bit better it seems Nuki uses unique identifiers for the keypad codes that can only be found out via the retrieveKeypadEntries function. Maybe you can implement a service for temporary pincodes as well, that would be awesome! |
Hi @AlternativeBoi, |
I'm not the OP, but I would love this feature. |
Hi @AlternativeBoi , @haseat, The services are implemented in the dev branch. Note that you need to have some changes in the yaml (and maybe update esphome) as explained in the readme. 4 new services (callable from HA developer tools, scripts, automations, etc.) are implemented: |
@uriyacovy I'm happy to help testing starting next week, as I'm currently abroad. I'll post here if I have any questions/remarks. |
Hi Thank you for you great job ! When I'm trying to call service : I'm getting error in logs: Keypad 2.0 connected to lock and could be managed through phone |
Thanks @denissp.
|
Something strange happens, before I enable logging lock and unlock works without problem [D][api:102]: Accepted ::FFFF:192.168.1.21 I repair lock, erase esp flash |
Additional logs [D][api:102]: Accepted ::FFFF:192.168.1.21 |
@denissp, how did you enable logging? Are you connected to the esp directly (usb) or via wifi? |
Looks like it's not related to debug ( I enabled debug in esphome yaml file) It's somehow related to BT communication As a workaround I added simple semaphore into code which prevent command execution until i get status update from lock: also I added small hack into else clause in void NukiLockComponent::update_status(), this helps recover from crashes, but after adding semaphore everything works without this this hack.
I could share code and additional logs a little bit later |
|
OK, I figure out where was my problem related to keypad entries After defining pincode I successfully retrieve all keypad entries. I assume that there should be ability to define pincode either through HA services or through esphome configuration I will look into my stability issue little bit later. |
@uriyacovy Thank you very much for your effort building the missing link between the Nuki and ESPHome. I'm glad to read that you have the keypad capabilities developed already in the DEV branch. What makes me curious: beside the keypad, I also paired two Nuki Key Fobs to the lock. Would it be possible to see them in ESPHome as well? Again, many thanks for all of your work bringing the loose ends together. 👏🏻 |
Hi @Pe-MaKer, Regarding the support for multiple locks, it was discussed here: #2 |
Thanks @uriyacovy, Looking at Hass Nuki NG (https://github.com/kvj/hass_nuki_ng), the individual passcodes are managed as switch.entities in HA, which can be activated or deactivated. I would like to see this for ESPHome Nuki lock as well. Regarding the Nuki Fob, I might have misunderstood: They are BT key fobs, which are managed in the Nuki lock as additional authorisation entities besides the PIN codes. Also with the possibility to activate and deactivate them as switches. So it is not about controlling another lock, as in the topic you linked to. To put it briefly: The cherry on the cake: |
Sorry for the late reply.
|
Don't worry, I'm glad you're still sticking to the topic. After a few days of productive use of ESPHome Nuki Lock together with a door opener relay and a R503 fingerprint reader, my requirements have changed. However, what I would like to know from the Nuki integration is which key triggered the last opening or if an incorrect PIN was sent to the lock. It is important for me to know if someone is trying out PINs on a lucky chance at night. |
I reviewed the Nuki API documentation and I'm not sure there's a way to get this information. |
Yes, it is available on the App. Other integrations as like "Nuki Hub" and the "Hass_Nuki_NG" provide something like "lock/authorizationName" or "sensor.nuki_haustur_last_unlock_user". |
@uriyacovy are there any plans to continue developing ESPHome Nuki Lock? |
Unfortunately, due to lack of time, I'm trying to just maintain the current module. If anyone else would implement the feature, I'll gladly pull. |
Hello!
First of all, thank you for creating this integration. It solved a fairly big problem with the Nuki, I appreciate it.
I would love to see you integrate the addKeypadEntry, updateKeypadEntry and deleteKeypadEntry functions of the library you are using into a service. No other custom bridge that I found has the keypad features integrated, so this would be really helpful.
Thanks a lot.
Cheers,
AlternativeBoi
The text was updated successfully, but these errors were encountered: