Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Timezone issue

I have a simple Python script to reads my data from the API (using the python-fitbit module) and shuffles it off to InitialState every 15 minutes.  I am using a call to activities() to gather my steps, etc and then logging them to IS.  At no point am I manually injecting a datetime, although IS is logging the entires using UTC (but displaying the popover time as local).  No problem.

 

The issue arises in that when I request data from the Fitbit API, my data counts are reset at 8PM local (0000z) every day.  Obviously, this is an issue and I can't figure out why it is happening.  The API docs seem to imply that the data will be timezone agnostic, but shouldn't values reset at 0000 my time?  Right now, day over day steps counts are only valid from 2000 to 2000.

 

My timezone is set appropriately in the Account Settings.

 

undefined 

Best Answer
0 Votes
1 REPLY 1

It's been a few years 🙂  But did you get past this?  I'm running into the same issue.

Best Answer
0 Votes