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

Auto adjustment max HR broken?

So I bought the Forerunner 955 little over 1 week ago and I had put my max HR manually to 196 (highest I've seen when testing it out in the last year).   In the course of this week Garmin auto adjusted that to 186 ... ok.   So yesterday I did a tempo run and really pushed myself to register max HR on the watch so it would correct the max HR  again.   This is where I don't fully understand how this works with Garmin.  I had a max HR of 198 during my tempo run, but the watch corrected my max HR setting to 192.  I wonder why it didn't just push up max HR to at least the max value during the run.   I ended up manually adjusting the max HR on my watch again.  I hope this time it will not lower it again.  Could it be because I'm doing mostly easy runs?

  • Garmin works in mysterious ways... It indeed makes no sense.

    You can prevent it by disabling auto max heartrate detection in:

    Settings - user profile - heartrate&power zones - automatic detection - max heartrate

    (Haven't got it in English so might differ a bit)

    Because why use the actual measured max heartrate when you can use an algorithm to predict it incorrectly right?

  • I also had that problem with both maximum heart rate and lactate.
    I turned off both automatic settings but I see that after every run it keeps changing my heart rate zones from bpm to % lactate.

  • I had the same experience with it lowering to a value below what was reported for the run.

    I had to disable the auto detection for max heart rate because the watch lowered it, I changed it back, and then after every subsequent run (mostly very easy nowhere near max HR) it was lowering it again to that same value.

  • Same here. So after adjusting it to my new max hr of 198 last friday, I went for a long slow run (1h20 min at 130-140bpm) yesterday and it readjusted my max HR to 192 again...  So the watch 'forgets' that I just ran more the day before?  Another broken feature on my 550€ sportswatch.   Turned off the auto HR setting as suggested here.

  • In this image we see a double error.

    1. Heart rate set according to my lactate threshold (150 bpm).
    After the race the heart rate zones are random (z2, z3 make no sense. Z4 should start at 100% = 150 bpm).

    Failure 2.
    I want to change my heart rate zones manually again. In zone 4 it starts at 150 bpm, but when I try to change it, the maximum I can add is 105 bpm, and so on with all the other zones.

    I will have to hit reset zones.

    Auto HR is off.

  • I’m also getting this. Seems like a bug

  • I think the 105 you are entering is incorrectly linked to %, not beats per minute. 

  • I have the same issue with my 955, MHR is way off compared to my real value. I am going to now manually input it in the profile and turn off autodetect.

    Odd as this should be spot on taken from the values attained from training. I would understand if it was a one off or two spikes occasionally, but consistently having trained now for two weeks and several of my runs and clocking a higher value of HR it still logs in my MHR in the profile at least 13BPM lower.

    I am hoping this is a bug that Garmin will iron up and get it fixed soon

  • Same here. 3k ALL OUT test on Sunday, max recorded by chest strap HR 196, the watch offered to save 192 as a value. Today, long Z2 2 hour run, max recorded by chest strap HR 171, the watch offered to save 191 as a value. Turned off max HR auto-detect for now. Also, I do not know for you guys, but the zones provided by the LTHR estimate make much more sense for me than the max HR ones (even with 196)

  • I did an easy run this morning; max HR of 152, average HR of 142. When I ended the run the watch altered me that a new max HR of 190 had been detected/calculated. 

    Is this how it’s supposed to work? Is it looking at my easy pace along with a bunch of other metrics and algorithmically estimating my max HR?