Charge 5 spO2 measurement issues

[Maddy_C]

My Charge 5 was recording my spO2 very well until the day before yesterday. Now it says an app is needed to do this reading. However, when I looked deeper it said the app wasn't available for the Charge 5! How do I get my O2 readings back? 

[MikeC.]

I'm having the same issue which started today and can't find a solution!

[doclynn]

Same issue here. I've been measuring O2 sats for months, today I wake up to this nonsense. An app is needed but it's not available? What the heck is going on? And the new display of health metrics stinks. 

[doclynn]

And... 5 minutes later the SpO2 is displaying properly. The increasing flakiness of fitbit is really a pain. Every change makes the device worse. 

[doclynn]

And... this morning it isn't working again. Only my RHR showed up, all the other metrics are "no data" and spO2 is telling me I need an app. What fresh hell is this?

[supertrooper3]

I had the same problem this morning for the first time. After going into the settings on my FitBit watch and restarting the device, the SpO2 was suddenly back again!

[BoilerBill]

Also not working here. The app installs on the watch and appears to work but the Fitbit app tells me I need to reinstall. When I do try to install it tells me that it's not suitable for this device. This only happened in the last few days

[doclynn]

And today it's not even showing my sleep or any health metrics other than rhr. What is going on? Very upset.

[MikeC.]

I was on chat with them, and had to uninstall, then reinstall the Fitbit app on my phone.  That seemed to fix it.....until today!  Same problem as before, except the fix is not working.  Went with chat again and they are going to the higher ups.  I have to wait for an email from them.

[RiekoC]

Hello @MikeC. , @doclynn , @BoilerBill , @supertrooper3 , @Maddy_C 

Please see this thread on the same issue (<-- click link) where the Moderator acknowledged that the team is aware of the issue and is working on fixing the problem. So far, there isn't a timeline for the fix. 

At this point, there's no troubleshooting steps that we can recommend since the issue is on the Fitbit side.