The watch prompt me to make the update, I did it, and then the heart rate is gone. In System I have WDR:0.00(0.00.00)
Where did the firmware for heart rate gone?
What can I do now? All the updates ware ok until now.
Please help!
Mine updated yesterday. I rebooted the watch after the update was done just to make sure everything was good to go. The release notes make me think they only made a change to correct the battery drain issue when the watch was off. So really I shouldn't be seeing any differences in the actual heart rate logic.
I went out for a 5 mile tempo run.
1 mile @ 8:00 min/mile
3 miles @ 6:50 min/mile
1 mile @ 8:00 min/mile
Oddly enough, it got a lock on my heart rate instantly, which it hasn't done lately. It usually takes at least 30 seconds. So far, so good.
Here's the graph:
The first 10-12 minutes were rough. The HRM numbers were way too low and it was pretty apparent it didn't really have a lock on my heart rate.
It finally seemed to grab on to my correct heart rate around the 12:00 minute mark.
From there it performed well, aside from a cadence lock at the 29:00 minute mark.
I was bragging up the HRM the other day, so hopefully this is just a fluke and doesn't have anything to do with the update. I'll keep testing, though.
Yeah, all I had to do was manually restart my watch, and toggle Bluetooth on/off on my phone.
But yeah, it's a weird oversight to not restart the watch after doing an update on the OHM.
That said... it reported my max heart rate at 99 when I went on a 4 mile easy run this AM. That is significantly low, it should have hit at least 130.
I really should dust off my chest strap so I can see just how accurate/inaccurate this is. I assume my old strap I used with my Forerunner 305 will work with this watch.
I have the same problem. Re-pairing does not work ("Connection failed"). Please fix this!
AFTER UPDATE: Oddly, some phone dependent widgets were good, but one was waiting for data (weather). Checked my Connect App on my phone and noticed that the device was showing "Not Connected". Tried to sync and got "Connection Failed". I finally rebooted my watch and everything was fine after that.
So did a run tonight, heartrate was quite a bit off... But was intervalling and didn't really pay attention during run so didn't refit the watch or anything...
Must re-evaluate during a normal, steady paced, run but this was pretty crappy. Hope it was just this run and not due to the update (as steady paced runs before this update worked great).
yep, mine was pretty much trash tonight, worst its been ever. hopefully just due to cold weather and intervals.... but right now i much prefer 2.60
How long were your intervals? Here it was 400m @5k pace / 200m rest...
Can imagine those are too short as the watch doesn't adjust too smoothly (understatement of the year).
Ugh, was really happy with 2.60... Hope I'm not thrown back again with 2.70.
*Edit* Thinking about it I would at least expect to see SOME changes. But after my first 2 intervals it doesn't even go above like 120bpm. I WISH I was that fit. Bah, always like a russian roulette game with this watch and also with garmins updates.
I agree, had the same problem then I turn off/on both my iPhone6 and my watch and problem solved.
Also 2.6 was a perfect crap, always blocking at 84bpm. I usually run with another person with the same watch and BOTH had the same problem. So far 2.7 is better, is not perfect but way better.
Did the update, got the 4.70 also, forced a hard reset and started my personal configs from scratch. Am hour ago went for a Les Mills RPM class and the HR was on target the whole time (compared with another watch+chest strap provided in the class).
https://connect.garmin.com/modern/activity/1174876565
So far so good, this seems to be a big step forward even with such a small changelog. Tomorrow I'll test some intervals workout in the treadmill and saturday/sunday a long outdoor run. From people reports in this thread regarding the OH sensor accuracy it seems Garmin finally hit the sweet spot for this watch :)
