Sensor error radar 0:9

Garmin don't care about this problem :-(

Had same error. After removing radar light from sensors list radar start working fine. Definitely some bug in 9.1 firmware.

Me too!!! Had the same pop up today!! Error 0:9 , never had any issues before!!!

the sad thing is that when I receive this 0:9 error, my radar is actually correctly detecting the traffic behind me... so if Garmin could simply remove the error message or make it smaller, I could even live with it...

On a Wahoo Elemnt Bolt a Radar Error message froim the Varia can be dismissed; on the Edge 530 the only way to get rid of seems to be to stop and start the ride. It is happening after I have done a right turn at a crossroads onto the quietess road implying the Varia is getting confused by traffic moving across and towards it.

I just swipe up from the bottom of the screen,an Edge 1030 plus.

Yep started getting this every ride since 9.1

Garmin doesn't admit it is related to Edge firmware so it is not close to be fixed :-(

I had this 0.9 radar error for the first time ever yesterday. My RTL510 has latest firmware and the Edge 530 is version 9.30.

This was only my second ride with 9.30, and I only had 4 rides before that on 9.10, because I was cycling indoor all winter. My last outdoor ride last Fall was on 8.20 in Nov 2021. So within only the first 6 rides on 9.xx firmware, I have already encountered this error. By comparison, I have about 15000 km on firmware before 9.xx and recall never having this error message.

I had just walked my bike out of a building where I took a break (the Edge was manually paused). I was standing still with the radar facing the wall of the building. Suddenly the 0:9 radar error message popped up on the Edge. I tried to clear it with the "back" button (works on other popup messages), but the error didn't go away / came back. I then tried unpausing the Edge, but it still didn't clear. So I rebooted the power on the Varia, and then when it reconnected to the Edge again there was no more error.

Hoping this is a rare event, but given all the many reports I have been seeing here since the 9.xx firmware arrived, I suspect it won't be.