Difference between HRV on Fenix 6 and 7 Pro

The sensor difference appears to make a significant difference in HRV values recorded overnight. Specifically, my 7 Pro is consistently ~5pts below where my 6x was, given the same daily workout load and life choices.

Now this would not be all that big of a deal except there's no way to tell it to adjust, nor to clear it other than a full reset. I used the migration option when I got the 7 Pro which pulled all the data forward from the 6 and thus resulted in this, and its been close to three weeks.

I know that these values are relative anyway and not really taggable between people, but it doesn't appear that the watch is adjusting the "baseline" to meet conditions either over time -- or am I just not waiting long enough?

I could hard-reset but am not sure I want to do that since that, of course, erases everything else and then I have go back and set it all up again including the data fields and such which did come across.

Will this adjust if I give it more time or am I going to remain in "unbalanced" purgatory forever if I don't clear it and let it start over?

0 Duggs over 1 year ago

If you look at the baseline history there are slight changes in the max/min values which suggests it will "rebaseline" over time. I guess the 3weeks to get initial readings would be a good timeline to work to.

0 PeterW over 1 year ago

Two things, your 7 pro elevate HR is 2 generations newer than your fenix 6 and significantly more accurate. I would be inclined to believe your seven Pro is more accurate of the two.

Also, HRV baseline will adjust overtime but it takes several weeks to adjust

0 tickerguy over 1 year ago in reply to PeterW

I assume it probably is more-accurate, and its relative anyway. But -- the point is that it is penalizing me across the board on training readiness and such while objectively, on sleep quality and all the rest I can determine I'm "as healthy" as I once was and there's nothing going on illness or training-wise that is out of the ordinary. Never mind that it was a step-function change when I moved from one device to the other....

So I assume this is a sensor difference and I don't really care which is "right" -- but I do care that it's playing *** with other metrics. I'm curious if it will rebase or if the only way to address this is to hard reset the unit.