Unfortunately, I have some that can't complete.
Than with working correctly retriggering protection it will be "Missing Trigger" condition. Please make sure this is what you want. If "Missing Trigger" is not acceptable you should rethink how to create a correctly working rule(s).
I use a mix of conditional triggers and required expressions on my rules. Some with PB's, some without. Most of my required expressions are timed based such as sunset, sunrise, or specific time.
I have no issues with the double triggering rules or missed triggers. None of my triggers will retrigger that quickly that a PB will not have time to change therefore preventing the rule to run again.
That is why I didn't understand why you was saying the timing was such a big deal. I have never had issues. I didn't realize there were triggers that would retrigger less than a second later. If you have those then I understand what you are saying.
Good for you and I am glad to hear you did not step into the discussed problems.
For instance in my case I have multiple PIR/mmWave sensors in many places. The reason is - to speedup a response for lights to turn on. Any sensor must turn on a light but because there are few around they may send triggers near simultaneously. However the related rule must not be retriggered multiple times, only one instance must be running. Another example - all rules triggered by buttons. Again only one instance must be running despite how many times button was pushed by somebody impatient.
Frankly, I don't see any reason for the same rule running multiple instances. This is nothing more than wasting memory to begin with and CPU cycles. All my rules are designed to be running only single instance at a time. After using this approach (single rule instance at a time) I never stepped into low memory condition and other resource related problems.
Just shearing my experience with HE/RM.
It is good you share. People need to understand what other people experience. I have rules that can be triggered by either PIR motion sensor or an MMWave sensor and then the MMWave sensor inactive is the trigger to turn off the lights. I don't have any conditional triggers or required expressions on these rules. I let either of those items turn the light on then the other will report motion when you enter its area. I have this for almost every room in my house and have no issues at all. No problem with the rules running or hub function. Now if I had a ton of those it might be different but I have approximately 10 and they done all run at the same time. Maybe 3 or 4 at once.
