Fenix 5x and tempe

The Garmin tempe broadcasts once every 30 seconds, so if you connect in 5-10 seconds you are very lucky! I suspect that the f5X waits for a few readings before it considers itself connected. I too find this a little annoying and I'm sure my f1 reported connecting quicker. But the average connection time cannot be quicker than 15 seconds even if it waits for only a single message.

It can be quite variable how quickly the Tempe connects to my F5x, from just a few seconds to 2-3 minutes. I don't bother to wait for it, I just set off and it always connects. I don't mind that the first minute or so gives a completely different temperature to the rest of the activity. When the Tempe connects is obvious on the temperature plot in GC as there is a big difference in temperature between the internal F5x temp and the Tempe.

The problem is the fenix 5x shows nothing when i switch to it then takes long by ambitemp free it shows from last connection and 24h hour min and max temp in 0,1 units
The fenix 5x updates it self but switches back to watchface.
I use GearMin face already wrote to developer it only shows fenix 5x internal temp only not from tempe.
Please fix this or let users easy create there on watchface where you can use tempe bpm...
The options for own watchface are more then poor.

The Garmin tempe broadcasts once every 30 seconds, so if you connect in 5-10 seconds you are very lucky! I suspect that the f5X waits for a few readings before it considers itself connected. I too find this a little annoying and I'm sure my f1 reported connecting quicker. But the average connection time cannot be quicker than 15 seconds even if it waits for only a single message.

Not so. It transmits two messages alternating every two seconds, tedious details here. So if the 5x caught the first transmission from the Tempe, you'd have the full data in 4 seconds maximum. It takes longer because of the way the watch searches for the Tempe, switching the receiver on and off at intervals until it syncs to the Tempe transmission timing.

If the OP's S7 is syncing faster, it's doing it by turning the ANT receiver on for much longer, which uses more battery power - the Fenix design is very conservative of battery life.

Battery save should be users choice you have backlight settings for light with every button and gesture.
So i want a watchface with tempe and as much info as possible the GearMin is okay but it doesn't shows tempe only 5x internal sensor. When i switch to tempe it takes too long i have to turn light on and see if it has connected this costs battery life too.
So please garmin with next fenix 5x update let users create there on watchface with as much sensor readings as possible. If i'm in gps or ultratrec i can see tempe is active the whole time, but only shown in garmin connect.

Not so. It transmits two messages alternating every two seconds, tedious details here. So if the 5x caught the first transmission from the Tempe, you'd have the full data in 4 seconds maximum. It takes longer because of the way the watch searches for the Tempe, switching the receiver on and off at intervals until it syncs to the Tempe transmission timing.

If the OP's S7 is syncing faster, it's doing it by turning the ANT receiver on for much longer, which uses more battery power - the Fenix design is very conservative of battery life.

Thank you for the correction McBadger and sorry to add to the "fake news". I am sure I had read many times in these forums that the broadcast was done once every 30 seconds, but I had not seen your 2015 post before today. What you state makes much more sense and explains why the fenix1 is much quicker than the fenix3/5 if they simply chose to open the listening window at the expense of using more power.

What is even more annoying is that on the f5 is seems to forget the data and sync time very quickly, so if you leave the widget and go back to it only a few seconds later you have to wait a long time again. On the f1 and the f3 this does not seem to be the case.

I have to say that I'd prefer the extra power usage to get a lock quicker. I frequently used to look at the temperature on my f1, but on the f3 & f5 it simply takes too long for the widget to be useful and now simply use the tempe as a method of recording temperature during activities. Sometimes the widget times out without ever getting the lock. Assuming I understand things correctly now, it would only take extra power to get the initial reading since after that point it will be in sync and only needs to on the receiver when the next update is wanted.

Do you know if it is the widget itself which controls when the receiver is turned on/off or is this down to the native watch code? i.e. is it possible that other temperature widgets could be quicker at getting the temperature if they use ant directly? Or is this part under the direct control of the native watch code?

What is even more annoying is that on the f5 is seems to forget the data and sync time very quickly, so if you leave the widget and go back to it only a few seconds later you have to wait a long time again. On the f1 and the f3 this does not seem to be the case.

In the app store link in my sig is the "temps" widget. Displays both the interval temp as well as the tempe if available. It also will cache the last tempe reading for up to 4 hours (it's configurable) and display that (with a time stamp) while trying to get a new reading.

What is even more annoying is that on the f5 is seems to forget the data and sync time very quickly, so if you leave the widget and go back to it only a few seconds later you have to wait a long time again. On the f1 and the f3 this does not seem to be the case.

Actually, this part is not true. All my watches, f1, f3 and f5 all drop the connection pretty quickly. I just did a few tests and had not used the f1 and f3 for a while so needed to put them on charge. It appears that while on charge, the watch does not disconnect from the tempe! Makes sense, but given watches are not really designed to be used while on charge I am a little surprised this logic exists. I wonder if there are any other functions which work differently when the watch is being charged versus running on battery alone. Widgets also do not seem to timeout while the watch is on charge.

Anyway, in general, I find that the f1 connects to the temp quicker than the f3 & f5 to the point that the widget is not very useful. I would prefer a higher battery usage to get the connection quicker.

Thank you for the correction McBadger and sorry to add to the "fake news". I am sure I had read many times in these forums that the broadcast was done once every 30 seconds, but I had not seen your 2015 post before today. What you state makes much more sense and explains why the fenix1 is much quicker than the fenix3/5 if they simply chose to open the listening window at the expense of using more power.

I'm on a one-geek mission to educate the forum :) There is a lot of misinformation about, and how it works is not intuitive.

I have to say that I'd prefer the extra power usage to get a lock quicker. I frequently used to look at the temperature on my f1, but on the f3 & f5 it simply takes too long for the widget to be useful and now simply use the tempe as a method of recording temperature during activities. Sometimes the widget times out without ever getting the lock. Assuming I understand things correctly now, it would only take extra power to get the initial reading since after that point it will be in sync and only needs to on the receiver when the next update is wanted.

Do you know if it is the widget itself which controls when the receiver is turned on/off or is this down to the native watch code? i.e. is it possible that other temperature widgets could be quicker at getting the temperature if they use ant directly? Or is this part under the direct control of the native watch code?

It's native - if you write your own widget, all you get to do is to tell the watch whether or not to look for ANT+ sensors, it's up to the watch how it does it. Even if you are coding for a custom sensor, all you can tell it is what the message transmission rate for the sensor is, it's up to the watch to hunt it down. I'd speculate that it turns the receiver on at a rate different from the message rate, and when it catches one, locks on to that timing. Which is fine for HR monitors, which will lock as fast as you can pick up GPS, but as you say, annoying for Tempe. The ANT documentation suggests you'd be listening for up to 45 seconds for a Tempe with the standard Garmin behaviour.

ETA: I was thinking about this on the way home. If all your sensors are on and ready to go, the watch could catch the lot in a few seconds with the receiver on continuously. But when to stop listening? It has no way to know which ones are currently around, and if you've started the gps but not moved your bike to wake up speed and cadence sensors yet, it won't find them until they are awake. But if it stays switched on continuously for a minute, it will use something like an hour's worth of battery, given that the duty cycle for ANT is pretty small. (An hour's worth with sensors on and GPS off, that is). So it doesn't make sense as an approach, other than for the Tempe widget where you could listen for up to 5 seconds then time out, assuming you've opened that widget by mistake or with the Tempe out of range.

Clip stable?

The clip to fix tempe on a backpack does not seem to be very stable. Any ideas on how to replace it or put tempe on a backpack without sorrows loosing it?

Thanks in advance

Marcus