Might be worth telling us what you have done so far in case someone has other ideas.
You are right ! I have documented some of my tries
here and
here.
To summarize:
- I have dealt with the usual culprits (turned off Sentry, Cabin Overheat Protection, Summon Standby, turning off the car alarm completely, unplugged all USB devices…)
- I have done all kind of reboots (soft and hard/power off)
- I have turned off mobile access and revoked all the API keys by changing the password (with some limited success). The car seem to be losing less range and sleeping “differently” based on my short observations.
- Turned off Wifi (I do have LTE reception where my car is parked, i.e., in my garage and outside at work).
-Made sure no fobs are in range to somehow trigger the car (also tried turning off walk-on-unlock for good measure)
-I used the bug in dynotest to access those additional screen, and indeed the MCU reported never having slept more than 1 hour in one of the menus.
I have also reenabled TeslaFi (and only that) today and started fiddling around with the sleep settings (mostly increased the “Polling delay after waking up” value to 3). The car now reports longer bouts of sleep (up to 3 hours), but since the option “offline shown as sleeping” is turned on it seems to be mostly placebo (confirmed by the raw API calls which show the car as offline and not sleeping). Using Teslamate instead exhibits the 59 minutes offline/15 minutes online patterns shown previously on this thread by others, and has done so since the day I got my MCU update.
I am in contact with Tesla support, but their only advice so far was to turn off mobile access and use no third party apps at all (which as I reported got rid of the excessive vampire drain); which I don’t really consider a solution.. merely a workaround. Something tells me there is something else at play here, it can’t be a coincidence that my car was sleeping normally for 3+ year and that it suddenly stopped the day I got the MCU2/AP3 upgrade. (For reference, coming from MCU1/AP2)