KeyMaster Z-Wave lock manager and scheduler

Share your Projects!
2263

Hello, I wanted to come back around to this addon as the last time I tried it a few months ago, it never worked correctly with my lock (BE469WK V CAM 619). It’s unclear as to why this is (if it was a HA, addon, or zwave issue), but I wanted to link this dude’s github that was used on SmartThings: https://github.com/ethayer/lock-manager

I know that they are completely different technologies and nothing might be gained from it, but I wanted to pass this along in case there was anything that could be gleaned from it that might help in situations where the Schlage BE469 locks were involved, as mine always worked flawlessly with those.

Feel free to ignore this if you don’t think it’s helpful!

2264

Hi All,

I initially installed my front door lock (Schlage BE469ZP) in Feb 2020 and set it up in Home Assistant. The first time I had to replace the batteries was in Feb of this year. Now I have replaced them in May & in August. They only seem to be lasting around 3 months now.

Has anyone else seen this happen? I am not suggesting it is anything to do with this project just curious why all of a sudden I would see this sudden consistent battery drain

2265

You may want to check to see if you’re Polling the device and turn it off if it is.

2266

OK Thank You,

How do I do that ?

2267

Not sure which z wave integration you have, but I found this one for the old Z wave integration: Z-Wave - Home Assistant

I’m not sure how it would be adjusted for Z wave JS

2268

Yes I am still running the original Z-Wave intergration

image
image708×113 4.51 KB

Do you know what value needs to be added to turn polling off? Currently I do not have anything to do with polling in my configuration.yaml

2269

Sorry, I’ve never done it before, but I think it’s this one: Z-Wave - Home Assistant

2270

Thanks for this,

I see there is an option to add the following:

image

All I have currently in my config is the USB path and the network key. Maybe someone else can comment is the polling_intensity line neccessary (it states default: 0 which is no polling)

Appreciate your help though

2271

Upgrading to zwavejs is your best option at this point.

1 Like
2272

Just wondering but how would one go about having the alarm on their house disarm but only when a certain code is used, say slot 2?

2273

Create an automation to catch unlock events for that slot. I don’t know if this actually works. I just kinda winged it.


  - alias: keymaster_frontdoor disable alarm when unlocking slot #2
    trigger:
      platform: event
      event_type: keymaster_lock_state_changed
      event_data:
        lockname: frontdoor
    condition:
      - condition: template
        # Check for Keypad Unlock code and slot #2
        value_template: >-
          {{
            trigger.event.data.code_slot == 2
            and
            (trigger.event.data.action_code is undefined or trigger.event.data.action_code in (6, 19))
          }}
    action:
      - service: script.turnoff_alarm

@firstof9 and @raman325 might offer a better version, as the underlying zwave functions might work better.

2274

BTW, I changed the autolock functionality a tad. If you open the door, the autolock timer resets. It was a pain locking on me for multiple in/outs.

1 Like
2275

I am running core-2021.9.7, OS 6.4, with zwavejs2mqtt 0.25.0 and the zwave integration talking to zwavejs2mqtt over websockets. I just upgraded to the above from the legacy zwave 1.4 implementation. I copied my key from the original implementation into the S0 legacy key in zwavejs2mqtt. All of my devices have reappeared and are connected to home assistant.

I have two Yale Security YRD226 locks. Both of them were working perfectly with KeyMaster and the old zwave implementation. Now they show up in zwavejs2mqtt with security ‘S0_Legacy’. However the only entities that show up in home assistant are: lock.front_door_lock, sensor.front_door_lock_node_status, binary_sensor.front_door_lock_the_current_status_of_the_door and I can’t even lock and unlock the lock using lock.front_door_lock.

Any thought on what I need to do to get KeyMaster to work with my locks again? Do I need to rejoin these devices with S2 security?

Thanks in advance!

2276

The easiest thing to do is exclude your locks, factory reset them, then reinclude. Then install the integration. It’s what always works for me.

2277

Thanks - I’ll start with this and see how it goes - appreciate it.

2278

This seems to have worked. I’ll post if anything changes. Thanks!

2279

I am looking to change the auto-lock timeouts for my locks from the default 15min and 5min to 1min and 30 seconds respectively. I have tried changing their respective input text values (input_text.keymaster_front_door_autolock_door_time_day and input_text.keymaster_front_door_autolock_door_time_night) from the lovelace badges which works for about a day and then they get reset for some reason back to 15 and 5. Is this the right place to change the timer lengths or is there somewhere else I should look?

Thanks in advance!

2280

Hi. I have a question about the door sensor in the lock configuration. I have an Elk M1 alarm system that has sensors for all my doors. The values of these sensors is either normal or violated, and none of the alarm sensors are available in the entity autofill entry for the door sensor in the lock config. These locks are Yale YRM476 type, and they don’t have a door state sensor available from the lock.

What should I do to be able to use the door sensors on my alarm? I guess I can try and make a binary sensor based on the value of the alarm sensor, but how should it be defined? On = door open or door closed, etc…?

thanks!

2281

On = opened

2282

Thanks. I think I can make a template automation to translate normal/violated to off/on. BTW, does keymaster only allow the use of binary sensors for door status?