Fitbit Blaze...Updated Firmware...showing a ton of steps after???

[vaporhockey83]

Hello,

I recently updated the firmware on my Fitbit. All of the information on stride is correct. After the update, I had over 7,000 steps on my tracker and dashboard. Oddly enough, when I go to the ticker with the hour ranges, it shows the correct steps. A lot fewer. All of this is the same with miles, the calorie burn, etc. Is there a fix for this or is my tracker trying to make up for time that I was walking around while updating? Just throwing some possibilities out for this. Anyone else having this issue or have an answer for it? I'm generally on top of what's going on with my Fitbit, but this has me clueless. Thanks.

Patrick

Also, FYI, running: Firmware Version: 17.8.301.7

[vaporhockey83]

If this isn't strange enough, I just added up the hourly ticker. It's 1754. My total on my tracker/dashboard is 7540. Strange that the "754" part is correct. Something seems very wrong here.

[Rich_Laue]

What is the "ticker", and what steps was done to manually add steps to this ticker. I know manual are able to be added to the dashbiard. 

I'm totally lost. 

[vaporhockey83]

Sorry, I should refer to them as they are. The "tiles" on the dashboard, both on my phone/website, show varying data. One tile that shows today's overview (steps, miles, calories, active, floors) combined versus the other tile that shows hourly data. The hourly data you have to select a tab to see each of the above. My hourly data is absolutely correct. I've been asleep and then walked into my sedentary job. The other tile, my tracker, and phone dashboard all show 7,540 steps taken. 1.93 miles walked. I have most definitely not taken that many steps or walked that length. The floors show 7 versus the hourly's figure of 2 (2 is correct). Sleep shows correct info. I have not added any manual steps at all. The hourly tile appears spot on where everything else is definitely incorrect. 

[Rich_Laue]

Could it be that the tracker did not reset at midnight? This could happen if the timezone switched before midnight and the clock jumped from say 11:20 to 12:20, the tracker never saw the 11:59>12:00 so it did not reset data.