Check out my first activity.
HR drops to 63. The strap is the Garmin HRM-RUN. Less than a year old. Works fine on other garmin devices.
What's going on?
Is anyone else noticing the HR drops on other devices after pairing with the 520? I get the same drops on my fenix3 now. I've changed the battery on my transmitter but still see the drops during my workouts.
I'm also having problems with my HRM from Wahoo. The 520 won't pair correctly with the Wahoo Tickr. If it does pair it looses connection after 5 seconds. I'm 100% sure the problem isn't the Wahoo Tickr since it worked flawlessly with my 510 and it still works perfectly with other ANT+ or bluetooth devices. I deleted the HRM sensor and now it won't even recognize the Tickr anymore. Has anyone else had similar problems?
I got my Edge 520 today and have exactly the same problem with my Tickr. My Tickr works perfectly with 510, Vivoactive, iPhone etc but doesn't want to know about the Edge 520. The Edge 520 works fine with the Garmin HR strap I own. Maybe a firmware update will fix this soon?
Dear Me
Thank you for contacting Garmin Europe.
I apologize for the confusion caused.
Please be advised the the Edge 520 is not compatible with the HRM-Run as this Heart Rate Monitor is specifically for running watches. That is why it works perfectly with your Forerunner 620.
Please find the links for the compatible Heart Rate Monitors :
https://buy.garmin.com/en-GB/GB/shop-by-accesories/fitness-sensors/heart-rate-monitor/prod10996_010-10997-00.html
https://buy.garmin.com/en-GB/GB/shop-by-accesories/fitness-sensors/soft-strap-premium-heart-rate-monitor/prod15490_010-10997-07.html
If there is anything else I can help you with then please let me know.
It's not really good enough - especially for bike/run sessions or duatholon. Atm either lose running dynamics or lose heart rate on the bike. I guess the former is preferable but hopefully be a SW update soon to fix.
Wow - that is one of the most disappointing customer service responses I have ever seen. Clearly the 520 has a bug where it misparses the battery level message as a pulse message. Why won't garmin just fix the bug?