Temperature widget with tempe not connected

I have a tempe that's registered as a sensor to my fenix 5.

When outside of activity, this means the temperature widget shows "Temp. not connected". If I want to see temperature trending outside of activity (and based on internal thermometer), I need to manually turn tempe off in the sensor pool and then remember to turn it back on before an activity.

Is there a better way to combine the tempe readings during an activity with a 24 hour view on temperature based on internal sensor?
  • My guess would be that Tempe transmits always, while foot pod and HRM only transmit when they detect activity. So to save battery, it transmits with longer intervals. But it is only a guess.
  • Do we have any possibility change config to connecting faster with tempe, when tempe is moving & connect already with hrm or footpod ?
  • No, because this is related to how tempe broadcasts and tempe settings can't be changed. If you read the post on previous page, that explains why the handshake takes longer (the "pulses" from tempe and the receiving on the side of fenix need to "align"). But once connected, tempe broadcasts every 2 seconds and connection remains more or less stable at least for me.
  • What do you want me to explain? I said "connection remains more or less stable at least for me". 3 ANT+ dropouts during a 2.5 hr run fit my definition of "more or less stable". Connection depends on watch placement, tempe sensor placement, battery status, weather, etc etc etc. The issue on the run you shared has absolutely no significance in context of any metrics you track for your run (avg temp, temp trending).