03-03-2019
10:18
- last edited on
03-04-2019
07:10
by
AlvaroFitbit
03-03-2019
10:18
- last edited on
03-04-2019
07:10
by
AlvaroFitbit
I’m not getting credit for my floors. My previous fitbits all worked correctly with floors. Is the Versa configured differently? Can it be adjusted for altitude so I get credit where credit is due?
Moderator edit: updated subject for clarity
03-04-2019 07:18
03-04-2019 07:18
@McJosh Welcome to the Fitbit Community! I hope you're doing well! Sorry to hear that your Versa isn't counting your floors. Your device uses it's altimeter to detect variance in altitude. It will count 1 floor for every 10 ft it detects you climbed. There are situations that may affect the floor count like stormy weather (that has an actual impact on atmospheric pressure), gusts of wind, an AC unit in a closed room or opening a door. I suggest you start by cleaning the back of the device with cotton and rubbing alcohol then use compressed air at a distance to clear the altimeter's opening (check the image for reference). Finally restart it.
Let me know how it goes.
If a post helped you try voting and selecting it as a solution so other members benefit from it. Select it as Best Solution!
03-04-2019 09:05 - edited 03-04-2019 09:24
03-04-2019 09:05 - edited 03-04-2019 09:24
I'm having the same problem and my fitbit is only a week old...and now the one i had has disappeared...WTF Firbit!!!!!!
03-11-2019 06:49
03-11-2019 06:49
Thanks for the response. I'll provide some more detail as my question wasn't answered.
1. My stairs are more than 10 ft.
2. The Versa was brand new (it does track floors it doesn't track them for every 10 ft).
3. The back of the device is completely clean as it is brand new out of the box.
4. Restarting the device made no difference.
5. Compressed air made no difference.
6. Other fitbits are recording floors consistently.
7. The forum is littered with complaints about Versa tracking floors inconsistently.
My question was why does it behave differently than previous fitbit trackers. The responses I see in the forums indicate this issue isn't being taken seriously. When will this be fixed?