Kia: Difference between revisions

Kia has explicitly designed Kia Connect as a closed platform. In 2025, the company added CAPTCHA-based authentication to its EU login process <ref>{{Cite web |last=@Jesus-M |date=2025-08-07 |title=EU login error (again) #855 |url=https://github.com/Hyundai-Kia-Connect/hyundai_kia_connect_api/issues/855 |url-status=live |archive-url=https://web.archive.org/web/20250903172139/https://github.com/Hyundai-Kia-Connect/hyundai_kia_connect_api/issues/855 |website=[[GitHub]]}}</ref>, which disrupted community integrations such as [https://evcc.io/en evcc], [https://github.com/Hyundai-Kia-Connect/hyundai_kia_connect_api hyundai_kia_connect_api], [https://github.com/Hyundai-Kia-Connect/kia_uvo Home Assistant], and others. These projects had previously enabled features such as retrieving the state of charge, smart charging with renewable energy, and integration into smart homes.

When asked about an official interface, Kia responded that “the Kia Connect ecosystem is designed as a closed platform” <ref>{{Cite web |last=@astrakid |date=2025-08-27 |title=Since Kia API update: vehicle soc: timeout #23147 |url=https://github.com/evcc-io/evcc/issues/23147#issuecomment-3229600956 |url-status=live |archive-url=https://web.archive.org/web/20251210182819/https://github.com/evcc-io/evcc/issues/23147 |website=[[GitHub]]}}</ref> and that “an implementation of a public API is currently not planned due to security concerns” <ref>{{Cite web |last=@Snited |date=2025-08-28 |title=Since Kia API update: vehicle soc: timeout #23147 |url=https://github.com/evcc-io/evcc/issues/23147#issuecomment-3233590258 |url-status=live |archive-url=https://web.archive.org/web/20251210182819/https://github.com/evcc-io/evcc/issues/23147 |website=[[GitHub]]}}</ref>.