Improved Lactate Threshold Measurement Feature in 21.19

I see a big problem in a new feature too. I got my last update on 6.01 on a short and easy run with  WHR only. There was no LTHR update message on the watch. It is simply in GC now. Such magic. There were 3 LTHR runs with a chest strap after, but no updates came. Very untrustworthy.

Garmin really messed something with this "feature".

My father started using a forerunner 255 this past month. He has it paired with a coros arm band - so not chest strap, if that matters - and for a while the LTHR it suggested seemed to be normal @ 155/157, close to what I approximated from one of his fast 5k run, which was ~152 bpm. After the last few runs however, the LTHR was adjusted to 165, and today to 167. His max HR that he ever hit (probably not true max but close) was 168bpm. Clearly, this cant be correct. It started right after the blue triangle of death fiasco - although likely unrelated.

I haven't been running for the past 2+ months due to a knee injury, so I can't test personally; guided test was still a thing when I last ran. I use a HRM pro+ and after a few runs it settled to 180bpm, which feels right for me.

I think it's really stupid to remove the test. I understand wanting to make LTHR available to everyone, but why take away the guided test?

Can you please elaborate and explain? Why would you need to reset zones? Is this mentioned anywhere else?

I think he is referring to the fact that after a new LTHR is detected the heart rate zones are not updated to reflect the change, the bpm limits of the zones stay the same. It's the same fore maxHR if you have your zones based on maxHR.

So if you want your zones to reflect the new LTHR value you need to go into settings and reset hr zones, which will reset to the default zone percentage limits.

For example, let's say you had an old LTHR of 160, your zone limits would be:

104, 128, 142, 152, 160 => 65%, 80%, 89%, 95%, 100% of LTHR (default percentages - normal)

Then, after a run, your watch detects LTHR at 170. I know, crazy difference, but I've seen worse lately :) Now the LTHR value will be updated but the zones will stay the same:

104, 128, 142, 152, 160 => 61%, 75%, 84%, 89%, 94% of LTHR (modified percentages - wrong zones)

After you go to settings and reset zones:

111, 136, 151, 162, 170 => 65%, 80%, 89%, 95%, 100% of LTHR (default percentages - correct zones)

Thanks, this is bizarre, why do you think Garmin does it this way or do you think it is a bug?

Well, considering how much the detected LTHR values seem to fluctuate lately, I'm really happy the HR zones are not updated automatically, but I can myself decide when to update the zones based on the current LTHR.

I don't think it's a bug since it's an old issue that I'm sure many people complained to them about; and I think it would be an easy fix if they wanted to fix it. As for why Garmin does it this way, I have no idea; maybe they have so little faith in their LTHR estimates that they don't want to mess up the zones as well. And as Bitti said, maybe it's a good thing it works this way, what with the bonkers LTHR values Garmin spits out lately.

Also I don't think it has anything to do with the new patch that "improved" the LTHR calculation, as m8d16 implies. I had to reset the zones way before that patch dropped. It's just the way Garmin does things I guess, but I wish we at least get a toggle setting to auto-update zones when a new LTHR, maxHR is detected.

My lactate thersold test not in my running and cycling. After update 21.22.

pasa lo  mismo con mi umbral de 147 a 169 

Today I get an update but not with my SRAM Quarq AXS Powermeter. Today I paired my 965 with Beta Version 22.18 with my Kickr Core and there you are. I think there are big problems with Quarq Powermeter. I also find it a bit strange that the Kickr Core appears under sensors on the watch but not in the Garmin Connect app. Maybe one has similar challenges.