mgolden50 wrote:Glenn,
Thanks for the update! It's working much better having the map enable/disable function working. I using it with Bing maps and their API key. However, when enabled the map does not pop up when the locations are refreshed. So it looks like no effective difference between enabled or disabled.
The most disconcerting behavior is even that at an 800 meters geofence radius, a stationary phone still pops in and out of the geofence periodically. Do you think that tase something to do with the Apple API?
It's still a more reliable presence detection solution than using IFFT web hooks installed on the phones. A wonderful alternative!
Thanks again,
Mike
Hi
Hmmm.. not sure I follow the ‘pop up’ comment and it is possible you are missing some functionality.
The map only ‘pops up’ - by this I mean open a browser window if have debug maps enabled. This is for testing only, and shouldn’t remain enabled.
The functionality of maps is to save a jpg image of the selected map for each iFriend enabled. There are saved in documents under iFindFriends. These images are always updated. The aim is to link to these images on a Indigo control page - showing current location for iFriend. You can also overlay on the control page - arrow/cross-hair as wish, location is always the middle of the image.
The geofence leaving. Hmmm. Occasionally there is a bad ‘lock’ or poor accuracy on location. Middle of night, charging in middle of house somewhere. I do have it set to take into account accuracy entering or exiting geofences, basically will ignore low accuracy location results (unless sizeable percentage of geofence away). It is possible that this has changed, it is somewhat hard to troubleshoot as need a log of the exit (when not a exit) to fine tune. Will see what I can generate at my end.
Edit:I have had a look and seems to be functioning correctly - will log for a while.
But I would add that:
Increasing your geofence size decreases its accuracy(Plugin calculates accuracy in meters divided by distance from geofence as a ratio of accuracy/distance).
Currently uses a ratio of 2 - less than 2 happy to act, greater than 2 will ignore.
This is by necessity given accuracy.
eg. If had 2km geofence, accuracy of 500m +/- wouldn’t be a problem, and would still remain/or exit geofence depending on location. (ratio of 500/2000, or 1/4)
If had a 200m geofence an accuracy of 500m would mean that this result would be ignored until better accuracy. (ratio 500/200, or >2).
So you may be making things worse by setting a 800m radius, but all means keep this one, but also have a tighter 100m geofence as well.
Glenn