Just curious what people are thinking of the new Wahoo Summit feature?
Haven’t seen much on YouTube about it other than @gpl youtube channel.
1 Like
I am not yet riding on the road yet here in Canada but at first glance it seems a little limited but a move in the right direction. I would like to see remaining distance to climb as a field on the climb page and not just the cue sheet.
1 Like
Very interested to see Shane @gpl referring to a forthcoming update to Wahoo’s Summit Segment climbing feature during his review of Garmin’s 540/840!
Sounds like it might be a decent implementation.
4 Likes
Excellent. Looking forward to the release (and the review!).
Awesome! Any idea on an approximate timeline when we can expect this feature to drop? Or can’t say due to a presumed embargo?
FWIW in reply to someone asking a similar question in the comments on that Youtube vid I linked to, Shane wrote:
" The Wahoo climbing feature is close, really close. I’d take an educated guess it’ll be within the next 4-5 weeks. "
2 Likes
Today is May 2, which I believe is when Summit Free Ride was supposed to release.
Checked the companion app and I believe this is it:
Can you confirm @gpl @dcrainmaker ??
Based on Wahoo’s details on the feature, that is the version introducing it.
Only bad news is that it is only available for the v2 versions of their bike computers.
Release notes are also published every time there is a release, so you can always look there to see what’s up.
Has anyone else had a problem with the Summit Segments after applying the update? I did a route today with lots of climbs. Each time, before the climb, I’d get the usual notification that it was coming up, but the Summit feature didn’t pop up like it did. I haven’t even tried for this in free ride. It was working just two days ago, before the update. The Summit Segment option is active, so it’s not that.
I’ve sent Wahoo a message, but I don’t know how long it will take to here back, so I thought I’d check with other users here as well.
Tried this yesterday on a gravel ride and it worked perfectly. Big fan of this feature!
2 Likes
Used it the last few rides and like it. The only issue i have is it stops hills at grade separated intersections, like if you have a hill that has an overpass, the hill will get split into two. Otherwise it works fine. The estimated time to top appears to be based on current avg speed, which is very inaccurate if you have varying grade
@buirechain i had this same problem yesterday on a ride, my first after updating to the latest firmware. Probably some bug introduced as it was working for me prior.
Which device are you using? I’m using a ROAM v1, so I won’t get the feature on free rides of course, but it seemingly isn’t working on preloaded routes either. I’ll enter a support ticket as well, but if you hear anything from Wahoo, feel free to share findings!
I have a Roam V2. The odd thing is that I’ve since gotten climbs on free rides, but not on the one route I did since the update.
Wahoo said they were looking into it. It sounds like I’m not the only one who reported this, so they’ve passed it onto the tech team and it will hopefully be fixed soon in an update to the Roam and/or app. Customer service said I would automatically hear back once they had a fix, though there’s no estimate of how long it may be.
1 Like
Sounds good. I did log a ticket this morning as well. Hopefully it’s resolved soon. Maybe it is something as simple as they turned off the route implementation when they turned on the free ride version on 5/2. Either way, It was a very nice to have feature that seemed to quickly disappear!
@buirechain, Wahoo did respond back to me as well and I pretty much got the same info back from them. When they responded back they also asked that I provide them my .fit file as well as the route file for the ride in question, which I did… HOWEVER…
I went for another ride today and used the same preloaded route that I used on Sunday. Oddly enough, when I rode the route today, the live summit segment page ACTUALLY RAN as expected. There were TWO things different with today’s ride vs Sunday’s ride that I’ve passed along to them. Not sure if they have any bearing on the issue whatsoever, but thought I’d also pass it along here as well on the off chance others are encountering the issue and wish to experiment…
-
When I rode this route on Sunday, at one point during the ride, my ROAM thought I was off course (i was NOT) and the “re-routing” message popped up on the screen. Today this did NOT happen.
-
I rode the route today as part of a scheduled workout, so after loading the route up, I switched the display over to the planned workout page and loaded up and ran the workout. It was this page that was open when I got to the climb. On Sunday’s ride, the standard route page was open.
Note, that I have checked my ROAM and I am still running the same current firmware version that I was running on Sunday, so nothing changed there.
1 Like
I’m on a Bolt V2 and seen the same thing, just this week. On a freeride (without a pre-planned route) the Summit stuff works as expected. But on a planned route, sometimes it’s missing some of the functionality:
- I still get the popup of an upcoming climb
- But the Summit fields I’ve stuck on other pages (eg. stuff like remaining distance to the climb’s summit, remaining vertical ascent, etc) all show “n/a” as they do when you’re not on a climb.
Haven’t figured out what, if any, the pattern is for inducing this faulty behaviour. I think I’ll contact Support, as this is happening now on the latest firmware. But, I’m reasurred I’m not alone, so it will be fixed eventually. Safety in numbers! 
What I think is happening for me is that the summit feature won’t work if I got a route onto my head unit by turning it on and telling it to check for updates (and then immediately gone for the ride). I’ve used that as a workaround because the android app is kind of a headache since it always wants to give me that $%#ed video (it was nice the first time around) and then acts as if I want to set up a new one instead of just reconnecting to my existing unit, and then forces me to pull up notifications to wait for then click on the bluetooth connection (seriously, has anyone figured out how to make that app work?).
Anyway, if I load routes through the app instead, it seems to work. I think it also would work if I loaded my cheating way and then turned the unit off and back on, but I’m not 100% sure. I don’t know if this is the problem anyone else has had, but I thought I’d share.
There’s a firmware update just released that purports to fix some of these Summit issues.
Bolt v2 link:
2 Likes