07-21-2022
10:45
- last edited on
07-22-2022
15:00
by
LizzyFitbit
07-21-2022
10:45
- last edited on
07-22-2022
15:00
by
LizzyFitbit
Hi, I just noticed that the green and yellow lines have changed and now are all over the place on the graph. All graphs for different days start with a 0:00 hrs. The fluctuations are not at all in line with what I was reading up until today. Anyone experienced this issue?? Thanks
Moderator Edit: Clarified subject
Answered! Go to the Best Answer.
08-04-2022 08:01
08-04-2022 08:01
I think it is a bug in the latest app update. I have the same app behavior. If you go back and look in your sleep history, they all look like that even though previously they looked fine. I am hoping a moderator can confirm this.
08-04-2022 08:02
08-04-2022 08:02
Same here!!!!!! You're right it's tiresome talking to support and they play it off as there are no issues. When I mention the fitbit community still go clueless. I agree by end of month fix it or remove this section until you have accurate graphics and data
08-04-2022 08:06
08-04-2022 08:06
It's August 4th and still no fix. Any estimated time on when the EOV will be working? This is I e of the main reasons I bought a fitbit.
08-04-2022
08:15
- last edited on
08-04-2022
11:07
by
LizzyFitbit
08-04-2022
08:15
- last edited on
08-04-2022
11:07
by
LizzyFitbit
Lizzie still waiting........some type of communication please
Moderator Edit: Formatting
08-04-2022 08:24
08-04-2022 08:24
Absolutely clueless! How do you work for Fitbit and you don't know about this page?
08-04-2022 08:38
08-04-2022 08:38
Exactly what I asked and surprise surprise Andy griffin.....no answer back
08-04-2022 09:25
08-04-2022 09:25
Ok gang - I just spoke to Sharon at Fitbit. She was very patient with me and even walked me through how to do a screen shot (ha-ha on me) of my graph. I sent it to her with the explanation that now all my EOV graphs dating back to June look like that even though they were all green before. I explained it was not just me. (I also asked her to look at her sleep score and graph) She told me that Fitbit is aware of the situation and working on it. She said on July 28th (?) Fitbit did acknowledge the issue on the community thread? I think that is what she said. Did anyone catch that?
So hopefully they are aware and are working on it - that's all I needed to know - aware and working on it
08-04-2022 09:54
08-04-2022 09:54
I think that this link was posted up yesterday - it is worth repeating though! 😀
08-04-2022 09:56
08-04-2022 09:56
Check the link to the best answer above.That would be Lizzie's answer of 28 July.
08-04-2022
10:40
- last edited on
06-07-2024
10:55
by
MarreFitbit
08-04-2022
10:40
- last edited on
06-07-2024
10:55
by
MarreFitbit
Hello everyone!
I appreciate your feedback and your patience regarding the oxygen variation graph. We have gotten confirmation, that chart Improvements for the estimated oxygen variation and weight trends charts will be available in a new release this month. Keep the app updated to receive the latest changes/improvements.
08-04-2022 10:58
08-04-2022 10:58
Great news! Glad to hear!
Since this has been an issue for a couple weeks, and won't be fixed immediately, will we all receive a month's credit on our subscriptions?
08-04-2022 11:06
08-04-2022 11:06
I use a CPAP and I'm very concerned about the results it has started showing for oxygen saturation.
Is this accurate? What are the scales on these graphs?
08-04-2022 11:11 - edited 08-04-2022 20:46
08-04-2022 11:11 - edited 08-04-2022 20:46
In response to Lizzy moderator saying fix ETA by EOM...At last ... 2 mos. Later! Really#.@#! and no offer of rollback pending another mo. before update? Pl. Lizzy - Tell them to thoroughly test! Since I had to jump thru hoops to roll back to a previous Jul 12 22 software rev I removed update permissions to try to keep it from updating to ur buggy release. Pl. advise WHEN exactly it releases in order to update. Can you tell us what the prob l m is/was?
08-04-2022 11:26
08-04-2022 11:26
Hopefully Fitbit can open up an update to the Sp02 levels chart to make some understanding. Obviously they have reworked the presentation and where high variation used to cross the upper line, now high variation is only a tiny bit higher and the base rate. I also have a concern that my Charge 4 pebble has been replaced and previously I would see flat line sections but now I am seeing almost as much flat line as data. If the flat line is representing times where the pebble is unable to report SpO2, then I need to immediately file a request for another pebble replacement. We also need to understand how to interpret the new chart and what amount of variation is deemed as high variation and what the top of the chart translates too.
08-04-2022
11:32
- last edited on
08-04-2022
11:43
by
RodrigoMFitbit
08-04-2022
11:32
- last edited on
08-04-2022
11:43
by
RodrigoMFitbit
Unlikley. Fitbit has a pattern of not handling SpO2 well and keeping users in the dark. It is already 3 weeks and nothing.
Noted that Fitbit is aware. My question is why push out an update that is obviously flawed and makes the SpO2 interpretation even more unusable. Why will Fitbit not actually tell users what the chart does and why does Fitbit block access to REAL SpO2 measurements. I also ask why the chart has so many flatline areas. What gives? Is zero variation averaged into the single value reported as a zero? Do the programmers not actually test or use the beta code or does fitbit think that the user community should do all the quality testing?
08-04-2022 11:35
08-04-2022 11:35
Thanx for your reply, its totally confused me l wish Fitbit had just left it alone tbh.
08-04-2022 11:42
08-04-2022 11:42
This! its a problem that needs resolve ASAP!
08-04-2022 11:43
08-04-2022 11:43
Is this still broken? When do we expect a fix?
08-04-2022 11:55
08-04-2022 11:55
And guarantee the hopefully fixed release will be advertised totally as "even more improvements to charts" with no mention of this failure.
08-04-2022 12:00
08-04-2022 12:00
To me the quick solution is to roll back to a previous version and then work on solving the issue. Instead of making customers wait and have to deal with the bug day after day. smh