05-17-2021 00:16 - edited 05-28-2021 02:55
05-17-2021 00:16 - edited 05-28-2021 02:55
My altitude measurements has increased significantly, started 8 days ago
. Even on a day with little wind it is recordings lots of stairs. Today i already got 24 stairs after a short walk with the dog. Never seen this happen before even on stormy days, same short walk. I do normally walk and run in a hilly terrain and stairs around 50 is a good estimate, even up to 100 around 1 of May where i was climbing lots of hills.
Compared with my iphones estimate on stairs climbed, it should have stayed fairly even throughout May, except for the first days of May.
Can the algoritm used to measure altitudes change outside of firmware updates, i.e. by an app update?
I rarely pay much attention to stairs climbed and am merely puzzled on the sudden change and wonders if Fitbit can change the algoritm on the fly, perhaps that could be done with HR mesurements as well.
here is from my iphone for comparison
05-18-2021 07:58
05-18-2021 07:58
Noticed Sense erratic floor behavior recently too, without any phone or Fitbit App update.
Trusty old Versa remains with accurate results, floors, steps, heart rate all working well, but not the Sense.
Author | ch, passion for improvement.
05-18-2021 12:01 - edited 05-18-2021 12:02
05-18-2021 12:01 - edited 05-18-2021 12:02
Fitbit is aware but have yet to fix this problem. I got 143 floors walking my dog for 20mins this morning.
05-28-2021 02:54 - edited 05-28-2021 02:57
05-28-2021 02:54 - edited 05-28-2021 02:57
Something is definitely very wrong, either a hardware fault or Fitbits attempt to smoothing out spikes.
Look here, logs from running back in October. Start and finish at the same spot with a hill 1km away and a flat area. All is good and one got spikes on a windy day. These are aceptable in my oppinion despite the flaw on windy days.
Now look here, these are from May, either the hardware sensor broke or Fitbit changed the algoritm, these are way off.
All four are exactly the same route and should be similar to above, with one 30m steep hill, a flat route around a lake and back up the hill.
Any ideas what might be wrong here, hardware or software fault? I much preferred the above and getting off readings on windy days compared to the attempt from Fitbit to smooting out the artifacts.