help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Inaccurate exercise elevation graphs

Replies are disabled for this topic. Start a new one or visit our Help Center.

‎05-04-2020 03:34 - last edited on ‎09-22-2020 14:23 by Fitbit Moderator

‎05-04-2020 03:34 - last edited on ‎09-22-2020 14:23 by Fitbit Moderator

Hi,

 

My Versa 2 seems to have some problem causing elevation graphs recorded during runs to become erratic towards the end of the runs. I'll attach a couple of screenshots from a run to demonstrate. The first one is from the Fitbit app, the second one is the same run as seen in Strava. The run is recorded via the Fitbit app, Strava is not open during the run, it only receives the data from Fitbit because I have connected the accounts:

 

FitbitFitbitStravaStrava

 

As you can see, the Fitbit elevation curve becomes very erratic slightly before halfway through the run and shows a preposterous elevation gain (almost 500m) and ends at a different altitude than it starts even though the run in circular. In reality the run is not very hilly. The Strava elevation curve and total elevation are definitely more accurate. What's odd is that even the Strava data should originate from my Fitbit, as I'm not using Strava at all during the run. Almost all my runs show this behaviour, just a few seem unaffected. Does the Fitbit app have some bug in displaying/analysing elevation data correctly? Or is Strava somehow able to correct the corrupted data from Fitbit? Anybody else with a Versa 2 seeing something like this?

 

I'm using firmware 35.70.7.21 on the Versa and the latest app version on my iPhone.

 

Moderator Edit: Clarified subject

Best Answer
Labels:
0 Votes
0 REPLIES 0