hyundai_kia_connect_api
hyundai_kia_connect_api copied to clipboard
Published
20 hours ago •
Hyundai-Kia-Connect
Hyundai-Kia-Connect
Client should attempt to log in when receiving an error fetching data
- Hyundai / Kia Connect version: 3.11.4
- Python version: python3.11
- Operating System: hassio
Description
When receiving an error from the USA endpoint, the token did not automatically refresh.
The first sign in was:
2024-01-01 15:11:21.188 DEBUG (SyncWorker_19) [hyundai_kia_connect_api.KiaUvoAPIUSA] hyundai_kia_connect_api - Sign In Response {"status":{"statusCode":0,"errorType":0,"errorCode":0,"errorMessage":"Success with response body"}}
The second sign in was due to the
2024-01-02 14:13:50.245 DEBUG (SyncWorker_22) [hyundai_kia_connect_api.VehicleManager] hyundai_kia_connect_api - Refresh token expired
2024-01-02 14:13:50.818 DEBUG (SyncWorker_22) [hyundai_kia_connect_api.KiaUvoAPIUSA] hyundai_kia_connect_api - Sign In Response {"status":{"statusCode":0,"errorType":0,"errorCode":0,"errorMessage":"Success with response body"}}
The failed sync:
2024-01-03 12:01:01.247 DEBUG (SyncWorker_27) [hyundai_kia_connect_api.KiaUvoAPIUSA] hyundai_kia_connect_api - sending https://api.owners.kia.com/apigw/v1/cmm/gvi request with {'vehicleConfigReq': {'airTempRange': '0', 'maintenance': '1', 'seatHeatCoolOption': '0', 'vehicle': '1', 'vehicleFeature': '0'}, 'vehicleInfoReq': {'drivingActivty': '0', 'dtc': '1', 'enrollment': '1', 'functionalCards': '0', 'location': '1', 'vehicleStatus': '1', 'weather': '0'}, 'vinKey': ['XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX']}
2024-01-03 12:01:01.586 DEBUG (SyncWorker_27) [hyundai_kia_connect_api.KiaUvoAPIUSA] hyundai_kia_connect_api got response <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Draft//EN">
<HTML>
<HEAD>
<TITLE>Error 404--Not Found</TITLE>
</HEAD>
<BODY bgcolor="white">
<FONT FACE=Helvetica><BR CLEAR=all>
<TABLE border=0 cellspacing=5><TR><TD><BR CLEAR=all>
<FONT FACE="Helvetica" COLOR="black" SIZE="3"><H2>Error 404--Not Found</H2>
</FONT></TD></TR>
</TABLE>
<TABLE border=0 width=100% cellpadding=10><TR><TD VALIGN=top WIDTH=100% BGCOLOR=white><FONT FACE="Courier New"><FONT FACE="Helvetica" SIZE="3"><H3>From RFC 2068 <i>Hypertext Transfer Protocol -- HTTP/1.1</i>:</H3>
</FONT><FONT FACE="Helvetica" SIZE="3"><H4>10.4.5 404 Not Found</H4>
</FONT><P><FONT FACE="Courier New">The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.</p><p>If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.</FONT></P>
</FONT></TD></TR>
</TABLE>
</BODY>
</HTML>
What I Did
Reloading the integration resolved the issue
