Why doesn't Shell execution protocol pass a parameter to raspbian?

Designer 2.5
1

Hello…

Here’s my setup and sequence of events:

Command:

Name: runShell

Protocol: Shell execution protocol

Path: /home/pi/openremote/bin/ech.sh

Command abcd

parameter:

Button:

Command: runShell

Script in /home/pi/openremote/bin/ech.sh :

#!/bin/sh

echo “param $1” >> /home/pi/echout

date >> /home/pi/echout

Run:

First, one local execution:

./openremote/bin/ech.sh wxyz

Then, three taps on the iPod’s button:

tap tap tap

Results in file echout:

param wxyz

Mon Feb 19 22:02:32 PST 2018

param

Mon Feb 19 22:03:24 PST 2018

param

Mon Feb 19 22:03:29 PST 2018

param

Mon Feb 19 22:03:32 PST 2018

Why didn’t Shell execution protocol pass abcd ???

73,

Gary

2

UPDATE It works as advertised after a reboot! Is there a fix in the works? 73, Gary

3

Hi
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

https://groups.google.com/forum/m/#!topic/openremotecommunity/OoHpROaS8As

Excerpt######

Please create a command in designer that looks like this :-

Command name :-

csvmaker

Protocol :-

Shell execution protocol

path :-

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

/opt/OpenRemote-Controller/webapps/jscanvas/csvmaker.sh

command :-

–value=${param}

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”)

Dummy

4

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.

Kind regards,
Michal Rutka