Why did MileIQ catch an extra drive?

The most common reason MileIQ would catch a drive in error is that one MileIQ account is logged into multiple devices (i.e. iPad and iPhone or iPhone and Android).

Unfortunately, it is a problem to try and run MileIQ on two devices at once, as this can cause quite a bit of confusion for the MileIQ drive processor. If this is the case, please delete the app off one of the devices (or sign out and sign back in with a different email on the second device). 
 
If the account was not logged into multiple devices at one time, please check our Drive Detection best practices to ensure that the device is set up optimally for drive detection.

If everything is set up correctly, have you moved recently? It may sound odd, but WiFi base stations are programmed to remember location information. So, if you move and plug in an old base station in a new location, it may take up to a week or more for the base station to 'learn' the new location.
 
In the meantime, the device and the base station may be reporting different location information and if the move was a relatively short distance from your old address, our drive processor may occasionally think that a drive has occurred even when one hasn't. We are working to eventually account for this unique oddity.

If you think the above base station issue may apply to you, we have a couple of things for you to try to help the base station update its location information more quickly: 

  • One trick is to keep Apple or Google maps open on the device while it's connected to WiFi (for a couple of hours). The idea here is that the GPS function in the maps application will help the base station to 're-learn' the new, correct location. This has been successful in many cases.
  • If that isn't practical or doesn't work, you can try updating your WiFi information with Skyhook, a partner with mobile device device makers for WiFi location information. To do so, enter your base station MAC address in the Skyhook form here. They have documentation for finding the required information, but feel free to reach back out if you hit a snag.
Have more questions? Submit a request

Comments

Article is closed for comments.

Powered by Zendesk