[Request] temp sensor automatic option

I understand what's being asked but definitely do not want that functionality.

Few reasons: The internal temperature is useless. It's too high and not accurate. I don't want the readout to bounce back and forth between tempe and internal temp. Secondly, while the temperature graph from the internal temperature readout is nice, I understand why it can't be done with the tempe. The internal temperature sensor is always being logged since it is local to the watch, which gives you the nice graph -- the tempe, to achieve the same functionality, would have to power up and KEEP powered up the ANT + radio at all times to get the logging data necessary to generate that graph. The tempe itself has no storage and therefore can't provide "history" to the watch.

In an activity, sure, stay connected to the tempe and log the temperature, which is what the watch does. When not in an activity, no way.

The internal temperature sensor does give an accurate record of the internal temperature; it is just not the environmental temperature.

The native widget only shows this temperature when the Tempe sensor is switched off. Outside of an activity if you don't disable the Tempe sensor the widget says Tempe not connected. Some find that annoying and request (as in OP) that when disconnected outside of an activity or for some period (over 10 minutes say) it defaults to internal.

Frankly, it is of little user importance as it isn't a record of environmental temperature. The internal sensor is important for barometer sensor pressure algorithm but the user does not really need to see it. Of course if Garmin had not allowed users to see it they would have a barrage of requests to do so. Ho hum. Personally I disable the temperature widget rather than on/off Tempe sensor.

I see the native widget you're talking about now (I thought it was the same as on other devices, but it's not). Yes, it's waiting for a Tempe, and the whole "connection can take a minute" with the Tempe seems to be more than that at times. Now I'm seeing it's data, but I'm sure that will time out after being out of range of the tempe for a period of time and need to reconnect again, and it won't just keep the connection open.

So, it looks to me the widget is working, but you need to take into account the minute or more it takes the watch to get data from the Tempe. I just got a reading, it timed out and went back to the watch face, and now it's back trying to connect with no data, which it did happen about a minute later again. Maybe it should cache the reading for a period of time, so if you go right back to it, it can display that while trying to reconnect. (I know a widget that does just that, but I won't mention it! :) )

The watch doesn't request a reading from the Tempe. The Temp just broadcasts 24/7, and the watch listens for the data.

(I think I may have looked at the native widget before I has paired a Tempe)

I see the native widget you're talking about now (I thought it was the same as on other devices, but it's not). Yes, it's waiting for a Tempe, and the whole "connection can take a minute" with the Tempe seems to be more than that at times. Now I'm seeing it's data, but I'm sure that will time out after being out of range of the tempe for a period of time and need to reconnect again, and it won't just keep the connection open.

So, it looks to me the widget is working, but you need to take into account the minute or more it takes the watch to get data from the Tempe. I just got a reading, it timed out and went back to the watch face, and now it's back trying to connect with no data, which it did happen about a minute later again. Maybe it should cache the reading for a period of time, so if you go right back to it, it can display that while trying to reconnect. (I know a widget that does just that, but I won't mention it! :) )

The watch doesn't request a reading from the Tempe. The Temp just broadcasts 24/7, and the watch listens for the data.

Yes, this is exactly what the watch should do. It should cache the tempe data for a bit so if you get a reading, timeout, and scroll right back 5 minutes later it shows the previous reading. But really how long should you cache that value? I would imagine not very long at all. If you do cache it for too long it can give a very misleading temperature readout.

But that isn't what this thread is about. I don't want to see the internal watch temperature on that screen, ever. It's completely useless information if you are actually wearing the watch. If you had it mounted somewhere not on your body then maybe... except in that scenario you are probably actually in an activity, which means you are getting a constant stream of "good" data from the tempe.

In the widget I was told not to mention (:) ), It caches the last tempe reading for an amount of time the user can define (default is 30 minutes), but you can set in minutes how long (1-240 minutes). Or so that it never expires. (and it shows a time stamp from when the last reading was seen, so you can see how old it is).

It's not a native widget, but there's a reason Garmin allows 3rd party apps! :)

So you can see the last reading from the internal sensor (if available, based on the specific type of watch), and the last Tempe reading (that isn't expired) while it's waiting for a new reading from the Tempe. (that whole "it can take a minute or more" thing)

Jim, you're a trooper!

I am sure everyone is happy for you to mention it! Did anyone say you couldn't. Your first two postings were not recognising the issue of the poster. Or were your intentions just to hijack? Surely not. Anyway, poor forum etiquette aside, your widget is indeed promising--didn't I say so--but I would prefer Garmin to do the coding for the native widget disconnect defaulting.