Having issues with your Fitbit wearable? You’re not alone, as the Fitbit community forums are full of users complaining about problems with the displayed time.

Owners of multiple kinds of Fitbit watch, including the Charge 6, Sense 2 and Inspire 3, say their device shows the wrong time with the latest firmware.

There are repeated reports of Fitbits reverting to GMT, or at least the wrong time zone, despite multiple attempts to re-sync the time with the phone companion app.

“I have a Fitbit Sense 2,” writes FitbitUser1112. “For the past six hours or so, Fitbit is showing Greenwich Mean Time (GMT) on my Fitbit. I live in India, which is GMT+ 5 hours and 30 minutes.”

“A few days ago, my Charge 6 suddenly started showing the wrong time. It is 12 hours and 25 minutes wrong,” writes Little_Me in another post.

The timing of these issues suggests it may have been caused by a recent update to Fitbit’s software, version 210.26. It was released across multiple product lines on September 6.

I have approached Fitbit for a statement on this issue, and will add any extra information provided to this story.

Fitbit has acknowledged the issue on its social channels, in response to users noting the issues they have on X, to the FitbitSupport account.

“We’re aware of the wrong time being displayed on some Fitbit devices & our engineers are working to get it fixed as soon as possible,” the account wrote in response to user Manas.

The account is also asking for Fitbit users’ email addresses and countries of residence when they ask FitbitSupport to investigate.

What Is Fitbit Update 210.26?

Changes made to the Fitbit software in version 210.26 vary by device, but the patch notes claims the update improves the accuracy of GPS across models, and introduces more auto-recognition of different kinds of exercise.

It also claims the heart rate accuracy of the Fitbit Versa 4 and Sense 2 have been improved using “advanced Google ML.” That’s machine learning.

Not having any luck getting your Fitbit to display the right time? This may be a case of Fitbit needing to issue another minor software update to get time zone sync back in order. You may have to put up with this bug for a few more days.

Share.
Exit mobile version