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

Just to add my voice to this, I have had my VA3 for 3 months now and had absolutely no problems until the release of version 3.5. With that release, every single run I have done (4 of them on various routes and distances) has had my heart rate dropping to 70 and then slowly climbing again. I have no other sensors attached, HR broadcast off and the only app active while running is DozenRun. Something definitely broke for me with the release of 3.5 and sensor 5.8 that was fine before.

We are continuing to investigate this issue and have not stopped doing so since it was first escalated. The frustration of this issue is completely understood and we apologize for all of the inconvenience this continues to cause. For the users who are saying that they are no longer seeing this issue after the most recent sensor hub update (this update did not specifically have a fix for this in place), we may reach out to you to gather information to aid us in finding a permanent resolution.

It's nice to know it's still being worked on but seriously, how long are we meant to wait? anyone would think the VA3 was a prototype and we were all beta tester not retail consumers

I too have the same concerns. It's been over a half a year since the product was released and at some point you throw in the towel and caulk it up to a problem with the hardware. So does Garmin create a version 'b' of the VA3 or do they replace our units with another product known to work like a FR645 or FR935? I'm willing to pay the difference, I just need a device that works with a speed sensor and collects my heart rate data. I really love the VA3 other then the speed sensor disconnecting. I hope they either throw more resources/developers at fixing this issue or create a version b. I think everyone is at the point where enough is enough. I might suggest Garmin sending us really vocal users private BETA's where they are trying to fix this issue, so we can at least know we're not being ignored.

I share these concerns as well. While is true that Garmin has let us know that the issue is being investigated, there is no clue whether we are close to a definitive solution or not. And the fear of a hardware defect is concrete. What is going to happen when our devices will be out of warranty? It’s already been six months. Another six will go by fast. At that point Garmin could just say “too bad”. I thought about switching watch (fr645?), but I don’t want to be disappointed again...

I have had Vivoactive 3 for about 6 months and never really got the garmin speed and cadence to work without dropouts. A week ago I bought a fenix 5X and just tried i for 2 times a 25min indoor bike and not a singel dropout, that is strange, but I am happy that it finally works. I hope it stays that way

Well, knowing how difficult to develop modern device right from first time - I am with Garmin. Yet the fact people consider when everything works as it should right from the box - "strange" - is new low. Especially for such reputable company as Garmin.

I really want Garmin to succed with fix, I really like watch and think that Garmin marketing did well with creating great line-up of devices (where I am going - praising marketing!), yet concerns voiced above look valid and growing daily. So far the only thing I see that Garmin acknowledges problem, yet I am still not sure it is not systematic one.

IMHO, Garmin is not getting things fixed is because not enough people are saying enough is enough and returning the device.

I just received my 3rd VA3 replacement from Garmin last Monday April 16, but sad to say that all the issues i experienced with the previous 2 VA3's are still in my current watch these are the HR dropouts, Ant+ disconnection (im using a Garmin footpod) and Bluetooth disconnection (Iphone 7 plus).. this dropouts/disconnection goes all together and occurs like every 15 or 20 minutes while doing an activity. HR drops to 70-80 then slowly goes up. not really sure if a true fix is coming, because the 3.5 update has nothing to do with this long time VA3 problem.