Yeah, I think they probably just tweaked it up a bit.
What you describe is the same for me. I get 90% of my "rest" while I am asleep. During the day, I will only get the odd blue line here and there.
To me, that makes sense. The body is doing almost 100% of it's recovery when you are sleeping. That is the most important time for recovery, so it makes sense.
This is what mine looked like on day-2 of a "rest and recovery" period (sometimes I take 2 or even 3 days doing nothing to get full recovery). I think I did 10 minutes of yoga or something, but nothing intense.
Also, if you hard reset the watch, everything would back to normal and you would see normal patterns again that corresponded with your stress and activities. But after 2-10 days, the values would gradually start to get corrupted until it reached the same situation again.
It's worth noting that a high stress score is not "bad". It's just a signal that you've done a lot of work and your body is repairing and recovering (and getting stronger). Maybe you guys who are getting lots of high stress scores are just doing a lot of hard training? If you're training hard and often, it would be perfectly normal to expect high stress scores. Low stress scores wouldn't make sense. In fact, in a way, you're aiming for "high stress scores". It's telling you, "okay you've done enough work, time to recover". If they tweaked it so that the stress scores went down and everyone was getting low stress all the time, that could be interpretted as, "you're not working out hard enough or often enough".
However, if you're not training very intensely, or not doing it very often, then you definitely shouldn't be getting high stress scores all the time (unless you're drinking booze every night).
Are you guys actively recovering? As in making a plan to recover after a hard workout day with no workouts, no alcohol or coffee, plenty of water and an early night in bed? That is how I got my stress levels to go down on v8.0.0 (screenshot above). It actually took a couple of days of that, but the stress level did go down.
The point I'm trying to get across is that everything is the same as before 7.60, no drinking, same workout routines and intensity, same rest, all other metrics are normal (RestingHR, training load and effort, performance, sleep, etc) is just the HRV widget that went completely out of whack after 7.60 and does not correspond to all other parameters, and before 7.60 it did correspond. It is not simply that its giving somewhat proportionally higher values than before or if its more sensitive to changes, if that were the case it would be no problem since the specific value is of no interest, its the overall zones they fall in and their trends, and those would still be there and that is not the case.
Seems not everybody have this bug (you don't appear to fortunately), but others do, in my case it was clear with my Fenix5 after 7.60, and a bit later same exact thing happened to my wife and her Vivoactive3. Anyway seems it has been fixed now, hopefully.
The point I'm trying to get across is that everything is the same as before 7.60, no drinking, same workout routines and intensity, same rest, all other metrics are normal (RestingHR, training load and effort, performance, sleep, etc) is just the HRV widget that went completely out of whack after 7.60 and does not correspond to all other parameters, and before 7.60 it did correspond. It is not simply that its giving somewhat proportionally higher values than before or if its more sensitive to changes, if that were the case it would be no problem since the specific value is of no interest, its the overall zones they fall in and their trends, and those would still be there and that is not the case.
Seems not everybody have this bug (you don't appear to fortunately), but others do, in my case it was clear with my Fenix5 after 7.60, and a bit later same exact thing happened to my wife and her Vivoactive3. Anyway seems it has been fixed now, hopefully.
Yeah mate, I understand. It seems that for whatever reason, I've been lucky and just not got that bug you guys are talking about.
Perhaps it's due to my locale, or the fact that I got the watch quite recently (I think I updated it to v8.0.0 before I even strapped it on my wrist).
