sleep questions... new user

[fieldstone]

Hi All!

I clicked on "log sleep" and I only see the "simplified sleep" data. Whereas the day before (I've only had it for 2 days 🙂 I saw the full data set included deep sleep and REM. 

What is the purpose of using clicking on "log sleep"?

Should I assume that Fitbit will create the full sleep data set if I don't click "log sleep"

How long after I wake up does Fitbit create the Sleep timeline if I don't click on "log sleep"?

Can the "log sleep" be undone to see the full sleep data including REM?

thanks in advance.

[JohnnyRow]

Usually there is no need to use "log sleep".  Just let fitbit detect and log sleep on its own with no intervention on your part.  It usually posts it fairly soon after you wake, but if not, just give it some time.  "Log sleep" I guess could be useful if you didn't wear your fitbit at night.  I don't know how that affects sleep stages as I never use it.
Also about sleep, note if you take daytime naps, less than 3 hours, you generally won't get sleep stages.  And less than 1 hour, sleep will not be detected.  In that case, if you want to get credit for that sleep time, you could use 'log sleep' for that, or at the start you could use 'begin sleep', then 'I'm awake' when you waken.

[fieldstone]

Thanks for the reply.

After searching the forum, it appears that some people are getting the "simplified sleep" results after upgrading the firmware, which is just the Awake, Restless and Asleep info, but not the REM, deep and light sleep parts. So, now I'm wondering if the incomplete sleep information is due to the tracker not positioned correctly and not getting all the tests to complete the sleep report or if the new firmware which was updated yesterday is the problem?

thanks again,

[JohnnyRow]

Just a personal opinion here: search the forums enough and you're always going to find people blaming the latest update for any problem. Sometimes it might be true. But in your case, since it's only been one night, and you've got a simple solution that it might be caused by using "log sleep", I see no reason to be searching for reasons to jump on the bandwagon to blame Fitbit's update before even trying an easy other solution first.  Besides, there's an occasion night when you just might not get sleep stages with no obvious reason.  That doesn't necessarily mean that fitbit has just taken that away, as many people immediately jump to the conclusion.  It might just go away for a night and then come right back if your band happened to slip on your wrist or such.  It doesn't necessarily mean the sky is falling.

[fieldstone]

Hi Johnny

Thanks for the reply...  no worries I'm not panicking, just learning 🙂

> you've got a simple solution that it might be caused by using "log sleep", I see no reason to be searching for reasons

Does using "log sleep" only create a simplified sleep report? 

[fieldstone]

update:

Sleep was correctly reported. Rules out the firmware and leaves 2 likely candidates:

1. tracker was not positioned correctly

2. clicking on log sleep?

~ since sleep relies upon 24 hours of data for some of the metrics there's an outside chance the firmware reboot misplaced some data?

but in all cases, I love the new Inspire 3 it a fantastic tracker and has all the bells and whistles that I need... and that looooong battery life.