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

Just adding my voice to the disgruntled ..............

Having similar issues with my VA3, It all seems to be working just fine and then the HR reading drops to 70 and takes anything from a few seconds to a few minutes to return to normal.
I have a Mio Fuse with oHR sensor and it has never missed a beat in the years that I have had it paired with either my phone (Samsung S-Health) or my Oregon 750.
When the VA3 is working the readings between the two units is just one or two bpm.
I decided to switch to the Garmin as my step count, HR data and tracklogs were all in different apps and devices and I wanted an all in one solution.
For the most part I am very happy with the VA3,hope that they get the issue sorted soon.

ciq.forums.garmin.com/.../1335044.jpg

Just adding my voice to the disgruntled ..............

Having similar issues with my VA3, It all seems to be working just fine and then the HR reading drops to 70 and takes anything from a few seconds to a few minutes to return to normal.
I have a Mio Fuse with oHR sensor and it has never missed a beat in the years that I have had it paired with either my phone (Samsung S-Health) or my Oregon 750.
When the VA3 is working the readings between the two units is just one or two bpm.
I decided to switch to the Garmin as my step count, HR data and tracklogs were all in different apps and devices and I wanted an all in one solution.
For the most part I am very happy with the VA3,hope that they get the issue sorted soon.

It's still the biggest bugbear for me and my VA3 and given how long Garmin are taking to address it worries me that they even can.

It's still the biggest bugbear for me and my VA3 and given how long Garmin are taking to address it worries me that they even can.

Yeah this looks more and more like true. Despite Garmin promised (asked us) fix in update, update come and go with cosmetic fixes that no one (okay, I am sure those fixes are legit for someone) does not really care. My worries are growing and growing.

And then there was tonight's hike after work ................. no blips or issues.
This was the trip up - the one coming down looked the same.
The only settings change I made was to turn off broadcasting my HR during an activity - I had turned it on in order to make a comparison file on my phone on previous hikes.

ciq.forums.garmin.com/.../1335479.jpg

And then there was tonight's hike after work ................. no blips or issues.
This was the trip up - the one coming down looked the same.
The only settings change I made was to turn off broadcasting my HR during an activity - I had turned it on in order to make a comparison file on my phone on previous hikes.

So you are saying that turning off broadcasting of HR will save us? Well, I am off to my trainer today. Just to be sure I am using ANT+ Cadence and Speed sensors.

I would really like to be able to say that for sure, but I haven't had the device for long enough to be sure, so it's just an observation for now.
I don't use any sensors though. I will go again tonight in the hope of a repeat performance ................and hopefully a longer hike.
Had to cut it short last night because of a mountain fire.

I would really like to be able to say that for sure, but I haven't had the device for long enough to be sure, so it's just an observation for now.
I don't use any sensors though. I will go again tonight in the hope of a repeat performance ................and hopefully a longer hike.
Had to cut it short last night because of a mountain fire.

The problem this Forum was created for has thing to do with Broadcast HR I do not broadcast HR.. The issue has to do with ANT+ sensors dropped as the OHR drops.If you are not using sensors then you would not see this problem.

The problem this Forum was created for has thing to do with Broadcast HR I do not broadcast HR.. The issue has to do with ANT+ sensors dropped as the OHR drops.If you are not using sensors then you would not see this problem.

Ermmm .... I am seeing the HR dropout as others have posted - even if it is without ANT+ sensors involved - so it is a common problem that I am seeing, it just manifests itself under a different set of conditions..
So there is an issue, even for those that do not use ANT+ sensors and perhaps turning off broadcast may assist some folk.

So tonight I managed a longer hike, still no blips ..............

ciq.forums.garmin.com/.../1335897.jpg

Ermmm .... I am seeing the HR dropout as others have posted - even if it is without ANT+ sensors involved - so it is a common problem that I am seeing, it just manifests itself under a different set of conditions..
So there is an issue, even for those that do not use ANT+ sensors and perhaps turning off broadcast may assist some folk.

So tonight I managed a longer hike, still no blips ..............

That is certainly good news for you and others that do not use ANT+ sensors. I verified that HR broadcast is off on my watch, and never has been on. It is off by default. So for those of us that use ANT+ and OHR, we are getting dropouts, not only with the HR, but with the ANT+ sensors connections as well. I am thinking that the dropouts of the HR is causing the sensor drop outs. I have seen some posts that say say when they use an external HR sensor, the problem does not occur.

While I had to skip trying it (despite my promise), I can attest that I am using watch on my trainer with Speed, Cadence and external HR sensor and still seeing those drops in ANT+ connections. Not as often as I would see it with internal HR, yet it is still there. So yeah, you straighten up point - with external HR there are no HR broadcasts from the watch, obviously. Yet drop-outs are happen. It i somewhat more difficult to prove/spot, since graph just drops to 0 and you can argue that I simply stopped pedaling, yet it is there.