-
-
Notifications
You must be signed in to change notification settings - Fork 115
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
Time shift in PZ rides #2690
Comments
hi @mnasman1 thanks but the log is corrupted :( could you please upload it again and wait for the finish of the upload before pushing comment? Thanks! |
Same thing, you have to wait the upload, if you want you can send me it to messenger |
Hi @mnasman1 I was looking to your issue, these are the times that Peloton instruction give us: 00:03:26 power 153 If these metrics aren’t matching to your workout then tue issue is related to Peloton API, it means that Peloton API are sending the wrong metrics. Let me know |
I kinda figured it was an issue with the api skipping the time allotted to spin ups and moving right into the build. It must be something with the way older rides are configured. |
yes I guess so too, thanks @gorgone87 let me know if you are interested on this |
Describe the bug
Some powerzone rides seem to shift the time forward skipping the time allotted for spin ups and having a long z1 at the end of the ride.
To Reproduce
Steps to reproduce the behavior:
It seems to be random, although it happens more on older rides.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Append a debug log
Uploading debug-Wed_Oct_23_06_40_50_2024.log…
Follow this guide https://github.com/cagnulein/qdomyos-zwift/wiki/How-do-i-get-the-debug-log-in-case-something-doesn't-work%3F
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: