HRV Status calculating error

What looks like a calculating error for overnight average happened on my Instinct 2s after the 11.18 update February 20. It happens on the watch, because the watch calculates before syncing.

It took a while before I realized, but mid March I was sure, especially after the one March 14.

I got in touch with support. Again clueless, but finally agreed to send on to developers March 20.

In the mean time I asked around. I've found two with the same issue. I don't know what watches they have - if it's an Instinct 2 or not. They seemed unwilling to tell me.

By now I'm fairly sure my watch is again calculating correctly for at least a week, depressing though it may be.

I don't think my eyes are deceiving me, and I wonder if others have or have had the same issue?

The picture shows two days with dates and Overnight Avg/highest 5-min Avg. And then the graph.

Top Replies

All Replies

0 trux 8 months ago in reply to justasp

Can you check how the overnight HRV looks like in Garmin Connect? You have to enable the option Overnight HRV under the graph with sleep stages (on the right end - you may need to swipe the options to the side to get to it).

In my case, it looks all right and credible in GC, and it makes clear that the Y axis labels on the watch are misaligned.

0 justasp 8 months ago in reply to trux

GC gives the same graph and the values +/- correspond to HRV from my old polar watch worn on other hand the same night. It's just Garmin average value is somehow calculated wrongly.

It's definitely not the Y axis problem. And it is repetitive problem when my HRV should/is low.

If my HRV is higher I could get quite possible HRV average value from the first look:

0 7714909 8 months ago in reply to trux

I sold my Instinct. My 255s has a graph on the watch that is not affected by the Instinct display bug. I always check the watch first, and when the average is wrong, it's immediately obvious on the watch display. But it's equally wrong on the watch, it just doesn't show the average line, so I have to scrub my finger along the graph to find a place where the average is on the graph.

I still get bugs where even the spikes can't explain the average value.

0 7714909 8 months ago in reply to 7714909

0 justasp 8 months ago in reply to 7714909

So you getting faulty HRV average reading on FR255 till now?

P.S. again faulty HRV average from last night on Enduro 3:

0 7714909 8 months ago in reply to justasp

That particular photo was from May. I've neglected photographing the egregious ones lately. I will photograph the next one.

0 7714909 8 months ago in reply to justasp

The one from today illustrates that spikes (essentially artifacts) will give you the wrong average.

0 Jan_Mantau 8 months ago

I think the average calculation is correct but the graph on the watch is erroneously shifted, because in Garmin connect web the graph matches the average. On my watch the graph is shifted so much up that the calculated average seems to be the minimum nightly HRV:

In Garmin connect web the graph is consistent with the calculated average of 81:

0 7714909 8 months ago in reply to Jan_Mantau

Instinct has a display bug. My 255s does not. The dotted line is in the right place, but the average isn't correctly calculated. This is from this morning. There's no way to argue this is correct!

0 Jan_Mantau 8 months ago in reply to 7714909

How do you know it's the average that is wrong and not the graph?