04-21-2016 12:12 - edited 09-12-2016 10:52
04-21-2016 12:12 - edited 09-12-2016 10:52
Update 5/6/16:
Hey all,
I've been keeping a close eye on this thread, and I wanted to give a quick update.
For reports of Blaze steps and/or distance being inaccurate, I think this is definitely something worth looking into. I've passed on all the feedback to our team so they can investigate. As a friendly reminder, remember that accuracy depends on many factors.
Here's a couple things being worked on:
For 'Auto' setting being too dim, you can switch to 'Normal' as a workaround in the meantime. Please note switching to 'Normal' will have a slight impact on battery life.
I'll provide updates when I can. Thanks everyone. 🙂
Update 4/27/16:
The firmware update should now be available to everyone. Update your Blaze and let me know how it goes! You can read the release notes for version 17.8.200.3 in the lead post or check them out on our help site. 🙂
Update 4/23/16:
Sorry for the wait, here's the release notes!
"The Simplified Chinese, Japanese, and Korean languages are now available on Blaze. Note that Blaze is only available for pre-order from fitbit.com in China, Japan, and Korea.
This release also resolves a couple issues:
You can find these release notes for this update (17.8.200.3) on our help site.
4/21/16:
Hey everybody,
Some of you may have noticed there's a new firmware update for Blaze! We just started pushing this update out yesterday, and just like any other update, we'll be rolling it out in waves. This update focuses on a few bug fixes. Release notes will be posted here soon.
Thanks!
05-04-2016 05:02
05-04-2016 05:02
@mrskdhill wrote:
Sorry, it is not possible to revert. Have you tried restarting the Blaze?
Yup, I've restarting and resetting it at least four times. I've deleted, downloaded and re-installed the app a few times. Speaking to fitbit suppot doesn't help, they just send me a bunch of online articles which i have already read and done. They just don't understand it's not me, it's this new firmware update that is causing the issue. I haven't any issues with my fitbit until this update. I've never seen an update that goes worse than before, more like a downgrade.
05-04-2016 05:05
05-04-2016 05:05
repeatedly. Often not by choice since the battery won't make it anywhere near a full day with any activity. 😞
05-04-2016 06:26
05-04-2016 06:26
05-04-2016 06:27
05-04-2016 06:27
05-04-2016 06:28
05-04-2016 06:28
05-04-2016 06:28
05-04-2016 06:28
05-04-2016 06:47
05-04-2016 06:47
05-04-2016 06:52
05-04-2016 06:52
05-04-2016 07:12
05-04-2016 07:12
People having trouble after the update - have you tried removing the blaze from your account and adding it again?
If nothing is working, fitbit should send you a new tracker. I know everyone isn't in the US, but that's generally their go to if you call them.
05-04-2016 17:44
05-04-2016 17:44
theres a problem after this update sir... My blaze is not connecting to phone and while i am travelling on my motor bike blaze is recognising them as steps ....please do fix this ! Thanks
05-05-2016 01:53 - edited 05-05-2016 11:53
05-05-2016 01:53 - edited 05-05-2016 11:53
Fitbit is replacing mine - very good service.
05-05-2016 10:56
05-05-2016 10:56
05-05-2016 11:40 - edited 05-05-2016 11:42
05-05-2016 11:40 - edited 05-05-2016 11:42
Hi @CMichelle,
I have just purchased a Blaze & accuracy seems OK so far, will test out 2night against Endomondo to see how the 2 rally together. Will be interesting to hear back on how your replacement fairs or whether their could be a software flaw with the blaze. Look 4wards to hearing your replacement report.
Cheers 🙂
05-05-2016 13:19
05-05-2016 13:19
05-05-2016 13:42
05-05-2016 13:42
@DSmithSanDiego - That is how it was designed to be.
Kelly | Oklahoma
Alta HR, Blaze, Flex 2, Charge 2, Charge, and Aria * IPhone 7+
05-05-2016 13:59
05-05-2016 13:59
05-05-2016 15:19
05-05-2016 15:19
Hi, @cyclejuice and @picasso66! I wish I could report my replacement Blaze is working better but unfortunately, it isn't. I honestly feel like there is a glitch with the Blaze screen that causes it to miss steps the faster you walk or swing your arms. Most of the time, just around the house or office, it is pretty accurate, though I have plenty of examples I could give when it isn't. For instance - the 250 steps per hour goals - I have a path marked around the office to the restroom and to get a glass of water and is just over 250 steps so each time I take it, I should reach that hour goal, right? MOST of the time I do but every once in a while, it misses the steps, for some reason.
Then, I did a test with the Mobile Run in the Fitbit app Tuesday night and while the GPS kept the distance accurate, my steps from the Blaze were WAY off. I went 3.12 miles and it said I only took about 5,000 steps. For me, it should be more like 6,300.
So, once again, I am taxed with trying to decide to return this or not. I am so sick of wondering - is it going to count my steps right this time? If I can ever find the time, I think I will probably call Fitbit and downgrade to the Charge HR. I hate having to set up and learn a whole new tracker but am hopeful since it's been out longer, it's more accurate. I've only been holding back because I love getting notifications on my Blaze. I can say I have NEVER had any problems with firmware updates (each took only about 15 minutes), my notifications always work, I don't have any problems synching to my phone, it tracks my heart rate well on all exercises and always logs my sleep correctly.
I would love to hear from any Blaze users out there who have NOT any issues with it under counting your steps? Does this device really work well for some people? I know we all come to these message boards to find help for our issues but maybe we aren't all having the SAME issues. I keep hoping one day, I will wake up and this thing will just work but I don't think it's going to happen. I'm doing another walk tonight and I'm going to let the Auto Recognize Exercise function track it and see what it comes up with compared to Endomondo. If the steps are off again, I think I just need to suck it up, pick up the phone and dump this piece of junk. It's become so much more trouble than it's worth. So disappointed!
05-05-2016 16:10
05-05-2016 16:10
I'm experiencing the same problem.
05-05-2016 16:16
05-05-2016 16:16
I keep a close eye on these forums. As an early adopter here in Australia of the Blaze and previous owner of 2 other Fitbit models. I have to say I have had NONE of the issues that have been described in any of these posts.
While I understand that there will always be teething problems and issues that need firmware updates etc, I seem to see a lot of stuff that can be addressed by either reading the manual of doing research prior to purchase.
As for the step count I cant say i have noticed a big difference from my old Charge or comparing it to my wifes Charge HR. I think no matter how accurate a device is there are always mitigating factors..ie. stride lenght etc. From my point of view if it was undercounting steps I would look at it as a way for me do do more 😉 to make up the difference :))
05-05-2016 16:22
05-05-2016 16:22
I have not experienced any problems with my Blaze. It is spot on (within a step or so). I have watched it as I have walked and it counts accurately. My Alta did not. I could not even watch the Alta as I walked, as there was a delay in the Alta. It always had to do a catch-up. I think this is where the problem lies with the inaccurate count. I hope you can figure it out with the Blaze.