Sensor Pairing and Connection Issues after 12.30

i did the reset & all garmin sensors worked ok but the stages crank arm was still the same, nothing i did would bring it back to the way it was. i dont use bluetooth on my phone but it is paired up to the unit & the bluetooth is switched off on the phone. i checked the garmin and it was saying it was enabled so i disabled the phone on the 820 & just been out to try. in nearly 3 miles it didnt lose connection once  so will see when i go on a longer ride. hth, still drains the battery fast though.

Although my sensors are fine during the ride, I noticed that the 820 is taking a lot longer to initially detect them after it starts up. Whereas, before the update, the Vectors and SCD would be detected as soon as I spin the cranks, it now takes about a minute before it beeps and reports them as connected. 

Downloaded 12.30 and I have had issues with it constantly loosing connection to my di2. Every few minutes it will say 'di2 found'. 
I have tried the following;

-Factory reset

-Added all the sensors again

-Deleted 820 and re-added the Garmin to the app

-Checked for any further updates

It seemed to work for most people, it didn't for me, so I repeated this twice.

Is there anything else I can try? Is it worth trying to add the old software 12.10?

Thanks

Hi  ajridermk

Try this way.

-Factory reset

-Update the unit via Garmin Express

-Added all sensors again.

In my (little) experience you don't need deleted and re-added the Garmin to the app and the last thing you have to do is added the sensors. At least is how it worked for me.

Turning off the bluetooth in my Edge 820 helped me.

Tried this and no luck. What old software version works best? Might install an older version

Check out my road cycling activity on Garmin Connect. #beatyesterday
connect.garmin.com/.../4764685163

Hi Matthew.

I'm hoping that this might be helpful in debugging the issue...

Yesterday I put my 820 on charge in anticipation of today's ride. It obviously powered up and offered me the firmware update. Without thinking I accepted it, quickly I checked to see if there were issues with it and then found this thread and wished I'd not accepted the update.

Rather than have a nightmare ride I followed the advice of a factory reset provided by user 3529307 elsewhere in this thread. Stupidly I didn't back up files so I had to completely reconfigure from scratch. I added all my sensors; Garmin HRM, Garmin cadence; Bontrager Duotrap speed & cadence (bike2), plus my Bontrager Ion 200 RT / Flare RT2 Lights. All ok so far.

Since I had the Bontrager lights the rear has always occasionally left the network and was replaced (the replacement does the same thing). So when I saw the usual message on my ride this morning I thought it was the rear light playing up. My eyesight not being what it once was I realised as the message came up virtually every MINUTE that it was the front light which was attached to the same mount as the 820. After 20 minutes it was driving me crazy so I stopped my ride, removed the front light in the settings and added it again. After this, it behaved perfectly. Although the rear light did still disconnect once later in the ride.

So in summary even with a clean config and the front light being added the 12.30 software was dropping connection until I removed and re-paired it with the head unit. Not sure if this is significant or not but just in case it's helpful this is my ride:

connect.garmin.com/.../4772763930

As I have shared before. I'm also facing sensor(s) connection issues after I had installed the latest firmware. What I did so far:

1) Downgrade to version 12.10

  Result: Sensors connecting and no issues with loosing connection.

2) Reset de device and upgrade to 12:30 again

  Result: First ride was ok. No disconnects. Today I did the Stress score check. I had again disconnect with  ANT heartrate sensor.

  Workaround: Disable Bluetooth and there are no disconnects anymore

With all information shared by a lot of users so far. I would expect that Garmin will come with a firmware update asap!

same problem here. I wonder if garmin tests the updates before release? The problem seems to be very common and Garmin does not react. I'm getting tired of Garmin