Versa mileage tracked accuracy

[AlfTupper67]

Hi,

Can anyone one tell me in general how accurate the mileage is on the Versa? I used to use an app on my phone and it seems to differ greatly from that recording. If I walked 5 miles it's is showing as 4.3 on the Versa. Even allowing for the (possible) inaccuracy of the phone free app (Edmundo) this seems a lot. I know you can calibrate the Versa but I really don't want to go down that line. All I wanted was to put on the Versa and get a more accurate reading of the miles that I walked. Any help greatly appreciated. Oh and should I be using the treadmill option when I'm walking as it doesn't have a walking option. 

Moderator edit: Subject for clarity 

[tecishere]

Its big known problem that doesn't look like its getting fixed any time soon i'm afraid. There's a big thread here:

https://community.fitbit.com/t5/Versa-Smartwatches/Distance-on-GPS-map-doesn-t-match-with-exercise-s...

[tecishere]

Its big known problem that doesn't look like its getting fixed any time soon i'm afraid. There's a big thread here:

https://community.fitbit.com/t5/Versa-Smartwatches/Distance-on-GPS-map-doesn-t-match-with-exercise-s...

[tecishere]

Its big known problem that doesn't look like its getting fixed any time soon i'm afraid. There's a big thread here:

https://community.fitbit.com/t5/Versa-Smartwatches/Distance-on-GPS-map-doesn-t-match-with-exercise-s...

[Carl_L]

It's a 'problem' only insofar as the Versa doesn't have inbuilt GPS. Watches with inbuilt GPS are accurate out of the box (but don't have a 5 day battery life) but, so is the Versa if you take the correct steps to ensure your phone battery optimisation isn't breaking the GPS connection whenever it determines Fitbit to be a background app.

I measure (alongside a click wheel) courses for charity events dozens of times a year and, now my phone is set up correctly, never encounter any errors (bar a few meters at the start if I don't allow the GPS connection to settle between launching the app & starting moving).

Edit: Remember that, when GPS connection is broken, Versa can only rely on stride length- best to ensure connected GPS is never lost.

[SunsetRunner]

It's not just the Versa. I have trialed two Ionics with built in GPS and
they were as inaccurate as the Versa. I have a Garmin Forerunner 645 which
last 4 days easy with the GPS on all the time, it tracks distance
perfectly. I can only draw a conclusion that the Fitbits have some inferior
hardware or just bad firmware, in either case this is not being addressed
by the manufacturer

[tecishere]

@Carl_L  I disagree. Both Strava and Fitbit use my phones GPS and Strava is consistent where Fitbi isn't

[Carl_L]

@tecishere Thanks for confirming.

I can only post what I find and that is that, with my current phone (Samsung S10+), and my previous phone (Huawei P20 Pro), Fitbit always tallies with both a click wheel and Viewranger.

You don't say whether you have allowed Fitbit to ignore all battery optimisation & run in background - Strava could be the cause of the problem if it's grabbing focus. Ironically, I first discovered this rabbit hole when Fitbit was the CAUSE of a problem - whenever I tried to map a route in Viewranger, after about 20 mins Fitbit would auto-recognise the exercise & grab focus away from Viewranger, screwing up my mapping.

[tecishere]

@Carl_LTotally understand what you mean. I only started using Strava at teh same time to check what it reported. On my earlier posts you can see that initially I wasnt using Strava while running, it was when it imported the data from Fitbit that I noticed the anomalies. On my run yesterday Fitbit seemd to use the phones GPS without issues as the pace times and maps are complete, so I don't think its an issue for me anyway.

[jleite]

So the fix is to calculate my stride length, what is the point of connecting to GPS if it can't measure a linear distance?

[Rituparna]

I use Fitbit Versa 2. It does not accurately calculate the miles i run. I run the same track everyday 6m. However below is the result Fitbit gave me for 3 consecutive days.

Day 1: 4.6m

Day 2: 4.86m

Day 3: 2.48m

The days i run faster fitbit gives me lesser miles.  It tracks the footsteps instead of distance to calculate the miles. In case your running faster, you'll have lesser footsteps thereby the glitch in calculation.

I am pretty disappointed and would return Fitbit soon. 

[RomComMom_8]

I did this using the puddle method of measuring snd averaging my stride length. It falls right between 27 and 28 inches so fitbit is not far off. I manually measured the distance around my driveway at 1/10 of a mile. However since the last update it is making me walk more like one and a half laps to register 0.1 on my versa lite. Im saying it worked before. Now it doesn't. Also, I have found that I am unable to set a straightforward mileage goal. If I set my goal in the online dashboard at 3 miles per day, it automatically changes it to 1.86 miles in my android app. Again, only since the update has this occurred. If I set my goal at 3 miles in the app, the dashboard changes it to 4.86 🤦‍:female_sign: i am reaching my goal. But the app doesn't show that I did on the main screen. Not enjoying my fitbit as much. Please help.

[RomComMom_8]

I have had my versa lite for 2 years. Im experiencing the same issue with mine. But only since the last update about a month ago. This is a fitbit issue. Not a versa issue. I hope they fix it soon.

[RomComMom_8]

I have a versa lite and I'm having the exact same issue. Only recently and I have had the watch for two years. I know the distance around my driveway is 1/10 of a mile but since the last update, it is showing at 0.07 or 0.08 instead of 0.1. And showing a pace of 24 minute mile when i know I'm walking 3.5mph at least. 

[Helepera]

Failed to make a difference on my Versa 2.

Fitbit seems to be ignoring what is a very wide spread issue. The watches advertised to collect data accurately and it does not do what it purports to do. It is false advertising and very unethical on behalf of Fitbit

[JeffDaniel]

This answer makes absolutely no sense.  Why would FitBit have to calculate anything to determine what a mile is?

Regardless of my stride length - algorithms - where I run comfortably for 10 minutes or I am crawling on my lips in utter pain - a mile is still a mile.   

5,280 feet - on any watch - phone or any other device that measures.  So, you answer tells me that a mile is a variable?

[rockinrobin1204]

I agree with you there, they don't appreciate us. I too wish I could get my money back and get something that works . 

[Surry11]

Your issue is not unique.  The first 3 months I had the Versa 3 I thought it was pretty accurate.  Then I noticed that the distance recorded was dropping while I was walking a known route.  I started to use the Samsung Gearfit app and Google fit to check the Versa 3 accuracy.  What I found was the Versa 3 is about 75-80% accurate in distance and about 85-90% accurate in step count.  I have called and completed several chats sessions over the past 2 months and each time I am told, "this is being elevated for response."  I never hear back.  I now have a card with all the crossed-out case numbers on it from each new customer service contact. 

[Surry11]

I have done all that with my Versa 3 and nothing has changed.  GPS relies on radio signals from GPS satellites and is independent of steps.  So, when my Versa 3 shows GPS connected it should accurately measure distance.  Mine does not.  I have observed my Fitbit step counter not moving for anywhere between 10 and 50 steps while walking a steady pace.  Using my phone GPS and walking a known distance route I have seen Versa 3 lag by 20-25%.  I will say when I had a Charge band that paired with phone GPS I never had these problems.