09-15-2020 09:19
09-15-2020 09:19
I was happy to see the new clock face.... it loaded... I went to sleep. Woke up to: "Couldn't read spo2"
Sigh. If it's that the watch has to be tighter, that's not really possible after years of having a fitbit, I know how tight I can wear it and still sleep. Any other thoughts? TIA
09-15-2020 09:49
09-15-2020 09:49
@RED123 It could be a glitch. I'd try wearing it again to bed tonight to see if you get a reading tomorrow. I think a few people might be reporting this, so just hang tight and hopefully tomorrow you get a value. 🙂
09-15-2020 22:14
09-15-2020 22:14
I just installed it as well and it's not picking up my SpO2 either. I have seen a lot of people having this issue.
09-16-2020 11:36 - edited 09-20-2020 06:16
09-16-2020 11:36 - edited 09-20-2020 06:16
This affects me, too. I installed the clock face two days ago. Yesterday it said it couldn't read the Spo2 data. I checked I had the most recent firmware, check. I checked all permissions, check. I rebooted my device. The second night the same thing, no data. I am wearing my monitor tight and slightly above my wrist. I've gone through the manual to see if there is anything I'm missing. I have a Versa 2. I'd very much like to be able to use this data. Thanks for you help.
09-17-2020 08:39
09-17-2020 08:39
Me again. Still wake up every morning to "couldn't read SPO2" - this is really disappointing, poorly executed. I can accept the limitations of fitbit (long wearing user, habit is a powerful thing) but it really chaps my hide when they promise something new and exciting that isn't actually real.
09-19-2020 06:11
09-19-2020 06:11
Same issue for me. Very frustrating!!
09-24-2020 04:49
09-24-2020 04:49
Sorry guys. It happens to me in the same way as you all mentioned. I read that you have to make sure that spo2 is selected during the sleep not other metric faces. I'll give that a try.
09-25-2020 08:07
09-25-2020 08:07
So in addition to logging out, uninstalling and reinstalling, I tried making sure the SPO2 face was selected while I slept and am now getting the data... so I'm not sure which one worked, but it's there now.
09-25-2020 08:46
09-25-2020 08:46
You mention uninstall/reinstall, which I assume to mean the new SPo2 feature. Can you describe how to do that?
09-25-2020 08:56
09-25-2020 08:56
Sure, this is exactly what fitbit support asked me to do
But like I said I have no idea if that's what got it to load or if it was making sure the SPO2 face was selected before I went to sleep.
Also, as a side note, I do not allow Fitbit to access my contacts, because I feel that's just a little intrusive. But I did turn on the other permissions that I had previously shut off. Good luck!
09-25-2020 12:40
09-25-2020 12:40
It won't work unless you have the SP02 face selected when you go to bed. And in the morning sometimes I have to wait an hour or two until I finally see the reading. After that I switch back to my favorite face.
09-30-2020 15:39
09-30-2020 15:39
Me too, plus I had that right tile on the face.
Hate to say it, and have had Fitbit for years, but am starting to think of the Series 6 in the other watch ...
10-21-2020 19:46
10-21-2020 19:46
Mine worked for quite some time, since it first became available. Then out of the blue, about four days ago, it just stopped reading. Made sure the Spo2 face was selected at bedtime, deleted the app and reinstalled it, and still not reading. A bit frustrated at this point.
10-23-2020 08:53
10-23-2020 08:53
I’m having issues too. Some days I get an Sp02 reading, other days I get ‘sleep to update’ message with no Sp02 value. Can’t figure out why. Sp02 clock face always on. I have had no readings when I only slept 4 hours. Thought perhaps that was it but since then I have gotten readings when I slept 3 1/2 hours. Last night I got 5 hours and 45 minutes sleep and no readings.
Maybe battery. It was at 30% when I got up this morning.
10-30-2020 12:36
10-30-2020 12:36
I have this same problem too. What is the fix???
01-13-2021 18:07
01-13-2021 18:07
What is the point of this forum?? So many of us with the same problem but no fix?? I"m even more confused.
01-13-2021 18:13
01-13-2021 18:13