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

Time shift in PZ rides #2690

Open
mnasman1 opened this issue Oct 23, 2024 · 7 comments
Open

Time shift in PZ rides #2690

mnasman1 opened this issue Oct 23, 2024 · 7 comments
Assignees
Labels
bug Something isn't working

Comments

@mnasman1
Copy link

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):

  • OS: iOS
  • Version 2.17.0

Smartphone (please complete the following information):

  • Device: Iphone6
  • OS: ios 15.8.3
  • Version
    Wed Oct 23 07_13_09 2024_power
    Fri Oct 4 07_27_34 2024_power
    Mon Oct 21 07_13_53 2024_power

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.

@mnasman1 mnasman1 added the bug Something isn't working label Oct 23, 2024
@cagnulein
Copy link
Owner

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!

@mnasman1
Copy link
Author

@cagnulein
Copy link
Owner

Same thing, you have to wait the upload, if you want you can send me it to messenger

@mnasman1
Copy link
Author

@gorgone87
Copy link

gorgone87 commented Oct 24, 2024

Hi @mnasman1 I was looking to your issue, these are the times that Peloton instruction give us:

00:03:26 power 153
00:59:00 power 153
00:01:29 power 201
00:01:14 power 253
00:00:34 power 153
00:03:25 power 201
00:04:27 power 253
00:03:28 power 201
00:03:24 power 253
00:02:24 power 253
00:01:05 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.
In case we can try to fallback to the homefitnessbuddy API

Let me know
Thanks!

@mnasman1
Copy link
Author

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.

@cagnulein
Copy link
Owner

yes I guess so too, thanks @gorgone87
@mnasman1 what I can do is trying to prioritize homefitnessbuddy (as I did since a year ago) API.

let me know if you are interested on this

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