Region: Australia (5) · Brand: Hyundai (2)
Vehicle: Palisade (model reported "PALISADE 19/22"), ICE (petrol)
Detected: vehicle.ccu_ccs2_protocol_support = 0
Versions: kia_uvo v3.6.0 · hyundai_kia_connect_api 4.23.1
WORKING: lock, unlock, force_update, all status/location entities.
FAILING: start_climate / stop_climate — fails on the legacy branch AND when
ccu_ccs2_protocol_support is forced to 2 (CCS2). Identical error both ways.
Exact request the library sends (legacy branch):
POST https://au-apigw.ccs.hyundai.com.au:8080/api/v1/spa/vehicles//control/temperature
body: {"action":"start","hvacType":0,"options":{"defrost":false,"heating1":0,"igniOnDuration":5},"tempCode":"08H","unit":"C"}
Exact response:
HTTP 400
{"retCode":"F","resCode":"4005","resMsg":"Unsupported control request - Vehicle is not supported (vehicleId: )"}
Key point: remote climate/start WORKS in the MyHyundai app for this vehicle, so
the vehicle & subscription support it. The app's request could not be captured
(the app uses certificate pinning). Strong hypothesis: an ICE Palisade needs a
remote engine-start endpoint (e.g. /control/engine), not the EV-style
/control/temperature the library uses for all vehicles. Happy to run any
diagnostic build to help pin down the correct AU ICE endpoint/payload.
Region: Australia (5) · Brand: Hyundai (2)
Vehicle: Palisade (model reported "PALISADE 19/22"), ICE (petrol)
Detected: vehicle.ccu_ccs2_protocol_support = 0
Versions: kia_uvo v3.6.0 · hyundai_kia_connect_api 4.23.1
WORKING: lock, unlock, force_update, all status/location entities.
FAILING: start_climate / stop_climate — fails on the legacy branch AND when
ccu_ccs2_protocol_support is forced to 2 (CCS2). Identical error both ways.
Exact request the library sends (legacy branch):
POST https://au-apigw.ccs.hyundai.com.au:8080/api/v1/spa/vehicles//control/temperature
body: {"action":"start","hvacType":0,"options":{"defrost":false,"heating1":0,"igniOnDuration":5},"tempCode":"08H","unit":"C"}
Exact response:
HTTP 400
{"retCode":"F","resCode":"4005","resMsg":"Unsupported control request - Vehicle is not supported (vehicleId: )"}
Key point: remote climate/start WORKS in the MyHyundai app for this vehicle, so
the vehicle & subscription support it. The app's request could not be captured
(the app uses certificate pinning). Strong hypothesis: an ICE Palisade needs a
remote engine-start endpoint (e.g. /control/engine), not the EV-style
/control/temperature the library uses for all vehicles. Happy to run any
diagnostic build to help pin down the correct AU ICE endpoint/payload.