Edge 840, Di2, and firmware 27.13

OK, being stubborn and also allowing the Di2 to power down - then I finally managed to get the 840 to connect to the Di2 again.

I was then able to do more testing: I started the Edge 840 unit, then shifted on the Di2, and after about 30 seconds (which is a looong time, my 510 unit will find the Di2 in a couple of seconds) then the 840 unit found the Di2 and then almost immediately lost it again. I kept the Di2 awake by shifting and resynched all the sensors and after about 5 minutes then the 840 unit found the Di2 again.

This was a not problem before on the 26.18 firmware on my 840 unit and this is not a problem on my 510 unit.

Reading the 27.13 change log, I'm wondering if

• Improved user experience for pairing secure BLE sensors
• Fixed missing tone when connecting new sensor
• Fixed issue with pairing third‑party power meters via Bluetooth
• General improvements to device stability and addressed various minor bugs

or something else in FW 27.13 had unintended consequences?

Topic https://forums.garmin.com/sports-fitness/cycling/f/edge-840-series/412027/version-27-13---speed-sensors-dropping-out-constantly also sounds fairly similar to my issue.

EDIT/addition: Is there a now a timeout at the start of the ride (or has that timeout been reduced) where the unit will stop searching for sensors? When biking home from work I will generally not touch the shifters for the first few hundred meters, even a kilometer since the bike will be in the appropriate gear from when I arrived at the office. So the Di2 system won't be activated for a while.

Is there a now a timeout at the start of the ride (or has that timeout been reduced) where the unit will stop searching for sensors? When biking home from work I will generally not touch the shifters for the first few hundred meters, even a kilometer since the bike will be in the appropriate gear from when I arrived at the office. So the Di2 system won't be activated for a while.

Did perhaps any of these changes in FW 27.13 have unintended consequences?

•     Improved user experience for pairing secure BLE sensors
•     Improved gear preset selection to automatically apply a valid configuration when a shifting system reports a non‑standard gear count
•     Fixed issue with sensors displaying improper name
•     Fixed missing tone when connecting new sensor
•     General improvements to device stability and addressed various minor bugs

I did more testing and was finally able to get the 840 unit to add the Di2 back. But in follow-up testing it took the unit 30-45 seconds to find the Di2 (my old 510 will find it in 1-2 seconds) and I noticed that the 840 unit will lose it immediately again. Then it may come back about 5 minutes later or only when I manually resync sensors.

Are there any news on anyone from Garmin taking a look at this? Riding yesterday, an overall ride in 3 parts with stops in between where the device went to sleep then the device only picked up the Di2 after the stops when I manually triggered a sensor sync.

After the stops I woke the device and it found my HRM, speed sensor and cadence sensor but not the Di2. Of course the Di2 was working properly, I was shifting, but I had to find a quiet part where I could ride but still press buttons on the device to resync the sensor. As soon as I did then device found the Di2.