Training effect data

I'm not denying that some have a bug. I'm providing a balanced perspective and making sure that Garmin understands that this bug is far from universal. It wouldn't help much if their fix breaks something that wasn't previously broken for others.

Furthermore, Chris hasn't exactly been forthcoming about the bug - who is affected, who isn't, what causes the bug. It's the usual story of stony silence and an information vacuum. If you took the original post and Chris's reply at face value you'd think it was completely broken. The fact is that it isn't completely broken and no doubt for many of us it's absolutely business as usual. It seems to me that that is worthwhile information to share.

It also seems to me that customers are doing a better job of information sharing than Garmin, even if it is only speculation based on their own individual observations. What a pity that Garmin does not seek to clarify the facts for us! It might save some friction.

Nothing new here. Every time a new release come , problems come. But what is sort of strange is that some have problems, some have not. Guess that’s why it’s a pain in the a……. for Garmin. After ver 19.20 my calories when i am hiking is the 50% of what it use to be ( I always go the same track). But when i am cycling (indoor and outdoor) using powermeter, everything is as normal.

Is training load calculated based on HRV? I was sure it was only based on the different HR-zones? Where can I read more about that? Only found this https://support.garmin.com/en-US/?faq=SEkNpdGyhR917js0qQL3Q6 

Reading between the lines on emails I’ve exchanged with them, the issue seems to arise from Garmin is reading the HRV data from third party straps since they changes whatever they changed in 19.x  

When I provided some data early on I never mentioned HRV at all (I tried Bluetooth and ANT+, speculating that that was the issue), but the later replies from them have continuously referenced “HRV data”, the latest being hasn’t been stored and therefore it won’t be possible to correct the training metric data on affected activities. 

Garmin being Garmin they’ve tried to suggest it is the strap manufacturers who are at fault because of “how the data is being sent”, but they have ignored the question “if that’s the case then why is this only broken from 19.x onwards?” and avoided going down that path again. 

Thats very interesting! It sounds like they changed the formula in 19.x to include HRV-data for more accurate calculation, which caused a lot of problems for the devices without HRV-data.

It sounds like it could be an easy fix, I mean, they should be able to use the same formula as the built-in optical sensor to fake the data from the 3rd party sensors which are missing HRV-data.

Hello. What is the schedule to fix the training effects issue? It's also effected my training status and calories burned.

I'm finding Aerobic TE is calculating values OK but possibly seems a little higher since 19.20 - I've not seeing any Anaerobic TE for running on 19.20, even after a harder tempo run yesterday where previously (pre 19.20) I would have. That said, after a harder bike session on 19.20 (middle of last week) I was seeing Anaerobic TE - this possibly suggests the issue is with the running algorithm specifically?

I don't run anymore. I bike. And I'm seeing the same problem runners like yourself are having with anaerobic TE calculations.

Any update on when the issue will be fixed ?