[Request] temp sensor automatic option

Yes please!

+1 !!
Thanks

I came from F2, F3, F3HR and now I'm on F5X

I use the temp sensor from the very beginning but what I'm really missing is the same option as for the internal HR sensor
I want to use temp sensor data if sensor is available otherwise use the internal data

Today I have configured the temp sensor but most of the time it is not available because it is mounted to my running shoes,
As long I have the sensor connected everything is fine but most of the time, I see no temperatur data, because the sensor is not in my area.

Please introduce an option "automatic" as it is for the internal HR sensor

+1
The fenix 2 works the same though i.e. if you have the tempe to automatically connect you only get temperature readings when it is connected.

maybe a CIQ widget could do it just need to develop one unless one is already available

See "temps" in the app store link in my sig. A widget that will display the internal temp and also tries to connect to the Tempe. "Time and Tempe" looks like a watch face (but it's a watch-app), that will display the readings from a Tempe.

I've has no problem with the Tempe on the f5. It can be a bit touchy if it's a bit far/blocked from the watch. If you go to my facebook page, in mid feb, I posted a pic and details on how I attach the Tempe to whatever/wherever it works best.

+1 !!
I came came here to start raise this topic and glad to find I'm not alone... It must be such a simple fix but yet no change from the F3, please please please give an option of auto-

or as a compromise pressing start in the widget gives options (like barometer calibration in barometer) and select internal/ external temp- simples!

I guess I still don't quite understand the problem. If you have a tempe and it connects, it will be used. The thing with the Tempe, is it can take a minute or so to connect, and after that, it only reads the temperature every minute.

I just added the temperature field to a run activity, while I was a ways from the tempe, and it was showing the internal temperature. But as soon as I got back to the tempe, it connected and the DF shows the reading from that (it was easy to see as the internal temp can change more than every minute, and is also about 10F higher than the tempe (at least at this time of year and I'm wearing the watch).

I know on some devices the Tempe will connect faster (but have never heard exactly why), but every newer watch I've used (vivoactive, vivoactive HR, fr 230 and f5) take up to a minute to connect, but then the Tempe data is saved in the .fit.

The Tempe will only connect to the watch when something requests it to be connected. It's "all about the battery". It doesn't want to have a connection to the Tempe if nothing is looking for Tempe data. The Internal temp is used for the baro, etc, and there is no "ant+ radio" (battery issues) involved so it's always. available.

Yes, your guess is right, you don't understand.

What they want is the Temp Widget to default to the internal temperature when the Tempe is out of range. You know, like when it is on your running shoe in the shed and you are at work?

Yes, your guess is right, you don't understand.

What they want is the Temp Widget to default to the internal temperature when the Tempe is out of range. You know, like when it is on your running shoe in the shed and you are at work?

The "temps" widget I mentioned shows both, with a timestamp as far as last time it got data from the Tempe. The History shown for the internal temperature isn't saved by the firmware for a tempe, so you can't see a graph of that, and as a widget is a "quick view" thing and will time out after a couple minutes, it can't build it's own history. You want to see Internal and Tempe if it's available? Like I said, the "Temps" widget in the apps store does that.
The "temps" widget:

https://apps.garmin.com/en-US/apps/17580ca9-816e-4203-a6a5-002eb543c04a

If it's not doing something you want let me know and if it can be done (technically), I'll try to do it.

I think you still don't get it. Yeah, your ConnectIQ app does look promising, but the OP and supporters want the native widget to default to internal when Tempe is not connected. That is they want Garmin to change the firmware to do this. This has been an ongoing and frequent request from F3 users and now F5 users.

Think of it this way. It's like the HR widget. It's shows the internal HR sensor (that's the data it has). If you put on your HR band, it doesn't switch over to a Ant+ HRM, as first of all, it's not looking for one, and secondly, it wouldn't have the data to build the graph (at best, it would only have the data from when the widget was running, which is only a couple minutes worth. The Ant+ HR graph would be a bit better, as it xmits much more often (about every second) while the Tempe only Transmits every minute. You wouldn't want the watch to collect data from Ant+ sensors 24/7, unless you wanted to pay the prices in battery life, so it would have the history for the few occasions you switch to the widget.

Anothet app of mine (Time and Tempe) https://apps.garmin.com/en-US/apps/54e90766-dc58-4f42-b898-261a090949c5 does connect to the Tempe and stay connected as long as it runs, and it burns more battery than a native watch face, and in fact more than one that goes out to the internet and gets full weather data every 10-20 minutes.

I'm trying to explain what happens on the technical side of the native temperature widget "looking like"/switching to the Tempe when it's in range.

However if you want to suggest this to Garmin, you can use the this link to do so: http://www8.garmin.com/contactUs/ideas/

Think of it this way. It's like the HR widget. It's shows the internal HR sensor (that's the data it has). If you put on your HR band, it doesn't switch over to a Ant+ HRM, as first of all, it's not looking for one, and secondly, it wouldn't have the data to build the graph (at best, it would only have the data from when the widget was running, which is only a couple minutes worth. The Ant+ HR graph would be a bit better, as it xmits much more often (about every second) while the Tempe only Transmits every minute. You wouldn't want the watch to collect data from Ant+ sensors 24/7, unless you wanted to pay the prices in battery life, so it would have the history for the few occasions you switch to the widget.

Anothet app of mine (Time and Tempe) https://apps.garmin.com/en-US/apps/54e90766-dc58-4f42-b898-261a090949c5 does connect to the Tempe and stay connected as long as it runs, and it burns more battery than a native watch face, and in fact more than one that goes out to the internet and gets full weather data every 10-20 minutes.

I'm trying to explain what happens on the technical side of the native temperature widget "looking like"/switching to the Tempe when it's in range.

However if you want to suggest this to Garmin, you can use the this link to do so: http://www8.garmin.com/contactUs/ideas/

I don't mean to be rude but your continuing promotion of your widgets is not what the OP and others wanted in their original requests. You miss the point however good your apps are (not tried them so can't say). Garmin of course are aware of the issue as it was a lengthy thread in F3 and some had posted to ideas.