Where did heat acclimation go

I have a first generation Instinct that is always on, including during my ride, with Physio True Up turned on for both.  My watch doesn't seem to provide any heat acclimation input, not part of its ability.

So for this to work you must be paired with your phone when doing the activity as it needs the humidity data provided by the weather forecast. To see any acclimation I think the weather forecast needs to show temperature above 76 F

aweatherall that makes sense.  I am connected to my phone with the 530, I do get weather data on my 530 and my heat acclimation is working.  It is the other posters that are having issues with heat acclimation.

aweatherall said:

So for this to work you must be paired with your phone when doing the activity as it needs the humidity data provided by the weather forecast. To see any acclimation I think the weather forecast needs to show temperature above 76 F

Exactly as I did. If I had not done this way GC web would not be able to show weather data assigned to the activity. It assigned 31.1 C degrees, which is 88 F. I checked and the weather station provided humidity, too.

So everything happened as in all the early cases when relevant Heat Acclimation was calculated and not 1%.

And it was not a fake ride of 5 mins without any training effect:

And I do not know from where this value of 1% comes. Is it the remaining part of a higher value gathered by wearing my F6X, or that of an earlier ride made a couple of weeks ago with 530? As I wrote in the other thread one cannot check the historical chart of Heat Accl. of 530/830 if it is not his primary device.

Sidenote:

today I had a run with F6X, my setup was the same (the same phone with me, GCM was running again), I see the weather data of the same (!) station including temperature and humidity, the temp difference between this run and that ride is just 1.1 C degrees, and F6X rose my Heat Accl. from 4% to 26%.

Sub-sidenote:

while yesterday my 530 (1%) and my  F6X (4%) showed difference values of Heat Accl. even after 3-4 syncs of each device, today 530 copied the value of 26%, so no discrepancy.

My conclusions:

A) the dataflow from F6X to 530 is at least partly fair meaning Heat Accl. is OK, Traning Status is OK, while training load data are different  in spite of the fact that both devices use the same Physio TrueUp method by Garmin Support Articles. NB: Training Statuses can be different between 530/830 and F6X, but not the Training Load*

B) I still have to figure out when 530 does not calculate properly Heat Accl., and my bet is that this phenomenon causes the strange discrepancy between Heat Accl. values  of 530 and F6X meaning that the dataflow from 530 to F6X is worse than in the reverse direction.

*
”The Device Compatible with Unified Training Status with act as the PTD by default. The device without Unified Training Status will still generate its own Training Status that will be visible on the device itself, but the Training Status on the PTD and in Garmin Connect will be the true Training Status. You will no longer see the option to toggle between different device's Training Status in Garmin Connect if a PTD is set on the account. ”

“

Garmin Connect users with multiple devices can use Physio TrueUp to keep much of their data in sync between their various devices, including training load, with some exceptions. The calculation methods for training load were updated with some 2019 and 2020 models of various device families.

No big loss, it laughably tells me I'm "100% heat acclimated" when temperatures are in the 80s.

I too think there is a bug.  I am going to call Garmin sometime next week

Thanks.

When I called Garmin Europe they tended to propose me calling the local Garmin. The latter say they will forward what the users have found, but they add that their reports are typically not considered with a high weight. Maybe it is because our country is not bigh enough and Garmin might rank the bug reports based on their sales ranking.

So my strategy to report here, in online forums and pray that Garmin-Chris, Garmin-Blake etc. embraces the problem described here as a bug to be discussed with engineers.

But if local heros like you  take up their full armour and are ready for a duel with Garmin support it will increase the chance of a fix to some extent.

Today I decided to parallelly start and stop Edge and Fenix. I do hate this, because it confuses training load and sometime other physiological  data even if one of the activities is finally not saved.

First I saved 530, which said 25% has become 25.

Before any sync could have happened I saved F6X, which said 25% has become 33%.

So I have excluded even the chance of a fatal coincidence that F6X is simply luckier as regards the time pattern  of its usage.