Thanks everyone for chipping in and trying to solve this with me !
Are you simultaneously running two remote apps?
I was, but since trying to diagnostic this a little more precisely I have been using only one at once (and sometimes none, as explained in my previous posts); it was actually one of my first suspicions when I first tried to diagnostic/resolve this about 6 weeks ago. For reference, I have been using TeslaMate with the Streaming API exclusively.
Have you upgraded the Tesla app?
Yes, I have been using the latest iOS app on my phone (exclusively). I have no Tesla widgets what-so-ever and also tried deleting and re-installing the app already.
You will also hear roughly when it goes to sleep because you'll hear the HV battery disengagement "clonk", and the whirring will stop.
The whirring does stop, and I can hear the electrical clicks and clonks (also when waking up the car afterwards). This does however not correlate with less range loss in my case.
The first thing you should do in this situation is change your password.
I have done this a few times already with mitigated results (see previous posts).
but don't mention third party apps at all.
I'd also say that TM graph would be enough to raise a case with Tesla
That's what I already did (screenshots of states in TM and TeslaFi, both of different diagnostic time-frames). But their answer (and Durzel pointed out) has been to blame this on third party apps. What speaks against this is the fact that I have let the car sit for about 7-8 days with no apps in use (token revoked, Tesla app not even logged in) and
still got abnormal range loss and the MCU reporting never having slept 3941 seconds (through the dynotest bug a few fw versions ago). That's an hour and 5 minutes and correlates with what I am seeing on TM and TeslaFi.
My hot take at the moment: my car never sleeps, it just goes offline. Sometimes actually going offline (i.e., LTE taking 5 minutes to re-connect when “waking up” in areas with plenty of 3G74G signal; this specific issue I am currently still investigating with Tesla) instead of sleeping. My far-out theory is that something went bad when they imported the config during the MCU upgrade, which prevents the car from actually sleeping (funnily enough, the diag mode was reporting my “Car computer” as being “mcu_transition”. Maybe some random energy saving mode is still taken into account, but now shown on the UI...?).
My next steps are the following:
1) Testing the 12v battery (although I now see on my pictures that it was at 13.92v, which is a little too high… maybe it was being fed by the car battery itself?)
2) Doing another test with "Mobile Access" turned on but no logging/apps at all over 24+ hours and see:
2.1) if the vampire drain gets better
2.2) if the "LTE" disconnect still happens when waking up the car.
3) Trying with TeslaMate exclusively (no Tesla app either) to see if the car goes asleep at some point
4) The one I am trying to avoid: factory reset the car.
If none of those fix it; I'll do my best to try to escalate this with Tesla. I have read in the TeslaFi support forums somewhere that someone was having a similar issue, and it turned out to be a faulty electrical seat motor (or was it a sensor?) what was constantly drawing power and keeping the car awake; but unfortunately I don't have the necessary tools or time to diagnostic something like that…
I will keep you updated with those findings.