I have to charge through the Blink charging network frequently at a given location.  This has a fixed rate of $.02/30 seconds of charging.  Is there a way to use this rate automatically in calculating the charging cost for that geo location?

I know James did a good job explaining sleep settings here

...but until I wrote down the following, I just could not wrap my head around it.  So sharing in case this helps others to understand how this works

1. While in Idle
2. Will poll vehicle 1/min (the Polling Time While Idle value)
3. …for this period of time: Idle Time Before Trying To Sleep (30 m)
4. After this time has expired, will NOT poll vehicle for period of time: Time To Try Sleeping (15 m)
5. … in an attempt to let the car sleep
6. If detect car is asleep, then will not poll, but will continue to check if it is asleep
7. If detect car did not fall asleep, Go back to step 1
8. If car awakes from sleep, go back to step 1

The above is true when NOT in Nighttime TeslaFi Sleep Mode or Deep Sleep Mode

It is not clear where wind speed data is coming from but since there is no associated direction it is completely not useful. It seems obvious that wind is a factor, but the direction of the wind is more important than the velocity. Please try to add the direction to the data collected so users can benefit from the data, rather than have wasted data show up in our logs.

Add a button on the main page to stop polling and try to put the vehicle into sleep mode.

This is particularly useful when going to work. After parking, I know I'm not going anywhere else, so I'd like to put the car to sleep right away instead of waiting for the idle period. 

Update of new navigation dat file is currently an issue and it is for a lot of drvier unclear when the update will be done.

Will be really helpful to see if new version is published by Tesla and how a new version will be rolled out

At home my car is in underground parking - 3 levels down - so it has no network or GPS connection. TeslaFi does not detect that I arrived at a destination - it just keeps the drive going to whatever place I go the next day. The only way to fix this today is to manually edit every trip.

I would suggest a feature that a drive automatically ends (at the last known location) when the connection is lost after a configurable time of minutes. 

Now that you have added the cost savings comparison vs gas, which is an awesome addition. When vehicle is idle, sleeping, etc., I would like to see range loss as a cost or reduction in savings compared to gas (as there is no range loss on ICE vehicles when engine is off)

We use a Zappi Charger at home and set it for using Solar Power in the day however the annoying thing is if a cloud comes over or the house draws some extra power so there isn't enough surplus to charge the car it will automatically pause/stop the charge then continue once there is enough surplus solar energy.. 

Issue with TeslaFi is that each of the pause then start again charges get logged as a new charge session.. Would it be simple enough to add in an option that when the vehicle is plugged in and the charging stops for say anything less then 15mins then starts again that it just carry's on the logging as the same charging session so it doesn't show up as a new one.. On a dodgy day we can end up with 30 odd charges. This could even be added just as a logged location like "Home" and set it just for during the day so if you charger behaves like this in the middle of the night it would still log it correctly. 

Even if we get an option to add charging sessions together that would help.. I'd rather those 30 start stop chargers show up as one. 

Also I love the idea of the different tariffs (Economy 7 for example).

Many Thanks

Simon

It would be very nice if the calendar view could be exported via an ICS link. That way you are able to import it in Google Calendar and such.

Each event type could be added in two ways:

- As regular appointments with a start/end, interesting for charging sessions and trips
- As all day events, where the time/total is listed in the item its event name

Idea:  Scatter plot with the old version number on X axis and new version number on Y axis (or maybe a 3D barplot).  The idea is to enable the use of clustering to pick out patterns, if any, in the software rollout.