Coros Review
I tried to like the Coros. So many fun and useful features and data analysis. Crazy long battery life. But that’s about where it ended for me (us because I bought one for Steve too).
Reasons (offenses from least to most egregious):
1. Multiple times I bent my wrist during a run (to pop it, shush) or during a strength training workout and it hit the timer button and stopped my watch. Not cool. I shouldn’t have to worry about that.
2. The Wellness Check feature was so fun. Until neither Steve nor I could ever get an accurate blood oxygen reading. We both always logged numbers so low we should have been in the hospital.
3. It disconnected from my watch three times in the first week. Had to restart everything to get my notifications again.
4. It doesn’t give total daily energy expenditure (TDEE), i.e., total calories burned per day. Yikes. So that meant I had to add either my BMR or RMR (could not get a clear answer on this but I think it was BMR) to the burned number to get my TDEE. But I tried it both ways and could not get the math to make sense either way. Which means no tracking my total calories anymore. Not okay with me.
Even with all of the above, even with that fourth one, I thought I could live with it. But.
5. My activity heart rate was wildly inaccurate. Eight out of ten workouts showing walking rates in the 110s to 130s and running in the 160s to 190s when all my manual checks were a good 30 bpm lower. Way way off.
I thought maybe it could be fixed. Or adapted to. But it was so much effort trying to get it to work. And it wouldn’t stick.
The straw was my 5-mile run on Tuesday. See heart rate chart above. I decided not to look at my watch and just go slow and run by comfortable feel. I thought it was doing fine until I looked down at mile 2 and saw 188 and climbing. I stopped, walked a little, went back to running. Looked down again after mile 3 and saw all stats blanked out. Because according to my watch, my heart rate had gone over 220 and wouldn’t track anymore.
And when Steve got back from his run? Lo and behold the same thing had happened to him. That was only his second run but his first one the day before was almost just as bad.
The inaccuracy lasted beyond the workouts too. My heart rate would show as being in the 100s to 130s an hour or hours after my activity. Always far off from my manual checks - or anything I ever saw on my Garmin the last 5 years.
And unfortunately, heart rate inaccuracy affects every single other metric Steve and I care about - recovery time/status, running fitness, calories burned (which were *laughably* high), daily stress level, efficiency, training load, HRV.
So thanks but no thanks, Coros. We returned them today and ordered a couple of Garmin 970s. Can’t help but look forward to that. (Hopefully we are happy with them because we got them at a discount from GovX and there are no returns.)