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

Does anyone elses Edge 830 create fake rides?

Vincent.Bayliss
over 1 year ago

Whenever I record a ride, my Edge830 will produce a second ride that gets fed through to Garmin-Connect and then onto Strava (i.e. I get two rides).  The second ride has a time stamp that sits will within the time period of the first ride and is always a shorter ride in both length and time.  For example: yesterday, I did a 57km ride, starting at 5:40am (with a timing of 2 hour and 14 minutes).  No problems with this ride but then my Edge830 pushed through a second ride that has a start time of 6:21am (so, inside the time of the first ride) that was 26km in length and a timing 1 hour and 5 minutes.  This second ride has no GPS coordinates (i.e. no map displayed in GC or Strava) and, as mentioned, the timing of this ride sit within the start and finish of the first ride.  This happens every time I go for a ride now.

Then, today at approximately 10am, I looked in the Ride-History on the unit itself and there were two rides listed for today.  Here's the weird thing:

1. It was 10AM when I looked at this and 1 ride was for 7:16PM (LATER TODAY) and the other was for 4:29PM (ALSO LATER TODAY).  Its logging future rides!

2. I haven't been on the bike today!    

WTF Garmin?  Now, the default answer to this will be to do a factory reset but this is a lot of work to remap all the sensors and set up the screens and custom data fields.

Here's a screen-dump of the two rides from yesterday.

Here's the history on my head-unit:

  • 0 over 1 year ago in reply to Artem

    Here's my setup.  I have the 830 and a garmin speed sensor 2 on my back hub (in addition to other sensors like HR monitor and power).  I don't have any wearable.  When I stop a ride, it auto syncs through my phone (via the GC app) and then to strava (via strava integration in GC). 

    Somehow, my speed sensor 2 appeared directly paired to my phone and I thought that was the issue.  Not so.  Having unpaired it through Bluetooth settings, I am still getting phantom rides. 

    It's definately coming from this sensor though. Strava shows the ride coming from that. What I just noticed is that in GC, it's listed under Garmin Devices (along with my 830).  I just deleted it from there, unpaired it from my head unit and repaired it to my head unit.

    My next ride will decide if that's the fix. 

  • 0 over 1 year ago in reply to Vincent.Bayliss

    I believe that is absolutely your problem.  You should NOT have the sensor paired with GC if it is paired to the head unit (830).  A common mistake as the Garmin documentation isn't clear that it should be one or the other.  The sensors should only be paired to the Edge, nothing else.

  • 0 over 1 year ago in reply to Cranky K.

    I do hope it's just me.  I have had a lot of issues with previous garmin head units (500 & 820) that were either software or hardware related.  I gave Garmin one more roll of the dice and bought the 830 and its been great until now.  The phantom issue I believe will get sorted fairly easily through correct set up but the unit started doing weird pausing on my last ride (which is one of the problems I experienced with a previous unit). .  If this pause thing continues, I'll just move over to wahoo. 

  • 0 over 1 year ago in reply to Vincent.Bayliss

    Consider not using auto-pause, it seems to cause many issues.  Breaks are part of the ride, I have no interest in auto-pause.  I record non-stop but Garmin Connect will still show me my moving average vs. total time.  It also still reports through to Strava.  Strava still shows my moving average speed even though I don't use auto-pause.  I get it, auto-pause is a feature and you should be able to use it if you choose, but a great many of the complaints on the forum are by those using auto-pause.

  • 0 over 1 year ago in reply to Artem

    The issue is where the sensors are connected to both your phone (via Bluetooth pairing) and your head unit (in the sensor section of the settings).  They should only be paired to the latter.  You can actually pair to both at the same time and that's where you get issues.