When you change sleep start/ wake time, average stress fails to update correctly.
I had about 6 hour overnight sleep scored 88 IIRC (certainly well above 75). Then I had a long nap in the afternoon of 3h 2m due to heavy training in the morning which overrode the overnight sleep.
I went into Connect and manually adjusted sleep time to original values (wake time was my alarm time and I roughly remembered start time/ checked stress history). Except now my score was just 70. Everything restored to excellent except duration (understandable) and stress. Connect claims my average stress was 30 when it was below 15 (and most of the time below 10). Stress graph was completely blue. I reset times back to nap using the exact times, score was 34 like before I made any adjustments, and stress was again 30. Yet graph was again all blue, staying below 15 (so, well below the 25 threshold).
I have no idea where the 30 comes from. And both time periods give the same average score which is unlikely. There must be a bug in the way it's calculated, at least when there are multiple sleep periods.
I only noticed this because as I was preparing my dinner hours after my nap, my watch warned me that my recovery was extended due to poor sleep. It completely killed my readiness score. Yet I feel excellent. Body battery went up by 27 points during the nap. And this is why I consider it a bug. I feel better than I felt in the morning, the sleep clearly helped me, yet the watch thinks the opposite. Because it forgot all about the overnight sleep. This is what you get for assuming that there is going to be only one sleep per calendar day.
If anything, my long afternoon nap should have been considered sleep for the next night. Not replace sleep from previous night. And then it would be replaced by proper overnight sleep (or not; I went to sleep in the afternoon before when I needed to stay up all night). If this nap has a negative consequence, it's going to be that I will find it harder to fall asleep/ go to bed later because I'm well rested.
Restoring sleep time also had no impact on recovery or readiness. But I guess that's a watch problem, not Connect problem. Since it's 965, I'm not even going to bother reporting it separately.
