Repository navigation
fix: kia/hyundai Login - #4099
Merged
Merged
Conversation
LKuemmel
approved these changes
Oct 13, 2026
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 das in Discussion #3410 gemeldete Problem: der SoC-Abruf schlägt für alle Kia/Hyundai-Nutzer dieses Moduls fehl, unabhängig vom eigenen Account/Passwort.
Ursache: Kia/Hyundais IDPConnect-Server blockiert inzwischen die
client_id, den dieses Modul für den Login verwendet, serverseitig als "abusing request". Das ist kein individuelles Credentials-Problem - alle Nutzer mit dieser client_id sind betroffen.Fix: Portiert den OneApp/CCI-Login-Flow aus dem hyundai_kia_connect_api-Projekt (Home-Assistant-Integration, der dieses Modul schon bisher als Referenz folgt - siehe #3751). Der neue Flow nutzt einen anderen, nicht blockierten client_id für Authorize/Signin, tauscht den Code dann über zwei zusätzliche Schritte (CCI-Token, dann CCS-Token) gegen einen Token, der von den bestehenden
ccapi:8080-Endpunkten weiterhin akzeptiert wird - alle nachgelagerten Funktionen (Fahrzeugstatus, PIN, etc.) bleiben unverändert.