Tempe Sensor keeps deactivating

I don't use the tempe sensor that much. But I remember having the same issue earlier this summer. So it was before 11.10

I own a couple of heart rate monitors (one HRM-RUN and one Tickr optical), speed & cadence sensors, a footpod and a Tempe.

The Tempe is the only one that is not being switched off after use by the watch since beta 10.75.

Are you seeing this with any other sensors?

Pedantically, the Tempe is never deactivated, it keeps transmitting all the time whether anything is monitoring it or not (it's not completely passive,  it frequency hops and responds to requests) - this is all about what the watch is doing, or not doing.

I have experienced a similar issue with my Stages Powermeters (on two bikes) at some pre 11.10 betas. I reported this to Garmin and they asked for the log file as this was obviously a known issue. Since 11.10 this problem is solved.

Maybe I did not explain the issue perfectly right, I am talking about the Fenix setting : Sensors - Tempe - Status on/off, after setting the status to "on" the watch will display the tempe temperature for some time, but will automatically toggle this setting to "off" after about one minute.

I thought that was probably what you meant, yup, we’re talking about the same thing. I don’t think it’s specific to the Tempe, it’s a general problem with some of the sensor pairings. What I see is slightly different, as they are turned off between one activity and the next and I need to turn them on in the sensor menu, but they are not turned off after a minute with the watch active.

Think I have the same problem with my Fenix Pro Saphire FW 11.10:

Between 2 activities, some or all my sensors switched off. Instead of "searching", my watch indicates in the settings menu "sensors" that they are deactivated. I have to activate them manually again.

Having this problem since several week (after updating to 11.10) I tried to analyse why this happen and realized that it happens after chagrin my watch.

Just using the widget won't keep the tempe connected.  It disconnects after a short time unless you are recording an activity.  And each time you use the widget, it can take up to a minute to connect,

If you are hiking, use the hike activity, which will keep the Tempe Connected, (as well as a HR band if you use that), or will put the OHR into a higher precision mode than just normal 24/7 mode

I think Pattoon’s is talking about, that the sensors are deactivated automatically instead of staying connected or searching...

I never had consistent and reliable connection to Tempe, even before v11. 

A bit of a frustration so I use 'AmbiTemp' on my Android phone (ANT+ capable) which connects and stay connected to Tempe.  Not ideal but at least an option for certain of my use cases.  (In fact, it will literally stay connected for weeks, tracking temp)

I know I come late to the party, but according to Garmin, this is by design to preserve battery:

https://support.garmin.com/en-US/?faq=OXy2ma8HD90xtJE9sQmUS6

"At the start of an activity or when you view the temperature widget, your watch will look for a previously paired tempe sensor and will connect the tempe if it is in range and powered on. Once you have concluded your activity or left the temperature widget page for more then 30 seconds, it will disconnect again to conserve battery. "

No, that is the intended behaviour, this was something different, where a firmware bug was switching sensors off. Normal behaviour is you go into the sensor menu and the status is Not Connected, switching to Connected when it’s found. You can manually set the status to Off so the watch will not look for the sensor in question. The watches were doing that spontaneously and you’d need to go into the menu to force the search to start.