A nice idea for Model X owners will be to have a different Drive efficiency calculations as now are the same for Model S and Model X (based on 20kWh/100km).

As you know Model X is larger and weights more than Model S and Typical range should be calculated different and maybe based in something between 22kWh/100km and 23kWh/100km

It would be really useful to be able to download the drives for a specified period (default: yesterday?) as excel(csv); The information on the daily listing pretty much matches what I would need - starting point, end point, start odometer, end odometer, start time end time.

This would really make the task of keeping a logbook of drives much less aggravating.

Download drive list to excel, add business/privte indicator and possibly a comment and it's done.

Steps to reproduce:

1. Start charging the car with max charge level at, for example, 60%.
2. Open TeslaFi and note the "Estimated Completion" time in the current charge record.
3. Close TeslaFi
4. Change the max charge level (e.g. from 60% to 90%) before charging is complete.
5. Open TeslaFi and look at the "Estimated Completion" tims in the current charge record.

Result:

1. "Estimated Completion" time does not change as a result of changing the Max Charge level.

Expected Result:

1. "Estimated Completion" time should be updated when max charge time changes.

Suggestion: instead of putting the "estimated completion" DURATION in the charge record, why not put the estimated time of day at which the charge will be complete? This can always be calculated by adding the API datum time_to_full_charge to the current time of day. If this is updated whenever the charge record is displayed, then isn't that more useful?

In looking at the raw data feed, many items are listed as 'None' when the connection state is online. Why would things like inside/outside temp and shift state be none? Shouldn't we be able to see the status as parked and the temps? There may be others, but have not looked through all the columns.

- In charge totals page (https://www.teslafi.com/charges.php?chargePercent=80) you show batery range and estimated range but I think that there is an error or you are not showing Typical Km. My Model X has 396Km typical at 100% and the data you show there it's much larger.

On a whim, I decided to add up the times for sleep, idle, drive, charge, and Supercharge about a week ago. In almost every case, they add up to anywhere from 4 to 15 minutes shy of a full 24 hours.

Shouldn't the data equal 24 hours? Not sure if the missing time is represented by issues with get a response from the API.

Some data:

* Car was in service mode on 2/21 presumably for the amount of time missing from 24 hours.

Until the cookies can be extended, is it possible to add a link to the sleep alert email to allow the user to start polling again without having to sign in again? It could be randomized and encoded in order to avoid any potential security issues.

The outlets at work seem to be very fickle and either reduce the charging from 16a to 12a randomly or will lose power entirely (especially if someone plugs into the next plug apparently tripped the breaker, as had happened today).

Looking at Charge 118 from today, the charge started at 12:04 p.m. then was interrupted at 12:48 p.m. The UMC was not lit green and the IC was showing zeros for volts, amps and mph so the power basically stopped at this particular outlet (and all the ones nearby).

You may need to determine how to handle a scenario when someone had been charging then the power was stopped abruptly. Looking at the charge table data, it looks like 40a was being requested but it was either returning 0 or none values. The charging_state field also seems to go from Charging to NoPower so perhaps the site needs to not record the car as charging but idle? I don't know...

Originally reported on 8/22/16.

I recently had a drive that started at 11:50 pm which ended past midnight. It seems like the little map in the right column cuts off right at midnight while the remainder of the drive shows on the map for the next day.

To keep the reporting consistent, it seems like the site should either A) have the map match the drive history for the particular day, OR B) split drive records at midnight (like how you've recently done for sleep and idle).

Option B was something we spoke about months ago and I recall you thinking about gathering opinions once you open up access to more users. If the consensus is to have each day stop at midnight, you can probably just keep the same record number for any record types that go past midnight but just have the UI know to split it right at 11:59/midnight.