MaxHR reading wrong

My max HR updates are now hovering around a higher-than-expected but not absurd level. Sometimes updated +1, other days -1 BPM.

I changed the HR zones from %HRR (had been using that forever, just used to it) to %LTHR. Now the reported time in zones, training load and effect are much better in line with previous experience.

The only thing that is off is VO2Max, now higher than in 10 years ago, while Runalyze shows a slow trend down over the years. The 5K prediction time is exltremely ambitious to say the least, but if the whole 5K would be on even pavement sloping downhill with the wind in my back.. maybe.. at least I can dream of such performance.

I think I have to disable autodetect on the 7 also, because threshold runs are rated as 'low aerobic'

This is a sign that your VO2 data is out of whack. The most likely suspect is your HR Max value.

Disable the HR Max detection because the algorithm is still too prone to be vulnerable to erratic HR date due to sensor errors.

Do a HR Max field if your doctor lets you and put the value manually.

Alternatively, you can take your peak HR in an all-out 5k race and add 4-5bpm. You can also take your threshold HR and divide by .9.

Finally, you can adjust your HR Max 5bpm up or down, run for a few weeks with good pace data, and see if the prediction for your 10k is getting real close to your threshold pace. For most runners the 10k or 15k is run at threshold.

When all these data points kind of converge to the same HR Max value over a few weeks you know your are in a good place.

note: make sure your disable VO2 max for trail running. Use trail running for any run that contains a lot of steep hills. The VO2 Max algorithm is supposed to filter out odd HR/Pace pairs but there are limits.

Apparently it also reads it wrong without my HRM. This run today, I forgot the strap but it skewed my HR again, claiming a max of 214bpm!

wschoot said:

Apparently it also reads it wrong without my HRM. This run today, I forgot the strap but it skewed my HR again, claiming a max of 214bpm!

In your place, not because I would take too seriously, but just to be sure, I would do a lab test with ECG under load to check whether you do not suffer from arrhythmia. Personally, I do not have any false Max HR detection issues, regardless whether I use the wrist HRM or my HRM-Pro, but everybody is different, and your HR curve may be simply different (while still healthy) and can lead to the false detection. Only a specialist will tell you.

I understand what you are saying and I think that makes sense. However, my point is moreover that whenever Garmin reports a maxHR of 214 in once place, I would expect it to show in the run as maxHR as well. They should both reflect the high value or both don't, right?

wschoot said:

However, my point is moreover that whenever Garmin reports a maxHR of 214 in once place, I would expect it to show in the run as maxHR as well. They should both reflect the high value or both don't, right?

Perhaps it was not detected during the run.

It would indeed be helpful to be able to find out when during this day I had 214bpm. Would this be logged somewhere for us users to find?

wschoot said:

Would this be logged somewhere for us users to find?

Well, you could try checking the JSON data with browser's DevTools » Network, on the HR page in Garmin Connect Web, but the values there are averaged over 2 minutes intervals (while the sampling rate out of an activity is 15s), so it is not guaranteed it will be there.