Tempe and Connect IQ - feature request

This is probably a SDK 2.0.0 thing, but I want to get it on the list!

I've had a Tempe for about a month, and it's a neat little device. As it's a standard sensor on the Vivoactice, it was simple to add to my walking/running/hiking app - it took longer to find a good place to display the temp on the crowded screens! It also means temperature data is in the FIT file, and there is a graph on Garmin Connect for each activity.

I also developed a "watchface-like" app that shows the time/temp/step data/move bar etc, with daily highs and lows for the current day (only from times the app is running though...).

The Tempe however transmits THREE pieces of info. The temperature, which is exposed in CIQ, but also the 24max and 24min, which aren't exposed in CIQ. I ask that all three items be exposed, as the data is already there...

I thought about adding my own ANT interface for the Tempe, in my "watchface-like" app, as is done in the Garmin Tempe App, so I downloaded it to try out.
Wow! each time you start it, it's got to do it's own ANT connections! And that takes time.

I know the 920 doesn't have native support for the Tempe, but for other devices, I think it would make sense if 24min and 24max were included in the "sensor info" call back. It would make things much easier for things like my "watchface-like" app, as instead of doing the whole "ANT dance" to get data the FW already is getting with a standard sensor.
  • We've discussed this some in the past (I think it's probably somewhere in this monster thread, but I haven't taken the time to look), and I agree that these should be included. For now, this can be done with a generic ANT interface. The Tempe app we made handles the connection itself precisely because the FR920 doesn't have native support, so I believe you could avoid that if you didn't support the 920.

    We have a larger task of improving sensor exposure in Connect IQ, and we're working closely with the positioning and sensors team to:

    1. Make sure we make everything available in the best way
    2. Get everything documented properly

    I'll open a separate ticket for your request because I don't think we have anything tracking your specific request, and I want to make sure it doesn't get lost. :)