Fitbit Product Experts Alumni are retired members of the Fitbit Product Expert Program. Learn more
There is an issue with the step counting as shown here, with the dated Core Stats.
At 15:38 the watch was indicating an erroneous 13,256 steps
After a sync it was showing a more accurate 8,536 steps
How or why this bug has appeared is unknown. It is due to improper syncing/server processing.
There is nothing a user can do to fix this bug, any attempts could make matters worse and be a waste of time.
If the watch is not connected to the Fitbit App, by closing the app [often not possible] or better by turning off Bluetooth, and the steps are correct it would confirm that as the cause.
For Versa/Sense users [not Versa 4 or Sense 2], the SimpleCheckUp app [first screen] might help to know on the watch when the watch last synced.
When turning on Bluetooth again, it is necessary to manual sync a few times to get the correct steps to show.
This bug is NOT related to any watch firmware update or Fitbit App update and applies to all phone and watch types. There will be no update issued to fix it.
Steps counting bug - Update March 20th
It seems this is still not entirely stable and Google may still be introducing changes.
Small adjustments can appear when auto syncing [every 15 minutes about depending on connectivity] or even manual syncing randomly.
Steps counting bug - Update March 19th
After some more testing and in the absence of any official information from Google - the app finally appears to sync correctly without any unwanted adjustments.
Of note, no action by the user was/is necessary for the syncing to be correct, as the error was only at the Google end.
Steps counting bug - Update March 17th
Some people still noticed minor adjustments to the watch steps when syncing, meaning the problem is still not fully fixed.
Steps counting bug - Update April 7th:
The ensuing minor steps adjusting bug that was still prevalent seems also fixed now.
Steps counting bug - Update March 13th:
This may finally be fixed - check steps on your device and manually sync, If the app then shows the same for you it is fixed. However some minor adjustments still seem to occur.
Stress Management Score - Update March 7th:
The missing Stress Management Score that affected all user types [regular or premium] is supposedly fixed now without any user intervention. Though the missing history is not recovered.
For those still not getting it yet please make a separate post/investigation.
Author | ch, passion for improvement.
Answered! Go to the Best Answer.
Use the device sync not the pull down sync! It will run through twice and if you hit the sync once more, your steps will be correct. Oh also leave Bluetooth off until you’re ready to sync
Best AnswerHi all,
I just received an email from support that tells me to get an update from Google play, from .47 to .48, from March 11. Interestingly,I was unable to copy their email for some reason! Maybe that will help, who knows?
As have I. I warmed up with 4 miles before working a soccer tournament last weekend. I was seeing my steps over 30,000 (not surprising on a full sized indoor field with 8 games) but then down to 24,000. I actually have another watch I use for soccer, and had that one tracking steps, and they didn't match. I got 4400 steps on one game with the other device.
FITBIT SUPPORT - PLEASE FIX THIS.
Best AnswerI just got off a chat with Fitbit customer service. Of course they're familiar with the problem and they're working on it ASAP to fix it. I tried to tell them my workaround and maybe that would help them find the issue but they didn't seem to interested. They told me even if you have a workaround it's still broken. A few years ago I found a miles issue in the app that really only affected iPhone users. If you look at the individual time frames for miles, they are not miles. They will not add up to what the total miles are and I figured out that it's a convoluted formula to get you to what they should be per hour. The program actually looks at the miles as kilometers and so it turns it into something. I found if you multiply the hour by the formula to convert a kilometer to a mile then it will turn it into a mile and you can get the mile amount. This is never been fixed since it started several years ago. If you have an android, you don't know what I'm talking about.
Best AnswerConfirmed. I just had the problem again. I caught it before I got my "first" 10000 step notice.
Best AnswerNo, I removed and downloaded from google play twice and got the same earlier version twice. Very frustrating.
Best AnswerMissy1436. A new watch would have the same issue. As has been posted here around a dozen times, this is not a Sense or Versa, or any watch model problem. This is an issue with the Fitbit app and the sync with the servers.
I have been told by Support that I just have to keep on checking the play store to see when the update is available....so any day between now and the 11th!
Best Answer