Distance doesn't match map

[Mollysuds]

I went for a ride this morning. The map fitbit generated of my ride seems about right, but the distance is way out. I rode 8.9 km according to the path I mapped on Google Earth, but fitbit says my 52 minute ride from home, around the lake and back home was 1.5km. I had my phone in my pocket, with bluetooth and mobile data set to switched on.
Have I set something wrong? Suggestions please on how to make fitbit read the distance correctly.

Is it a clue that my fitbit also delays and sometimes simply does not turn on when I turn my wrist. I need to press the button to get it to wake up. And also that it fails to register many of my steps?....I have walked to another room and back and it still shows no steps. I was standing up all yesterday afternoon, working between two tables 3 steps apart, and it registered only the steps I took along the verandah and driveway.

[AlvaroFitbit · Accepted solution]

@Mollysuds Welcome to the Fitbit Community! It's great to have you here! Currently there is a bug in which distance may not be correct while using the Connected GPS function. You can try using the Run option as it has been found to provide better results with GPS but at this time the issue is still being investigated so I can only ask for your patience while the team resolve this.

Let me now how it goes!

[Mollysuds]

Thank you

[GrannyYiayia]

Thank you. I am having this problem with connected GPS too. Glad to hear it’s just a glitch and should be resolved soon.

[Farnicus]

Is there any progress on fixing this bug? I'm having the same problem when I use the GPS Connected run feature. This is frustrating.

[Algotron]

I'd like to see some progress here too.

It's hard to see how Charge 2 computes a running distance which neither follows its own GPS map plotting nor, failing that, properly multiplies steps by stride. Needless to say I carry my GPS-enabled phone and use the Run activity. 

That it happens when I cycle is bad enough. But when running I see my cardio fitness score go down not because I am slower but because the distance is systematically off. 

My suggestion to the FitBit developer team is that if they use the GPS map preferentially to establish distance. Although not 100% accurate, it is much closer to the actual course run than whatever method is currently used. 

[hcarroll]

Was this bug ever fixed? I've started having this problem crop up with my Flex 2 in the last couple of weeks (now a year after the original post). It's really frustrating.

Thanks!

[SalimahD]

I have this same issue with my Versa 2 - the GPS distance is way off compared to Samsung mapping or the phone GPS.  I walk daily with my husband and his more accurate with Samsung watch compared to my Fitbit and this is getting very frustrating 😞