PLUGIN: Rules Engine - V0.19.2

Plugins & Plugin Development General Plugin Discussion
41

Hi Vosmont,

I’d sure like that once option. If you can indicate per condition to be evaluated only at the start and not while the delayed tasks are still pending it would be truly powerful. You can then have a mix of once and ‘repeat’ (yes I have that in LUA now). I now have quite a bit of LUA scattered in many scenes. Becomes a bit of a pain to maintain.

Cheers Rene

42

Version 0.07 is available :

  • fix lots of UI bugs
  • add “isCritical” parameter on group of action
    Defines if the actions of the group can be stopped if the status of the rule changes during their execution (critical can’t be stopped).
43

I have managed to test the last version on my VeraEdge… there’s a hot fix available for device without service.
It seems to work well (my rules are working)

44

Here are some examples of rules with the version 0.07

45

Nice! thnx for the examples

46

Thanks for your work here. The hotfix addressed my issue.

I was beginning to think I was cursed with my Plus.

X

47

I don’t get this…
the same rule on v0.5 was working fine, now on v0.7 KO :frowning:
rule: if there is a move and it is not “day” turn on light wait 15 minutes and turn off.

48

As my VeraEdge became very instable, I test rarely the modifications on the legacy Vera. I’m now developping on openLuup.

I should receive a new VeraPlus controller, and then be able again to test on the Vera before submitting the changes.

My VeraEdge is slowly dying with more and more bad blocks in NAND memory (http://wiki.micasaverde.com/index.php/Vera_Nand).
I don’t know if it’s my way of using this box that has corrupted it.
I upload very often files on it for testing and developping my plugins.

As it results in writes on “/etc/cmh-ludl”, in the same filesystem as “/etc/cmh”, where is stored “user_data.json” (where all variables of device are stored), I’m now trying to have the smaller footprint as possible on this folder (aka NAND memory).

That’s why, for sparing the Vera, these changes have been made :

  • .lzo files are decompressed in “/tmp” (RAM)
  • informations on rules are stored permanently in “/tmp/log/cmh” on “/dev/sda1”, aka the usb key where are stored the logs.
49

[quote=“Tommi, post:47, topic:189418”]I don’t get this…
the same rule on v0.5 was working fine, now on v0.7 KO :frowning:
rule: if there is a move and it is not “day” turn on light wait 15 minutes and turn off.[/quote]

Unfortunately, a lot of changes have been made in v0.07 and rules created in v0.05 are no more compliant.
You will have to edit them.

The rule you gave in the screenshot seems to be OK.
What does not work ?

(in v0.07, you have a panic button, and the RulesEngine is turn off by default. Perhaps you have to switch it on)

EDIT : for your initial need, you should also look at the excellent plugin “Smart Switch Plugin” which allows to create easily timers for lights.

50

The properties are for modifying the rule behaviour. You can add your own (see plugin Virtual Alarm Panel).

The default properties are :

  • (TODO) auto untrip : the idea is to deactive the rule after a defined amount of time (as a motion detector). I have not found a use case, so this feature is not already developped.
  • is aknowledgeable : you can set an acknowledgement on a rule (by clicking on the icon of the rule), ie the actions of type reminder will be discarded.
    A use case is if you have a recurrent vocal warning on an opened door, you can stop the warning with an aknowledgement, because it’s normal that the door stays temporarily opened.
51

Probably related to the issue I am having with my VeraPlus saving the state of things, but when I try to edit a rule I get the following.

Desynchronization: id #NaN of the rule at position 0 in the xml file is not the expected id #2. You should not save.

52

@xeinth, as I haven’t got a VeraPlus, I’m not sure that this plugin is fully compliant.
Some users have reported that some environement variables seems to be different.

As RulesEngine does some internal stuff on the filesystem, perhaps the problem is here.

Could you active the debug mode (variable Debug=4) and send the logs from the start of the plugin (and perhaps when you modify the rule) ?

tail -f /var/log/cmh/LuaUPnP.log | grep "^01\|RulesEngine"
53

[quote=“vosmont”][quote=“Tommi, post:47, topic:189418”]I don’t get this…
the same rule on v0.5 was working fine, now on v0.7 KO :frowning:
rule: if there is a move and it is not “day” turn on light wait 15 minutes and turn off.[/quote]

Unfortunately, a lot of changes have been made in v0.07 and rules created in v0.05 are no more compliant.
You will have to edit them.

The rule you gave in the screenshot seems to be OK.
What does not work ?

(in v0.07, you have a panic button, and the RulesEngine is turn off by default. Perhaps you have to switch it on)

EDIT : for your initial need, you should also look at the excellent plugin “Smart Switch Plugin” which allows to create easily timers for lights.[/quote]
Thanks… but the rule was re-created and not used from previous release.
There was just KO on the rule, without any explenation.
After going back to 0.5 all works fine.

Wysłane z mojego SM-N910C przy użyciu Tapatalka

54

When a rule is in error, you have a red exclamation mark. If you click onto it, you will have more details.

In 0.07, the RulesEngine main device has a switch button to activate it, aka panic button (besides you wil find the buttons to view to the rules and the history).
If your rules are KO without errors, your RulesEngine must be stopped.

55

[quote=“vosmont, post:52, topic:189418”]Could you active the debug mode (variable Debug=4) and send the logs from the start of the plugin (and perhaps when you modify the rule) ?

tail -f /var/log/cmh/LuaUPnP.log | grep "^01\|RulesEngine" [/quote]

Here is the relevant part of the log. To describe what was going on:

  • I have a single rule in place. Set the debug to level 4
  • Opened the rule, changed the description and saved it back. Receive a warning upon opening it.
  • After saving the rule, a second rule appears which is the same when opened.

If I reboot, it seems go back to a single rule which looks correct. (not reload luup). However, I haven’t tested this with multiple rules and it could be that it is only keeping the last rule.

x

56

Ok thanks, I will check that.
It seems that I’ve forgotten to recompress the file… so it can’t work on legacy Vera for new rule (works well on openLuup)

You can fix it by hand : download the file “C_RulesEngine_Rules.xml” and edit the xml file at “” and put the id of the rule.
Then upload your modified file onto the Vera.
You could also do this in the rule editor by forcing the id and saving.

Think of making a backup of your rule

Version 0.08 is coming soon

57

[quote=“vosmont, post:56, topic:189418”]Ok thanks, I will check that.
It seems that I’ve forgotten to recompress the file… so it can’t work on legacy Vera for new rule (works well on openLuup)

You can fix it by hand : download the file “C_RulesEngine_Rules.xml” and edit the xml file at “” and put the id of the rule.
Then upload your modified file onto the Vera.
You could also do this in the rule editor by forcing the id and saving.

Think of making a backup of your rule

Version 0.08 is coming soon[/quote]

Vosmont,

Thank you for taking a look. Indeed on my first take it seems to have addressed the issue. One comment for your consideration. This may not generally happen to others, its possible this happened because I cloned a rule by copying the XML. That could have given a duplicate ID that put everything in a funny state.

It could be interesting to have a ‘clone’ button just to allow easy modifications based off a simple rule. Copies everything but zeros out the room and device parameters.

Another thought would be a means to carry state information forward between successive runs of a rule. This would be helpful for rules in which there are many ways it can be started and stopped. For controlling a light, it could be enabled based on a switch, event or motion. You don’t want to motion stopping to turn off a light that was enabled by a switch. Levels could help if I understand them correctly but perhaps yields complex logic. I suppose they allow a moore state machine, and I’m wondering if a mealy might make some things a lot easier.

x

58

[quote=“xeinth, post:57, topic:189418”]This may not generally happen to others, its possible this happened because I cloned a rule by copying the XML. That could have given a duplicate ID that put everything in a funny state.

It could be interesting to have a ‘clone’ button just to allow easy modifications based off a simple rule. Copies everything but zeros out the room and device parameters.[/quote]

you can clone your rule by two ways :

  • copy/paste in the rule editor. You should then delete the id of one rule. I will add a control on duplicate ids before saving.
  • XML import in the rule editor. This feature is made for exchanging templates between users. I have added a control on ids in 0.08.
    You can export a rule with a skeleton without devices and reimport it.

The rule is active until its conditions are filled. Ie, if you have a condition and a list of condition with “one is true” on your switch and your motion detector, this should work (As long as the switch is on, the condition is filled) ?

59

Hi Vosmonth, Xeinth,

First of all many thanks for this usefull plugin!

First when I open the rule maintenance, the list under the create button is empty.
When I created a new rule (again) and after saving several times I ended up with 10 rules.
It seems a new rule was created each time I (intermediate) saved a rule
After a full reload (CTRL-F5) the rules disappeared again.

When the list was visible, I was not able to delete the duplicate rules.
when looking in the time line all rules where active, also the duplicate ones.

I am on Vera-Edge 1.7.1707.

60

@vosmont

This really is exceptional work and makes this significantly easier…
Please keep up the good work

@all
we should raise a bounty to motivate vosmont to keep going… this is going to make our lives much easier