Unbalanced HRV since 15.77

Quite a few poeple are reporting this as per this thread. Software 15.77 bugs (Fenix 7X Saphire Solar 15.77) - fēnix 7 Series - Wearables - Garmin Forums

Want to raise this as im getting unblanaced HRV since 15.77 whereas before it was pretty stable. Looks like a bug or maybe a massive improvement on what was misreporting before?

thanks,

  • I'm monitoring my HRV since November, when I bought my F7x Pro (didn't have this metric before, on my old F5), but to me it looks like almost spot on. Meaning that every time my HRV is unbalanced I can pretty much tell why (cold, covid, too much wine, too much or too late dinner, bad sleep, overtraining etc).

    Likewise. I've been monitoring HRV since the feature first launched. No odd changes here for me with the new firmware. As Cane mentions, if it's unbalanced, it's been due to overtraining (or big training sessions late night), or illness.

    where garmins algorythm over-estimates HRV (it is consistent, but a couple of points above)

    Do you have a link to one of these reviews? Garmin simply average the variation between heart beats in milliseconds across your entire sleep duration. You'd have to try pretty hard to get this "wrong" given the simplicity of the calculation.

    The only thing I can think to check is that people's sleep windows are set correctly and the sleep start times on days were the HRV has gone weird are actually during a time when they were asleep. If that all checks out, take a look at your diet, whether or not you're drinking booze at night (that really messes with it), whether you were exercising late at night on those days which pushes recovery into your sleep time etc.

  • https://gadgetsandwearables.com/2023/04/16/garmin-vs-whoop-hrv-heart-rate-variability/

    here is one of the articles i've read, dont have time to find the videos. From the article you can se the HRV from garmin watch is consistantly higher (however the graphs follow each other quite well indicating a systematic error with one of the devices. Does not mean garmin is the wrong one). 

    I dont think hrv is a "simple" calculation. The watch has to get the variation correct down to a few milliseconds, which to me sounds quite diffucult when the watch only has an optical sensor

  • There are optical sensors that can sample at 10,000 frames per second.

    As for the Elevate sensor in the Fenix, you'd need to know the sample rate in order to determine if it's able to detect movement variations in the sub 10ms range. I'm sure Garmin's hardware engineering team have accommodated for it given how obvious the requirement is.

    My comment regarding simplicity refers to the algorithms used to compute variation. It's trivial from a software standpoint.