Bug: Inaccurate step count when switching time zones causes date change

[wyattstorch42]

I'm not sure if it's best to report this in the iOS forum or the forum for the Fitbit One model. However, I'm pretty confident I know what happened.

I walked about 12,000 steps yesterday. Before boarding a plane, I synced my steps by opening the Fitbit app on my iPhone 6 running iOS 10 with the latest version of Fitbit. Then I placed my phone in airplane mode for the duration of the flight.

The flight was from San Francisco to Salt Lake City, so I jumped forward one hour. When I landed and reenabled cell service, my phone updated to reflect the new time zone.

At 12:45 AM MDT, I noticed the clock on my Fitbit's screen still reported 11:45 PM (i.e. it hadn't synced with my phone so it didn't know I had moved time zones). I opened the Fitbit app on my phone to trigger a sync, which fixed the clock time on the device's screen.

However, when I opened the app this morning, it reports over 13,000 steps despite me barely walking today. I still see the 12,000 number on yesterday's view as well. My conclusion is that the steps that I took yesterday were "copied" into the count for today, after the sync to update the device's clock that I did last night -- since the hour jump moved me from one day to the next. As a result, it's reporting way more steps and floors today than it should.

If it makes any difference, I performed the sync while the One was in sleep capturing mode.

[SantiR]

@wyattstorch42 Welcome to the Fitbit Community! That is strange, it may be a bug! Thanks for reporting your experience. You can also report this experience to customer support, just for them to be aware of this. What I recommend to do is to manually log an activity as driving (check that excellent post from @Rich_Laue) for the hours that those extra steps were credited. That option will delete that data and shouldn't happen again. 

Try that out and let me know how it goes!