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

Device forgets random sensors if it "sleeps" during an activity.

Edge Explore 2 device, used with a number of sensors: Fenix 6 pro for wrist HR (I broadcast HR from the watch, not a separate cycling activity on the watch), a varia radar, a variety of Specialized ebike sensors.

The device starts a fresh activity just fine. All sensors automatically operable and doing what they are suppposed to. But....

If the Edge device goes to sleep, like a cafe stop or lunch break, whatever, with the activity paused, the sleep can be automatic or traiggered manually, the device will stop connecting to a random selection of the sensors, sometime one, sometimes another. Disabling/re-enabling a sensor can -sometimes- wake that sensor up, but only a small fraction of the time. Removing the sensor then putting it back doesn't help when it is in this state. It seems to make no difference if the sensors are continually on while the Edge sleeps, or the sensors are fully off, and carefully started up before the Edge device, or if the sensors aare powred on after the Edge wakes up. Once it's in this state, it stays that way until perhaps the next days, or the next full reboot of the device.

A hard reset and redoing the sensors makes it go away, until the next system software update, then the problem returns. This is recurring with each system software update for about a year now.

  • i turned off autosleep today, with bluetooth connected. 

    During a MTB session of a couple of hours, I had a sensor disconnection. They disconnect for me during training, not when I stop. For now I will have to continue going out with the phone disconnected so as not to lose the cadence and heart rate sensors.

  • It doesn't work for me. 

  • I have turned off auto sleep withing the activity profile, and yes, it does prevent the problem for me. However, if you take a long break like for a meal or similar, you need to leave the unit on beeping away in your pocket or bag.

    It prevents the problem, but it's not an optimum solution

  • I had the same concern but found a workaround for my device at least. When you take a break, stop the ride using the button on the bottom but don’t tap the finish flag to save it. Instead, long press the power button and power off. When ready to continue the ride, power back on and then press the bottom button again. The ride will resume and you haven’t lost anything.

     I’ve tried it on two consecutive rides with no issues. Of course, YMMV so I’d suggest trying it yourself on a throwaway ride before trying it on one that matters.

  • Come on Garmin, fix this

  • +1.
    GPS lost HB sensor, and only way to make it work again was remove sensor from menu, turn off GPS, turn on and add again.
    For a first time using the unit, I was pretty upset.
    Also disconnects the sensor a couple of times where as my 20€ CC400 computer never failed me.
    For 250€ this isn't acceptable.

  • It ist unbelievable that Garmin does not even react. So many users have the same severe problem. Also support does not help. 
    Sorry Garmin this is not how you should treat your customers!

  • yes, it‘s really crazy that this still haven‘t been fixed — and everywhere it has so good reviews, why is nobody talking about this HUGE issue. It really is the absolute core ability of the device not working reliably! 

  • Yesterday HR strap connected but no info about HR. I have restarted EE2, strap new paired and there were still no Infos on the screen... The strap is working because I use it with my another (unfortunately) Garmin device. 

    So for me this device firmware is very poor and unfortunately Garmin doesn't want to do something with it. 

    Has somebody tested beta firmware? I'm afraid of the beta when official doesn't work, but maybe there is a solution?