It is very precise and the number is indeed somewhere around 152-153.
Probably 152.5 rounded to 3 or something like that. I posted a screenshot a while back.
This is why I have hard time calculating in miles. Actually the math is 76.5 and below not 75.5 like I said.
And I actually tested this, when I was at around 76kWh it showed about 497km
Too many rounding errors you guys should change to km
I think it's actually better to use miles, at least for US cars. The reason I say this is because I know that the API app provides the raw data in miles, and has to be converted to km by the app if the car is set to display km.
Also, I know my car's constant is exactly 287, an integer. I am able to verify that exact value by using the API miles value with 2 decimal places along with my TM-Spy data. The 287 number clearly does not convert to an integer for km. The conversion value for km is 178.3332.
Now maybe European cars do it the opposite way, and use a precise km constant that has to be converted to miles. If that is the case, then you should stick with km.
I have a question for you. Does SMT give a value for either rated miles or km? Or do you have to read the value from the car display?
I know TM-Spy does give a rated miles value for model S, but it only gives it to a rounded whole number. But I have been able to verify it is the same as the API value, except rounded. But I need the API number with the additional precision to verify the exact constant my car uses.