Here’s my setup and sequence of events:
Protocol: Shell execution protocol
Script in /home/pi/openremote/bin/ech.sh :
echo “param $1” >> /home/pi/echout
date >> /home/pi/echout
First, one local execution:
Then, three taps on the iPod’s button:
tap tap tap
Results in file echout:
Mon Feb 19 22:02:32 PST 2018
Mon Feb 19 22:03:24 PST 2018
Mon Feb 19 22:03:29 PST 2018
Mon Feb 19 22:03:32 PST 2018
Why didn’t Shell execution protocol pass abcd ???
UPDATE It works as advertised after a reboot! Is there a fix in the works? 73, Gary
I don’t know if this helps our hinders…
I struggled to get the shell execution command to work, until I put a dummy sensor in.
This is a setup I use in a couple of machines
Please create a command in designer that looks like this :-
Command name :-
Shell execution protocol
Note that the path must be the exact path from root to the csvmaker.sh script file.
WITHOUT a preceding “.”
Your path may differ from what is shown here
Polling Interval ;- BLANK
Regular Expression :- BLANK
Sensor name :- (I found I have to create a custom sensor for this to work, which I called “Dummy”)
The shell execution protocol has a bug, which causes that after update of the command from the designer the controller needs a cold reboot. This is very old bug, but still there obviously.