ISSUE: Stuck on Deleting or Adding #270
Labels
Comments
|
I'm having the same issue. Only happens on one of my child locks and only 3 code slots. I deleted the lock and re-added it and the same thing happens on the same slots for the same lock. I'm trying to look at the logs, but I don't know where the logs are located. |
|
OK I figured out how to "fix" it, or at least manually push the codes to the door. Once done, the slot shows it as "connected" or "deleted". Once I did this fix, I could change the code, disable or enable the code and it works as it should. It's almost like there was a some sort of communication problem with just those code slots and for some reason Keymaster couldn't get the lock to change the code. and when I manually pushed the code to the lock, it fixed the problem. Here is what I did:
Sometimes I had to play around with it or maybe it just took a few minutes to work. The first slot worked right away and keymaster changed it to "connected" The second slot I had to un-enable it, then run the script. At that point, keymaster showed it as "deleted" and when I enabled it, it showed "Adding" then shortly after "Connected" The third slot took a few times of running the script and enabling / disabling the slot in keymaster. Maybe it just takes time to cycle through the system when you run the script? I don't know, but as of now, it works as it should. Oh and finally, it seems obviously, but if you have multiple slots that need to be done, make sure you change them in the script after the previous slot is fixed and save the script before running it. Hope that all makes sense. Good luck. Any questions, please ask. |
|
@dcf1999 That WORKED! I had a similar experience as you, had to do it a few times but eventually, it got back to a working state. Thank you so much. |
|
I ended up forcing the automations "synchronize _______" and that fixed it for me. |
|
I just acquired a lock from someone that had been doing manual code management on the lock itself. I ran into this same problem. My solution was to disable the offending slot and then use the developer tools / services to do the following: call keymaster.clear_code with the lock entity_id and the code_slot defined. Once this was done, I could enter my target code and set to enable and it picked up properly from then on. Keymaster definitely has a bit of an issue when taking over a lock that has been in use in some way outside of Keymaster management. |
Which is funny because it's just the zwave commands wrapped up.
I've noticed this mostly happening on specific brands of lock, Yale and Schlage. Kwikset seems to work flawlessly out of the box. 🤷♂️ |
The one I acquired was a Kwikset :-/ It's happened to me with two different previously used Kwiksets. |
|
Strange, I've never had any issues with my Kwikset. |
|
@firstof9 I only seem to have the issue with Kwikset locks if they've been used outside of Keymaster. Or in the case of one lock, a different installation of HA & Keymaster that I moved locations of! It's all around codes already being in the lock and Keymaster for some reason doesn't pick them up properly though I've seen it actually get the codes but it seems to get stuck in a weird state of deleting/adding them. |
|
I am having this issue but with Every user code. |
|
If you are still stuck... Remove Z-Wave Device:
Add lock again. This time use the code route
From this point I tried the method suggested here of manually clearing the code slots thanks to @tykeal. I honestly am not so sure that the button in the back with the battery is secure. I think the way I wrote above to add the lock in Z-Wave JS made all the difference. |
|
Hoping someone can help! I also have the Schalge BE469ZP (Allegion) and have exluded it and removed all keymaster integrations 3 times now and set everything back up using @alsoszaa method of adding the lock back in. The lock connects just fine in home assistant, but I can not get this integration to work. After installing the the integration in HACS and then adding the integration in HA, I get 11 entities (10 code slots and the network sensor). When I view those 11 entities though, the 10 card slots show as "unavailable" and the network entity shows just a "-" under status. I'm guessing this is why, if I go through the rest of the set up process, I am unable to clear and reset codes, either in the UI or through the developer tools. Please be gentle as I am new to HA, but would greatly appreciate any help that can be offered. Other Zwave devices are working just fine, when these sensors are generated through the integration, they are all showing as unavailable. Thanks in advance! |
If you go to dev tools -> settings -> info under system health, what does the keymaster info say? Example: |
|
Thanks for the response! Mine is showing exactly what you have in your example. |
|
Once the network status goes 'on' it should attempt to pull your codes from the lock and make the sensors available. |
|
Thanks Chris. I’ve been away for the last couple of hours and just had the chance to check the keymaster entities. They are all showing unavailable still with the exception of the network entity.
…________________________________
From: Chris ***@***.***>
Sent: Sunday, April 24, 2022 1:46:29 PM
To: FutureTense/keymaster ***@***.***>
Cc: eboline ***@***.***>; Comment ***@***.***>
Subject: Re: [FutureTense/keymaster] ISSUE: Stuck on Deleting or Adding (Issue #270)
Once the network status goes 'on' it should attempt to pull your codes from the lock and make the sensors available.
—
Reply to this email directly, view it on GitHub<#270 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ARZAC2533MOSVTUA4T66X7LVGWJILANCNFSM5REGG27Q>.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
Try enabling debugging to see if there's any errors happening. |
|
I’ve enabled debugging (based on info in the wiki I think) but not real sure how to check for errors. Can you provide some information on how to do that?
…________________________________
From: Chris ***@***.***>
Sent: Sunday, April 24, 2022 6:06:59 PM
To: FutureTense/keymaster ***@***.***>
Cc: eboline ***@***.***>; Comment ***@***.***>
Subject: Re: [FutureTense/keymaster] ISSUE: Stuck on Deleting or Adding (Issue #270)
Try enabling debugging<https://github.com/FutureTense/keymaster/wiki/Troubleshooting#enable-debugging> to see if there's any errors happening.
—
Reply to this email directly, view it on GitHub<#270 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ARZAC22NZEONVRAUG3MCNF3VGXHZHANCNFSM5REGG27Q>.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
So I went to Dev Tools -> Services and selected the "logger.set_level" service and put "custom_components.keymaster: debug" and pressed "Call Service." The box turned green and I got no error messages on the screen. I then went to Configuration -> Settings -> Logs tab. I don't see anything related to keymaster, but maybe I'm not reading it correctly. Here's what comes up:
|
|
View your |
|
I'm having the same issue, I tried the dev tools clear code and I'm getting this in my logs; |
|
This means your lock didn't complete the interview. |
|
Thanks, weird as the lock was working for months, I added another lock and it seems to be having issues. I'll try re-interviewing. |
|
I’ve tried reinterviewing the lock multiple different times and still no luck. Still showing the code slots as unavailable.
…________________________________
From: tommywatson ***@***.***>
Sent: Tuesday, April 26, 2022 5:33:54 AM
To: FutureTense/keymaster ***@***.***>
Cc: eboline ***@***.***>; Comment ***@***.***>
Subject: Re: [FutureTense/keymaster] ISSUE: Stuck on Deleting or Adding (Issue #270)
Thanks, weird as the lock was working for months, I added another lock and it seems to be having issues. I'll try re-interviewing.
Thanks.
—
Reply to this email directly, view it on GitHub<#270 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ARZAC22SUD262K4BKW72YFTVG7PDFANCNFSM5REGG27Q>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Need those logs to help you find out why. |
|
Good morning, sorry the delay. I've been out of town on work. Are these the logs you are hoping to see: |
|
These contain no debug logs from keymaster. |
|
I double checked my configuration.yaml file to ensure that logging was enable using the instructions above. Then I called the service through Dev Tools -> Services from the instruction and got a green check mark. This is what was added to the log when I called the service: |
|
Try making your configuration yaml similar to this: logger:
default: error
logs:
custom_components.keymaster: debugand restart Home Assistant, this will give a better run down of what's going on. |
|
I really appreciate your help with this Chris! I updated the configuration.yaml file as you showed above and restarted HA. Here's what is in the log now: |
|
|
|
Having the same issues with my Schlage lock , Keymaster, and Z-wave. I have a Zooz ZST10 Z-Wave S2 USB Stick that I use on my HA. I just requested a firmware update from the manufacturer. They make you request it, it's not immediately available on their site. Hopefully this will fix some of the incomplete interview issues. Here is the link for those interested: https://www.support.getzooz.com/kb/article/1126-how-to-perform-an-ota-firmware-update-on-zooz-devices-in-home-assistant/ |
|
I finally got beyond "stuck on adding or deleting" today. I noticed that some of the sensors on my locks were "unknown". I have deleted, re-added etc the locks before but not today. I just kept re-interviewing them, again and again until the codeslots where working. Re-interviewed, re-started, and eventually both were working without add/removing from z-wave. Screenshots are a lock before/after |
|
The only thing I am seeing in that log related to keymaster is the warning about a custom integration which has not been tested by Home Assistant.
I have the packages directory and see a .yaml file for every code slot (10 in my case) along with the common and Lovelace file. I also see a bunch of files under customs components->keymaster. Do I need to edit any of these files?
…________________________________
From: Chris ***@***.***>
Sent: Monday, April 25, 2022 11:15:36 AM
To: FutureTense/keymaster ***@***.***>
Cc: eboline ***@***.***>; Comment ***@***.***>
Subject: Re: [FutureTense/keymaster] ISSUE: Stuck on Deleting or Adding (Issue #270)
View your home-assistant.log file in the /config directory.
—
Reply to this email directly, view it on GitHub<#270 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ARZAC22SI5SWLWDXFZOELA3VG3AKRANCNFSM5REGG27Q>.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
After trying most of the suggestions mentioned here and removing the schlage lock connect many times and adding it again, I finally succeeded to connect the pins. To do it or to test it, do the following: |
|
nope, still does not work for many people. i have a yale and two schlages i tested with 2" from the hub. i can start from scratch, re-interview, anything you can think of, it doesn't work. i created a new HA to test this with all the various fixes and still nothing works. the locks get stuck on adding/deleting. some people can get a random slot to work, or add codes manually first then add to keymaster, but what's the point? you're introducing a layer of complexity for no reason. this issue goes back 1-2 years with various brands. threads get closed with no real resolution and there are multiple threads open with this issue. i would not trust this integration until this is fixed. |
Did you delete all the default codes that come with the lock? I was experiencing the same issue for weeks. I finally resolved by deleting all the codes and then went to the keymaster and start creating the users and their codes. I dont remember if I had to restart HA. Update: |
Closed
|
If it is of any help for anyone else, seeing I've been banging my head too on this issue for a while, I have solved it with the workaround automation I shared here! |
|
I am having the same issue described above. I am on 2023.1.7 on my main instance running zwavejs getting events over WS from an rpi that has my zwave stick running HASS 2023.1.7 w/ zwavejs there. My zwave network is (from what I can see) super stable. My lock is a BE469ZP Here is what I have found:
So seems like a bug in keymaster dealing with those first 3 pins |
|
Hopefully this helps as I was having the same issues as everyone else here and this resolved the problem for me:
solution found on reddit: https://www.reddit.com/r/homeassistant/comments/tuxdu9/schlage_connect_lock_cannot_set_usercodes/ |
|
Oof - that sounds like a painful process for someone with a lot of locks paired with automations already tied to them. I have five BE469ZP's, and they're finicky to pair short of removing the control board and battery pack and re-adding right next to the controller. Wish only step 3 was necessary for slots 1-3 to work and not be stuck in deleting/adding state. |
|
A re-interview can be done in place, you don't have to move the lock anywhere. |
Thanks - there's a known issue with the BE469ZP that causes re-interviews to lose all nodeinfo details until a magic amount of tries fixes it. Used it as a chance to update my stick's firmware, so not all was lost. Unfortunately, after getting it reinterviewed correctly, the lock is still stuck on deleting. I don't think these locks are solid candidates for tweaking with. If it works with basic functionality, I'd leave it be. |
|
I had been having this same issue, all codes stuck adding/deleting. Background, had working config with 2 x Schlage B468, zwave-js and key master. zwave-js handled by 2 x raspberry pi with zooz USB ZST10 sticks. I accidentally cleared zwave config on one of the zooz sticks while upgrading firmware, and when I added everything back in I could never get key master to properly handle codes for the door that had to be re-configured. Long story short, for troubleshooting, in zwave-js, make sure your lock has the User Code command class (go to device detail, Node section, you should see "User Code v1" or some such along with other details. If you don't see it, re-interview the node, and you might need to tick the "Reset security classes" checkbox. I had just gone through a reconfig (remove key master integration, exclude lock, re-add lock, re-add key master integration), and it was still broken. Confirmed User Code class was absent, re-interviewed one time, User Code class showed up, all is fixed. I have to wonder if Keymaster could show an intelligent error when trying to handle codes if the "User Code" command class is absent. |
|
Having this issue on my Yale Assure 2 lock after swapping out the ZW2 module for the ZW3 module (in hopes of making my z-wave connection more reliable). I deleted the existing keymaster integration and created a new one. The code slots set through keymaster are actually being set in the lock, but keymaster doesn't reflect that (stuck on "Adding"). I can manually use both the zwave_js.{set_lock_usercode,clear_lock_usercode} and the keymaster.{add_code,clear_code) services to set and clear codes, and those both succeed (the "Call Service" button changes to a checkmark after a few seconds). When setting the code through the UI, the debug logs show the error message "DEBUG: Code slot NNN not enabled": I've tried resetting all of the code slots manually through the service calls. This succeeds, but doesn't resolve the issue with setting the codes through the UI. Any idea what causes the "Code slot NNN not enabled" message? |
|
I tried debugging this a little more. It looks like the "Code slot NNN not enabled" is coming from here: , which is calling into zwave_js here: https://github.com/home-assistant-libs/zwave-js-server-python/blob/ca30b7558eeac921582e3dabd8d0591d3f4364bc/zwave_js_server/util/lock.py#L80. I didn't see any reference to this function in the zwave_js debug output.Here is the zwave_js debug output when adding a new usercode. The zwave_js messages show success in setting the usercode. However there is no mention of the get_usercode function which keymaster is calling. Any idea how to debug this further? |
|
Check to make sure the code slot is |
I'm using the official Z-Wave JS add-on, not the Z-Wave JS UI unfortunately. I don't see anything about code slot in the list of enabled or disabled entities, nor in the zwave-js configuration page. Is there any other way to look this up? |
|
Only way I know how. |
|
I switched from the Z-Wave JS add-on to the Z-Wave JS UI add-on (following https://www.home-assistant.io/integrations/zwave_js/#how-do-i-switch-between-the-official-z-wave-js-add-on-and-the-z-wave-js-ui-add-on), and that seems to have fixed the problem. I can add and remove codes as expected. I didn't try switching back to Z-Wave JS to see if it was the switching that fixed it, or Z-Wave JS UI. Thanks for the suggestion! |
Just spent a crazy amount of time trying to get this working, until I found your comment. Sure enough everything started working fine after a series of re-interviews and rebooting my HA server. Fortunately I don't have a frequent need to update pins, set schedules for them etc and that is the primary thing that this bug impacts. At any rate @FutureTense maybe consider marking this issue as resolved or won't fix and add a note in the docs? |
|
Sorry to reply to this thread again, but I'm having this issue again, although I've found a workaround and I wanted to get your thoughts on it. Removing existing codes works. They do not get stuck. However when adding a code, KeyMaster gets stuck at "Adding". I do get a notification saying that the code has been added, and the code actually works on the door lock. However KeyMaster doesn't know that the code was successfully added, and remains at "Adding". The problem with this is that when I disable a code slot, the code isn't actually disabled, I assume because KeyMaster thinks it was never actually enabled. The first workaround that I found was to go into Z-Wave JS UI, go to the User Code config, and click "Refresh Values". This works. It takes a while to refresh all of the values though, and generates a lot of traffic with the lock. When I look at the events in Z-Wave JS UI, I can see all code slots being refreshed, from slot 1 to 500, and it takes several minutes to complete. A shorter way that I've found to refresh this value is by issuing the following service call from HA: The parameter '5' is the code slot to refresh. After issuing this service call, KeyMaster immediately updates from "Adding" to "Connected". I'm wondering if this is a bug in zwave_js, and if I should report it there? |
|
In case anybody needs it, I've permanently worked around this issue by creating an automation which triggers on the user code add zwave-js notification event, and then issues a zwave-js CC command to refesh the specific slot which generated the event. The device_id in the trigger is the device id for the lock. alias: Fix Keymaster User Code Add
description: ""
trigger:
- platform: device
device_id: ebcc82a6df7be991068406c54e9be498
domain: zwave_js
type: event.notification.notification
command_class: 113
type.: "6"
event: "14"
condition: []
action:
- delay:
hours: 0
minutes: 0
seconds: 5
milliseconds: 0
- service: notify.mike_notify
metadata: {}
data:
message: Detected User Code Add {{ trigger.event.data.parameters.data[1] }}
enabled: true
- service: zwave_js.invoke_cc_api
target:
entity_id: lock.assure_2_keyless_touch_screen_deadbolt
data:
command_class: "99"
method_name: get
parameters:
- "{{ trigger.event.data.parameters.data[1] }}"
mode: single |
|
I'll just add how I got mine working. Called the clear lock user code svc on slot 1. Then all my slots started working again. Good luck. |
Unfortunately this doesn't resolve the issue for me. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
Describe the bug
When adding / removing Code3 from the Home Assistant dashboard the PIN Status is stuck on Deleting or Adding. All of the other code #'s work fine, can add and delete without issue.
Environment (please complete the following information):
HassOS
Unraid VM
Home Assistant 2022.3.5
zwave_js
Yale YRD-256
Logs
Paste your error logs here.
Screenshots
Additional context
Otherwise works great!
The text was updated successfully, but these errors were encountered: