Home > Tips and Tricks

Fitbit Charge 5 not tracking sleep & heart rate: How to Fix

In this guide, we will show you the steps to fix the issue of Fitbit Charge 5 not tracking sleep & heart rate. When it comes to health and fitness trackers, then there are a slew of names in this domain. However, even then, it is the offering from Fitbit that has managed to grab much of the limelight. In this regard, its Charge 5 beholds a slew of noteworthy features.

Fitbit Charge 5 not tracking sleep

From the basics measurement of Calories Burned, Distance, and Steps to the advanced ECG app for your heart & an EDA sensor for your stress, there’s a lot to look forward to. However, in spite of all the goodies involved, it isn’t free from its fair share of issues either. As of now, various users have voiced their concern that their Fitbit Charge 5 is not tracking their sleep & heart rate.

Fitbit Charge 5 not tracking sleep

If we talk about the former, then it ether straightaway doesn’t start recording or only records once you have slept for around 5-6 hours. Likewise, the watch also randomly quits heartbeat recording without any prior alert. And it goes without saying that both these bugs are causing a great deal of inconvenience to the end-users. If you are also in the same boat, then this guide shall help you out. Follow along.

Fix Fitbit Charge 5 not tracking sleep & heart rate

Fitbit Charge 5 not tracking sleep

  1. To begin with, head over to the Settings menu.
  2. Then scroll down a little bit and select Restart Device.
  3. After that, tap on the blue Restart button.Fitbit Charge 5 not tracking sleep
  4. Your watch will now restart and the process will take around 30-45 seconds.
  5. Once it boots up, the underlying issue would be rectified.

So these were the steps to fix the issue of Fitbit Charge 5 not tracking sleep & heart rate. Do note that it is a temporary workaround and the issue might re-appear after a few hours. So you will then have to perform the above-listed steps once again to fix this issue. While in no way it is the most viable approach but as of now, it is the only way out.

As far as the official stance on this matter is concerned, the developers are yet to acknowledge this issue, let alone give out any ETA for the rollout of a fix. As and when any of these two things happen, we will update this guide accordingly. In the meantime, the aforementioned workaround is your best bet.


Share: