Resolved -
Fitbit has communicated to us that they have resolved all open issues around their application and their API syncing. We are resolving this status page and appreciate everyone's patience with this. It has been challenging as there were things out of our control with changes to the Fitbit API and Fitbit issues that required their attention.
If you encounter scenarios where you see a cloud-connected Fitbit user seeing different things in what is showing in the user's Fitbit application and what is in the Validic API, Validic technical support is here to assist. We do request that you do the following before writing in though.
1. Work through the steps on this page with the affected user: https://help.validic.com/space/VCS/3480453131/How+to+troubleshoot+Inform+issues
2. If working through those steps doesn't resolve the issue then open a ticket with our team and share the troubleshooting steps you have taken along with screenshots of the user's Fitbit application that shows a difference in what is in the Inform API. Don't forget to share the Validic ID and Org ID. Validic technical support will need that information to fully investigate the scenario for the user.
Oct 22, 10:27 EDT
Update -
We want to provide you with an update on the current status of our integration with Fitbit. Our team met with Fitbit late last week and there are open items on both sides to find a resolution to the changes that Fitbit made to its API.
Current known issues include:
1. Data inconsistencies with calories burned, distance, and time in heart rate zone values.
2. Data delays/inaccuracies with steps, distance, calories burned, and time in heart rate zones.
Fitbit is working to address these issues.
In addition, a recent change to their processing algorithms has made it possible for you to receive values that are much higher or much lower than you might expect. It’s even possible that you could get negative values from Fitbit for these metrics. Please see our FAQ for more information about this change and how you can help your users: https://help.validic.com/space/VCS/4174643202/Understanding+Recent+Changes+in+Fitbit+Data+Display
Our Recent Improvements:
- Enhanced our data validation processes to catch and handle unexpected data formats
- Improved our error logging and monitoring systems to quickly identify and respond to issues
- Updated our documentation to provide clarity on current limitations and workarounds
Next Steps:
Validic will be adjusting our Fitbit integration to start reporting all calorie values as they are received from Fitbit. This alert will be updated once our code change is deployed. In the meantime, please see our FAQ for more information about this change and how you can help your users: https://help.validic.com/space/VCS/4174643202/Understanding+Recent+Changes+in+Fitbit+Data+Display
We will continue to provide updates as we make progress with Fitbit.
Sep 30, 09:56 EDT
Update -
Though Fitbit has removed the web API status page entry from their website we are still seeing data inconsistencies. We are in communication with Fitbit regarding the elements noted in previous posts on this status page.
This page will be updated when we get further input from Fitbit on their undocumented changes to data delivered through their API
Sep 20, 13:36 EDT
Update -
There has been a delay in updating this status page due to there being not a lot of movement to report.
Fitbit is still reporting issues with their WebAPI on their status page https://status.fitbit.com/
We have open communication with Fitbit and are awaiting updates on the issues mentioned on 9/5 on this status page as well as data latency issues which are causing slowness on our end. We can only deliver the data to our clients when the data is received from the vendor API.
We've been told they are working on both the changes in the data sent in their API (9/5 post) as well as the latency issues from the Fitbit API we are experiencing.
This page will be updated when there is additional information to share on the path to resolution.
Sep 13, 15:26 EDT
Update -
We are currently waiting for Fitbit to respond with input from their side regarding the fix we put in and any additional fixes we may need to implement to account for the change in data delivery through their API. We will update when additional information is made available from Fitbit.
Sep 9, 10:00 EDT
Update -
Summary
We are continuing to investigate data inconsistencies originating at Fitbit impacting the data payloads delivered to us through their API for summary and workout endpoints. These changes were first observed late last week and immediately brought to Fitbit’s attention.
Issues Identified
Negative Calorie Values: Some records from Fitbit contain negative calorie values.
Action taken: We are ignoring these negative values.
Impact: Some Validic clients may not receive calorie data in affected records.
Data Type Inconsistencies: Certain metrics are occasionally received as strings instead of numbers.
This issue often correlates with the presence of negative metrics.
Action taken: We are dropping records with unexpected data types.
Additional Data Format Change
A separate issue was identified and addressed regarding a change in Fitbit's data format.
We are actively monitoring this change and are prepared to adjust if Fitbit reverts to the previous format.
Affected Metrics
The following metrics have been observed to be intermittently affected by the above issues:
heart_rate_zone_very_low
heart_rate_zone_low
heart_rate_zone_medium
heart_rate_zone_high
energy_burned
basal_energy_burned
active_energy_burned
Note: Not all records for these metrics are affected. We are only dropping metric values with negative values or unexpected data types. You will receive all normal and expected metric values.
Current Actions
We have escalated both the negative metric values and data type inconsistencies to Fitbit for investigation.
Our team is continuously monitoring the situation and will provide updates as more information becomes available.
Next Steps
We will continue to work closely with Fitbit while they resolve these issues and minimize the impact on our clients. Further updates will be provided as the situation develops.
Sep 5, 12:59 EDT
Monitoring -
A fix has been deployed to account for changes made by Fitbit. Data is flowing successfully. We are monitoring to ensure the fix resolves the issues encountered with the integration.
Sep 4, 23:12 EDT
Update -
We are continuing to work on a fix for this issue.
Sep 4, 14:16 EDT
Identified -
We have identified the issue and a fix is being groomed. I'll update this page when that solution is released to account for the change from the Fitbit end.
Sep 4, 08:40 EDT
Investigating -
Validic is investigating possible issues with the delivery of data from Fitbit.
As a result, you may see delays in receiving user data from Fitbit users and users may see issues when trying to sync to Fitbit.
We will provide updates here when they are available.
Sep 4, 00:12 EDT