Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Lactate Threshold detected on Forerunner 965 but it is not updating in Garmin Connect

Stefan
over 2 years ago

Hi,

Lactate Threshold detected a couple of times on Forerunner 965 but it is not updating in Garmin Connect. I notice this issue after I upgrade my watch from FR945 to FR965. I still use the same Garmin HRM-RUN (red one) cest strap.

The last Lactate Threshold I can see in Garmin Connect is missing heart rate value and probably is from older FR945.

My current setup is:

1. FR965 with firmware version 4.19

2. Android 12 on Samsung S10e with One UI version 4.1

3. Welcome for any email enquiries

4. You may access my Garmin Connect account for analysis what's going on

4. Located in Romania

 

  • 0 over 2 years ago

    Thanks for sharing, Stefan. This topic has been escalated, so it's been under deep investigation. May I have permission to reach out to you via email, so I can add you to the report?

  • 0 over 2 years ago

    Same problem on multiple watch models.

    It was briefly fixed in the recent 955 betas but they broke it again when they released the final update (v15.19). 

  • 0 over 2 years ago in reply to Garmin-Sierra

    Yes, you may contact me via email.

  • 0 over 1 year ago

    I’m also currently experiencing the same issues on my forerunner 965 running the same software version. 

    any fixes yet? 

  • Former Member
    0 Former Member over 1 year ago in reply to woolfale

    as a workaround

    have a look on the watch in 'user profile / heart rate & power zones / heart rate'

    • when lthr is not updated here set it manual and sync the watch

    there is also a difference between outdoor team en fitness team how the watch stores the new lthr inside the fit file

    • outdoor team, the new lthr zones zones are stored in the same fit file as when the lthr update occurred
    • fitness team, the new lthr zones are only visible in the fit file after the next activity, sloppy ?
      • I do not use Garmin Connect Mobile or any data sync from watch with Connect

  • 0 over 1 year ago in reply to jambongris

    Has it been fixed?

    I'm experiencing the same...

  • 0 over 1 year ago in reply to RockBastard

    LTHR auto-detect began working again for me recently, maybe 5-6 weeks ago.  

    No issue at all anymore. I had been syncing directly from the watch over wifi for a while as it seemed like Bluetooth syncing may have been part of the issue but I went back to syncing over Bluetooth and I’ve had ~6 LTHR auto-detect updates going back to the beginning of October and they always show up in Connect.

    Note that I have a FR955.

    Actually, come to think of it, it may have been around the same time that I upgraded my phone from an iPhone 8 to and iPhone 15. If that’s the case, maybe the Bluetooth syncing on my old phone really was the issue.

  • 0 over 1 year ago in reply to jambongris

    OK, thanks; I will try to pair it with my son's iPhone and see if that could correct it!