Blaze issues with pace and distance

[jennandlincoln]

Yesterday I noticed that my pace and distance calculations on my Blaze are very incorrect. I walk the same route at work daily and typically get 2.24 km as my distance. The last two days, it has came back as 1.4 km. Also, my usual pace is about 14:25. The last two days it was recorded as 23:40.

Has this happened to anyone else? Know how to fix it? I haven't updated anything or changed anything.

Moderator edit: subject

[Machin51]

Yep same here, all good until a couple of weeks ago. Last week I installed Strava and ran with that instead and it was accurate. Fitbit was still showing a shorter distance so definitely the app and not my phone or GPS etc.

Bit pointless using my really.

[Vickiw89]

Exactly the same. Ran with Strava and was 3.98 miles. Fitbit said 3.25 miles. It's affecting all my stats too like fitness score as it's picking my heart rate up but pace is different. Sometimes up to 19 minute miles instead of 10 and a half for the same heart rate. Fitness score dropped from 41 to 38 since the issue. The Fitbit is totally useless if it isn't fixed surely we should get a refund as it's faulty? 

[nickfletchercc]

So, out of desperation I purchased a Versa 2 today to see if it would do any better. A measured 3 Km walk was measured at 2.4 Km, the Versa 2 is going back tomorrow and I am going to pick up a Garmin 647 instead. A real shame as I love the Fitbit app it is better than Garmin connect in my humble opinion, but if they can't make a device which can perform the sole function it is made to do, why should I waste my money on it?

[frank_h]

Dear Fitbit,

I think the contributors to this thread need some information about what, if anything, is being done your side to look into this issue.

You need to accept we know how to use the device via connected GPS and that it simply is not providing accurate information.

Look at the date the thread started, the evidence provided by many people about the timing of the problem. It started around September 17 and is happening across different phones. People have confirmed their phone tracks just fine without Fitbit. Indeed a new fitbit Versa also displays poor tracking information. And considering the 3.6 app was released about 17 September it seems to point towards this being the problem.

This has been reported on here for over 2 weeks and there has been no serious response from Fitbit. People may be spending money needlessly on replacement devices if this is a software problem. As a minimum I think people need to know whether this has been raised as a potential software issue and kept informed regarding the status and likely fix dates.

[TwinkleStarr]

I've just done a post as i'm having the same problem.

My 5k race came up as 3.6k. That's no good to me at all, very frustrating. 

This has only started happening in the last couple of weeks.

I have restarted it several times 

[TwinkleStarr]

Same has happened to me and now on Strava as my Blaze is linked to it

[Machin51]

Literally just finished my run.  My Strava and Fitbit are not linked. Strava came back as 10.6km while Fitbit logged 8.73km so no improvement since I last tried my watch.

[ohhhlily]

I did a 5 mile run this morning and tracked it with the Fitbit run. It only got 3.9 but the route I took measured 5. Is this an issue that can easily be fixed? Because this is not the first time it's happened to me and it looks like it's happening to other people as well.

[TwinkleStarr]

Yes its happened to me several times now . Unreliable now I'm afraid

[jennandlincoln]

Thank you all for your replies.  I have been in touch daily with Fitbit now for 3 weeks and all I'm getting is, update this, reload that, double track with GPS (but not the one I picked, has to be one of their apps... sigh), so I have to do it again now.  I don't really see an end to this and I'm giving up after this next GPS tracking, as it's gotten ridiculous and nothing has changed.

Thank you all for also pointing out that our issues occurred roughly the same date!  I hadnt realized there had been an update, but this makes a lot of sense! I am looking forward to seeing this fixed. Hopefully soon!

Thank you to the person who posted about buying a Versa and having the same issue.  This solidified my decision to not upgrade my Blaze to the Versa.   I haven't decided top what yet, but it will not be a fitbit.

I'm also disappointed that Fitbit corporate hasn't reached out to this group to acknowledge the issue and offer an idea of when this will be resolved.

I appreciate everyone who took the time to weigh in on this.  Knowing I am not alone in this has made a big difference!

[gkkm]

Mine is very similar. Hoping for an answer,

[gkkm]

That would be great!  I know I’m missing out on a lot of steps!

[gkkm]

Mine is linked to an iPhone tho!

[gkkm]

I have an 8

[Nakshatra]

So I am not the only one facing the problem.

I am experiencing the same issue..and yes, it started to surface about 2 weeks back. The distance and pace are all awry..the gps map is correct but the distance recorded is about 30% less and hence the pace too is all wrong.

Sad, that Fitbit team hasn't been able to replicate and provide an update/fix to the problem.

FitbitTeam- We need a fix since it really seems the last update screwed the tracking all together.

[frank_h]

Seems to fit the same pattern - welcome to the club!

Wall of silence from Fitbit I'm afraid, no engagement from the moderators on here either. Useless response from them, highly disappointing. 

[jennandlincoln]

Has anyone else noticed an improvement?! I just did a walk that wasn't my usual route, but the pace/distance seems like it might be accurate! Has there been a new update in the last week? I hope this has improved for all of you!

[Machin51]

No unfortunately not for me. I ran 11km  today and Fitbit logged it as 9km. I did notice a bug fix update but obviously not for this bug 

[frank_h]

Not tried today but yesterday Fitbit recorded 3.9km, whereas it was recorded on my Google maps timeline as 5.5km. 

[Jimbard]

I've had the same issue. Prior to september my fitbit was accurate on  a regular 6 mile run. Since September it is measuring about 30 percent less although runkeeper is still measuring 6 miles. I have also checked routes with google maps which shows the same as with Runkeeper. Again my fitness score has suddenly dropped as a result