Garmin RearVue 820 problems

Hi everyone.

Just bought the RearVue 820 and did few rides and there are number of weird issues.

Equipment:

- Garmin 1050 with latest firmware

- RearVue 820 with 6.23 firmware

As others have mentions, riding with my wife she was constantly detected as bike behind me and stayed on the screen. I had to do peloton mode, and disable alerts, shrink the section to small. Garmin please add an option to either disable small vehicles/bikes or same speed detection, many of us don’t want to have the radar overlay all the time.

But ok, i said to myself atleast I can see when my wife falls behind and then kindof know the distance. But this is where it’s very strange. Whenever she is detected she shows up as righ behind me.

As I surged a little bit and dropped her, suddenly she is gone from the screen.

I look behind and she is not that far away. As I wait a little bit, and she is closing in she shows again on the screen, but right behind me so at the top of the overlay, even if she is not fully on my tyre yet.. she is somehow not detected at the max distance? Sometimes she is detected at half the distance but again shows way to close on the overlay again..seems while this is hapoening the cars also get bugged and not detected at max distance sometimes but rather half distance..and show only from the middle of the line on garmin not from the bottom..

This thing happened all the time during the ride. Very buggy. Not to mention that when cars go over us she would turn into car and back to bike often..

Please update and do the disable of same speed/bike. Will probably fix all the issues Disappointed

  • I had my first issue yesterday. My commutes have been fine, no issues at all. But half way through a 4 hour club ride, and the 820 stops detecting anything. Turned both the head unit off/on, radar off/on - nothing. And it wouldn't actually reconnect to the head unit.

    Solution was to stop the ride (finish) and restart the ride. It then started working again, but it only paired in Ant+ m ode, not BT - so had the limited detection data. 

    Not a great start to something that was working so faultlessly earlier in the week.