The app cannot know the state of the car, e.g driving or charging, without polling (data fetch) or if you use a flow (condition or action) that fetches the state.
So if you start driving and use a flow, then the app will know right away that it’s driving.
If you use data fetch with an interval of 10 minutes for example, it will take a maximum of 10 minutes before the app sees state, and it will then fetch the state every minute.
When you are driving and the app knows that, it will also start “streaming”, where a smaller set of data will be updated with a higher frequency, e.g. speed, gps location, etc.
The previous app could detect that without waking up the car each time. The moment i started driving or charging it knows what i was doing without polling each time keeping my car awake.
I see that the old app tracked location with two different intervals (parked and driving). The tracking will fail if the car is asleep with an error ({:error=>"vehicle unavailable:"}), but will be successful of course as you start driving. You are right.
With 60 minutes, and data fetch enabled, it will check the status of the car every 60 minutes. That will wake the car up if it is asleep, and it will stay awake for 10 minutes. The 10 minute awake period is by Tesla’s design.
With the latest release (v. 1.2.4), it will also see that the car awakes, and if it start charging or driving it will continue to fetch data every minutes until it stops charging or driving.
Same here, at first I got to the point where I could give the MFA code, but now it times out before that. Haven’t linked the car yet, and did try a reinstall of the app.
