help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Is lastSyncTime really in UTC?

ANSWERED

‎08-17-2015 14:33

‎08-17-2015 14:33

Hi guys,

 

according to documentation result of querying /devices endpoint should return lastSyncTime in UTC, not user's local timezone.

 

However, when user has America/Phoenix timezone set and for this user I receive notification at 14:12 (UTC-7) and after that I make request to /devices endpoint I get 'lastSyncTime'  2015-08-17T14:12:32.060, which doesn't seem to be UTC.

 

I would expect lastSyncTime to be set to 2015-08-17T21:12:32.060

 

What am I missing?

 

Thanks.

Best Answer
Labels:
0 Votes
1 BEST ANSWER

Accepted Solutions

‎09-08-2015 12:41

‎09-08-2015 12:41

Just got reply from tech support on my email, maybe this will help somebody in future:

 

According to our tests, last sync time through that endpoint returns the last sync time in the local time of the user.

Thanks for bringing this issue to our attention. For now, please take the appropriate changes to utilize the customer's local last sync time instead of last sync time in UTC. We're sorry for the inconvenience.

 

 

View best answer in original post

Best Answer
0 Votes
2 REPLIES 2

‎08-28-2015 13:23

‎08-28-2015 13:23

No ideas?

 

Just wonder if anybody from Fitbit read this forum at all?

Best Answer
0 Votes

‎09-08-2015 12:41

‎09-08-2015 12:41

Just got reply from tech support on my email, maybe this will help somebody in future:

 

According to our tests, last sync time through that endpoint returns the last sync time in the local time of the user.

Thanks for bringing this issue to our attention. For now, please take the appropriate changes to utilize the customer's local last sync time instead of last sync time in UTC. We're sorry for the inconvenience.

 

 

Best Answer
0 Votes