They could, but that would trigger the rule anytime the value changed (and it was greater than the entered threshold).
Instead, it sounds like they only want the rule to trigger one time when the value was below a certain value and then changed from below the value to above the value.
I think you’re on the right track here, though I don’t know that you need to store the previous value.
One approach would be to use a True/False variable to indicate the status. I would use a separate rule just to track this variable… then use that variable changing as the trigger for your main rule.
There’s a few approaches you could take here - one is to just always flag the variable true/false based on the value that comes in. Then in your other rule, you would use a ‘state stays’ true in order to trigger the main rule.
In the example above, I’m using an expression as it simplifies the flow, but you could also use an IF Condition block and then set the variable appropriately within the THEN / ELSE sides if that’s more intuitive to you.
Then in the actual rule, we trigger on $ABoolean stays true for X seconds. If we use a ‘changes and is true’ trigger, then every time the value comes in and the variable is set to true again, it would retrigger the rule. The beauty of a ‘state stays’ trigger is it only triggers the first time the variable changes to our desired value and it has to change out of that state before it will trigger again.
