Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

HRV, low state for a long time

Thom@s
over 1 year ago

My HRV has been too low for 4 weeks. I think the watch is measuring wrong. I'm healthy and everything is as it was. No change in lifestyle, sleep, stress, everything ok. My Training Intensity is rather less now.

Does anyone have the same experience?

Top Replies

All Replies

  • 0 9 months ago in reply to Etupes25

    Hey thanks for the tip about resetting HR zones after an auto-detect event. I did a LTHR test with my HRMPro+ last weekend and had a 5BPM increase over the previous result from a few months prior. When I looked at the zone settings (based on %LTHR) I saw that the percentages had all changed such that the actual BPM limits remained unchanged. Upon closer inspection the zone boundaries were nonsense for all zones ("option 1" in table), although thankfully zone 3, which I use for base runs, was centered on the right range.

    I did as you suggested and reset the zones plus toggled the base between %MaxHR and %LTHR. Everything made a lot more sense after that. So it would seem that there is a bug in zone values when auto updates are made.

    It is a bit weird that if I reset zones when the base is %MaxHR and then switch to %LTHR, I get different zone limits than if I reset them with %LTHR selected. I am not sure what to make of this since the zones are wildly different. For now I am sticking to “option 5” in the table below. Should I use the value from "option 2" where I did the reset when %LTHR was the base, since I have a somewhat reliable value for it?

  • 0 9 months ago in reply to ZombieSloth

    Yes, you should do one last reset “column 5” and you should the same as column 2.

    i am not 100% sure you need to change the system, reset, go back to your preferred system and reset again. I just wanted to make sure the app would re-read the key anchor values. Maybe a simple reset on your favorite system would do (your column 2). 

    i noticed that on Garmin Connect mobile on the iPhone there is a display bug. After a reset,  despite the fact that the app tells you the reset was completed, the values don’t update. I need to navigate one level up in the menus and then come back down to the zones to see the values actually change..

  • 0 9 months ago in reply to Etupes25

    In the table, it is showing a sequence of 5 operations that I did. Sorry that I was not more clear.

    1. Column 1 is what was in there after the last automatic LTHR update, with %LTHR as the base
    2. Column 2 is what was shown after the reset operation with %LTHR as the base
    3. Column 3 is what was shown after I changed the base to %MaxHR
    4. Column 4 is what was shown after the reset operation with %MaxHR as the base
    5. Column 5 is what was shown after I changed the base back to %LTHR

    I find it a bit odd that columns 2 and 5 differ so much. Honestly I do not know what to trust there. The zone settings do have a significant impact on the training metric calculations, correct?

    Or are you saying that I should do one more reset with %LTHR as the base (make a "column 6"), which should match the column 2 values, and move forward with that for my training?

    Thanks!

  • 0 9 months ago in reply to ZombieSloth
    ZombieSloth said:
    Or are you saying that I should do one more reset with %LTHR as the base (make a "column 6"), which should match the column 2 values, and move forward with that for my training?

    Yes.

  • 0 9 months ago in reply to Etupes25

    I see, thanks. It's worth a try...I wonder what it will do to my training metrics. Up to now my base runs have been in Zone 3 (shooting for an average BPM of 139). The new settings will have that sitting within Zone 2. Have I spent the last year working out with totally bogus zones? lol..."technology!"

  • 0 9 months ago in reply to ZombieSloth

    It is exactly the problem I describe in my posts. Although I do not have auto detection on (hat gave weird settings too), my %lthr zones were way off after I put in a new LTHR value manually (after a test run). My training schedule gave me easy runs in zone 3. I found out, when I switched to %HRmax, the BPM dropped a complete zone. So %LTHR gave me a complete zone too high. Therefore wrong training level. After multiple switches and resets of the zones (before Etupes25 advice I was just experiencing by trial and error), the levels between %LTHR and %HRmax now are the same.

    It is ridiculous that you constantly have to check all the settings in the watch/connect. I also had unexplained changes of HRmax (auto detection OFF), even changes from 194 to 206 or even bit higher. Now after every run I check the settings. In the past, it damaged my preparation for 10k and also for a full marathon. I barely trust the watch. I get more and more disappointed due to this stupid faults. Every update of the firmware I consider as suspicious.

  • 0 9 months ago in reply to ZombieSloth

    The %LTHR and %MaxHR percentages are from different leagues:
    %LTHR talks about LTHR percentage, and %MaxHR talks about BPM.
    100%LTHR is not equal to 100%MaxHR.

  • 0 9 months ago in reply to LaudelinoQ

    Sure they are different. In both systems you can calculate/determine the BPM which comes with the 5 zones. They should more or less be the same. Not exactly, because the base of the calculations is different. But my zone 2 ended just below LTHR. so at 176 BPM. Z2 was called Easy.. Nothing easy on 176BPM :-). When I switched to %HRmax, it gave me 157 for the end of Z2. That is more "Easy". AFter I switched back to %LTHR and resetting the zones in between, Z2 based on %LTHR is now also somewhere around 157. @ZombieSloth experienced the same. A base run ended up in Z3.

  • 0 9 months ago in reply to DaKo

    As far as I know, maximum heart rate is a temporary value, but it is the same value in the presentation of HRmax and Lactate Threshold.