<![CDATA[Local URLs for API services]]>What URL pattern can I use to trigger exposed services locally on my device without going through cloud.onion.io?

Once deployed, my Omega will not be able to connect to the internet (due to poor connectivity in a remote area), but I still want other devices on the local network to be able to trigger events from remote sensors.

Apologies if this has already been documented somewhere.

Thanks,
benthenchelys

]]>http://community.onion.io/topic/836/local-urls-for-api-servicesRSS for NodeSat, 14 Mar 2026 07:53:52 GMTSun, 12 Jun 2016 17:42:59 GMT60<![CDATA[Reply to Local URLs for API services on Mon, 13 Jun 2016 05:11:18 GMT]]>What URL pattern can I use to trigger exposed services locally on my device without going through cloud.onion.io?

Once deployed, my Omega will not be able to connect to the internet (due to poor connectivity in a remote area), but I still want other devices on the local network to be able to trigger events from remote sensors.

Apologies if this has already been documented somewhere.

Thanks,
benthenchelys

]]>http://community.onion.io/post/5851http://community.onion.io/post/5851Mon, 13 Jun 2016 05:11:18 GMT<![CDATA[Reply to Local URLs for API services on Mon, 13 Jun 2016 22:06:36 GMT]]>@benthenchelys Good question!
Unfortunately, there are no local URL endpoints for the services exposed on the Cloud.
That's where our Cloud <-> Device connection comes into play.

However, all of those services are available on the command-line through the ubus. Check out our ubus tutorials for more info.

Your other devices and sensors can potentially use SSH to trigger ubus commands. Hope that helps!

]]>http://community.onion.io/post/5855http://community.onion.io/post/5855Mon, 13 Jun 2016 22:06:36 GMT