This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Temperature precision in Garmin Connect

I have an Instinct Solar paired with a Tempe. On an activity (hike or bike) I have a data field to display temperature. It's displayed with one decimal place (e.g. 15.4C). However, when the activity is uploaded to Garmin Connect the number after the decimal point is always zero. It doesn't even round the temperature (so 4.6 will become 4.0 and not 5). It's odd that the temperature is recorded to a higher precision but that precision is wrongly truncated in GC. It even displays a zero after the decimal point which looks like that was the actual temperature.

I phoned Garmin who said they'd pass it on to their tech department but I haven't heard back.

I bought the Tempe to record the temperature and it looks like GC is the point where it's going wrong.

Anyone else having this issue or know of a workaround?

  • Could you post a link to one of your activities with the Tempe data? I can then tell you whether you can access the raw data, and how.

  • Hi Trux, thanks for that. I can't seem to share my activities. It says I need to set my privacy to everyone (which I've just done) but it still thinks I have it set to only me. I can send you an activity GPX if you know of a way to do that on this forum :-)

  • GPX is useless for this purpose, as well as the FIT file, in this case. Using exported activities, I cannot show you how to get to the raw data easily (unless you want to use FIT file tools for that purpose). You do not need to change the global privacy settings. It is enough to share just a single activity, while preserving your privacy. If you are afraid publishing your location, share an indoor activity.

  • Hi Trux,

    Found I could share from the app. I had to copy the link to myself first but here it is

    https://connect.garmin.com/modern/activity/6255373115

    Cheers,

    Dayve

  • Unfortunately, the data is indeed stored as integer values (although in float format), and not available even through the JSON data. You can access the data through the URL [https://connect.garmin.com/modern/proxy/activity-service/activity/6255373115/details] - the temperature is the 3rd place in the array members of inner structure activityDetailMetrics. (the structure of the individual cells of the array may differ from activity to activity, and it is described further below in the structure metricDescriptors.

    So the only way to get the higher accuracy, is asking Garmin to change the way they record the data - call the Customer Support, and let them know about the issue.

  • Hi Trux,

    Thanks very much for looking into that. It's good to know that the data recorded is the problem. I guess the watch (Instinct Solar) records the higher accuracy from the Tempe but it's when it's uploaded to GC that it gets truncated to an interger?

    I'll let Garmin know but I don't suppose they'll be that bothered.

  • I guess the watch (Instinct Solar) records the higher accuracy from the Tempe but it's when it's uploaded to GC that it gets truncated to an interger?

    No, already the file recorded in the FIT file is an integer value. You can verify it by opening the FIT file loaded directly from the watch, with one of available tools for viewing FIT files

  • Oh, I see. Then despite the watch showing one decimal place of accuracy, it only saves as an interger to GC. Interesting why it's showing the higher accuracy but never using it (or even rounding it correctly). So if I saw a reading of 4.9 on my Instinct the actual temperature would be 4.0 on upload.

    It's an odd thing that Garmin are doing this.

    Still haven't got a reply back from them.

    Thank you so much for your help Trux; much appreciated :-)

    Dayve

  • Then despite the watch showing one decimal place of accuracy, it only saves as an interger to GC. Interesting why it's showing the higher accuracy but never using it (or even rounding it correctly).

    As a programmer, I'd tell they use the integer type (by mistake) when saving the float value, hence the decimal places get lost. It does not look like been done intentionally by design, because the temp field is indeed of the type float, and hence can store the value with higher precision. I'd tell that the developers never got the information from the support about this bug, hence never fixed it.

    Still haven't got a reply back from them.

    Rather use one of the direct contact methods - chat or phone. The email is not the best choice - you'll get just a canned answer without any possibility of quick feedback.

  • Hi again,

    I just got a reply back from Garmin. They are saying that the FIT protocol doesn't allow for the decimal place so Garming can't do anything to fit this.