Cyclone
Cyclonic Member ((.oO))
*Tesla fudging the numbers it's reporting.
If you really want to know the actual numbers, third party device is the best way to go, of course you have to validate the calibration of that device. No logger can unfudge the numbers.
I wouldn't say Tesla is fudging the numbers. What is listed is indeed the energy at the chargeport. However, there are losses before getting to the chargeport that the Sense is "seeing".
Consider converting music to MP3s. From a master source, it is converted to a format suitable for CDs. Then this CD format is often read in and converted to MP3s. Let's say you are using 256 kbps , 16-bit MP3 audio conversion. Then you send that from your MP3 player over Bluetooth to a premium sound system. Let's say the Bluetooth profile on the sound system supports 128 kbps , 8-bit MP3 audio. While surely you can blame the Bluetooth connect (predominantly the profile at the receiver) for some conversion losses, you would show even greater losses when comparing it to the CD or the master source. It is unfair to blame the Bluetooth receiver for those losses as they are beyond it's control.
So, if you want to complain about any losses between the chargeport and the battery, go right ahead. But don't blame Tesla for losses between the meter and the chargeport. You may want to yell at Tesla for any losses the UMC causes, but those numbers aren't being reported, so you still shouldn't turn around and say they are fudging the numbers.