FItbit not tracking sleep

[XhibitA]

I received the Fitbit Blaze for X-Mas this year and all has seemingly been well aside from the sleep tracking. Since this past Sunday the 25th I have only gotten 5.99 hours of sleep? The Version number for the Fitbit is: 17.8.301.8. I sync with the Google Pixel which appears to work just fine and the data between the phone and the website is spot on. I have reset the device and modified the sensitivity of the sleep tracker and still it only seems to pickup on an hour or two of sleep throughout an 6+ hour night of sleep. Does anyone else have this issue? I read online about a few folks having the issues and tried their fixes but it has not worked for me.

[FerdinandFitbit]

What a nice Christmas present! 😄 I'm glad to hear that everything else seems to be working fine!

Now, when it comes to the sleep part, the sleep tracking feature on your Blaze works based on autodetection which is based on your movement. When you haven’t moved in over an hour, algorithms assume that sleep has begun, which is confirmed by the length of time your movements are indicative of sleep behavior only (rolling over, etc). Morning movement tells your tracker that you’re awake.

This means that if you go to sleep but move a lot or don't stay still for over an hour, that time will most likely not be tracked as time asleep. Keep an eye on this as this could be a reason why you're not getting enough hours. Also, do you by any chance wake up and get up from bed at night? Do you see any interruption on your sleep record? These are things to consider as well.

Putting your tracker in Sensitive mode was a great call so keep an eye on it after checking the things I advised about above and see how it goes.

If you need more help with this, let me know. I'll be happy to help! Welcome to the Community Forums @XhibitA! 🙂

[XhibitA]

Good morning and thank you for the welcome Ferdin,

I understand your feedback and have chatted with other reps regarding the issue and have been given a bunch of excuses. Please allow me to provide you a visual as to the problem. Below are two images; one from when I used the Fitbit One and one of the past four days I have had the Fitbit Blaze.

                                                                                       

Notice the huge difference in the way they track sleep? The Fitbit One appears to actually track data whereas the Blaze provides little to no data. Last night it logged me sleeping 24 minutes and a total of just over 7 hours of sleep in the past four days.

I have had Fitbit reps tell me this is due to the way the algorthim was written. If this is true then you can see where the problem lies. What is the difference between the algorithm written for the Fitbit One and the Fitbit Blaze? If the alorithm is not device specific then I would suggest rolling it back as there were some design flaws implemented into it which ruined what was previously working.

Intrurruptions during my sleep cycle never used to matter with the Fitbit One, it still tracked them and the entire sleep cycle. I was told by another Fitbit rep to pay attention to how much I move when I sleep because this is causing the issue......Since I am obviously sleeping and unaware at this time I find this to be a suggestion said with ill humor.

Another rep told me to adjust the sensitivity of the tracker which had no positive results. I have been told to reset my device with almost every interaction with Fitbit support, even if I said I have reset it before by pressing and holding the left button and the lower right buttom for 10 seconds until it reboots. The typical response to this is try it for 20 seconds....try it for 30 seconds as if this is going to accomplish more than the last however many seconds it took to reboot the device.

Basically all I have been getting are excuses and no answers. I am not the only ne with the issue as you can perform a Google search on simple terms such as: "Blaze not sleep tracking" and you get a number of hits.

I would like someone to acknowledge that this is a device problem and not a problem with how I am sleeping or how long I am holding a button to reset the device. I received this as a gift and it simply infuriates me that it does not perform as advertised. I would be more livid if I had actually paid for the device.

Thank you.

[John_R]

I'm having the same problem but I have not called anyone about it yet.  I have had my Blaze only for 3 weeks now.  Have you been able to fix your problem?

[XhibitA]

Good afternoon,

After a few week I believe the tracker did start show more measurable results however it is still logging me with an average of 1.5 - 2.5 hours a night of sleep which is still inacurate as this amount of sleep would be detrimental to anyone's health. Below is a screen shot you can compare to the one  I previously listed above which does show that I am sleeping more overall but it is not tracking the actual sleep because of all the restlessness and some of the days are still hardly tracking sleep at all.

This is a known issue with the Blaze as I know personally that peers of mine are experiencing the same issue. It is sad that I have received nothing else from fitbit in regards to all the data I presented them with thus far.

So to answer your question directly, no, unfortunately the issue is still present. 

[Rich_Laue]

@XhibitA what mode do you have your sleep set for, normal or sensative? 

In sensative, it will say that during any movement of the arm that you are awake. This is really helpful when you want to know how much you move durring the night, but it will not show a true record of your sleep.

Normally the Blaze looks at the heart rate to determine sleep, in sensative it looks at arm motions to determine when you are moving around in the bed. No heart rate is monitored. 

I'm not saying this is the case, but the screen shot sure points to it.

[XhibitA]

@Rich_Laue, you do bring up a good point! During the initial troubleshooting of the tracking issue fitbit support had me set it to Sensitive. I have not adjusted it since then and since it is tracking more reliably now, that may just have an effect. I will change the setting tonight and report back if this fixes the issue. 

[John_R]

This might help and please let me know if it does.  Yesterday I changed my time setting on my dashboard to use the 24 hours in a day not 12.  To do that go to Setting - Personal Info - Clock Display Time - change the 12 to 24 and save.  I also set my sleep Sensitivity to Normal.  It track last night that I got 6 hr & 43 min and that is a lot closer then 3 hr or less it was tracking.

[XhibitA]

@Rich_Laue, So adjusting the sensitivity did help...I completely forgot about setting that to sensitive:

Granted it still is not as acurate as the previous Fitbit devices I have used. You can blatently see when I toggled the sensitivity so you did bring up a good point. It is tracking better but then this weekend ended with Sunday and Monday both being inacurate. I think we are getting somewhere though for sure. Thanks for the reminder on the sensitivity setting! There still appears to be an issue as I get an AVG of 7 hours of sleep per night and even with the sensitivity changed it misrepresents my down time.

[XhibitA]

Thanks @John_R I have edited the sensitivity per a previous statement (That was my bad, I forgot to reset it after talking to support) but I have not modified the clock. This seems odd and illogical to me but for testing purposes I will do it and report back after a few days. Changing the sensitivity has gotten me closer to what I used to read with the Fitbit One but it is still not 100%. Thank you for the feedback I will keep you posted!

Clock changed as of now 🙂