@bravenel After updating to this release I'm finding that setting a varialbe trigger with stay is no longer working. Example showing that there was no "stay" when triggered.
Also of note, this example isn't working either, something seems to be wonky with variable triggers. In this example test variable set as "stop" shouldn't trigger, but it does
Did not work after .157 but prior to newest z-wave firmware. After firmware update continued to not work.. After .157 and z-wave firmware things just got worse.. all (11) z-wave LR's showed pending and never became active (18+ hours).. The message in the logs revealed that the trigger event errored-out.. Rule 5.1 "Select Trigger Events" is "Motion Sensor Reset (off) turns on and Stays That Way for 0:00:05" whereas the device is a virtual device based on a system variable.. The trigger event controls 11 Homeseer HSM200 led lights.. I could manually change the led off/on and the actual color selected so i know it was not the devices.. I have read that there is now a problem with certain led lights with the newest z-wave firmware but again i tested without the latest firmware installed and the rule continued to throw an error.. To reiterate, the error occurred on "Select Trigger Events" and i would normally not be alerted in the logs whether the trigger event executed or not..
Briefly all z-wave LR's are a combination of Zooz Zen04 ZSE41 and ZSE11.. Rolled back the firmware update.. Trigger event continued to error-out even after a hubitat reboot..
End result, I did a cloud backup just prior to the update which was based off-of .151 and wound up restoring such.. i did not install .152 thru .156 because i did not like the feedback being provided on those variants.
You haven't providing any information that we can act on to figure out what the problem is. Please show the rule that fails, and the error from the logs.