I would like to provide a German translation of the site, provided that is the interest of the developer. If there is a translation file I can edit and send back I'll gladly help you out.

It would be really interesting if we could get battery temperature. Is this available through API, or have Tesla not exposed this? An important metric I think so pretty sure they are capturing it.

Hi, 

Just in the middle of my trial of TeslaFi, and have been comparing it against Teslastics. 

During a drive yesterday, I noticed that TeslaFi had missed some data which Teslastics captured. 

It seems like Teslastics is actually more accurate at capturing what really happened in a drive. I've attached two screenshots showing a drive I did yesterday afternoon. In that drive, there are two bursts of acceleration as I entered a short stretch of dual carriageway, then turned around at the bottom and returned in the other direction. Teslastics captures this accurately, whereas TeslaFi is completely missing part of the run.

The outward run is at 17:40:30 and the return is at 17:42:00. 

From what I can see, Teslastics appears to be polling the API three times a minute during a drive, compared to just once a minute for TeslaFi. 

I've seen mention of fast polling in TeslaFi in another thread, but I can't seem to find anywhere to switch it on. 

Has this feature been added now? 

Thanks,

Andy.

This request is an extension of the feature request to add support for peak/off-peak pricing when charging. 

In the UK, my current provider charges 14.29 pence per kW from 0430-0000 and then 5 pence per kW from 0000-0430. 

Right now, I'm deliberately limiting my charging to the off-peak hours to ensure that my costings in TeslaFi remain accurate. 

However, there was a time when I first started using TeslaFi where my all day rate was 15.29 pence per kW. When I updated the price in settings, all of the charge records at this higher price were modified too, so I've lost accuracy in my costings. 

It would be great if it was possible to manually edit the per kW cost for each charging session to account for this situation. 

In addition, supercharging in the UK appears not to follow the same structure as elsewhere. TeslaFi allows for multiple supercharger rates, but only for 60kW or less, or above 60kW. This pricing structure is not used in the UK. Right now, we have a typical rate of 24 pence per kW (which covers most superchargers), but some are now priced at 25 pence per kW and those in very high traffic areas are charged at 26 pence per kW. These prices do not depend on the charge rate, but on location. 

In order to ensure that supercharger costs are also tracked accurately, it would be great if we could have per location pricing values, or the ability to manually edit a supercharger session cost to reflect pricing that is higher than the standard. 

Similar to my previous ticket, I've now got several drives not getting identified at all, yet the raw feed shows the car logged at speeds and changing locations. 

Today, 01/08/2019 08:10:12 I started driving to work after having the car parked/offline since yesterday.

02/07/2019 17:52:30 I drove from a friend to my home, parked and then left for work the following morning - this is all logged as one continuous drive, yet teslafi logged this line later that day (guess it was sleeping while we drove home..)

02/07/2019 22:43:25 online None 0 61 110560.538 Charging 287.06 26.4 1682 0 853 0 0 103.8848 Driving->Idling @ Hjemme

could an option to automatically end drives when found home be added? or as suggested, autoend drives that've had the car offline for x hours?

I like the calendar view where you're able to get a summary of a particular month.  It would also be informative to be able to select between 2 dates. A customized report/view would allow comparative analysis over several dates that are not bound to a particular month.  So for instance you want to view a summary for a roadtrip/vacation lasting several days or investigate a particular cold spell over several days and how it impacted your efficiencies, etc.

I've seen a few comments in other forums that TeslaFi does not display the correct Vehicle Option Codes for the Model 3. This would not make it possible to verify autopilot hardware version. My code string is below, does anyone else see the same?

AD15,MDL3,PBSB,RENA,BT37,ID3W,RF3G,S3PB,DRLH,DV2W,W39B,APF0,COUS,BC3B,CH07,PC30,FC3P,FG31,GLFR,HL31,HM31,IL31,LTPB,MR31,FM3B,RS3H,SA3P,STCP,SC04,SU3C,T3CA,TW00,TM00,UT3P,WR00,AU3P,APH3,AF00,ZCST,MI00,CDM0

I have sentry mode set to auto-enable at all untagged locations as well as at a tagged location where I charge. When I park and start charging at the tagged location, I get the notification that sentry mode will be enabled in 5 minutes but it is not enabled and no second notification is sent.

If charging is subsequently interrupted (charging station breaker tripped) sentry mode is enabled.

Sentry mode auto-enables correctly at this location when not charging.

It is possible to enable sentry through live controls while charging.

I haven't tested whether sentry auto-enables at untagged locations while charging.

Maybe this is intended behavior (why?) but I haven't seen that documented anywhere.