Geofencing Agent about huginn HOT 16 CLOSED

@chriseidhof, want to start a new issue to discuss building an iOS app? What feature set do you see it having?

from huginn.

That's a good idea. You could almost do it with a TriggerAgent consuming the UserLocationAgent's feed.

from huginn.

Well, geofencing on the client-side is much more preferable since it has more accuracy ond consumes less power - but it would require to push the fencing information to the device and thus a special client

from huginn.

Probably a good fit with #166

from huginn.

Added to agent suggestions list in #353

from huginn.

One thing you might want to look at is Owntracks, which publishes geolocations using MQTT.

from huginn.

Possible solutions for client side reporting of location are the rosumi gem for iOS and Tasker or something similar for Android.

from huginn.

For personal geofencing you'd have at most maybe 15 fences.. wouldn't it be preferable to be able to generate the fences on huginn, then push coords to a huginn mobile app for handling client side, and when breached could push to huginn for next steps.

that way the same container could be used for all "location events" (ble, wifi, gps, secret handshake) and be a standard way to handle it?

from huginn.

It'd be cool if someone wants to work on this!

from huginn.

If there is help needed with the iOS app, I might be able to do that...

from huginn.

Well, we don't really have an iOS app right now. It'd be cool if someone wanted to make one!

from huginn.

I have been thinking about this for a long while, though I didn't know the term geofencing.
I wonder if we should extend TriggerAgent, add a dedicated agent or implement a Liquid extension for use from any agent.
Also, a location picker UI shall be a must-have, so I've been pondering implementing an input widget after seeing @dsander's HTML based configurator complete. etc. etc...

from huginn.

I think before we go down the app route we should probably implement/define a decent API for accessing Huginn.

Unless you find the current post interface sufficient?

—
Sent from Mailbox

On Thu, Oct 30, 2014 at 12:33 PM, Akinori MUSHA [email protected]
wrote:

I have been thinking about this for a long white, though I didn't know the term geofencing.
I wonder if we should extend TriggerAgent, add a dedicated agent or implement a Liquid extension for use from any agent.

Also, a location picker UI shall be a must-have, so I've been pondering implementing an input widget after seeing @dsander's HTML based configurator complete. etc. etc...

Reply to this email directly or view it on GitHub:
#5 (comment)

from huginn.

Absolutely. I couldn't agree more.... Does anybody know what are the best
practices for building good APIs? I've been out of Rails for quite a while.

As for the app side, we can consume basically anything... although JSON is
probably easiest.

I think it'd be really cool if we could start with basic login, and get the
events out... maybe later on also support for listing and modifying
agents....

from huginn.

I'm going to implement GeofencingAgent. Is the Haversine formula considered good enough for typical use cases, independent of where you live/are?

from huginn.

Wikipedia says that the haversine formula and law of cosines can't be guaranteed correct to better than 0.5%. That seems like it could be an issue for local geofences, but I don't really know.

from huginn.