SpO2 readings one day behind

[yoongielogy]

I have a bit of a weird situation.

Under Health Metrics, there were a few nights in a row where the Fitbit failed to record my SpO2. That's fine, tracking can fail for any reason.

The problem is, when it does record SpO2 it now records it for the previous day. For example, when I wake up and sync on Friday, that reading shows up on Thursday.

I'm seeing a similar bug reported a year ago for another device: https://community.fitbit.com/t5/Ionic/Sp02-graph-lags-by-one-day/td-p/4504160

Seems to only be happening this week after a firmware update? All my other readings appear in the correct dates.

[hillmanoholic]

This happens on mine and as it has always happened I have accepted it as normal. On my morning sync my health metrics update but my O2 always says “No data for the past 24hrs” but the following day my O2 reading will appear. Just assumed there must be a time of day when it updates that doesn’t match my morning! 

[t.parker]

Try to reboot the watch after waking up. I noticed on my Sense (may apply to Charge 5, too) that the SpO2 sensor keeps running after waking up and probably it delays syncing (if you sync the watch with the app you will see sleep data, readiness but no SpO2 for this morning). Rebooting the watch brings data immediately after syncing with the app. I wish Fitbit implemented manual sleep termination (which terminates all the sleep-related readings) like [my-other-watch].

[yoongielogy]

That's very interesting, but doesn't quite sound like the problem I'm describing. I know the SpO2 data takes a while after waking up until it becomes available (I think the FAQ says it can take up to an hour). That's what's happening for me, it's slightly delayed after waking up, but I still get an SpO2 reading.

The problem is that the reading would appear one day behind, although it's from the most recent reading. For example, if I wake up with 95% SpO2 on Friday, and decide to sync it, that reading will appear as though it was taken on Thursday (although it's clearly for Friday). The link I posted has many other examples of people experiencing similar issues for Ionic, and it looks like there's another poster who has the same problem for Charge 5 who replied in this thread.

All my other metrics show the correct dates, so it seems to me this is most likely a date/timezone handling bug specifically for the SpO2.

[yoongielogy]

Still happening after restarting the app and device. 

Not a huge problem, but pretty annoying since this is a paid feature. Any chance this can be patched in the next firmware update?

[yoongielogy]

Over a year later and still seeing this problem. Is this really that hard to fix?

It's a paid feature, so I'm pretty annoyed it's still an issue after a year. Any ETA?

Otherwise, I feel like potential buyers and subscribers to Fitbit Premium need to know about this before buying.

[MsDraz]

Have you tried directly contacting Fitbit support by chat or phone?

Following is a link to help you contact Fitbit support: https://myhelp.fitbit.com/s/support?language=en_US