I'm finding that historic (i.e. I'm not looking at today) calorie values in the API are often (at the moment 4 days in 6) one lower than displayed on the dashboard (e.g. the API says 3425, and the dashboard says 3426 for the 19th Jan). The API data is rounded to an integer value It appears likely to me that the rounding of the two values are inconsistent. Though the data are often displayed as charts, for me it's an issue that slightly undermines the apparent trustworthiness of apps that use the API. Is this a known issue?
