Attached is a fresh log. Questions? Why are some actions crossed out, some say skipped, and others actions as resumed still say paused?
The lines are to visually indicate that your IF statement evaluated false, so the actions under it were skipped. So reading from the bottom up, the rule was triggered by the switch going on. The first IF state IF switch is on evaluated as true so it paused the rule. The second IF statement wasn't evaluated at all (because it's an ELSE-IF and the first IF was already satisfied) so it was skipped and the action under it was skipped.
For the second run, it was triggered by the switch turning off, so the first IF statement was evaluated, but was false so the action was skipped. The the ELSE-IF statement was evaluated, resulted in being true, so the action was executed.
That would be the odd part if written with the log because it shows here that after the RM action to resume the rule, the rule was still in a paused state. This goes back to this statement:
This could very well be a bug where you manually pausing the rule is trumping what the automation is trying to do. Or, it could just be that rule pause/resume in RM is not working. I would turn off your virtual switch, go into the "Screen Porch Motion Detected" rule and make sure it's not paused, and then test this one again. When you turn the switch on (which should pause the "Screen Porch Motion Detected" rule) go into the "Screen Porch Motion Detected" rule and see if it shows paused or not (if you already have the page open, give it a refresh to make sure you're seeing the current status).
Again, you would have less clutter in the logs if you removed the unnecessary ELSE-IF/THEN condition test. All it needs to be is ELSE since you know the Screen Porch Motion Switch is off at that point .. no need to check it.
Thanks for all the suggestions. I will try them out.
