05-18-2016 14:15
05-18-2016 14:15
06-06-2016 22:46
06-06-2016 22:46
I have had my Blaze for just over a week. Accuracy was not an issue until a few days ago. I have a set route that I walk with my wife. First time walked it the Blaze indicated just over 6,000 steps. Walked it today and it indicated just over 3,600 steps. It is incredibly frustrating when I read that Best Buy is yanking the Blaze from the shelves and there is nothing being put out by Fitbit. I'm to the point of returning it!
06-06-2016 23:38
06-06-2016 23:38
"There is no help to receive. Since the last "update" it just doesnt work corectly. We all either have to wait and hope they fix the issue or return our FitBits. FYI, its been since April 21st that these problems started."
MikeS, are you saying that before the last update that the Blaze was fine for steps and distance ?
I got mine about April 15th and don't know if I did an update -- probably did when I first got it, don't remember.
06-07-2016 07:04
06-07-2016 07:04
06-09-2016 17:27
06-09-2016 17:27
Adjust your walking stride length. That worked for me. If you are a regular walker your stride is generally longer than normal when you are excersizing. Garmin = .26, Blaze = .18. .26/.18 = 1.44 Go into your settings and multiply whatever the stride length default is by 1.44. See if that does not help.
06-09-2016 17:31
06-09-2016 17:31
06-09-2016 17:38
06-09-2016 17:38
I don't understand the step count issue. I'm not having a problem. I don't want to insult people's intelligence by suggesting things they may have already done. I wear mine on my non-dominant arm and have it set that way in tracker settings. That would be one thing I could think would miss steps as I know, with my Fitbit Charge, if you wore it on dominant arm but were set to non-dominant, the extra movement of your arm caused steps to register when you did not take them. Perhaps the reverse is also true.
06-09-2016 17:40
06-09-2016 17:40
I'm using firmware version 178.200.3
Anyone know what the latest is?
06-09-2016 17:49
06-09-2016 17:49
06-09-2016 18:14
06-09-2016 18:14
06-10-2016 14:50
06-10-2016 14:50
See @FerdinandFitbit's post here
06-11-2016 13:18 - edited 06-11-2016 13:20
06-11-2016 13:18 - edited 06-11-2016 13:20
I'm having the same problem. It under estimates mileage on average by approximately 25%. I also have the One and I wore them both (without syncing) on the treadmill today. The steps were 1500 higher on the One and the miles were very close to the treadmill. At work, I can get up and walk for 30 steps or so before the Blaze starts counting.....it never does a catch up either. Thinking about sending it back. If it worked right I'd love it!
I've made sure I'm wearing it in the correct position on my arm and have also adjusted my stride lenght.
06-19-2016 22:24 - edited 06-19-2016 23:15
06-19-2016 22:24 - edited 06-19-2016 23:15
My Blaze has been off by anywhere from 20%-30% in calculating steps and distance. Today I walked 4.17 miles. Based on the stride length that is defaulted for me I should have had 8,987 steps. Blaze only counted 5,972. That is a 34% difference!!! This is completely unacceptable. Oh and I also mowed the lawn and it showed I went on a bike ride.
06-20-2016 02:09
06-20-2016 02:09
06-20-2016 11:49
06-20-2016 11:49
06-20-2016 13:07
06-20-2016 13:07
apparently NOT everyone is having an issue (but all the complaints are here so it seems like it). I have no idea what will happen (as i slog toward the dreaded set-up and connecting my phone again), but we will find out.
06-20-2016 13:59
06-20-2016 13:59
06-20-2016 17:59
06-20-2016 17:59
06-21-2016 08:16
06-21-2016 08:16
Hey everyone, please see the post I made over here and post in that thread if you have anything to add.
10-24-2016 18:58
10-24-2016 18:58
My new fitbit blaze is measuring distance inaccurately. I see that people have been complaining about this for months. Is there a fix or should I return the device?
10-25-2016 05:35
10-25-2016 05:35