I might be blind, but I just noticed this switch in Rule-5.1. Could someone give me an example where turning on this switch might be helpful?
If you have ever been tempted to use Private Boolean to prevent re-entrant execution, this is the same idea. As always with an arbitrarily flexible tool, there are various uses cases and not one "typical" example. But in general, it can be used (as an alternative to these other methods without a significantly different outcome--it's not magic that will help a device that sends rapid-fire events, for example) when you want to prevent re-triggering of a rule while some actions are still pending. Often, this would be a wait, delay, or similar, though I suppose it could happen while you're still working down the list of "regular" actions, too (just less likely since that is all normally pretty fast).
Here is the discussion that prompted the feature, along with one example in the original post in this topic:
2 Likes
Thank you for your detailed response and the link to the other discussion leading to the switch being added!
I'm still working on a Dryer/Washer "done" notification rule, and this might help. The Yolink vibration sensor is being triggered over and over. I want to execute the actions when the vibration stops (for a while).
I'm trying to use a Zone Motion Controller, but it's still kinda brittle.
The washer/dryer 3rd party app does not support Yolink unfortunately, otherwise I would be trying that pre-coded app.
