Support Porsche mobile auth flow and Macan EV data#84
Open
Support Porsche mobile auth flow and Macan EV data#84
Conversation
Owner
|
Thank you for this PR, it looks promising! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This updates the library to work with Porsche's current mobile auth flow and restores live vehicle data for newer vehicles such as the Macan EV.
The previous implementation relied on the older native app auth assumptions and older vehicle status endpoints. Porsche now uses a different mobile client flow and current vehicle data is available through
app/connect/v1/vehicles/....What changed
Auth flow
code_verifieracross captcha/login continuationcode_verifierConnection handling
Vehicle/account data
app/connect/v1/vehicles/...for current overview dataTested
Tested against a real Porsche account and Macan EV payloads:
Notes
This PR intentionally focuses on the underlying library. Home Assistant integration changes should be handled separately once the updated library is available.