Hi,
It's been second time that i've noticed that when new Lactate Threshold is detected my watch also updates max HR value by the same difference. For example this morning my LTH went from 174 to 176 and watch updated those in runing zones but it also updated my max HR from 200 to 202 ... It seems like a bug to me... Previous time it updated my max HR to 206
And to clarify in both runs i had max HR of ~192 so i didn't get new max HR reading (my current is 200 from 3 months ago)
Yesterday I installed 22.74 Alpha firmware, following which I modified my heart rate zones to be based on threshold HR, which I adjusted up to 179 based on recent performance. Max HR remained at 195. I erased my whole activity history too, but not my records.
Today I had a real easy Z0-Z1 ride for a bit over an hour, at the end of which the watch decided to update my Max HR to 178, one less than threshold.
After syncing with GCM all my zones there looked exactly as I had set them and Max HR was still 195. On the watch, however, Max HR was indeed down to 178, as announced by the watch, while threshold was still 179.
Here are my most recent rides with HR stats. Where on earth did Garmin get a max of 178 from?
I will obviously report this in the alpha channel, but i thought I'd chip in here as the topic is similar.
in case of %LTH zones there is max HR on at the end of zone5 so I think it uses this value. When I manually fixed mine from 206 to 200 automatically then next day my base run suggestion was 150bpm instead 155bpm while having 206 there.
