Internal temperature (fenix 3) ?

With the 2.1.x SDK you can use SensorHistory.getTemperatureHistory(), which will return an iterator for readings for the internal sensor.
(I'm using it on a va-hr with the 2.74 beta FW), and I'm not sure about the f3. The 2.1.0 doc indicates it's a 2.1.0 feature, but you may want to try it.

That's the only way I've found to access the internal Temperature. (it doesn't seem to include data from a Tempe)

When you use "Sensor.setEnabledSensors( [Sensor.SENSOR_TEMPERATURE] );", that will enable the Tempe and get the Temp from it, but won't get the internal temp.

Hi Guys,

I was surprised to receive this complain from a user today. That the temperature data field of my app was not working in Fenix 3.

The strange part of the issue is that the temperature info is in the fit file and it is uploaded and displayed in Garmin Connect,
so I supose some bug in the firmware is preventing CIQ apps from accessing the internal temperature sensor.

I also remember testing it in earlier versions of the Fenix firmware and it displayed the temperature of the internal sensor correctly.
I am pretty sure about this cause it is the only watch I have that has an internal sensor, I had no option but to use it in my real device tests.

I will do more tests this week and will let you know the results.

Cheers,

Robinson

I don't have a f3, but I do have a va-hr with an internal temperature sensor. I've never seen the internal data from within a CIQ app (except when using SH.getTemperatureHistory(), and then it's only internal, even if a Tempe is being used).

With a Tempe in use, when the .fit is uploaded to GC, I see a Temperature in the corner of the map, as well as a graph of the temperature during the activity. If I leave the Tempe at home, I still have the temp in the corner of the map, but no graph. I read somewhere, that for the va-hr, that's what's supposed to happen. (internal temperature isn't saved in the .fit)

Using fitToCSV I don't see any temperature data without the Tempe, so it's not that the internal temp data is just being ignored by GC.

Do you see Temperature data in the .fit even if you don't have a Tempe? If so, is it the same FW as the user has? With the 1.3.x and 2.1.x VMs there could have been changes to some of the .fit (I've seen cases where the .fit is in a newer format - FIT 2.0)

Hi Jim,

I just atached a fit file. It is an activity I recorded with my app in a Fenix 3 running firmare 7.00
There is also a png showing how to verify the activity was recoded with my app.

Fortunately I used my app name as the name of the recorded activity, so if you open the fit file in any text editor and search for "workoutgenius" you will find it.

Considering that, I am absolutely sure the internal temperature recording behavior changed after firmware 7.00

ATTACH]36571[/ATTACH]

One important thing that I learned the hard way Jim, is that based on the behavior of one watch you cannot extrapolate the behavior of the others, despite the huge Garmin effort to keep the platform uniform.
I charge for my apps and because of that I bought various watch models to test them in the real devices. Be able to simulate the issues of my users in the exact same hardware and the same firmware they use is essencial to provide quality.

Cheers,

Robinson

What version of CIQ is on the f3 7.00 FW? I'll bet it's 1.2.x

FW drops after that may have a 1.3.x VM.

If the last digit of the FW is 0, it's production (7.00). Non-zero, it's a beta (7.01)

Settings>system>about should show you the CIQ version on a watch.

For me, I don't charge for anything, but for non-trivial things (well, maybe even watchfaces :) ), I only publish for devices I have access to (I have one or I know someone that has one, that can test or a done a beta for me)

You don't get the same download numbers as apps that support all devices, but you have happy users! :)

Jim

Fw 7.00 was a stable relase and it was running CIQ 1.2.6, exactly the same CIQ of the latest stable firmware 7.20 (the one is running today in my watch)

1.3.x VM has nothing to do with it and I hope when garmin finally releases if for Fenix, they fix the temperature bug.

https://www8.garmin.com/support/download_details.jsp?id=7623

Changes made from version 7.00 to 7.20:
Added support for accessing other data screens while in a swim workout rest interval.
Improved accuracy of distance and lap counting for Pool Swim.
Improved Auto Lock behavior to avoid locking while in use.
Improved the reliability of foot pod calibration.
Improved ETA and ETE estimates when navigating a course.
Improved label and background consistency across all widgets.
Fixed an issue where Project Waypoint was not using the system setting for bearing units. (Settings > Sensors > Compass > Display)
Fixed a potential issue where VO2 Max and Lactate Threshold estimates were being used incorrectly with Trail Run activities.
Fixed an issue where distance data fields for SUP were using incorrect precision and units.
Fixed a potential issue with high battery drain in watch mode.
Fixed a potential issue where the user was not given a warning alert on the last length of a swim workout.
Fixed a potential issue where certain multisport profiles were not available in the app list when navigating a course.
Fixed a potential display issue with one of the analog watch faces. (Requires Display update 3.50)
Changes made from version 6.90 to 7.00:
Added support for CIQ SDK 1.2.6.
Added support for Achievements. (Summary of personal records available after an activity is saved, and while still on the saved activity summary page.)
Added support to turn off activity monitoring Goal Alerts. (Settings > Activity Monitoring > Goal Alert)
Added support for post activity download of Heart Rate data from HRM-Tri and HRM-Swim sensors. (History > Activity > Download Heart Rate)
Added support to calibrate altimeter at extreme altitudes.
Added floors climbed history to the steps widget.
Added the heading bug to the elevation plot page.
Added support for saving a waypoint from the Dual Grid page.
Added support for displaying status of GPS EPO data to the About page. (Settings > System > About > Scroll to the EPO Status Page, Note: downloaded EPO data will not always be stored on the device file system)
Added support for viewing more than 100 Saved Locations on the device.
Added support for Walk App (Settings > Apps > Walk).
Added support for Swimrun App (Settings > Apps > Swimrun).
Added additional backlight settings: a 4 second timeout and a 5% backlight level.
Improved distance scrolling on the Project Waypoint page.
Improved Bluetooth to phone connection reliability. (Requires BLE/ANT FW 3.50)
Improved auto zoom during waypoint navigation.
Improved the readability of golf course names on the golf course list page.
Improved accuracy of floors climbed data
Fixed a potential issue where Intensity Minutes were not being calculated correctly for devices paired with a Heart Rate sensor.
Fixed an issue where the Auto Scroll setting was not available for paddle sports activity profiles.
Fixed a potential issue with Timer alarms not working as expected if Do Not Disturb was enabled.
Fixed a potential issue where the device could crash when saving a swim activity with HRM Tri data.

I really think you need to try again with one of the betas with the 1.3.x VM. There was a production release for the va-hr with the 2.1.1. VM (2.80) today, so 1.3.1 will be coming to the f3 in the very near term, and that could be the difference you see... (when 1.2.x came out there was new FW for every device about the same time (well, except the Epix, but that's a long story! :) )

With the f3, I'm willing to guess you have many users running beta FW (with the f3, they seem to do beta drops quite often!).

I'll bet that there will be production FW with the 1.3.x VM coming pretty soon (production FW with 1.3.x or 2.1.x FW has come out for other devices already this week, and with CIQ releasing 2.1.2 today, I'd expect other devices to release production FW sometime this week)

I hope so. As soon it comes I will verify if the temperature sensor issue is fixed.

I keep track of firmware version and CIQ of all registered users in my web site and I have to say that only a dozen in a thousand use beta firmware.
Most people have absolutely no IT knoledge nor interest in learning how their device works. They just want it to work properly.

Cheers,

Robinson