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 average pace due to pause

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

‎10-05-2017 18:14

‎10-05-2017 18:14

I am a new Fitbit owner and am feeling frustrations when using my Blaze for running. I just went for a run and generally average about a 5:30 pace. When I look at the km splits, they are all showing well over this. The first km shows my average pace as 6:10 and I never ran that slow during the run. I did pause my run a couple times while waiting at intersections and this seems to be accounted into the average. Isn't the purpose of the pause button not to account for this? Also, it seems that it takes a while for the pace to "catch up." While almost sprinting down a hill, my watch showed that I was running at a pace of 7:45! I have never in my life run a pace over 7 minutes. This is all very frustrating and makes me want to go back to using my free Runkeeper app and ditch this watch.

Best Answer
0 Votes
2 REPLIES 2

‎10-08-2017 04:04

‎10-08-2017 04:04

A warm welcome to the Community @allic17. Regarding to the accuracy of the Blaze, could you please provide me some screenshots about the information you are seeing? In the meantime, you can a look at this post, where you will be able to find some tips to make your Blaze more accurate.

 

Hope to hear from you soon. Woman Happy

Alejandra | Community Moderator, Fitbit

If you like something I recommended, I encourage you to mark that reply as "Best Answer". 🙂

Best Answer
0 Votes

‎10-08-2017 10:12

In response to AlejandraFitbit

‎10-08-2017 10:12

Just did the same route today and came see 2 serious issues.
1. It seem to take Fitbit about 200m before showing a pace that is somewhat accurate. While running it also seems to lag.
2. When I pause my run, the timer pauses but the pace is still being tracked and so are the laps. Therefore my average pace is much higher and my lap cues (which are set for 5 minutes) are not actually every 5 minutes of my run.
This is all very frustrating. It does not see that Fitbit is a suitable watch for runners.
Best Answer
0 Votes