Problem using executeCommandLine and curl

Setup, Configuration and Use Beginners
1

Hi,

I’m trying to execute a simple url call to push a notification to pushbullet, using curl and executeCommandLine

The following works from the command line:

curl --header 'Access-Token: [my API]' -X POST https://api.pushbullet.com/v2/pushes --header 'Content-Type: application/json' --data-binary '{"type": "note", "title": "Test Title", "body": "Test Body"}'

So I expected this would work from an openhab rule:

executeCommandLine("curl --header 'Access-Token: [my-API]' -X POST https://api.pushbullet.com/v2/pushes --header 'Content-Type: application/json' --data-binary '{\"type\": \"note\", \"title\": \"Test Title\", \"body\": \"Test Body\"}'")

but it doesn’t - does anyone have any insight into what might be the problem?

thanks!

Dan

2

Hi Dan,

It seems that the command line needs to be formatted in a special way. Check out this example.

Cheers,
Marcel

1 Like
3

Thanks - not sure I follow from that what formatting changes are needed. Do you know if there’s a summary somewhere?

4

Ok,
I test and with this it works:

executeCommandLine("curl@@-k@@-H@@Access-Token: [apiToken]@@-XPOST@@https://api.pushbullet.com/v2/pushes@@-H@@Content-Type: application/json@@--data-binary@@{\"type\": \"note\", \"title\": \"Test Title\", \"body\": \"Test Body\"}@@")
5

Wow - thank you. Bloody complicated!

6

Hello
Wasn’t sure if I should start a new thread or hijack this one?
I am trying to call a script with executeCommandLine but it doesn’t seem to work.

This works in command line but not in rules:

/usr/bin/python3 /volume1/homes/mark/scripts/pythonremote/pythonremote.py --message SGS6 message

I have tried below without luck:

/usr/bin/python3@@/volume1/homes/mark/scripts/pythonremote/pythonremote.py@@--message@@SGS6@@message

Any suggestions?

7

I used to execute Python scripts successfully with this syntax

executeCommandLine("python@@./configurations/scripts/ivona_brian.py@@Something relevant and witty@@")

That was getting a bit messy and my attempts at doing it via the exec binding were not going well.

Someone on another thread mentioned this method described here: http://jpmens.net/2014/02/15/who-phoned-fritzbox-openhab-and-mqtt

I adapted it and after the usual 4 hours of hair pulling, it worked!

I have no idea why you have to put …

 + " "

…after the variable.

I guess it is just one of the many “precious” little tests that OpenHAB likes to put us through, to abandon everything we have learned from nearly every other language :smile:

rule "Ivona TTS"
when
    Item Speak_Ivona changed
then
{
    var String command
    var String commandFull

    logDebug("Ivona_TTS", "String " + Speak_Ivona.state + " ")
    command = "python3@@/opt/openhab/configurations/scripts/ivona_brian.py@@"
    commandFull = executeCommandLine(command + Speak_Ivona.state + " ")
}

end

So I can now just update the item with what I want it to say

    postUpdate(Speak_Ivona, "Hinkle Finkle DInkle Doo")

Hope it helps and bonus points if you know who said those words :wink:

2 Likes
8

I tried use this syntax in a rule executeCommandLine("python@@./home/pi/drive.py ") or
executeCommandLine(“python@@/home/pi/drive.py “) or
executeCommandLine(”/usr/bin/python /home/pi/drive.py”) etc…

the log response is always positive (for exemple: "executed commandLine ‘python drive.py’ ")
but the script doesn’t work as it does when I launch it normally from the terminal
I’m running on a rasp jessie
what should I write? thanks

9

I am not sure, I appear to be struggling a little with it this week. What once worked, now doesn’t.

I think my issues are permission related due to removing my manual install and reinstalling via apt-get (I’m on Wheezy on a Pi). I.e. having to make sure script and rule files were now owned by user “openhab” rather than “pi”. I also had to add openhab to the group “audio”.

Not sure my experience is relevant but it might point you in the right direction :slight_smile:

10

If you haven’t already may be worth temporarily running openhab as root, just to see if that fixes things. If it does then definitely a permissions issue.

11

It wasn’t a permission issue, I had to specify the path of a file in the script. thank you anyway!