Elemnt Bolt/Strava WTF?

Saturday’s ride was recorded normally. Sunday’s ride wouldn’t upload from the Wahoo app to Strava, then seemingly disappeared. Turns out that the Bolt thinks I did Sunday’s ride on January 1, 2006. I managed to get it uploaded to the app by unpairing/pairing it and syncing it. I then uploaded it to Strava, which, of course, also thinks it was done in 2006. There was a GPS glitch at one point where I apparently teleported. That had never happened before (I’ve had this unit for 5 or 6 years?).

Same thing happened today, but this time after I uploaded it to Strava, it has been flagged and I can’t see any segments. Also teleported at least once: Morning Ride | Strava

According to the unit’s settings, it has the correct date and time. WTF?


(and, no, I didn’t hit 75mph)

Thanks, and wow!

If it said 88mph, that would explain some things

5 Likes

ICWYDT :slight_smile:

Here’s Tuesday’s Time Travel Ride. There’s a glitch in the GPS at mile 25. No unlikely top speeds. Unfortunately, I was going for a Strava PR right after that glitch (the southernmost point in the ride), and I can’t see it.

Edit: And I have no idea why Strava has flagged it…

I had a really weird one 10 years ago, with a Garmin Edge 500 and Strava. A nearly 3 hour ride shows up as 0 miles/1 second, but the map shows the entire route, and all the segments show my average speed and time, but no HR or power.

The file uploaded and displayed fine in MapMyRide and Ride With GPS, so it appears the issue was at Strava’s end.

A few years ago, I had another one with a Bryton 420, which an hour into the ride showed me well on the way to setting a new Everesting world record. Unfortunately, Strava says I only climbed 713’ on that ride…

I know Wahoo has the whole ‘back in time’ issue right now, but for what it’s worth I had the same era Bolt and it just stopped communicating with the Wahoo app about a month ago. I reached out to Wahoo customer support, and after a week of dealing with a ton of time between responses, I was told that by following up on a request after 48 hours dropped your ticket down to the bottom of the queue (and that my impatience was the problem).

So I told them forget it and bought a Garmin instead. And promised to share that story. Their emergency press release suggests they’re going to start trying to fix the software bug, but I personally have zero faith in that. Good luck :frowning:

I am really upset that joke is not getting the appreciation that it deserves

1 Like

Had the same headache with my old Bolt last weekend thought I’d cracked 200 miles before breakfast, Strava didn’t agree :sweat_smile:. Honestly feels like these things age like milk once the firmware goes sideways. You know what’s wild? I loaded the same FIT file into RideWithGPS and it looked totally fine, but Strava made me out like I’d taken a warp tunnel. Maybe best workaround is exporting the file and pushing it through something like fitfiletools before uploading. Not pretty, but at least you don’t lose the ride.

Using fitfiletools and modifying the timestamp is what I did to get it into Strava.

1 Like

I have updated my device, but haven’t tested it. Does it work for you guys?

I just started and stopped a ride, and it has the correct date and uploaded to Strava just fine.

1 Like

Not fixed for my first gen .

(edit)

It appears that I now have downloaded the appropriate fix for my Bolt 1, so we will see tomorrow if the date issue is fixed. Also, we’ll see if the temperature issue is fixed (min = ave = max temps), and if the failing map display (intermittently loses current location on map) is fixed, and if the failing breadcrumb issue is fixed (fails to update the map based on current location), and if the current turn-by-turn issue is fixed (shows incorrect distances for each turn)…

And…it now works. Date fixed, temps fixed, map seems fixed, didn’t check for bread crumbs or turn-by-turn.