Lock-Manager is now named KeyMaster
Lock-Manager is no more and will soon be removed from the HACS store. Taking its place is KeyMaster. The reason for the name change is a bit complicated, but in order to execute certain functions from automations, we had to remove the ‘dash’ from the integration name. We decided it was better to go full tilt and make the change obvious. I’ll post a “state of the integration” update when I find some time.
Excellent work to all of you and a huge thank you for everything you do for the community. This is a great project.
Is there a migration path between Lock-Master and Keymaster? Or is the recommendation to just uninstall Lock-Master and then install and configure Keymaster?
I also noticed that Keymaster isn’t publishing release versions yet. Will that be coming soon?
Since the input field names aren’t changing, the PIN and Name data should persist.
Your settings however, you’ll need to re-setup for the new integration, but that’s pretty trivial stuff.
Has anyone successfully got this working with Yale Zwave locks? I have 3 locks that each have the following entities attached:
zwave.lock_backdoor_2
sensor.lock_backdoor_alarm_level
sensor.lock_backdoor_alarm_type
sensor.lock_backdoor_battery_level
lock.lock_backdoor
I have Keymaster installed and configured, but it hangs on the “Pin Status: connecting” when trying to add a new code.
There was a bug with detecting zwave that should be resolved now, please update and see if the issue persists.
Not at homeat the moment, but I was able to update the integration. Upon rebooting the code that I tried setting earlier was suddenly accepted and the pin Status showed connected. However when I tried to reset it and put in another code it hung again at “connecting”…so I rebooted the server again and it once again accepted it. We’re getting closer? Lol…any suggestions?
That’s unfortunately the best case scenario with the old zwave integration. 
So Keymaster isn’t built to work with the baked in Zwave integration?
It is, but the zwave integration has many pitfalls, most obvious is the missing ability to actually delete most lock’s user codes.
Hi all, I’m getting super close to getting this working but I’m stuck somewhere.
I have a Kwikset 912, using OpenZwave on the “Core” VM install running on proxmox with an aeotek USB dongle passed through.
I can set codes via the debug tools and see them in the OpenZwave manager application, but the tools provided with the lovelace code cannot trigger a code change.
If I match what I’ve manually set via the debug tools and what the code slot reads via the keymaster page it will show connected, but I can’t toggle or change codes with it.
I spent a bit too much time on the clock at work digging through this but couldn’t make much headway on what I should do to start finding my problem.
I’ve confirmed: Allow_automations is enabled, but can’t find what else to do or what is a good start for debugging.
I did notice that an update was available and installed it.
I can lock & unlock the handle using the options on the entity for the lock, but can’t update codes except through the debug panel. An interesting observation as well: on the version from HAACS from roughly a week ago (I installed an update yesterday afternoon, and another today) would show the user code in the Code Slot X page, but wouldn’t pull into the lovelace panel, as of one of these two most recent updates that wasn’t happening until I used the debug page to push a new code to the lock.
Check the log for errors.
So far nothing shows up in the log when I interact with the lovelace panels, is there a way to verify the debug command took? I didn’t get any visual feedback or a line in the log when running the commands.
update: I was able to set a code by doing keymaster.add_code so I’m almost wondering if the UI part of the tool is somehow disconnected from the backend?
Thanks! That seems to have resolved the issue.
Yes, followed all directions, I now get a log with a DEBUG: Code slot X value: with the codes I set, and no new things appear when I mess with the toggles in lovelace.
Are you using zwave or ozw ?
OZW is what I have been using. followed the complete setup instructions on the wiki from github.
Does the integration work as expected under OZW? Will it allow me to clear/add codes on my Yale locks without having to restart the my HA?
AFIAK, in testing using OZW the locks performed exceptionally well.
The only problem I’ve noticed is sometimes the code slots wouldn’t update properly sometimes if you had an empty code slot in between used slots.
Exmaple:
Slot 1: Code
Slot 2: Code
Slot 3: <blank>
Slot 4: Code <-- sometimes wouldn't update on a code change/clear
Slot 5: Code
The issue isn’t the lock, but within OZW itself, as the lock would actually clear the code, but the info just wouldn’t update.