06-28-2021
06:13
- last edited on
06-29-2021
16:10
by
SilviaFitbit
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

06-28-2021
06:13
- last edited on
06-29-2021
16:10
by
SilviaFitbit
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
Update broke my Versa 2, most of the health metric stuff no longer works and the sleep tracking is back to basic
Moderator Edit: Clarified subject
06-29-2021 16:09
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



06-29-2021 16:09
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
@ShariRfit Welcome to the Fitbit Community. Thanks for the details mentioned.
I'd like you to double check the following information on why you might not see your health metrics data:
- Wear your device for at least 1 full day (during the day and to sleep at night). Check your stats after you wake up in the morning. Note: skin temperature requires 3 nights of data.
- Make sure the back of your device is in contact with your skin. The band should be snug but not constricting. If you experience any discomfort, loosen the band, and if it persists give your wrist a break by taking it off.
- Most metrics require at least 3 hours of quality sleep. If you move a lot during your sleep or the sleep session is too short, you might not get a reading.
- To track your blood oxygen saturation, confirm you have an SpO2 clock face installed (available on Ionic, Sense, and Versa series) or the SpO2 app (available on Sense and Versa 3). For more information, see How do I track blood oxygen saturation (SpO2) with my Fitbit device?
In regards to the sleep tracking, let me know how many days you've received sleep patterns instead of sleep stages.
Hope this helps.
Want to get more active? Visit Get Moving in the Lifestyle Discussion Forum.

06-30-2021 01:24
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

06-30-2021 01:24
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
It was an update glitch that is fixed now
