Fitbit Blaze losing steps

[SherrilAdian]

My Blaze is losing steps. It seems to be having an issue last 9000 steps. Everytime I sync I lose about 400 or so steps.

[SilviaFitbit]

@SherrilAdian Welcome to the Community! It sounds like you're using two devices in your account and that's the reason why you're losing steps when you sync your tracker. You may want to learn more about having two devices set in your Dashboard by checking Can I use more than one Fitbit tracker with the same account? . 

Hope this helps. Let me know how it goes. 

[MelissaMc]

I had the same problem yesterday.  I received my new Blaze. I first removed my Charge HR from my account, setup my Blaze and was approaching 10,000 steps when is abruptly dropped to 5,200 and then to 3,900 for the day.  I was prompted to reset up my Blaze several times earlier in the day, but thought it was working correctly at the point it started losing steps. Support told me to turn it off and back on several times. I did that today but am worried I can't trust the Blaze.

[Rich_Laue]

@MelissaMc are you only looking at the app, or have you also looked at the dashboard on fitbit.com which seems to need to update before it displays correctly. 

I find the app sometimes acts flaky, the web seems to show correct data more often. 

[MelissaMc]

Hi, I did both. The tracker itself lost the steps. I switched from the
Charge HR at noon and set up the Blaze with no lag. There is no data from
12:25 to 5:10 showing as of today. However, the Blaze showed the higher
amount of steps and started dropping chunks of steps after 6 pm yesterday.
I'm going to manually log the steps if I can and just watch it today.
Thanks!

[Twitchy]

I have used the Charge HR since it came out. Having measured my stride on a 400 meter track I know exactly what my stride is based on 10 different walks with at least 4 rounds per walk.

That has been input in my program under Account>Advanced Setting> Stride Length. The Set Automatically slider is set to off.

I have noticed that the Blaze appears to ignore the slider and calculates your stride as you walk throughout the day. In essence, it's ignoring the flag set by turning off Set Automatically even though thats not supposed to work unless it's teamed up with a GPS. 

So, I loose steps switching from Blase to Charge HR and back.

[Rich_Laue]

@Twitchy the stride would affect distance and has no affect on step count.. 

Fitbit normally uses two stars to figure out the distance,, the step count and the stride.. Changing either one will affect my the distance shown but the stride can not affect the step count. 

Steps are one thing that all fitbit tracker a actually counter, the other thing is time.. Fitbit uses these twos things and your stride when calculating every other stat. 

For me to get the distance recorded in the Blaze i had to manually set the stride. 

[AlejandraFitbit]

Welcome to the Community @MelissaMc, @Twitchy it's great to see you around and @Rich_Laue thanks for stopping by and the recommendations.  @Twitchy As you were able to see, now the Blaze records your stride length automatically, I recommend turning this feature on by following the steps you already mentioned. Now @MelissaMc, I would like to know if your tracker keeps taking your steps away? If it does, I recommend restarting the tracker and test it, if this procedure doesn't work, feel free to contact our support team, since they have the proper tools to see the information that it is recording.

Catch you later. 

[tennesseeds]

Mine has lost thousands of steps.  

[tennesseeds]

Sorry, I should have been more clear - my fitbit blaze loses steps often.  I am not sure what causes it.  It will be fine and then act like it just forgot our last sync that it just did moments before but will deduct sometimes thousands of steps and resync that erroneous data to the app.  Or visa versa - not sure which one is flaking out.  The good thing is at least the workout challenges will retain their accurate step count - so, it doesn't affect the challenges.  Seems like a different data bank.  

[Rich_Laue]

Is this loss, during a sync?

[tennesseeds]

Yes, I think it usually happens at a sync point.