Are the possible return values of the API calls documented somewhere?

[Panda88CO]

Hi
I have a need to map possible return values from a returned API parameter into integer values. E.,g. what are the possible return values that can occur for a car's charging state? Is it documented somewhere? If not it would be a great document to have :-)

Thanks

[SylvainGa]

I've asked the same question and didn't get an answer. This is what I found out and using. This is based on standard errors with a few modification for Tesla

	"400" => "Bad_Request",
	"401" => "Unauthorized",
	"402" => "Payment_Required",
	"403" => "Forbidden",
	"404" => "Not_Found",
	"405" => "Method_Not_Allowed",
	"406" => "Not_Acceptable",
	"407" => "Proxy_Authentication_Required",
	"408" => "Request_Timeout",
	"409" => "Conflict",
	"410" => "Gone",
	"411" => "Length_Required",
	"412" => "Precondition_Failed",
	"413" => "Request_Too_Large",
	"414" => "Request-URI_Too_Long",
	"415" => "Unsupported_Media_Type",
	"416" => "Range_Not_Satisfiable",
	"417" => "Expectation_Failed",
	"500" => "Internal_Server_Error",
	"501" => "Not_Implemented",
	"502" => "Bad_Gateway",
	"503" => "Service_Unavailable",
	"504" => "Gateway_Timeout",
	"505" => "HTTP_Version_Not_Supported",
	"511" => "Network_Authentication_Required",
	"540" => "Vehicle_Server_Error"

[Panda88CO]

Thanks
That helps
I was actually looking for possible return values of a given parameter returned by the API. I need to translate the returned string to a number to allow it to integrate in a different platform

E.g. from charging state:
"response": {
"battery_heater_on": false,
. . . . . .
"charger_power": 0,
"charger_voltage": 0,
"charging_state": "Complete",
"conn_charge_cable": "SAE",
"est_battery_range": 171.24,

What other values than Complete exists??

Is that documented somewhere?

[GaPhi]

Here are the values I have already seen for that field. I have the same for all other fields if someone wants to create the documentation... case "charge_state.charging_state": return ![ null, // Unavailable "Disconnected", // Disconnected "NoPower", // Connected, no power "Starting", // Connected, starting charge "Charging", // Connected, charging "Stopped", // Connected, charge stopped "Complete", // Connected, charge complete ].includes(d.after) Le mer. 30 mars 2022 à 22:33, Panda88CO ***@***.***> a écrit :

…

Thanks That helps I was actually looking for possible return values of a given parameter returned by the API. I need to translate the returned string to a number to allow it to integrate in a different platform E.g. from charging state: "response": { "battery_heater_on": false, . . . . . . "charger_power": 0, "charger_voltage": 0, *"charging_state": "Complete",* "conn_charge_cable": "SAE", "est_battery_range": 171.24, What other values than *Complete* exists?? Is that documented somewhere? — Reply to this email directly, view it on GitHub <#554 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADUNWNN6LF4VWB6OMMYQRCDVCS3AXANCNFSM5RY6FQOQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[SylvainGa]

Oh, sorry. I should have read better :) This was posted already in #207

#207

[Panda88CO]

If you can forward the values, I can take a look at documenting it

[Panda88CO]

thanks Christian Olgaard

…

________________________________ From: SylvainGa ***@***.***> Sent: Wednesday, March 30, 2022 2:38:25 PM To: timdorr/tesla-api ***@***.***> Cc: Panda88CO ***@***.***>; Author ***@***.***> Subject: Re: [timdorr/tesla-api] Are the possible return values of the API calls documented somewhere? (Discussion #554) Oh, sorry. I should have read better :) This was posted already in #207<#207> #207<#207> — Reply to this email directly, view it on GitHub<#554 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/APQ7ECUPJMVRVXMMF2BHW4TVCTCVDANCNFSM5RY6FQOQ>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[GaPhi]

Here is my NodeRed node that is in charge of detecting any change in vehicleData command response.
(It also fixes the response for some values but this is just to simplify the remaining logic of the numerous flows)

delta.zip