Detected sleep interval is hours past bedtime.

[Dave_Demase]

I have my Sleep Bedtime set for 10:30pm and wake set for 7:30am in the Settings. Yet, automatic Sleep Detection seems to break up my sleep graphs into two time frames; one before midnight (although not right at 12:am) and one after midnight. I would want to have a single Sleep Graph and Analysis for the entire sleep session starting at 10:30pm to 7:30am. How can this be done on the Versa?

[Marrrmaduke]

@Dave_Demase Versa will post sleep stages only for the sleep it detected automatically and not the time you usually go to bed. Can you post some screenshots of the sleep recordings from your Fitbit mobile app? Also, double check that your Sleep Sensitivity setting is not set to sensitive but to normal. This can cause such fragmentation. The sleep sensitivity setting can be accessed only via Account settings on Fitbit.com. You cannot change it in your Fitbit mobile app.

[Dave_Demase]

Thanks for the reply.

1. I checked the sleep sensitivity on the web site config, and it is set to normal.

2. I have taken a screen shot, shown below, of some sleep recordings:

I accidentally deleted the "companion" session to the one for Today 12:21am - 7:23am. This was my attempt to clear out what appeared to be duplicate entries in this screen. You'll see those as you go through the screen grab, and I don't know what is causing the duplicate records at this point. There was previously a "companion" session labeled Wed that started around 10:30pm and went till near midnight, that later continued with the Today session.

The two entries labeled Tue & Wed are actually one sleep session across midnight.  I'll be checking again in the morning tomorrow what gets recorded and posted.

[Marrrmaduke · Accepted solution]

@Dave_Demase Try clearing your presets for bed times. Just delete them, log out of the app, log back in and sync your tracker. Then let's see if Versa still splits the sleep. Perhaps there's a bug that causes it to get confused after the sleep times are pre-defined.

[SunsetRunner]

Mine seems to be doing the same thing over the past few days. and funny thing, I had my Fitbit charging last night but still detected a sleep pattern 🤔

[Marrrmaduke]

@SunsetRunner Which firmware version are you running? Did it start after the 3.0 update?

[SunsetRunner]

@Marrrmaduke Hi I’m using 33.1.30 and yes I believe it happened after the update. I also just realized it didn’t detect any sleep pattern from the 20th to the 23rd. 

[Marrrmaduke]

@SunsetRunner Can you verify for me that heart rate was recorded properly? Can you please post the screenshots of HR recordings from your Fitbit mobile app? 

[SunsetRunner]

@Marrrmaduke Yes it detected my heart rate

[Marrrmaduke]

@SunsetRunner yes, your HR is fine. Would you happen to have bedtime set up like @Dave_Demase? If yes try clearing it and syncing your Versa. The last resort is a factory reset (restoring Versa to factory defaults) but it's a hassle as will require setting up Versa from scratch.

[Dave_Demase]

I'm a newbie with the Fitbit replacing my MS Band as of Monday this week. I did the Versa firmware upgrade out of the box this past Monday night, but didn't wear the watch to bed that night. I'm at 32.33.1.30 firmware now.

A couple of new observations for you:

I had been fiddling around with the Sleep Schedule Times earlier in the week, however I have not touched them in the past 24-35 hours. Last night I got a good and expected Sleep Graph and time interval (single session). So I'm thinking that if I leave those parameters alone again, tonight might turn out like last night. Stay tuned.....

[Marrrmaduke]

@Dave_Demase please do keep me posted. I would really like to know if it's Versa readings or perhaps Fitbit are tweaking things on their backend which impacted calculations. Eh

[SunsetRunner]

@Marrrmaduke, I didn’t have particular times set up, however I did have a time asleep goal. I took that off last night based on one of your previous comments and my sleep pattern logged last night.  I’ll continue to monitor it

thank you 

[Marrrmaduke]

@SunsetRunner Please do. Something rattles in my foggy brain that I read somewhere in the forum about sleep presets causing some issues. But again, this might be just my imagination... Let's hope it keeps!

[Dave_Demase]

Well, very "interesting" results last night. First glance at the sleep results this morning showed a session starting at 10:45pm and ending at 2:10am, with no follow on session through my actual sleep until 7:30am. I also noticed that the app hadn't synced since around to 2am hour either, showing an error on the sync notification. No amount of coaxing would break that logjam, either. I resorted to power-cycling both devices. When back up, the Bluetooth link still wouldn't connect as before. More futzing around with this and that, until a new email came in on the phone and a Notification popped up on the watch. I really don't have a handle on the underpinnings of how the communications are suppose to work, yet. I now figured that sync was ok, but checked Bluetooth on the phone and no link yet (waaa????). Went back to the app to check sync status and no change from error. Went to the sleep section again and while looking at the previous results the screen updated in real-time and now the session is in the final expected state.....10:45pm to 7:30am just as in real life.

While a desirable conclusion for today, this doesn't give me any insight into what are the fragile parts; what to do about it, if anything; whether to acknowledge this loose association of systems are half baked; or spend my time worrying about more important things. I've deleted the sleep schedule parameters for now and will go forward with that.

[SunsetRunner]

@Dave_Demase, it’s strange for sure. Mine detected last night as well so it gives me some hope lol. But it’s always detected my sleep pattern pretty accurately until the update. So I feel like the misreadings have something to do with the update 

[Marrrmaduke]

@Dave_Demase that I can explain. Versa needs to be able to talk to your phone/sync. One of the users of this forum already performed bunch of experiments. 😊 So basically no sync, he would not get sleep logs. After your Versa synced it pushed the data to servers where the calculations are done, sleep got recalculated and downloaded to your app, so you could see it.

@SunsetRunner not necessarily. Each updates requires changes on their back end. I hope they're sorting or already have sorted it out. Keep an eye on it.

[Dave_Demase]

Another night with Sleep Schedule set to blank yielded another night of successful data acquisition. So it seems to me the Sleep Schedule is just way to define a goal for a structured sleep pattern. Fine, I can live with out that reference if it means I'll collect the accurate data each night.

Another observation I have taken to detail is the wireless link between phone and watch. I noticed when there is difficulty transferring data between devices that the BT status on the phone is set to ON, but the phone shows no connection. If I set the watch to PAIR, and the tap the BT definition for "Versa (Classic)" it connects straight away and Sync occurs in a jiffy. Sometimes after that, the watch will on its own set the BT status to ON or OFF from PAIR  and the cycle of no comms begins anew until I intervene once again. There is another BT def in the phone for "Versa" as a BT generic device, while the BT "Versa (Classic)" has a Profile for an input device. The former never seem to connect under any circumstances, but appears to be required for operation as it will re-define itself if I remove it and leave Versa (Classic) alone. Today auto-sync seemed to stay in an expected state of operation on its own. I'd like for that to be the normal state, of course. 

[Marrrmaduke]

@Dave_Demase I'm glad we figured out the sleep stages. Really happy it works for you. We can attempt to figure out syncing issues. Can you please remind me your phone model and OS? Sorry if you have already mentioned it, but my brain is like a Swiss cheese today. Need more coffee 😐

[Dave_Demase]

I have an LG V20 running Android 8.0 Oreo and a Versa SE with the most current firmware 32.33.1.30

It seems that sync has been stable and working regularly for the past 24 hours now. This morning when I woke up the sleep session had ended at 5am while I had actually arisen at 8:30am. As before, however, the graph updated in real-time before my eyes to the correct interval without my intervention.

I'm beginning to think that BT Low Energy is the initial conduit for the two devices to touch each other, since the BT config in the phone is rarely showing a connection as active when sync is inactive. This would explain how Notifications seem to come into the watch in near real-time even without an an active full strength BT connection. Just some speculation on my part, and my coffee has already been downed.