Failed setup, will retry: Incomplete update received

[zipposi]

Describe the bug
After the last update the integration no longer connect to the Škoda services. The app works as usual.. I tried do uninstall and reinstall the integration, the result is the same.

Is this working in MySkoda app?*
I loged out and reloged in the MySkoda app, no problems or warnings.

Latest working release
It stopped working after the last update (I noticed it around 20.12.2024). But not sure, because it took me a few days to see the problem.

Debug logs

Logger: myskoda.rest_api
Source: /usr/local/lib/python3.13/site-packages/myskoda/rest_api.py:103
First occurred: 18:38:10 (5 occurrences)
Last logged: 18:39:12

Invalid status for GET request to /v1/vehicle-automatization/TMBZZZAAZMD802498/departure/timers: 500
Invalid status for GET request to /v1/vehicle-automatization/TMBZZZAAZMD802498/departure/timers: 429
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/site-packages/myskoda/rest_api.py", line 97, in _make_request
    response.raise_for_status()
    ~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/client_reqrep.py", line 1161, in raise_for_status
    raise ClientResponseError(
    ...<5 lines>...
    )
aiohttp.client_exceptions.ClientResponseError: 500, message='Internal Server Error', url='https://mysmob.api.connect.skoda-auto.cz/api/v1/vehicle-automatization/TMBZZZAAZMD802498/departure/timers'

Installation:

• Home Assistant variant: [e.g. Hass OS, on Home Assistant Green HW.
• Python version - don't know - probably up-to-date, because everything is updated.

Additional context
After reinstalling there are no errors after entering username and password, but after this is finished there are no devices and the error is displayed in the integration module.

[dvx76]

The only thing the log extract shows are the Skoda API returning HTTP 500 (internal server error) and 429 (rate limiting). If you believe this is caused by the latest version you can force HACS to install an older version to test that theory. But by the looks of it the problem is due to errors/limit coming from the API.

[zipposi]

What can I do about it? If is the API limit, why is thew app working - isn't the same access (same user/pass..)?

[zipposi]

BTW: Thanks for the integration. Now I have a problem, but I really appreciate your work.

[zipposi]

Is enough to wait a few days and then re-enable the integration?

[prvakt]

please try again tomorrow.. usually MySkoda resets those API limits after midnight.. We have added departure endpoint recently for cars with departure timers capability and probably this is causing problem for your car.. I will have a look on this, but can take some time because of Christmas 🎅 May I know what car you have?

update: if is it CitigoE iV, it looks like this car is very sensitive and with very low API limit for some endpoints

[Dedier]

update: if is it CitigoE iV, it looks like this car is very sensitive and with very low API limit for some endpoints

I've the same issue, my car is a CitigoE iV. I've waited almost a whole day to make sure the rate limit was removed (disabled the app to make sure it didn't connect the Skoda). I just enabled it again and this is the first part of the log file. I might have overlooked something important, but there is quite some sensitive information in the logfile, therefor didn't want to upload the whole file. Please let me know if I can do some other testing / missed something important in the logfile I can add to assist with finding the solution. I'm running version 1.17.2 and tried to newly install the integration (didn't test previous versions).

2024-12-24 00:45:57.105 WARNING (MainThread) [myskoda.auth.authorization] Retrying failed request to refresh token (0/5). Retrying... 2024-12-24 00:45:58.206 WARNING (MainThread) [myskoda.auth.authorization] Retrying failed request to refresh token (1/5). Retrying... 2024-12-24 00:45:59.315 WARNING (MainThread) [myskoda.auth.authorization] Retrying failed request to refresh token (2/5). Retrying... 2024-12-24 00:46:55.688 ERROR (MainThread) [myskoda.rest_api] Invalid status for GET request to /v2/air-conditioning/***/auxiliary-heating: 500 Traceback (most recent call last): File "/usr/local/lib/python3.12/site-packages/myskoda/rest_api.py", line 97, in _make_request response.raise_for_status() File "/usr/local/lib/python3.12/site-packages/aiohttp/client_reqrep.py", line 1157, in raise_for_status raise ClientResponseError( aiohttp.client_exceptions.ClientResponseError: 500, message='Internal Server Error', url='https://mysmob.api.connect.skoda-auto.cz/api/v2/air-conditioning/***/auxiliary-heating' 2024-12-24 00:46:57.706 ERROR (MainThread) [myskoda.rest_api] Invalid status for GET request to /v1/vehicle-automatization/***/departure/timers: 500 Traceback (most recent call last): File "/usr/local/lib/python3.12/site-packages/myskoda/rest_api.py", line 97, in _make_request response.raise_for_status() File "/usr/local/lib/python3.12/site-packages/aiohttp/client_reqrep.py", line 1157, in raise_for_status raise ClientResponseError( aiohttp.client_exceptions.ClientResponseError: 500, message='Internal Server Error', url='https://mysmob.api.connect.skoda-auto.cz/api/v1/vehicle-automatization/***/departure/timers' 2024-12-24 00:47:02.995 DEBUG (MainThread) [myskoda.mqtt] Sending PINGREQ 2024-12-24 00:47:03.007 DEBUG (MainThread) [myskoda.mqtt] Sending PINGREQ 2024-12-24 00:47:03.010 DEBUG (MainThread) [myskoda.mqtt] Received PINGRESP 2024-12-24 00:47:03.015 DEBUG (MainThread) [myskoda.mqtt] Sending PINGREQ

The pinging goes on for a bit. Then this is send 124 times in approx 100ms:
2024-12-24 00:47:26.409 DEBUG (MainThread) [myskoda.mqtt] Received PUBLISH (d0, q0, r0, m0), '***/***/operation-request/vehicle-wakeup/wakeup', ... (153 bytes)

The response is about 250 times this:
2024-12-24 00:47:26.540 DEBUG (MainThread) [myskoda.mqtt] An operation 'wakeup' is now in progress. Trace id: *** 2024-12-24 00:47:26.540 DEBUG (MainThread) [myskoda.mqtt] Message (operation-request) received for *** on topic vehicle-wakeup/wakeup: b'{"version":1,"operation":"wakeup","status":"IN_PROGRESS","traceId":"***","requestId":"***"}'

With sometimes this in between:
2024-12-24 00:47:26.560 DEBUG (MainThread) [custom_components.myskoda.coordinator] Manually updated myskoda data

Eventually it comes to:
2024-12-24 00:47:26.663 DEBUG (MainThread) [myskoda.mqtt] Received PINGRESP 2024-12-24 00:47:26.676 DEBUG (MainThread) [myskoda.myskoda] Trace: GET https://mysmob.api.connect.skoda-auto.cz/api/v1/vehicle-auto - response: 500 (54 bytes) Unknown error occurred during getting departure timers 2024-12-24 00:47:26.676 ERROR (MainThread) [myskoda.rest_api] Invalid status for GET request to /v1/vehicle-automatization/***/departure/timers: 500 Traceback (most recent call last): File "/usr/local/lib/python3.12/site-packages/myskoda/rest_api.py", line 97, in _make_request response.raise_for_status() File "/usr/local/lib/python3.12/site-packages/aiohttp/client_reqrep.py", line 1157, in raise_for_status raise ClientResponseError( aiohttp.client_exceptions.ClientResponseError: 500, message='Internal Server Error', url='https://mysmob.api.connect.skoda-auto.cz/api/v1/vehicle-automatization/***/departure/timers' 2024-12-24 00:47:26.678 DEBUG (MainThread) [custom_components.myskoda.error_handlers] Received error 500 with content Internal Server Error 2024-12-24 00:47:26.679 WARNING (MainThread) [custom_components.myskoda.error_handlers] Error requesting vehicle from MySkoda API: Internal Server Error (500), ignoring this 2024-12-24 00:47:26.679 DEBUG (MainThread) [custom_components.myskoda.coordinator] Finished fetching myskoda data in 2.671 seconds (success: False)

[flofricke]

Hi,

I also have a Citigo eIV and I have the same problem. The Citigo's hardware is older and an SMS is probably sent to the vehicle to wake it up and query the current data. Hence the rate limit, I assume.

It would be great if the end points could be configured, especially for this vehicle. Everything worked great with one of the last versions. I use the information at 15-minute intervals to stop charging at 80%.

[prvakt]

update: if is it CitigoE iV, it looks like this car is very sensitive and with very low API limit for some endpoints

I've the same issue, my car is a CitigoE iV. I've waited almost a whole day to make sure the rate limit was removed (disabled the app to make sure it didn't connect the Skoda). I just enabled it again and this is the first part of the log file. I might have overlooked something important, but there is quite some sensitive information in the logfile, therefor didn't want to upload the whole file. Please let me know if I can do some other testing / missed something important in the logfile I can add to assist with finding the solution. I'm running version 1.17.2 and tried to newly install the integration (didn't test previous versions).

2024-12-24 00:45:58.206 WARNING (MainThread) [myskoda.auth.authorization] Retrying failed request to refresh token (1/5). Retrying... 
2024-12-24 00:45:59.315 WARNING (MainThread) [myskoda.auth.authorization] Retrying failed request to refresh token (2/5). Retrying... 
2024-12-24 00:46:55.688 ERROR (MainThread) [myskoda.rest_api] Invalid status for GET request to /v2/air-conditioning/***/auxiliary-heating: 500 Traceback (most recent call last): File "/usr/local/lib/python3.12/site-packages/myskoda/rest_api.py", line 97, in _make_request response.raise_for_status() File "/usr/local/lib/python3.12/site-packages/aiohttp/client_reqrep.py", line 1157, in raise_for_status raise ClientResponseError( aiohttp.client_exceptions.ClientResponseError: 500, message='Internal Server Error', url='https://mysmob.api.connect.skoda-auto.cz/api/v2/air-conditioning/***/auxiliary-heating' 
2024-12-24 00:46:57.706 ERROR (MainThread) [myskoda.rest_api] Invalid status for GET request to /v1/vehicle-automatization/***/departure/timers: 500 Traceback (most recent call last): File "/usr/local/lib/python3.12/site-packages/myskoda/rest_api.py", line 97, in _make_request response.raise_for_status() File "/usr/local/lib/python3.12/site-packages/aiohttp/client_reqrep.py", line 1157, in raise_for_status raise ClientResponseError( aiohttp.client_exceptions.ClientResponseError: 500, message='Internal Server Error', url='https://mysmob.api.connect.skoda-auto.cz/api/v1/vehicle-automatization/***/departure/timers' 
2024-12-24 00:47:02.995 DEBUG (MainThread) [myskoda.mqtt] Sending PINGREQ 
2024-12-24 00:47:03.007 DEBUG (MainThread) [myskoda.mqtt] Sending PINGREQ 
2024-12-24 00:47:03.010 DEBUG (MainThread) [myskoda.mqtt] Received PINGRESP 
2024-12-24 00:47:03.015 DEBUG (MainThread) [myskoda.mqtt] Sending PINGREQ

The pinging goes on for a bit. Then this is send 124 times in approx 100ms:

2024-12-24 00:47:26.409 DEBUG (MainThread) [myskoda.mqtt] Received PUBLISH (d0, q0, r0, m0), '***/***/operation-request/vehicle-wakeup/wakeup', ... (153 bytes)

The response is about 250 times this:

2024-12-24 00:47:26.540 DEBUG (MainThread) [myskoda.mqtt] An operation 'wakeup' is now in progress. Trace id: *** 
2024-12-24 00:47:26.540 DEBUG (MainThread) [myskoda.mqtt] Message (operation-request) received for *** on topic vehicle-wakeup/wakeup: b'{"version":1,"operation":"wakeup","status":"IN_PROGRESS","traceId":"***","requestId":"***"}'

With sometimes this in between:

2024-12-24 00:47:26.560 DEBUG (MainThread) [custom_components.myskoda.coordinator] Manually updated myskoda data

Eventually it comes to:

2024-12-24 00:47:26.663 DEBUG (MainThread) [myskoda.mqtt] Received PINGRESP 
2024-12-24 00:47:26.676 DEBUG (MainThread) [myskoda.myskoda] Trace: GET https://mysmob.api.connect.skoda-auto.cz/api/v1/vehicle-auto - response: 500 (54 bytes) Unknown error occurred during getting departure timers 
2024-12-24 00:47:26.676 ERROR (MainThread) [myskoda.rest_api] Invalid status for GET request to /v1/vehicle-automatization/***/departure/timers: 500 Traceback (most recent call last): File "/usr/local/lib/python3.12/site-packages/myskoda/rest_api.py", line 97, in _make_request response.raise_for_status() File "/usr/local/lib/python3.12/site-packages/aiohttp/client_reqrep.py", line 1157, in raise_for_status raise ClientResponseError( aiohttp.client_exceptions.ClientResponseError: 500, message='Internal Server Error', url='https://mysmob.api.connect.skoda-auto.cz/api/v1/vehicle-automatization/***/departure/timers' 
2024-12-24 00:47:26.678 DEBUG (MainThread) [custom_components.myskoda.error_handlers] Received error 500 with content Internal Server Error 
2024-12-24 00:47:26.679 WARNING (MainThread) [custom_components.myskoda.error_handlers] Error requesting vehicle from MySkoda API: Internal Server Error (500), ignoring this 
2024-12-24 00:47:26.679 DEBUG (MainThread) [custom_components.myskoda.coordinator] Finished fetching myskoda data in 2.671 seconds (success: False)

This is very strange and it really seems MySkoda api is trying to WakeUp your car because our integration is just polling data from MySkoda API, not from the car. Only place where wake-up is called is from MySkoda mobile app when you start it (and when wakeup is enabled in settings), and even that will happen max 3x per day

From logs I have noticed you car is requesting auxiliary-heating data even your car probably doesn't have this capability, so I will have a look why its requested, but don't this that's causing this problem

[prvakt]

fyi looks like MySkoda api is having some issues today

[SamA699]

I also have a Citigo eIV with the same error result in homeassistant.
I waited 24 hours ... still the same .... the Skoda-App shows "Nicht verfügbar", so it may be a skoda-server problem!?

[thomasgodon]

I also have this since a few hours, but the my skoda app is also not working, seems like the api is down/malfunctioning in general atm :)

[prvakt]

@Dedier: would it be possible to generate diagnostics report from your car when MySkoda is back online? I'm just wondering why auxiliary-heating data was requested for your car because I'm guessing your car doesn't have this capability

[zipposi]

I also have Citygo IV

[zipposi]

Waiting 2 days, still is a problem.. The application (also closed for 2 days) still works OK, just the integration doesn't work.

Please advise.