Light Network Edge 830

Same form me...i have radar and ut800 but don't see the liht network 

Had to do the same thing.  I called Garmin support and they mentioned the long button press.  You should end up with both a light and a radar sensor paired in the end.

I also found that if I had the UT800 and RtL515 paired, powered them down to charge them, powered them up and  then tried to get the light network up again, it always failed.  I found out that if I had the speed sensor active, however, the light network always formed quickly.  So, my routine is now: head to garage, attach UT800 and RTL515 unit to bike, power both up, power up  Edge 830, rotate front wheel to get speed sensor active and voila!  The Lighting Network forms.  Strange isn't it.

Old Guy. I have to admit that strange as it might sound...it works!!! Thank you.
I am upgrading from an Edge 130 to an Edge 830 and establishing the light network now became a nightmare as well as an unpredictable process. Your simple trick is a great workaround. Powering on first the 830 and then the sensors + speed sensor worked equally well for me.

Yes. Your order of powering things up is better than what I put in my original post.  Edge first, sensors second, RTL515 and UT800 last. Works every time.  Glad to have added some much needed practical relief from frustration during these Pandemic times. 

OldGuy

Wish I’d read this 3 days ago!  Spend past 3

days trying to get UT800 and RTL515 working together.  

Even formatted Edge 830, factory reset, added maps back, re-added sensors and still didn’t work.  Interestingly, I had just worked out a clean Garmin Edge (just factory reset) worked fine with the lights only - it was when I added the HR, Speed and Cadence sensors it stopped working.  Just tried spinning the front wheel and as you mentioned about it worked perfect so thank you!

Good to hear...happy riding!

sad to say firmware update version 7 still doesn't fix the issue however the work around of spinning the front wheel first still works.

I’m retired now, but when I was working as an engineer for many years, I had often seen that “real time” software issues were slippery to debug. A lot of “bugginess” is due to software architectures that are not ‘updated/redesigned’ to deal with new requirements. What I really mean is that development groups take shortcuts when they’re understaffed and poorly managed. Also, if SW groups are not colocated geographically, the quality of the product often suffers (right and left hands not working together). There are ways to get ‘it’ right, but it requires experienced managers and investment.  Garmin has been around a long time, and overall has weathered the rapid evolution of technology surprisingly well. Their GPS business was essentially wiped out by the smartphone.  Yet, they’re still here. I imagine that their ability to increase R&D investment is 0. So, as customers, I guess we get what we get...and thankfully we haven’t gotten ‘chapter 13’....which has happened to other products I’ve purchased.  But, the engineer part of me is so frustrated that this really annoying and time wasting bug exists at all. It should be fixed as a matter of pride.

OldGuy