Rule Machine issue w/ 703

There’s a bug. Stand by. We fixed it and will put out an update. Yet tonight.

1 Like

This bug has been fixed, and build 704 released. Please update to 704.

1 Like

704 fixed the previous issue. Tried removing RM and reinstalling my 703 backup before rebuilding rules and it fixed the issue. However, I previously somehow added a custom command to RM that I cannot remove because it does not show as available to remove, so I will be using my rebuilt rules instead with the clean install of RM. Sometimes it’s just better to start over!

Thanks @bobbyD, @bravenel and @patrick for your help with my issue.

2 Likes

I'm not understanding that explanation. I would think that if I define a single condition, but then I return to add a second condition, I would want to see the first condition displayed as well. Please see example below where one of my lighting rules does show the single condition, and is not behaving the same as a water sensor rule.

Let me further explain:

If you have a rule with a single condition, there are only two possible "rules" that could apply: That single condition or NOT that single condition. RM assumes that you intend the single condition to be the rule. Here is what happens:

Notice that after hitting Done on choosing the condition, that RM automatically filled in the Define Rule setting to be that single condition. Now, if you click on Define Rule you get the normal page for setting up a rule, where nothing has yet been selected, like this:

At this point I could select NOT, or I could select the single condition, like this:

If I select Front Door active there and hit Done, guess what, the rule back on the main page will be exactly what was shown above in the first screen shot. So, RM has actually saved me that step for this simple one condition rule.

Now, suppose I choose two conditions. I get this:

Notice that the rule is not filled in for the Define Rule selection, unlike what happened with the single condition case. That's because there is no way for RM to know what logic to apply for the two conditions. It could 1 OR 2, or 1 AND 2, or NOT (1 OR 2), etc. When I click on Define Rule now, I will get the exact same screen shown above in the second screen shot,

At this point I will have to select the logic I want for the rule, by selecting the condition I want first, then AND or OR, then the next condition, etc.

Then, after selecting all of that, and hitting Done in the rule definition, I get this:

Now, my complex rule has been defined and shown on the main rule page under Define Rule.

I hope this clarifies for you what is going on.

3 Likes

I understand now what I was not doing. Thanks for taking the time to explain!

Thanks for this explanantion @bravenel . I could never get my head wrapped around how conditions and defined rules worked but this helps quite a bit. If we have any RM veterans out there, a “for dummies” wiki like we have for CoRe would go a long way and save Bruce a lot of time and effort.

Any volunteers? :smile:

1 Like

RM is a funny thing: The majority of rules actually only have a single condition. Then, the majority of what's left with multiple conditions have very simple rules, like A AND B, or A OR B. It is very rare that one needs parenthesized terms, or to use NOT.

I've had well over 100 rules at times, less now since I use apps like Motion Lighting and Button Controller. The most complex rule I've ever had is this one below. Four conditions, really two pairs of two conditions, and a rule that says that if either pair are both true then turn on some fans. There are a couple of companion rules that turn these fans back off again when things cool down. This one fires every day once it's hot here in Scottsdale, and never fires during the cooler months. The whole point of this rule is to turn on these exhaust fans only when it's cooler outside than in the garage -- otherwise, they would be sucking hotter air in to replace the air blown out, effectively heating the garage instead of cooling it.

3 Likes

This leads me to possibly a better option than a wiki. I learned how to use Core by looking primarily at more complex pistons created by other users. Maybe a couple of Topic like we have in the ST forums would be helpful.

a Share your RM Pistons post (not sure what to call each RM automation)
a RM Peer Assistance post.

I’m not sure we have the forum user base for these to take off yet but I guess it can’t hurt.

3 Likes