Fitbit Versa distance inaccurate

[Raffinaderij]

Hello, 

I bought the Fitbit Versa a couple of weeks ago, and love the way it works! But, it seems it isn't doing a very good job at measuring distances,  which I think is one of the main features an activity tracker is supposed to be flawless at. 

I've compared the distance of a run I do regularly on a couple of devices and apps: Apple Watch, Geonaute GPS tracker, Fitbit Charge HR (connected GPS), several iPhones, Samsung Galaxy S9, apps like Strava, Runkeeper, Nike +, Google fit. They all seem to have more or less the same distance at the end of the run, which is: 6.8 - 6.9km. This is more or less correct, as the measured track is 1800m long (I run 3 laps = 5400m) and I have to run an additional 2x725m (1450m) to go to the track and get back home.

Today I did another run with the Fitbit Versa. And it measured only 5,86km.  Which is more then 13% off... Meanwhile I tracked the same run with Strava on my Samsung, which is using the same GPS: 6,8km. You offer a close collab with Strava, but why aren't the distances in sync? And even more, when I do the same run with the Versa a couple of times, the distances aren't the same. For example: I did the same run last week with the Versa: 6,36km. How do you explain this? My tracking apps don't seem to have any problems with locating the GPS signal or staying connected. My Phone is in my pocket which is about 0-50cm from the Versa, bluetooth is on.  Connected GPS is on and working fine the whole time. The run is also showing up on the map in my fitbit app correctly, but the distance is way off. To me this seems to be a software issue, which should be easily resolved in another software updated. Please fix this issue asap! If my old Fitbit Charge HR was able track the distance correctly via the fitbit app, why isn't the Versa? 

Thx

Raf

Moderator edit: subject and format

[missbunnypenny]

Hi All, 

I've had my Versa for a while but have only just started running (was using it predominantly for gym/walking).  I seem to have the opposite issue to others whereby I ran this morning and it logged me as having run 13.06km but when I plotted it in a map, it was only 11.57km.  I wouldn't have noticed except the friend I was running with logged less than me on Strava but had run further, in order to meet me.  I don't have any software updates outstanding and I've tried all restarting everything...  I do have issues with it not syncing and having to go through force stopping the app more and more frequently.  Looking at the comments on this thread, looks like I may need to get comfortable and await several hours on the phone to them!

[Nfrantz111]

This is interesting because I had zero issues with my Versa until the most recent firmware update about a month ago or so? 

I've done all the tricks and it's still WAY off. Calculating at least a half mile over my actual distance. 

[RucknRun]

Yes the last firmware has to be the issue.  It is taking way too long for them to acknowledge it is an issue and fix it.

[SunsetRunner]

This Versa 2 is junk.

I have my GPS on and it is connected via bluetooth and Nike Run Club measures 2.85 which is accurate.  Fitbit measures 3.15.  This is .3 miles is a lot to be off.  I am using it connected via BT. Should be connected to GPS.  IDK when it would ever be accurate to measure distance by stride outside.   

My stride can lengthen or shorten depending on incline, decline, if I am trying to beat someone to the finish line... how could stride ever be accurate?  Why not use connected GPS.  This thing is screwed up bad.  You had one job.

[AlfTupper67]

Yup. Totally agree, the accuracy is not even close.

Sent from my iPad

[Sundarraj]

I have the same problem. I ran a 10K today and one two weeks ago with Fitbit Versa 2 connected to GPS through my phone. Today I waited for it to connect and started it only after it said it has connected. It still gave the distance covered as 11+ km whereas I had run only 10km

[urmoluts]

i must say i use fitbit versa as alarm clock after latest firmware version. i had problem with iphone 6s and after that i use fitbit with oneplus 6. now it connect and lose gps after some hunderd meters. then gps is lost and does not work.

probably if fitbit make new watch with build in gps i think to buy because i like fitbit software but year after year gps connection over bluetooth is getting worse.

[JanmarieJ]

My versa 2 is way off. Almost 1/2 mile short. Please advise. I did not pay what I paid for this watch to have to use another watch or app for tracking miles while walking or running!

[Debbiealyce]

I couldn't agree more. They don't care and won't do anything to rectify
the problem. It doesn't have GPS in the device. They tried to tell my it
was my GPS. I wanted a refund and they wouldn't. The accuracy is never
correct always at least 1/2 mile off. I'll never get another Fitbit when
this one quits working. I'm sorry you are having the same problem.

[parker7887]

Replace with a Garmin....much better!Sent from my Sprint Samsung Galaxy S8.

[parker7887]

I believe the issue doesn't have built in GPS and uses a pace count to determine distance...easiest fix is to buy a Garmin. You will be much happier I promiseSent from my Sprint Samsung Galaxy S8.

[AlfTupper67]

Thanks for that. You are probably right.

Sent from my iPad

[AlfTupper67]

Yes, not fit for purpose as you say. Keeps time good and that’s what it is now used for.

Sent from my iPad

[Mikey_Di]

Hello! 

If this is supposed to be true then why do I have the same issue while biking? I went on a bike ride and the GPS on my phone said it was supposed to 3.3 km my versa lite said it was only 1.8 km. I hope you can give me an answer that can explain this and/or give me a way to fix this.

Best regards,

Mikey.

[RucknRun]

The problem is it used to work great and one of the firmware updated broke it.  I don't understand how long it is taking to fix.

[tecishere]

Same issues here. I love Fitbit as a platform and was going to buy an Ionic but think Apple is the way to go unless this is fixed quick. I look at my Versa as i'm running and think i've done 5K but it reports 4.93.  This is a walk I did today:

From the app:

From the web:

[Aj12334]

I have the same issue. Have been taking the same route & my new Versa 2 is reporting the distance variably as 6.5 to 8.15 km. And each time I started after getting GPS connected confirmation from my mobile - which was in my pocket. In addition, I synchronised the watch with the mobile app to update the step count every 500 steps. Yet the variable difference persists. Yesterday & today I also wore my old Polar RC3 GPS watch for confirmation & on both days it showed distance as 8.29 km. Hope Fitbit or someone can suggest a solution.

The helpline may not be very useful - in my last Blaze, when the battery seemed defective, I was told they have no service Centre world wide. Bought my Versa 2. Then saw a you tube recommendation, ordered a battery on Amazon, replaced it similarly & the Blaze is fully ok!

Am otherwise happy with the Versa 2 - just hope Fitbit can resolve this issue.

[parker7887]

Dude this is has been an issue for nearly 2 years...I doubt they are going to fix it. I am not sure that they can fix with how the watches are made. It may be crap because the watch itself doesn't have GPS. I loved the versa appearance wise but functionality...just buy a Garmin.Sent from my Sprint Samsung Galaxy S8.

[parker7887]

One way to update that I didn't try. Fitbit uses an average stride length
based of gender in height. According to the average for my height and what
my Garmin tracks is a difference between 2 inches this is huge for
measuring distance correct. There is a spot where you can input your own
stride length I believe.

[Coffmansusan5]

Doing the same work out with a friend wo has the same Versa 2. Mine increases the distance by almost a mile.  My friend's and my Samsung S9 record accurately. So dissapointed.!