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

15.19: LTH still doesn't sync with GC

9610916
over 2 years ago

I just did a run with the 15.19 update and the watch detected a new lactate threshold which I accepted. However, after syncing with Garmin Connect, the new threshold did not show up in the app. 

So as far as I my case is concerned we are back to square one with this whole LTH mess.

Im still firmly convinced this has something to do with the presence of both a general heart rate and various "sport heart rates" for running, cycling and swimming on the watch.

I noticed that on the watch, the new threshold was automatically entered to the "Sports Heart Rate" for "Running", but the general LTH failed to update on the watch and still showed the old value. What's curious, the max heart rate is correctly updated both in the "running" and in the general category, but the LTH is not.

Since Garmin Connect doesn't even seem to be able do distinguish between or display different heart rates / LTHs for different sports, it takes the data from the general HR / LTH, which is not being properly updated on the watch.

I did an experiment now and removed the running, cycling and swimming heart rate from the watch, leaving only the general one. I will observe what happens the next time I get a LTH update.

Anyone else is experiencing this problem even after updating to 15.19?

  • 0 over 2 years ago

    All, 

    Thank you for your participation regarding this topic, I apologize for the disruption. It's been under deep investigation, but we do not have a fix just yet. I will update this thread when I know more.

  • 0 over 2 years ago in reply to 8980788

    Same here, had the 255 since December. I've never gotten a LTHR. Do you wear a Garmin chest strap? I use an Amazon special. It connects to the watch. But I'm starting to wonder if that's not the culprit. 

  • 0 over 2 years ago in reply to 8980788

    I use a Garmin HRMRUN. It worked w/ all of my other Garmin watches, but so far no LTHR on my 255. It doesn't matter what brand strap you use, as long as it outputs RR intervals. If your strap only outputs HR, then it can't calculate LTHR, because it needs RR intervals for LTHR calculation

  • 0 over 2 years ago

    Further update - I seem to be the exception here in that my 255M (ver.15.19)/Garmin HRM combo detects new LT HR & pace numbers and updates GC (iOS & web) successfully.  Last time it happened was on 1 June when I did a progression run. I did another progression run earlier this morning and new LT numbers for both HR & pace were detected and accepted on watch, then both synced ok to GC. 

  • 0 over 2 years ago in reply to AKL

    Today it worked for me too. Had a 4x4 run outdoors with the HRM Run strap, and got new lactate threshold values. This time I was asked to accept them, and the values synced nicely to the Connect cloud by WiFi.

  • 0 over 2 years ago in reply to neurogeek

    Finally broke down and bought a real HR strap, Garmin HR Pro Plus, watch is on 15.19. Went up a nasty hill on my long run and the HR went up. I have a new LTHR reading on the watch, I accepted it, and it showed up in Garmin Connect. So my issue was the cheap knock off HR strap. 

  • 0 over 2 years ago

    Another update: I'm 61(M) in south east England with 255M (15.19)/Garmin HRM Pro+ strap and did a 10Km slow run earlier today, average pace 6:47min/Km and average heart rate148 BPM (max164 BPM). Weather was sunny & quite warm at 21C.

    After the run, I was surprised to see the watch had "auto-detected" new LTH HR & Pace & Power numbers, surprised because I was running slowly though my heart rate was high due to the warm weather. I accepted the new numbers on the watch and the watch synced with my iPhone GC via Bluetooth. New LTH values were also synced correctly with GC (Web). 

  • 0 over 2 years ago in reply to 3573752

    Quick update: did a threshold run this evening with HRM pro and auto detected new lthr and pace. Accepted, synced and shows up in Garmin connect and watch. Problem seems fixed now - think needed one more lthr detection after the first one after the update above