Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strava 3.2.42/ HA 2024.11.3 - All Run Values show significantly decreased values #188

Open
Plawasan opened this issue Nov 22, 2024 · 7 comments
Assignees
Labels
bug Something isn't working

Comments

@Plawasan
Copy link

Plawasan commented Nov 22, 2024

I'm on version 3.2.42 and I've noticed today after updating to 2023.11.3 that the ALL Run values started showing bogus data. YTD still show correct:

image

image

image

And data directly from Strava:

image

There are no error messages in logs.

Thanks

@craibo craibo self-assigned this Nov 25, 2024
@craibo craibo added the bug Something isn't working label Nov 25, 2024
@craibo
Copy link
Owner

craibo commented Nov 25, 2024

Hi @Plawasan

I have also noticed this.
I do not believe it is the integration but rather something that has changed on the Strava API.
Will look into this soon as I have a bit of time

@craibo
Copy link
Owner

craibo commented Nov 25, 2024

I have confirmed this is an issue with the Strava API and raised a query with Strava Community.
Will update this issue when I know a clear path forward

@craibo
Copy link
Owner

craibo commented Nov 26, 2024

The issue raised on Strava Community, no response yet
https://communityhub.strava.com/developers-api-7/athlete-v3-stats-api-all-run-totals-and-others-are-incorrect-7826

@jouster1974
Copy link

jouster1974 commented Dec 14, 2024

for clarity, 2023.12.3 hasnt fixed this

As you can see, my reported total running distance is a little off

image

image

total ride distance even more so

image

image

@craibo
Copy link
Owner

craibo commented Dec 14, 2024

This issue has been investigated and confirmed by Strava. A Ticket has been opened to get the issue with the API values fixed.
No ETA at this point.

@craibo
Copy link
Owner

craibo commented Dec 20, 2024

Response from Strava:

Thanks for following up. The team has actually just identified the issue.
The data that is exposed is the expected data - only data from activities set to Everyone visibilty. Previously there was a bug, which included cumulative data for activities with other visibility settings.
Let us know if you see anything different as you navigate.

I have responded. After making activities visibly to Everyone the counts do not correct themselves.
In addition,

  1. The read_all scope should allow us to get the private activities to.
  2. There are discrepancies between the different counts YTD, ALL Recent

@Plawasan
Copy link
Author

That's a bs response.. you're not polling an API for public info, you're polling it with a token for the specific user so not exposing the private entries is just stupid. Keep fighting! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants