Garmin TempeVersion 1.0 Connect IQ

Thanks for your feedback!
How long did you wait? I tested it several times with my FR920XT FW 5.25 and it needed max 10 seconds until connect.
Maybe you delete the Tempe setting files on watch. Go to Garmin->Apps->DATA and Garmin->Apps->SETTINGS to delete the Tempe files.
Can you please attach the log file? Before please create a <APPNAME>.txt in Garmin->Apps->LOGS and start the app.

Thanks,
Daniel

-------------------------------------------------

Could you send me tempe app 1.2 version before fixing this issue? (attach file)
I don't have anymore the 1.2 version. (included negative temperatures); I just have 1.1 version.

Thanks.

--------------------------------------------------------------------------------------------
Hi,

Even with tempe app 1.4 version, same thing.
I waited for more than 2 minutes without success and several times too.
This is the log : I deleted tempe files before starting the app.

Thanks

Thanks, the log file helped a lot.
I saw that you received a channel closed (MSG_CODE_EVENT_CHANNEL_CLOSED) event. I think in cause i used GenericChannel.close(); when restarting the sensor. I removed the close() call and used only the release() followed with an init(), setConfig() and open() call when restarting the sensor.

Can you please test the attached version?

Thanks a lot,
Daniel

Thanks, the log file helped a lot.
I saw that you received a channel closed (MSG_CODE_EVENT_CHANNEL_CLOSED) event. I think in cause i used GenericChannel.close(); when restarting the sensor. I removed the close() call and used only the release() followed with an init(), setConfig() and open() call when restarting the sensor.

Can you please test the attached version?

Thanks a lot,
Daniel

-----------------------------------------------------------

Hi,

doesn't work with your new version

back to 1.0 version : please send me 1.2 version

Thanks

Thanks, the log file helped a lot.
I saw that you received a channel closed (MSG_CODE_EVENT_CHANNEL_CLOSED) event. I think in cause i used GenericChannel.close(); when restarting the sensor. I removed the close() call and used only the release() followed with an init(), setConfig() and open() call when restarting the sensor.

Can you please test the attached version?

Thanks a lot,
Daniel

1.4 production version is working better than the last version. Identifies on first pass for me more than it ever has.

Tempe_FR920XT Beta version

Thanks, the log file helped a lot.
I saw that you received a channel closed (MSG_CODE_EVENT_CHANNEL_CLOSED) event. I think in cause i used GenericChannel.close(); when restarting the sensor. I removed the close() call and used only the release() followed with an init(), setConfig() and open() call when restarting the sensor.

Can you please test the attached version?

Thanks a lot,
Daniel

Hi,

Tempe_FR920XT.prg doesn't work : see the attached file

back to 1.0 version : please send me 1.2 version

Thanks

Question about Tempe in general.

I'm reading this thread and reading about the pairing by Ant+, and it makes me wonder...

If I enable "Sensor.SENSOR_TEMPERATURE", will it use the Tempe if it's configured in the firmware? (like you enable a FP or HRM).


if it is a "sensor" as far as CIQ is concerned, it seems an app like this can be done without directly accessing Ant+.

Ok, I just looked around the vivoactive. In settings>sensors, you can pair with a Tempe, and for data fields, you can select Temp, Temp max, or Temp min.

No app needed. What am I missing here? Having an app that does this outside of an activity? (the temp should be availability by way of the sensor module..)

I might invest $25US and get one and see what it can do...

Ok, I just looked around the vivoactive. In settings>sensors, you can pair with a Tempe, and for data fields, you can select Temp, Temp max, or Temp min.

No app needed. What am I missing here? Having an app that does this outside of an activity? (the temp should be availability by way of the sensor module..)

I might invest $25US and get one and see what it can do...

Yes you are right. For Vivoactive you can pair the Tempe via System Sensor settings and access the values with the standard data fields in your activities.
But for the FR920XT you have no chance to pair the Tempe via System Sensor settings. So we have to go the way via a ConnectIQ app.

The sensor module only returns the current temp. But the Tempe has a 24min and 24max value too. So we have to access the temp directly via ANT+ module.

curious. How come it is not available for the 920xt?

I implemented the Tempe and got a user reports that it works as expected on an VA but not sure of the rest. The F3 has a built in temperature (only accurate if you don't wear the watch I guess)

Yes you are right. For Vivoactive you can pair the Tempe via System Sensor settings and access the values with the standard data fields in your activities.
But for the FR920XT you have no chance to pair the Tempe via System Sensor settings. So we have to go the way via a ConnectIQ app.

The sensor module only returns the current temp. But the Tempe has a 24min and 24max value too. So we have to access the temp directly via ANT+ module.

I second Nikeow's question. Why isn't it available as a system sensor on the 920? And what about the F3, Epix, etc?

For the 24min and 24max, does the Tempe have a power off mode, and are these only values for while it's powered on, or is it always on? Can't 24max and 24min be added to the access provided by the sensor module? The va has datafields for 24max and 24min, so the firmware must already have the info, it just needs to be exposed.