Blaze Accuracy - Connected UPS vs Walkmeter vs Health

[SunsetRunner]

Similar to others, I find that when I use conected GPS, my step count decreases when walking the same route. I walk every morning around my block, it's approximately .53 miles.  Without using connected GPS, I typically get between 1200 and 1300 steps. If I measure the same course with the Health app and/or use Walkmeter, these both typically show between 1200 and 1400 steps.  My Blaze, if I use connected GPS almost always shows 950 steps. Same block, same distance yet the results are consistiently not the same.

Blaze Not Connected:  averages around 1300 steps

Blase Connected: averages around 950 steps

Health: averages around 1300 steps

Walkmeter: averages around 1300 steps.

I'm puzzled that when walking the same course, I get two different answers from my Fitbit.  I do adjust my stride length based on my Walkmeter average about once a month, but over time, my length is beginning to average about the same distance, so stride length has remained fixed throughout my above testing.  Sadly, I'll probably use the connected GPS less given that inconsistency and apparent accuracy issue.

Next up, I'm going to keep my phone on me all day, and compare my Fitbit to Health at the end of the day, but based on the above, as long as I don't use connected GPS, the numbers will probably be very similar.

[bbarrera]

Step counting is at the core of any Fitbit tracker, and not influenced by your stride setting.

Disappointing, and as you said we've seen others reporting step counting issues.

As an experiment, try putting Blaze into Run exercise mode (instead of Walk) when using Connected GPS. Then go on your walk and compare results. 

[bbarrera]

@SunsetRunner did you have a chance to try using "Run" exercise mode while walking? I know it sounds like a strange request, and although unlikely it will fix your step counting issues, Fitbit has confirmed issues with using Connected GPS for mileage while in walk or hike modes (this article is about Charge 2, however there have been user reports for Blaze on this forum since April). 

You should contact support and have them exchange your Blaze for a new one. It could be a problem with your particular device.

[robcassely]

I have noticed repeated discrepancies between the Blaze "connected GPS" distance and Walkmeter (which I have verified independently through distance measuring websites). The Blaze is both different and inconsistent e.g. when doing the same 5.6km walk to work, the Blaze gives anything from 5.12km to 5.63km. Not too impressed as the same GPS used for both (iPhone 5C).

[bbarrera]

@robcassely Sounds like similar accuracy issues on the Charge 2 - this review published today has details. Your phone is fine, because Walkmeter is accurate. So its clearly a Fitbit issue.

Not the same as step counting accuracy issues @SunsetRunner is having, but still troubling.

[SunsetRunner]

I stopped worrying over this inconsistency, but just for kicks, I just completed two walks around my test block.  Again, the connected GPS on my Blaze is nothing short of disappointing.  First walk, not using connected GPS 1300 steps, second walk with connected (worthless) GPS 800 steps.  Total distance for my .53 mile circuit, .44 with the connected GPS. Again, nothing short of disappointing.   

Given my current new issues with Blaze and the simple fact that the 'feature' of the Blaze, connected GPS is worthless, I guess I'm going to return to the market and find something that meets my needs.  I love the app and love the motivation that Fitbit has offered, but now that the app isn't updating consistently from my Blaze and that connected GPS is a failure, I'm going to start shopping anew for something that works.  

A very disappointed Blaze owner.