Charge 6 Firmware Update 210.26

[LizzyFitbit]

We’re excited to announce that a firmware update version 210.26 for Charge 6 has been released to all our members. Some of you might already have this update available. If you installed it, let us know what you think!

We release updates to customers in phases. If you don’t see it, check the Fitbit app in a few days, and you’ll see a message when you can install the update. We appreciate your patience while we get this update to all of our customers.

*Firmware releases are not distributed based on region or location and can reach anyone no matter where you reside. We do not recommend performing a factory reset to force the update to your device as your data will be lost and you may not get the update. Please be patient and wait until you see the update banner inside of the Fitbit app to begin the firmware download.

WHAT’S NEW AND FIXED

• Your device can now auto-recognize 6 new workout types: running, walking, biking, elliptical, rowing, and spinning.
• GPS accuracy has been improved by better switching between on-board and connected GPS during a workout.
• This release includes bug fixes and improvements.

Full release notes can be found here.

HOW DO I UPDATE?
See How do I update my Fitbit device? for step by step instructions for updating your Charge 6. If you run into difficulty updating, review these Why can't I update my Fitbit device?

We’re interested in hearing your feedback on this update! Let us know what you like! If you encounter unexpected behavior during or after your update, please post the details below.

[dah_sunnyvale]

I recently updated firmware on my charge 6 (unsure of revision number).  A few days later (Sep 6) and it is completely non-responsive.  Charging doesn't work.  Multiple attempts to reset with charging cable buttons (C5 + C6) fail.  No response (no vibration) attaching to cables. 

Similar problem to when I updated firmware on my charge 5, and ended up switching to my charge 6 Christmas present.

Cleaning contacts did not help.

My suspicion is that the update stopped charging from working.

I spent years doing software QA, so I'm good at following directions.

Any hope of getting my device working or should I just give up on Fitbit?  (I've been happy with my Google Pixel phones).

Fitbit app on my Pixel 6a is still working.  Any info I can get from it for you to debug with?

[dah_sunnyvale]

P.S.  After the update, my Charge 6 gave me a number of new workout options (I only use "walk").  Perhaps that helps identify the firmware rev?

[Peghigs]

Same with mine.  I installed the firmware update and my 4 month old Charge 6 totally died and was unable to be revived.  My app showed that I needed to install the update, but wouldn't allow me to.  It was already installed, and would not allow me to click on it.  I am in the process of waiting on replacement of the charging cord that they forgot to send me when they replaced my unresponsive Charge 6.  I hope the update does not need to be applied to my replacement Charge 6.

[Ij80]

Yep but I Ve discovered today, changing credit card, that I cannot add any more credit cards because of new security procedures (all cards can be now activated to digital payements on GPay trpught the bank app). 

Do you know some credit debit card still available on Fitbit charge 6? Revolut for example? Tks

[Peghigs]

Can't help you.  I don't use the credit card/pay feature with my Fitbit.

[Cherylpnz]

I updated my phone's fitbut app today and it totally killed my charge 6- screen balnk no activity even though charged and wont pair with the phone. What did the update do? Wind it back as it doesnt work

very annoying

[Hagow]

Hi, I just wanted to note that the "HR on equipment" feature no longer seems to be working well for me after the latest update. I primarily use the feature to connect my Charge 6 as a hear rate monitor to Strava on my Pixel 6 phone. This has worked well for me from when I bought it in June 2024 up until mid-August 2024. After that, it only seems to connect to Strava after I pair my fitbit to my phone for the first time.  Subsequently, it fails to connect again unless I tell my phone to forget the bluetooth connection to the Charge 6 and re-pair it again. Anyone else run into this problem after the update?

[MissJD]

Whatever was recently upgraded did not fix the GPS accuracy--it broke it. I walk regularly on a public trail, and the mileage for the trail has been confirmed by the city and is posted on the trail. In the past, my Fitbit always perfectly matched the trail mileage as reported by the city. Now suddenly, it is wildly off--by as much as 3/4 of a mile after a 5-mile walk. I have restarted both the device and my phone a half dozen times and that has not resolved it. I have tried both phone and dynamic for the GPS settings and neither has resolved it. What can be done to resolve this? I am about ready to throw away this device and try another brand.

[Angela_Chu]

Did the update screw up Charge 6's display time? I am based in Singapore, and my Charge 6 is showing 12:08 PM instead of 20:08 PM! The Charge 6 is 8 hours behind! I have ensured the location and time settings are set to Singapore, uninstalled and re-installed the app, restarted my Fitbit watch countless of times but still no use! Can Fitbit advise ASAP! I am not the only one facing this issue in Singapore. There are others and there are also others facing this issue from other countries too! 

[AnmolRohatgi]

Facing the same issue in India. Display time is forced set to GMT.  Just to validate, I tried changing to multiple other time zones. Worked for shanghai/Adelaide. 

[GirishKalia]

My fitbit charge 6 is forced set to GMT time zone instead of India timezone i.e., GMT +5:30 

I have tried all possible routes of changing the timezone or resetting the device but the problem still persists. 

Seems to be a bug in latest firmware update. 

[jahanzeb_10]

Same issue here

[jahanzeb_10]

Display time is set to GMT and If I change it it only goes to GMT +1 or GMT -1

[Superleche]

The update has brought a BIG BUG. The time shown on the watch is not correct. Until yesterday the time was correctly set, and today it dawned out of sync and there is no way to correct it. It always shows the time corresponding to GMT+00:00 Time Zone no matter what settings are made.

The date, time and location on my Pixel 8 are correct. My Charge 6 is set to take the settings from the phone, however, as I mentioned, there is a incorrect time. My time zone is GMT-05:00 and there is no daylight saving time.

Through the Fitbit app, in the date and time settings, the same time is shown on the phone (GMT-05:00) but the time is not correct. I have changed to manual settings and it still does not correct the time. I have also tried changing the language and nothing. I have restarted the phone and watch and nothing is fixed. I even set the time zone to GMT-02:00 Greenland and the time is still GMT+00:00 Greenwich.

[Sheyla]

The new version completely screwed up the time shown on the clock face. I've tried disablyng gps, disabling automatic time zone, manually changed time zones on the phone app, it does not show accurate time for any city in my timezone. I'm either way ahead or way behind.
This update sucked. Fix it back to previous version, please.

[Y19HL]

My timezone is stuck at gmt, instead of local time. Very upset.

[Angela_Chu]

Hello! I changed my time zone to Shanghai (GMT+8, same as Singapore where I'm at), synced and restarted Charge 6, and it WORKED! My sleep score and hours which were previously not displayed on Charge 6 (but I could see them via the app) were updated as well. May wish to give this a try if anyone of you are in a similar time zone. 

[Sheyla]

I'm on GMT-3, tried it twice and nothing. I've even removed and re-added the device on my app, too.
Sometimes when I select citites in my time zone, the app un-selects them immediately.
After hours of frustration, I've selected Havana's time zone simple because its the closes that's working (1hr behind rather than 3hrs ahead). Will try again later, now I gotta go to work.

[bunin.oo]

It's showing the wrong time, and nothing seems to fix it.