Maximilian, thank you very much for your help.

I experimented a little more and also concluded that the method doesn't work for the pulses option. However, I did find a work around.

Instead of using the fast-gpio access through the ubus call (which would allow me access from anywhere), I created a 1-liner script that looks like this:

fast-gpio pulses 19 $1 3

and named it /root/gpio19

Going back to the Onion Cloud, I chose the method launch-process, and as the command I set:

/root/gpio19 /root/input.csv

The response is:

{
"resp": "Command to launch in background: /root/gpio19 /root/1.on.csv"
}

and it actually does what was supposed to!

By the way, I'm using this to create a middle man between the Internet and my RF controlled outlets. I can now develop apps or crontabs to turn things on and off through the house.

Maximilian, thank you very much for your help.

I experimented a little more and also concluded that the method doesn't work for the pulses option. However, I did find a work around.

Instead of using the fast-gpio access through the ubus call (which would allow me access from anywhere), I created a 1-liner script that looks like this:

fast-gpio pulses 19 $1 3

and named it /root/gpio19

Going back to the Onion Cloud, I chose the method launch-process, and as the command I set:

/root/gpio19 /root/input.csv

The response is:

{
"resp": "Command to launch in background: /root/gpio19 /root/1.on.csv"
}

and it actually does what was supposed to!

By the way, I'm using this to create a middle man between the Internet and my RF controlled outlets. I can now develop apps or crontabs to turn things on and off through the house.

Thank you very much for your explanation. However, I have been successfully running the utility in its normal use case, which is from the command line in a shell. This works just fine:

root@Omega:~# fast-gpio pulses 19 /root/input.csv 3
Pulses GPIO19: r)wr)w,

Now, I would like to run it from the Onion Cloud. Since one of methods to do it, is to use the ubus format, for debugging purposes, I ran ubus locally in the CLI, and I could get the read option to work:

root@Omega:/# ubus call onion fast-gpio '{"params":{"read":"19"}}'
{
"cmd": "Read",
"pin": 19,
"val": "0"
}

However, I can't get the syntax of the pulses option right. I tried the following:

root@Omega:/# ubus call onion fast-gpio '{"params":{"pulses":{"19","/root/input.csv","3"}}}'
Failed to parse message data

root@Omega:/# ubus call onion fast-gpio '{"params":{"pulses":{"19" "/root/input.csv" "3"}}}'
Failed to parse message data

root@Omega:/# ubus call onion fast-gpio '{"params":{"pulses":"19","/root/input.csv","3"}}'
Failed to parse message data

root@Omega:/# ubus call onion fast-gpio '{"params":{"pulses":"19 /root/input.csv 3"}}'
Command failed: Invalid argument

root@Omega:/# ubus call onion fast-gpio '{"params":{"pulses":"19,/root/input.csv,3"}}'
Command failed: Invalid argument

Do you know how the syntax for the ubus looks like for the pulses option?

Thank you!

Hi,

I have been trying to use the fast-gpio utility with the pulses option from onion cloud without success. I can make it work with the read option, which only takes a single parameter after the read, but the pulses needs 3 parameters. Does anybody now the syntax for it?

Thank you,

Ricardo.