I have just installed 6.0 production software on my Fenix 5X, but there is still a bug in thermometer: in stock temperature widget for example, shows 32C, in activity data field shows 33.0 C and in "temps", 3rd party widget, shows 31.6C (that is what i think it?s right). Missing decimal digit in stock widget and in activity data field decimal widget is still ".0" .
As the guy that wrote Temps, here's my take. First, there could be a bit of "rounding" involved.
In the Temps widget, I use the saved history of the internal temperature sensor, which could be a minute or two old. The native widget might be a bit more "real time" (but you won't see the internal temp if you have a Tempe paired).
The Data field will be real time (unless you have a tempe paired, and then it will only update once a minute, and that will be shown)
So in other words, the data you posted for all three looks to be correct to me, but maybe slightly different due to rounding and the time of the sample itself. (But I'm happy Temps in the one in the middle! :) )
Just a note: The internal sensor definitely can have temperatures that are "off", and it's impacted by your body heat when you wear the watch, or in cold weather if you are wearing long sleeves, a jacket, etc. For getting ambient temperature, the Tempe is really the way to go.
I don't care about absolute readings... I know that wear the watch affect temperature reading... I'm talking about the lack of first decimal point in temperature widget that translate in lack of precision in temperature data field that show always .0 instead of for example 30.5 ! If you use the watch for open water swimming, also 0.5C are important and I have no need to pair my Tempe during swimming... However decimal digit was always been present in previous software version, I don't know why they have remove it...
I agree that this is strange and very unhelpful - this metric is probably the most useful and interesting to me. The temperature reading during open water swimming is clearly wrong after the auto-update to 6.0.
I got a reading of about 16.4C (settles after about 5 minutes swimming) using firmware 5.4 earlier in the week, this seems broadly in line with a pool thermometer reading which was around 16.0C (I think the Garmin is always 0.25 - 0.5C higher but this is consistent).
Then the auto-update happened and the next day, with no significant weather change, it just stayed on 18.0C the whole swim (around 25 minutes). So not even rounded correctly!
I've now (with great difficulty and losing all my settings) rolled back to 5.4 and had to switch off auto-update. This was successful - yesterday the temp reading settled at 16.3C, which I believe is pretty close to accurate.
Why would Garmin deliberately do this? I know there are some barometer changes in 6.0 but that doesn't explain why the temperature is now rounded to the nearest degree, nor why it also became so inaccurate (the water definitely wasn't more than 16.5C or so, so no way it should have rounded to 18C). Perhaps they don't understand how useful this is for open water swimmers - I use this to decide how long to stay in and also chart the pool temperature over time (so it doesn't matter if it's slightly high, as long as it's consistent with itself and has decimal points.
