Rule 4.0 -- The new Rule Machine Rule 4.0 is the culmination of a journey in the transformation of Rule Machine. At once it simplifies and adds power, resulting in a fully generalized automation engine. The prior top-level organization of RM is thrown out, replaced by a simpler interface. The cha…

Sorry about this problem. This came about from a Global Variable with a space in the name. The bug has been fixed for the next release. In the meantime, please see the PM I am sending you about it.

Hi! I would like to propose an additional feature: option to reference to the triggering device in conditions within the triggered rule, sort of like how actions around private booleans can reference the rule itself. Here is one use case: I have a rule that I would like to run whenever any of a few…

[image] hans.andersson: option to reference to the triggering device in conditions within the triggered rule, sort of like how actions around private booleans can reference the rule itself. This can be done a couple of ways. One is that the last event is available as a string %value%. This …

[image] hans.andersson: The limitation right now, so far as I understand RM 4.0, is that when a "contact sensor changed" event occurs, I have no way of determining whether the change itself was an opening or a closing—I can check only the current state of each of the sensors, but that says nothi…

I just converted a BC app instance to RM 4. This button device is a Lutron RadioRA 2 keypad. That new RM 4 rule is throwing an error that does not seem to cause problems: [Screen Shot 2019-09-13 at 7.28.36 AM.png] I have a different RM (2.5) rule that "presses" a Lutron keypad (the one in the new…

Same error [image] Errors on a Few RM Rules 📐 Rule Machine® This one is somewhat of a mystery. We cannot reproduce the failure. I'm thinking of making a small change to the code for the next release to see if it clears this up. But without being able to really understan…

[image] bill.d: This button device is a Lutron RadioRA 2 keypad. That new RM 4 rule is throwing an error that does not seem to cause problems: This error is somewhat of a mystery at the moment. Could you show the rule that is throwing it.

[image] bravenel: Could you show the rule that is throwing it. Here it is. I would guess it's due to 2 rules running at the same time as this button controller rule doesn't cause an error when called by pushing a physical button. Button 1 was the button that was pushed via the other RM 2.5 ru…

It has something to do with per mode actions. But we have not been able to reproduce the failure yet. I'm making a 'superstitious' code change in the next release that may correct it.

[image] bravenel: Sorry about this problem. This came about from a Global Variable with a space in the name. The bug has been fixed for the next release. In the meantime, please see the PM I am sending you about it. Hi! If the PM above were to be a workaround, could you let me in on it? I c…

[Released] Rule 4.0

Rule Machine® All things Rule Machine

Ken_Fraleigh September 13, 2019, 1:01pm 1074

Same error