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

HRM-Pro connected but not transmitting data

I recently replaced the battery in my HRM Pro and now it won’t transmit HR data to my Forerunner 935, Edge 830 or Zwift via BT despite each saying the HRM is connected. I’ve tried reinstalling the battery, and removing/reconnecting the sensor. This isn’t the issue of post-swim downloads because my FR and Edge are in range and seem to be connected during the workout.  I've let the HRM sit for a couple of minutes without the battery so any residual charge can dissipate and even flipped the battery for a few seconds before reinstalling the right way up. Any suggestions or idea what’s going on?

  • Hi,

    Not sure if it's related but also got problem since yesterday with my HRM-Pro sync in Ant+ with an Edge 530 and a Quatix 6. Both detect the HRM but without data or with suspicious data.

    As I said, all started yesterday during a bike ride. For the first twelve minutes HR was ok around 120-155 bpm and drop at 75-90 bpm for all the end of this activity (50 minutes).

    This morning, I wasn't able to took my HRV with my quatix. Also try in BLE with my phone and HR was totally wrong 120 bpm with peak over 200 while I was laying in bed. 1h hour after, starting a run HR at 75 bpm without data from running dynamic. So I disable ant+ to switch for optical HR and finish my run with those data.

    Battery is new as I change it one week ago, I did 8 activities without problems.

    AFAIK Garmin didn't update the firmware for HRM-Pro. I got the new one for the Edge last Monday but didn't saw any problems for HR that day. My quatix is also still in 19.20 version, I just noticed the watch was very slow during my run this morning (all is ok atm).

  • Did you get this fixed? Similar had happened to me today

  • Support changed mine, a know issue where the poor design let water enter :-/

  • I’ve gotten mine to work sporadically, but no permanent fix. Calling support is the next step. Glad they fixed yours.