<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with ubus fast-gpio]]></title><description><![CDATA[A list of topics that have been tagged with ubus fast-gpio]]></description><link>http://community.onion.io/tags/ubus fast-gpio</link><generator>RSS for Node</generator><lastBuildDate>Sat, 18 Jul 2026 02:36:43 GMT</lastBuildDate><atom:link href="http://community.onion.io/tags/ubus fast-gpio.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 29 Oct 2017 01:36:15 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[fast-gpio pulses syntax from onion cloud (ubus syntax)]]></title><description><![CDATA[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.
]]></description><link>http://community.onion.io/topic/2455/fast-gpio-pulses-syntax-from-onion-cloud-ubus-syntax</link><guid isPermaLink="true">http://community.onion.io/topic/2455/fast-gpio-pulses-syntax-from-onion-cloud-ubus-syntax</guid><dc:creator><![CDATA[Ricardo Cassia]]></dc:creator><pubDate>Sun, 29 Oct 2017 01:36:15 GMT</pubDate></item></channel></rss>