Versa not tracking distances accurately

[CarDow]

I do the same 5k run every day and  on my versa it can differ by 500m-1k?? I have updated my software on my phone(android) and the gps is connected as is bluetooth.

[Rich_Laue]

Are you using the Fitbit App or the Versa to record your runs, @CarDow? I assume you start the run recording through the Fitbit app

Does the map look the same every day?

[CarDow]

I start the run on my versa but I have the phone with me when I run. The maps are pretty much the same each time

⁣Get BlueMail for Android ​

[Rich_Laue]

Have you setup your stride in fitbit?

Fitbit supplements the GPS with the users stride for distance. 

[BornClimber]

I am having the exact same issue.

I went for a run on two different days and took the exact same route. The map recorded in the app is exactly the same, implying the connected GPS ran correctly. But the distance recorded on day 1 was 3.25 miles (which is correct as per Google Maps) but today was recorded as 2.72 miles. This completely throws off my average pace and my VO2 max assessment.

Is this an error in the app or the watch? If the GPS points are recorded correctly then why cant the app be smart enough to use google maps (or other maps) and know the exact distance?

Using stride length when there is GPS available is a *very foolish design*, because one can run slow or fast depending on day and their goal. I was trying to max out my run today to see my fastest capability. If the app just counts this as a regular stride then that's absolutely useless.

FitBit Versa.

Firmware version 32.70.8.0.

Android App Version 3.21 (20243500)

[BornClimber]

I should add that the error in distance calculation happened *after* the most recent Firmware update.

i.e. the correct distance was two days ago. Then I updated to 32.70.8.0

And then today's measured run distance was wrong (too short) by 0.5 miles.