10-17-2020 04:40
10-17-2020 04:40
I always switch to the rather boring spO2 clockface before going to bed in order for that function to work (Duh!), but I always notice that when I get up around 7:00 AM, that only then mu device is saying "Recording spO2". Why is it not measured and recorded sometime during sleep?
10-17-2020 05:20
10-17-2020 05:20
It doesn't start recording until it detects you have fallen asleep. I see the same thing with mine: it still says "Recording" when I wake up in the morning. This eventually is replaced with the reading - on good days, at least, sometimes it doesn't work at all, but that's a bug.
If you wake up in the middles of the night, it should say "Recording".
12-26-2020 08:39
12-26-2020 08:39
This is happening to me, too, albeit on my Versa 2. I feel like it's frozen/hung. Because I go into the Fitbit app on my phone, to try to change the face back to my regular one (app>profile>Versa2), and it's just a blank white screen.
It takes an hour or two after I wake up and notice it, but it eventually unfreezes and displays "Last night's range" instead of "Recording SpO2."
12-27-2020 11:28
12-27-2020 11:28
Same here. Usually takes 2+ hours for mine after I wake up for the reading to show on my Sense instead of it saying it is still recording the data. It makes me a bit wary on the days when I wake up and need to charge it before I head out or something as sometimes my sleep data isn't showing up properly everywhere either, regardless of how many times I try syncing. Like today the app on my phone had the hours I slept but when I went to check for more information it showed nothing logged at all - not even the hours. Also, nothing showed up on the dashboard on my laptop either. Nothing on the Sense too. It sometimes won't log everything until the SpO2 reading shows up on the watch face as opposed to seeing the "Recording SpO2" message.
If this is a bug - which I believe it is, as it shouldn't take this long at all after waking up to record the data, and even without SpO2 logged in the rest of the sleep data should still be visible everywhere else one would think - or maybe it is preventing the sleep data from fully syncing altogether - I hope it gets fixed soon.
12-27-2020 21:47
12-27-2020 21:47
@WehuttyWanker it takes some time for the SpO2 to get calculated and displayed back on the clockface. SpO2 is only measured during sleep. Same as temperature, breathing rate and HRV.
12-28-2020 11:10
12-28-2020 11:10
@Marrrmaduke okay that explains the clockface issue and calculating, but regardless of whether it has SpO2 data calculations finished or not, if the Sense is synced with the app and the dashboard, shouldn't the rest of the sleep data still show up anyway or is it holding off on calculating that as well until the SpO2 data is finished calculating as well?
And does that mean you need to continue to wear the watch while it is calculating or can you remove it for charging, etc. and allow it to continue the calculations while off-wrist if the sleep data, including SpO2, still isn't filled in yet and doesn't seem to do so until the SpO2 finishes and shows up on the watchface?
12-28-2020 13:54
12-28-2020 13:54
@sarcazm no, you don't need to wear it for the calculations and sync is both ways. So - I wake up, Sense registers I woke up, gathers sleep and SpO2 and other sensors data, sync with app, app syncs to the cloud where calculations happen, calculated results sync back to app and via app back to your sense. More or less.
12-29-2020 04:54
12-29-2020 04:54
I
I have found if I restart the watch by depressing the button for 10 seconds or so just after waking up, the SpO2 number shows up on the watch face immediately and app too.
I do this when I am impatient and want the number right away.
I use the face below
06-22-2022 05:35
06-22-2022 05:35
I purchased my Fitbit Sense on Sunday, June 19th. The oxygen recording was still recording when I woke up. The basic troubleshooting step that I took was to restart the Fitbit and it loaded right after I rebooted the device.
07-09-2023 06:19
07-09-2023 06:19
Thank you. This really worked.