EDIT! Bruce, I think the problem is with the evaluation of simple conditions in my actions, not the rule evaluation as I initially suspected, please disregard for now. Thanks, @Ryan780 and @eric.dalquist
While 220.127.116.11 does appear to fix the problem I reported in 18.104.22.168 about RM 3 not subscribing to presence states correctly, there does appear to be a new issue with this build.
I have created an example rule and attached screenshots of logging and application states. Jist of the problem is that it appears conditions are only evaluating a single event even if there are supposed to be several events considered (AND). I haven't confirmed it yet, but it appears this may affect more than just conditions but also conditional actions.
As you can see from the logging, the rule is only evaluating the state or first variable and not the mode, motion or other variable states. Excuse the error in the second condition of the rule, but I don't think it makes any difference for what I'm trying to show (the third condition should have been mode is sleep not sleep mode deactivate vMotion active).