Does the WeConnect API support MBB platform vehicles ? about weconnect-cli HOT 3 CLOSED

When both cars are usable with the new app it is likely that it should work. But it is a bit strange that it is not working right away

from weconnect-cli.

Ok, thank you.
I also get some errors on the ID.4:

• Entity sensor.id_4_gtx_last_trip_average_electric_consumption (<class 'custom_components.volkswagen_we_connect_id.sensor.VolkswagenIDVehicleSensor'>) is using state class 'measurement' which is impossible considering device class ('energy') it is using; expected None or one of 'total_increasing', 'total'; Please update your configuration if your entity is manually configured, otherwise report it to the author of the 'volkswagen_we_connect_id' custom integration
• /vehicles/WVWxx /domains/climatisationTimers/climatisationTimersStatus/timers/2/singleTimer: Unknown attribute targetDateTime with value 2023-02-18T09:00:00Z
• /vehicles/WVWxx : Unknown attribute climatisationTimersStatus with value {'value': {'carCapturedTimestamp': '2024-02-25T10:49:46Z', 'timeInCar': '2024-02-25T11:49:45+01:00', 'timers': [{'id': 1, 'enabled': True, 'recurringTimer': {'startTime': '06:45', 'recurringOn': {'mondays': True, 'tuesdays': True, 'wednesdays': True, 'thursdays': True, 'fridays': True, 'saturdays': False, 'sundays': False}, 'targetTime': '06:45', 'repetitionDays': ['monday', 'tuesday', 'wednesday', 'thursday', 'friday']}}, {'id': 2, 'enabled': False, 'singleTimer': {'startDateTime': '2023-02-18T09:00:00Z', 'targetDateTime': '2023-02-18T09:00:00Z'}}]}} in domain departureTimers
• /vehicles/WVWxx : Unknown attribute temperatureOutsideStatus with value {'error': {'message': 'Bad Gateway', 'errorTimeStamp': '2024-02-25T17:02:08Z', 'info': 'Upstream service responded with an unexpected status. If the problem persists, please contact our support.', 'code': 4007, 'group': 2, 'retry': True}} in domain measurements
• /vehicles/WVWxx : Vehicle data for WVWxx is empty, this can happen when there are too many requests
• Trips could not be fetched for car WVWxx due to too many requests.

I presume the last few of those may be related to "too many requests", but not all of them.
I am an experienced programmer and know Python. I may be interested in contributing or doing some testing if I can fine some spare time :).
If you have any suggestions on where to start, that would be appreciated.
More specifically, there seems to be a lot of different urls used to authenticate and get data. Any info on this and how to log the raw output for analysis would be helpful.

Thanks again.
Jon

from weconnect-cli.

the first message is coming from another integration right? some of the warnings will go away after you update

from weconnect-cli.