Image of the car?

[MikeBishop]

The app is clearly able to generate an image of the car. From some inspection on the Tesla web site, it looks like it's using a URL like....

https://static-assets.tesla.com/v1/compositor/?model=m3&view=STUD_3QTR&size=1440&options=DV4W,IN3PW,COL3-PPMR,W38B,MT303&bkba_opt=1&context=design_studio_2

However, since the options codes in the API have been frozen/deprecated, clearly they're getting the list of options from someplace else. It's possible they're just translating things off data_request/vehicle_config, in which case the translation database must be a pain to manage. Any chance to retrieve that translation code? Can you tell if the app using the same approach to get the vehicle image?

[davidhodge]

I don't know what the official Tesla app is doing, but for Nikola I decided that I have had to maintain a mapping from known vehicle_config varieties to option codes. Would love to know if there's a better way to do it, but have yet to find it.

[kevinelliott]

@davidhodge How are you able to detect Model 3 Performance in Nikola from the vehicle_config? I'm not seeing anything obviously different than a standard Model 3.

[Urkman]

Why is this closed? I think this still a valid question...

[itsMeDavidV]

Yeah I also don't necessarily think this should be closed. There is a valid approach to getting vehicle option codes. We should work to figure this out.

See: tdorssers/TeslaPy#11 (comment)

[timdorr]

This isn't part of the API. The options codes haven't worked properly for years. However one gets a picture of their car using this image generation service isn't going to be done through this API, hence I closed this out.

[itsMeDavidV]

Hmm I don't think we can completely rule out that the API won't give us access to option codes or a vehicle image.

Just some from endpoints:

"VEHICLE_DETAILS_ASSETS_REQUEST_V2": { "TYPE": "GET", "URI": "bff/v2/mobile-app/ownership/vehicle-details-assets/v2", "AUTH": true }

"OWNERSHIP_VEHICLE_SPECS_REQUEST": { "TYPE": "GET", "URI": "bff/v2/mobile-app/ownership/vehicle-details", "AUTH": true }

"OWNERSHIP_RESERVATION_DETAILS_REQUEST": { "TYPE": "GET", "URI": "bff/v2/mobile-app/ownership/reservation-details/{rn}", "AUTH": true }

"VEHICLE_ORDER_LIST": { "TYPE": "GET", "URI": "api/1/users/orders", "AUTH": true }

There's something to be said for if a token intended for owner-api use will allow access to these, however I think this is def worth figuring out. Best case, it does.

[timdorr]

The API gives you option codes, but those have been the same option codes (regardless of the actual car configuration) for any vehicles produced in the last few years. They're not the same ones provided by the Tesla Account site where this image lives.

[itsMeDavidV]

Right, I'm thinking there's a possibility for a new source for correct option codes in the API.

[Urkman]

I also think, there is a valid way to get the option codes... Somewhere...
Tesla also needs them in their app...

[timdorr]

They get that from the data endpoints. Specifically, from vehicle_config, which uses more semantic descriptors than just option codes.

Options codes mostly came from Salesforce data. The website might be obtaining it directly as an option code list and the mobile app API might be translating that data to the semantic structure for the vehicle_config data/endpoint.

[Urkman]

Something like this?
https://gist.github.com/Kemmey/b18964d42c5617b2247fa7bacbfa2638

[MikeBishop]

Yes, that is one major piece of code I drew from to generate my own translation.

[Urkman]

Perhaps you can share the code?

[MikeBishop]

https://github.com/MikeBishop/MMM-Powerwall/blob/master/MMM-Powerwall.js#L2283

[Urkman]

@timdorr Perhaps we should add these mappings somewhere to the Documentation. And enhance it, when there will be new mappings?
As for my MY(09/2022), the wheels are: "Induction20Black". That is currently not handled by the mapping...

[timdorr]

We have the option codes listed here: https://github.com/timdorr/tesla-api/blob/master/docs/vehicle/optioncodes.md

But how they're translated to the API data seems like a futile effort because they change so often and we don't know if Tesla will introduce further structural changes. That seems like a lot of work to map to just this one single image generation service 🤷

[Urkman]

I think it would be grate, to have a source of information for this...
btw, here are the codes for the two new colors and the wheels used in Germany:

    // Induction20Black: WY20P
    // Gemini19: WY19B

    // Quicksilver : PN00
    // MidnightCherryRed  : PR00

[MikeBishop]

Added, thank you! I'll take any other updates here.