Stopping charge
https://github.com/chrisstaite/ZEServices/blob/6f54be2e93af184a0883c5ffc8c3f2dcd26eaa75/zecommon/src/main/java/com/yourdreamnet/zecommon/api/Vehicle.kt#L84
Apparently it is impossible to manually stop charging after starting it manually, both with action "STOP" or "CANCEL", but I have been suggested to switch charging mode from "always" to "scheduled" to have same effect, although I didn't test it yet. Possibly this would result in "successfull" charges? As of now all my charges have an "error" as final status:
{
"chargeStartDate": "2022-03-21T23:35:12Z",
"chargeEndDate": "2022-03-21T06:32:50Z",
"chargeDuration": -61342,
"chargeEndBatteryLevel": 71,
"chargeEndStatus": "error"
},
{
"chargeStartDate": "2022-03-22T19:43:12Z",
"chargeEndDate": "2022-03-22T20:58:58Z",
"chargeDuration": 4546,
"chargeStartBatteryLevel": 50,
"chargeEndBatteryLevel": 54,
"chargeEndStatus": "ok"
},
{
"chargeStartDate": "2022-03-23T01:00:32Z",
"chargeEndDate": "2022-03-23T05:46:17Z",
"chargeDuration": 17145,
"chargeEndBatteryLevel": 51,
"chargeEndStatus": "error"
}
In my case, even START does not work. Can you confirm still working currently for you?
Function startCharge (/actions/charging-start) gives the error Unexpected response code 403
Bad response to kamereon request: {"type":"FUNCTIONAL","messages":[{"code":"err.func.403","message":"{"errors":[{"status":"403","code":"security.access","detail":"Access is denied for this resource"}]}"}],"errors":[{"errorCode":"err.func.403","errorMessage":"{"errors":[{"status":"403","code":"security.access","detail":"Access is denied for this resource"}]}"}],"error_reference":"FUNCTIONAL"}
com.android.volley.AuthFailureError
http request is https://api-wired-prod-1-euw1.wrd-aws.com/commerce/v1/accounts/xxxx/kamereon/kca/car-adapter/v1/cars/xxxx/actions/charging-start?country=GB
The other functions works fine, reading status and preconditioning start/stop (/actions/hvac-start).
Any ideea?
stopping charge works fine by sending request to change charge status from "always" to "scheduled". Then you can turn it back to "always".
Fixed for me, it is working now, I think it was an issue with the server.
Thanks!