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

Not fixed. I’ve sent another email. It was so bad yesterday and I rode outdoors. Also had crazy elevation.ciq.forums.garmin.com/.../1324413.png

Just to follow up, even with a ANT+ strap I keep seeing intermittent dropouts of the speed/cadence although it's not nearly as bad as before. HR data from the strap seems okay at least.

Its pretty easy to tell how many drop outs you had. (other then the sensor reconnect warning and the HR showing 80 every 5-10 minutes). Plug the watch in your computer USB and open the SNS_ERR.TXT file with Wordpad in the GARMIN folder. Count the number of Sensor Hub Resets. (I had 16 yesterday). Without the speed/cadence sensor connected, the HR works fine and I don't get any new sensor hub reset messages. When I've used an ANT+ strap with a speed sensor, everything has worked as expected so I've never looked at it afterwards. I'm starting to wonder if maybe our units are having hardware issues or if they all came from the same batch. I have the slate version and bought mine in early November of last year. I'm not seeing a large quantity of upset people posting on this forum on this issue so maybe theirs is working as expected? Garmin support recommended I wait for the next version of the firmware before replacing; they acknowledged that 3.30 did not fix everyone but hinted it fixed most people. Not seeing Garmin Joey or Blake very active on the VA3 forum like they've been on the FR645 forums to acknowledge the developers are investigating issues.

Hmm, you've described exactly what I see. While I have not tried to do indoor cycling without ANT+ sensors - watch fails (connection to ANT+, HR resets to 80 and height is somewhere over the rainbow) if I am using internal HR. That barely happens with external HR. Mine is also slate version and bought somewhere mid of November last year. Another thing - my bike computer never able to pick up HR ANT+ transmission from watch, but that can be blamed on computer (NiteRider Rebel 8.0).

Mine is black and stainless bought in December, but who knows how long it sat on the shelf.

We are aware of users who are seeing this issue with the latest system software and sensor hub and are investigating the cause currently. We understand the inconvenience this is causing and ask for your patience while we work towards a permanent solution. This thread will be updated when more information is available.

We are aware of users who are seeing this issue with the latest system software and sensor hub and are investigating the cause currently. We understand the inconvenience this is causing and ask for your patience while we work towards a permanent solution. This thread will be updated when more information is available.

That's really reassuring to see our issues aren't falling on deaf ears, thanks

We are aware of users who are seeing this issue with the latest system software and sensor hub and are investigating the cause currently. We understand the inconvenience this is causing and ask for your patience while we work towards a permanent solution. This thread will be updated when more information is available.

Yes - but remember that this problem occurred before the latest system software and sensor hub. The upgrades did not help at all. I have had a ticket opened since firmware 3.3. In fact had a ticket opened earlier but it was closed as they thought the problem was fixed. I bought the watch in December and have had this problem from the beginning.

JohnO1516 We understand the frustration with this issue and ask for your patience while we continue to investigate the cause for you and other users. There have been previous improvements made and I'm sorry if these have not resolved the issue for your use case. The issue in particular is one that I have previously been able to reproduce in house but I am no longer seeing this on my own vivoactive 3 in multiple scenarios. We are actively working to provide a permanent solution.