Joined
·
27 Posts
I originally had this question in another post, but didn't want to hijack his thread. I tried (and still love) Stats, but thought I'd look into TeslaFi for its richer data set. Although this isn't rocket science, I can't get my P3D to sleep while using TeslaFi. I'll consistently loose >3% battery each night with TeslaFi, but with Stats, there's simply no loss at all. The car bounces every 24-40 minutes from sleeping to idling (see screenshot). The image is only capturing a portion of the nights usage, the rest didn't fit in the screenshot.
Someone had suggested that the combination of Stats and TeslaFi could be causing the problem as Stats polls every 30 minutes or so, and it could be waking up the car that TF had put to sleep. I logged out of Stats (the application runs locally so no server to keep pinging), so last night's data represented TF alone. I've also included a screenshot of my sleep settings. The only thing I changed was to allow "Idle Time Before Trying To Sleep" to sleep earlier at 20 minutes vs 30. I had also previously checked the "No Shift State Readings", but that didn't have any impact as well.
Anyone have any idea what can be causing this? I love the granularity of the data captured by TeslaFi, but the current drain is too great (especially while it's sitting at work with no charger hooked up) for me to justify. Hopefully it's a simple solution I'm overlooking (and yes, I've read the TF section on sleeping). Some people report the same excessive drain over Stats, while others report no drain at all. Where's the variable? Thanks all.
Someone had suggested that the combination of Stats and TeslaFi could be causing the problem as Stats polls every 30 minutes or so, and it could be waking up the car that TF had put to sleep. I logged out of Stats (the application runs locally so no server to keep pinging), so last night's data represented TF alone. I've also included a screenshot of my sleep settings. The only thing I changed was to allow "Idle Time Before Trying To Sleep" to sleep earlier at 20 minutes vs 30. I had also previously checked the "No Shift State Readings", but that didn't have any impact as well.
Anyone have any idea what can be causing this? I love the granularity of the data captured by TeslaFi, but the current drain is too great (especially while it's sitting at work with no charger hooked up) for me to justify. Hopefully it's a simple solution I'm overlooking (and yes, I've read the TF section on sleeping). Some people report the same excessive drain over Stats, while others report no drain at all. Where's the variable? Thanks all.
Attachments
-
174.4 KB Views: 311
-
107.2 KB Views: 259