I have found this as well. At work the fights-of-stairs counter seems pretty accurate. At home it is woefully inaccurate, perhaps off by 20:1 on count of # of flights counted. I think if you stop after only 10 feet or so, it forgets you were doing a flight but if I go up sets of 15' or more, it counts well.
I tried going up the stairs at home, then waiting an hour, then going back down, waiting an hour, then look. Didn't count. This is repeatable. I went up a ladder up the back of the house, 18' or so, and it counted that.
At work we have three stories. I tried starting at my floor, one above the parking lot level, then going down 1, up 2, down 1 without stopping at the top, look at data. It counted correctly. It does seem to take some time to conclude that I did the flight, 2 or 3 minutes?
I tried going up the elevator. It didn't seem to notice that.
It keeps track even when the App is open showing "All Data" for the flights counter. But it doesn't show up for a while.
I have a theory, and it is mine. That theory is that people who wrote this software live in Ranch style houses without basements or two story houses with very tall first floors. This is the way new housing is being built in Orlando. Then they all work in buildings with 15' flights of stairs. Do they have Ranch style houses in Silicon Valley? Perhaps they never noticed that this doesn't work because they none or non-typical flights of stairs at home? Laugh if you want, I've seen bugs caused by stupider reasons that this! See Mars Climate Orbiter which crashed because the coding for one function was done in Newtons instead of Pounds-force. Also see the Therac-25 radiation therapy machine which killed people it was being used to treat because the coders had expected ASCII-NUMBERS only for configuration and recorded two characters of data while only displaying one character if a ASCII-LETTER was typed. This resulted in large numbers being entered for radiation-level. (At least I think that's what the bug was)