Unreliable step counting bug

[Guy_]

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 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.

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.

[MB555]

Ach that's a shame. Hope they fix it soon and you can happily keep your Fitbit. Mine at least doubles the steps then sync and they go back to accurate.

[NorfolkReg]

Has there been any feedback from Google/Fitbit about this? It’s really annoying, some days I reach my target step count 3 times!

[MB555]

Haven't heard anything as yet.

[NorfolkReg]

😟 shame

[ArcadeTechGW]

I agree, but what can you do?

Our watches indicated different start times for our activity today, so we tried to set it to where we wanted it.

The Sense on the App - NOPE - I'll set it where ever I want to.  How about 11 am until 10 PM?  Change it, save it, NOPE, 10 am until 11 pm.

Try multiple times, same effect.  How long FitBit does it take to fix a "server issue?"  Can we get an answer to that?

I'm going out for dinner tonight.  Best Buy is nearby.  Maybe it's time to say farewell to the FitBit brand (which means Google Watch too) and look somewhere else?

[Guy_]

There's a bug if you switched to daylight savings where things can't be changed or are wrong, but should be ok on Monday.

[MWJ]

I wished they have a fitbit contact so we can get the real answer instead
of just whining about the problems.

[NorfolkReg]

At least I now know it’s not just me…😐

[MB555]

You can go on Fitbit Support on X if that's any help. Nothing like a good whine 😀

[d7e]

I am really disappointed in fitbit. I really liked the sense 2 and the app but am now moving on. I looked at both the pixel 3 and galaxy watch 7 and ended up buying the galaxy watch 7 44mm. Other than the need to charge the galaxy watch more often it looks like a much better watch with hopefully better support. Time will tell....

[Starry2]

Thanks, mine has been doing this since last year around the time of google changeover funnily enough. But the on wrist device is accurate and the app just keeps reducing steps overnight in this case. Resyncing, turning Bluetooth off and on again, logging out shutting down a turning everything thing back on again only sometimes results in a temporary fix. I cannot find a way of unpairing my app with my old inspire, it’s not as per the previous suggestions. I think it’s time for a change if Fitbit are not putting in a fix on this.

[6down3togo]

re the Step Counting Bug

I find I do get to the correct step count after several manual re-syncs.  If I don't manually re-sync, by bedtime it has corrected itself.

I go for a daily walk along the route I have walked many times before.  By days end my steps end up being within what I consider to be normal range.

It's annoying, especially when I'm hoping to get a calorie count before dinner so I know if I can have a bit of dessert afterwards, but completely livable temporarily imho. LOL.

[Sargal]

Seems like the watch should be controlling the numbers, not the other way
around. If I don’t use the app the watch does just fine. I waited until I
reached my goal of 20000 steps then pulled up the app to record the
workout. Boom, 3000 steps were gone. 😡
I’ve tried everything. Hey Google, if you are not going to make things
better don’t take over a company and screw it up for its users.

[Suzbaus]

Has anybody has an update and, that update fixed the problem?

[MWJ]

No but I called fit bit today. Said they were aware of the problem &
trying to find a fix.

I requested they update their findings on the community board. He said he
would pass along my suggestions. I'm not too hopeful.

[carrieL0603]

Seriously, I actually tried out a Samsung watch and found it not as good as fitbit and switched back to the versa 3 when it was new. Since I think I will be switching from a Samsung phone to an iPhone soon I might make the switch to an Apple watch. Which is a shame because I have been an arden fitbit wearer since the beginning!

[Ashish_s]

I looked at my step count and ordered a burger as a treat. After I synced and the step count updated, I could only afford the lettuce from my step budget. Daam shame I tell ya.

First, the UI disappointment and now, this. If Google does not up it's game soon, they will start losing 8 year Fitbit loyalists.

[Sargal]

I have an Apple Watch and a Fitbit versa 3. Yeah crazy, right. I spent a lot of time counting steps and checking both of these watches. The Fitbit was 3 to 8 hundred steps better at being correct on the steps. I count steps on Versa and everything else on my Apple Watch. Just sayin. Have a great rest of your day. 

[JMS10]

I have a Sense and if the clock face I use has steps, that step count is accurate while the step count on the app and core stats are incorrect. The incorrect counts ultimately match the clock face steps so it would be interesting to know where the authors of the clock face are pulling their count from versus where Fitbit is pulling the app and core stats from.

[Chrissy101]

Did it ever fix because mine is doing it now.