Is anything working properly on Blaze?

[Mczech]

Sleep doesn't work properly:  Most days is says I am fully awake 1-2 hours before  I know that I was.  

does not record miles: 15000 steps is not equal to  .75 miles.  

about 90% of the time I don't get notifications.  I will for a day if I go and turn off notifications and then turn them back on.

The ONLY thing is does is record steps.    I am very disappointed.   

I have posted in a few forums in here and customer service wanted to replace my blaze.  As I see they have done for many.  This does not fix the problem 😞    

I see that there are many people out there with all the same problems I am having.  I had high hopes that an up date would fix it, one ran the other day......no such luck.    I just wish they would fix it. Obviously its a software problem 😞 

[MarkMM]

Sorry, but if a replacement showed .75 miles for 15,000 steps as well, I'd say it's somehow user error. 😉

[Mczech]

Your funny.....there was no replacement and there is no possible user error.  It simply cant/wont/does not compute miles. Only steps.  Read the forums..... I am not alone.  The GPS feature does not work properly.

[MarkMM]

You said Fitbit wanted to replace your Blaze. But you seem convinced it's a software issue. Did you have them send a replacement? 15,000 steps counting as less than a mile walked is about the worse discrepancy I've seen so far. Not that I've read every topic, but that's pretty bad. 

[Rich_Laue]

Without GPs the Blaze indeed will compute miles. It does this by multiplying the steps by the stride setting. 

Have you checked your settings for height weight age and gender? Also make sure the stride is at 0 or shows a realistic number.

Just a thought, try creating a manual walk, pick a time and put in 1 mile for distance. Now lets look at the event and see how many steos it gave you for the mile. This would be calculated by the set stride.

As for notifications as long as they are turned on in the tracker. Swipe down on the clock, and thw Blaze has been restarted, the problem is in the phone.

Make sure the app is up to date.

Lets start an investigation.

[Mczech]

I did not have them send a replacement.  I went down this road with stupid issues and 3 replacements on my flex....different reasons of course.   There has to be a fix.   I had it a day it worked just fine, then a software update ran and it has not worked right since.  

[Mczech]

I have tried everything listed.  If it is my phone app.... then that means the Windows 10 app is bad too.  Neither one computes it correctly.

[macgurlnet]

I saw in a post a little further down that notifications for Windows 10 devices isn't supported yet. If you go to the link below:

https://www.fitbit.com/devices

And select your phone, what options do you see? If Calls/Texts doesn't come up, that means compatibility isn't guaranteed yet.

You might also be one of those people that's best off calculating their stride length, rather than relying on the estimate the Blaze gives you. Stride length plays a part in calculating distance.

See here for how to calculate stride: https://help.fitbit.com/articles/en_US/Help_article/1135

One other thought - do you track a lot of exercise with the connected GPS? If the GPS is getting enabled, that will be used to calculate distance. So, if you're walking on a treadmill or something similar with little movement, that could explain the miles being way off.

~Lyssa

[MarkMM]

Interesting point about GPS steps, Lyssa.

I don't think Windows phone app is the issue. You should be able to turn your phone completely off and the watch still tracks distance. 

[macgurlnet]

---

@MarkMM wrote:

Interesting point about GPS steps, Lyssa.

I don't think Windows phone app is the issue. You should be able to turn your phone completely off and the watch still tracks distance. 

---

If it's working like it's supposed to, I think so too. I don't think the app is the source of the issue - or, at least, not the only source.

~Lyssa