09-19-2016 09:59
09-19-2016 09:59
09-19-2016 10:59 - edited 09-19-2016 11:03
09-19-2016 10:59 - edited 09-19-2016 11:03
If it was a known 6 miles, divide the number of steps into 380,160 and plug the resulting value into your walking stride length here under body info. (calculated result is most likely between 2ft 1in and 2ft 11in)
Tomorrow see if that 6 miles is more accurate reported, if it isn't double check the absolutely, positively reported measurement of the 6 miles 😉 then contact customer support.
WmChapman | TX
Ionic, Versa, Blaze, Surge, Charge 2, 3 SE, AltaHR, Flex2, Ace, Aria, iPhoneXR "Every fitbit counts"
Be sure to visit Fitbit help if more help is needed.
09-19-2016 11:09
09-19-2016 11:09
09-19-2016 11:12 - edited 09-19-2016 11:19
09-19-2016 11:12 - edited 09-19-2016 11:19
how many steps for the "6 miles" (380,160 inches) ?
I just walked 1.53 miles (1.53x 63,360 inches) = 96941 inches/3114 steps = 2 ft 7 in
WmChapman | TX
Ionic, Versa, Blaze, Surge, Charge 2, 3 SE, AltaHR, Flex2, Ace, Aria, iPhoneXR "Every fitbit counts"
Be sure to visit Fitbit help if more help is needed.
09-19-2016 11:19
09-19-2016 11:19
09-19-2016 11:20 - edited 09-19-2016 11:21
09-19-2016 11:20 - edited 09-19-2016 11:21
yep, about 3 miles+ = about a 5k
Set your stride for 2ft 6 inch and see what the result is tomorrow, I'm pretty confident if you did it in 7000 steps it isn't 6 miles, maybe it takes two laps.
WmChapman | TX
Ionic, Versa, Blaze, Surge, Charge 2, 3 SE, AltaHR, Flex2, Ace, Aria, iPhoneXR "Every fitbit counts"
Be sure to visit Fitbit help if more help is needed.
09-19-2016 11:22
09-19-2016 11:22
09-19-2016 11:24
09-19-2016 11:24
09-19-2016 11:29
09-19-2016 11:29
Your steps are half as you say. Takes me greater than 10k steps to get to my 5 mile a day goal.
Try restarting your blaze after you have made sure a "human" value is in your stride profile.
Press and hold the Back and Select buttons (left and bottom right) until you see the Fitbit logo on the screen. This should take less than 10 seconds. Let go of the buttons.
WmChapman | TX
Ionic, Versa, Blaze, Surge, Charge 2, 3 SE, AltaHR, Flex2, Ace, Aria, iPhoneXR "Every fitbit counts"
Be sure to visit Fitbit help if more help is needed.
09-19-2016 11:35
09-19-2016 11:35
09-19-2016 11:37
09-19-2016 11:37
09-19-2016 11:40 - edited 09-19-2016 11:42
09-19-2016 11:40 - edited 09-19-2016 11:42
Exactly Steve.
doublecheck 2 ft 4 in in the walking box.
hit the coral colored "save" button, sync to your mobile dashboard. See how many total steps are on your blaze, walk exactly 100 steps (without turning) and check the new total for me...
WmChapman | TX
Ionic, Versa, Blaze, Surge, Charge 2, 3 SE, AltaHR, Flex2, Ace, Aria, iPhoneXR "Every fitbit counts"
Be sure to visit Fitbit help if more help is needed.
09-19-2016 11:57
09-19-2016 11:57
@SteveT101 wrote:
Just went on a 6 mile walk (known distance) Fitbit blaze only counted 7000 steps and 5.5 km. This discrepancy started a couple of days ago with steps and distance. I have tried restarting my Fitbit with no luck.
@SteveT101 walking a 6.6 mile trail and Blaze is only recording 7000 steps? Something really wrong and its not stride length.
A few comments/questions:
- try restarting Blaze 3 times, one of the community moderators has made that point repeatedly so I'd give that a try
- are you entering walk mode, or letting Blaze auto-detect activity?
- are you using Connected GPS?
- are you using walking poles?
- are you moving arms vigorously?
- using iPhone and Connected GPS? Did you recently upgrade to iOS10?
Aria, Fitbit MobileTrack on iOS. Previous: Flex, Force, Surge, Blaze
09-19-2016 11:57
09-19-2016 11:57
09-19-2016 12:06
09-19-2016 12:06
1 inch change in stride = 4 steps per 100
so you'd have to reduce to less than a foot stride length to get an accurate step count, if your arms swing freely then something is wrong with the axis sensors in your Blaze, contact customer support and let them know your Blaze's step counting has dampened 40% and you have tried multiple restarts.
WmChapman | TX
Ionic, Versa, Blaze, Surge, Charge 2, 3 SE, AltaHR, Flex2, Ace, Aria, iPhoneXR "Every fitbit counts"
Be sure to visit Fitbit help if more help is needed.
09-19-2016 12:06
09-19-2016 12:06
09-19-2016 12:11 - edited 09-19-2016 12:12
09-19-2016 12:11 - edited 09-19-2016 12:12
It wouldn't, walking pole or hand in pocket would (slightly, but not 40% 😉
WmChapman | TX
Ionic, Versa, Blaze, Surge, Charge 2, 3 SE, AltaHR, Flex2, Ace, Aria, iPhoneXR "Every fitbit counts"
Be sure to visit Fitbit help if more help is needed.
09-19-2016 12:22
09-19-2016 12:22
@wmchapman wrote:if your arms swing freely then something is wrong with the axis sensors in your Blaze, contact customer support
Agreed. Sounds like a fundamental problem with your Blaze, get support to swap it.
Aria, Fitbit MobileTrack on iOS. Previous: Flex, Force, Surge, Blaze
09-19-2016 12:39
09-19-2016 12:39
09-19-2016 13:04
09-19-2016 13:04
@SteveT101 Fitbit MobileTrack also works great as step tracker if you carry phone in pocket. I've been using it since my Force got recalled, then got a Surge, and then MobileTrack again when I got an Apple Watch. Actually I prefer "MobileTrack in pocket" to wrist tracking because I get more accuate step counts when pushing a shopping cart around Costco every weekend. Plus during Step Challenges I get "step credit" while cycling - not as much as walking the same amount of time, but I'm getting a moderate-to-vigorous cardio workout which is more important to me as I follow the CDC recommendations and not the 10,000 step myth (which evolved from a Japanese pedometer company).
Aria, Fitbit MobileTrack on iOS. Previous: Flex, Force, Surge, Blaze