Discrepancy between HR zones and post-activity report/training effect

I noticed the same inconsistency - quite confusing and annoying  to see lots of green (=3rd zone) in one graph although it’s 0% when you look at how much time you’ve spent in that zone.

Did you find out how / why that happens?

fenix 7ss 7.35

I did some tests and I found out that my fenix 7 uses the "generic" HR zones to draw graphs and calculate training effects (aerobic, anaerobic) and related metrics (load, workout primary benefit).

The cycling and running specific zones are ignored by the watch and are used only in Garmin Connect and to show you your zones during a workout in the specific field.

So I solved the problem compiling the generic HR zones/max/treshold to mimc the running and cycling parameters (I made an average between the two, because my runnig values are all a little higher than my cycling counterpart).

Now the graphs and the primary workout benefit make sense.

I’m not sure I can follow.

The two charts/ photos above are both from the watch and they are inconsistent. The 2nd chart shows ample green while the first tells us green is essentially 0%.

As far as that inconsistency is concerned I would say: It doesn’t matter if they both are based on the generic HR zones as long as both charts use the same HR zones.

Does that make sense?

I think the point is that the defined zones are not used consistently between functions on watch and analysis shown on GarminConnect. This is what I'm finding as well and it's widespread. It feels as if different functions both on the watch and on the app were set up by different teams and each made their own decisions about what zones or threshold values to use for each thing.  And since Garmin doesn't document these things, it's very difficult to figure out what is going on.  Intensity MInutes has some very hard to find options to determine what is considered moderate or vigorous but it doesn't really explain how it works when you choose the settings.  Fitness Age doesn't explain what is considered vigorous and if it's the same as Intensity Minutes.  HR Zones on Garmin Connect seem not to use Sport Specific zones - at least not consistently. All of these issues would be pretty easy to fix. 

The first graph (vertical bars) uses my defined cycling/running zones, while the second one uses the generic HR zones: if these zones are different, the two graphs follows.

And I think the watch calculates primary workout benefit on saving using the generic HR zones.

After I altered my generic HR zones, what I was thinking was a "base" training was classified as "base" on saving, and not as "Tempo" as before.

Oh this would explain a lot- I also found that the categorization (base, recovery, tempo) made no sense to me. 

Yes, I agree. Sometime Garmin's software is frustrating. It works well, when you finally understand how it works under the bonnet. And most of this thinks could be easily fixed with a patch, so Garmin should put great attention to its forum and reports from the users.

That's just ridiculous!
I've not noticed it because I set my custom HR zones everywhere I could

Yes exactly.  That's what is so frustrating about so many of these issues - they aren't hardware problems or complex algorithms that need to be developed.  They often seem to be due to lack of testing and lack of coordination between different efforts at Garmin.  I did a review of the Fenix 7 with a lot of things that I find problematic - about 80% of them could be resolved by a combination of documentation and relatively easy patches.  On the one hand, you have things like detecting sleep stages - I'm sure those are NOT simple so I recognize the technology isn't quite there yet.  On the other hand, using the wrong HR zones, or not being clear which zones are used, or using different zones on the watch and on the app or setting a floor counting altitude threshold that is too strict - these things are not difficult to fix. It's hard to understand why Garmin doesn't resolve the easy ones. Quick wins, right?   

There could be a bit mor finesse from such a well known and respected brand. A similar data mismatch occurs between max HR in an activity and the overall daily HR display. Activity will show, for example, max HR 174, but the master HR display will typical show something less. There are no doubt separate data tables between activity HR and the general HR. A bit of cross referencing would resolve that glitch.