Data inaccuracy in weekly and monthly graphs

[Loukar]

Has anyone noticed the programming error in the weekly and monthly step/calory graphs since the November 2014 update?
The weekly graphs no longer give a current average of steps upto a given point. They give an average divided by 7 days which can only be correct when all the 7 days are completed. Hence, if you look at a weekly graph on the first day of the week, it will divide the result by single day result by 7 and tell you your average is 1/7th of the daily result. Seems stupid. The monthlies are even worse. I've contacted fitbit and they deny that it ever did anything different before the update.
To me, if 3 days have passed in the week, the total steps divided by 3 gives you the average, not divided by 7.
Ridiculous.

[MariamV]

It's great seeing you around @Loukar! Hey, what you're describing sounds fairly odd. Keep in mind that your weekly graph's average is based in a seven day calculation. I also use the iOS app and these are my weekly graphs for steps and calories, the average is based on 7 days. Check this out:

It'd be great if you could post me with some screenshots of what you are observing to determine if we're dealing with a bug. In that way we can pass it along to the proper area of expertise. I'll be looking forward to your new comments! 

[Loukar]

Hi Mariam,

Mon 1/5 15982

tue 2/5 15527

wed 3/5 26645

thu 4/5 11335

total 69489

divide by 4 elapsed days 

69489/4=17372 steps daily AVERAGE

graph average above is 2232

why?

because 69489 divided by 31 days that are in May is

69489/31=2241 close enough

but that answer assumes the other 27 days are ZERO steps each.

IT USED TO WORK CORRECTLY BEFORE THE NOVEMBER 2014 UPDATE

I've complained numerous times even sent data to support.

RIDICULOUS MISTAKE

Funny thing is it's wrong for steps and calories but not for sleep.

Loukar

[MariamV · Accepted solution]

@Loukar thanks for getting back to me and for posting the screenshots.

I see what you mean, however, your Fitbit account will take the last seven days to average your steps for the week. So let's say I'm checking my weekly average today which is Tuesday, then tomorrow the steps I did last Tuesday won't count for the seven days average since it takes your steps for the past 7 days.

Also, take into account that in order to have a monthly step average the month still has to end. After May ends, please check your graph for the monthly average. 

Additionally, check this post with info on how does your calories in vs out work with your Food Plan. Any other question, I'll be around! 

[Loukar]

Hi Mariam,

My apologies if I sound crass, but it all sounds like an excuse rather than a solution.

It's not difficult to calculate a weekly or monthly average, all you need to do is divide by the number of days elapsed in that period. The formula doesn't calculate for the last 7 days, simply for the number of days elapsed during the week of month to date.

As a matter of fact, Fitbit correctly calculates the average to date in each week for the sleep graph.

The graph below shows my average for the first 4 days of the week calculated properly, and not the four day cumulative total divided by 7 as the programming does for weekly steps.

It is a programming error that first happened after the nov15 update. It's a pity there's no desire by Fitbit to correct this.

I used to compete against my averages on a daily basis, and I'd try to better the previous week and the previous month, BUT now, I can't do that because I don't know how the CURRENT week or the current month is tracking because the averages are WRONG until after the week or month ends.

I find it a pity that such an easy PROGRAMMING error is being ignored by a global company. 

Loukar

[Loukar]

Hi Mariam,

Please see prior post, as the data below proves the graph in the prior post.

 34 hours 47 minutes total for the week to date, hence divided by 5 days elapsed so far, ANSWER is 

6 hours and 57 minutes CORRECT

If the calculation was as per the error in weekly and monthly steps,

the program would divide by 7 and give an answer of 4 hours 58 minutes.

INCORRECT 

Since the program gives the correct answer in this situation, doesn't it then INFER that it's making an error in the way it calculates averages for steps weekly or monthly. ??????????

NO MORE EXCUSES, PLEASE FIX IT FITBIT

Anyway, I've been bringing this up for 18 months and I've lost hope that Fitbit can even be stuffed in fixing it,

Loukar

[Loukar]

Hi Mariam,

PPS

Please see prior post:

The error is the same in

Calories Burned as it is for Steps.

HOWEVER

Distance, Active Minutes and Floors Climbed ALL WORK CORRECTLY

Difficult to explain!!

Loukar