Blaze on Android can't calculate weekly sleep averages

[BillIrwin]

After waiting almost nine months to have the weekly report step count variance always being 10,281 different than last week fixed, it will be interesting to see how long this one takes. Now that I have seen two examples of simple math being grossly incorrect I can't trust any of the analysis without checking the reports manually to verify they are correct. This should be done in beta and quality control, but isn't being done ... obviously.

It's time to build a spreadsheet to track my progress and give up on the pretty presentation. I will take accuracy over appearance any day.

I never would have checked if the average hadn't been so low - 4:46, when the lowest sleep was 6:19.

I went to the website and it shows the correct average, so this bug is at least in the Android app and possibly the iOS app as well. I'm using Android Fitbit version 2.67.2 (2193262).

Fitbit, let's see if this simple mathematical bug can be corrected in under six months. You should take a serious look at your quality control system (is there one?) to understand how obvious and simple errors like these get out to your customers. Ask yourself how many of your trackers are sold from a recommendation from someone else. Then translate that into a dollar amount of lost sales due to your customers being exposed to simple bugs. Your path should be clear then.

[AlejandraFitbit]

It's great to see you around @BillIrwin.

I appreciate the attachment. Could you please be more specific about the issue you are having with your sleep information? Since by seeing the image, I can see that the tracker is registering this information. In the meantime, you can take a look at our What should I know about sleep stages? article. Also, verify that your Fitbit app is updated.

See you around. 

[BillIrwin]

Seriously? I am incapable of being any clearer or specific than I have already been .The weekly average is wrong! If this is not obvious to you then pass it to someone else. Any programmer would see the problem instantly .

[BillIrwin]

I just checked and my Android app was updated two days ago .Hopefully that this bug has been fixed quickly I went to the sleep analysis and saw the same erroneous average sleep calculation. It's still broken.

You should be able to replicate this bug on any Android phone unless the problem is specific to something. I see the bug on both my Samsung Galaxy Tab A and my Galaxy S4 phone so I suspect it's pervasive .