I was looking at the very nifty (do we still use that word ?) Mobilinc app and GeoFencing..

I may just pick it up..but wanted to find out first if there are any provisions for stand alone GeoFencing with ISY Native ?

 

or do we need to use Mobilinc ?

 

thanks

 

Matt

Nothing native in the ISY, you would need Mobilinc on iOS or Mobilinc & Tasker on Android.

 

-Xathros

thanks Xathros ..

Does Mobilinc need to be enabled or opened on task or can the App be closed and Geo-sensing will still be active ?

 

Thanks Again

I can only speak for the iOS version. On my iPhone, as long as ML is in the background and the phone is awake, it works like a charm. If the phone is snoozing, it can sometimes take a minute or more for it to notice that it has crossed a boundary.

 

-Xathros

I can only speak for the iOS version.

 

In the case of android, tasker handles the geo-location duties. When tasker senses crossing some threshold, it will call on mobilinc to perform the insteon duties. My experience that the state of mobilinc matters not at all. Tasker runs in the background.

Hi Matt,

 

This is Wes from MobiLinc chiming in. For Android/Tasker/MobiLinc, oberkc is dead on. Tasker handles the geo-fence threshold detection and hands off the command to MobiLinc to process all in the background. MobiLinc does not need to come to the foreground.

 

The only thing you need to be aware of with geo-fencing on MobiLinc for iOS is that the MobiLinc app needs to be allowed to run in the background. You accomplish this by not force closing the app or killing it when not in use. Simply exit MobiLinc like any other app and it will do it's thing in the background monitoring for boundary crossing with the help of iOS. See our website on Geo-fencing including specific notes on iOS 7: http://mobilinc.com/features/geofence/

 

When iOS detects a boundary crossing it tells MobiLinc and MobiLinc then executes in the background to tell your ISY that the region has just been crossed.

 

Xathros is also correct. iOS could take a up to a few minutes to detect a crossing. In our testing, it usually detects the crossing instantly, but this depends on a lot of factors. See the website link for notes on this.

 

If you have any other questions, feel free to email us at: support@mobilinc.com

 

Wes

Hi Wes..

I am trying your demo lite version.. And the geofence scenarios when integrated are truly limitless..

Nice work

 

To make sure I don't leave my wife in the dark and set the alarm on her.. I would need to create a program with a condition based on her device and condition setting.

 

If matt phone is 0

And Michele phone is not 0

Then

Xxx

 

and the the reverse condition of the above would also need to be set...I presume multiple conditions would need to be set if the kids are home .. Etc..

 

Do you have a "best practice" ISY script available ? .. For different scenarios .. Etc ..

 

Thanks...

Hi Matt,

 

I don't really have any pre-canned scripts that work for most scenarios. MobiLinc/Tasker/geofencing is a powerful combination, but with that power and openness comes complexity and uniqueness to each install since rarely two people will use these features the same way.

 

You are on the right track with multiple devices. A more basic example is looking for all the phones (people) to be gone (0) before taking any action. If anyone comes home then "wake the house" back up with whatever that means to you. Lights on, disarm, etc.

 

The best thing I can suggest is to dive in and experiment and let us know what neat things you come up with!

 

Wes

Having problem...have Mobilinc Pro on wife's phone and try to setup a new geofence a little further out. I created a 500m fence but it's not showing up on the isy. When I look on the iPhone, it says "Variable Not Found". Any ideas?

Were you able to do a "Tap to Sync with ISY "

Not sure if that would enable or update the variable

 

Matt

Thanks so much for reply...

 

Yes, did "Download All" and "Updates Only"...no joy.

I can only speak for the iOS version.

 

In the case of android, tasker handles the geo-location duties. When tasker senses crossing some threshold, it will call on mobilinc to perform the insteon duties. My experience that the state of mobilinc matters not at all. Tasker runs in the background.

 

Just reading this thread and noticed this. Mobilelinc is not necessary to geo-fence, only tasker. Tasker can send REST commands to ISY directly. The simplest thing to do might be to have Tasker set a variable on ISY which indicates you have entered the geo-fence and then let ISY do the rest. Similarly, you set Tasker to "un" set the variable when you exit the geofence. Tasker is an incredibly powerful tool, albeit not the simplest to figure out.

Apostolakisl is right. Only Tasker is necessary to do this.

 

I was previously doing this my DD-WRT router with a script but it wasn't very reliable. Via REST it would set a variable on ISY when devices associated. I'm now in the process of doing this via Tasker instead so that it's based on soley on Wi-Fi association. The only drawback is the need to do it on each device in the family vs in one place on my DD-WRT router.

Apostolakisl is right. Only Tasker is necessary to do this.

 

I was previously doing this my DD-WRT router with a script but it wasn't very reliable. Via REST it would set a variable on ISY when devices associated. I'm now in the process of doing this via Tasker instead so that it's based on soley on Wi-Fi association. The only drawback is the need to do it on each device in the family vs in one place on my DD-WRT router.

Have you done this yet?  I could use some direction...Thanks