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

Garmin Built-in Temperature Widget

Former Member
Former Member
I have a Garmin Tempe sensor paired with my 935. Earlier this morning I went on a bike ride and after it was completed the built-in widget read current temperature 44 degrees, max 73 degrees and min 41 degrees. This makes sense because I know the Tempe sensor dropped and reconnected during my ride and I'm assuming the max reading of 73 was taken from the internal temperature sensor. It's been a few hours since my ride and the sensor has been disconnected from my watch. I just checked the widget again and the current temp is reading 49 degrees, max 73 and min 41. So, my question is when does the data refresh? My assumption was since the sensor was disconnected from the watch for a few hours and I just connected that the three fields would all read the same until some time had gone by and there was an actual temperature change.
  • These values are stored on and sent by the Tempe and represent the min/max values of the last 24 hours. You can only reset them by removing the battery from the Tempe and re-inserting it.
    (edit/facepalm) You wrote that the 73 degrees can not have come from the Tempe so something else must have been happening. Maybe a soft reset of the watch (off/on) resets it.
  • The 24hr max of 73, was from sometime in the last 24 Hrs. The min/max values aren't from just when it's connected - they're from the last 24 hours.
  • Former Member
    0 Former Member over 7 years ago


    So, are you saying the 73 degree max didn't come from the internal sensor? Does the built-in widget take readings from an external sensor only? If that's the case I have no idea were it came from as the sensor was connected on my handle bars and made no connect with my body. The sensor wasn't used within 24 hrs of my ride either and was kept in my garage which hasn't seen a temperature higher than 50 degrees in weeks.
  • The native widget shows data from the internal sensor unless you have a Tempe paired (even if it's not connected). Then it only shows Tempe data.

    That's why I wrote Temps It caches the temperature from the Tempe so it will show for a bit if it's not connected, but will also show the data from the internal sensor (with a history graph)
  • Former Member
    0 Former Member over 7 years ago
    That's strange because if I open Garmin's built-in temperature widget I have no display until it pairs with my Tempe sensor. That leads me to believe the Garmin widget uses an external sensor and not the internal sensor. Are you saying it uses the internal sensor if a Tempe isn't paired? My widget just tells me "not connected" if the Tempe sensor is out of range, but I can't explain the 73 degree max if it didn't come from the internal sensor.
  • It's rather cold here (-1 to +5) and I use a Tempe that is always stored outside. During activities I do see spikes coming from the internal sensor (+23 for example) but these do never display on the temperature widget.
    If your 73 is gone after 24 hours after the activity, it was likely caused by the Tempe registering a wrong value, however rare that is.
  • TMK17 - if the Tempe is paired, the native temperature widget only displays it's data. I'm thinking the 73 is the "24 hour max" that's saved by the tempe.The Tempe saves a rolling 24 hr max and min.
  • Former Member
    0 Former Member over 7 years ago
    The native widget shows data from the internal sensor unless you have a Tempe paired (even if it's not connected). Then it only shows Tempe data.

    That's why I wrote Temps It caches the temperature from the Tempe so it will show for a bit if it's not connected, but will also show the data from the internal sensor (with a history graph)


    Unless my 935 or built-in temperature widget is broken, I don't think this is the case. The widget has never given me any readings unless it's connected to an external sensor. The widget will just show "not connected" if there's no sensor in range.
  • Unpair the Tempe and try again.
  • Former Member
    0 Former Member over 7 years ago
    You are right. I unpaired the Tempe sensor and now I have internal temp readings. Seems a little silly to me that once you pair a Tempe sensor that it will always look for an external sensor only. You'd think if it didn't find one it would give you the internal temp. Having to remove the sensor to get an internal temp doesn't make sense. Thanks for the info Jim.