Cadense Sensor

After 2.7 FW the VA3 picks up my GSC10 speed/cadence sensor when I initiate a bike activity, but I consistently loose the sensor about 4-8 mpg les into an indoor bike activity. I have yet to capture a complete ride. The heart rate freezes at the point of sensor loss. Definitely something seriously wrong with this watch and FW.

We updated the change log and added a note. Device team noted that "Improved ANT sensor pairing". I would recommend testing the Foot Pod and post back if you are still having issues.

I did not have problems with the foot pod before 2.70. Now I consistently loose footpod during activities (after starting with the footpod connected) while my FR230 on my other wrist does not.

After 2.7 FW the VA3 picks up my GSC10 speed/cadence sensor when I initiate a bike activity, but I consistently loose the sensor about 4-8 mpg les into an indoor bike activity. I have yet to capture a complete ride. The heart rate freezes at the point of sensor loss. Definitely something seriously wrong with this watch and FW.

I did a 16.5 mile mountain bike ride tonight and the speed sensor connected from the beginning and appeared to stay connected. I kept checking the sensor status and I didn't get any connect/disconnect messages. Might be worth trying a fresh battery; that fixed both cadence and speed sensors for another member here. I think they need more power then other Garmin watches to keep connected.

I tried a fresh battery (and discovered that my GSC10 battery rubber gasket/seal is broken ...) which did help to keep the connection from dropping out. Still hard to initiate the connection.

Hi from Sweden

I bought Garmin cadence sensor and speed sensor. I bike on my road bike on a trainer Indoor and I can get it to connect and I can se Booth the cadence and speed on the Watch, I had to alter the Watch what it could show. Sadly after a while on the bike it losses the Connection to Booth the sensors. After a while it might find the sensors again, but it is pretty worthless as it drops the Connection al the time. The sensor is only 2 months old, maybe old stock, old battery?. Maybe strong wifi in my flat, cancels the Bluetooth out? I have not tried outdoor yet. I have the latest firmware 2.80

I have a vivoactive 3 with the latest firmware (2.9)on it. I had an old speed ( with magnet ) and cadence sensor. The speed sensor seems to disconnect at various times when riding an indoor bike training. So I decided to buy a new speed sensor ( not the cadence, since I barely looked ai it ). Installed it to the wheel ax.... Paired fine ( after I removed the old one ) . Seems to connect ok when starting an exercise ( indoor bike ) , but then at various times again , disconnects... At that time I also noticed that my vivoactive 3 freezes. It goes back to the watch face ( time stops for the training ,no speed indication ) , then randomly flips to an other screen, and when it return to the exercise, it still freezes ( at no point I can get into settngs , or the right button doesnt do anything ). Then suddenly the exercise screen responds, seconds flows away, but no speed sensor detected . One long press to go to the settings, sensors --> manually connect the speed sensor.BUt no luck.. At that time there's nothing more to do than stop the training!!! Garmin pls give us some good info and a solution please. IMHO the old sensor is still fine, but there seems to be an issue with the firmware of the vivoactive ?? Is there a new beta version available so we can test the behaviour of the sensor with it ???

I did not have problems with the foot pod before 2.70. Now I consistently loose footpod during activities (after starting with the footpod connected) while my FR230 on my other wrist does not.

I've also had this EXACT same issue, and it began with (I think) the two most recent firmware updates, 2.7 and 2.8 - I'm on 2.9 now and having the same observation. What I'm observing in my runs is that the footpod constantly tries to 'reconnect', about every 1/2 mile or so, and also typically when I stop (I have auto-pause ON). I feel a buzz, look down and see 'footpod connected' - and in the span of about an hour run, that might happen 10 times. It always connects, so that's not an issue really, it's just annoying for this to be happening over and over. And over.

Thought I'd add this to the pile.

I opened a ticket with Garmin on this and they are aware and working on a fix. Not having the speed sensor is cutting down my mountain bike distances. Difficult to get any PR's or KOM's without it. :)

I purchased the Garmin ant+ Bike Speed (582660) and Cadence (619293) Sensors, the connection between my garmin vivocative 3 and the sensors drops several times when in use very frustrating , I have replaced the batteries as per support pages from garmin but still get the same issue. My Garmin vivoactive 3 SW version 2.90 GPS version 4.30, TSC version 2.10 , sensor version 5.50 WHR Version 20.03.24, connect IQ 2.4.1 apart from the sensor disconnects the vivoactive 3 works fine, The speed sensor is connected to the rear wheel as per guide (but does say on garmin support page to connect to from wheel ??) , I have also made sure that there is no magnetic /electrical interference nearby. waiting for garmin to get back to me . The watch seems to freeze when the sensors loose connection , its painful as you're trying to record rides... most of my rides seem to indicate that i have only done a few Km after an hours work out ..... garmin sort it out

Unfortunately is a known bug:-(
There are already several posts about this problem, both about the sensors dropping their connection and the watch freezing.
It really sucks.

It seems that everything works fine if you either:

• connect also an HRM band
  
• or, disable the speed sensor (use the GPS for speed readings instead) and only keep the cadence sensor.
  

These are not really solutions, though, as only a minority of users will be satisfied with it.

The best thing to do is contacting Garmin support (chat is probably the fastest way) and put pressure on them.
Hopefully they'll come up with a solution soon:-/