Iām the breaking change guy. We are slowly moving more of the logic out of automations into code, so future releases may require package regeneration to essentially remove the automations that have been moved into code, but the entity names and your lovelace dashboard shouldnāt be changing anytime soon. The entity renaming effort was needed so that we could make the code easier to build.
so, i just switched from ozw 1.4 to the ozw integration (and i guess iāll be switching again once the new default is available, but thatās neither here nor there)ā¦
whatās the best way for me to change lock manager (or now keymaster) over from the old zwave entity to the new one? i changed the setup to use the new entities, but i still donāt think itās working correctlyā¦should i uninstall and reinstall keymaster?
Having some issues with notificationsā¦ Iām trying to get a notification for one user when the lock is used, and Iāve added the manual notify script to the keymaster_common.yaml file, but no luck actually getting a notification. lock notifications are enabled, but door notifications are not (not using a door sensor). Notifications are enabled for the code slot I want to notify.
My script code is as follows (just in case I botched it somehow)
frontdoor_manual_notify:
mode: parallel
sequence:
- service: notify.mobile_app_sm_n975u1
data:
title: "{{ title }}"
message: "{{ message }}"
Any help?
Hi,
I have a Z-Wave lock that is exposed to Home Assistant through the Fibaro HC2 integration. Do you think I could manage it using this?
Thanks 
Marc
Hello Everyone,
I find my status is often stuck on āConnectingā and never Connected. Iāve had a few times where it works for unknown reasons, but overallānot connected therefore new code are not synchronizing.
I am using OZW, and 1 lock connected for a few days and now it doesnāt, the newest lock has never connected, just stuck on Connecting. I can remotely lock/unlock the lock itself, so I know its connected with my zwave dongleā¦
Thoughts? How do I troubleshoot this?
Note: Schlage BE469
Thanks!
I really hope this isnāt a RTFM thing, but I am unable to edit any of the textbooks on the Lovelace dashboard for keymaster. I copied/pasted the generated code and can flip the sliders, but am completely unable to click in the input_text to set a name or PIN. I have tried chrome and safari and the home assistant app on osx and searched all over. Sorry for the dumb question, Iām sure itās an PEBKAC error, but I just canāt figure it out. Is anyone else able to tell me what Iām doing wrong?
Due to a weird quirk with the lovelace UI, you have to click where the word āPINā and āNameā are the first time editing.
1 Like
100% - thank you! It was only kind of a PEBKAC error!
1 Like
can anyone assist here? the status report definitely isnāt updating since i switched over so i definitely have to do something new, i just donāt know what it is.
also, i have installed it manuallyā¦i donāt have HACS installed. if that mattersā¦
Yeah, about that. Remove what you installed already and then install HACS. Use KeyMaster and not Lock-Manger. Read the Wiki to get started.
Just migrated from lock-master to keymaster. Noticed a couple things
-
numberbox-cardis required from HACS for the generated lovelace card. This wasnāt mentioned on the wiki at https://github.com/FutureTense/keymaster/wiki/Lovelace-View - I have 4 codes being set, and they all seem to connect, except code 4. But, it appears like there might be a entity mismatch, because Code 4 shows āconnectingā, but Code 5 (which has nothing), shows syncād.
Empty code slot + no PIN in UI = syncāed 
So thatās right.
As for slot 4, could be slowness with ozw/zwave not refreshing the slot code properly, only debugging messages can say for sure.
Weāll get that updated ASAP.
I set the input_number PIN value to the PIN that was already set, and it went in sync. I didnāt realize that I had a mismatch.
1 Like
i really donāt want to use HACS if i can avoid it. iāve got custom components and a somewhat complex docker install and i donāt want to go adding things that could cause me issues. much more controllable for me to just install it manually, especially so when i wouldnāt be using anything in HACS at the moment other than this. i see no reason to add two things when iām only going to use one.
i have had it installed manually this entire time and it works just fine this way, i just want to know what i need to do to make my lock work again now that iāve switched from the native zwave integration to the betaā¦
of course, if iām reading way too much into this and adding HACS doesnāt add that much complexity, please let me know. iām all ears. i just remember trying to use it previously and having it cause issues with my install / update process, so i gave up and installed manually.
Everything should be fine, the integration should swap between whateverās operational at the time, just reconfigure the integration with the sensors, unless theyāre the same names.
theyāre different names, but reconfiguring doesnāt seem to have worked. at least something wonky is going onā¦the status report definitely is not updating even though iāve reconfigured with the new lock entity name.
is removing the current version of lock-manager that i have installed and then installing keymaster from scratch my best way to go here?
You can give it a go, since itās the latest code base.
I added version v0.0.0.0.9 which reverts to an earlier version that works. We will make a fix and publish an update ASAP, but this should hold you over until then.
So not sure what the heck happened but suddenly my keymaster is having issues.
Iām running latest version from HACS and it was working just fine.
