johnpolasek wrote:Initially, it looked like gtreece's procedure was working for me; my phone was registered as in the back yard rather than in the house, but that was OK, and the home fence showed up on the map. BUT, then this morning, I noticed that the phone hadn't moved from it's original location, it still showed 0.5 charge and was listed as not charging even though it has been sitting on the charger all night and the phone shows 100%... I thought that maybe the plugin simply hadn't been refreshing, but the timestamp for the device was this morning at 5:12. Does the plugin not change any data (other than the time) until the phone moves some significant amount?

As I stated in a different email..... How often the data is updated depends on Apple.

Find my iDevices can request an update as often as wished. For example, I could request an update every minute. But Apple, may only update the Find My iPhone data every 15 minutes? Every 30 minutes? Every 5 minutes? Or maybe, the iPhone is smart, and if it is moving it will update more often to the Find My iPhone server...?

The simple fact, is that we don't know, and we don't have any way to find out.

Out of frustration with this, I decoded to experimented with Google's Latitude.... I loaded Latitude on my iPhone, and according to Latitude, at 1 am, my iPhone was 5 miles away (near a college), and for the next 3-4 hours, roamed within a 1 mile sphere around the college. This happened multiple times over the next two nights....

Now this was with Google's own Latitude client.... I'm pretty sure that the iPhone didn't leave the bedside....

Now back to Find my iPhone / Find my iDevice. FMID relies on the data that Apple returns, since I don't have any way to validate the data that is returned, I have to treat it as valid....

So, if for some reason Apple decided to return unchanged data from 2 hours ago, I don't have a way to reject it... Or to caution you about it...

Until Apple opens the feature to developers officially, there isn't much that I can do....

- Ben

Another pester question... I know it varies, but roughly how long does a forced status update usually take? Now that I've got your great little plugin working and variables which tell me whether everybody's iPhone is at home or not every 15 minutes, I've been thinking of using the Garage Door status and motion sensors as a low end security system; whenever the motion sensors that turn on the kitchen and den lights see movement or the garage door opens, I've already got a conditional trigger that if all the phones are listed as out, does a forced update to see if somebody got home after the last 15 minute update, with the plan that IF after the update occurs there are STILL no phones at home, a second trigger can send me an email... so the only question is how long to delay before checking for the results of the forced update?

Ben,
Are there any timelines on reducing the CPU usage for indigo plugin host process? This plugin is chewing up a ton of usage and running a whole lot hotter than it usually does.

johnpolasek wrote:Another pester question... I know it varies, but roughly how long does a forced status update usually take? Now that I've got your great little plugin working and variables which tell me whether everybody's iPhone is at home or not every 15 minutes, I've been thinking of using the Garage Door status and motion sensors as a low end security system; whenever the motion sensors that turn on the kitchen and den lights see movement or the garage door opens, I've already got a conditional trigger that if all the phones are listed as out, does a forced update to see if somebody got home after the last 15 minute update, with the plan that IF after the update occurs there are STILL no phones at home, a second trigger can send me an email... so the only question is how long to delay before checking for the results of the forced update?

I think it varies depending on how many devices you have in your account. I have six total and it takes 30-60 seconds after a forced update to retrieve location information.

Dewster35 wrote:Ben,
Are there any timelines on reducing the CPU usage for indigo plugin host process? This plugin is chewing up a ton of usage and running a whole lot hotter than it usually does.

Find My iDevices only eats up CPU time, when it's actually running. And that is CPU bound waiting for the other end (Apple's servers) for the majority of the time.

If your seeing any significant CPU usage during the run, then there's something potentially not kosher there....

The only time where there is any significant CPU issues might be when the plugin first starts up, and that is due to polling MobileMe / iCloud for the identies of the devices....

Can you email me at Benjamin AT schollnick DOT net, with a debug log of a FMID session?

johnpolasek wrote:Another pester question... I know it varies, but roughly how long does a forced status update usually take? Now that I've got your great little plugin working and variables which tell me whether everybody's iPhone is at home or not every 15 minutes, I've been thinking of using the Garage Door status and motion sensors as a low end security system; whenever the motion sensors that turn on the kitchen and den lights see movement or the garage door opens, I've already got a conditional trigger that if all the phones are listed as out, does a forced update to see if somebody got home after the last 15 minute update, with the plan that IF after the update occurs there are STILL no phones at home, a second trigger can send me an email... so the only question is how long to delay before checking for the results of the forced update?

In theory a moment or two....

But in practice I have seen Apple's server take a varied amount of time to update. Anywhere from a few moments, to 15-30 minutes.... More often than not, it's a few moments... But I have seen longer periods, although, I believe that might be due to throttling on Apple's part, so if your only updates every 15 minutes or so, you probably will update quickly....

But once again, only Apple can tell you the rules of how that works....

bschollnick2 wrote:Find My iDevices only eats up CPU time, when it's actually running. And that is CPU bound waiting for the other end (Apple's servers) for the majority of the time.

If your seeing any significant CPU usage during the run, then there's something potentially not kosher there....

The only time where there is any significant CPU issues might be when the plugin first starts up, and that is due to polling MobileMe / iCloud for the identies of the devices....

Can you email me at Benjamin AT schollnick DOT net, with a debug log of a FMID session?

I keep getting this and the google voice plug-in mixed up... both deal with my phone so I guess on some level it makes sense, but there are no issues with find my idevices. Sorry for the mixup.

Dewster35 wrote:I keep getting this and the google voice plug-in mixed up... both deal with my phone so I guess on some level it makes sense, but there are no issues with find my idevices. Sorry for the mixup.

Understandable....I'm just glad that everything is fine with FMID.

I am now getting these same errors as listed below (copied from page 3 of this thread). Another URL change perhaps?

bschollnick2 wrote:

hamw wrote:Yes, I think that's helpful. I'd add that if you are west of the prime meridian your longitude begins with a (-) sign.

got another issue. I replaced my PLM (had a 2413 fail, subbed in a 2414 and then replaced with a new 2413) and introduced some kind of error.

Code: Select all

 Find My IDevices Error          plugin runConcurrentThread function returned or failed; will attempt again in 10 seconds
  Find My IDevices                Preferences were updated, reloading Preferences...
  Find My IDevices                Find My iDevice Plugin Loaded...
  Find My IDevices Debug          UpdateTime - 15
  Find My IDevices Debug          username - XXXXXXX@me.com
  Find My IDevices Debug          Password - XXXXXXX
  Find My IDevices Debug          Debug Mode is On (Only recommended for Testing Purposes)
  Find My IDevices Debug          Running Concurrent Thread
  Find My IDevices Error          Invalid MobileMe Account Information
  Find My IDevices Error          Please configure Find My iDevice with your MobileMe credentials.
  Find My IDevices                   Retrieving location data
  Find My IDevices Error          Error in plugin execution runConcurrentThread:

Traceback (most recent call last):
  File "plugin.py", line 358, in runConcurrentThread
  File "plugin.py", line 318, in run_search_for_idevices
  File "plugin.py", line 238, in fetch_updated_MobileMe_Locations
  File "plugin.py", line 206, in fetch_MobileMe_Device_Names
<type 'exceptions.AttributeError'>: 'Plugin' object has no attribute 'MobileMeAPI'

  Find My IDevices Error          plugin runConcurrentThread function returned or failed; will attempt again in 10 seconds
  Received INSTEON                "Thermostat MBR" temperature changed to 76.0
  Find My IDevices Debug          Running Concurrent Thread
  Find My IDevices Error          Invalid MobileMe Account Information
  Find My IDevices Error          Please configure Find My iDevice with your MobileMe credentials.
  Find My IDevices                   Retrieving location data
  Find My IDevices Error          Error in plugin execution runConcurrentThread:

Traceback (most recent call last):
  File "plugin.py", line 358, in runConcurrentThread
  File "plugin.py", line 318, in run_search_for_idevices
  File "plugin.py", line 238, in fetch_updated_MobileMe_Locations
  File "plugin.py", line 206, in fetch_MobileMe_Device_Names
<type 'exceptions.AttributeError'>: 'Plugin' object has no attribute 'MobileMeAPI'

  Find My IDevices Error          plugin runConcurrentThread function returned or failed; will attempt again in 10 seconds


I deleted all the phones, checked MobileMe, deleted FMiD, re upped them all, did disable and reenable and still get this error. Also tried stopping and re-starting the server. The machine has also been rebooted. Ideas?

Pure bad timing...

It appears that Apple has switched over to a new URL for the Find My iPhone server... I will be testing a change over the weekend that appears to resolve this issue... This appears to be related to the iCloud service...

midd wrote:I am now getting these same errors as listed below (copied from page 3 of this thread). Another URL change perhaps?

They probably have changed the Version ID that needs to be passed to the service again... Sadly, there is no way to automate this, but I'm thinking of adding a remote poll on startup for the current version ID's.... But I don't know if the user base would like that....

I'm a little busy at work, but I'll work on vetting this and packaging up an updated version...

- Benjamin

I would not be opposed to a poll every 24 hours as long as we can set the time that it occurs. It beats you having to manually update it every time and if it does happen to change in the middle of the day, we would only be without it for a few hours... or if you could have a forced refresh to check to see if there are changes.

Dewster35 wrote:I would not be opposed to a poll every 24 hours as long as we can set the time that it occurs. It beats you having to manually update it every time and if it does happen to change in the middle of the day, we would only be without it for a few hours... or if you could have a forced refresh to check to see if there are changes.

I think there maybe a slight issue in communication.

Find My iDevices polls as often as you wish. The Time/Date stamp in the device states, is the time/date stamp of that poll.

Apple seems to cache the data, and there is no way for Find My iDevices to know if the data that Apple sends, is current, or cached.

Apple has not documented when they cache the results... And yes, I could compare the results to the previous run, but how would I be able to tell if the identical result is due to the user sitting in the same chair for an hour or two, or Apple caching the results over the last 30 minutes.

Find My iDevices returns the data that Apple sends to it, without Apple making the Find My iphoto interface official, and documenting it, I don't see how the results can be made any more reliable.... I simply don't control what data is being sent back from Apple.

If you are receiving duplicate results each time, and your being forced to run a manual refresh to get a accurate result? Chances are your refresh time is set too low. That seems to be one of the triggers for caching, but that's just a guess. The lowest refresh rate I suggest is 15 minutes...

- Benjamin

Im fairly new to the Mac file system but I absolutely cant find the second installation path:

"/Plugins/Library/Application Support/Perceptive Automation/Indigo 5/IndigoWebServer/Plugins"

Where the heck is it???

I believe the path should be:

Code: Select all

/Library/Application Support/Perceptive Automation/Indigo 5/IndigoWebServer/Plugins/

matt (support) wrote:I believe the path should be:

Code: Select all

/Library/Application Support/Perceptive Automation/Indigo 5/IndigoWebServer/Plugins/

Yes, that is correct...