Strange HR recording with Burner selected

TonyG

I have been getting some strange things happening to the recorded HR values when I use the Suunto + Burner app, the strangeness appears to be triggered when I pause the activity (on this occasion when I crossed a busy road).
couple of things I noticed when out on the watch.
the HR Zone outer circle got stuck on blue half way through the activity (zone 1) even though the watch was showing the correct HR when I was running 140 - 154 (zone 2 / 3)
and appears to be represented in the HR chart?? see below

but the zone values on the app appear to be correct as does the average Hr 142 for the entire recorded activity See above and below for zones %

the splits within the app i.e every 1km seem to be correct also except split 10 where 99 average was recorded (this is where I think the pausing of the activity triggered the strangeness) see below 2 images

the auto export to strava shows the recorded HR as it is in the chart and as such give average HR as 107 which is def wrong,
confused as to what has gone wrong here with the data
I have sent logs to suunto via the link in the app but didnt get any sort of reference number to share
I should add, this is the second time this has happened both when using the burner suunto + app.

Dimitrios Kanellopoulos

@tonyg do you have a link ? On Strava how does the hr look like?

Was that a belt ?

TonyG

@dimitrios-kanellopoulos The HR on Strava looks like the chart on SA and as such gives 107bpm Average,

here the link to SA,
https://www.suunto.com/move/tonygray190/61740232111b7c1dbf59247b
Strava
https://strava.app.link/vVnV2ZxLAkb

yes this was a chest strap

Interestingly I have just read on Facebook group a chap with same or similar issue
https://www.facebook.com/groups/SuuntoAmbit/permalink/4455281987897163/

Dimitrios Kanellopoulos

@tonyg was that a polar h10 ?

TonyG

@dimitrios-kanellopoulos yes!

Dimitrios Kanellopoulos

@tonyg please share with me in pm the link. I have a possible explanation for this if I am correct.

However I guess this is HRV / RR data issue.

It’s been explained a couple of times and I think if you load the file on QS you will see the same result.

The problem is that when the belt looses good readings RR data are only few creating a low heart rate.

But then I have the question. Did you see on the watch the correct heart rate but only later in the app you have this issue ?

TonyG

@dimitrios-kanellopoulos throughout the run I saw good Hr reading on the watch, only once did i see a low hr reading, and that was after pausing the activity to cross the road, when i un-paused it it showed 55hr but very quickly (10 seconds or so) climbed back to 147bpm (where it should have been).
apologies, what link would you like shared?

Dimitrios Kanellopoulos

@tonyg pm the link please.

Dimitrios Kanellopoulos

@tonyg will be taking a look next week though so take your time.

TonyG

@dimitrios-kanellopoulos sorry, not sure what link would you like pm’d

I thought I supplied them all in an earlier post.

zhang965

I’ve got some weird noise

Dimitrios Kanellopoulos

I found the issue.

Egika

@dimitrios-kanellopoulos and it is?

Dimitrios Kanellopoulos

@egika at some point it looks like the h10 stops broadcasting RR / IBI data (HRV) that we use to create the HR and switches to HR samples and quite a few HRV samples.

It looks like an h10 edge case (both users have the same belt) so I am not sure how this should be fixed

TonyG

@dimitrios-kanellopoulos would this be the case for all belts sold and used, I wasnt sure if all belts recorded or broadcast R-R data, so is the watch displaying a different value, as it was displaying the correct Hr Value throughout the activity and I was checking alot due to having this issue on a previous activity.
Is it related to using the burner app? or would a drop in R-R data have this issue regardless.
many thanks for exploring and discovering the issue.
T

Dimitrios Kanellopoulos

@tonyg not realted to burner. Just your belt stops broadasting RR / HRV and switches to normal HR.