520 Plus fw 5.30 - dropout all sensors

Just to add that I'm having this issue too since "upgrading" to 5.30, Speed, cadence and HRM are all patchy, mostly don't connect but sometimes do for a short period of time before dropping out again. C'mon Garmin, I've got some lockdown training to do :-) 

I had the same issue and after reading the various suggestions in this thread (thanks folks), went down the restore factory settings route, which, so far has worked to reengage with my Garmin HRM and cadence sensor. Having to reset everything was tedious, but I'm relieved to have got there in the end. Good to see the note from Garmin that they're now onto it.

I did a total reset erasing all my data, but it did not work, unfortunately. This morning, after the reset, the Edge connected to all sensors (speed, power meter and heart rate) but values dropped to zero after 30 seconds.

I understand Garmin can make a mistake in new software (although with testing this may have been prevented ?) but I do not understand the slow response (6 days after it was reported here) and that Garmin does not communicate to the users directly (and allow them to update the software after Garmin knew there was a bug in it).

I logged a call with them about 10 days ago. Took them a week to get in touch, the last being last Friday when they emailed me asking my permission to look at the activity on my Garmin account!

I did give permission, but asked them to explain why they wanted to access my account. So far, i've had no reply whatsoever. I'm not surpised really, Garmin are very secretive and non-communicative when things go wrong (which to me seems too regular to be a conincidence).

For such a major player in this sector, it's a pity Garmin aren't as communicative with their customers as they are at getting their marketing and PR stuff out to potential new customers.

I just spent a fruitless hour on Garmin support chat trying to solve this. We tried removing and adding sensors, wiping files on the 520+ and a full hard reset, which lost all of my data and still didn't fix the problem. Not impressed. 

I asked if I could roll back the update and was told that I couldn't. I was told they were aware of the problem and were working an update. I pointed out that my device is effectively useless until they release a fix.

I asked why Garmin would release an update like this if they knew it was going to cause these problems. His answer was that they didn't know it would cause these issues. Do they not test before releasing?!

i agree, tried this in my last indoor training. HRM, Quarq powermeter and Garmin v1 speed sensor (only ANT+ one) are fine, only eTap 1st gen (not AXS) is bouncing in and out due to its aggressive timeout behavior (30sec), that's ok, i didn't expect to have standby time from eTap when going up&down on a real mountain out there...

OperationOne Are your sensors being recognised automatically, or do you have to add them manually?

Also, have you tried this outside or only on an indoor session? Wondering whether environmental factors (wind road surface etc) might come into play to disrupt things

I also think that whatever works for one doesn't work for others as regards disabling the phone connection.

Simon

https://www8.garmin.com/support/download_details.jsp?id=15149#Instruct 

Now the beta page shows 5.31 was released on 22-Apr.  But I clicked "download", and the downloaded file is named 5.24beta.  What is going on?