EU - shedule charge and climatisation for non ccu_ccs2 vehicles

[Bob33700]

Hello,
I'm in Europe, owning a KIA (doesn't support ccu ccs2 protocol)

I'm trying to shedule charge and climatisation... without success.
Here are details :
my code is :

vm.check_and_refresh_token()
id: Vehicle = list(vm.vehicles)[0]
vm.schedule_charging_and_climate(id, ScheduleChargingClimateRequestOptions())

The process fails in _get_control_token() witch generates a request with authenticated headers and data: {'deviceId': 'e72b83f7-2bdb-47d4-90ba-826dad28b3fa', 'pin': ''}... and brings response : {'errId': 'f3610016-a585-489d-b4f0-853912b6cd29', 'errCode': '4002', 'errMsg': 'Invalid parameters'}

Some other requests are OK (get status, lock/unlock, climate,... ) this one (schedule...) is the first that I use witch uses 'control_token' to build 'control_headers' all others simply use 'authenticated_headers'

I can't figure what is the problem
Can anyone help please ?

[Bob33700]

OK, I found this: the current implementation of schedule_charging_and_climate in KiaUvoApiEU.py is for ccu_ccs2_protocol only.
(url = SPA_API_URL_V2... + control_headers)
My vehichule is older than this and doesn't support this protocol.
I tried changing the url to:

url = self.SPA_API_URL + "vehicles/" + vehicle.id
        url = url + "/ccs2"
        url = url + "/reservation/chargehvac"

with authenticated_header only like for all others requests for non ccu_ccs2 compliants vehicules
I receive a SUCCESS response:

headers: {'Content-Type': 'application/json; charset=utf-8', 'Date': 'Sun, 16 Feb 2025 17:01:13 GMT', 'Etag': 'W/"4f-4puzKZFGfFyC5CmEAi09Yjc18pE"', 'X-Powered-By': 'Express', 'X-Ratelimit-Limit': '-1', 'X-Ratelimit-Remaining': '0', 'X-Ratelimit-Reset': '0', 'Content-Length': '79', 'Connection': 'close'} 
cookies: {} 
content : {"retCode":"S","resCode":"0000","msgId":"a0a01300-ec87-11ef-a5cf-2f5bcf64b7ec"}

but the check_action_status fails to get a success response before the deviceId was invalidated... so it iterates with 'result': None and then fails with 'resCode': '4002', 'resMsg': 'Invalid request body - Invalid deviceId. '

The KIA Connect application on my phone indicates that the request was a SUCCESS : all informations are OK whith my request

Abstract: we can implement schedule_charging_and_climate for vehicules that don't support ccu_ccs2 protocol too.
The only problem remaining is with deviceId witch invalidation breaks check_action_status