Fitbit EOV Acting Weird Again

[n8vz]

For the last three days my Versa 3 has been showing periods of high EOV after a week of no high EOV readings. However, this makes no sense, since each time my SpO2 is reported by my Fitbit as being in a high and acceptable sleeping range.  For instance, last night the range was 94 to 98, with an average of 95. The only explanation that I can think of is that the EOV graph algorithm is responding to a rapid drop or rise within that acceptable range.  But that would be an artifact and not an actual indication of a desaturation of clinical significance.  To me this points to the need for further refinement of the EOV algorithm by Fitbit firmware and/or software engineers. Anyone think otherwise?

[n8vz]

Same thing happened last night.  The SpO2 average was 97 and the range was 96 to 100%.  Something is wrong with this EOV graph.  Time for Fitbit to remove this feature until they fix their algorithm.

[abdul2961]

Please update the Fitbit app has been fixed.... Also the graph shows variations during sleep not the actual percentage

[n8vz]

I believe I have the latest software and firmware updates, unless there are new ones in the last two weeks.  The last one I processed said it fixed EOV, but it obviously didn’t.  

You miss the point about the graph.  High variations are supposed to indicate potential breathing problems and the possibility of sleep apnea, which requires desaturations below 90 percent while sleeping.  Obviously with the range I posted, I’m not experience that level of desaturation. In fact, the indicated range is not that great at all, so the high EOV being indicated must be wildly inaccurate.  Either that or the SpO2 reading and indicated range are wrong.  They can’t both be correct. 

[n8vz]

Now I have a different problem. For the last two weeks every night the EOV graph is flatlined.  The graph is so useless this doesn’t really bother me, but it is weird.  All other stats are gathered as per normal, including SpO2.