I have a Versa 2, but this has been a problem with just about every one of the FitBits that I have owned. I guess my question is - is it just me? or does everybody have this problem? And if it's everybody, then why not Fitbit just admit that this feature doesn't work and get rid of it? Here's the issue:
My various FitBits always have a tendency to overcount floors, and this Versa 2 is the worst. It's also by far the worst at accounting for elevation changes while running or walking. I had decided with my last FitBit to just live with it, because honestly floors climbed is not that important to me. But it's so bad I just have to ask about it. Case in point:
(1) Way overcounts floors. My lowest day this week is 198 floors. I can stay at work all day, on a flat surface, not go up any flights of stairs, and still get credit for 200-300 floors climbed. I've checked in the morning before I get out of bed, and so far it's always been at zero floors. But then I go downstairs - DOWNstairs - and within 30 minutes I have 20 floors climbed.
(2) Terrible at measuring elevation changes when paired with the GPS on my phone. The other day I took a walk - the elevation change from my home when I started to my home with I got back - exact same location - was a 90 foot decline. I took a run the other day - two times around a loop that had two big hills on it, so it should have measured four big hills. It measured just a gentle slope going up, then a long gentle slope going down for a couple miles (ending up at my car a hundred feet lower than my car was when I left it). Interestingly, it pairs with RunKeeper, which created a beautiful elevation chart showing the four hills, even though both FitBit and RunKeeper mapped the route perfectly on the map.
This really isn't a big deal for me. I'll use RunKeeper if I care about my elevation changes, and I'll just not worry about flights of stairs. But it's so bad, and it's been bad on every FitBit I've ever owned , I've just got to wonder whether there is something physiologically wrong with my wrist, or whether FitBits are just really bad at this.
Yes, I've tried resetting, yada, yada... doesn't help.
