Actively monitor timing restrictions on Conditions to trigger Logicblock evaluation

[DanT]

The problem here is that the evaluation is not triggered once all conditions would be met. And that‘s because the timing restrictions of the conditions are not actively monitored (this would require some sort of process that is constantly monitoring all such conditions and trigger re-evaluations).

https://groups.google.com/forum/#!msg/apilio/nvHMWG4fImk/TowGcEpFBQAJ)

[BOS]

I agree on the feature requests but I have another vision on how to do it (easier ?)

On my side, I would like to simply revaluate conditions after variable conditions timeout…

[pebneter]

Hi @BOS,
we are currently beta testing this. Interested in join the group?

[Anna]

This feature was released last month All the details here:

How to setup time constraints for Conditions: delays and timeouts

With Apilio you can add delays and timeouts to some of your Conditions, so you can make your setup smarter: What if you have a presence sensor that only sends the one event when it detects someone, and nothing else? How do you know that nobody is in the room if there is no “idle” event? Or what if you have a sensor that sends lots of false positives. How do you know when it has finally settled on a value? Apilio is here to help! When to add a delay to your Cond…

Improved Conditions: giving you a more flexible and powerful way to run your logic

If you are a long-time Apilio user, you probably have used the option to automatically evaluate a Logicblock whenever one of the connected Variables changes. With this new update, we are supercharging our conditions and you’ll be able to use them as triggers for your logic going forward! [Apilio - new conditions with superpowers] Using variables to run Logicblocks (legacy) To prepare for this update, we started by moving that original option to evaluate the Logicblock from the Logicblock to …