You could do that with the old app. I used it all the time for J1772 stations.
I never noticed that before. I always unlock the port from the 17".
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.
You could do that with the old app. I used it all the time for J1772 stations.
I woke up this morning to a software update prompt. I scheduled it for 9:30am CT when I know the car won't be needed for a couple of hours. Fingers crossed that I am getting v6.0 (currently on 5.11).App installed, relogged into app, now that TM knows I have it they should send me v6.0 tonight, right?
Good. This means there aren't any iOS 8 dependencies for starting the car.
Starting the car is a Tesla API, just like starting the A/C... It shouldn't have any thing to do with iOS API. Am I missing something?!Since it has been rumored to be out with beta testers for several months I was not expecting it to need iOS8. Maybe V 7.0 will though!
The notion was that something new in iOS 8, like Touch ID, would be required to start the car. The Tesla API might have had some sort of authentication mechanism that required it.Starting the car is a Tesla API, just like starting the A/C... It shouldn't have any thing to do with iOS API. Am I missing something?!
I woke up this morning to a software update prompt. I scheduled it for 9:30am CT when I know the car won't be needed for a couple of hours. Fingers crossed that I am getting v6.0 (currently on 5.11).
Starting the car is a Tesla API, just like starting the A/C... It shouldn't have any thing to do with iOS API. Am I missing something?!
Ah, OK... I understand what you mean. I am not sure if the lower regen applied at lower speeds is intentional or a physical constraint.
I believe this already happens to a certain extent. The upper limit of the regen may be determined by your speed, but within that limit, the amount of regen I think already depends on how quickly you release the accelerator.
It might, and might not use the regular API.
Nothing prevents the app from using a different way to communicate with the car (bluetooth, nfc, or maybe even a direct wlan connection).
It depends on whether the phone needs to be physically close to the car or not to be able to start it. I can see the advantage of being able to start the car remotely - if I am on my own, and lose the fob and AND my own phone, then my wife can then start the car for me from wherever she is so I can drive home. But on the other hand, there are quite a few security implications with this that are easier to resolve if the phone needs to be close to the car to start it.
And even if it uses the regular REST-api, it might require some kind of secret sauce that only iOS can give it. Some kind of key exchange - maybe a three way handshake, involving an iOS crypto API.
This could ofcourse also be done with various Android APIs so it does not mean it have to be iOS only.
Until 6.0 is actually out there, we can't really know.
but how much programming time and effort did it take to add "Name Your Car"?
I would rather the time and programming skills it took to implement that option be put to better use and give us something worthwhile in its place (like backup guidelines).
I highly doubt the name function took any resources from the guidelines feature.
They require very, very different skill sets. something like name your car can be added by an entry level coder or intern. The guidelines, if even possible, require a highly skilled low level GPU programmer.
It is a little of like saying I wish the gardener did not waste time mowing your lawn, instead of spending time in the lab curing cancer.
I'm guessing: not much.
+1I suspect there is a lot of infrastructure work going along with this allowing control of multiple cars from the app.