Training still being recorded incorrectly

The same for me. I ran on Friday. 79% in zone 2, 19% in zone 1. Average heart rate 148, max 157. Even though it was very easy run, it was labeled as Tempo. Not to mention today - I ran with a friend of mine. Easy run, we were talking most of the time. Average heart rate 156  (there were some hills). Labeled as Threshold (my lactate threshold is 185...). Numbers since last update are very strange and useless for any plans of next training.

Thi is an issue across all devices from one of the recent software update . FR 955 is showing same issues. They seem to be releasing a new beta in the last day or so to (try) and address this... I updated in my 955 but not convinced as yet..

Heart rate *zones* are not used to assess a run (that was executed with GPS) from a training effect perspective.

Pace as % of VO2 Max Pace is the metric that is used, as well as patterns, intervals, rate of change, etc. The foundation is that there is a straight line of correlation between VO2 and work (pace or power) up to VO2 max, where the line levels off, as the muscles saturate with lactic acid.

It is hard to predict how a run will be classified for 2 main reasons: first the algorithm is a black box, and second the patterns are assessed statistically.

So, depending on how you have set your heart rate zones, you might be in your zone 2, but your pace puts you in a zone 3 as % of VO2 Max Pace.

Or your heart rate goes to your zone 4 or 5, but not with patterns that put in a anerobic-powered pace, and you run is base or tempo.

Look here. There is a tiny difference between a 60mn run at moderate pace (base run) and a tempo run (60mn at marathon pace)

www.firstbeatanalytics.com/.../

Think of this a second. Could you run a marathon in your zone 3?Your 60mn marathon pace will probably stay in zone 2, and start drifting up to zone 3 and above after about 2 hours...

To be clear, it doesn't mean that HR data is not used (it is, since it is the basis for VO2 estimation), but your time in heart rate zones is not used.

To address the misalignment you should consider doing 2 things:

- determine your true max heart rate. Turn off max heart rate detection by the watch. This is very hard to test in the field, but you will find workouts designed to get you there while avoiding lactate limitations. They typically look like a VO2 max workout, with the last high interval run until your pace collapses. Don't use the max heart detected by the watch. Worst case, if your doctor doesn't let you run a field test, use a formula like 220-age to get started.

- run a threshold test. Turn off LT auto-detection and set your heart rate zones based on LTHR. This is as close as you can get in terms of aligning the heart rate zone with VO2 zones.

- run a balance training. Use the suggested daily workouts to do so.

I did and still doing all the above, tweaked my HR max estimate by a 1% and, through trial and error, aligned the metrics and confirmed them with 3rd party tools like trainingpeaks and WKO software.

Correct. Garmin has said they have some data sync issues, and they also corrected some bugs in race prediction.

I noticed the daily biking suggestions targets are much more normal this last week or so, but there are still some issues.