I just got a new Hank 4 button controller, I got everything working the way I wanted by keying off of the action_name field and scene_id I can fire diferent automations for single vs hold events. I foolishly then decided to upgrade Home Assistant and my automations no longer work. I noticed when looking at the zwave_js_value_notification event that the action_name field is no longer there.
I could probably change my automation to trigger off of the value field, 1 seems to be single press, 2, hold, 3 release. But I am wondering what has changed.
event_type: zwave_js_value_notification
data:
domain: zwave_js
node_id: 12
home_id: 3674734580
endpoint: 0
device_id: d48cb0cda28de88a8f0be0fa57b6dba3
command_class: 91
command_class_name: Central Scene
label: Scene 003
property: scene
property_name: scene
property_key: "003"
property_key_name: "003"
value: 1
value_raw: 1
origin: LOCAL
time_fired: "2022-10-08T23:36:01.054738+00:00"
context:
id: 01GEWZ98RYTJ19YHPQM5A3J4MK
parent_id: null
user_id: null
You can download the Device diagnostic file and see what is listed for the Central Scene metadata. If it doesn’t show those strings, I would try a re-interview.
You could also switch to using the value_raw field which would be resilient to any kind of metadata issues. This is the mapping of strings to raw values:
Look in the Device diagnostic file (from the device page). If the metadata is missing, then likely an interview error. You’d have to look in past logs to see that. If you’re using the core add-on, then there are no past logs.