Heart intervals broken on Venu firmware update (and now other devices)

Hi,

My app has been working consistently for quite a long period. Venu had a firmware update and I started to get reports of the app displaying zero results. The cause of this is that no interval data is being generated / seen by the app though BPM is being reported. A user has tried many other HRV like apps and they all FAIL as well.

I've tried various changes to the sensor handling to see if this fixes the issue to no avail. I am now in the situation that a) the simulator shows no issues and works perfectly every time (even with original code that stopped working after the firmware update and b) users are now in the situation that if they run the app twice then they will get interval/beat data. This remains the case for a period of time ie subsequent runs work every time and then reverts to having the app run twice.

These on device issues (simulator has no issues and no crashes) are almost impossible to debug now as the ability to read the LOG file has been removed (they no longer exist - someone said because of MTP file system). Either the simulator needs to get up with API and firmware iterations or there needs to be better tools for live debug. ERA doesn't report anything of course.

original code (has worked OK for months):

var _ans;

if (Sensor has :enableSensorType) {

Sys.println(">=CIQ 3.2 detected");

_ans = Sensor.enableSensorType( Sensor.SENSOR_HEARTRATE);

if (_ans) {

Sys.println("Strap enabled");

} else {

Sys.println("no strap");

_ans = Sensor.enableSensorType( Sensor.SENSOR_ONBOARD_HEARTRATE);

if (_ans) { Sys.println("OHR enabled");} else {Sys.println("no OHR either");}

}

} else {

_ans = Sensor.setEnabledSensors( [Sensor.SENSOR_HEARTRATE]);

Sys.println("Enable response ="+_ans);

}

Sensor.registerSensorDataListener(self.method(:onHeartRateData), options);

Note: sensors are disabled on exit of app.

Current code ( various versions of this have been tried with enabling both together and separately as here)

if (Sensor has :enableSensorType) {

Sys.println(">=CIQ 3.2 detected");

//_ans = Toybox.Sensor.setEnabledSensors( [Sensor.SENSOR_HEARTRATE, Sensor.SENSOR_ONBOARD_HEARTRATE]);

// USE enableSensor as it doesn't disable other sensor types

_ans = Toybox.Sensor.enableSensorType( Sensor.SENSOR_HEARTRATE);

Sys.println("Enable3.2a ="+_ans);

_ans = Toybox.Sensor.enableSensorType( Sensor.SENSOR_ONBOARD_HEARTRATE);

Sys.println("Enable3.2b ="+_ans);

// ONBOARD only works on > 3.2.0 devices

} else {

_ans = Toybox.Sensor.setEnabledSensors( [Sensor.SENSOR_HEARTRATE]);

Sys.println("Enable ="+_ans);

}

Any ideas welcome!!! This has broken 3 different apps.

Regards,

David

davidmct-g over 2 years ago in reply to jim_m_58

Thanks. I've found that

_ans = Toybox.Sensor.setEnabledSensors( [Sensor.SENSOR_HEARTRATE, Sensor.SENSOR_ONBOARD_HEARTRATE]);

returns [] in the simulator and [4] ie SENSOR_HEARTRATE on the watch and not [8] as expected ie OHR.

getRegisteredSensors returns not an iterator but an object containing and index and type. If you try to access them the simulator crashes.

davidmct-g over 2 years ago in reply to davidmct-g

Pretty sure this is now a firmware bug.

If I remove the enableSensorType for Sensor.SENSOR_ONBOARD_HEARTRATE and just set a listener then I get Intervals for the OHR source (after a longish delay of 10 seconds). The ANT strap works in either case.

var options = {
			:period => 1, 	// 1 second data packets
			:heartBeatIntervals => {:enabled => true}
		};
		Toybox.Sensor.registerSensorDataListener(method(:onHeartRateData), options);

pstoppani over 2 years ago

I'm seeing the same issue on the SQ2. No heart rate and not temperature data on the real devices. Works fine in the sim.

jim_m_58 over 2 years ago in reply to pstoppani

From what I see, the sq2 devices don't have a baro altimiter, and without that, no internal temperature sensor. You need to use a Tempe.

pstoppani over 2 years ago in reply to jim_m_58

Yeah my bad. Still, heart rate history isn’t working on the new FW.

davidmct-g over 2 years ago in reply to jim_m_58

Jim,

How do we raise this issue to Garmin? My watch built in HRV measurement is also bad now - also sleep, training readiness etc (Fenix 7x 11.28)

Regards,

David

jim_m_58 over 2 years ago in reply to davidmct-g

The bug report forum is the first step. You can also post in the product specific forums.

davidmct-g over 2 years ago in reply to jim_m_58

I've posted in the F7x forum. I can't raise a bug report as no active beta. Seems no option to create a new one.

jim_m_58 over 2 years ago in reply to davidmct-g

The bug report forum right here in CIQ:
https://forums.garmin.com/developer/connect-iq/i/bug-reports

flocsy🤠 over 2 years ago in reply to davidmct-g

And if you really want Garmin to know about the problem then after posting all possible details in the forum go to https://support.garmin.com/en-US/ql/?focus=topics and report it there in EMAIL!!!! by sending the link to the forum post. This way you'll (maybe) get some feedback, and know if/when they'll start to check the problem.