This is pretty cool - could be a useful tool if you start seeing sensor drop outs

This is pretty cool - could be a useful tool if you start seeing sensor drop outs

At least you and me love them. And we expressed this love, since we have 6 Tempes altogether.
OK, my new hypothesis is that the Sensors are displayed in GCM if and only if:
- your sensor reports battery status
- you social security number's 5th digit is a prime
- the 7th digit of the sensor…
Tempe certainly deserves more love! It won't show as a sensor in this list, because the sensor ID of a Tempe is never stored in activity FIT files. But that has advantages; you can record data from more…
I've not mentioned the Tempe at all, I was talking about Stryd...!
Lol. Threading in here can be a bit hard to follow!
Think I’m now agreeing with you that the Stryd doesn’t show up in ANT.
I have two HRM Run units, different generations, and they both show up as footpods, so there’s that. The one I renamed shows that, the one I didn’t says Footpod followed by the ANT ID. I’ll rename that too to try to cut the confusion.
Think I’m now agreeing with you that the Stryd doesn’t show up in ANT.
One thing I've noticed which could be a coincidence - having paired the Stryd and a Wahoo Tickr and Polar H9 as BT sensors today, my watch has been losing 1.5% battery life per hour since just doing nothing, something I haven't seen since the 19.20 battery debacle.
Oh, that's interesting, can you please play with it more and then answer my question here: https://forums.garmin.com/sports-fitness/cycling/f/accessories-sensors/293175/cadence-sensor-bt-vs-ant
And this even more so interests me now because I was just about to but a Polar H9 to myself, so new important info is welcome...
Thx for the fonfirmation.
I have this sort of experience regarding Tempe. Occasional is a right word to describe it.
I lost my confidence when I found the thread in which Jim_m_58 stated that Tempe did not show battery info at all, because Jim always seemed to me a developer having exact info always.
Jim always seemed to me a developer having exact info always.
Jim is tremendously knowledgeable on Connect IQ - I can’t think of anyone who is more expert and I have a huge amount of respect for him. There are a few details of ANT messaging where he’s not quite as accurate, though he still knows more about that than most people do.
I’ll see if I can track the documentation down later, I think it’s in the files for one of the PC ANT monitoring programs rather than the FIT SDK
So I have just done about 2 hours indoor riding - I paired the Polar H9 by ANT for the first time to the Forerunner 255. I deleted all BT pairing yesterday from the Fenix 6 as the watch started battery drain even in smart watch mode outside of activities. Drain issue solved as soon as the new pairings added yesterday were deleted. There is probably a bug with a 'hanging' BT connection in BT/ANT/BLE so a BT session is left open on the watch when it should be closed.
I recorded on the F6 and 255 at the same time...

but the H9 does not show up in Devices - even though it transmits battery via ANT and watches even reported low battery status at the start of the first activity today.
.
Yesterday when I paired by BT it showed up very quickly (F9.56.71.CB.FA)
So I think if we want reliable battery reporting, we need to use BT, even if battery is reported in the ANT profile.
As I use multiple devices, for me I need to keep to ANT for multiple simultaneous connections.
I am the owner of FR945 but more or less the SW is the same as Fenix6 and I use Verity sense and RDP ant + and I see the battery, FP Polar ble and I see the battery, FP Zwift ble I don't see the battery, Tempe I really don't see the sensor in GC
OK, my new hypothesis is that the Sensors are displayed in GCM if and only if:
- your sensor reports battery status
- you social security number's 5th digit is a prime
- the 7th digit of the sensor's MAC address is not 1,4 or 8, except when it's 8 and the 3rd digit equals to 9- the 2nd digit
Mmhhh... Seems to have some some calculation in common with the algorithm used for the sleep tracking.......