Question to actively killed shell execution

---

Hi all,
is it possible to avoid this?

It happens when I kill a running script which was started by pimatic shell execution plugin before. Sometimes I want to kill the script which is responsible to control my Jarolift shutters. For example I touch the move down button, normally the shutters move to 80% or 100%, but sometimes it is necessary to stop it on 30% or 40%.

Everything works, but I want to avoid this messages…

@OrTiN said in Question to actively killed shell execution:

Everything works, but I want to avoid this messages…

Did you redirect standard error to null as follows?

execute "sh /home/pi/Homation/jalousien.sh >/dev/null 2>&1"

If this still giving you an error try the following

execute "sh /home/pi/Homation/jalousien.sh >/dev/null 2>&1 || true"

See also https://forum.pimatic.org/topic/45/solved-pimatic-shell-execute-ignore-complete-output

@mwittig: As usual perfect fast support.
">/dev/null 2>&1" was present and therefore I was not sure what went wrong, but with “>/dev/null 2>&1 || true” it works.

Thx!

I’m just being curious, what is the contents of the shell script?

And do you kill the script by logging in to your Pi en using the kill command from the command line? Or do you use a rule to do so?

The script I use for my shutters has 400 line and handle several scenarios triggered by arguments at call, so I try to explain only in short.
When I start the script (by pimatic rule) it does it job. One of the first commands in it is to write its pid into a tmp file by using “echo $$”. This file exists as long as the script runs. The runtime can take up to 30 seconds. Most of this time will be spend to wait for the correct shutter end position (the script sleeps).
When it will be necessary to stop or I decide to move the shutters up during running down, maybe after 6 second I press the stop or up button (button device) in pimatic and the same script will be called via rule with the relevant stop or up argument. At the really beginning (before the script write its pid into the tmp file) it checks for a existing pid file. If this exists the content will be read and used to kill the found process pid.

When I don’t kill the process the script which starts the shutter movement is still alive and stops the shutters once more in the 24 second after the shutter where already stopped in the explained scenario (runtime 30s - 6s until press stop or up).

Unfortunately Jarolift can not be controlled easily directly be pimatic. So I handled it by my magic crazy script…

400 lines? Wow, that’s an extensive script! How is de shutter connected? GPIO, serial, rf? just last week I was able to make my movie screen work using the serial interface of the screen, and that was only one command to make it go up/down/stop

Currently I’m using GPIO’s to control a 8 channel relay board, where the relay contacts are soldered to the relevant push buttons of the Jarolift RF sender unit.

@OrTiN said in Question to actively killed shell execution:

As usual perfect fast support.

Thanks for the positive feedback. You make my day