Blaze not recording heart rate or sleep correctly

[dgwalsh]

Hi, my Blaze was working great for about a year, but suddenly something changed. It is now unable to consistently track my heart rate (the resting HR is stuck at a number which is inaccurate, I think).  Also sleep details are not showing up anymore.  When I looked in to the reasons given via the app, none of them fit well.  I have double-checked to ensure my sensors are clean/clear of any dirt, debris etc. and that isn't the issue.  I also am not wearing the device any differently. 

The step counts, tracking during exercise (used for running), and most other activities seem to be OK. I'm not positive on the HR during exercise but I'm not too concerned about that.  Could it be that the device is just starting to wear down and get old prematurely?

Any suggestions???

Moderator edit: Updated title for clarity

[FerdinandFitbit]

Hi there @dgwalsh, welcome to the Fitbit Community Forums! 🙂

I'm sorry to hear that you're having problems getting your Blaze to record your heart rate and sleep correctly. Thanks a lot for all that you've tried to get it to work. I'd like to help you out.

Now, sleep and heart rate, both work together. In order for your Blaze to record your sleep, it needs to have a reliable heart rate reading. If your heart rate is not being recorded correctly, most likely, your sleep will not be recorded properly either.

Have you tried by any chance to restart your tracker and see if this makes any difference? If not, you can easily do this by pressing the left and lower right buttons for 10-12 seconds. This will make your tracker to reboot. After this, check and see if the lights on the heart rate monitor work correctly and see if your heart rate is being recorded more accurately.

Hope this helps. Let me know if you need more help!

[NeilJB]

I’m having the same issue as user dgwalsh whereby heart rate is stuck at 70 and sleep patterns are no longer be recorded. 

Ive restarted the device by both the holding the buttons down and the shutdown feature. 

This has been an issue since Wednesday 6th March when Fitbit version 2.89 was installed. 

How can this issue be resolved by a new update or the version be uninstalled?

many thanks,

neil

[NeilJB]

@dgwalsh - did you ever get your Fitbit issue resolved, and if so how?

many thanks,

neil