KeyMaster Z-Wave lock manager and scheduler

Thanks for the post above. I was able to get the notifications working decently with. Now to figure out how to customize it so it will post the time/date when they unlocked the door.

sequence:
  - data:
      title: "{{ title }}"
      message: "{{ message }}"
    action: notify.pushover
alias: keymaster_yale_front_door_manual_notify
description: ""

I am not a pro, but I’ll try to help. There may be better ways. You’ll have to play with templating.

You will have to customize the {{ message }} part. Either by looking up where that variable is set (there are a couple of automations that keymaster generates), or by appending/prepending another template to it for the time.

I think something like this would work:

sequence:
  - data:
      title: "{{ title }}"
      message: "{{ message }} at {{ states.sensor.time.state }}"
    action: notify.pushover
alias: keymaster_yale_front_door_manual_notify
description: ""

Note - the previous sensor mentioned has to be turned on with the time_date integration. There are a few options for time, date, or time and date that you can pick from or add to eachother to get the format you want for the notification.

Here are a couple places to start learning about templating time and the keymaster notifications:
https://www.home-assistant.io/docs/configuration/templating/#time
https://community.home-assistant.io/t/keymaster-z-wave-lock-manager-and-scheduler/166419/2996?u=cake1468
https://community.home-assistant.io/t/the-epic-time-conversion-and-manipulation-thread/85786/4

1 Like

I have installed appdaemon.
I am not sure where to paste the code from above.
Can you advise or point me to where I can learn?

Did this solution work for anybody?
I just spent 6 hours leaning how AppDaemon and implementing this py script.
And my locks are still hanging on Adding and Deleting…

Believe it or.not, I wrote 85% of KeyMaster on an iPad.

2 Likes

I couldn’t figure out how to get Keymaster to output notifications so I made a self-contained automation that uses zwave_js_notification. And it works well and is not reliant on Keymaster. I hope the beta comes out soon since the current version is difficult to figure out - I’ve installed it twice, never works.

Door codes on the lock that ā€˜seems’ to work (no keymaster errors) never populate and the other lock gets nothing but errors (works fine in Zwave JS) but oddly it correctly shows the lock/unlock status on screen… everything else as yo u can see is just errors.

I just dont trust KM at this time.

Plus I dont get why there isnt a stock Keymaster notification since it seems like nearly everyone would want one (mobile, persistent, etc) to know who and when doors unlock/lock. I tried some code floating around in this thread and it never worked for me.

That’s why you got more skills than me!! LOL!!

HACS changed how to get to betas, you have to turn it on via the HACS integration in Devices and Services.

Once you are in HACS from Devices and Services click here:

Find keymaster in the list and click it, once in there toggle on Pre-Release:

Then the beta will show up.

I’m seeing a beta a 0.99-b0 updated 8 months ago. Is this the recommended beta?

As long as you’re not trying to use Rental Control with Keymaster, then yes, I would recommend picking up the beta. It cleans up the entities significantly and my original testing with my test setup showed that it responded better and seemed less likely to wedge than current mainline release.

1 Like

Hi Andrew, Thanks for the Add-On.

Issue I have encountered when trying to add iCal link from Google calendar:
Rental control does not create the main calendar ā€œOn/Offā€ entity, and the events entities remain ā€œunavailableā€.

The iCal link from Airbnb works normally.

I guess the add-on cannot parse the secret/private links from google calendar.
Airbnb can share public links, since no guest information is included in the description.

Do you think there might be a solution in the near or coming future?

Thanks.

@eli-pavlov this thread is for KeyMaster :wink: I suggest you ask on the Rental Control thread itself. But I’ll answer anyway since I’m the creator of Rental Control.

The integration works just fine with Google Calendars. I use it that way in all of my properties for maintenance company access as well as in my testing setup.

Please see the FAQ in the README on How do I use custom calendars?. As an FYI RC will not allow you to save a calendar URL if it cannot validate that the URL returns cleanly. So, if you have managed to get RC to fully register, then the issue is in how you are creating your events.

1 Like

Thanks a lot Andrew.

Considering that 0.0.99 is out, is there any reason to be on the b0 version?

If you don’t use Rental Control to drive locks for STR or other reasons then hopping on the beta will get you a cleaner configuration. I only say this because Rental Control relies on Keymaster to drive code automation for STR and I still haven’t gotten a version out that supports the updates made in the beta as it makes some significant changes to certain workflows that I haven’t exactly worked out yet cleanly.

I don’t use Rental Control. Cleaned up entities was my goal. The version numbering, and release date is what confused me as well as similar release notes. Makes it appear that 0.0.99 succeeds 0.0.99-b0, but it sounds like are ā€œimprovementsā€ in -b0?

Yes, definite improvements. All of the entities get attached to a device. All of the input_<type> entities are done away with instead there are corresponding <type> entities that are attached to the device. My experience while testing it is that it tends to be less likely to have an issue getting a code added or removed. Admittedly the testing on that was a lot less rigorous as I don’t have it in play anywhere currently as I need Keymaster for Rental Control

Is there anything necessary to migrate other than redownload in hacs? Looks like there are still a bunch of automations, scripts, and helpers. They still hang around?

I have a bunch of input_datetime. and other helpers. Would they go away?

IIRC the process was: install via HACS, restart. Once HA completed starting restart one more time as some stuff doesn’t quite migrate cleanly on the first restart.

1 Like

I tried looking through the form but couldn’t find anything on my issue. I believe I followed all the steps to setup keymaster correctly but I am getting ā€œEntity not foundā€ where I believe the ā€œpin statusā€ and " pin state" should be. I’m wondering if my locks are just not compatible? They are Schlage Connect Z-wave Plus

EDIT:
well I restarted Home Assistant and that fixed the first issue. Now I have a different issue where Pin Status is stuck deleting