Great, obviously I'm a bit busy now, but yes, the callbacks shouldn't be transmitting data that is always 0 - possibly that means that the last day of the month is not included?.
'movement' is slightly nebulous in it being directly related to the amount of acceleration reported from the accelerometer. It's not meant to be in any particular units, but is there purely for use in sleep tracking (when I believe dips/peaks will indicate certain sleep periods) .
However if it's always 255 for a day something is wrong. The idea is the number for the day should be the average of all entries (which are all clipped to 255 too).
Looking at the code just now I discovered a deleted line! I'll just fix and commit this
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Great, obviously I'm a bit busy now, but yes, the callbacks shouldn't be transmitting data that is always 0 - possibly that means that the last day of the month is not included?.
'movement' is slightly nebulous in it being directly related to the amount of acceleration reported from the accelerometer. It's not meant to be in any particular units, but is there purely for use in sleep tracking (when I believe dips/peaks will indicate certain sleep periods) .
However if it's always 255 for a day something is wrong. The idea is the number for the day should be the average of all entries (which are all clipped to 255 too).
Looking at the code just now I discovered a deleted line! I'll just fix and commit this