v2.47.0 stopped working in EU

[daviddanko]

Region and Brand of car
EU/Hyundai

Version of the integration
v2.47.0

Describe the bug
After upgrading to v2.47.0 the integration stopped working for Hyundai in EU. Downgrading to v2.46.2 fixes the issue.

Debug logs if an error occurred
I replaced all the IDs with placeholders.

2025-12-07 13:37:37.858 DEBUG (SyncWorker_2) [hyundai_kia_connect_api.KiaUvoApiEU] hyundai_kia_connect_api - Get Device ID request: https://prd.eu-ccapi.hyundai.com:8080/api/v1/spa/notifications/register {'ccsp-service-id': '<SERVICE_ID>', 'ccsp-application-id': '<APPLICATION_ID>', 'Stamp': '<STAMP>', 'Content-Type': 'application/json;charset=UTF-8', 'Host': 'prd.eu-ccapi.hyundai.com:8080', 'Connection': 'Keep-Alive', 'Accept-Encoding': 'gzip', 'User-Agent': 'okhttp/3.12.0'} {'pushRegId': '<PUSH_REG_ID>', 'pushType': 'GCM', 'uuid': '<UUID>'}
2025-12-07 13:37:38.337 DEBUG (SyncWorker_2) [hyundai_kia_connect_api.KiaUvoApiEU] hyundai_kia_connect_api - Get Device ID response: {'retCode': 'S', 'resCode': '0000', 'resMsg': {'deviceId': '<DEVICE_ID>'}, 'msgId': '<MSG_ID>'}
2025-12-07 13:37:38.337 DEBUG (SyncWorker_2) [hyundai_kia_connect_api.KiaUvoApiEU] hyundai_kia_connect_api - Get cookies request: https://prd.eu-ccapi.hyundai.com:8080/api/v1/user/oauth2/authorize?response_type=code&amp;state=test&amp;client_id=<SERVICE_ID>&amp;redirect_uri=https://prd.eu-ccapi.hyundai.com:8080/api/v1/user/oauth2/redirect&amp;lang=en
2025-12-07 13:37:38.597 DEBUG (SyncWorker_2) [hyundai_kia_connect_api.KiaUvoApiEU] hyundai_kia_connect_api - Get cookies response: {'account': '<ACCOUNT_TOKEN>'}
2025-12-07 13:37:39.261 DEBUG (SyncWorker_2) [hyundai_kia_connect_api.KiaUvoApiEU] hyundai_kia_connect_api - Get Access Token Response: {'scope': None, 'idp_cd': 'hmgid1.0', 'access_token': '<ACCESS_TOKEN>', 'refresh_token': None, 'id_token': None, 'token_type': 'Bearer', 'expires_in': 3600}

To Reproduce
Upgrade to v2.47.0

Expected behavior
The integration should function properly and not display ‘unavailable’ for each entity.

Screenshots

Additional context
N/A

[bfish2]

Same problem in US since upgrade.

[andreas-bulling]

same here

[cdnninja]

For EU could we get more logs? Looks like no errors.

[Merwases]

Same in Germany Ioniq5.
After a Raspi/HA Restart, integration is dead.
Downgrade to last version solved and got it working again.
Must be a strange bug at last version from today.

About more logs... hmmm.... I assume any maintainer is using its integration too and may watch any problem usually first, isn't it 🤔.
More logs will show same I assume too, so...?

[apigram2]

Same for me. Downgrade worked ! :) Thanks

[Puma7]

Same here, but i can't see why the log said:
2025-12-07 18:53:36.999 DEBUG (MainThread) [custom_components.kia_uvo.coordinator] Finished fetching kia_uvo data in 1.915 seconds (success: True)

So dosn't seam to be a connection issue more a issue that HA cant find the etitiy any more?

And yes, the downgrade over HACS -> KIA -> three dots -> download
works

[Merwases]

I always wonder about the point, that maintainers seems to not test any update against their own Hyundai and derivates HA setup just BEVORE releasing any new stuff to the crowd 🤔.
It' just thought as a constructive thinking of mine, as I'm always not understand such mayor failures of a smooth working top integration pointig to exactly the mentioned thing 🤷🏼‍♂️.
(May write in German if.... 😘)

[matthijs]

I've just upgraded the integration again to get some debug. But I don't get any debug info, despite the fact that I have the following in the configuration:

logger:
  default: info
  logs:
    custom_components.kia_uvo: debug

The only log I see about this integration:

2025-12-07 20:05:05.429 INFO (SyncWorker_0) [homeassistant.loader] Loaded kia_uvo from custom_components.kia_uvo
2025-12-07 20:05:05.429 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration kia_uvo which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-07 20:05:08.185 INFO (MainThread) [homeassistant.bootstrap] Domains to be set up: {'smartevse', 'input_text', 'knmi', 'backup', 'kia_uvo', 'open_meteo', 'mobile_app', 'application_credentials', 'template', 'solaredge', 'labs', 'zone', 'wake_on_lan', 'scene', 'pi_hole_v6', 'history', 'frontend', 'script', 'reolink', 'timer', 'logger', 'http', 'sun', 'input_boolean', 'dsmr_reader', 'alarmo', 'automation', 'homeassistant', 'twinkly', 'energy', 'input_select', 'hacs', 'anniversaries', 'input_number', 'mqtt', 'zha_toolkit', 'forecast_solar', 'version', 'co2signal', 'network', 'kodi', 'recorder', 'config', 'afvalinfo', 'schedule', 'zha', 'fritz', 'hardware', 'input_datetime', 'counter', 'input_button', 'analytics', 'tag', 'person', 'my', 'logbook', 'local_todo', 'switch', 'group', 'system_health', 'shell_command'}
2025-12-07 20:05:08.925 INFO (MainThread) [homeassistant.bootstrap] Setting up stage 2: {'smartevse', 'input_text', 'knmi', 'backup', 'kia_uvo', 'open_meteo', 'mobile_app', 'application_credentials', 'template', 'solaredge', 'zone', 'wake_on_lan', 'scene', 'pi_hole_v6', 'history', 'script', 'timer', 'reolink', 'sun', 'input_boolean', 'dsmr_reader', 'alarmo', 'automation', 'twinkly', 'energy', 'input_select', 'hacs', 'anniversaries', 'input_number', 'mqtt', 'zha_toolkit', 'forecast_solar', 'version', 'co2signal', 'kodi', 'afvalinfo', 'schedule', 'zha', 'fritz', 'hardware', 'input_datetime', 'counter', 'input_button', 'analytics', 'tag', 'person', 'my', 'logbook', 'local_todo', 'switch', 'group', 'system_health', 'shell_command'}; already set up: {'frontend', 'logger', 'http', 'network', 'recorder', 'homeassistant', 'config', 'labs'}
2025-12-07 20:05:13.886 INFO (MainThread) [homeassistant.setup] Setting up kia_uvo
2025-12-07 20:05:13.886 INFO (MainThread) [homeassistant.setup] Setup of domain kia_uvo took 0.00 seconds
2025-12-07 20:05:14.811 DEBUG (MainThread) [custom_components.kia_uvo.coordinator] Finished fetching kia_uvo data in 0.913 seconds (success: True)
2025-12-07 20:05:24.933 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up kia_uvo.binary_sensor
2025-12-07 20:05:24.933 INFO (MainThread) [homeassistant.components.sensor] Setting up kia_uvo.sensor
2025-12-07 20:05:24.934 INFO (MainThread) [homeassistant.components.device_tracker] Setting up kia_uvo.device_tracker
2025-12-07 20:05:24.936 INFO (MainThread) [homeassistant.components.lock] Setting up kia_uvo.lock
2025-12-07 20:05:24.937 INFO (MainThread) [homeassistant.components.number] Setting up kia_uvo.number

When doing a 'Force update' I get the following response:

2025-12-07 20:37:03.058 DEBUG (MainThread) [custom_components.kia_uvo.coordinator] Finished fetching kia_uvo data in 0.003 seconds (success: True)

The response is almost immediately, normally this takes between 5 and 15 seconds.

[cdnninja]

I always wonder about the point, that maintainers seems to not test any update against their own Hyundai and derivates HA setup just BEVORE releasing any new stuff to the crowd 🤔. It' just thought as a constructive thinking of mine, as I'm always not understand such mayor failures of a smooth working top integration pointig to exactly the mentioned thing 🤷🏼‍♂️. (May write in German if.... 😘)

Well it says right on the home page that I no longer own one of these cars, even if I did each region is unique. Are you volunteering to fix this?

[cdnninja]

I've just upgraded the integration again to get some debug. But I don't get any debug info, despite the fact that I have the following in the configuration:

logger:
  default: info
  logs:
    custom_components.kia_uvo: debug

The only log I see about this integration:

2025-12-07 20:05:05.429 INFO (SyncWorker_0) [homeassistant.loader] Loaded kia_uvo from custom_components.kia_uvo
2025-12-07 20:05:05.429 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration kia_uvo which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-07 20:05:08.185 INFO (MainThread) [homeassistant.bootstrap] Domains to be set up: {'smartevse', 'input_text', 'knmi', 'backup', 'kia_uvo', 'open_meteo', 'mobile_app', 'application_credentials', 'template', 'solaredge', 'labs', 'zone', 'wake_on_lan', 'scene', 'pi_hole_v6', 'history', 'frontend', 'script', 'reolink', 'timer', 'logger', 'http', 'sun', 'input_boolean', 'dsmr_reader', 'alarmo', 'automation', 'homeassistant', 'twinkly', 'energy', 'input_select', 'hacs', 'anniversaries', 'input_number', 'mqtt', 'zha_toolkit', 'forecast_solar', 'version', 'co2signal', 'network', 'kodi', 'recorder', 'config', 'afvalinfo', 'schedule', 'zha', 'fritz', 'hardware', 'input_datetime', 'counter', 'input_button', 'analytics', 'tag', 'person', 'my', 'logbook', 'local_todo', 'switch', 'group', 'system_health', 'shell_command'}
2025-12-07 20:05:08.925 INFO (MainThread) [homeassistant.bootstrap] Setting up stage 2: {'smartevse', 'input_text', 'knmi', 'backup', 'kia_uvo', 'open_meteo', 'mobile_app', 'application_credentials', 'template', 'solaredge', 'zone', 'wake_on_lan', 'scene', 'pi_hole_v6', 'history', 'script', 'timer', 'reolink', 'sun', 'input_boolean', 'dsmr_reader', 'alarmo', 'automation', 'twinkly', 'energy', 'input_select', 'hacs', 'anniversaries', 'input_number', 'mqtt', 'zha_toolkit', 'forecast_solar', 'version', 'co2signal', 'kodi', 'afvalinfo', 'schedule', 'zha', 'fritz', 'hardware', 'input_datetime', 'counter', 'input_button', 'analytics', 'tag', 'person', 'my', 'logbook', 'local_todo', 'switch', 'group', 'system_health', 'shell_command'}; already set up: {'frontend', 'logger', 'http', 'network', 'recorder', 'homeassistant', 'config', 'labs'}
2025-12-07 20:05:13.886 INFO (MainThread) [homeassistant.setup] Setting up kia_uvo
2025-12-07 20:05:13.886 INFO (MainThread) [homeassistant.setup] Setup of domain kia_uvo took 0.00 seconds
2025-12-07 20:05:14.811 DEBUG (MainThread) [custom_components.kia_uvo.coordinator] Finished fetching kia_uvo data in 0.913 seconds (success: True)
2025-12-07 20:05:24.933 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up kia_uvo.binary_sensor
2025-12-07 20:05:24.933 INFO (MainThread) [homeassistant.components.sensor] Setting up kia_uvo.sensor
2025-12-07 20:05:24.934 INFO (MainThread) [homeassistant.components.device_tracker] Setting up kia_uvo.device_tracker
2025-12-07 20:05:24.936 INFO (MainThread) [homeassistant.components.lock] Setting up kia_uvo.lock
2025-12-07 20:05:24.937 INFO (MainThread) [homeassistant.components.number] Setting up kia_uvo.number

When doing a 'Force update' I get the following response:

2025-12-07 20:37:03.058 DEBUG (MainThread) [custom_components.kia_uvo.coordinator] Finished fetching kia_uvo data in 0.003 seconds (success: True)

The response is almost immediately, normally this takes between 5 and 15 seconds.

The debug will need the API listed "hyundai_kia_connect_api" for logging.

One item that would be helpful to narrow this down is switching the hyundai_kia_connect_api in the manifest to older versions of the API and restarting until it works:

https://github.com/Hyundai-Kia-Connect/hyundai_kia_connect_api/releases

Last version was 3.49.4. Few existed in between. This would help narrow down if the API or the integration.

[matthijs]

When using the current version (2.47.0) with 3.49.4, I get the following:

2025-12-07 21:54:57.686 ERROR (SyncWorker_7) [hyundai_kia_connect_api.ApiImplType1] Unknown error in API response: Authorization field missing
2025-12-07 21:54:57.693 ERROR (MainThread) [custom_components.kia_uvo.coordinator] Unexpected error fetching kia_uvo data
Traceback (most recent call last):
  File "/home/homeassistant/hass-venv313/lib/python3.13/site-packages/homeassistant/helpers/update_coordinator.py", line 419, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/homeassistant/.homeassistant/custom_components/kia_uvo/coordinator.py", line 126, in _async_update_data
    await self.async_check_and_refresh_token()
  File "/home/homeassistant/.homeassistant/custom_components/kia_uvo/coordinator.py", line 190, in async_check_and_refresh_token
    await self.hass.async_add_executor_job(
        self.vehicle_manager.check_and_refresh_token
    )
  File "/usr/lib/python3.13/concurrent/futures/thread.py", line 59, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/home/homeassistant/hass-venv313/lib/python3.13/site-packages/hyundai_kia_connect_api/VehicleManager.py", line 155, in check_and_refresh_token
    self.initialize_vehicles()
    ~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/home/homeassistant/hass-venv313/lib/python3.13/site-packages/hyundai_kia_connect_api/VehicleManager.py", line 89, in initialize_vehicles
    vehicles = self.api.get_vehicles(self.token)
  File "/home/homeassistant/hass-venv313/lib/python3.13/site-packages/hyundai_kia_connect_api/ApiImplType1.py", line 127, in get_vehicles
    _check_response_for_errors(response)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^
  File "/home/homeassistant/hass-venv313/lib/python3.13/site-packages/hyundai_kia_connect_api/ApiImplType1.py", line 107, in _check_response_for_errors
    raise APIError(f"Unknown error in API response: {error_reason}")
hyundai_kia_connect_api.exceptions.APIError: Unknown error in API response: Authorization field missing

[matthijs]

With version: 3.51.0 I get the following log:

2025-12-07 22:01:08.164 ERROR (MainThread) [custom_components.kia_uvo.coordinator] Unexpected error fetching kia_uvo data
Traceback (most recent call last):
  File "/home/homeassistant/hass-venv313/lib/python3.13/site-packages/homeassistant/helpers/update_coordinator.py", line 419, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/homeassistant/.homeassistant/custom_components/kia_uvo/coordinator.py", line 126, in _async_update_data
    await self.async_check_and_refresh_token()
  File "/home/homeassistant/.homeassistant/custom_components/kia_uvo/coordinator.py", line 190, in async_check_and_refresh_token
    await self.hass.async_add_executor_job(
        self.vehicle_manager.check_and_refresh_token
    )
  File "/usr/lib/python3.13/concurrent/futures/thread.py", line 59, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/home/homeassistant/hass-venv313/lib/python3.13/site-packages/hyundai_kia_connect_api/VehicleManager.py", line 163, in check_and_refresh_token
    self.token.valid_until - timedelta(seconds=10)
    ~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~
OverflowError: date value out of range

And tried again with 3.51.1, every sensor stays unavailable. Also for the other versions.

I'll try the previous version (2.46.2) and try with newer api versions.

[matthijs]

For your info: I've tried every combination: 2.46.2 with 3.49.4 up to 3.51.1 and it works fine.

So I guess something is wrong with the 2.47.0 release. Hopefully this will help in finding the problem. If you want me to test more just let me know. But that will be tomorrow...

[nickv1091]

same issue here. I also downgraded and brought my attributes back online.

[cdnninja]

@renatkh