The reason we don't use Geo-Fence labels as location labels is because we've found a lot of GeoFences are not named based on geographic location. This is one of the reasons we separated out "Locations" to enable custom labels for common destinations. This gives pilots the best of both worlds being able to name locations and geo-fences separately as well as the functionality to create geo-fences from locations. Perhaps there is a better way to make this clearer for a user interface perspective?
Would there be a way for your system to "look up" the starting and ending drive locations to see if they are geofenced locations, and if they are, then use the location name instead of the address?
As an example, my drive today, which started at home, resulted in a "drive underway" message that provided a location near, but not at, my home. If it just reported "Drive begin at <location name>, that would be an improvement. Also I have not yet given you feedback on the drive notifications, and I will soon, but right off the bat, your @ sign should just be "at." That symbol was historically only correctly used for "five apples @ 50 cents each." Now, of course, it is also used in email addresses, and many people use it incorrectly exactly as you have, but it is actually incorrect.
The entire color pallet and overall design for the thing is being re-developed by people who know much better than I about artsy fartsy but most likely will be driven by the exterior color of the car and a pallet to match. In the short term I will at least make it readable.
Awesome!
Last thing, when you say pop the graph our, do you mean go to full screen?
Full screen, or just quite a bit larger, but with your stuff still showing in the background.
There's a lot of information there, and the bigger the better, if people want to examine the data more closely.
Thanks again for all the feedback and your time.
Happy to keep helping! Thanks for being so responsive!
Sorry to sound redundant but I really can't thank you enough for your time on this.
The way TC is calculating efficiency is pretty straightforward and may be completely wrong. When the charge is completed the number of miles added by the charge is divided the "actual" miles added which is the difference in range between the start of the charge and the end of the charge. If the charge adds 10 miles and there are 10 miles more in range at the end of the charge from the beginning, that 100% efficiency..right?
I'm not certain, but I think you may just be calculating and deducting the vampire drain during the charge. I'm not sure how TeslaFi gets both numbers. I'm just almost certain that their calculation is correct.
Also checked on the battery heater notifications, at no point did the API "see" the battery heat on (only looked in last 24 hours).
That's interesting, because everyone claims the battery will heat when the cabin is heating on shore power if range mode is off. We'll have a better idea tomorrow, as when my car starts charging tonight, the battery heater is sure to come on. Let's see if your software "sees" it or not.
And thinking more about it, you said your software didn't see my battery heater on any time in the last 24 hours. I only turned the notification on this afternoon, but the charge overnight would have also turned on the battery heater. Is it possible that somehow you may only be seeing the battery heater on if the car is also on? I drive with range mode on, so the heater would not be coming on during my drives. If we need to test this though, I can start my drive tomorrow with range mode off, which would definitely start the battery heater. Then we would know for certain if somehow your software is just not getting the information from the car correctly.
One more quick thing...
The geofence messages end with the note about the time zone, but they are not time-stamped. You may want to include the time in the message.
Again--many thanks!