-
-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong car model in fleet statistics #545
Comments
Could you please send me your Logfile |
This part (the only ref in 3000 lines or send the full logfile where? 27.03.2021 03:30:47 : #2: change TeslaLogger state: GoSleep -> Start 27.03.2021 03:30:47 : #2: Restart communication with Tesla Server! 1 |
Please send me your whole Logfile to: mail a.t pogea.de |
Done thank you |
Please update to latest version. |
Thanks, all charts now go to M3 LR The only reason I became aware of trim_badging was in doing PD on the problem - my performance M3 returns p74d in trim_badging The M3 LR has the same battery as the p74d but the efficiency/range numbers are different, the new performance (with the heat pump/octovalve) comes with a different battery capacity and therefore, I assume, different trim_badging. |
…nextgen Feature closechargingstate nextgen
Could you please send me the raw JSON file of your nodered code? |
I use https://github.com/mseminatore/TeslaJS so don't get a JSON or do you mean something else - I can provide the object returned unedited |
you can see the raw JSON that TeslaLogger receives from Tesla: |
Hi,
Do I need to enable something else for debug or am I targeting the wrong docker container? |
this is the docker container where TeslaLogger.exe is running |
That was fun:
|
For comparison, here's what teslaJS returns:
|
WTF? |
LOL |
Model S, TeslaLogger: {"response":{"can_accept_navigation_requests":true,"can_actuate_trunks":true,"car_special_type":"base","car_type":"models","charge_port_type":"EU","default_charge_to_max":false,"ece_restrictions":true,"eu_vehicle":true,"exterior_color":"Red","has_air_suspension":false,"has_ludicrous_mode":false,"motorized_charge_port":false,"plg":true,"rear_seat_heaters":1,"rear_seat_type":1,"rhd":false,"roof_color":"None","seat_type":1,"spoiler_type":"None","sun_roof_installed":2,"third_row_seats":"None","timestamp":1617086937685,"trim_badging":"85","use_range_badging":false,"wheel_type":"Base19"}} |
I'm being victimised ;-) |
since update yesterday we've got trim badging for model3. |
Hi, I have a base performance from 2019 (Model 3 Performance WITHOUT performance package). http://teslalogger:5000/debug/TeslaAPI/1/vehicle_config gives:
|
I have a pre-octovalve Model 3 performance, if you interrogate vehicle_config.trim_badging then the correct value of p74d is returned i.e. 74kWh of usable battery.
If I go to My Degradation" then I'm presented with M3 SR+ a 62kWh battery
The chart for LR would be slightly more appropriate (but still incorrect) as the battery size is the same
A chart for M3 performance is required as the P3D range is less than that of the LR
The same applies to other fleet charts.
The P74D needs to be segmented out in the data harvest as:
It should be noted that the "2021" performance model 3 has a larger battery and will report a different trim_badging
The text was updated successfully, but these errors were encountered: