EventRunner 6/7

[jgab 2,647]

ER7 v0.1.15 has a shorthand/alternative for coloring a log text.
Ex.
 

Please login or register to see this code.

So, log.<color name>(...)
It translates to log("#C:<color name>#...")
It will color the whole text logged.

[Sjakie 156]

Jan is this included? If no it generate an error.

Please login or register to see this code.

 

post(#debug_Partities_Afwezig,+/00:00:07)

error no plus time

 

Please login or register to see this code.

 

 

[jgab 2,647]

27 minutes ago, Sjakie said:

Jan is this included? If no it generate an error.

Please login or register to see this code.

 

post(#debug_Partities_Afwezig,+/00:00:07)

error no plus time

 

Please login or register to see this code.

 

 

'restart' is a reserved keyword now, and can't be used as the name of a event or variable. ER7 will give a better error message now that the word is reserved.
There was a bug in all the arm functions, fixed.

v0.1.17 uploaded.

[jgab 2,647]

Updated the documentation links in the first post to be up-to-date with ER7's features.

[Christb 33]

Hy @jgab, did you change the way to declare rules in a QA additional file?

See below:

Please login or register to see this image.

/monthly_2026_05/image.png.3159875e7d0c55e984401f1d62ca4a1f.png" />

 

with in additional file 'lumVestibule':

     .../...

 

gives error:

[27.05.2026] [16:24:50] [DEBUG] [QUICKAPP769]: EventRunner 7, v0.1.15

[27.05.2026] [16:24:54] [DEBUG] [QUICKAPP769]: ER7 REG lumVestibule

[27.05.2026] [16:24:55] [DEBUG] [QUICKAPP769]: =========== Loading rules ================

[27.05.2026] [16:24:55] [DEBUG] [QUICKAPP769]: ER7 QuickApp:main() start -> running Libraries)

[27.05.2026] [16:24:55] [DEBUG] [QUICKAPP769]: ER7 EXEC lumVestibule

[27.05.2026] [16:24:55] [ERROR] [QUICKAPP769]: timer handler failed with error: ./include/lumVestibule.lua:49: attempt to call a nil value (local 'rule')

 

 

[jgab 2,647]

21 minutes ago, Christb said:

Hy @jgab, did you change the way to declare rules in a QA additional file?

See below:

Please login or register to see this link.

 

with in additional file 'lumVestibule':

Please login or register to see this link.

     .../...

Please login or register to see this link.

 

gives error:

[27.05.2026] [16:24:50] [DEBUG] [QUICKAPP769]: EventRunner 7, v0.1.15

[27.05.2026] [16:24:54] [DEBUG] [QUICKAPP769]: ER7 REG lumVestibule

[27.05.2026] [16:24:55] [DEBUG] [QUICKAPP769]: =========== Loading rules ================

[27.05.2026] [16:24:55] [DEBUG] [QUICKAPP769]: ER7 QuickApp:main() start -> running Libraries)

[27.05.2026] [16:24:55] [DEBUG] [QUICKAPP769]: ER7 EXEC lumVestibule

[27.05.2026] [16:24:55] [ERROR] [QUICKAPP769]: timer handler failed with error: ./include/lumVestibule.lua:49: attempt to call a nil value (local 'rule')

 

 

There is a "new" way to declare user modules.

Note that the QA file's name need to start with an 'x' or it will be removed if you run update with QA Dist.

[Christb 33]

12 minutes ago, Christb said:

id you change the way to declare rules in a QA additional file?

I have found that changing rule=er.rule by rule = er.eval, all the rules are now loaded.😀

I now need to find why some of these rules are showing errror with "❌ Undefined variable:".

Sure it is comming from the file paste from ER6 to ER7 QAwhich need some changes as the compatibility between 6 &7 is good only with standard rules but not with option like:

rule("name1","condition => action") which is now rule("condition => action",{name="name1")

It worths to make the changes as you add the group feature that was present in ER5 and lost in ER6 and new interesting features.🫠

[jgab 2,647]

2 minutes ago, Christb said:

I have found that changing rule=er.rule by rule = er.eval, all the rules are now loaded.😀

I now need to find why some of these rules are showing errror with "❌ Undefined variable:".

Sure it is comming from the file paste from ER6 to ER7 QAwhich need some changes as the compatibility between 6 &7 is good only with standard rules but not with option like:

rule("name1","condition => action") which is now rule("condition => action",{name="name1")

It worths to make the changes as you add the group feature that was present in ER5 and lost in ER6 and new interesting features.🫠

yes, if you use a script variable before it has been assigned a value you get the error. It is a very common cause for faulty rules so therefore it is now an error. make a custom to have rules to setup variables 

Please login or register to see this code.

 

[Sjakie 156]

Please login or register to see this code.

Please login or register to see this code.

retyped same and replace  underline error stays?

[jgab 2,647]

3 hours ago, Sjakie said:

Jan is this included? If no it generate an error.

Please login or register to see this code.

 

post(#debug_Partities_Afwezig,+/00:00:07)

error no plus time

 

Please login or register to see this code.

 

 

Sorry, the +/ n/ and t/ operators was accidentally dropped. Back in ER7 v0.1.18.

[jgab 2,647]

31 minutes ago, Sjakie said:

Please login or register to see this code.

Please login or register to see this code.

retyped same and replace  underline error stays?

Fixed in v0.1.19. I was too restricted with identifier names (like _). v0.1.19 is also accepting more national characters in identifiers.

[Sjakie 156]

no problem!

 

Please login or register to see this code.

 

[Sjakie 156]

Please login or register to see this code.

Please login or register to see this code.

 

Please login or register to see this code.

remark Partition 20 same trigger >> no error

Please login or register to see this code.

Please login or register to see this code.

A-sync function only if I have "once" if removed error gone

[27.05.2026] [19:37:25] [DEBUG] [QUICKAPP661]: ❌ ./include/rule.lua:453: scanHead: missing op in AST node: NEG 
src: $Afz_Hum_Delta_Keuken < 0 & $Afz_Hum_Delta_Keuken < -100 => $Afz_Hum_Start_Keuken = keuken.humidity:value; log.pink('Check >>> $Afz_Hum_Start_Keuken >> reset %.f %%',$Afz_Hum_Start_Keuken); log.pink('Check >>> $Afz_Hum_Delta_Keuken >> reset %.f %%',$Afz_Hum_Delta_Keuken); log('26-A'); wait(0)

 

 

All 6 QA's are on ER-7, one without error

more to come

[Christb 33]

I am very happy with ER7..

I have finished the configuration of all my rules using v0.1.15 and used 'qaDist' to update the version to 0.1.19 with every think working fine.

ER7 and qaDist are marvelous tools for the HC3 

[jgab 2,647]

12 hours ago, Sjakie said:

no problem!

 

Please login or register to see this code.

 

Fixed in v0.1.20

[jgab 2,647]

10 hours ago, Sjakie said:

Please login or register to see this code.

Please login or register to see this code.

 

Please login or register to see this code.

remark Partition 20 same trigger >> no error

Please login or register to see this code.

Please login or register to see this code.

 

 

[Sjakie 156]

Jan, v01.20

I need more visible lines in debug

er.opts = { started = false, check = false, result = true, triggers=false}

 

How to get rid of all the lines rule .. : 0

Please login or register to see this attachment.

[jgab 2,647]

43 minutes ago, Sjakie said:

Jan, v01.20

I need more visible lines in debug

er.opts = { started = false, check = false, result = true, triggers=false}

 

How to get rid of all the lines rule .. : 0

Please login or register to see this attachment.

 

v0.1.21 has some more fixes (no device error)
If you want to get rid of 

Please login or register to see this code.

you set result=false

Please login or register to see this code.

 

You can also set it for just a single rule
rule("x => y",{result=false})

[jgab 2,647]

ER7 will throw an error if we use a device that don't exist.
Ex.
rule("999:value => log('ok')")
and there is no device, 999 on the HC3, there will be an error.
In v 0.1.22 the check can be disabled by setting
fibaro.dontCheckDevices=true

 

However, it's a common source for errors so it can be good to have it enabled.

[Sjakie 156]

Jan no idea where to fix. Have a few in different QA's

Please login or register to see this code.