https://www.dropbox.com/s/ut7tg2e4x4spqdj/fingscan-v-4-15-1.zip?dl=1FINGSCAN v 4.15.1
Added feature to link FINGscan <—> iFind (version>=1.0.60 required)
With this link FINGscan now can use information from:
FING
PING
ASUS router WiFi association info
Mother/Cookies
iFind distance
to determine if devices or groups of devices or one device in a group of devices is/are home or away and trigger the proper events
iFind link:What it does if enabled:iFind has a module that will “tickle”/ trigger FINGscan when a device has changed its distance to home. FINGscan in turn will then query the proper iFIND device/state to get distance to home info. It will calculate the speed and direction ( coming home or going away ) and estimate the expected arrival time. It will then set the refresh frequency of iFind of that device to 70% of the expected arrival time ( between 10 seconds and 12 minutes). When the device ( e.g. iPhone) enters home (with 50 meters of home as defined in iFind) it will use that information to trigger events ie Home (or Away if it leaves) as defined in FINGscan config.
When the device is at home or > 20km away FINGscan will revert back to iFind defaults to determine the next refresh (ie home, night schedules etc.)
From a priority point of view: If FING things that a device is home it will always use that, as it is positive identifiable info: the device answered a ping or is sending packages on your local network. It must be home. Once FING times out (no message for x minutes - as defined in FINGscan Configuration) iFIND information will take over. But also here there is a timeout you can set ie if there is no info for > xx minutes it will also ignore iFind info eg if you are on a plane etc.
How to enable:1. in iFind in Menu/Plugin/iFind/Configure enable the FINGscan link checkbox
2. in FINGscan select iFind like in the attached screen shot:
- Screen Shot 2015-10-28 at 4.25.48 PM.png (128.59 KiB) Viewed 20498 times
The cool part in this that it minimizes queries between the plugins by using the “tickle” trick. It is like a trigger, but the user does not have to set anything up and adopts automatically to changes in parameters.
Thanks to Mike for reviving the iFind/iDevice functionality (We missed that for a long time!!) and for implementing the tickler.
if anyone is interested in how this work, let me know... or you can check the iFind and FINGscan plugins yourself
Karl