Sleep stages for Blaze

[nursejoyt]

I have a Fitbit Blaze and the help section states it should show me my sleep stages, for example, light sleep, deep sleep, and REM.  My app and dashboard are not showing me this information.  It is only showing me time asleep, time restless, and time awake.  Where do I go to see my sleep stages?  I have had my Blaze for a year now and it has never shown my sleep stages.

Thank you.

[Squapan42]

Texted customer support. They took my information then texted me back a couple hours later. Said they had fwd'd my info to their engineers and for me to be patient while they work on a fix.

Sent from secret places

[DeinGesicht]

---

@Norb0807 wrote:

I reviewed the postings and answer from the moderator.  The Blaze has worked fine with posting my sleep until last night - and this morning there was nothing posted.  And because it did not post my sleep last night I am unable to view the sleep details prior to yesterday.  And yes, I slept more than 3 hours - I was in bed around 10pm and got up at 5am.  The battery was fully charged when I went to bed and I did not sleep any different than any other night.  Please fix the issue sooner than later.

---

Mine didn't work overnight, I woke up at 7.30 then went back to sleep for about 3 hours - and THEN it recorded stages. So I've around 5hrs old style, 3 with sleep stages. No pattern or logic to it that I can see at all. I just turned off battery optimisation on my xperia xz for fitbit, you never know 😕 

[DeinGesicht]

PS, I didn't "start sleep" on the app, it auto detected those 3 hours...

[Mazco]

I totally agree with you. It is clearly a problem but no one from Fitbit will admit this. I have been in contact with their support and been told to jump through all the hopes you talk about.

My Blaze needs charging /wearing in a different place /rebooting etc etc. 

This morning I was told in an email that the problem is caused by me lying on my arm at some time during the night. 

I now have to lie awake all night checking that I'm not lying on my arm in order for my tracker to track my sleep. 

I would suggest that if sleep tracking will only work for people who play completely still, on their back all night, it doesn't work!

[Tommy10]

Absolutely Fitbit problem. My sleep stages are now working last 2 nights doing everything wrong e.g. Loose on my wrist, when it didn't tight on my wrist 3 & 4 nights ago.
Suck it up Fitbit -- NOT YOUR CUSTOMERS' PROBLEM!!!😇😇😇
Tommy10

Sent from my iPhone

[Scarchin]

This is where I think we are (especially for folks new to this thread).
Fitbit clearly rushed this out to coincide to the launch of the Alta HR.
If you have a Fitbit and Sleepstages is not working (which is my situation with a Charge 2), I would not waste one minute of your time right now trying to get it "fixed" etc.
They clearly released this knowing that there would be glitches but that the promoting of the Alta (and the heavy media PR involved) was worth irritating existing owners for a few months.
Let's face it - Sleep Stages is a bonus that did not exist when we purchased our devices, so getting mad over an upgrade that is taking time is a waste of energy.
I say hold on until late summer before this gets sorted out.
If the moderator is reading this, here is my recommendation for you to pass a long - a free year of Premium (and extended subscriptions to folks who are Premium members now) to current users who were told that something would happen that didn't. I think that's a fair exchange that basically costs Fitbit very little in proportion to the good will it would maintain.

[Squapan42]

How about new Blaze owners? Mine was purchased 4/5/17 and sleep stages was a feature that influenced my decision to buy the product. And it has worked only one day since purchase.

Sent from the wood shed

[Scarchin]

In your case, I would either just return it now or contact Fitbit and tell them that they need to fix this within a week (I'm assuming you have 30 days to return it) or that you will be returning the device.

[CSimoneJ]

I had the same issues with sleep stages all last week.  Did all the recommendations:

log out of App

Restart the Blaze

wear tighter

wear it higher on the wrist

etc:

2 nights ago I did NOT hit the "begin sleep log" and I got the sleep stages.  Did the same thing last night and I got them again.  I don't know if it's fixed but I will be curious if some of you do the same thing and see If it works for you.

[Tommy10]

Couldn't agree more! For a company that is trying hard to become a social networking site to put frustrated existing customers through ridiculous time wasting hoops when they should instruct their technical support people to say, "Our problem -- give us a few weeks/months to get this sorted out." is corporate stupidity!

Folks are having problems intermittently with the sleep stages regardless of the device or what they're doing.

Tommy10

[Avi13]

Can you please clarify? My Fitbit charge 2 recently got updated and my app shows sleep stages but there is not data showing up. Will this be added soon? Seems strange to show me that sleep stage data is possible but then not get that data. Thanks! 

[FerdinandFitbit]

Hi there everyone! I'm glad to see you all in the Community Forums! 🙂

I'd just like to jump in and clarify a few things.

-Sleep Stages seem not to be working for everyone yet or to be working intermittently. Our team is already aware of this and working hard to get it all working properly.

-For some Charge 2 users, Sleep Stages has not been rolled out to all of them so it can be working for some and not working for some others and instead, you'll see the old sleep pattern log.

-If you were previously starting your sleep in the app, don't do it if you'd like to see Sleep Stages instead of the regular old Sleep Pattern. If you start it on the app, you will not see Sleep Stages for that night and even if you log your sleep manually, Sleep Stages will not appear if it was not recorded from your tracker directly.

Thank you all for your patience with this and any other thing you may need, let me know!

[jknight]

I have never had to hit a sleep log button!  i works now, but didn't in the beginning of this new sleep log sleep stage graph.  Again, it is their program, they need to get it figured out, work thru the bugs and we have to wait while this happens.  Frustrating, not a good working model for a business, but sooner or later they should get this worked out so no one is having these problems.

[jknight]

I am a restless sleeper, I do not wear the fit bit Blaze tight,  It didn't want to work at first but now it is.  thing I notice is people are being told to start sleep stage tracking at bed time?  I have never had to do anything but put the watch on after I charge it and that is it.  I sync it and after a few weeks of off and on sleep phase tracking not showing up, I now have had consistent ability to see my sleep phases after syncing in the morning.  It isn't the watch/tracker, it is the programming, i.e. the fit bit techs need to work this out.  Not sure why some watches/trackers are showing for some folks and other's not.  I did once, restart the blaze, and also got the latest firmware.  That didn't help the sleep stage issue.  At least not right at first.  Whatever corrected the issue for me,I still believe is a programming issue, not how you sleep, nor how tight your band is.

Moderator edit: Word choice

[Starkman78]

I have a Charge 2 and still no sleep stages.

[Squapan42]

Think you are probably right

Sent from the wood shed

[PodPa]

any updates as to when the Fitbit blaze will be adding the sleep stages?

[TroyJ]

I had issues initially, but none for the last 10 days. I make sure to allow it to sync before I open the sleep portion of the app.

Get Outlook for iOS

[DeinGesicht]

The only way I've been able to get a full night's reading is to NOT click 'start sleep' in the app.  I've been letting it auto-detect for the past three nights and it's worked.  Not to say it won't stop working again, but it's the only luck i've had with it so far. 

---

[Mazco]

We tried this last night and it worked. Well keep going and see if that was a one off or if it has  solved the problem