I don’t think this is an Enbrighten Zwave issue but more me doing something wrong in my automation. HA can detect through Z-Wave JS UI that a the momentary toggle is pressed up or down and will display it in the devices events. Because the up and down press are detected as different scenes in the switch I’m trying to use one automation to turn on or off other devices.
I’m going to assume your trigger isn’t working reliabily. The problem is event entities don’t trigger like you would expect them to. If you add an attribute to the state trigger, it will only trigger if the attribute changes (according to the docs). So multiple KeyPressed events in a row will not trigger, but if you double press (changes attribute) and press again it will start to work. For event entities I find this very annoying and un-intuitive.
Delete the attribute from the trigger so that it triggers on the state (event timestamp). Then check the attribute value in the conditionals instead. It will look something like this, which I took from the example in the docs.
And if you don’t care about the downsides of device automations, it’s easier to use the built-in central scene triggers, which work the way you expect, as events don’t rely on any kind of changing state, they just trigger.
This one seems to have an issue as well if I do both of them like the below, I think that because the both keypressed event HAVE happened at some point in time it chooses the first one. I think if I add the ID back to the choice, it will then know which once triggered the automation.