climatisationTimers error

[Mats1717]

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

Add your logs here.

This error originated from a custom integration.

Logger: weconnect
Source: custom_components/volkswagen_we_connect_id/__init__.py:179
Integration: Volkswagen We Connect ID
First occurred: 07:31:05 (72 occurrences)
Last logged: 07:31:13

/vehicles/WVWZZZE19RP003986/domains/chargingProfiles/chargingProfilesStatus: Unknown attribute nextChargingTimer with value {'id': 0, 'targetSOCreachable': 'invalid'}
/vehicles/WVWZZZE19RP003986/domains/climatisationTimers/climatisationTimersStatus/timers/1/recurringTimer: Unknown attribute targetTime with value 04:55
/vehicles/WVWZZZE19RP003986/domains/climatisationTimers/climatisationTimersStatus/timers/1/recurringTimer: Unknown attribute repetitionDays with value ['monday', 'tuesday', 'wednesday', 'thursday', 'friday']
/vehicles/WVWZZZE19RP003986/domains/climatisationTimers/climatisationTimersStatus/timers/2/recurringTimer: Unknown attribute targetTime with value 04:55
/vehicles/WVWZZZE19RP003986/domains/climatisationTimers/climatisationTimersStatus/timers/2/recurringTimer: Unknown attribute repetitionDays with value ['wednesday']

[MaximumFish]

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:

2023-12-22 22:58:20.577 WARNING (SyncWorker_0) [weconnect] An unsupported status: 1018 was provided, please report this as a bug
2023-12-22 22:58:20.941 WARNING (SyncWorker_0) [weconnect] /vehicles/WVGZZZE2ZMP015099/domains/automation/climatisationTimer/timers/1/singleTimer: Unknown attribute targetDateTime with value 2022-01-15T00:00:00Z
2023-12-22 22:58:20.941 WARNING (SyncWorker_0) [weconnect] /vehicles/WVGZZZE2ZMP015099/domains/automation/climatisationTimer/timers/2/singleTimer: Unknown attribute targetDateTime with value 2000-01-01T00:00:00Z
2023-12-22 22:58:20.942 WARNING (SyncWorker_0) [weconnect] /vehicles/WVGZZZE2ZMP015099/domains/automation/chargingProfiles: Unknown attribute nextChargingTimer with value {'id': 0, 'targetSOCreachable': 'reachable'}
2023-12-22 22:58:20.943 WARNING (SyncWorker_0) [weconnect] An unsupported status: 1018 was provided, please report this as a bug
2023-12-22 22:58:20.951 WARNING (SyncWorker_0) [weconnect] /vehicles/WVGZZZE2ZMP015099/domains/chargingProfiles/chargingProfilesStatus: Unknown attribute nextChargingTimer with value {'id': 0, 'targetSOCreachable': 'reachable'}
2023-12-22 22:58:20.952 WARNING (SyncWorker_0) [weconnect] /vehicles/WVGZZZE2ZMP015099/domains/climatisationTimers/climatisationTimersStatus/timers/1/singleTimer: Unknown attribute targetDateTime with value 2022-01-15T00:00:00Z
2023-12-22 22:58:20.952 WARNING (SyncWorker_0) [weconnect] /vehicles/WVGZZZE2ZMP015099/domains/climatisationTimers/climatisationTimersStatus/timers/2/singleTimer: Unknown attribute targetDateTime with value 2000-01-01T00:00:00Z

My logs are growing at a tremendous pace!

[henel321]

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.)

[henel321]

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.
tillsteinbach/WeConnect-python#162

[mitch-dc]

I cant do much about this at the moment. The error comes from the underlaying lib :(

[jthun]

There's a new release of the library now. Looks like Till's fixed some of this.