I don’t see any list of “supported locks” in the github repo or on this thread.
Do we know if this supports the Ultraloq locks?
More specifically the Latch 5 Fingerprint & U-Bolt Pro?
The supported locks are essentially any ZWave lock as it currently can only talk to something managed by the ZWave controller. Zigbee control has been in development for a while but last I knew was running into some issues.
All other locks are not supported as no work has been done to be able to support them.
HA itself would first have to be able to connect and control the lock before any work in Keymaster to support a different protocol could be considered.
So, the first thing to figure out is if the lock in question is a Zwave lock and is communicating properly with HA.
If it is, then it should work with Keymaster.
The problem is all Z-Wave locks are supported, but to different depth.
So all are equal, but some of them are more equal than others. 
I would love to see a matrix of locks. I am asking on another thread how to scrape this thread for this data.
IMO, you’re doing it backwards, you should be looking at the ZWAVE locks that don’t fully support all of the ZWAVE lock commands. Like you said. not all ZWAVE locks are equal, I made a decision to purchase my locks based on the supported commands. Then HA & KeyMaster unlocked additional commands and features I was not aware of.
Some times the lock support commands are not listed in the specs so you would have to ask their support for pre-sale information.
Probably wouldn’t be a bad idea. I can state that Kwikset’s Zwave compatibility seems to pass muster for KeyMaster. They’re the only locks I use. I’ve got several of the older 910s, 912s, and the newer HC620s. Pretty much all the problems I have with the locks is the initial setup and occasionally the lock missing a code update when the Zwave network is a little saturated with events. That’s usually cleared up with a keymaster.refresh_codes call.
For Zwave locks a buffering repeater is almost a must have. This eliminates most missing code issues, slow lock programming response, and errors. For me I make sure I have either an Aeotec Range extender (s2) or a Z-Wave Smart plug between the lock and the HA device.
1 Like
I have 2 Zwave repeaters less than 5 feet from the lock. I think the biggest issue is that the lock that seems to have this issue the most is the most utilized. I’ve got 4 different Rental Controls integrations controlling different sets of slots on it and when codes are going in or coming out they’re doing it to 2 different locks on my mesh at the same time every time. Seems to do some funky things to this lock in particular.
Additionally, this lock is only 15ft from the controller.
In general, I don’t have issues, but it does happen sometimes.
Okay. Based on your comment, I bought an Kwikset HC-620 Z-Wave. I will be installing it Saturday.
Still, would love to see a matrix. 
Tried removing the spaces, but unfortunately still no notifications. No errors in the log, but no notifications.
Any suggestions on where to look next?
At this point do I need to try and remove and re-add the lock?
Problem is you used the UI editor to add the script. This usually causes the script name to not be what you’ve named it.
If you check the dev tools, you’ll likely find that script.keymaster_frondoor_manual_notifiy doesn’t exist.
I am reading the documentation included with keymaster in HACS and the “wiki”.
I am uncertain if the following steps are all I need.
I am running HAOS.
I have keymaster installed.
I have Z-Wave JS add-on installed (0.4.4).
I have Z-Wave JS integration installed.
The HACS Keymaster documentation state:
- add your devices to your Z-Wave network via the inclusion mode
- use the Home Assistant Entity Registry to rename each entity that belongs to the device and append
_LOCKNAMEto it. - This will automatically generate the keymaster files
- have to uninstall or disable your
zwavenetwork (from the wiki) - install
zwave-js-serverorozwdaemon(from the wiki)
What is zwave-js-server?
The only reference to Z-Wave Server on HA website where they seem to use Z-Wave JS driver, Z-Wave integration, and Z-Wave JS Server interchangeably.
If I have to uninstall one or both integration and add-on as per documentation,
- which one do I have to uninstall?
- will this impact my existing Z-Wave devices and connectivity?
- how can I tell what to install as
zwave-js-server, considering HA docs and Keymaster docs are using overlapping naming convention but there is no way to identify in HA installation which is which?
Thank you.
I think the wiki needs a bunch of work
Installation steps (going from memory but I’ve got 4 HA systems setup with KeyMaster, some with multiple installations)
- Be running HAOS (it’s easiest for everything)
- Create the
packagesdirectory inside yourconfigdirectory if it doesn’t already exist - Install Keymaster integration from HACS and reboot HA
- Have Zwave setup in HA, either using the default ZwaveJS add on which gets installed by default when you add the Zwave integration, or better, the Zwave JS UI add on
- Install the Zwave integration (if you haven’t yet, the previous step and this can effectively be in either order as not having a Zwave add on installed will cause the default one to get installed)
- Include your lock, you shouldn’t need to edit any entity names
- Install the Keymaster integration itself and tell it which lock to use, the configuration files will be automatically created in the
config/packagesdirectory and loaded if possible - Create a new dashboard and copy in the generated dashboard configuration or create your own custom dashboard.
Thank you. I do have keymaster working, and I am grateful for it.
I think the wiki needs a bunch of work
I think all of HA needs much of this. 
Maybe this your could be the “year of documentation”.
I could not find explanation for the various options that I got.
I make the assumption that the “Day”- and “Night Auto Lock” triggers a lock if the MagSensor status is closed.
What I do not grasp is what is difference between the two? Is “Day” stops the locking if unlocked? Is Night starts? Does it just do it once, or if mag sensor is closed, and unlocked, it will lock between the times?
I would be fine if it just got triggered say midnight once if the door is closed.
Alternatively, between time range if the door is closed per mag sensor
The day and night autolock options are how long to wait after the door sensor (looks like you’ve got it set as MagSensor) is closed before it tries to lock. If it fails to lock it will wait that amount of time again and then retry.
Day and night are defined as between sunrise and sunset for day and sunset to sunrise for night. The autolock timers only operate if you have the Auto Lock Enabled option turned on.
Personally, I stopped using the built in autolock bits as I had a lot of different things I wanted to do based on the status of the door. So I built my own automation. Same with the built in notifications system, I had enough logic around notifications that it was easier for me to just build my own.
Raman’s been working on a very nice integration, it doesn’t have all the feature sets KeyMaster has but those could be implemented via automations easy.
He’s leveraging the HA calendar for scheduling, very slick, recommend checking it out.
Oooo… interesting. Now how am I going to test this and make it another possible lock manager for Rental Control? My test system doesn’t actually have locks setup outside of a virtual lock!
You can run it along side of KeyMaster, they don’t bother each other, unless you try to change a slot’s code 
Yes, but I modify slot codes regularly via Rental Control
Hello All,
I have some Schlage locks, which are stuck always in “adding”. Install is up to date throug HACS. I have confirmed strong zwave signal, able to remotely lock/unlock almost immediately, and no zwave errors showing. Just switched from a 700 series controller to 800 controllers, and though the controller is faster, when I change a code, turn things on/off, I see no action. I’ve struggled with this in the past thinking it was my zwave mesh, but since then I have ruled that out.
Is there any guidance that I can receive to troubleshoot? Or a document that I can go through? Ive had this issue intermittently in the past, and its just a hard wall for me.
When you turn off the slot (so it should go to disabled) does it actually do that or does it stay in Removing state as well?
I’ve got one lock that consistently gets a bit stuck and all I (usually) have to do is just run a keymaster.refresh_codes service call against the lock.