Auto detected max heart rate way too high!

On watch

User profile>Heart rate & power zone>auto detection

Yes I know???

CRB said:

I’m 53 years old and no way on gods earth can I get near to 184.

Why is that not possible?

Have you tested your HRmax properly?

Preferably in a sports medical examination?
I am 51, and the official test gave me an HRmax of 192.

Sorry, I was on the phone and didn’t read your post properly.

That said I am also 53 and have a max HR of 192, so 184 is not completely unrealistic.

The reliability treshold is likely, a filter removing too sudden and unrealistic high values (much higher than 184) to be physical possible.

That doesn’t explain where 184 comes from. Nor does it explain the vast differences in workout pace’s when changing the target type.

like I’ve said, doing a Threshold or VO2 max suggested workout using HR as the target is impossible! I can’t physically run or bike fast enough to reach the required zone

“That doesn’t explain where 184 comes from.”

You already have garmin explenation and even cited it. but you don’t relate to it, in your post. You talk about looking back and removing spikes an all previous workouts etc. but not about what maximum heart rate had actually been recorded and went through Garmin’s processing. 

Remove a spike later, will not undo the processing. (That would require roll-back log of MaxHR changes and where exactly they where detected. If editing in that activity happens, it would then have to re-analyze it. Garmins analysis happens on the watch, which will further complicate matters.)

So how do you reset it? And why would a spike of 2-3 seconds pass Garmin’s reliability test? 

So are you saying it was recorded in your activity. I think it would have much more helpful with a sample of said hear rate and then possible make a bug report, if you find that it shouldn’t cause the maxHR to be adjusted.

All I can recommend, is that you disable auto detection, if it is causing you problem. Max heart rate doesn’t really change much anyway. I don’t have problem with autodetection. I use a Polar Verity Sense on my upper arm. It was adjusted slightly up from 190 til 192 a few months ago. But it used to be 193, so it is not unrealistic. 

Since you already know your LTHR, maybe change your zones to be based on it, will help with your workouts and make maxHR irrelevant. 

Here is what my experience was a few months ago. 

First, the optical HR sensor glitched - when I was cruising an easy downhill it must have locked to cadence or something like that and it had me in zone 5 for a good 30 minutes while my real HR was likely 30 bpm lower.

Second, after the run my max HR was adjusted to some insanely high value - something in the upper 190s even though I am 53 years old. That was also much higher than the max HR observed during the run,  even considering the glitched HR sensor. 

Third, that had changed my HR zones according to the new incorrect max HR even though my HR zones were LTHR based. That's what really got me angry. If the zones are lactate threshold based then they should be changed only when lactate threshold changes, which clearly wasn't the case. The beginning of Z5 must always be 100% of LTHR, but that changed it to something like 106% of LTHR. 

And that isn't even all. I should mention that max HR detection was disabled on my watch. But it seems one of the updates must have reset that setting and switched max HR detection on again, and then the above had happened.