Hi all,
I’ve been lurking reading and learning for a while now, and thought I was getting the hang of HA and Z-Wave, but I’m stuck and would appreciate some help. I’m running home assistant OS 16.3 and Core 2025.12.5 in VMware running on a window 11 laptop using a Zooz 800 Series USB Stick.
I just installed 2 Eaton z-wave RF-9643-N dimmers and I have 4 z-wave enabled deadbolts in the house. My goal is to have the kitchen door deadbolt turn on the dimmer switch in the kitchen when the lock is unlocked from the keypad.
Of the 4 locks, the front door is a Yale Assure Lock Touchscreen Deadbolt. The remaining 3 are Kwikset 914s that I added a z-wave module to I found on Amazon. (Home Connect Lock Module, Rf Z-Wave Chip REV 3.8 for Kwikset Models 909, 910, 911, 912, 913, 914) The Z-wave device page shows them all identifying as 912 locks. I control all 4 locks using Keymaster. After reading all the posts I could find I put together this automation.
alias: Kitchen Light on with remote Kit door unlock
description: ""
triggers:
- device_id: 70b578de08fbcd9a89b7062e6bd86174
domain: zwave_js
type: event.notification.notification
command_class: 113
trigger: device
type.: "6"
event: "4"
conditions: []
actions:
- action: light.turn_on
metadata: {}
target:
entity_id: light.z_wave_plus_universal_smart_dimmer
data: {}
mode: single
It works if I unlock via HA, but not with the keypad which is what I expected. to make it recognize the keypad unlock, I thought it would be as easy as changing event from “4” to “6” but no luck. After lots of failed attempts I decided to try and use the front as the trigger and the following code worked fine, and turned the light on in response to a keypad unlock.
alias: Front door trigger light
description: ""
triggers:
- device_id: 3f077f536e6b5d2ce85c94c801f1abc4
domain: zwave_js
type: event.notification.notification
command_class: 113
trigger: device
type.: "6"
event: "6"
conditions: []
actions:
- action: light.turn_on
metadata: {}
target:
device_id: ed6755d341176a11ee0b1ac15cbd5fb7
data:
transition: 0
brightness_pct: 50
mode: single
Since that worked exactly as planned. So I used the same code with the kitchen lock device ID for the Kwikset kitchen door lock.
alias: Kitchen light on kitchen keypad unlock
description: ""
triggers:
- device_id: 70b578de08fbcd9a89b7062e6bd86174
domain: zwave_js
type: event.notification.notification
command_class: 113
trigger: device
type.: "6"
event: "6"
conditions: []
actions:
- action: light.turn_on
metadata: {}
target:
entity_id: light.z_wave_plus_universal_smart_dimmer
data: {}
mode: single
But the light doesn’t come on.
More reading the posts leads me to the developer tools events page where I listened to * and for the Kwidset locks I can see the RF lock and unlock messages and I can see the Keymaster lock state changed message that go with the RF lock/unlock. However, if I make a manual lock action or a keypad lock action I see no events from any of the Kwikset locks, but I do see manual and keypad actions for the Yale lock.
I’ve looked at the z-wave configuration pages for the Yale and Kwikset locks and nothing jumps out at me as different between them. I’ve noticed for the Kwikset locks the Keymaster status is usually (maybe always) wrong after manual or keypad changes until I re-interview the device or take a HA lock/unlock action that “fixes” the false state to true.
Any suggestions on how to get the Kwikset deadbolts communicating on Z-wave for manual and kepad actions are greatly appreciated. If I can fix this, I think I can get the automation working.