Repository navigation
Kia/Hyundai: X-Fingerprint-Signatur für CCI-Gate - #4232
Open
seaspotter wants to merge 1 commit into
Open
seaspotter wants to merge 1 commit into
seaspotter wants to merge 1 commit into
Conversation
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.
Behebt den CCI-Token-Austausch-Fehler (Code 9035, "ungewöhnliche Aktivität") von #3410 (comment) (seit 2026-10-14, betrifft alle Nutzer dieses Moduls, unabhängig vom Account - gleiches Problem wie zuvor in #4099, nur eine Ebene tiefer).
Kia/Hyundai verlangen auf den CCI-Endpunkten jetzt eine X-Fingerprint-HMAC-Signatur über die Client-Identität. Ohne sie: 9035 (Header fehlt), 9036 (falsche Signatur), 9037 (Zeitstempel zu alt).
Signierschema und die Secret-Konstanten sind aus hyundai_kia_connect_api (#1352/#1355) portiert, dem Referenzprojekt, dem dieses Modul schon bisher folgt. Exchange/CCS-Exchange/Refresh versuchen jetzt zuerst den signierten Endpunkt, mit Fallback auf die bisherige unsignierte Route nur bei den Gate-eigenen Fehlercodes - andere Fehler (falsches Passwort, Serverfehler) verhalten sich unverändert.
Langfristig lohnt es sich aber nicht mehr dieses teils reverse-engineerte Modul weiter zu maintainen, da es auch von Hyundai/Kia/Genesis eine EU Data Act API gibt: https://document.pleos.ai/en/api-reference/vehicle-data-api/intro (Modul dazu folgt)