02-02-2016 14:08
02-02-2016 14:08
02-03-2016 03:40
02-03-2016 03:40
You can't 'stop it' since these readings are down to the nature of the altimeter sensor used for floor detection.
Fundamentally, using air pressure measurements to identify a climb of 10ft and log a floor leaves the tracker susceptible to detection of air pressure changes for other reasons e.g. wind, weather fronts moving through or the motion of your arm through the air (which was probably the cause here).
The Floors reading has no effect on calculated calorie burn so all that you can really do is understand the limitations that this measure is subject to.
Mike | London, UK
Blaze, Surge, Charge 2, Charge, Flex 2 - iPad Air 2, Nokia Lumia 925 (Deceased), iPhone 6
Take a look at the Fitbit help site for further assistance and information.
03-04-2016 03:00
03-04-2016 03:00
I have the same problem. It has surely nothing to do with the theory of the function.
It worked normal for a few weeks (have a Surge), but like this morning, when I wake up it shows already 8 floors (what was before 0) and after sitting 8 hours in the office, it shows 46 floors.
Just because of this wrong kind of measurement (it looks like it did this for 8 days already although I only noted it yesterday) I even just got the 500 floors Helicopter batch.
I hope there is a way to correct this back manually, as this is a clear nonsense result and can not be explained with barometric pressure changes any more.
04-30-2016 16:35
04-30-2016 16:35
11-16-2016 18:32
11-16-2016 18:32
I just got the "Rollercoaster" badge today and no way I climbed 125 flights of stairs! Ridiculous! A friend of mine gave me his Surge because he moved to an Apple Watch, and maybe I can understand why.