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: 

Sleep Log Web Api asleep minutes does not match FitBit stages or Fitbit UI, making my app look wrong

‎08-06-2018 03:12

‎08-06-2018 03:12

Any help on this? 
I'm using the following endpoint

Fitbit::BASE_FITBIT_API_URL . "/1.2/user/-/sleep/list.json?offset=0&limit=100&sort=desc&afterDate=" . $date,

 

Best Answer
1 REPLY 1

‎08-09-2018 20:06

‎08-09-2018 20:06

I'm seeing the same thing currently. 
I'm specifically looking "light", "wake", "deep", "rem" attributes in the Summary of the sleep response.
I've verified it with the web api explorer, so it's not just a problem with my code or the python-fitbit library. 
I compared it to the app and a CSV export. App and CSV export are consistent.

WEB api is throwing out clearly wrong numbers. In fact, there's 3 days in a row that are showing the exact same numbers.

Best Answer
0 Votes