Heat acclimation and wrong temperature in Garmin Connect.

During a trip I tested  the watch in another city. The reported temperature in the other city was correct and both the watch in the widget and Garmin Connect reported in the map the right temperature. Now I'm running always with the wrong temperature, it outside is 30°C the watch reports 20°C. So the watch calculates bad all the values, for example heat acclimation and VO2 max

What's the thread you're referring to?

I completely agree, whit Garmin tempe, the watch should rely on the ANT+ temperature sensor rather thant the nearest weather station.

Nearest weather station sucks, it's kind of OK if:

• You close to a weather station
• You have your phone with you
• Your phone has a working internet connection
• You are at the same altitude as the weather station
• You're running outdoors

I'm not sure anymore, that was 4 months ago! You can probably find it by looking through the "related" threads on the right side of the forum screen in this thread. There was a lengthy discussion about how inadequate the feature was and its limitations. It is back to freezing temps here in the Pacific Northwest, so I expect we won't be hearing too much about this feature again until next summer, or maybe it will start up all over again from the people in the southern hemisphere starting to realize it's limitations now that it is starting to warm up there.  

I agree. I’m thinking about getting a newer watch with heat acclimation feature, but if that’s the scenario it won’t absolutely work for me.

Just did a very short mountain walk with my Garmin Tempe connected. For most of the walk it sensed between 12.3 and 11.7 °C (54.1-53.1 °F) and, once synced on GC, on the main page, on the map thumbnail it reports 24°C (75.2°F). Two completely different seasons.

It’s pretty obvious that, if Garmin relies on absurd data to pass it to sophisticated FirstBeat algorithms the results can not be useful at all.

With Garmin Tempe you get precise measurements, updated every couple of minutes. Why ignoring them?!?

Well one reason you might ignore is that the Tempe is highly sensitive to sunlight and inflates the temperature readings as a result.  Not sure whose genius idea it was to make a temp sensor BLACK but hey it is what it is.  (I've actually lightly painted mine white and it's more stable but still susceptible to sunlight.)

I don't necessarily agree. White would have been better, but you should avoid direct sunlight no matter what, and while under the sun it make little difference the color of the device. While Hiking I've placed it pretty much under the backpack: I can see very little and linear temperature changes, which is a consequence of a good positioning.

Plus, any sensor should be ignored because of poor usage. Should you ignore chest straps or cadence sensors because a user may fail to properly install them? 

I do think Garmin should honour what data the watches collect directly from the user, instead of relying on bogus temperature taken from other regions or totally different climate zones.

Let me rephrase that. Since a Garmin Tempe is not a weather station, which is meant to be left at direct sunlight (as you may know, the classic radial shields patter to allow air flow), leaving at sun, which is bad, will raise the sensor temperature by many degrees, no matter the color of the paint. Of course, black would be warmer, but still white would be -very- inaccurate with such wrong positioning. It would be naive to think that white reflects the full spectrum of sun radiation.

Sure, while hiking it's easier to shade it, but also while running it all depends. I run early in the morning. Maybe around this time of the year I get the sun way before 7 AM, but I usually run at dawn, so once more, color is not a variable, or at least an excuse, not to use current temperature for watches calculation. Like any other sensor (I wear at least three for any activity), my watch depends on them to provide instant data or FirstBeat calculations.

It's up to the User to properly set up the sensors; why should Garmin display temperature data while trashing it for accurate local-based calculations, like heat acclimation?

I'm a little sad that Garmin didn't fix the Garmin connect wrong temperature after 12 months that I initially reported and documented this issue