Hello community.
I Need that slider back to value 0 before Item “Volumen” receive update and to execute two (executeCommandLine), for that reason I have created a rule that execute the next code, at the end it send command 0, but I present the issue that this command(Volumen.sendCommand(0) execute indefinitely, it never stop.
Hi, i don’t exactly what you want to do, but as understand your rule is a dead-end rule, as you send an update- Command to your Trigger-Item (Volumen), with Volumen.sendCommand(0).
Peter has definitely identified one of the problems for sure.
To elaborate.
Volumen receives an update
Execute the two command lines
I’m surprised you don’t get an error on the logInfo since it is incorrect syntax.
You send a command to Volumen
Volumen receives and update, return to step 2.
And so around and around you go never stopping.
That’s your first problem. The second problem is I believe the Slider can send more than one command based on one movement of the slider (I could be wrong on that point, I don’t use Sliders). This will cause the Rule to execute multiple times.
You need to use a Design Pattern: Proxy Item that gets displayed on your sitemap. This triggers a Rule that sends a command to Volumen. Then you need to send the 0 command back to the Proxy Item, which will break the infinite loop.
Hello fibu and Rich.
I just test this rule and it works fine, the mainly problem was I dont understood the difference between “received update” and “changed status”.
rule "vol+"
when
Item Volumen changed
then
val eject=executeCommandLine("mosquitto_pub -u openhabian -P 7121799422 -t broadlink/televisor/boton/volsubir -m play-34ea346ff7ac" ,100000)
val eject1=executeCommandLine("mosquitto_pub -u openhabian -P 7121799422 -t broadlink/televisor/boton/volsubir -m play-34ea346ff7ac" ,100000)
val eject2=executeCommandLine("mosquitto_pub -u openhabian -P 7121799422 -t broadlink/televisor/boton/volsubir -m play-34ea346ff7ac" ,100000)
logInfo("mqtt", eject, eject1, eject2)
Volumen.sendCommand(0)
end
Look at the docs for Rules which describes all the Rules triggers. The tl;dr is:
received command: triggers the Rule immediately only when an Item receives a command
changed: triggers the Rule when an Item changes state. The Item may change state as a result of a command or an update
received update: triggers when the Item receives an update. An update may not actually indicate that an Item changed state. A command to an Item will also cause that Item to update as well.
