Please forgive me if I am in the wrong area for this post. I have discovered something that appears to be a bug and I don’t know where I should report this.
Anyway, today I was editing some of my automations and found that when I try to define a trigger for a Z-Wave switch, I can no longer set the Value using the drop-down that HA provides. The options are listed in the drop-down but when I select any one of the options nothing is retruned to the Value field. This used to work but now it doesn’t.
I have attached a screen shot of the dialog I am using:
No matter what I select, it is not displayed in the Value field. I have a number of automations that use the KeyPressed, and KeyPressed2x options. This has allowed me to control multiple things from a single switch. But now that seems to be broken.
When viewing the YAML for my automations, the “value:” entry under the “triggers:” section is now missing.
I can only assume that a recent update caused this as it used to work. Has anyone else experienced this?
Unfortunately, clearing the browser cache didn’t fix the problem.
alias: Master Suite Bathroom - Exhaust Fan Switch OFF 1X
description: Single-tap switch triggered automation that turns the exhaust fan OFF.
triggers:
- device_id: 7f04ae2dec78a95031e29209596b0fdf
domain: zwave_js
type: event.value_notification.central_scene
property: scene
property_key: "002"
endpoint: 0
command_class: 91
subtype: Endpoint 0 Scene 002
trigger: device
value: 0 <===== I added this line back into my YAML
conditions: []
actions:
- action: script.1695752159108
metadata: {}
data: {}
mode: single
However, I edited the YAML and added the “value: 0” manually and now my automation is working. But when I try to edit the automation using the GUI the value is not shown in the Value field. And when I select a new value it is not displayed in the Value field.
I manually edited all of my other automations and now my system is working. I hope this is addressed in a future update.
I am having the same issue with the automation UI, also with my Zooz switches. It was after updating to Home Assistant 2026.3.1 when this issue started. I reverted to a pre-update backup (2026.2.1) and the UI works as expected, so definitely looks to have been introduced in one of the recent updates.
Yeah, I’m using Zooz also. Being able to double-tap, or tripple-tap a switch to trigger an automation is a really great way to get extra functionality from a wall switch. But this HA GUI bug is making it difficult.
