So both of these are trigger comparisons, so they will only possibly be checked if that is the cause for the piston running (ie not a test).
-
rises above requires this event reading to be the transition from below the requested to above (ie a transition)
-
remains above requires this to be the 2nd (or further) reading which is still above.
the statement in your logs:
Comparison remains_above = false (event device/attr eXcluded)|
suggests that the first comparison, the event that ran the piston was not the trigger for this run.
It does appear the event was the trigger for the 2nd part of the OR
This suggests the event was the first transition of <=55 -> 61, where rises above would have been true, but remains above would be false.
It would be good to see a couple of executions (ie some history) to better understand what transitions are happening....
The other option is that webCoRE did not have history of a previous execution due to that trigger firing. This could be because you just changed the piston and the webCoRE cache is cleared, I'm not sure this is the case however.
I will look if I can further improve webCoRE logging to make things clearer on what it is seeing.
There is a condition comparison
device:attribute was less than value, which will as a condition tell you now if the value is less (and does not depend on the value changing being the trigger for the piston).
If you want the piston to wakeup on events for the device:attribute, you would need to do always subscribe or other tricks mentioned:
