Farfar
commented
1 year ago I saw quite some people with issues (#174, #175, #176, #178) on the integration which is caused by a missing Consent in the MySkoda App.
I managed to capture the calls which are performed to GET the specific consent-status and POST a confirmation (by accepting the terms). Maybe it would be helpful to check the status of the consent and use it to throw a more cleaner error in the logging.
- A GET call is done to https://api.connect.skoda-auto.cz/api/v1/users/[USERID]/identities which returns:
{ "identities": [{ "identity": "MBB", "actionsToCompleteIdentity": [] }, { "identity": "DCS", "actionsToCompleteIdentity": [] }, { "identity": "CONNECT", "actionsToCompleteIdentity": ["GIVE_DOCUMENT_CONSENT"] }, { "identity": "CABS", "actionsToCompleteIdentity": [] }] }The GIVE_DOCUMENT_CONSENT is probably the status that prevents further actions to the API to get the car status.
{ "consentRequired": true, "versionDetails": { "id": "[ID]", "versionId": "[VERSIONID]", "locale": "en-GB", "title": "ŠKODA Connect", "text": "<br>\n\n### Terms and Conditions\n----------------\nImportant legal terms and information for setting up and using ŠKODA Connect services.\n\n[TERMS AND CONDITIONS ŠKODA CONNECT > ](https://consent.vwgroup.io/consent/v1/texts/SkodaConnect/gb/en/termsOfUse/latest/html)\n\n<br>\n\n### Information on Personal Data Processing\n----------------\nInformation on handling user data across ŠKODA Connect functions.\n\n[INFORMATION ON PERSONAL DATA PROCESSING > ](https://consent.vwgroup.io/consent/v1/texts/SkodaConnect/gb/en/dataprivacy/latest/html)", "disclaimer": "" }, "consent": { "id": "[ID]", "userId": "[USERID]", "decision": true, "versionDetailsId": "[VERSIONID]", "collector": "[COLLECTOR]@apps_vw-dilab_com", "updatedAt": "2021-10-14T09:02:53Z", "version": 2 } }
- A POST is done to https://document-consent.vwgroup.io/api/v2/consents to confirm the decision to accept the terms
Payload {"decision":true,"userId":"[USERID]","versionDetailsId":"[VERSIONID]"}
Response
{ "id": "[NEWID?]", "userId": "[USERID]", "decision": true, "versionDetailsId": "[OTHERVERSIONID], "collector": "[COLLECTOR]@apps_vw-dilab_com", "updatedAt": "2023-01-15T21:42:35.045Z", "version": 3 }
- After accepting the terms the first GET call to https://api.connect.skoda-auto.cz/api/v1/users/[USERID]/identities return this response:
{ "identities": [{ "identity": "MBB", "actionsToCompleteIdentity": [] }, { "identity": "DCS", "actionsToCompleteIdentity": [] }, { "identity": "CONNECT", "actionsToCompleteIdentity": [] }, { "identity": "CABS", "actionsToCompleteIdentity": [] }] }
Yes! This is exactly the type of information I need to improve the integration under these circumstances. I've seen this endpoint being used from version 5.x of the app, it wasn't used in 4.x, it had another endpoint to check valid consent. Now the question is: how to get the document ID. It would be nice to add the functionality to accept from config flow. For starters it should be enough with this information to implement a check that throws a relevant error message.
RamonQu
dvx76
I saw quite some people with issues (#174, #175, #176, #178) on the integration which is caused by a missing Consent in the MySkoda App.
I managed to capture the calls which are performed to GET the specific consent-status and POST a confirmation (by accepting the terms). Maybe it would be helpful to check the status of the consent and use it to throw a more cleaner error in the logging.
A GET call is done to https://api.connect.skoda-auto.cz/api/v1/users/[USERID]/identities which returns:
The GIVE_DOCUMENT_CONSENT is probably the status that prevents further actions to the API to get the car status.
A GET call is done to https://document-consent.vwgroup.io/api/v2/consents/required?document-id=[DOCID]&user-id=[USERID}&locale=en-GB
Payload {"decision":true,"userId":"[USERID]","versionDetailsId":"[VERSIONID]"}
Response