Constant Sensor Connected Notifications

Hello - Just got a bike and my edge 830 keeps notifying me that the SRAM etap shifters are connected. Have had to turn off all notifications, but wondering has anyone had this issue previously, and found the solution. No problems with all other sensors, and have checked battery, etc. 

  • I have the issue, I am getting dozens of notifications per minute. For the price we paid this is simply not acceptable. I have deal with your incompetence with numerous bugs in the past, that garmin is refusing to address,  but that one makes the device unusable. 

    I cannot have 400€ paperweight, so if no solution is provided in the next week, I will be returning it and getting my money back, and finally move to Wahoo. 

    I am literally typing this in my bib shorts unable to do my session ... 

  • Completely agree with you. Solutions make no sense because when the issue is happening the device is unusable. I’ve been amazed there isn’t more outrage 

  • Might be jumping from the fry pan into the fire, (Garmin have tried a few attempted solutions in recent years / devices without any apparent success), but there is a recent beta which includes, 

    • Updated GNSS, sensor, ANT, BLE, NFC and Bluetooth libraries for improved connectivity

    https://forums.garmin.com/beta-program/edge-540-840-1040-series/f/announcements/416034/public-beta-28-11-pre-rollout 

  • I tested the beta, same problem. 

    I also did a hard reset, same problem.

  • Quick update on my experience with edge 540. I am on software version 27.14. I have done multiple system resets. I finally had a ride with ZERO issues. The one thing I intentionally did differently, was pair every sensor via ANT+ and removed any sensor that showed up as bluetooth

  • After several rides with no issues, i rode a ~67mi custom course, with turn by turn navigation, that i created on the garmin connect website. During that ride I had several HRM and Varia radar sensor drop outs. Not to the level they had been, but still more than there should be. Of important note, the other rides that had no issues were just free rides. following a workout on the headunit. So now i wonder if following a course via GPS is somehow causing processing issues with sensors.

  • I am so frustrated with this problem! You can't do any of the suggestions because the alert just keeps popping up. I can't even power it down. At this point I will need to buy a Wahoo so I can race with data. Garmin this is unacceptable!

  • Hello thanks for your feedback, we understand this error can be frustrating.
    You should always be able to power the Edge off manually by pressing and holding the power button for an extended time (15 seconds or until the Edge shows a blank screen). We'd recommend the Edge is unplugged, if the Edge is plugged in and charging it will power back on immediately after shutting down. 

    Before re-starting the Edge, be sure that all available sensors are disabled, powered off, not sending a signal, or out of range. This should allow you to remove and re-add the sensors giving trouble. The Edge will typically pair via ANT+ by default, but be sure that no sensor is being listed twice or multiple times in the Edge sensor menu.

  • Hello all, thanks for your patience and feedback.

    Changes are available in the current beta software for Edge 540, 840 and 1040 (version 28.13) and are expected to resolve a repeated sensor found/connection message pop up. It is possible that you will need to both install this update and remove sensors presenting this message before repairing them. 

    You may enroll in the beta software program via Garmin Connect to install this update now: Enrolling in and Learning About Garmin Beta Software Program
    This update (version 28.13) will move to a public software release and prompt to install to your device after syncing over the next few weeks.

  • Others have indicated that using the Beta "fix" did not fix things. I have gone back to my Wahoo as I have a race coming up and I can never get even to an option to reset because the error won't go away.