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
02-04-2022 20:18
02-04-2022 20:18
Came up to Queensland yesterday. Clocks went back by 1 hour as the State does not adopt daylight saving unlike New South Wales. Miraculously Sp02 was reported correctly last night. Wonder what it will be tonight 😂
02-05-2022 05:35
02-05-2022 05:35
@SunsetRunner So I'm like 99% sure that even when I wake up early on a work day, I have my SpO2 available for my at 5am. That would be 7pm your time if I have that correct. But you've already said it can be past that time and you still won't have the previous nights SpO2. 🧐
02-05-2022 06:34
02-05-2022 06:34
It's eleven thirty pm and this is the present screenshot
By the way it's not that I don't have it, it is the one written as yesterday. Not a big deal but just because it's a silly bug it would be nice to have fixed it to improve the users experience.
02-05-2022 06:56
02-05-2022 06:56
@SunsetRunner Yeah that's ridiculous that you don't have one for the 5th, last night, yet I do.
Their dating will always confuse me as my previous sleep tracking would date it the night of the sleep and not the morning after. 😂
02-05-2022 22:44
02-05-2022 22:44
It was too good to be true. After being good for the first night when we changed the time back by 1 hour to Queensland time it was back again to the 1 day lagging on the second night 🤦🏻:male_sign:
02-07-2022
10:19
- last edited on
02-27-2024
03:34
by
MarreFitbit
02-07-2022
10:19
- last edited on
02-27-2024
03:34
by
MarreFitbit
Hi everyone.
Thanks for the detailed information and the steps tried on your own. Also, for the screenshots provided. This issue was reported to our team before and they're working on to identify a resolution as quickly as possible. I understand how you're feeling about your SpO2 data not updating correctly and please know we'll keep our team informed of the impact to you and other members.
Your patience and feedback are truly appreciated, and I'll update this thread once we have more details to share.
See you around.
02-07-2022 11:14
02-07-2022 11:14
"This issue was reported to our team before and they're working on to identify a resolution as quickly as possible." Well I really really hope so, but also notice that statement has been used on other long-standing issues without any sign of action so far.
02-11-2022 15:37
02-11-2022 15:37
Hi there, @scaddenp.
Thanks for taking the time to share your thorough feedback. I understand where you're coming from and I apologize for this inconvenience. While we don't have a time frame, please know your feedback will be passed along so our team can keep working hard on this situation. In the meantime, let me recommend keeping the Fitbit app updated and your Sense synced correctly so the rest of your details are updated correctly.
See you around.
06-10-2022 05:17
06-10-2022 05:17
Hello. It’s June. I ended up here because I have a brand new Charge 5 and I’m seeing the exact same issue as everyone here, and a handful of other threads where people have reported the same thing. Any update?
This bug means the Health Metrics screen will always say “not all data has loaded” for the current day.
I work as a software developer, I swear this fix can’t possibly be that complex. I don’t think most people here care about fixing the old data, just leave a one day gap and fix the new data. From the timestamps I’m seeing, it’s been over a year and a half since this issue was first reported. Please communicate this to the developers, someone needs to finally prioritize this bug. Just be because the bug doesn’t affect Americans doesn’t mean the rest of your customers don’t matter.
06-10-2022 20:05
06-10-2022 20:05
No the problem has not been fixed and I am having to put up with the 1 day lag since I owned the Sense and have the Premium subscription for almost 1.5 years now. The excuse I am hearing is that Fitbit cannot handle the time zone for Australia but I think this is just BS because it can handle the other metrics OK.
06-11-2022 00:01
06-11-2022 00:01
I agree with you about the BS excuse. Even it was true well they can find another way to solve the issue that is solely depending on them, this time they can't blame the other parties integration like they always do.
By the way I'm in Korea and my family suffers the same issue with a Luxe and a Sense, i had the same problem with a Charge 4. So the issue is not on the tracker but on the backend, not sure if only on Android (as we use) or iOS too.
06-11-2022 00:35
06-11-2022 00:35
I am on latest version of iOS and latest version of the Fitbit app.
06-12-2022 13:34
06-12-2022 13:34
LizzieFitbit said 7 months ago - " I understand where you're coming from and I apologize for this inconvenience. While we don't have a time frame, please know your feedback will be passed along so our team can keep working hard on this situation"
"Keep working hard on this situation" - I call BS. I am also a programmer and would be embarrassed if I couldnt fix in a week.
06-12-2022 17:05
06-12-2022 17:05
I m also on latest Andriod n latest Fitbit app version n Premium subscription. I have since gave up tracking the SPO2, its either 1 day or 2 days missing. I bought an oximeter so that I get can instant SP02 reading if I m.unwell.
11-20-2022 03:06
11-20-2022 03:06
I can also confirm this is happening on my Charge 5 HR.
Can I remind everybody that this is a paid feature? It's mind boggling how it's now 2 years without any action from your part.
I feel like you need to escalate this and get this prioritised, or stop taking money for Fitbit Premium.