VO2 max steadily rising since 20.16 when using a stryd

Update: VO2max seems to be leveling off. Also performance condition is lower, although still higher than before 20.16.  But I have been thinking. The VO2max reported by garmin is not your real VO2max, it is only an estimate.  The real VO2max can only be measured in a laboratory, and, according to a physiologist I once asked about it, doesn't change a lot. The estimate is based upon the data your watch collects, an your age weight en length. The watch measures tempo, speed, hart rate, HRV and uses that to estimate the VO2max. Suppose they decided to include the power measured by a stryd  into the mix? That would definitely generate a  different estimate, which would level off after some time.

I can also report it does seem to be leveling off but there was clearly an adjustment to the Firstbeat metrics where everyone now is getting a free bonus vo2max point somehow.

My race predictor in comparison has not changed at all, nor my LT HR/pace, all the same and the efforts feel identical.

If I didn't have this kind of detail to examine, it would easily fool me

(Feb 25 was the new minor Firstbeat update on the Fenix6 series in the v28beta firmware)

past six months very gradual daily, February 26 BOOM rocketship

(distance is locked to the stryd pod and not GPS)

Any updates on this? Will this be updated in upcoming versions or should one downgrade to some previous FW. It's frustrating that my numbers are now way off.

Any update on this from other users.  I had about a month of rising VO2max and runs being categorised with higher training effect than would be expected,  I then stopped using the Stryd pod and my VO2 max value had been steadily falling back to its old value and runs categorising correctly. 

If anyone knows if this had been resolved I can try using stryd again.

Just curious, what does everyone have the Pace setting set to in the settings for the Stryd Zones data field? I rolled back to 19.41 due to this issue (which fixed it), but found that I could reproduce it on 19.41 as well (at least the overly high Training Effect after easy runs) if the Pace setting in the data field was set to "Pace" (i.e., instantaneous pace with no smoothing) instead of "3s Pace". I haven't tried playing with this setting with the newer Fenix firmware versions, but I'm wondering if that could have anything to do with it. Anyone using newer Fenix firmware with Stryd and 3s or longer pace averaging?

Just curious, what does everyone have the Pace setting set to in the settings for the Stryd Zones data field? I rolled back to 19.41 due to this issue (which fixed it), but found that I could reproduce it on 19.41 as well (at least the overly high Training Effect after easy runs) if the Pace setting in the data field was set to "Pace" (i.e., instantaneous pace with no smoothing) instead of "3s Pace". I haven't tried playing with this setting with the newer Fenix firmware versions, but I'm wondering if that could have anything to do with it. Anyone using newer Fenix firmware with Stryd and 3s or longer pace averaging?

Ok. I downgraded to 19.41 and set automatic updating to OFF. So no updates (or new Garmin watches) for now.. Sad.

An update as to whether going back to 19.41 works would be helpful. 

It seems to work well, Vo2max is going back down, exercise loads seem consistent with my feelings and so on.