12-16-2021
03:22
- last edited on
02-07-2022
09:52
by
LizzyFitbit
12-16-2021
03:22
- last edited on
02-07-2022
09:52
by
LizzyFitbit
On 18 March I reported this issue of the Sp02 data on Health Metrics lagging by one day. Fitbit replied acknowledging they know about the issue. It is now 16 December and the issue is still unresolved. I have the latest Fitbit App and the latest upgrade for the Sense.
Moderator Edit: Clarified subject and updated label
12-16-2021 05:13
12-16-2021 05:13
At least there is an output / report to those.
12-16-2021 11:35
12-16-2021 11:35
I reported this this too. Utterly beyond me why they can sync other data from watch but not SPO2 which the watch is reporting. Script kiddies doing the programming? - or more likely simply not interested. Not exactly the only issue like that. Feels like the development team have left the room.
12-16-2021 11:36
12-16-2021 11:36
Of course getting the data one day late is a bonus. My wife often doesnt get data at all despite being about to see the SPO2 value on her watch.
12-16-2021 21:27 - edited 12-16-2021 21:28
12-16-2021 21:27 - edited 12-16-2021 21:28
Here in Japan we have the same problem. I think it has to do with timezone (I saw some reports from Australia) but this can't explain why the other metrics are correctly shown.
What I find always disappointing is answers like "Fitbit is aware of the issue but UNABLE to provide a date when this will be fixed" or, even worse "we might not be able to provide a fix for the immediate future"
By the way the problem is not restricted to Sense but it's in the app (I have the same issue with Luxe, specifically using Android)
12-17-2021 01:46
12-17-2021 01:46
I think the difficulty isn't to fix the lagging, but all users' previous SpO₂ data have to be moved by one day, including data on Fitbit's server and users' local app. That's why Fitbit hasn't apply the fix till now.
12-17-2021 03:32
12-17-2021 03:32
Well if this is the case the more they wait the more the data they have to move. If they fixed when it was as first reported it would have been easier.
The problem is that probably the developers are not even aware of the bugs as i have the feeling that nothing we report here is being forwarded.
12-17-2021 11:26
12-17-2021 11:26
Hmm. I am in New Zealand so that fits with it being a time zone issue. But still dont get wht SPO2 is different from every other measure on the clock which are in local time and SPO2 could just be synced with all of them.
12-19-2021 21:46
12-19-2021 21:46
So far no response from Fitbit 🤦🏻:male_sign:
12-20-2021 01:59
12-20-2021 01:59
@Guitarplayer developers may read community forums. Even if it's not being forwarded anywhere, they would have to be living in a cage with no access to the outside world to stay that oblivious to the problems users have with their devices 🙂 It's more like, the company strategy is not to fix those issues, the fixes are not in their roadmap. It is easier to pretend the problem doesn't exist than allocate resources to investigate and resolve it. Especially, when the company is rushing from one release to the next one and, I assume, no devs left to spare. I remember a very old bug in the Android app (showing '--' instead of calories in the 'Workout' summary). Very visible one, you couldn't miss it yet it took over 2 years since it has been reported to finally fix it. Solving issues is certainly not a priority.
02-03-2022 13:40
02-03-2022 13:40
I also reported this problem to Fitbit Support on Mar 2021 and after some diagnosis/remedial (install/uninstall,; wear more days; sync daily; etc), they acknowledged that it's a known problem on the fitbit app.
Now it's almost year later, recently inreplacedna replacementn Sense cos my original Sense failed to start, been wearing the new Sense for a wk, SP02 in still only showing up on the clock face but on the fitbit app, it is still 1 day lag. Sad that prob still not solve after 1yr.
02-03-2022 17:38
02-03-2022 17:38
@Klimhl I've been using my Sense since December 29, 2021 and had yet to see a delay or miss in SpO2 until today. My Health Metrics doesn't show yesterday. Let's see if this is the start of a 1-day delay.
02-03-2022 19:30
02-03-2022 19:30
Today is Friday.4Feb
My Sense clock face has the SpO2 % displayed but Health Metrics main page showed "no data in the past 24 hours" Blood Oxygenation and the graph Oxygen Saturation showed this wk daily readings for Sun,Sat,Mon,Tue,Thu 3Feb only).
This is 1 day lag right ?
Wanted to attach the snapshots but can't find a way....
02-04-2022 06:37
02-04-2022 06:37
Looks like I got my missing SpO2, 2/2, and yesterday and today's already.
To attach a screenshot, I'm on my phone and tap the photo icon in the reply and select my screenshot.
02-04-2022 07:03 - edited 02-04-2022 07:07
02-04-2022 07:03 - edited 02-04-2022 07:07
02-04-2022 07:57
02-04-2022 07:57
@SunsetRunner I'm in Tampa, FL so EST. That's pretty crazy they can't adjust for time zone if that's the main issue. That makes sense why @Klimhl can't post pics. Prevents spammers.
02-04-2022 17:59
02-04-2022 17:59
This morning I woke around 6 and, after having synced my Fitbit, I took the following screenshots.
Resting Heart Rate
Breathing Rate
HRC
SpO2
Skin Temperature
You can see that Skin Temperature, HRV, Breathing Rate are recorded, Resting Heart Rate misses one day (still to be calculated) but SpO2 lacks 2 days. For information also the tracker lacks the indication of SpO2.
After few hours I checked again the tracker and the SpO2 indication appears (96%) so I synced again and here are the screenshots.
Resting Heart Rate
SpO2
You can see that now Resting Heart Rate is updated while also SpO2 is update but one day before. I can wait until midnight, sync as many times you want, restart, perform factory reset and change phone and this behavior won't change. This issue has been going on since the release of the Health metrics and Fitbit never fixes or even try to update the users. It's still small things that ruin the pleasure to use the Fitbit service.
02-04-2022 18:11 - edited 02-05-2022 01:44
02-04-2022 18:11 - edited 02-05-2022 01:44
I wonder what time and time zone their information is processed in. @SunsetRunner
02-04-2022 18:48
02-04-2022 18:48
As I wrote I'm in South Korea (Time zone in Seoul, South Korea (GMT+9))
The mystery is however why all metrics are processed correctly and only SpO2 isn't. Where are the developers? Can you contact them?
02-04-2022 19:07
02-04-2022 19:07
Hi everyone,
Tks very much for ur advice.
I m in GMT+8. Its Sat 11am now
@SunsetRunner, I encountered the same, all the rest of the Health MMetri data are current as at Sat except Sp02 which is still showing Fri data, whilst my Sense device is already reflecting most current %.
I was just commenting that this prob has been unsolved for a year. I hv given up hope and only check once in a month if the apps is fixed.
Happy wkend all... 😀