HR/ANT+ dropouts may be fixed with Sensor Version 5.8

While my ride was somewhat limited last weekend - one thing is certain - HR broadcast still not working (for me to NiteRider Rebel 8.0). But here is interesting note - while pedaling (did this purposefully on trainer - exactly where all problems observed initially) - saw message about speed sensor reconnecting (indeed it could be very much legit reconnect - sensor is on rear wheel) - yet can't spot it (should be there drop?) in the graph. More testing is due this weekend.

I’ve had similar disappointing experience. With exception of the ride I posted previously, hr broadcast to an Edge520 has still been a trainwreck of flat-line dropouts and “stuck” sub-100bpm readings. Interestingly I see many “phone disconnected/phone connected” notifications on the Edge.

Had some rides recently with a HR broadcast instability scenario that lead me down a train of thought that perhaps installed third-party watch faces which display HR data might impact broadcast stability. (several rides suffering from frantic broadcast failures after I added a new watch face and made no other updates)

As I understand it, these faces run even in the background, so one, or maybe all, may interfere with HR data routing in some way which results in a connected head unit (Edge520 in my case) showing "-––" null flatline HR data. Two-thirds the way through today's ride, frustrated by constant flatlines, I stopped and deleted all 3rd party faces and immediately saw a significant improvement in stability. Anecdotal Single Data Point caveats apply, but something I'm going to chase down further.

Bumping...

I'm having consistent cadence and speed sensor connection drops while riding on a trainer. I put fresh batteries in both sensors. SW Version 5.90 and Sensor Version 6.00. Am I the only one or have others given up?

I noticed that when i used my VA3 and Edge 820 paired to the same sensors (speed cadence and hr monitor) the VA3 tends to disconnects more often from the sensors compare to the Edge. Tried using the VA3 only seems to solved the disconnection.