Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Garmin Tempe sensor connectivity for the Edge series

crt_hun
over 4 years ago

Hi All,


After I purchased an Edge 830 and realized that the Tempe sensor is not supported (weird) I wrote a Tempe datafield and a widget for the Edge series.

Datafield: https://apps.garmin.com/en-US/apps/bedd1447-4816-40a9-83e1-0ed22c5bbcc3

Widget: https://apps.garmin.com/en-US/apps/22dc8040-24d9-4a31-b8a2-d50cb4892482

Please, let me know if you have any issue with them and enjoy,

  • 0 over 1 year ago in reply to the-ninth

    Just add the data field to one of your pages. It'll show "searching" until the next time the Tempe broadcasts its readings then the Edge will show the temperature.

  • 0 over 1 year ago in reply to peteb478
    peteb478 said:
    Just add the data field to one of your pages. It'll show "searching" until the next time the Tempe broadcasts its readings then the Edge will show the temperature.

    Thanks, I'll try that - it will have to wait a few days though since I just sent my Tempe back. It shows wrong values, temperatures between -30 and -40 instead of the 15-20 we currently have (Celsius). Values are wrong on two different Garmin devices, so I guess the sensor is defective.

  • 0 over 1 year ago in reply to peteb478

    It just does not work for me, I waited for over 10 minutes, but the data field still shows "Searching...". The same in the widget. I waited for over 10 minutes, but no values are shown. On my Fenix the Tempe is connected and I can see data, so it seems to be active and broadcasting, but not on the data field/widget on the Edge 830. Any hints on how I can solve/debug this?

    Edit: I now tried a different data field, and that one works, after some time I can see values there, but not in the CRTTempeField.

  • 0 over 1 year ago in reply to the-ninth
    the-ninth said:
    Edit: I now tried a different data field, and that one works, after some time I can see values there, but not in the CRTTempeField.

    Although I am from HUN, so there is a big chance that I let a compatriot down, but I also use the same datafield for a while that you tried. Both for  Edge 530 and F6X. I prefer it to the native Tempe field on F6X, because a) you can set an offset linked to a specific Tempe b) you can set a tolerance time which excludes data in the beginning from the calculation of min/avg/max c) it shows the battery  level of my Tempes d) its data update frequency is higher than that of the native Tempe field.

    I have 3 Tempe devices, and without that ciq datafield I would have stopped to use it, because I hated applyin the offsets “in my brain” memorizing which one of the Tempes were actually used.