10-24-2024 12:51
10-24-2024 12:51
Hello--
I'm hoping someone can advise me on a problem I'm experiencing using the recommended python client for Fitbit data. I'm retrieving data for a single device. That device is syncing correctly and all of the (many) API calls I'm making for this device are returning correct data except one: The data for the "activities/steps" resource has been zero for every day starting August 28 (and it returned an incorrect value of 12 steps for August 27).
The API endpoint I'm using (actually, that the fitbit python client is using on my behalf) is shown in the following log fragment (where STARTDATE and ENDDATE are, in the actual URL, August 15 and October 23 in YYYY-MM-DD format-- including those date strings is not allowed by the forum software?)
urllib3.connectionpool[32794] DEBUG Starting new HTTPS connection (1): api.fitbit.com:443
urllib3.connectionpool[32794] DEBUG https://api.fitbit.com:443 "GET /1/user/-/activities/steps/date/STARTDATE/ENDDATE.json HTTP/1.1" 200 None
For what it's worth, the Fitbit iOS app exhibits what appears to be a symptom of the same underlying problem: It displays all activity and sleep data correctly except step data, for which it displays the exact same values shown above: Good values until August 26, a weird value (12) on August 27 and zeros since then.
Does anyone have information that might help me understand what's going on here? The fact that the iOS client exhibits this problem makes me think it's not a problem with my code. Anybody heard of problems with this API?
Thanks!
10-24-2024 13:08
10-24-2024 13:08
Hi @jsinnott
If there isn't any data in the mobile app, then the Web API is going to return the same response. So, this problem might be with the mobile app or syncing service. I'm going to send you an email to request some additional data to investigate further. If the problem seems to be with the mobile app or syncing, then I'll need to move you over to the main customer service team to troubleshoot.
10-24-2024 13:10
10-24-2024 13:10
Hi Gordon--
Thanks so much for the quick reply. I'll look forward to your email 😄.
..j
10-24-2024 19:18
10-24-2024 19:18
Hi @jsinnott
I've moved your post to the iOS team. As I said, I didn't see steps for your account through one of our tools, which is why you are probably getting 0 steps through the Web API. Someone on this team can help figure out why the steps are not coming through.
Best!
10-24-2024 22:20
10-24-2024 22:20
I believe I’m experiencing a similar issue?4 Weeks are now displaying little to no data and I’m seeing many 0s as of this month.
10-24-2024 22:51
10-24-2024 22:51
Forgive the typo in the previous post. Many random days and weeks are showing 0s under several metrics including hourly activity and steps. I’m glad I snagged the first screenshot in August!
10-27-2024 13:53 - edited 10-28-2024 08:23
10-27-2024 13:53 - edited 10-28-2024 08:23
@Gordon-C I have had the same problem as well. Note that I get a weekly email from fit bit that shows the actual steps taken, distance floors, and calories. So the device is successfully updating the servers. The app just can't read the data from the servers and display and aggregate them. This is purely function of the app and you will see it among the android users as well.
Thanks for trying to get this fixed!
10-28-2024 14:50
10-28-2024 14:50
@GordonFitbit , very nice to see input from you here. You are the very first person to respond to this problem who seems to be identified as someone with an actual connection to Google technical service. Do you have the ability to see that this incredibly frustrating problem that began August 26 gets fixed? Large numbers of your Fitbit users are unable to use their devices as needed. It is impossible for me to believe that you and your technical colleagues do not have the knowledge and skills to swiftly fix this problem. So, why hasn't it been fixed for months? Why must this continue?
Also, Mr. Crenshaw, we really, really want the Windows Dashboard back. That Dashboard was significantly superior to the new Google app. It is incomprehensible that it was arbitrarily removed. Please, please, could you try to get Google to put it back up?
Thanks!