Hi. I am noticing that sometimes after an upgrade or a reboot, my autolock timers reset to 5 and 15 minutes. Is there something I am doing that is resetting these accidentally?
I just setup notifications and it works, but it is sending the wrong user who opened the door. Any ideas what it might be? I added this to the scripts.yaml
Good evening all,
I need to update my Zwave from the old depreciated one to ZwaveJS. I’ve watched a couple of YT tutorials on migrating to the newer system and it looks pretty straight forward. I only have a couple of Zwave devices but my biggest fear is my Schlage Zwave lock on my front door that I use with the awesome Keymaster. I have already made a note of my secure Zwave network key from my configuration.yaml.
Is there anything in particular I need to pay attention too when undertaking the migration?
Regards
Richard
Further to my post above I did migrate to Z-Wave JS successfully and my lock worked after renaming the entities to match what I previously had.
I do have a problem with 3 out of the 6 slots. I had codes in all 6 slots but three if them were disabled as they were not in use. The three slots that were active can be disabled or the code changed and everything syncs. I cannot enable or change the codes in the other slots. The pin status changes to Adding but never changes to connected
I have even removed Keymaster completely and re installed it but the same thing still happens.
I’d appreciate any thoughts on what might be causing this
Usually a PIN like 5555 isn’t valid and the locks will reject it.
I actually managed to get the 3 slots working again,
I was looking through the entity options for the lock and found this
I opened each of the slots that were not responding and manually ran them and from then on everything worked normally.
Thanks for the reply
3 Likes
I am running 2022.2.9, and the latest version of keymaster. Everytime I restart HA, the lock’s day and night autolock intervals reset to default values. What I am I doing wrong?
2 Likes
Quick question,
I actually have 4 Schlage BE469 locks, currently two of them are being used in Keymaster, Is there a limit to how many lacks can be added?
There’s no limit.
Cool thank you,
I did go ahead and add my 3rd lock and it was a breeze. Will be doing me 4th tomorrow 
I’m new-ish to HA, but a total newb to customizing lovelace dashboards. I have successfully configured 7 Yale Assure SL locks with Keymaster, each lock on a different tab in a dashboard using the generated yaml. Two locks have 18 slots and the others have 10 slots each, so needless to say, there is a lot of information on each of these tabs.
I’d like to build an overview tab that gives me a quick summary of the state of all slots and all locks in a compact format. This view doesn’t need to edit anything or activate/deactivate the locks, it just needs to report current state.
I’m thinking a table for each lock, perhaps formatted like this:
Lock Name
| Slot | Status | State | Name | PIN | Enabled | Date Range |
|---|---|---|---|---|---|---|
| 1 | Connected | (√) On | John | 1234 | True | Mar 1 4pm - Apr 1 12pm |
| 2 | Disconnected | ( ) Off | Sue | 5678 | False | None |
Columns:
- Slot: the slot number
- Status: so I can quickly check activity, especially to see if it is stuck as
AddingorDeleting - State: The
(√)and( )would be the yellow circle checkmark state icon - Name: Guest name
- PIN: Guest’s PIN code
- Enabled: If the slot is currently enabled or not
- Date Range: If
Use Date Rangeis not enabled, this would beNone, otherwise the start/end dates.
Are there any existing custom cards or github projects that I should consider using? Any examples of yaml and/or custom code to render a tabular card like this? Any other advice that might help guide me to a working solution (iteration through slots, conditional date range output, etc)?
This is for a multiple unit Airbnb. I’m worried that a guest will arrive and their lock code won’t work. My hope is that this overview will make it easy for me to quickly identify potential problems.
1 Like
You should explore existing dashboards and available controls in HACS to see what’s possible.
I installed KeyMaster today and so far so good, it recognizes the lock and I can unlock/lock with it. However, I try to add a PIN and it just sits there on “adding” and never makes it. I monitored the zwavejs2mqtt log and didn’t see anything hit it when I created the PIN.
What should I look at when trying to troubleshoot this?
Try what this user stated:
1 Like
I fixed it. I had the lock installed before I had it hooked up to zwave and there were user codes in the first few slots. I deleted the old codes and then it allowed me to start adding them through keymaster. Problem solved!
1 Like
Same, I have a lot of trouble with this. The codeslots go “unavailable”. Sometimes fussing with it helps but not today.
@FutureTense Hello, I am using the Yale Assure SL Zwave lock (3 in total) but for some reason only 1 code which is in slot 2 has went to “connected” status. All other code positions stay in “Adding” or “Deleting” status. (This is what is occuring on 2 of the locks, on the 3rd lock, none of the 4 code positions move to the “connected” status, all stay in some “…ing” status)Can anyone give me any guidance as to what is going on or how to troubleshoot/ fix this issue.
Thank you all for your help!!
Same thing is happening to me right now. I’m using the Yale Assure lock. Also some of the codes are sync with my other lock of the same type and some aren’t
I’m starting to question the maturity of Home Assistant sadly because I’m running into tons of things that I wouldn’t call “user friendly”. The whole system is reminding me alot of webcore from smartthings which I mostly stayed away from because I’m not a programmer by trade. I can tell home assistant is more than likely insanely powerful if your highly technical but otherwise, I’m not so sure. There have been quite a few things so far that have been much harder to implement than I thought would or even should be. Whereas smartthings has precompiled widgets for the largest features (home security monitor based on sensors, safety monitor based on leaks etc.). All of this seems to have to be “rolled” by the user within the Home Assistant environment.-- Unless I just don’t know where to look–The lock managing noncomponent is seemingly another one (Widget in smartthings called “Smart Lock Guest Access”). If you end up learning anything, please post back here even if it ends up being another integration. The number of entities this one created drives me batty also everytime I look at it.
It may just all be a: I need to temper my expectations situation if I am going to stick around and remember were not dealing with a multi-billion dollar corporation down this path.
This is 100% accurate Weston. Period. It is a fundamentally different philosophy. And while HA is WAAAY more user friendly than past iterations - there’s ZERO way I’d reccommend it to my dad - a non technical user. SmartThings is (INCREASINGLY) designed for a novice user, opting to shield the complexity, while HA leans into it and encourages customization. That said - this particular tangent of the conversation is WAY off topic for Keymaster so out of respect for the thread owner, if you want to continue that conversation there’s a few ST v. HA threads on the forum frequented by ST refugees. - er - former users. They’re easy to find. (All I will say is HA is Webcore on steroids, gamma rays, and it ATE the Hulk. If you didn’t like Webcore, you’re going to have a tough time with HA.
As to your specific issue, yeah that happens - and not only with the Yale. Keymaster can only report what the lock is telling it. There’s MANY ‘Stuck on adding…’ reports on the forum. Higher up in this VERY thread. Unfortunately, there’s almost as many resolutions as there are reports. I had the issue myself. My 3 older Schlages were a royal pain to get past ADDING. (I later traced its likely cause to a communications issue in my Zwave network related to a firmware bug.) To clear it, I ended up manually clearing out all of the codes using ZWaveJS service calls in the HA debug tool, then I restarted the lock configuration in Keymaster from scratch and they finally ‘took.’ Fortunately adding / removing codes is a once every 6 months kind of event here so that was good enough for my install.
1 Like