Often, AlphaHRV freezes on my Garmin, it then gives corrupted data in AI Endurance:
For example. today, it froze just below 0.75 for almost the entirety of the run. So all stats like durability are inaccurate for this run.
I wondering what kind of impact it’s going to have on my zones detection and if there is a way to tell the AI to ignore it for this run in particular.
We do have a freeze detection (like you say AlphaHRV freezes often) but seems like we should improve it since this activity evades it. Could you please send me the fit file to markus@aiendurance.com ? Thanks!
Is AlphaHRV required for extra data or is it just a way to see it while on the run?
It depends on how you connect your devices.
I have a forerunner 965 and the hrm pro. If connect the hrm to the watch with ANT+, I get the advanced running analytics, which I want, but I lose precision on the HRV data. It’s a Garmin quirk. So i use alpha hrv app to connect the hrm to the app with Bluetooth which add a second, precise, feed of hrv data to the fit file.
If I were to connect the hrm band to the watch with Bluetooth, I would have a precise feed of HRV data and wouldn’t need the app, but I would lose the advanced running analytics.
So I connect the hrm band to the watch with ant+ and also connect the band to the app on the watch with Bluetooth.
It’s complex because Garmin is making it quirky.
You get all the same data from AI Endurance post run/ride analysis. alphaHRV is to see the data in realtime
