You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently sets the date as :
date: moment().format('YYYY-MM-DD'),
If the user isn't in the same timezone as the server, this will result in the data getting reset to zero at the wrong time ( from the users perspective ).
It seems to work fine just setting :
date: 'today'
Although I've not tested the rollover yet, this would be Fitbit's problem if it goes wrong...