Blaze Firmware Update - 17.8.104.1 [Closed]

[AndrewFitbit]

Update 4/12/16:

Hey all,

As of yesterday, the firmware update for Blaze should be available to everyone. As is common with initial updates, this version focuses on stability improvements and bug fixes. We're looking forward to delivering feature improvements with future updates so stay tuned! 

Update 4/5/16:

I've addressed some things I've seen come up in this thread in a post I made here. Check it out! 

Hey! While it is April 1st, the Blaze firmware update to version 17.8.104.1 is no joke. As usual, we're rolling out the update in waves, and we hope to have everyone updated soon.

This release includes the following:

• General improvements
• Minor bug fixes

Any questions, just let us know. 

[Yorkie10]

Thanks. What you said is make sense. I guess the Blaze makes an estimation on daily calories base on your weight and height.

[Soldiergirl]

Only tracked via the dashboard. No notifications for it.

[hawkyou]

If the Blaze did half of what the Apple Watch does you would have to charge it twice a day.

[mgeorgalas]

Nope, my stride is set on there. My mileage is correct if I sync with my One, but if I sync with my Blaze it is way, way off. It takes 10,439 steps to get 5 miles on my One but it takes 12,500 to get it on my Blaze. Obviously the Blaze is bit using my stride length to calculate mileage and it seems like it is a very common problem on here.

[RealBlaze]

I have had my Blaze now for a month.  I found it to be pretty accurate.  Unlike many people have said.  The distance while walking was pretty close.  I walk a mile Fitness course and it shows up the same each time I walk the mile about 1.09 Miles.  So that is close enough and perhaps its where I turn and stuff.  The steps too are consistant at about 2200 to 2400 Steps for each mile I do.  Again it could be the turns I take and perhaps short or long stepping.  I have stepped out parts on the course and each time those are within a 1% Error Range.

Where I find the Blaze fails and I know why is the Ellipical machine. Unlike walking or running. Where the Blaze counts 2 steps per stride (For Me I swing my left arm when my right foot steps)  But the Blaze Recognizes the Elliptical movement and auto puts "Elliptical".  That is not the problem.  When you have it on your arm it only counts by "1's".

We have a Nordictrack SE9i.  It's brand new replacing out Nordictrack 990 Strider.  If I run a 2.43 Mile course on the SE9i the fitbit only logs about 1.10 Miles.  I even faked out the Blaze by tying (I had to use Paracord to get it around my ankle) the Blaze to my ankle and stepping hard down onto the foot pedal of the elliptical.  This helped and made it more accurate on distance.  It was still off at 1.91 Miles per a 2.43 Mile run on the Elliptical.

I am pretty sure that the Elliptical knows that distance since the strides are always the same and it knows how many strides it takes.  Also it takes me about 19 minutes to do this (At a resistance of around 5 to 8 so it's not like normal running)  The Blaze is totally off on Ellipticals.

[ThePreacher]

---

@Yorkie10 wrote:

Thanks. What you said is make sense. I guess the Blaze makes an estimation on daily calories base on your weight and height.

---

It does indeed do that and if you are wearing it then it uses your activity and heart rate to give an even more accurate calculation

[TammyLounsberry]

When will the new version be available for me to download? I currently have 17.8.102.7

[SunsetRunner]

@TammyLounsberry some time in the coming weeks

[mgeorgalas]

I find that really unacceptable.  By then there should be several more firmware updates, if not then there is a serious problem with the lack of fixing these issues.

[marcusb84]

Really? This is typical for most devices these days. Slow roll outs allow them to address issues the update process may cause.

[SunsetRunner]

It seems there are more than a few people who have absolutely no idea about software/bug-fix roll out.

[mgeorgalas]

I know exactly how it is rolled out.  But it shouldn't take weeks when you have a few thousand people with a device that has severe issues.  Imagine if the same process was used to update Windows or your phone.  My One says I have 3,075 steps so far today, my Blaze says I have 2,080.  That's about a 33% error rate.  The Blaze cannot correctly calculate my mileage, it is constantly off buy 20% because it is unable to use the stride length in my account settings.  Fixing these issues for a few thousand people a day is not acceptable when you release your new major product.

What happens if the new firmware does not fix these issues and then they release another, I wait a "few" more weeks until I get that update, meanwhile I go 6 or more weeks with a non-functioning device?  I guess you are correct, it seems there are more than a few people who have absolutely no idea bout how software/bug-fix roll out.

[marcusb84]

"But it shouldn't take weeks when you have a few thousand people with a device that has severe issues."

I am pretty sure they said they sold over a million Blazes. And what severe issues? Mine has worked just fine 99% of the time since I got it a few days after launch.

The same proces is used to update my phone, and I have a Nexus 6P on Google Fi. I still wait in line after the update is released.

[SunsetRunner]

Speaking as someone who has a Windows phone that has had bugs for more than 5 months, I'd say Fitbit's "few weeks" is well on schedule. 🙂

[MikeS1971]

@mgerogales I don't think your issue is with firmware, but with the tracker itself. My Blaze and Charge HR are pretty accurate with the amount of steps per mile they count. Especially after I calculated my average stride over a mile and added that to my FitBit account. I verified with other GPS trackers and pedometers afterwards and all is good. Before I did all that, my steps vs miles were way off.

[mgeorgalas]

@MikeS1971that is the thing, my One is fine but my Blaze is off.  I know my stride is correct.  Do you know what firmware you are running?  I am still on 17.8.102.7

[MikeS1971]

@mgerogales, I'm on the latest firmware. I haven't noticed any difference with the functionality of the Blaze. Everything works the same now as it did before.

[mgeorgalas]

I am going to try removing both fitbits from my account and readding them, blaze first to see if that changes anything.

[Stretch74]

I am new to this discussion and found it while I was searching for all things Blaze.  I love my Blaze!  I checked the version number on my device and says it is 17.8.102.7.  So it looks like I have missed a few firmware updates?  I just checked for a device update on the fibit site and it said my device was up-to-date.  Am I  missing something?

[Rich_Laue]

Hello there.
@mgeorgalas read the top post, This firmware is mostly about stability.
@Stretch74 nope you haven't missed it, as usual this firmware is rolled out, so the servers are not overloaded. In still working for mine to be available.