Edge 850 - sensors occasionally wont connect after auto-sleep

JarlathTG
13 days ago

When using the new Edge 850, I’ve noticed that sometimes during breaks, when the device goes into auto-sleep mode, the sensors sometimes do not reconnect when the device is turned back on. Restarting the device always solves the issue, but I usually save my current activity first to avoid losing training data. This problem has occurred on both software version 7.09 and 7.10. Is there a known fix or workaround for this sensor reconnection issue?

  • 0 12 days ago

    Having the same issue here. If you turn the screen off, say during a cafe stop the will not connect. The device cannot find them. The only solution seems to be stop the ride and restart the device. This breaks the ride into 2. Not awesome. Currently on 7.10. 

    Garmin please advise… or better yet fix. 

  • 0 11 days ago

    I also had this same exact issue.

    I was at a bike shop paused my edge 850 using the bottom right button.

    Then resumed recording and noticed my Garmin-Cadence-sensor and Garmin-Forerunner-HR-Broadcast-watch did not connect, after I finished my bike ride.


    I am on firmware 7.10

     Link to my activity: connect.garmin.com/.../20525514135

  • 0 9 days ago in reply to 8364326

    I had exactly the same today  .... paused ride at coffee stop and put screen in sleep mode, when i started off again i realised all of my sensors weren't connected ....... really annoying considering my 830 was bullet proof

  • 0 8 days ago in reply to MarkGuest

    This issue isn’t limited to the 850. It also happens on the 1040 solar. It is something Garmin need to fix when putting a computer to sleep. 

    A workaround is to stop/ pause your ride then switch off the computer. When you switch the computer back on, you can resume the ride and all the sensors work fine.

  • 0 4 days ago

    I've had this too on the 850, but to be fair this happened fairly regularly on my 530 too! Definitely not ideal. My workaround is to pause the activity, then restart the device (typically finds the sensors again no problem) and then un-pause the activity. This avoids breaking the ride into 2.