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

[Prof]

The same thing happened to me a couple of years ago.  I spent several days trying different things that were recommended.  They ended up sending me a new Blaze.  It works fine.

Moderator edit: content

[nickfletchercc]

I have also had the same issue over the last 2 or 3 days. We walk our dog twice a day on the same 3.4 Km route, for the last couple of days it has been measure by my Blaze at around 2 Km.

I have the device linked to a Samsung Galaxy S9 which has also started measuring the incorrectly even though it maps correctly on Strava.

[frank_h]

Also noticed this over the last week. The last accurate distance my Blaze recorded (GPS connected to S9) was on 14th Sep. Since then distances have been way off although the route has been mapped correctly. Today I ran a regular route of around 5km which was recorded as 3.3km, and similar errors have occurred last couple of times. Very frustrating, can’t work out why this is suddenly happening 

[RachelM81]

I'm having the same problem with distance and pace, I also have it linked to a samsung S9. I cant seem to find a way to reset it and its saying the software is upto date.Very frustrating

[nickfletchercc]

My guess is that the problem is with the S9, are you using Strava to record the run? It might be that, I updated Strava and all seems OK now.

[RachelM81]

Yes my fitbit is synced with strava. I'll try and update strava and see if that fixes it. Thanks

[bfc62dcfd]

I have had the same issue however unlike most in this post I use a iPhone 7

[frank_h]

A quick update on this. I checked the FitBit app was up to date and also Strava (although I assumed data was just passed to Strava on completion). My midweek run was much more accurate, first km was slow but the others has a reasonable timing, maybe 10-15 s/km slower than usual. Repeated the same run last night and the poor tracking returned. Overall average pace 2min/km slower than midweek. Hard to say whether the fault lies with FitBit or GPS on my phone. I’m going to make sure I have an accurate GPS fix on the phone next time to investigate further. Odd as no issues in 12 months prior to the last 2 weeks.

[nickfletchercc]

To be honest I have given up using the Fitbit, I am now using a Garmin device. From what I was seeing, the issue is with the communication between the Fitbit and the GPS. It seemed to me that if I received an email or a text message the communication would be interrupted and would not always be re-established. If it did reconnect I would get odd reading, during one run it claimed that I had completed a kilometre at 94 KM/H. Strava does not get involved with the recording of the data, I just find it easier to analyse what is going on via Strava than the Fitbit app.

[Machin51]

Yep I have the same issue with distances and also using S9 

Found out it I start the run using my watch instead of the app then it's even worse. 

I'm not using Strava though just Fitbit. 

I've updated everything and even calibrated my GPS but still getting poor results.

[Vickiw89]

I'm having the exact same issue. Was totally on 9th September when I did the great North run but all my runs and walks since have been off. Strava works fine and the gps on phone is fine as when I use these without the blaze it's accurate. really frustrating as GNR recorded perfect distance but last week 3 miles records as 1.8 miles.  Crazy. The map on Strava is correct just wrong miles. I'm using a Google pixel phone. Have reinstalled Fitbit app and no joy. Reset the Fitbit several times too. Anyone found a fix? 

[frank_h]

The fact that phone GPS is fine and the problem occurs across Apple and Android phones makes me think it is a problem on the Fitbit side. The release of app version 3.6 seems to be 18th September and would coincide with the poor tracking I’ve seen. Might be a case of waiting for an update and hoping it sorts things out. Would be good if there was some support or comment from Fitbit on this, as people will quickly lose confidence in their products

[bfc62dcfd]

I would hope they comment as there seems to be a growing concern regarding fitbit response to some Blaze issues. Ive read in other forums that some people weren’t pleased with the support and suggested buying other products

Sent from my iPhone

[Vickiw89]

I agree. Although my issues started on evening of 17th September but did seem to concide with an update. It's been almost two weeks though now. Fitbit need to sort it out. Fed up with it not recording everything right. Even normal walks and steps that aren't linked to Strava are incorrect on the watch but fine when I use just the phone. Bad service

[bfc62dcfd]

Sadly using even the phone is inconsistent

Sent from my iPhone

[frank_h]

Just looking back through the thread and most problems are around 17th September. Seems too much of a coincidence for this not to be related to the update around that time. Fitbit definitely need to provide some support on this matter now.

[AlejandraFitbit]

Hello guys, I hope you are doing fine.

I am sorry for the delay in respond and appreciate all the efforts in trying to fix this distance issue. If you are experiencing problems with your distance information, you should use specific run, walk, or hike modes for precise exercise stats and distance and pace information.

For more information about tracking exercise, see our help article: How do I track exercise and activity with my Fitbit device?.

Let me know if you need anything else. 🙂

[frank_h]

Thanks for the response.

The Run exercise mode on the Blaze has been used for tracking. It has been very reliable for me for 12 months+ until mid September when several people also reported the same issue with distance. Can you confirm whether this is software problem, as the date seems to coincide with the 3.6 app update. Thanks!

[Vickiw89]

I've had the same problem as Frank H, been working absolutely fine for 13 months plus. Did the great north run and it was bang on. Carried on doing exactly the same thing as always but it stopped working around 17/18th September.