-
Notifications
You must be signed in to change notification settings - Fork 52
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
climatisationTimers error #235
Comments
I'm getting a similar thing. Seemingly it's been going on for a few weeks but I only checked the logs in the last few days for something unrelated and came across hundreds (thousands?) of these:
My logs are growing at a tremendous pace! |
Getting exactly this as well but also for the charging timers - anyone found a fix/workaround? Has anyone tried setting proper timers/dates in the car but then disabling them? It seems the data in these are basically null/default values, which would be logical as I don't use these timer features myself.. (And they were really broken in the 2.3/2.4 firmware for ID-cars.) |
I tried setting timers for charging/climatization so they weren't null.. I'm still getting the same issues but with a proper timestamp in the error. 2024-01-29 20:11:00.640 WARNING (SyncWorker_4) [weconnect] /vehicles/FOOBAR/domains/climatisationTimers/climatisationTimersStatus/timers/2/singleTimer: Unknown attribute targetDateTime with value 2024-01-31T08:00:00Z Seems like VW changed the API naming, there's a bug reported on the weconnect python lib. |
I cant do much about this at the moment. The error comes from the underlaying lib :( |
There's a new release of the library now. Looks like Till's fixed some of this. |
Version of the custom_component
2.0
Installation method (hacs / manual)
HACS
Installation method of hass (venv, docker, hassio,...)
HASSIO
Configuration
Add your configuration here.
Describe the bug
ID3 car and get this errors in the log
Debug log
The text was updated successfully, but these errors were encountered: