Connect IQ 2.1.3 SDK Available!

The SensorHistory and devices was something I noted a while back, with the note about 2.1.x and the f3 and f3hr which are 1.3.x devices.

What you can try is set the min CIQ to 1.3 and the f3 will show again..

In the simulator SH is always available as well as the 4 calls (getHeartRateHistory(), etc). You may want to just build something simple for the f3 that checks that SensorHistory is available:

var hasSH=(Toybox has :SensorHistory) ? true : false;


and display the results. If it's false, it's not available on the actual device. If it's true, you may want to check which of the histories is available:
using Toybox.SensorHistory as SH;
.
.
.
var hasHRH=(SH has :getHeartRateHistory) ? true : false; //for example



Hm, it´s displays always true.
Seems that the check didn´t work as well.

Are you saying the "has" for SensorHistory is true, but then for getHeartRateHistory(), it's false? That's the case if it's an f3 and not a f3-hr, as getHeartRateHistory() is available on on devices with a optical HRM. On both a f3 and f3-hr, you may be able to use getTemperatureHistory(), getElevationHistory() and getPressureHistory() though.

Both showed true.

I just write down the rusalt as text.
Maybe this was my fault.
I'm brand new in programming. So sorry for that.

What is the correct way to show the result?

On the watch the result is just a wihte screen.

So I believe it´s not working on the fenix3 at the moment.
Garmin please change this as soon as possible.

Thanks!

Played a little bit around

with this code the result on the watch is false.

//SenosrHis
var Sh= "";

if(Toybox has :SensorHistory)
{
Sh = true;
}
else
{
Sh= false;
}

dc.drawText((width/2) +20,centerYS-50,Gfx.FONT_TINY, Sh, Gfx.TEXT_JUSTIFY_LEFT);

So SensorHistory is not working with the SDK 2.1.3 even with 2.1.4.
Garmin please fix this now!!!

So SensorHistory is not working with the SDK 2.1.3 even with 2.1.4.
Garmin please fix this now!!!

Actually what it means is SensorHistory isn't available on the f3/f3-hr (1.3.x devices). It works on both the va-hr (all 4 types of history) and 735 ( only hr history) (they are 2.1.x devices - I've tested both). The api doc for SensorHistory is a bit unclear, in that it says it's available in 2.1.x VMs (on the watches) but lists devices (like the f3/f3-hr/235) that are devices with 1.3.x VMs (where it's not available).