-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Skoda Karoq - Too Many Requests after failing to read 'warning-lights' #468
Comments
Thanks for your logs! From the logs, I can see something is happening with either the car itself, or the communication with MySkoda. We are receiving an ERROR pushmessage (via MQTT), which triggers a full update at the moment, as we try to find out what the status of the car is after receiving this generic error. I'll have a look at this, and see why this situation occurs. |
Would you be able to upload your Diagnostics from HomeAssistant? |
fyi, the diagnostics incorrectly contain the vehicle VIN in the "departure_info" endpoint data;
|
@prvakt I have seen two capabilities in these diagnostics that might be a trigger for us to change the way we approach the vehicle-health data: {
"id": "VEHICLE_HEALTH_WARNINGS_WITH_WAKE_UP",
"statuses": []
},
{
"id": "AUXILIARY_HEATING_BASIC",
"statuses": []
} Let's see if we see anything similar in CitigoE |
...
Looking at how to solve this now. If you remove the vehicle-health from capabilities polled, like you said, do you have any sensors unavailable that you would expect available? |
I have not identified any missing sensors that i would expect to exist. |
After starting integration (version 1.16.0) with Skoda Karoq (MY2020) as the target car, it fails after a short period of time due to 'Too Many Requests' (HTTP status 429).
This seems to be caused by repeated requests towards /v1/vehicle-health-report/warning-lights/vinremoved - seemingly when this request fails it is retried repeatedly with very little delay between attempts (see logs below), despite what the configuration states for update interval (60 minutes). When this situation happens the official MySkoda app soon starts failing (either returning an 'Unavailable' entirely, or stating that battery protection is enabled when trying to use auxilliary heater).
I have not figured out what is the initial error (before going into the loop of Too Many Requests -responses), there are some log entries like
and
in the logs before the warning-lights errors start appearing; likely related?
If manually changing 'coordinator.py' to load partial vehicle data (see below, not sure if I have all the CapabilityIds I need, but importantly omitting the warning-lights..), the integration seems to work correctly.
If needed I can try to get debug logs at some point.
(Related issue: #212)
The text was updated successfully, but these errors were encountered: