All day stress always reports HIGH since update 7.60

Former Member
Former Member
I know that the update was supposed to improve the reliability of the all day stress reading. However, for me it's done exactly the opposite. Since the update, my stress reading is always MEDIUM to HIGH (51 to 100) even when I'm sleeping! Is anyone else seeing this???
  • Thanks for the heads up, fingers crossed!
  • Former Member
    0 Former Member over 7 years ago
    It might be premature to conclude this is fully fixed but since installing the new beta (8.99) the reported stress levels dropped quite significantly for me (from ~20 during sleep to ~10 during sleep). Those were levels I last saw before 7.60.


    The number is really irrelevant. To my understanding, tt's just some number Garmin came up with to measure HRV. They chose between 0 and 100, but they could have decided to scale it between A and Z or 0.0 and 1.0. It's irrelevant. What is important, I guess, is the long term trend and the realtive changes that you observe between periods of high-activity and rest. Whether that number is 10 or 20 or 20-billion doesn't really matter. (to my understanding). It's the relative changes according to your schedule and lifestyle that are important.
  • Not really. Garmin is clustering the numbers into Rest/Low stress/Medium stress/High stress.
    Previously, during what I considered rest, the number was in the high 20s which is Low stress. Now in similar situations it's sub-20 which is Rest. That makes a significant difference interpretation.

    Agree with you that it doesn't matter if it's 0-100 or 0.0-1.0 but which number under which condition falls under which "band" is important.
  • Former Member
    0 Former Member over 7 years ago
    I do understand your point ... you want your records to be consistent over time. That's fair enough.

    But maybe Garmin just thought it was reading stress incorreclty before and they tweaked it in the update, and you're just not used to it yet?

    I only got my watch recently, so I never saw what it was like before. But for me it seems the stress scores to be exactly correct. If I work out a lot (or if I drink alcohol, or don't sleep well), then the stress score goes up quite high. If I take a few "recovery days" where I drink a lot of water, get good sleep, don't workout, etc., then I get lots of blue lines and "rest" periods. It seems fine to me how it is now. But maybe it's because I just never got used to how it was before? I dunno.
  • The numbers I was getting "after 7.60" were not completely impossible (as some other people here did report). But they went up in a way that did make little sense when interpreted (I basically could not achieve any longer periods of rest outside of sleeping). Again, now it seems to make more sense again, although it's not a drastic change.

    I believe that (since stress measurement is an experimental feature in first generation) Garmin is tweaking things behind the scenes quite a bit.
  • Former Member
    0 Former Member over 7 years ago
    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.


  • Precisely. After 7.60 and before 8.99 my only rest was during sleep (unless I had a few drinks but that's a different story). Almost all awake time was low or medium stress.

    After 8.99 the behaviour reverted to what I was experiencing before 7.60: Rest in the 10-ish range during sleep, low or medium stress during work (correlated with perceived stress) and rest when I am genuinely relaxed during the day. So much more aligned to perceptions and a higher degree of consistency.
  • I agree they fixed something in 8.99 beta firmware. For the last few months I did not get any rest periods at all, even during sleep. Granted this year had a stressful beginning for me in general, but that what an average day looked like (stress score around 40-50), see pics attached. And last week I had pretty bad flu/fever, so the score went up almost to a 100...so it still worked in a sense that it showed me a trend, but no restful period during my days off seemed not right. I updated it to 8.99 last night, and during last night sleep I woke up and looked to the stress widget out of curiosity and it gave me 0 - rest! I have never seen 0 before, so it all makes sense now!ciq.forums.garmin.com/.../1348243.png
  • Former Member
    0 Former Member over 7 years ago
    Sounds to me like they broke it.

    My screenshot above is v8.0.0. If you were getting "high stress" and it went to 0 after you updated, I'm going to be getting negative stress scores. :-(
    O.

    Or at the very least it will say I'm just constantly rested which is useless to me.
  • I agree they fixed something in 8.99 beta firmware. For the last few months I did not get any rest periods at all, even during sleep. Granted this year had a stressful beginning for me in general, but that what an average day looked like (stress score around 40-50), see pics attached. And last week I had pretty bad flu/fever, so the score went up almost to a 100...so it still worked in a sense that it showed me a trend, but no restful period during my days off seemed not right. I updated it to 8.99 last night, and during last night sleep I woke up and looked to the stress widget out of curiosity and it gave me 0 - rest! I have never seen 0 before, so it all makes sense now!


    This is great news, cause with thr4 it makes two people who have had the issue fixed by the 8.99 beta (I haven't installed it), so gives cause for hope. Hopefully they will deploy the same fix for the other watches like the FR or VivoActive3...