possible rule? -> if "$somevariable" then $someothervariable=execute "some command"

---

Hi,

I like to have a rule behave like:

if "$somevariable" is changed then $someothervariable=execute "echo $TimeInSecs | awk '{printf(\"%02d:%02d\",($1/60/60%24),($1/60%60))}'"

I already tried some variations but I can’t get it to work.

A workaround could be:

if "$somevariable" is changed then execute "echo $TimeInSecs | awk '{printf(\"%02d:%02d\",($1/60/60%24),($1/60%60))}' | curl --insecure -X PATCH --header \"Content-Type:application/json\"  --user admin:XXX@localhost/api/variables/someothervariable"

But I prefer the first option for its simplicity.
Is that possible?

Edit: I found that in post 262 the user asks the same question but he did not get an answer at that time.

@Harry-van-der-Wolf Thanks for referencing the other thread which already brought up the idea of using a ShellSensor. However, the ShellSensor is currently only executed at time intervals. To get the ShellSensor updated on demand a “execute” or “update” action is required to be perform on the sensor device. Rather than just adding the new behaviour to the ShellSensor (which would interfere with time-based updates anyway), I would implement a new device class (possibly a superclass of the ShellSensor, e.g. “PassiveShellSensor”). I think this needs further thought. May be another @Developer comes up with a better idea.

Thanks for your reply. Actually my question is a spin-off of topic 933, but I didn’t want to ask an off-topic question.
When acting on a button I need an event not a ShellSensor. I want/need to have an (almost) immediate, responsive reaction when I press a button. That means that the ShellSensor needs to run at 200 millisecs or so, which gives an extra unneccessary load on the system (but I did not measure that load) and it gives some screen “flickering” as the variable is also updated at that rate.

Currently the ShellSensor has a “command” attribute. It would be nice if it had a “rule” attribute.
This could either be an "if event then …"
ór, to keep the rules and devices separated, it could be a “rule”: “rule_id” statement, that will trigger the device based on that specified rule.
Although that last functionality is also more or less offered by the variablesDevice in combination with a rule, which leads me back to my oiginal question

did u get the if working?

Not in the way I asked it in this topic.

But I created a work-around by using the script by @envagyok (actually a slightly modified script)