How to get the current PWM value in RULES

[ReinhardDaemon]

Hello,
I would like to write a rule that increases the PWM by 5 at the push of a button.
The individual elements work, the keystroke is recognized, I can set the PWM directly in the console.

Used: Rule2, button6, pwm8

It doesn't work for me to read in the current PWM:

Rule2 ON button6#state==2 DO Backlog var1 pwm8; add1 5; pwm8 var1 ENDON

How does it work?

[sfromis]

In many cases, the way to query some value is to first issue the command to have it printed/logged, and then use a separate rule to pick up the value from the command JSON result, similar to getting sensor values. And then a third rule to act on a calculation result.

Something like
Rule2 on Button6#state==2 do Backlog PWM8 endon on PWM#PWM8 do var1=%value%+5 endon on var1#state do pwm8 %value% endon

Only a very few types can be referenced directly in rules.
https://tasmota.github.io/docs/Rules/#rule-variables

More generally, as you seem to be using ESP32, you also have the Berry language for more flexible and less quirky ways of doing automations.

[ReinhardDaemon]

Thank you so much for this input!
Yes, it is ESP32 and now it is the decision, whether to go on with rules, as the task is so simple, or to do it with Berry.

[ReinhardDaemon]

I have tried it. It works in principle, but problem is, when I just want to query the PWM8 value from the console with
pwm8
, Rule2 triggers on PWM#PWM8 ... and performs the actions then, which is not intended.
I think, there is no (easy) solution for this now and I must switch over to Berry scripting (?).
Or I have to set a flag variable, when I pressed the key, in order to distinguish later on, from where the event was originally triggered,
but maybe better to make the step to Berry now...

[sfromis]

Yeah, the complications to handle the quirks with "classic rules" were a reason why I pointed at Berry as a programming language with "less surprises".