How have you been determining that? Either I'm inadvertently keeping it awake somehow, I'm not checking the right thing, or the car isn't sleeping anywhere near that fast.
Confirmed. I was once in a big traffic (dead stop due to fire on the bridge not caused by Tesla:tongue, after placing the car in "Park", the car went to sleep after around 12 minutes. Maybe my car needs more rest than yours:biggrin:14-15 minutes is what I've measured.
Interesting. Thanks for your replies. The context of my original question was related to the use of the API. When the car is asleep, it doesn't respond/act on API calls/commands. I had not realized that the car being asleep (from an API perspective) is correlated with the car being asleep from an internal "display" perspective.
In case anybody is curious why I am asking this, I am using VisibleTesla to keep the car awake so that it will act on commands issued by EVMote.
It's only a one-direction correlation. API "sleep" can only take place when the car displays are asleep. That's not exactly what we were talking about.
I think there's something going on with the car right now, because it doesn't seem to want to go to sleep (perhaps log download, etc.). I've started the logger to collect information about when it's awake vs. asleep, I'll report anything I find here.
i would assume that if the in-car display is on, then the car is awake from an API perspective. However, the car could be awake from an API perspective without the display being on.