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!
08-30-2016 13:46
08-30-2016 13:46
@meresydotes wrote:
And have you noticed that fitbit moderators are not responding to my questions about the next update containing actual fixes, rather than just bells and whistles?
I honestly don't think they know. I also think that only a few of the moderators that post are actual real people. If you look at the responces for a select few "moderators" they look to be robo replies. They don't actually answer a question, it's just a cut/paste of the same response.
Even though I don't use my Blaze anymore and have moved to a different manufactuer, I do hope the update fixes the current issues. I never really cared about additional watch faces or other features being added. If it does get fixed, I can update it and sell it. I've already sold all my accessories I purchased (bands, frames, chargers). I just didnt feel right selling the Blaze itself with all its issues and making it someone elses problem. That wouldn't be right.
08-30-2016 13:52
08-30-2016 13:52
@MikeS1971 Well (presuming this doesn't get redacted), I've had Andrew helpfully redact comments he didn't like before and send me a lovely email about it, so I think he's real, at least.
Contrary to what is rational, I LOVE my Blaze. It's the fitbit I've been waiting for. I also have a lot of experience troubleshooting, so I had the patience and the knowledge and the motivation to work at it until I found a way to get it working for me.
08-30-2016 13:58
08-30-2016 13:58
08-30-2016 14:02
08-30-2016 14:02
@Txtea11 Click on the gear icon - then go to settings then Subsciptions & Notifications.
There are more setting for this forum and how you get notified. I bet you'll find you still have some subscribed threads.
Kelly | Oklahoma
Alta HR, Blaze, Flex 2, Charge 2, Charge, and Aria * IPhone 7+
08-30-2016 14:14
08-30-2016 14:14
08-30-2016 14:19
08-30-2016 14:19
Glad to hear you were able to get it figured out @Txtea11!
Enjoy the day!
Kelly | Oklahoma
Alta HR, Blaze, Flex 2, Charge 2, Charge, and Aria * IPhone 7+
08-30-2016 14:49
08-30-2016 14:49
@meresydotes Posts are only removed or edited if they're in violation of our Community Guidelines.
For anyone posting about accuracy, how about we re-visit this conversation after the next update? I don't know the details of the changes other than the new features listed, but I'd be more than happy to collect feedback as soon as the new update is available.
I've tried collecting data a few times before in this thread (as well as in other threads), and I've even reached out to users via PM to try and collect data to bring to the team. We did investigate, and there was a very small percentage of users that had discrepancies. I personally haven't had any accuracy issues with my Blaze, but I can only imagine it's a frustrating experience.
If anyone continues to have accuracy issues after the next update, I would encourage you to create a new thread detailing your experience.
08-30-2016 15:16
08-30-2016 15:16
As always, thanks @AndrewFitbit for dropping in and commenting.
Aria, Fitbit MobileTrack on iOS. Previous: Flex, Force, Surge, Blaze
08-30-2016 16:34
08-30-2016 16:34
08-30-2016 17:27 - edited 08-30-2016 17:33
08-30-2016 17:27 - edited 08-30-2016 17:33
I suggest we all go for a walk, run, lift some weights and appreciate things it does do and wait patiently for updates. If not go get a rubbish apple watch and complain on their forum.
Looking forward to reminders to move happening. Otherwise loving my blaze and thankfully never had any problems with it. Would just love to see more clock faces and a better barcode scanner for food logging.
08-30-2016 17:41
08-30-2016 17:41
@AndrewFitbit I've been offering my experiences on this thread and others for months. So have many other people. It seems pretty disingenuous of you to make it seem like you've been desperately looking for volunteers when you have a large group of people right here desperate to volunteer.
I even have a drawer full of previous fitbit models (original, ultra, flex, force, charge, charge hr) I would be happy to charge up and sync to a different account/ email address for comparison. Just say the word. Presuming I can remember how to swing my arms while walking again, since I've trained myself so well.
08-30-2016 20:37
08-30-2016 20:37
@AndrewFitbit wrote:@meresydotes Posts are only removed or edited if they're in violation of our Community Guidelines.
For anyone posting about accuracy, how about we re-visit this conversation after the next update? I don't know the details of the changes other than the new features listed, but I'd be more than happy to collect feedback as soon as the new update is available.
I've tried collecting data a few times before in this thread (as well as in other threads), and I've even reached out to users via PM to try and collect data to bring to the team. We did investigate, and there was a very small percentage of users that had discrepancies. I personally haven't had any accuracy issues with my Blaze, but I can only imagine it's a frustrating experience.
If anyone continues to have accuracy issues after the next update, I would encourage you to create a new thread detailing your experience.
We were working with FitBit tech support to resolve the issues with step accuracy. We even had a talk with some represenatives that visited a local store. FitBit actually has offices not far from me. At one point it was myself and six of my friends/co-workers trying to resolve these issues. All of us individually did tracked workouts that were replicated exactly but had astronomically different outcomes. Not compared to each other, but to ourselves. Support monitored these tests. Only solution support had was the standard answers everyone sees here. Which didnt change anything. Some of us received replacements from FitBit, some of us received brand new units locally to test. The results didn't change. All of us have stopped using our Blazes. Most have returned them. And out of all of us, I'm the only one that comes to these forums. I actually don't know anyone who ownes a FitBit of any model that comes here. I've unsubscribed from most topics, but keep coming to this one and similar topics to see if a fix ever happens and to provide my experiences with the Blaze. Its only fair that potiental customers researching the Blaze see both sides to make an educated purchasing decision.
Prior to the April update that started the current issues, my Blaze was actually accurate to my liking. The two things I honestly didnt care for were the charging design (solved by the aftermarket) and after some time with it, the frame (also solved by the aftermarket). A couple small tweaks to the interface would of been nice, but at least it worked. And if FitBit would of acknowledged the issues early on, I'm positive I'd still be using mine.
08-31-2016 00:47
08-31-2016 00:47
@AndrewFitbit wrote:@meresydotes Posts are only removed or edited if they're in violation of our Community Guidelines.
Well, someone just deleted about four or five posts from this thread where we point out (with evidence) that, on the FitBit Blaze page of the site you are advertising features that do not, as yet, exist.
So, posts are removed if they're in violation of community guidelines or if they could potentially affect sales.
08-31-2016 08:41
08-31-2016 08:41
I was just coming on here to discuss the fact that my Blaze step count seems extremely low.... It looks like this may be fixed with the newest update? My ChargeHR is a better guage, but I don't want to wear it every day. Let's fix the products we have before rolling out new ones, is an idea.
09-01-2016 07:22
09-01-2016 07:22
Thanks for stopping by @bbarrera! @chrisc76 we can not provide you an estimated date for the new firmware update release but it's coming soon! Stay tuned @Laurenypop thanks for sharing feedback! @meresydotes thanks for sharing your experience with Fitbit trackers! @MikeS1971 keep an eye for the next update! @Rylan as previously mentioned by @AndrewFitbit Posts are only removed or edited if they're in violation of our Community Guidelines. @rhonderoo thanks for participating on this thread, keen an eye on it for any update!
It is health that is real wealth and not pieces of silver and gold! Share your story!
09-01-2016 08:35
09-01-2016 08:35
"Similar to what I said here, there is a new firmware update coming out, but it's not coming out this week. We still don't have an exact date, but it is coming very soon so just be on the lookout for when I post new content."
Can you verify that this new Update will fix the Steps/Distance accuracy problems ?
09-01-2016 08:40
09-01-2016 08:40
@Corvettekid See the post I have here.
Short version is: I don't know, but I'd like to monitor this closely once people start updating to the newest firmware.
09-01-2016 08:42
09-01-2016 08:42
@Corvettekid Unfortunately, they cannot or will not confirm that. I've asked several times. They say they have no access to that information. I guess they're also not allowed to ask those who do.
09-01-2016 08:48 - edited 09-01-2016 08:51
09-01-2016 08:48 - edited 09-01-2016 08:51
"If anyone continues to have accuracy issues after the next update, I would encourage you to create a new thread detailing your experience."
Andrew, as soon as the update hits I will be doing a 1/4 mile (0.25 miles) track test at my local high school. Last time I did it, I got 0.18 miles each time. 72% accuracy. About what I found in walking in my neighborhood.
I'd be pleased if it is at 90% accuracy, not looking for 97% or 98% accuracy.
09-01-2016 08:54
09-01-2016 08:54
Its highly doubtful that any of the moderators have inside information about anything technical about any of FitBits products. They're here to moderate the forums and make sure guidelines are followed and to point people with issues to published troubleshooting tips.
I'd be very, very suprised if they even work for FitBit.