When helping a friend move to a new hub and re-create all apps (manually, not with a backup--consolidating from two hubs to one!), I discovered that this Simple Automation Rules 1.1 setup had an unexpected outcome to me:
- Observed behavior: Switch turns off 1 minute after all motion sensors become inactive, even if one sensor (or more) becomes active again in the meantime
- Expected behavior: The above only if all motion stays inactive for 1 minute, otherwise cancellation of the timer
I suppose that either interpretation of this is technically possible since the UI isn't clear whether "all motion stops" means "all motion stops and stays inactive," but it seems like this would be the most intuitive outcome (think of someone trying to use this to turn off a switch based on motion inactivity) or at least be an option.
And yes, I know that I could do this with Rule Machine or probably even Basic Rules nowadays, but this wasn't my hub or my automation. 
(The above is since I created it to try to identify their problem--they were hoping to turn on an "away mode" switch to change modes when all motion inside the house remained inactive for a long enough time. To their surprise, it happened frequently when at home!)
It should be noted that this differs somewhat from the original Simple Automation Rule behavior, as I found this app working as expected on their original hub. Of course, it should be noted that it doesn't give you the SAR 1.1. choice about whether it's any or all motion, but the behavior is "all" (like above) and the cancellation does happen as expected:
Tagging @bravenel to see if this is expected or not.
