Charge 6 - No Firmware Update button

[strickersa]

I have a Charge 6 that shows it is on Version 210.26. The current version for Charge 6s is 214.24. When I do the steps to update (Today tab, selecting device) there should be a pink Update button to select, but there isn't an Update button. How do I update to version 214.24?

Moderator edit - updated subject for clarity

[Vile_Andy]

Is there anything new on this? I have restarted both my phone and charge 6, as well as reset the charge 6 over the last few days but still no update button even though I am on 210.26

[Reaperhk]

I have done everything listed on "how do I update the fitbit device" and app, but I can't see the firmware updated.

The new app also does not support the old Sp02 reading too.

Do I need to do the factory reset in order to see the opinion?
(I am in Australia)

[Hotbill]

No, still no update available. It's really annoying. I understand that it's a progressive release but a snail would have released it faster than that. My guess is that it's a problematic update and they're trying to fix it. We are waiting for months now...

[narrlv]

I'd just like to post that this morning, indeed the 214.24 update finally arrived here, in California.

So apparently it is just necessary to keep up hope....

Installation was straightforward.

• Do be sure to connect your Fitbit to a good charger with the cable before beginning.
• If it's low on battery, not a bad idea to let it charge for an hour, say, to somewhere near 100%, before you click the button to begin. This will avoid problems with jostling the connector loose, surge in updating power demand, etc..
• with the phone near and Charge 6 undisturbed on the cable, updating was smooth. It took only 5 minutes, after promising it might take 40. This is with a fast internet and recent Bluetooth (pixel 6a) if that matters.

Now, the Bluetooth update part.

• this doesn't appear right away -- rather some minutes later, and I think on a sync attempt or re-opening of the Fitbit app
• it also was smooth, with delays, soon asks you to click to re-pair, which it handles
• the first sync after this Bluetooth revision had a big pause, about a minute -- not sure if this was expected, or just a bobble in my wifi. But it completed when left to do so, and afterwards has been rapid in steps as expected.

And, the 'indicators'....

• at first, I couldn't see any, did some variation on settings and attempts, I think not at all the thing to do
• then I read more carefully the update notes, and find that _none_ of the indicators would show unless one of their four conditions was true. And those conditions aren't true in normal operation
• I had noticed, with very much care, that there appeared for a brief moment, a nearly invisible 'shadow' at the top of display, where the indicators will show, on 'opening' the watch display (when you double tap, or have the wrist motion enabled and use it). 
• so it makes sense that indicators will show if need to, and not require a specific one of the watch faces, which I'd wondered about, as I'm using Continuum, which wouldn't have space if it wasn't an overlay.

My conclusion is that the 'indicators' are mainly an inducement to get you to update the firmware, and that what they really want is that you do it so that the Bluetooth changes can get put in place.

Good to have the latest firmware, anyway, and the Charge 6 has been working very well, including the no-phone inbuilt GPS. The secret to that is following their advice about a loose fit -- what that does is let the watch ride on its sensor bump, not squashed down with the sides flush on your skin. And that lets the antenna for GPS function, as it's built near the bottom sides.

And in addition, the band is much more comfortable when allowed to be loose, so it doesn't particularly get stuck to the skin. Having tried it both ways, with one of those very flexible perforated sports bands Google offers that I got with the watch.

[DaveN54]

Just a quick update. Finally got the new update 214 in Canada today for my Charge 6.

Install was really quick took about 5 minutes, the reconnect to Bluetooth was done within 1 minute.

All seem to be good. Hopefully everyone else gets the update quickly now.

Also thanks for a lot of replies offering difficult ways to update or get the update button on the app.

[Hotbill]

I finally received too.

It was about time. Thanks for your review

[Reaperhk]

Get the update too.

It still said that need SPO2 app install but the report gets the data

[Jayes249]

I've finally received the firmware update, installation was a breeze except
for the Bluetooth at the end. It took a little while to sync, but works OK
once done so.

One thing that irks me a bit is the diagonal strike-through (where the
heart rate indicator appears) when my connected device is switched off or
out of range. The HR appears briefly, then reverts to the strike-through.
It never did that with the previous version and is unnecessary IMO. Not a
biggie, but I'd suggest correcting this in a future update?

[narrlv]

Hi @Jayes249 , 

If I've understood you correctly, it seems that the strikeout should be expected, and not an irritant.

It's telling you that there's no current Heart Rate measurement available.-- as you said, when your device is out of range.

So this way you won't try to read it and get a wrong answer, or believe what would be an incomplete and thus not up to date history.

Sound rigtht, seen this way?  I did notice some refinements in how the latest app is presenting several items of its information, so it seems this one also was well intended. Unless it's getting in your way in another fashion!

Best on it,
Clive

[Jayes249]

(Please note this problem applies to clock faces where the heart rate reading appears middle-top and when it happens to coincide with the bluetooth disconnected symbol.) 

Not quite correct - the clock face is still showing what appears to be the
correct heart rate when disconnected, it's just that it only appears
briefly before the strike-through, which then remains on the screen until
it refreshes eg. after the next raise to wake. I find this annoying as I
often miss the reading on first glance and need to move my wrist (to
refresh the screen) to view it on second glance.

It will be interesting to see what the rest of the community thinks!