Hi all.
I experienced a couple of problems with the fenix 5 (I have 5s version) related to maxHR, lactate threshold (LT) and resting heart rate (RHR). they are all interconnected so I am listing them here:
1) maxHR, LTHR (lactate threshold heart rate) and RHR aren't automatically updated into my user profile, despite having automated-detection on.
2) It's impossibile to update them manually, either via garmin connect on web or on phone, or via the watch itself. After a lot of testing I figured out the reason is that the watch takes the garmin connect value for them.
Sub-problem 1: So if you update using your watch, that value gets overridden by the ones saved in garmin connect
Sub-problem 2: If you update using garmin connect, the way to do this is to go to "user profile">heart rate zones and then select "calculate heart rate zones based on" the thing you want to update the value for. So if you want to change your maxHR, you select "calculate heart rate zones based on maxHR". If you want to update your RHR you pick "calculate heart rate zones based on RHR". Same thing for Lactate Threshold. This allows you to insert the value and save it, which then sends it to your watch.
Now, the problem is that you can't update all 3 values together. As soon as you change one, the value you previously saved gets resetted to the minimum. So, for example, if I set up my RHR to 50, then do the same procedure to setup Lactate Threshold to 170, as soon as I do that, my RHR is defaulted back to 30 and this value is also transmitted to the watch.
I suspect point 1) has to do with the problem reported in point 2) (i.e. they are overridden by garmin connect values)
1) anyone experiencing this? If yes, any fix?
2) Is garmin aware of this issue? Are they working on it? If not, how do I report it?
3) I am worried this influences greatly all the stats. My watch thinks I have 30 RHR, 40 LTHR and 191 maxHR. All these values are wrong, and I fear they are the ones the watch uses to calculate many of my stats!! And I have no way to correct them!
So there you have it garmin, bug discovered, troubleshooted and source of bug is probably also discovered. Now go and fix it.
