Replies: 4 comments 2 replies
-
|
Those are the two endpoints the app is using. Does it not work to start/stop? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Will test from inside the car. But noticed some strange behaviors |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
For now everything seems fine, no error, no warning, but i'm in business trip for now so i can't easily control. Will be back at home tomorrow |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Thanks, I'll let you know |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Till,
While reviewing the climatization command handler in
connector.py, I noticed an asymmetry between the START and STOP URLs:https://ola.prod.code.seat.cloud.vwgroup.com/v2/vehicles/{vin}/climatisation/starthttps://ola.prod.code.seat.cloud.vwgroup.com/vehicles/{vin}/climatisation/requests/stopThe differences are:
/v2/version prefix, STOP does not/climatisation/startvs/climatisation/requests/stop)Is this intentional — i.e. does the Seat/Cupra API genuinely use different endpoints for start and stop? Or is one of them incorrect (copy-paste or outdated URL)?
Regards
Beta Was this translation helpful? Give feedback.
All reactions