[Rules] Enhancement: add %eventvalue<nr>%

[clumsy-stefan]

In newer ESPEasy versions you can use %eventvalue% to directly access the values of an event with multiple values. Used mainly to access variables of the new "Single event with all values" feature.

[tonhuisman]

Used mainly to access variables of the new "Single event with all values" feature.

And for all events that receive multiple values, like current Rules#Timer events that now have %eventvalue2% set to the loop count of LoopTimerSet commands, and for passing in multiple values from (external or internal) commands like /control?cmd=event,eventname=value1,value2,value3,value4

The current limit in ESPEasy is 4 event values, and %eventvalue% is equivalent to %eventvalue1% (for backward compatibility)

[TD-er]

The current limit in ESPEasy is 4 event values, and %eventvalue% is equivalent to %eventvalue1% (for backward compatibility)

Not sure if that remains a hard limit as it used to be related to the number of task values.
But now we're also using it for other event values, so I guess we might later allow for more eventvalues if needed.

[enesbcs]

Support added at commit c679a2e

[clumsy-stefan]

Seems to work (at least for me). Same rules with "eventvalue<nr>% as in ESPEasy works now in RPIEasy.

Thanks a lot, great work.

[enesbcs]

Thanks for testing, should we close this issue now?

[clumsy-stefan]

IMHO yes... If something comes up you could always reopen it (or open a new one) with a more specific description of the problem...

[clumsy-stefan]

I have the following ruleset:

on sht30#temperature do // Heizung und Lueftung
  if %eventvalue% < 5
    event,ch9r=0
    event,ch5d=1
    TimerSet,2,1800
  endif
  if %eventvalue% > 8
    TimerSet,2,1
  endif
endon

It seems it takes the last %eventvalue1% that has been set and not the current %eventvalue%. Probably some kind of race condition? As in this example the 13.59 has been set in a recent rule from an event that generates 3 values and assigns them to local variables.