Tempe widget ?

It's not a widget, but a watch-app. It looks like a watchface, and displays Time/Temp and other normal thing watchfaces do. (no seconds though)

https://apps.garmin.com/en-US/apps/54e90766-dc58-4f42-b898-261a090949c5

Accessing the Tempe from a widget can be a bit hard because the tempe only transmits once a minute, and widgets time out between 10 sec and 2 minutes based on the device.

That's not quite right. The Tempe transmits every two seconds, alternating two messages, which are updated every minute (so you only see the temperature changing once a minute). The slow transmission rate means it can take a while for the watch to pick up the transmission timing.

I've consistently seen it take up to a minute to fire up the connection (sensor already paired as a standard sensor) and get a temp reading. End result is that it can take up to a minute to see the data. (at least in Connect IQ - including when I'll looking for it every second).

As the Tempe transmits 24/7, I'd actually be a bit surprised if it transmitted every 2 seconds. Footpods and HRM, yes, they transmit often , but also have a sleep mode and are only transmitting when in use.

I checked this a while back using the ANT+ simulator software (which acts as an ANT receiver/recorder as well as a simulator) and an ANT stick plugged into my PC to record the messages coming off my Tempe (slightly more detail here), so I'm absolutely confident of what I say. Yes, it can take a long time to sync up with the message timing, but this seems to be something to do with the way ANT is implemented on the recent watches; over on the F3 forum there are a few messages from folks who've owned handhelds which pick up the Tempe more or less instantly (my Google skills are letting me down on finding a link to support that, sorry). You probably know this (well aware of your technical knowledge from your posts on the Connect IQ forum) but other readers may not: the watches search for sensors by turning the ANT radio on briefly at intervals until they catch a transmission, then use the timing of that to turn the ANT radio on synchronously with the sensor transmission through the rest of the workout recording, to conserve power. My speculation is they've come up with timing which makes the lock really slow for the Tempe which transmits every 2 seconds, compared with other sensors which transmit once or twice a second.

ETA: Other sensors generally transmit four times a second, going by the ANT protocol document.

Thanks for the info. Where the Tempe may transmit more often, in CIQ, it can easily take a minute (on some watches, it's as soon as the "Tempe Connected" toast appears from the FW), and it's often about a minute. Anyway, that's why I wouldn't do a CIQ widget for the Tempe...

Yup, I think you're absolutely right. The F3 has a built-in temperature widget, and that can easily take a minute to display the Tempe reading - just as well it does have a long timeout. I'm just nitpicking about the details of why it's a problem; got quite intrigued by the differences in lock time on different devices when I bought my F3.

FYI, on both the 23x and va-hr, even native apps can take about 1 minute to get the Tempe data, but I did hear from someone I know with a handheld and a tempe, and on it, the tempe data consistently shows in seconds after power-up. I wonder if on watches the FW waits for the first "new data" when connecting and ignores the repeats of the last minute's data or something..

Could be, indeed. Just been tinkering with an HRM and the Tempe, and I can see the HRM is transmitting at 4Hz and the Tempe at 0.5Hz; just taking about 8 times as long to find the Tempe as an HRM is another possibility. Maybe the handhelds just turn the ANT receiver on and keep it on until they find the Tempe, instead of gating it on and off. Puzzling! Thanks for your info, also.

I did a couple of experiments to look into that, and it doesn't look like it. It sends alternate messages of device capability and temperature data, and interleaves background pages every 129 messages containing manufacturer info, product info and battery status. So those last 3 repeat every 129*3*2 seconds is over 12 minutes, so it can't be waiting for those. All I see in the temperature messages is the value changing every minute. I used the ANT display simulator to catch messages while the F3 was searching, and the temperature message changed about 40 seconds before the F3 found the Tempe, which was before I started the search.

There is a comment in the profile that "The recommended search timeout is set to 45 seconds in the receiver. This allows sufficient time for a 0.5 Hz master to be found."

I'd always thought these devices were completely dumb, but it turns out you can request the background data pages from them and they'll then transmit them immediately. The F3, at least, isn't doing that, though.

I can send you the captured data if you're interested, pm me an email address if so.