Bug with mode changes / predicate?

[brad5]

I'm seeing errors in the logs from an RM5 rule:

The rule is pretty simple... and if I run the rule actions without triggering the rule they work fine and show no errors.

I can trigger the errors by forcing the mode to change, or it happens when mode manager changes the mode. If I remove the predicate statement, the errors stop.

Here's my mode setup:

[sburke781]

Not sure if this will help, but what is shown in the predicate section of the rule when you are in Predawn mode? Your screenshot shows the predicate resolving as false, just wondering whether it shows true when you are in that mode.

[sburke781]

I'd also tag @neonturbo here, I think he was trying to do something similar recently. And @bertabcd1234 was assisting....

[brad5]

Good catch but no... just a timing issue. Here's what it actually looks like in predawn mode:

[bravenel]

Yeah, this is a bug. Just saw it, and a fix will be forthcoming.

[brad5]

Thanks!

[neonturbo]

@sburke781

I'd also tag neonturbo here, I think he was trying to do something similar recently.

Wasn't me! At least not that I can remember. I haven't played with it much since Beta testing.

[sburke781]

Was thinking about this post and Roberts follow up suggestion of using a predicate.

Trigger based on changing away from a mode

Like this? Mine might not be the best example, because I have custom modes, but it should be similar for you. Select capability for new Trigger Event, and I picked "Mode" [mode] Forgot to add, you could just use "Changed" for the mode trigger, and in the rules do a conditional.

[brad5]

Resolved with the latest update, thank you!