It would be handy to have the ability to search for drives from 1 location to another location.  For instance, to easily get a report of all my Home to Work drives, or Work to Home, or...

I'd like to export all available data for my car, even if it exports as separate CSV files all zipped together or something like that. Currently, you must export one month at a time. I've now had my car for over 2 years, so this is a lot of individual clicking and exporting to get the full history.

Would it be possible to add the following commands to TeslaFi which could then be triggered via the TeslaFi API?

* Actuate Frunk

* Actuate Trunk

* Turn On Climate and allow  to set cabin temperature to a specific value

* Turn On A Specific Seat Heater w/ ability to set heat level

* Open & Close Windows

* Trigger HomeLink

Thanks to Tesla's recent MFA-related API changes I would much prefer to have my iOS Shortcuts point directly at TeslaFi since you are already keeping track of vehicle wake state and have the appropriate wake logic built into your API.

Thanks,

Dan

My son got his learner's permit and I need to log him driving for 40 hours. Does Teslafi have access to what driver's profile the car was set to when driving? If so, it would nice if it auto-tagged the drives with the profile name.

Also, I have been manually tagging his drives with his name, but when I search for drives with that tag, it just shows all of the drives. Does tag search work correctly?

Create API endpoints to access Drives and Charges instead of having to export to CSV.

As you know, sometimes a drive or a charge is missed due to comm failure with the car (and maybe other reasons).  It seems to be it would be possible to generate drive or charge records that approximate what was missed.

For example, my car was at the Service center. For the period of time in question, there was a LONG idle, but here is how it looked. 

While perfect accuracy is impossible, one could infer from this that at least 9.15kWh were added in a 'hidden' charge.  Breaking it out as a charge would be much more accurate.

I have also had drives go missing.  These can be detected by the end of a drive being at a different location than the beginning of the next drive.

Obviously these would be approximations, and would be missing much of the detail of a normal drive or charge, but they would help both in providing better information about what went on, and in avoiding people thinking that TeslaFi is not working correctly.

I was using Visible Tesla on my computer and my favorite feature was to be able to control the SOC on a schedule. Here in the North East the cold weather greatly affects the regen breaking, which is about my favorite feature of the car! Anyway, with the scheduled SOC, I would set it to charge a extra 5% starting at 5am, that way the battery would warm up by 5:30 when I left and my regen breaking was much better for my ride to work.

So, it looks like teslafi had no control feature... :( So, my idea would be to add scheduling to it if it is added.

I don‘t need an app necessarily, but a more responsive web design, would be tremendously helpfull. 
A few tweaks of html and css are far less effort than an App and good responsive Web design should be the standard these days. 
I think you could improve the user experience on mobile devices dramaticly with just a few hours/days of work. 

If I want to look at the one-month calendar for 6 months ago (e.g. to look up exactly when I went on some particular trip), I have to open the calendar for the current month and then hit "Previous Month" 6 times and wait for the calendar to load each time. It would be nice to be able to select a year and month in the calendar view directly.

Is it possible to import data from another service such as teslascope?