Originally Posted by
bahula03
speedlever- frustrating to have things go sideways like that on a ride, but maybe the jinx on the 305 will provide a chuckle in hindsight at some point down the road. When I switched from an Edge 500 to my current 820 I got the bundle figuring A) the HRM I got with the 500 would fail sooner than later (of course it still hasn't) and B) the accelerometer-based speed and cadence sensors are a much tidier install than the magnet-based predecessor, both sensors have been reliable to the point of being forgettable.
There definitely is a lot to figure out with computers, and Garmin making the 530 and 830 so similar just makes deciding more difficult IMO. Depends on how tied in to the Garmin ecosystem you are, but if navigation isn't one of your top "wants" it seems like a good opportunity to see if a Wahoo device is a good fit, worst case return/exchange it and go back to Garmin. I will say, in my experience with navigation on my 820, I've been plenty happy with the screen size and how it displays info (as you approach a turn, it'll switch away from whatever data screen you're on, show the map zoomed to fit the upcoming turn with the route highlighted, count the distance down as you approach, and then return to the data screen you were on).
Thanks for the perspective. If I didn't have the Vivoactuve HR watch, I might not be so tied into the Garmin ecosystem. Shucks, that Vivo HR is getting on in years too.. but still holds a good battery charge and comparing the HR data on it to the HR data from a chest strap, they seem very close generally speaking.
I assume the GSC-10 speed/cadence sensor I already have won't work with Wahoo? So I assume my startup costs will be greater with Wahoo than if I continue with the Garmin ecosystem I currently have.