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

Bike Cadence for runs/walks, temperature metrics wrong

Former Member
Former Member
Along with getting "Bike Cadence" stats for runs and walks, I'm seeing GC producing incorrect temperature readings (from a Tempe.) The Average temperature is often outside the span of the minimum and maximum temperatures recorded during an activity, which is mathematically impossible. Example screenshot below:

(Also shows bike cadence for a walk. Minimum temperature was 71.6F, maximum temperature was 73.4F, yet average temperature was shown as 70.9F.)
  • Here I have the same problem with cycling cadence on running/hiking activities. Anyone has any thoughts about why could it be happening?

    Thanks!
  • Yep! Most likely that Garmin has been making adjustments to Garmin Connect. If you see problems, report them to Garmin Support through the proper channels.
  • Former Member
    0 Former Member over 8 years ago
    We appreciate the discussion on this topic. The Garmin Connect team is aware of the issue where Bike Cadence is being displayed in the Stats section, and is already working on correcting this issue.

    @[email protected], we had not seen reports of the temperature data displaying incorrectly. We have escalated this to the Garmin Connect team for further investigation.
  • Former Member
    0 Former Member over 8 years ago
    Thanks, GFM1011. Here's another example of the average temperature being outside the bounds of the minimum and maximum from today.

  • Former Member
    0 Former Member over 8 years ago
    I experienced this again today, and may have an explanation. In the image below, both the temperature graph and the textual average/minimum/maximum are shown. The text shows the average temperature as 71.2, the minimum as 75.2, and the maximum as 77.0. But looking at the graph, there's a period of time at the beginning of the activity where the temperature shows as a non-viable 32 or so degrees. So perhaps the min/max calculation rejects that obviously out of bounds number, but it is taken into account when calculating the average temperature during the activity.