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

Lactate threshold heart rate is wrong in Garmin connect but right on watch

My watch recorded a lactate threshold of 8:24/mile with a HR of 172bpm which is consistent with historical values. However in Garmin connect it is shown with the correct pace but a ludicrous HR of 46bpm.

This obviously is nonsense. I've tried deleting activities and reimporting without success in correcting the erroneous days in Garmin connect. I could live with it as a spurious point but it results in the axis rescaling making the plots worthless.

Any ideas folks?

0 f|33tStA over 6 years ago

had exactly the same prob with Fenix 5 when i bought it more then a year ago, looks something is mixing you resting HR?

what version of hr-zones do you use, are on the watch the same values as in Connect, often they don't sync together?

on my Fenix 5 works Lactate Threshold only with the Garmin Test, it's impossible to get it with a own run activy, think arround 2-3 it isn't working for me

0 kerlaz over 6 years ago in reply to f|33tStA

Heart rate zones are the same on watch and Connect. I use %HRR for zones.

0 f|33tStA over 6 years ago in reply to kerlaz

with resting HR?

it could be, that Garmin Connect have a bug, Android or iphone?

for me Android 4.20 have some other displaying bugs too atm and nobody acts

0 kerlaz over 6 years ago in reply to f|33tStA

With testing HR.

Android phone.

0 f|33tStA over 6 years ago in reply to kerlaz

and your resting hr = 46bpm?

0 kerlaz over 6 years ago in reply to f|33tStA

Yep

0 f|33tStA over 6 years ago in reply to kerlaz

hmmm, thats strange, this situation happens more then one year ago on my fenix 5, didn't know how it was gone, during a Firmware Update or during controlling of the values everyday in the setting on my watch and in Connect, there was no official statement by Garmin.

You ever tried the Lactate Threshold Test by Garmin on the watch? same situation?

0 Former Member over 5 years ago in reply to kerlaz

No, not the same.