06-26-2017 10:02 - edited 06-26-2017 10:05
06-26-2017 10:02 - edited 06-26-2017 10:05
I have been through the replacement of my Charge 2 three times and then they sent me a Blaze. I have the same problem with all of them. My step count, distance and pace are severely under counted. I have tried the following things and I always have the app open on my iPhone 6 Plus:
This morning, I walked 2.17 miles per Runkeeper (which always matches walks tracked using the Fitbit app, Google Maps and my car's odometer) at a pace of 18:10. Since my stride is set to 28.8 inches, I should have 4774 steps. This is what my Blaze tracked using Connected GPS: 2.07 miles, pace 19:03, steps 3733.
Even if I concede that a 5% difference in distance is OK and within acceptable limits, 3733 steps with a distance of 2.07 miles gives me a stride of 35 inches which at 5'5" is most likely not attainable for me and wildly inaccurate.
The only thing I can see is in the pace display on the browser dashboard shows that I stop many times but I did not stop once. When I check my husband's pace display for the same walk (matching our strides), his shows a constant pace with no drop outs. I move my arms at a similar swing to his and am not carrying anything or not moving my arms.
Does anyone have an idea of what I could do to make my Blaze more accurate? I've been dealing with this since September and am at my wits end. I periodically go back and use my Fitbit One because it's accurate but without the features I like.
06-26-2017 12:40
06-26-2017 12:40
I'd like to know as well. I just upgraded to this one from the charge 2 and this blaze and absolutely awful at counting steps. I was walking around my kitchen cooking for a solid 30min and it didn't count a single step. Very frustrating, and not worth the money spent.
07-06-2017 19:14
07-06-2017 19:14
Update:
i ditched my Blaze. After almost a year of troubleshooting and inaccuracy, I bought an Apple Watch. $70 increase in price is worth it to have an accurate device.
Bye bye Fitbit, I'll most likely never buy a Fitbit again.
07-07-2017 09:41
07-07-2017 09:41
I'm having the same problem. My Charge HR worked great. Fitbit Blaze is only recording 3 miles for every 4 that I walk. That type of inaccuracy is unacceptable. Still no solutions from fitbit!
07-07-2017 11:00
07-07-2017 11:00
I too have the experience the blaze undercounting steps/distance. I had planned on recalculating my stride length to see if that gives me more accurate steps and distance but I am fairly certain I set that accurately some time ago.
I use my blaze in a comparative way so I am motivated by the info I get from it but this inaccuaracy seems not to be up to the standard for current fitness devices. Maybe the Fitbit Rep will have something to say about these multiple posts on this problem!?!
07-14-2017 20:12
07-14-2017 20:12
Update:
i ditched my Blaze. After almost a year of troubleshooting and inaccuracy, I bought an Apple Watch. $70 increase in price is worth it to have an accurate device.
Bye bye Fitbit, I'll most likely never buy a Fitbit again.
07-29-2017 10:17
07-29-2017 10:17
I and my friend this morning.
1. Started at same time 7.08 AM.
2. Both ran about 5.8 miles together and then he walked ablut a mile as he was tired. The pace was about 11'40" average for the 5.8.
3. I ran extra 3.3 (total 9.1) and arrived at 9.29.53 (Approximately 1 hr 22 min for 9.1).
4. My average pace on Blaze showed 9'52". Its off by 10%!! (9.1 miles / 01: 22 min = 9'.01" ).
5. Here is the strage thing. When we both looked at the pace of the FIRST five miles (His Run keeper vs my Blaze), his showed around 11'40". Blaze was showing 10'10", 10'18", 9'46", 9'48", 9'45"......
6. Looks from the others experience, I cant expect an answer from FITBIT and ditch it.
07-29-2017 10:58
07-29-2017 10:58
The Blaze has been a major disappointment. The amount of time to update and modify settings with the same outcome of missing up to 2000 to 3500 steps and 7-10 flights of stairs daily demonstrates the product is not dependable and certainly does not render the value paid for the device.