Heart Rate Stuck on 66

Mine is still stuck on 66

It's odd is that this is a problem for SOME people but not for others.

When I first got my watch it'd do the 66bpm lock when taking it off the charger. Easy to clear with a power cycle.

It hasn't happened even once since applying the WHR 2.40 update.

I'm sure it's annoying to have it keep happening, I hope they get it fixed for the instances the prior fixes didn't address. (suggests there may be multiple causes?)

Still on 66 after the update.

Did the updates and patch and my 235 still goes to 71 or 72 when checking my HR. Retuning it today just like I had to do with the Vivosmart HR with the same problem.

I thought Garmin made decent prof]ducts with good customer service. You learn everyday.

None of this works. Heart rate still stuck on 66

I have tried your update 3 times to no avail.

Return/exchange the watch for defective hardware.

BTW this is a user to user forum. You'll need to go to support.garmin.com if you want to actually contact Garmin Support.

Any foolproof solution yet?

So I just started using my 235 today - went for a run and things seemed fine.

Power cycled it and now I am getting the HR stuck at 66 issue.

I am on the latest updates.

What can be done?

Thanks!
-Jason

Unfortunately I've now become another member of the stuck at 66 club.
Watch has been working brilliantly, updated as soon as I received it, just yesterday it crashed however after having a fair few notifications fly in and after a reboot I'm just stuck at 66BPM

Contacted Support but no response yet - less than ideal when it's such a new product!

Both the 235 and Vivosmart HR have similar problems. Do not hold your breath waiting on an update. Garmin's update actually broke my VSHR

When the HR gets stuck on my 235 it usually works to set the automatic HR to OFF and then back ON again.

Also I've noticed it's more prone to getting stuck if the band is on too loose.

I had been successfully using my 235 since the end of December. I never had cadence lock issue, the 66 HR issue, or any of the other common issues (it worked just fine on my intervals). The only issues I had, sporadically, was it not registering sleep at all, or not registering it correctly, and it never automatically syncing with the app.

All that ended last weekend. In a span of two days, it didn't record ANY sleep data, the HR got stuck at 66 until I rebooted the watch, the HR during my run spent about 10 minutes sub 90 bpm (not even close to reality). I had one week left to return the watch to Amazon and I sent it back yesterday and ordered a TomTom. I have a TomTom Runner, which I really liked, but it had a couple of quirks that were annoying. Well, the Garmin actually has more quirks and given the big cost differential, back it went. If this were a $100 watch, I would think differently (heck, maybe even a $200 watch).

Got my 235 a couple of weeks ago and just had the stuck at 66 bug. I'm on whr 2.5

Does anyone know - is garmin aware of this, are they fixing it?