Great application. I'm only a month into it, but have a suggestion:
Can it read a standard calendar (i.e Google Calendar) and use that as part of the scheduler? For example, if calendar entry has a "location" assigned to it and the car is plugged in, you can:
(1) Query the current temperature and outside temperature verses the set point and intelligently turn on HVAC in advance. (This can be set to work only if plugged in.)
(2) Raise the charge level and give a boost charge before the event.
In an ideal solution, you could query the location of the car against the location in the calendar to estimate driving time. By subtracting the driving time, you have a time to work backwards from in terms of HVAC and increasing the charge. Since not all calendar entries will require car travel, perhaps it could only work if a full address is listed and it's more than 1 mile from the car's current location?
It's my understanding that going over 80-90% isn't detrimental if you plan to immediately use it. Perhaps it queries the distance to your next calendar event and estimates how much additional charging your completed trip will take? In other words, if it's 10 miles away, it'll automatically pre-charge the car for an additional 10 miles worth of estimated driving. I feel like this could help limit range anxiety by allowing people to normally keep their battery at a standard (or even lower) level, but "top it off" on-demand, knowing it'll be at your typical estimated range AFTER your trip.
Basically, this would be a smarter way to precondition for those of use without regular commuting schedules.
(I also love the idea of a boolean style HVAC scheduling as noted above. It could work not only in extreme heat, but prevent the car from dropping below a certain temperature.)
Thanks for all your work on this.
