markb1
Active Member
Wait, I think I figured it out. There's a *third* ID in that list response called id_s which does work.
id_s is just a string representation of id. Do you see something different?
You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
Wait, I think I figured it out. There's a *third* ID in that list response called id_s which does work.
My id, id_s, and vehicle_id are all different.
Interestingly, id_s = str(id + 1)
Came here to see if anybody else is having a "Error parsing response to oauth token request Error: login failed" with the teslacmd scripts. Been working for the last year and suddenly stopped working at 2:45pm (central) August 29th.
View attachment 335591
Anybody else?
My id, id_s, and vehicle_id are all different.
Interestingly, id_s = str(id + 1)
Hi foks,
I am a owner from Austria and I used the API with php for many months without a problem now. Since a while I do not get any response back but the text "our servers are waiting for a supercharger spot.."
I dug through the forum and found only the possible solution by adding "headers". But unfortunately I am no programmer and only used the standard php codes shown on Apiary. I don't know who to do this. Can someone please tell or explain what I have to change to make this working for me again?
Greetings
Gert
No pressure!As always looking forward to the post from @SG57 with your findings of the new v9 firmware API endpoints. No pressure!
Unfortunately no. My work around so far is to cache every single streaming token received then attempt to use each as needed, pruning ones that are invalid from the cache and refreshing to get the latest tokens as a last resort. This actually works quite well reducing errors dramatically.I've noticed this, too. Did you ever find any solution? What does that app do in this situation?
This is a bit off topic but does anyone know the format of the message the Tesla Mobile app receives from Google Maps via the Share feature?
Staring at the official app's Android source, they use the common Map intent filter with the "geo" URI scheme.This is a bit off topic but does anyone know the format of the message the Tesla Mobile app receives from Google Maps via the Share feature?