KeyMaster Z-Wave lock manager and scheduler

schwieb · December 10, 2021, 12:43pm

I figured out what I was doing wrong with the notifications! The installation wiki indicates creating this script:

<doorname>_manual_notify:
  mode: parallel
  sequence:
    - service: notify.phones
      data:
        title: "{{ title }}"
        message: "{{ message }}"

but you actually need to prepend ‘keymaster_’ to the script name like this:

keymaster_<doorname>_manual_notify:
  mode: parallel
  sequence:
    - service: notify.phones
      data:
        title: "{{ title }}"
        message: "{{ message }}"

To re-state the obvious, you also need to change the ‘doorname’ and ‘service’ section to your own specifications.

rct · December 11, 2021, 3:48pm

Migrating to ZwaveJS2MQTT, trying to setup KeyMaster per the documentation. I have Schlage BE469ZP deadbolts. While I have 16 entities for the lock, I don’t see a user code sensor or access control sensor. The entities I have are:

binary_sensor.mudroom_deadbolt_access_control_keypad_temporary_disabled
binary_sensor.mudroom_deadbolt_access_control_lock_jammed
binary_sensor.mudroom_deadbolt_home_security_intrusion
binary_sensor.mudroom_deadbolt_low_battery_level
binary_sensor.mudroom_deadbolt_power_management_replace_battery_now
binary_sensor.mudroom_deadbolt_power_management_replace_battery_soon
binary_sensor.mudroom_deadbolt_system_system_hardware_failure
binary_sensor.mudroom_deadbolt_the_current_status_of_the_door
lock.mudroom_deadbolt
sensor.mudroom_deadbolt_access_control_keypad_state
sensor.mudroom_deadbolt_access_control_lock_state
sensor.mudroom_deadbolt_battery_level
sensor.mudroom_deadbolt_home_security_sensor_status
sensor.mudroom_deadbolt_node_status
sensor.mudroom_deadbolt_power_management_battery_maintenance_status
sensor.mudroom_deadbolt_system_hardware_status

What am I doing wrong?

wittjosiah · December 11, 2021, 8:11pm

Thanks for making this great integration, it seems like exactly what I’m looking for to manage the pins on my locks.

I’ve been trying to set it up and while I’ve run into a few hurdles along the way I’ve managed to sort most of them out so far, however I’ve gotten a bit blocked and I’m not sure what’s wrong now. What’s happening is that all the pin statuses are always “Adding” or “Deleting” rather than “Added” or “Deleted”. I checked the locks and confirmed that there doesn’t seem to have been any changes to the codes as far as I can tell, it seems like they aren’t communicating. I saw this section in the wiki Troubleshooting · FutureTense/keymaster Wiki · GitHub but it hasn’t seemed to resolve itself.

As suggested, I’ve enabled debug logging (though I had to enable it system-wide as the service didn’t like when I pasted in the suggested yaml data). These are the logs that I saw which looked relevant to keymaster, but they don’t really seem to indicate much to me: 2021-12-11 14:35:59 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code - Pastebin.com.

Some other potential relevant details of my setup:

Locks are Yale Assure Lock SL Touchscreen Deadbolts
Running on a Raspberry Pi 3 with HomeAssistant OS (version 6.6)
Core is version core-2021.11.5 and Supervisor is version supervisor-2021.12.1
Using an Aeotec Z-Stick Gen5
Setup with ZwaveJS addon/integration (version 0.1.50)

Does anyone have any suggestions on what I should try to get it working? Thanks!

firstof9 · December 13, 2021, 2:51am

Nothing your lock emits events, so set those entries to sensor.fake

firstof9 · December 13, 2021, 2:57am

Go to Link to Info – My Home Assistant and see what the keymaster section says under system health.

Example:

wittjosiah · December 13, 2021, 12:53pm

Yup, I see the same in that section:

Screenshot from 2021-12-13 07-51-24

billr · December 13, 2021, 3:21pm

I am having the exact same issue with it hanging on “Adding”.
I am using a Yale YRD216 lock. The only thing I noticed was that when pairing it through Z-wave, it failed secure enrollment. It still added it, so I simply continued. I wonder if this is causing the problem?

schwieb · December 13, 2021, 3:27pm

I was having similar troubles as @wittjosiah until I updated to zwave-js 1.50. Incase you havent done that, give it a try.

billr · December 13, 2021, 3:53pm

Thanks for the suggestion @schwieb . I’m already using a fresh HA install with zwave-js 1.50

wittjosiah · December 13, 2021, 7:49pm

Interesting, that definitely sounds plausible to me. This is what my lock shows on it’s device page:

IIRC S0 means it wasn’t securely added but I didn’t see a separate option to secure add in Zwave JS like in the old Zwave integration. I assume ZwaveJS supports secure inclusion if others have gotten it working though, is there something special that needs to be done here?

billr · December 13, 2021, 8:11pm

Mine looks worse:
(I’m certain it failed secure enrollment)

I’m going to try to unpair/re-pair the lock now that I’m roughly 5 feet from the lock.

schwieb · December 13, 2021, 8:37pm

I recommend that you unpair, completely re-set the lock, and then re-pair again.

firstof9 · December 13, 2021, 8:40pm

Yes you have to have a secure connection in order for the lock to properly operate via zwave.

billr · December 13, 2021, 8:50pm

Just got it to add securely. I think distance was my original problem. I’ll likely permanently resolve it with a repeater, but for now, the HA instance is a few feet away. My debugging logs look a lot more promising, but now, codes are stuck on “deleting”.

I think I need to wipe the slate clean and start fresh

firstof9 · December 13, 2021, 8:52pm

All powered zwave nodes are repeaters, far better to just get a light switch or a plugin outlet to be a repeater, and be useful.

schwieb · December 13, 2021, 9:22pm

You may be alright now that you have successfully paired the lock securely. I know that the Kwikset lock has a ‘whisper’ function used during pairing to reduce the risk of someone outside intercepting your pairing. Once I synced my locks by having the hub closeby, I was able to move it back where it was in my data closet. Not sure if this is also true for your particular lock.

billr · December 13, 2021, 10:17pm

Just wanted to close the loop with my issue. Once I moved the HA box closer and re-paired the lock, it securely enrolled. I was then able to re-add the integration and everything worked as it should.

ThaNerd · December 23, 2021, 1:37pm

I tried the manual notify but it kept triggering none stop…
I am not familiar with this “mode: parallel”, how does it work?

keymaster_frontdoor_manual_notify:
  mode: parallel
  sequence:
    - service: notify.all_mobile_devices
      data:
       title: "Someone Unlocked The Doors"
        message: "Someone Unlocked The Front Door"

wittjosiah · December 27, 2021, 6:08pm

I’m circling back around to this again, I’m curious what security level is require for this to work. With the S0 Legacy security it still doesn’t seem to be working for me.

coolva · December 27, 2021, 6:36pm

Mine seems to work fine…