This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

"Sensor Found" notifications during ride - Using version 10.0

I can't remember if and how often I may have gotten the "sensor found" notification banner during rides with earlier firmware versions. But I get them frequently with version 10.0. I probably got the message a half dozen times or more on today's 50 mile group ride with 12 of us. Because I was riding and the lettering is small, I don't know if the sensors detected were mine or another rider's. Looking at this version's fixes, it shows that it "cleaned up" some of these notifications. Some? What does that mean? And when the notifications are displayed during a ride with others, whose sensors is the Garmin 820 detecting? I am not seeing dropouts of my data as far as I can tell.
  • I could fix it all (incl. phone BT pairing) by doing a factory reset and reinstalling all saved profile files. It's relatively quick and easy.
  • I could fix it all (incl. phone BT pairing) by doing a factory reset and reinstalling all saved profile files. It's relatively quick and easy.


    Hi LoneRider38, did it works ?
    Thx.
  • Yes I confirm it worked - but leave Garmin Connect to manage all the process. Don't try to pair directly from your phone BT setup, or modifying the pairing later. Leave GC do all...
  • Same problem here. Reset to factory and the problem seemed solved...BUT reappeared after a bit. In my opinion is definitely a bug.
  • Drusone : you are unfortunately right. After resetting all and setting up again with GC, everything was fine. Automatic connect, automatic course upload, stable connection to sensors...
    Everything then getting less and less reliable course after course.

    Definitely unstable, bad SW quality.

    Too bad. And Garmin being more than careless...
  • Garmin sensors : speed, cadence
    Bontrager lights Ion 800RT, Flare RT
    Connected to Galaxy S9+
    No Wifi
  • Same problem here. Firmware 10, all sensors are Garmin with new battery, last Connect version, smartphone OnePlus 6. Software bug i suppose.
  • What I really don't understand is that, after installing a new version of the firmware (10.2 beta in this case), the connection to the phone is back to working fine, with automatic BT connection, auto-upload and all the nice connectivity features. And course after course, it degrades to the erratic behaviour many of us seem to be suffering with.

    IS THERE ANYONE HAVING SHARES IN GARMIN ABLE TO HELP OUT HERE ?????
  • I believe I discovered the cause of the "sensor found" notices I was getting. I believe it originated from a dying coin battery in my Stages Gen3 left crank power meter (PM). I installed this new PM in late September 2018, which came with a "new" CR2032 coin battery. I assumed that the battery had a full charge when I removed the paper insulation from it in its battery holder on the PM. So I didn't measure its voltage. The PM worked great for several rides until I got the "sensor found" notices on my Garmin 820. A few rides later, I got wild swings in my power data from 0 to over 3000 watts. After three successive rides like this, I removed the coin battery and measured it with a voltmeter at 2.8 volts. I measured a new battery having 3.25 volts and installed it in the PM. My power data has been excellent since, even on today's ride that began at 36 degrees F and finished two hours later at 54 degrees - no dropouts, no "sensor found" messages except when starting the ride. I have found that other devices have problems functioning when coin batteries fall below 3.0 volts. And cold temperatures can compound the issue. Maybe this info will help some of you in this thread.
  • Former Member
    0 Former Member over 6 years ago
    I wouldn't blame the stages battery. Garmin software stinks. I am having all sorts of problems with 10.0 - no phone notifications, stages dropouts, On top of the screen halo that they replaced my unit once for with a unit that was probably just as bad and now much worse. Maybe time to buy Wahoo