OrientExpress wrote:Nope, Until LEAF Spy can be certified by Nissan as being a credible measurement tool, it serves no purpose other than to entertain.
I can see this attitude from a journalist. LeafSpy is not a fully creditable source of information.
Yet LeafSpy is useful. And can be verified as mostly correct by use.
Distance to empty, for example.
I'd like to have the dashboard displays from Nissan give me distance to empty (aka GOM) that I could trust. However, I know that that requires more information that the car has. Picture this: I'm sitting in my garage, and I'm getting ready to go somewhere.
Does the car know where? It might guess, based on day of week and time of day, that I'm about ready to do my usual commute. But that's a guess. And other times it probably can't even guess. Unless it can hack DuckDuckGo.
Does the car know what the weather is outside the garage. I do, but the car doesn't unless it receives weather reports. Does the car know that the roads I'm about to drive on have 10 cm of snow? Or not? Have they been plowed? Or not? Oh and the temperature is 18 F and the wind is blowing out of the south.
Does the car know if I'm in a hurry, or if I'm going to drive to stretch range? I don't see how.
I know more than the car, and can guess and then enter a miles per kWh into LeafSpy, and LeafSpy can project a range to Low Battery Warning. I use this to manage charging, driving and sometime route to arrive home above or just below LBW. Why? I want margin. Keeps me from worrying. The LEAF's gauges don't give me the ability. I can project a more accurate miles per kWh than the car car, mostly because I know more than the car does.
I'd like the same functionality from the car, of course. Let me adjust the (km/m)/kWhr used by the range estimator based on what I know. Let me set a different end point, perhaps 50% plus margin on an out and back run, or LBW, or VLBW, or something else.
The battery temperature bar is a joke. Please pass on the feedback that a real temperature gauge reading in F/C is useful.