teslamate-org / teslamate

A self-hosted data logger for your Tesla 🚘
https://docs.teslamate.org
MIT License
6.07k stars 757 forks source link

Consumption on raven? #191

Closed andersalavik closed 5 years ago

andersalavik commented 5 years ago

I wont get any consumption? Anything else seams to work grate.

We have an Model X Raven.

bild
adriankumpf commented 5 years ago

To estimate the consumption TM ships with a set of efficiency factors (Wh/km) for different vehicles. Those factors have been crowdsourced and are not not complete ... yet!

You can contribute the factor for your Model X after charging a couple of times: on the efficiency dashboard it displays the derived efficiency factors based on your data. If a value has been confirmed several times, feel free to post a screenshot of those values!

Edit: What's displayed below the name of your car on the web interface? If "Model X ..." is not shown (or if it just shows "Model X"), please add the first lines of the container logs after (re)starting TM (it should print "Vehicle could not be identified! ...").

mapchen commented 5 years ago

I experience the same issue with a raven.

For me its written Model X in the web page and the vehicle seems to be identified. At least i can not see a problem in the log.

adriankumpf commented 5 years ago

Then what's mentioned above applies to you too. If both of you can confirm the same efficiency factor it makes sense to add it.

For me its written Model X in the web page and the vehicle seems to be identified. At least i can not see a problem in the log.

It won't log an error. It's just debug information to identify new vehicles and it should be written right after starting TeslaMate.

mapchen commented 5 years ago

Lets see if this helps regarding the identification error:

teslamate_1  | waiting for postgres at db:5432 (2sec)
teslamate_1  | 08:15:07.133 [info] Already up
teslamate_1  | 08:15:35.544 [info] Running TeslaMateWeb.Endpoint with cowboy 2.6.3 at :::4000 (http)
teslamate_1  | 08:15:35.550 [info] Access TeslaMateWeb.Endpoint at http://192.168.0.31
teslamate_1  | 08:15:35.823 [info] Adding elevation to 1000 positions ...
teslamate_1  | 08:15:35.875 [info] Querying location for elevation takes longer than 50ms ...
teslamate_1  | 08:15:37.173 [info] Found 'TeslaMatthias'
teslamate_1  | 08:15:37.249 [info] Initializing handler
teslamate_1  | 08:15:37.250 [info] Connection has been established
teslamate_1  | 08:15:38.954 car_id=1 [info] Start / :online
teslamate_1  | 08:15:38.956 [warn] Vehicle could not be identified!
teslamate_1  |
teslamate_1  | %TeslaApi.Vehicle.State.VehicleConfig{
teslamate_1  |   can_accept_navigation_requests: true,
teslamate_1  |   can_actuate_trunks: true,
teslamate_1  |   car_special_type: "base",
teslamate_1  |   car_type: "modelx",
teslamate_1  |   charge_port_type: "EU",
teslamate_1  |   eu_vehicle: true,
teslamate_1  |   exterior_color: "Pearl",
teslamate_1  |   has_air_suspension: true,
teslamate_1  |   has_ludicrous_mode: false,
teslamate_1  |   key_version: nil,
teslamate_1  |   motorized_charge_port: true,
teslamate_1  |   perf_config: nil,
teslamate_1  |   plg: true,
teslamate_1  |   rear_seat_heaters: 3,
teslamate_1  |   rear_seat_type: 4,
teslamate_1  |   rhd: false,
teslamate_1  |   roof_color: "None",
teslamate_1  |   seat_type: 0,
teslamate_1  |   spoiler_type: "Passive",
teslamate_1  |   sun_roof_installed: 0,
teslamate_1  |   third_row_seats: "None",
teslamate_1  |   timestamp: 1570601738528,
teslamate_1  |   trim_badging: nil,
teslamate_1  |   wheel_type: "AeroTurbine20"
teslamate_1  | }

regarding the effeciency factors. I have not charged a lot so maybe this page populates correctly after a while ?

image

adriankumpf commented 5 years ago

Yes, this definitely helps. However, it will be difficult to distinguish between LR and Performance.

regarding the effeciency factors. I have not charged a lot so maybe this page populates correctly after a while ?

That's exactly how it is. It needs multiple charges that took longer than 15 minutes.

I'm wondering, though, why you're getting an error. Could you hover over the red icon and paste the message that's being displayed here?

mapchen commented 5 years ago

I'm wondering, though, why you're getting an error. Could you hover over the red icon and paste the message that's being displayed here?

It says: pq: division by zero

adriankumpf commented 5 years ago

I'm wondering, though, why you're getting an error. Could you hover over the red icon and paste the message that's being displayed here?

It says: pq: division by zero

That's fixed with the latest release (v1.11).

andersalavik commented 5 years ago

I think my optioncodes are fucked up.

Its a Modexl X Standard Range

19:49:19.969 [warn] Vehicle could not be identified!

%TeslaApi.Vehicle.State.VehicleConfig{ can_accept_navigation_requests: true, can_actuate_trunks: true, car_special_type: "base", car_type: "modelx", charge_port_type: "EU", eu_vehicle: true, exterior_color: "Pearl", has_air_suspension: true, has_ludicrous_mode: false, key_version: nil, motorized_charge_port: true, perf_config: nil, plg: true, rear_seat_heaters: 3, rear_seat_type: 3, rhd: false, roof_color: "None", seat_type: 0, spoiler_type: "Passive", sun_roof_installed: 0, third_row_seats: "FuturisFoldFlat", timestamp: 1570902559768, trim_badging: nil, wheel_type: "AeroTurbine20" }

option codes: ["AD15", "MDL3", "PBSB", "RENA", "BT37", "ID3W", "RF3G", "S3PB", "DRLH", "DV2W", "W39B", "APF0", "COUS", "BC3B", "CH07", "PC30", "FC3P", "FG31", "GLFR", "HL31", "HM31", "IL31", "LTPB", "MR31", "FM3B", "RS3H", "SA3P", "STCP", "SC04", "SU3C", "T3CA", "TW00", "TM00", "UT3P", "WR00", "AU3P", "APH3", "AF00", "ZCST", "MI00", "CDM0"]

bild
adriankumpf commented 5 years ago

I guess Tesla still haven't fixed this issue in their back end :/ That makes it pretty much impossible to automatically distinguish between the Model X LR and Performance unless both have the same hard-coded factor.

adriankumpf commented 5 years ago

Fixed with abfa8c96d5ef1d6007f356afd6f84aea5c1f2bdc

mapchen commented 5 years ago

I am still struggling to get anything to be populated into the derived efficiency table. image Any other hint what to do?

adriankumpf commented 5 years ago

The fix has not yet been released :) Wait for v1.12.

mapchen commented 5 years ago

just to give some feedback. This is how it looks after v1.12 upgrade. I do get now efficiency factors but average consumption is still not shown. @adriankumpf I can not say if this is by intention?

image

adriankumpf commented 5 years ago

Which type of range do you have configured – rated or ideal?

mapchen commented 5 years ago

rated.

adriankumpf commented 5 years ago

I almost forgot – the consumption values will be updated the next time you charge. To trigger a recalculation immediately, temporarily change the preferred range.