09-14-2018 06:58 - edited 09-14-2018 07:00
09-14-2018 06:58 - edited 09-14-2018 07:00
My Fitbit keeps failing with tracking distance correctly, super annoying as now I have to have multiple apps running just to make sure I get an accurate distance.
Here's the first complete fail of the run
This was a 5k run that FitBit failed to track:
https://www.dropbox.com/s/qslrah5uzgnfgh0/Screenshot_20180914-093528_Fitbit.jpg?dl=0
2 same distance runs, again FitBit did not track the correct info
1. https://www.dropbox.com/s/whcmsmxn6zdj256/Screenshot_20180914-093601_Fitbit.jpg?dl=0
2. https://www.dropbox.com/s/8r0ys0epm472h5r/Screenshot_20180914-093614_Fitbit.jpg?dl=0
And this is a correct tracking by Samsung Health. I know this is correct, I even checked on Google maps.
https://www.dropbox.com/s/fy1pm8r2hiwa4e8/Screenshot_20180914-093640_Samsung%20Health.jpg?dl=0
09-14-2018 08:03
09-14-2018 08:03
If you want/need to track distance and route (on a map), your best option would be a Fitbit that has built-in GPS (Ionic or Surge). If it’s not the case, you need to have your phone with you and rely on Fitbit’s Connected GPS feature, which is supported by a few trackers (e.g. Versa, Charge 2 etc.). For that feature to work as intended, there has to be a proper connection between your Fitbit and your phone’s GPS (via the Fitbit app) when you start the activity. Based on your first snapshot, that connection was not established. Next time you record an activity you want to map, make sure the connection is established before you start running. There should be a small symbol on your tracker indicating it’s the case. If you want to avoid the hassle, upgrade to an Ionic, which picks up GPS signal very reliably, at least in my own experience.
Dominique | Finland
Ionic, Aria, Flyer, TrendWeight | Windows 7, OS X 10.13.5 | Motorola Moto G6 (Android 9), iPad Air (iOS 12.4.4)
Take a look at the Fitbit help site for further assistance and information.
09-14-2018 09:06 - edited 09-14-2018 09:08
09-14-2018 09:06 - edited 09-14-2018 09:08
Thanks for your reply.
I have a Versa watch and always run with my phone. But my watch keeps disconnecting all the time. Even though everything is fine on the phone.
The picture #2 (https://www.dropbox.com/s/8r0ys0epm472h5r/Screenshot_20180914-093614_Fitbit.jpg?dl=0) and The last one (ttps://www.dropbox.com/s/fy1pm8r2hiwa4e8/Screenshot_20180914-093640_Samsung%20Health.jpg?dl=0) are the very same run. So this means that the phone GPS is working just fine, while Versa is not connected most of the time.
It used to work before but failing now
09-14-2018 11:24
09-14-2018 11:24
you can try adjusting your stride length, but I've had the same problems. I use map my ride to get the accurate distance (verified with my car's odometer) and Fitbit just to record the exercise. It's not perfect, but then, what is?
09-14-2018 11:34
09-14-2018 11:34
It just sucks as I was hoping to get a FitBit and have all my info tracked there. I guess there is no easy solution 😞
Hopefully, FitBit will fix this issue soon.
09-16-2018 11:15
09-16-2018 11:15
I think what is happening is your bluetooth is failing to stay connected. Which is kind of a combined fault between the phone and fitbit. I myself use my ionic which is built in GPS so I know it is accurate. I get your frustration, but when we rely on two separate technologies to accomplish one goal there is always a chance of failure....
Elena | Pennsylvania
09-17-2018 12:51
09-17-2018 12:51
in addition to May My Ride (to get the accurate info) I set my fitbit exercise option to walk (when I'm walking) so the exercise shows up on the dashboard. It'll always be lower than actual, but that is better than higher than actual.