Vampire loss sanity check

With the weather getting warmer, I'm back at the point where I can typically get in the 270ish wh/mi range for my ~67.5 mile round trip commute. That's typically the energy usage at which my rated miles on the dash just about matches the actual miles traveled as ticked off on the odometer

Today I pulled in to the driveway having averaged 272wh/mi for the day. Yet despite starting the day with 172 rated miles, and only travelling 67.4 miles, I ended up with 94 left. So I lost about 12 miles of range, despite my energy usage being at the "rated" level.

It appears that the range is vampire loss when sitting. This is verified by the Trips tab in Visible Tesla: when I parked this morning I had 136 miles of range left... when I jumped back in ~8 hours later I had 124. That's a 12 miles in 8 hours... or 1.5 miles an hour.

I have the Display energy savings set to on with "Always Connected" checked. I'm at firmware 6.2(101.36.2). This feels like a bit much for vampire loss to me.

So as a sanity check with recent firmware versions... what kind of vampire losses are folks seeing?

Back when the power savings screen was initially introduced with the "Always Connected" option, I seem to recall my vampire loss for a day being more along the lines of 4-6 miles a day.... I feel like it's crept up with the last few FW releases...

So... I found the culprit: I had to go thru a few iterations of Visible Tesla when I opted to try the new "0.50 series" versions. In that process I had not realized the new version had not preserved the "Allow Sleeping" option I had previously set.[1]

As soon as I re-enabled that, my vampire loss is now back down to the previous levels I had seen: I lost 3 miles in the same ~8 hour period yesterday, as opposed to 12 miles of range loss. This is with the car's power saving enabled and "Always Connected" checked.

For those of you above who suggested that you needed to unchecked "Always Connected" to avoid double-digit vampire losses in the space of a workday, I knew there was something wrong with that, as my car had performed much better than that after the new power-savings modes were introduced.

You may want to check if you have something else keeping your car awake (such as hitting the remote access API, etc...)


[1] Although in retrospect, the remote access via phone app was awfully snappy, so I should have suspected something was up...

FlasherZ said:

I use TeslaMS, which polls the remote access API occasionally. I wasn't aware that VT didn't.

Click to expand...

VT's , "Allow Sleeping" mode will check to see if the car is awake, and if so gather stats. If not it will avoid waking it up.

FlasherZ said:

TeslaMS has it as well, but if "always connected" is checked, it isn't asleep and therefore gets polled every minute, which drives vampire loss.

Click to expand...

Hmmm... if the car is set to enable power saving, then it appears to power down a number of systems. Checking "Always Connected" enables a subset of the systems necessary to respond to remote API calls more quickly (it still takes a bit to wake up the rest of the systems). But my car is definitely not fully awake with that combo set: the phone takes 15-20 seconds to get a response rather than 5, the car has to wake screens when I get in, VT has to wake it up to get charge state, etc... I also get significantly less vampire loss, as noted above.

If "Always Connected" isn't checked, these activities take quite a bit longer...

VT is able to discern this and poll the car and determine if it is awake, without waking it up if it is not. Perhaps TeslaMS can't do this?