substantial discrepancy in distance

[Victamon]

Earlier today I went on a walk with my dogs of approximately 0.98miles, which I recorded using my Sense 2 (running on most current firmware﹘ 60.20001.194.86) using Connected GPS from its linked Android smartphone (which was then running app version 4.11.fitbit-mobile- 110035547- 606605685). During the walk I did record a few (enumerating six) laps—which might not have any, but conceivably could have some, bearing on this glitch—which whem shown in mile increments happen to add up 0.99miles.

From the app﹘which I just updated from the Google PlayStore, to version 4.12.1.fitbit-mobile- 110039540- 614832183 even though its description thereat didn't mention anything about Connected GPS nor Sense 2﹘ under list of recent activities, this one is identified as a 0.97mile 30mins walk using GPS. So far so good. However, upon going into and inspecting it apparently the "Pace" track view failed to record or account for a large portion on the front end of the walk. (Were not for privacy concern, I would upload screenshots depicting precisely what am describing here in words.) So, I navigate to the desktop overview (fitbit.com/activities😞 from the list, this recent one shows as a 0.6mile (ostensibly meaning 0.60miles) Walk that lasted 30mins26secs, which curiously seems to correlate roughly with the visible path shown in the app for "Pace" (instead of "Heart rate zones"). Clicking into it, its details at the top does indicate total distance of 0.97miles with a 50'38" pace.. so _hopefully_ that is what the TCX file displays as well. Yet the singular map drawn (as the web view evidently has just one, instead of two) shows a 'final distance' icon of 0.60miles. And the four data metrics (one of which derived from two others, pace) plotted against ⦇scalar cumulative position⦈ apparently abruptly cease at slightly past halfway (i.e. toward the tail-, instead of the front-, end); whereas the same metrics plotted against ⦇elapsed time⦈ look more ordinary, though not entirely—pace goes away at around same point, and elevation goes abnormally flat at the same (although the bottom two categories that are each derived from biometric data appear pretty ordinary).

[Infodomoticapty]

Hola Amigo, a mi me pasa algo parecido no concuerda la distancia que mide mi sense 2 vs la que mide la aplicación desde el teléfono por ejemplo, hoy camine según el teléfono 3.08 Km y según el Sense 2 solo 2.5 Km. Tampoco se como se resuleve esto y del por que sucede, Saludos

[Victamon]

@Infodomoticapty  ¿On your 3.08㎞ self-propelled movement (as according to part or all of the app⳺, whereas the  watch live showed merely 2.50 km at conclusion⳻), did you use Bluetooth+ConnectedGPS from your smartphone to your Sense2 for the entire activity; Or none of it (⸮using instead the builtin GPS receiver of your Sense2)?, or some of each? ¿What does the map appear as﹖, from app ۽ web ‐access?

[Dundeeplodder]

I had the same issue today. The Fitbit app shows a distance of 3.5 miles but when existed to Strava it shown 2.34 miles. On the activity map in Fitbit the GPS map in the Heart Rate Zone shows the full distance. The Pace map and data cuts off the after 2.34 miles! How can the Fitbit data be different from the same activity, on the same watch in the same App! See screenshots below. 

 

 

 

 

[L15aM]

I've had exactly the same problem on multiple occasions over the last couple of months. Always the last mile (ish)  that gets lost regardless of the length of the run. Fitbit have told me to factory reset, to uninstall and reinstall.app, to make sure it is not also trying to track from my phone and then to wait for app version 4.14. None of these things have worked. Tracker works fine during a run, shows pace data for the full duration, GPS map for heart rate is accurate but pace is not. We are now at a point where they have asked me to export my data, I assume so they can look further. Not all that much help when I'm running London in 5 days and currently have a watch that I can't trust to do the job. If I get to the end and it tells me I have done 25 miles I'll lose my mind!! Hugely frustrated ☹️