Replies: 2 comments 2 replies
-
My current implementation :
|
Beta Was this translation helpful? Give feedback.
2 replies
-
Yes that's it.
To find arguments of any request, the easy way is just to have a look at
the log files produced by the tesla application (you have to jailbreak your
android smartphone to access the directory)
Another solution is to reverse-engineer the apk file and decompile java
code (also possible with native code)... it is more accurate to understand
the various special algorithm cases to handle.
Le sam. 13 mai 2023 à 16:27, Stefan Sturm ***@***.***> a
écrit :
… Thanks for your reply :)
I didn't know about the "let_sleep" query argument. Where do you know it
from?
So the url should look like this: "GET
https://owner-api.teslamotors.com/api/1/vehicles/{vehicle_id}/vehicle_data?let_sleep=true
"
Right?
—
Reply to this email directly, view it on GitHub
<#721 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADUNWNIJYSYCUCMETW4F6ZLXF6K6XANCNFSM6AAAAAAYAMKJJ4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What is you practice for calling the vehicle_data endpoint to always have the latest vehicle data?
Does calling this endpoint prevents the Tesla from going to sleep?
For me it looks like, when calling this endpoint every minute the Tesla is going to sleep some minutes later...
So, how do you handle this?
Beta Was this translation helpful? Give feedback.
All reactions