Sunday, 15 December 2013
fitbit and cycling
I'm about to go cycling, and thought I'd try an experiment with fitbit to see how it compares with cycle usage.
I've been using fitbit for a while but never bothered to check accurately what it does if I use it when on a bike. I've always surmised that it counts each pedal revolution as a step (which seems fair to me), so today I'll actually measure it properly.
Mine is the fitbit One, which is the small version that can go in a pocket rather than something on a wristband, which I consider to be rather too obvious. The Nike systems all use wristbands, but I'm not sure that I want to walk around lit like the festive season all year.
My fitbit is at 5,137 steps and 2.37 miles walked today so far. I'll check it again when I actually start cycling and again when I finish. Then I can link it to the number of pedal cycles I've done, based upon my Garmin read-out.
Update to follow...
So my revised fitbit count after the bike ride is 12547. And the number of pedal rotations was 6,870 according to Garmin Connect. There's about 212 steps unaccounted for, which is me faffing around to get the bike ready and also a short false start when I reset the Garmin after about a minute. Close enough.
So, I'll conclude that the fitbit is counting pedal rotations quite accurately.
The mileage is way off compared with the amount I travelled, but I don't really care about that, which I can pick up on Garmin. It's just useful to have a fitbit count that includes a representation of cycling time. I'm also much happier to have a low count for mileage compared with my actual cycling (more than 20 miles) which could otherwise be construed as cheating.
I'll still use the Garmin for calories etc, but it's good to know that the fitbit and Garmin are consistent.