EventRunner 6/7

[jgab 2,646]

3 hours ago, Sjakie said:

Jan I get still errors when I fa use --comment in a rule.

Is it not done anymore in ER7?

 

Sorry, in 0.1.38 the comment support is back

[Sjakie 156]

Jan this is scrolling over my screen on that way I can't look back what is/was happening.

Can I stop that?

Please login or register to see this code.

 

[jgab 2,646]

33 minutes ago, Sjakie said:

Jan this is scrolling over my screen on that way I can't look back what is/was happening.

Can I stop that?

Please login or register to see this code.

 

So, how does the rule look like that prints the log message?

Sorry, debug message left. Fixed in v0.1.39

I mean v0.1.40

Edited June 8 by jgab

[Sjakie 156]

Jan,  V1.0.38 >>>> can't see screen scrolling, if previous ER version stopped this

version v1.0.37 is normal debug

 

can print also version inhere?

Please login or register to see this code.

 

[jgab 2,646]

3 minutes ago, Sjakie said:

Jan,  V1.0.38 >>>> can't see screen scrolling, if previous ER version stopped this

version v1.0.37 is normal debug

 

can print also version inhere?

Please login or register to see this code.

 

I don't know what you mean with scrolling? ER can't control the scrolling of the console on the HC3...???
The version is printed when ER starts up, before loading rules, (it's part of :onInit() )
 

Please login or register to see this code.

 

Edited June 8 by jgab

[Sjakie 156]

Jan, the debug screen is rolling over my screen with the new version

the info in the debug window I see for the first time 

If I go back a version I see my normal debug screen with rules execution.

All er7 a'as are doing this HC3 is very slow now>> going back to perevious version

Will keep bedroom as version to answer your questions

 

Edited June 8 by Sjakie
slow

[jgab 2,646]

16 hours ago, Sjakie said:

Jan, the debug screen is rolling over my screen with the new version

the info in the debug window I see for the first time 

If I go back a version I see my normal debug screen with rules execution.

All er7 a'as are doing this HC3 is very slow now>> going back to perevious version

Will keep bedroom as version to answer your questions

 

Since v0.1.40 there shouldn't be any excess logging??? How does the log look like?

[Sjakie 156]

Looks as it always was, thanks.

[Christb 33]

Dear @jgab,

I have download my HC3 eventRunne7 QA and then unpack it via the command

plua -t unpack fqaExtract/EventRunner7.fqa ./fqaExtract with success ([09.06.2026][14:16:45][INFO   ][PLUA]: Unpacked QA fqaExtract/EventRunner7.fqa to ./fqaExtract/EventRunner7.lua)

 

When I try to run EventRunner7.lua, I am getting the following error:

[09.06.2026][14:17:55][INFO   ][PLUA]: Starting helper server on 192.168.1.32 8082
Fibaro SDK, online, (0.7205s)
[09.06.2026][14:17:55][DEBUG  ][EVENTRUNNER75555]: EventRunner 7, v0.1.40
[09.06.2026][14:17:56][DEBUG  ][PLUA]: Error in QA 5555, :121: bad argument #1 to 'orgDate' (invalid conversion specifier '%V')
[09.06.2026][14:17:56][DEBUG  ][PLUA]: stack traceback:
    [C]: in function 'os.date'
    ...python/current/Lib/site-packages/lua/fibaro\emulator.lua:121: in field 'date'
    [string "./fqaExtract/EventRunner7_rule.lua"]:104: in upvalue 'setupGlobalVariables'
    [string "./fqaExtract/EventRunner7_rule.lua"]:892: in upvalue 'bootEventRunner'
    [string "./fqaExtract/EventRunner7_rule.lua"]:968: in field 'EventRunner'
    [string "C:/Users/bruvi/Documents/Plua_Dev/fqaExtract/..."]:68: in method 'onInit'
    ...ython/current/Lib/site-packages/lua/fibaro\\quickapp.lua:331: in method '__init'
    ...ython/current/Lib/site-packages/lua/fibaro\\quickapp.lua:19: in field 'QuickApp'
    ...python/current/Lib/site-packages/lua/fibaro\emulator.lua:623: in function <...python/current/Lib/site-packages/lua/fibaro\emulator.lua:621>
    (...tail calls...)
[09.06.2026][14:17:56][DEBUG  ][EVENTRUNNER75555]: ER7 REG x_lumVestibule
[09.06.2026][14:17:56][DEBUG  ][ER7]: REG x_lumPalier
[09.06.2026][14:17:56][DEBUG  ][ER7]: REG x_lumOther

 

I have checked my few rules that use timming but cannot see any visible error .

 

BTW, the created QA header is the following:

--%%name:EventRunner7
--%%type:com.fibaro.deviceController
--%%file:./fqaExtract/EventRunner7_csp.lua,csp
--%%file:./fqaExtract/EventRunner7_scriptfuns.lua,scriptfuns
--%%file:./fqaExtract/EventRunner7_utils.lua,utils
--%%file:./fqaExtract/EventRunner7_compiler.lua,compiler
--%%file:./fqaExtract/EventRunner7_rule.lua,rule
--%%file:./fqaExtract/EventRunner7_tokenizer.lua,tokenizer
--%%file:./fqaExtract/EventRunner7_parser.lua,parser
--%%file:./fqaExtract/EventRunner7_stdfuns.lua,stdfuns
--%%file:./fqaExtract/EventRunner7_props.lua,props
--%%file:./fqaExtract/EventRunner7_x_lumVestibule.lua,x_lumVestibule
--%%file:./fqaExtract/EventRunner7_x_lumPalier.lua,x_lumPalier
--%%file:./fqaExtract/EventRunner7_x_lumOther.lua,x_lumOther
--%%u:{label="info",text="EventRunnner 7"}

-- %%offline:true

 

Does the Setup.lua file has to be added to the file list to have my QA running on Plua?

[jgab 2,646]

3 hours ago, Christb said:

Dear @jgab,

I have download my HC3 eventRunne7 QA and then unpack it via the command

plua -t unpack fqaExtract/EventRunner7.fqa ./fqaExtract with success ([09.06.2026][14:16:45][INFO   ][PLUA]: Unpacked QA fqaExtract/EventRunner7.fqa to ./fqaExtract/EventRunner7.lua)

 

When I try to run EventRunner7.lua, I am getting the following error:

[09.06.2026][14:17:55][INFO   ][PLUA]: Starting helper server on 192.168.1.32 8082
Fibaro SDK, online, (0.7205s)
[09.06.2026][14:17:55][DEBUG  ][EVENTRUNNER75555]: EventRunner 7, v0.1.40
[09.06.2026][14:17:56][DEBUG  ][PLUA]: Error in QA 5555, :121: bad argument #1 to 'orgDate' (invalid conversion specifier '%V')
[09.06.2026][14:17:56][DEBUG  ][PLUA]: stack traceback:
    [C]: in function 'os.date'
    ...python/current/Lib/site-packages/lua/fibaro\emulator.lua:121: in field 'date'
    [string "./fqaExtract/EventRunner7_rule.lua"]:104: in upvalue 'setupGlobalVariables'
    [string "./fqaExtract/EventRunner7_rule.lua"]:892: in upvalue 'bootEventRunner'
    [string "./fqaExtract/EventRunner7_rule.lua"]:968: in field 'EventRunner'
    [string "C:/Users/bruvi/Documents/Plua_Dev/fqaExtract/..."]:68: in method 'onInit'
    ...ython/current/Lib/site-packages/lua/fibaro\\quickapp.lua:331: in method '__init'
    ...ython/current/Lib/site-packages/lua/fibaro\\quickapp.lua:19: in field 'QuickApp'
    ...python/current/Lib/site-packages/lua/fibaro\emulator.lua:623: in function <...python/current/Lib/site-packages/lua/fibaro\emulator.lua:621>
    (...tail calls...)
[09.06.2026][14:17:56][DEBUG  ][EVENTRUNNER75555]: ER7 REG x_lumVestibule
[09.06.2026][14:17:56][DEBUG  ][ER7]: REG x_lumPalier
[09.06.2026][14:17:56][DEBUG  ][ER7]: REG x_lumOther

 

I have checked my few rules that use timming but cannot see any visible error .

 

BTW, the created QA header is the following:

--%%name:EventRunner7
--%%type:com.fibaro.deviceController
--%%file:./fqaExtract/EventRunner7_csp.lua,csp
--%%file:./fqaExtract/EventRunner7_scriptfuns.lua,scriptfuns
--%%file:./fqaExtract/EventRunner7_utils.lua,utils
--%%file:./fqaExtract/EventRunner7_compiler.lua,compiler
--%%file:./fqaExtract/EventRunner7_rule.lua,rule
--%%file:./fqaExtract/EventRunner7_tokenizer.lua,tokenizer
--%%file:./fqaExtract/EventRunner7_parser.lua,parser
--%%file:./fqaExtract/EventRunner7_stdfuns.lua,stdfuns
--%%file:./fqaExtract/EventRunner7_props.lua,props
--%%file:./fqaExtract/EventRunner7_x_lumVestibule.lua,x_lumVestibule
--%%file:./fqaExtract/EventRunner7_x_lumPalier.lua,x_lumPalier
--%%file:./fqaExtract/EventRunner7_x_lumOther.lua,x_lumOther
--%%u:{label="info",text="EventRunnner 7"}

-- %%offline:true

 

Does the Setup.lua file has to be added to the file list to have my QA running on Plua?

Setup.lua is stdfuns, so it is included.

The error you have is that the os.date formatter %V seems not to be supported on your platform... which is strange.
I have released v0.1.41 with an alternative implementation of %V, so it should work for you.

[Christb 33]

22 hours ago, jgab said:

I have released v0.1.41 with an alternative implementation of %V, so it should work for you

Thanks, working like charm😀

The immediate difference from HC3 QA is that the loading time is 2.209s when the HC3 is loading it in 0.605s, not a big deal...

[jgab 2,646]

11 hours ago, Christb said:

Thanks, working like charm😀

The immediate difference from HC3 QA is that the loading time is 2.209s when the HC3 is loading it in 0.605s, not a big deal...

You mean that the old version loaded in 0.6s and the new in 2.2s ? or are you comparing ER6 vs ER7 ?

[Christb 33]

4 minutes ago, jgab said:

or are you comparing ER6 vs ER7

No, the time Plua is loading the rules in vscode and the same QA working on HC3.

 

I did noticed that after moving to ER7 the HC3 loading time was around 3 time quicker than when using ER6👍.

 

When you said:  "os.date formatter %V seems not to be supported on your platform", did you mean vscode or Win11. I may try to fix it, if posible...

[jgab 2,646]

9 minutes ago, Christb said:

No, the time Plua is loading the rules in vscode and the same QA working on HC3.

 

I did noticed that after moving to ER7 the HC3 loading time was around 3 time quicker than when using ER6👍.

 

When you said:  "os.date formatter %V seems not to be supported on your platform", did you mean vscode or Win11. I may try to fix it, if posible...

Ok, but your PC is much faster than the HC3... but you say that the HC3 is faster?

Well, os.date("%V") usually return the week number (1 based), but it doesn't seem to be universal on all platforms...
I changed it to  os.date("%W")+1, %W returns the week zero based, so I just add 1 to it. %W is a documented standard formatter that should be on all platforms.

[Christb 33]

On 6/11/2026 at 8:17 AM, jgab said:

... but you say that the HC3 is faster

Yes true:

log HC3 -> [12.06.2026] [20:42:00] [DEBUG] [QUICKAPP769]: =========== Load time: 0.618s ============

log PC ->   [12.06.2026][20:44:01][DEBUG  ][EVENTRUNNER75555]: =========== Load time: 1.097s ============

It is just an information for you; as you said I was also thinking that the PC will be faster... but 0.4s is nothing.

[Sjakie 156]

Jan, if I want to update v0.1,43 it wil update but show  updated v0.1.41!

Edited Saturday at 06:55 AM by Sjakie

[Sjakie 156]

Jan, is there a possibility after restoring a backup to renew all values of the Global Variables?

So TOD and other values are as they should be?

[jgab 2,646]

52 minutes ago, Sjakie said:

Jan, if I want to update v0.1,43 it wil update but show  updated v0.1.41!

It was a bug after I moved around the source files. v0.1.44 fixes it.

40 minutes ago, Sjakie said:

Jan, is there a possibility after restoring a backup to renew all values of the Global Variables?

So TOD and other values are as they should be?

I don't know. I usually have rules that initializes GVs to start values if they don't have values. 

It's up to your own logic. ER has no memory of what has been set.