help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Heart rate tile not showing heart rate graph line

Replies are disabled for this topic. Start a new one or visit our Help Center.

‎01-10-2024 09:38 - last edited on ‎01-16-2024 11:05 by Fitbit Moderator

‎01-10-2024 09:38 - last edited on ‎01-16-2024 11:05 by Fitbit Moderator

I started using my Fitbit Sense 2 only a week ago, and after I charged it for the second time, the line connecting the dots in the heart rate tile is not showing. I can only see the dotted lines representing the maximum and minimum heart rate values but not the line showing all the continuous measurements for the last two hours.20240110_181357.jpg

Surprisingly, when I sync with the app, the app shows the heart rate graph correctly. However, the watch has stopped showing it correctly! Any suggestions? I have tried removing the device from the app and syncing again, changing all the setting options I saw, removing the tile from the app, and installing it again... Nothing works 😞

Thank you in advance!

----

I have this exact problem.

i got the watch just 2 months ago. The graph used to work, but not recently.

----

I fixed this by updating the software from the app.

Best Answer
0 REPLIES 0