blueprint:
name: Yale Lock User Code Actions (ZWave-JS)
description: Perform action based on code slot that unlocked door
domain: automation
input:
yale_lock:
name: Yale Lock
description: List of available Yale Locks
selector:
device:
integration: zwave_js
manufacturer: Yale
manual_lock:
name: Manual lock Operation
description: Manually locking thumbturn
default: []
selector:
action: {}
manual_unlock:
name: Manual unlock Operation
description: Manually unlocking thumbturn
default: []
selector:
action: {}
user_1:
name: User Code Slot 1
description: First Usercode Slot
default: []
selector:
action: {}
user_2:
name: User Code Slot 2
description: Second Usercode Slot
default: []
selector:
action: {}
user_3:
name: User Code Slot 3
description: Third Usercode Slot
default: []
selector:
action: {}
user_4:
name: User Code Slot 4
description: Fourth Usercode Slot
default: []
selector:
action: {}
user_5:
name: User Code Slot 5
description: Fifth Usercode Slot
default: []
selector:
action: {}
user_6:
name: User Code Slot 6
description: Sixth Usercode Slot
default: []
selector:
action: {}
user_7:
name: User Code Slot 7
description: Seventh Usercode Slot
default: []
selector:
action: {}
user_8:
name: User Code Slot 8
description: Eighth Usercode Slot
default: []
selector:
action: {}
user_9:
name: User Code Slot 9
description: Ninth Usercode Slot
default: []
selector:
action: {}
user_10:
name: User Code Slot 10
description: Tenth Usercode Slot
default: []
selector:
action: {}
user_11:
name: User Code Slot 11
description: Eleventh Usercode Slot
default: []
selector:
action: {}
user_12:
name: User Code Slot 12
description: Twelfth Usercode Slot
default: []
selector:
action: {}
user_13:
name: User Code Slot 13
description: First Usercode Slot
default: []
selector:
action: {}
user_14:
name: User Code Slot 14
description: First Usercode Slot
default: []
selector:
action: {}
user_15:
name: User Code Slot 15
description: First Usercode Slot
default: []
selector:
action: {}
user_16:
name: User Code Slot 16
description: Sixteenth Usercode Slot
default: []
selector:
action: {}
user_17:
name: User Code Slot 17
description: Seventeenth Usercode Slot
default: []
selector:
action: {}
user_18:
name: User Code Slot 18
description: Eighteenth Usercode Slot
default: []
selector:
action: {}
user_19:
name: User Code Slot 19
description: Nineteenth Usercode Slot
default: []
selector:
action: {}
user_20:
name: User Code Slot 20
description: Twentieth Usercode Slot
default: []
selector:
action: {}
user_21:
name: User Code Slot 21
description: Twenty-first Usercode Slot
default: []
selector:
action: {}
user_22:
name: User Code Slot 22
description: Twenty-second Usercode Slot
default: []
selector:
action: {}
user_23:
name: User Code Slot 23
description: Twenty-third Usercode Slot
default: []
selector:
action: {}
user_24:
name: User Code Slot 24
description: Twenty-fourth Usercode Slot
default: []
selector:
action: {}
user_25:
name: User Code Slot 25
description: Twenty-fifth Usercode Slot
default: []
selector:
action: {}
user_26:
name: User Code Slot 26
description: Twenty-sixth Usercode Slot
default: []
selector:
action: {}
user_27:
name: User Code Slot 27
description: Twenty-seventh Usercode Slot
default: []
selector:
action: {}
user_28:
name: User Code Slot 28
description: Twenty-eigth Usercode Slot
default: []
selector:
action: {}
user_29:
name: User Code Slot 29
description: Twenty-ninth Usercode Slot
default: []
selector:
action: {}
user_30:
name: User Code Slot 30
description: Thirtieth Usercode Slot
default: []
selector:
action: {}
mode: single
max_exceeded: silent
variables:
device_id: !input 'yale_lock'
trigger:
- platform: event
event_type: zwave_js_notification
condition: '{{ trigger.event.data.device_id == device_id }}'
action:
- variables:
user_code: '{{ trigger.event.data.parameters.userId }}'
lock_operation: '{{ trigger.event.data.event_label }}'
- service: logbook.log
data:
name: User Code
message: '{{ user_code }}'
- service: logbook.log
data:
name: Device
message: '{{ device_id }}'
- choose:
- conditions: '{{ trigger.event.data.event_label == "Manual lock operation" }}'
sequence: !input 'manual_lock'
- conditions: '{{ trigger.event.data.event_label == "Manual unlock operation" }}'
sequence: !input 'manual_unlock'
- conditions: '{{ user_code == 1 and lock_operation == "Keypad unlock operation" }}'
sequence: !input 'user_1'
- conditions: '{{ user_code == 2 and lock_operation == "Keypad unlock operation" }}'
sequence: !input 'user_2'
- conditions: '{{ user_code == 3 and lock_operation == "Keypad unlock operation" }}'
sequence: !input 'user_3'
- conditions: '{{ user_code == 4 and lock_operation == "Keypad unlock operation" }}'
sequence: !input 'user_4'
- conditions: '{{ user_code == 5 and lock_operation == "Keypad unlock operation" }}'
sequence: !input 'user_5'
- conditions: '{{ user_code == 6 and lock_operation == "Keypad unlock operation" }}'
sequence: !input 'user_6'
- conditions: '{{ user_code == 7 and lock_operation == "Keypad unlock operation" }}'
sequence: !input 'user_7'
- conditions: '{{ user_code == 8 and lock_operation == "Keypad unlock operation" }}'
sequence: !input 'user_8'
- conditions: '{{ user_code == 9 and lock_operation == "Keypad unlock operation" }}'
sequence: !input 'user_9'
- conditions: '{{ user_code == 10 and lock_operation == "Keypad unlock operation" }}'
sequence: !input 'user_10'
- conditions: '{{ user_code == 11 and lock_operation == "Keypad unlock operation" }}'
sequence: !input 'user_11'
- conditions: '{{ user_code == 12 and lock_operation == "Keypad unlock operation" }}'
sequence: !input 'user_12'
- conditions: '{{ user_code == 13 and lock_operation == "Keypad unlock operation" }}'
sequence: !input 'user_13'
- conditions: '{{ user_code == 14 and lock_operation == "Keypad unlock operation" }}'
sequence: !input 'user_14'
- conditions: '{{ user_code == 15 and lock_operation == "Keypad unlock operation" }}'
sequence: !input 'user_15'
- conditions: '{{ user_code == 16 and lock_operation == "Keypad unlock operation" }}'
sequence: !input 'user_16'
- conditions: '{{ user_code == 17 and lock_operation == "Keypad unlock operation" }}'
sequence: !input 'user_17'
- conditions: '{{ user_code == 18 and lock_operation == "Keypad unlock operation" }}'
sequence: !input 'user_18'
- conditions: '{{ user_code == 19 and lock_operation == "Keypad unlock operation" }}'
sequence: !input 'user_19'
- conditions: '{{ user_code == 20 and lock_operation == "Keypad unlock operation" }}'
sequence: !input 'user_20'
- conditions: '{{ user_code == 21 and lock_operation == "Keypad unlock operation"}}'
sequence: !input 'user_21'
- conditions: '{{ user_code == 22 and lock_operation == "Keypad unlock operation"}}'
sequence: !input 'user_22'
- conditions: '{{ user_code == 23 and lock_operation == "Keypad unlock operation"}}'
sequence: !input 'user_23'
- conditions: '{{ user_code == 24 and lock_operation == "Keypad unlock operation"}}'
sequence: !input 'user_24'
- conditions: '{{ user_code == 25 and lock_operation == "Keypad unlock operation"}}'
sequence: !input 'user_25'
- conditions: '{{ user_code == 26 and lock_operation == "Keypad unlock operation"}}'
sequence: !input 'user_26'
- conditions: '{{ user_code == 27 and lock_operation == "Keypad unlock operation"}}'
sequence: !input 'user_27'
- conditions: '{{ user_code == 28 and lock_operation == "Keypad unlock operation"}}'
sequence: !input 'user_28'
- conditions: '{{ user_code == 29 and lock_operation == "Keypad unlock operation"}}'
sequence: !input 'user_29'
- conditions: '{{ user_code == 30 and lock_operation == "Keypad unlock operation"}}'
sequence: !input 'user_30'
6 Likes
Doesnāt work for my Yale lock because the manufacturer is actually ASSA ABLOY. Can you update the blueprint to support this manufacturer (I think they are the parent company perhaps?).
My Assure locks all show up being made by Yale, and yes Assa Abloy is the parent company but this selector is defined by what is read by ZWave-JS. Until we get an āorā selector I donāt think supporting multiple manufacturer names would be possible. I could also only select a device class of ālockā but not all locks support these events and so I wouldnāt want people to get confused by trying to use this blueprint and it not really being supported. You are welcome to create a new blueprint for your locks and just make a copy of this one with the changes you need.
This worked perfect for my Yale lock which shows up as ASSA ABLOY. I am using ZWave-JS MQTT version as an integration. Perfect for letting me set automations when our house cleaner shows up! I also set to alert me if we are gone with a notice to the HA app with whos code was entered. Need to figure out additional to send me the capture of the entry camera. But @Nixon506E this is a great Blueprint!!!
Does this have to utilize the ZWave-JS integration locally on HA? Or will it work if I just point my ZWave-JS server to my HA MQTT? I imported it, but itās not detecting any locks.
Disregard. I installed the Z-Wave-JS integration and configured the websocket server to point to the docker instance I have running on another server, and it found my lock. Excellent work!
Apparently there was a breaking change in 2021.4 that made this blueprint non-functional. After some digging and trial and error the ultimate solution to get this working again is pretty simple.
change zwave_js_event to zwave_js_notification
change trigger.event.data.label to trigger.event.data.event_label
Thanks for the tip @tehkurt - I managed to get this blueprint working with your changes but when I enter a user code on the lock, I get this warning in the log:
Logger: homeassistant.helpers.template
Source: helpers/template.py:1366
Template variable warning: 'dict object' has no attribute 'userId' when rendering '{{ trigger.event.data.parameters.userId }}'
I think it has something to do with the user_code variable. It looks like it should be changed to this:
user_code: '{{ trigger.event.data.parameters["userId"] }}'
which also works but the warning in the log persists.
Any help appreciated.
Can anyone confirm if this works with the l1 Conexis yale lock?
iām currently still on the deprecated z-wave and have been hesitate to move over because I have a number of automations that trigger based on who unlocked the door.
cheers
++me also with the l1 Conexis yale lock. I did upgrade to zwavejstomqqt - and the lock is rediscovered and works well (fyi @tehkurt I had to repair it and fiddle a bit but it works)
Hi
If your on the new version of zwave arenāt you able to test it?
I will try and report back.
1 Like
Hey,
How did you get on?
Is there any way to add an action to the blueprint to be called when the lock goes from an āunlockā to a ālockedā state?
Thanks for this. Bloody handy! Had to modify one line to:
trigger.event.data.parameters["userId"]
Any chance you could add a conditions field so I can mimic what I used to have and only perform the actions if the alarm is set?
My suggestion is to make a simple automation to do that.
It would be to specific an action to change the blueprint for.
Pretty specific for a general blueprint.
Would be pretty easy to add this to the copy you use, though. Since it would be just for you you wouldnāt have to ad inputs or anything, just another condition.
While I understand I can just create a standalone automation (which is the way I am doing it now), I thought it would be a cleaner approach to have the ability built into the blueprint.
The blueprint is able to handle a number of āunlockā conditions but canāt handle a ālockā condition, seems like it would have been a popular feature (to act upon the lock becoming ālockedā
Thanks,
Thanks, Iāll see if I can figure that out.
how do import this or do i created a new in YAML ?