Lexus integration planned?

[Sx54A]

Hello everyone! Some time ago, Lexus was supported by the old Toyota integration. I need to read out SOC from UX300e and RX450h+
Is there anything in this direction possible?

Thanks a lot.

[CM000n]

None of the current maintainers of the project own a Lexus vehicle. Since there is no official API, but everything takes place via reverse engineering and trial and error, it is rather unlikely that support for Lexus is to be expected in the near future.
If we receive pull requests from any developers who own a Lexus vehicle that extend the current functionality, these are of course more than welcome. 😊

[Sx54A]

Thanks for fast reply. Unfortunately my only chance to support is Chatgpt... After hours of coding (manipulating pytoyoda code) it gives up. I will wait and hope for the future.

[BJReplay]

Hi,

I have a (just purchased) Lexus in Australia.

I can confirm that the Australian Toyota app and the Australian Lexus App look identical, have almost identical app IDs (e.g. com.au.lexus.oneapp and com.au.toyota.oneapp) and DNS calls (logged via my self hosted adguard home) look pretty similar: login.lexusdriverslogin.com.au and openidm.lexusdriverslogin.com.au vs openidm.lexusdriverslogin.com.au and openidm.toyotadriverslogin.com.au

I am going to try to get this going for Australia if I can (it's a pity it's not monolithic, because it means I need to get the API working first before I can get HA working, and I am much better in HA than in python), and will report back, but, for at least Australia, I can report that the Lexus App and the Toyota app are identical. Same login, same functionality, same data (same image of a Lexus in the Toyota app), same nickname for the car set in the Lexus app shows up in the Toyota app).

[BJReplay]

Partial Success, Partial Failure, for AU:

Modifying the URLs in the python library threw up a CloudFront error:

pytoyoda.exceptions.ToyotaLoginError: Authentication Failed. 403,

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>ERROR: The request could not be satisfied</TITLE>
</HEAD><BODY>
<H1>403 ERROR</H1>
<H2>The request could not be satisfied.</H2>
<HR noshade size="1px">
Request blocked.
We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
<BR clear="all">
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
<BR clear="all">
<HR noshade size="1px">
<PRE>
Generated by cloudfront (CloudFront)
Request ID: <redacted>
</PRE>
<ADDRESS>
</ADDRESS>
</BODY></HTML>

But disabling certificate pinning allowed me to capture the full login sequence - and I'm hopeful that the cloudfront error was due to differences in the paths

Some of the URLs are slightly different - the key difference appears to be tmca vs tme in the paths, as well as the base site.

I'm going to review the sequence and once I think I've worked out the differences I can't tell what the Euro sequence is, but I can probably guess, I'll update my fork and try the python library.

[BJReplay]

I got a lot further:

Fixed the URLs. Needed to swap uuid for subname when parsing the JWT.

Logged in successfully, but the simple_client_example.py doesn't seem to find any vehicles. I'll need to set up a full debug environment to step through to work out why the call to list vehicles isn't returning anything - the call is still to v2/vehicle/guid - possibly the model of the results is different.

The call to account (CUSTOMER_ACCOUNT_ENDPOINT = "TBD" in const.py) is v4/account

But it looks very promising - at least for Australia - that both Lexus and Toyota can be supported.

[CM000n]

I'm guessing it is because the payload contains (many) more fields than the model.

Additional fields will just be ignored. So that can't be the issue.
Maybe I will have a closer look later.

[BJReplay]

I got a little further - I took a scorched earth approach and used https://github.com/koxudaxi/datamodel-code-generator to generate a pydantic model from my results from v2/vehicle/guid and basically replaced the entire vehicle model with this (aside from renaming a couple of classes so it could be used).

Bingo, _request_and_parse worked, and returned a vehicle, so there's something in the model that is incompatible with the json returned from the AU endpoint.

I'm so far out of my depth that I'm pretty much drowning - I hadn't seen a pydantic model two days ago - that I'm going to struggle to contribute much here without some pointers - but I can capture the data from the API (for both Toyota - which is all I'm looking at now) and Lexus, later, if needed.

If you think this is a bridge too far for this API, just let me know - I have enough that I can build myself an API that returns what I need.

But if you think you can extend the EU API to AU as well, I'm more than willing to help - there are a lot of Toyotas on the road in AU.

[CM000n]

Presumably, not only the content of the models is different (which would not cause any problems, as additional values are simply ignored), but the structure of the models is different, which leads to incompatibilities.
So if we want to provide an API for all regions at some point, we would also have to provide different models for the same endpoints.
We could definitely create a branch here to consolidate the work on an extension for AU in one place.
If you like, I can also invite you to join the organisation as a maintainer.

At what point exactly are you currently stuck now that you can read out the VIN information? If I were you, I would comment out almost all endpoint requests in the vehicles.py module and reactivate and evaluate them individually. You will probably have to either create a different model or use a different endpoint address for almost every endpoint.

[BJReplay]

but the structure of the models is different

Yes, I think that's it - I spotted at least one section (I forget now - away from the PC) where the results in the existing model were described as bools but the results in the json were "True" or "False" so strs.

At what point exactly are you currently stuck now that you can read out the VIN information?

I tried the rest of the sample client, and it didn't return data, but I suspect that is because...

If I were you, I would comment out almost all endpoint requests in the vehicles.py module and reactivate and evaluate them individually.

Thanks for the hint. Now that I've got the ability to work out how to create a basic pydantic model that I can use, I think I'll take the approach to create all the models for the key api calls.

If you like, I can also invite you to join the organisation as a maintainer.

Thank you. Let me get to the point that I have something working - and if I do, I'll get back to you. That would be an honour.

[CM000n]

Yes, I think that's it - I spotted at least one section (I forget now - away from the PC) where the results in the existing model were described as bools but the results in the json were "True" or "False" so strs.

That's not what I meant. Incompatible and non-existent values are simply ignored.
In this case, "True" and "False" str values are even automatically converted to bool. 😉
I am referring to the actual structure and namings of the models and submodels.

[BJReplay]

I need to read out SOC from UX300e and RX450h+
Is there anything in this direction possible?

Firstly, have you tried installing and logging in to your vehicle with the Toyota Connect app? Does it work? In my region (Australia) both the Toyota and Lexus app both display the same data, and I can log into both.

In fact, the login sets cookies for both:

Set-Cookie: amlbcookie=01; Path=/; Domain=lexus.com.au; Secure; HttpOnly; SameSite=none
Set-Cookie: amlbcookie=01; Path=/; Domain=toyota.com.au; Secure; HttpOnly; SameSite=none

First thing to try is logging into the Toyota app, @Sx54A

Here's the data for an NX450h+

{
  "payload": {
    "returnCode": "000000",
    "positionInfo": {
      "acquisitionDatetime": "2025-05-01T06:32:27Z",
      "longitude": redacted
      "latitude": redacted
    },
    "vehicleInfo": {
      "acquisitionDatetime": "2025-05-01T06:31:58Z",
      "remoteHvacInfo": {
        "remoteHvacMode": 0,
        "remoteHvacProhibitionSignal": 1,
        "temperaturelevel": 31,
        "settingTemperature": 22.5,
        "blowerStatus": 0,
        "frontDefoggerStatus": 0,
        "rearDefoggerStatus": 0,
        "frontSeatHeaterStatus": null,
        "rearSeatHeaterStatus": null,
        "steeringHeaterStatus": null,
        "latestAcStartTime": null,
        "temperatureDisplayFlag": null
      },
      "chargeInfo": {
        "plugStatus": 45,
        "plugInHistory": 41,
        "remainingChargeTime": 65535,
        "evTravelableDistance": 62.2,
        "evTravelableDistanceSubtractionRate": 5,
        "evDistanceAC": 59.1,
        "evDistance": 62.2,
        "evDistanceUnit": "km",
        "chargeRemainingAmount": 99,
        "chargeType": 15,
        "chargeWeek": 0,
        "chargeStartTime": "42:35",
        "chargeEndTime": "42:35",
        "connectorStatus": 2,
        "batteryPowerSupplyPossibleTime": 16383,
        "gasolinePowerSupplyPossibleTime": 1023,
        "fuelGage": 100,
        "fuelGageStatus": 1,
        "gasolineTravelableDistance": 876,
        "gasolineTravelableDistanceUnit": 1
      },
      "timerChargeInfo": null,
      "maxNoOfChargeSchedules": null,
      "solarPowerGenerationInfo": {
        "solarInfoAvailable": null,
        "solarCumulativeEvTravelableDistance": null,
        "solarCumulativePowerGeneration": null,
        "monthlySolarCumulativePowerGeneration": null
      },
      "odometerInformation": null,
      "driveMonitorDisplayRange": null
    }
  },
  "status": {
    "messages": [
      {
        "responseCode": "ONE-RES-10000",
        "description": "Success",
        "detailedDescription": "Success"
      }
    ]
  },
  "timestamp": "2025-05-01T09:33:38.948"
}

[Sx54A]

Hello and thanks for the support!

I installed the Toyota connect app. I can login with my Lexus credentials. I can scan the Code but then I get a error message. Please see attached screenshot.

[BJReplay]

Sorry I can't help - I don't have to scan a code when I log into the Toyota app - it just lists the details of my vehicle automatically.

That seems to suggest that there is a difference between the Toyota and Lexus apps in Europe.

Judging by the fact that this API can at least log in to the Toyota app in Australia, I can theorise that the Toyota apps in Australia and Europe and the Lexus app in Australia all use the same Authentication (oAuth with an IDP) and have at least a similar API in terms of calls based on what I have seen.

But, without a vehicle to test against in Europe, it is very difficult to say what problem you are hitting.

[Sx54A]

I'm so excited, that I'm not the only one with this wish! Just to add: in EU Toyota App, I tried to add my Lexus via VIN number (instead of using the Code from multimedia system). Here I get the clear message: I should use Lexus Link+ App for this Lexus

[macoch13]

I am a Lexus (NX 450h 2022 or 2023) owner - Europe. Using Lexus Link+ app, with limited development skills in Python, but can use Postman, know something about rest api and having some development experience with PHP. If someone shows me a direction, I can at least try to contribute.

[BJReplay]

I have had some limited success with the Lexus Connected app in Australia. Login was fairly straight forward (replacement of URLs), but models have had to be replaced completely to get much further, and even then I haven't really been able to get data from the JSON returned via the API into the python models and API.

Work on hold because doing some consulting at the moment. I've forked the repo to work on this, but not committed any changes, because it is far from working.

I will report back here if I get to the point that I have anything useful, but I don't know that I'll be able to assist very much other than with generic hints as to issues I faced and how I worked around them - and then not really until July.

[jrollenmueller]

I've successfully tested Lexus integration (Details here: #7 (comment)). How are we able to publish this within the main branch (also for Home Assistant - HA)?

[m-ca-l]

Hi all, I am new to setting up a HA dashboard, but love the functionality that this integration brings! I own a Lexus NX450+ (and have access to all other current models) and would be happy to support anyone here to get the Lexus integration over the line.

Unfortunatly I am not very techy so would need some hand holding in order to help.

Thanks for the cracking work - hopefully I can help. Cheers

[jrollenmueller]

Same for me - I am a little bit techie, but I am awaiting it for such a long time - please help us pushing it over the line!

[MaBeniu]

The changes are pushed for review and approval already couple months ago... repo owners seem to be busy or absent.

[Paja-git]

Just tested the Lexus EU for the NX450H+ via the sandbox/simple_client_example.py. Looks to be fully working. Data retrieved are correct.
It is time to add the Lexus option to the HA integration! @CM000n

2025-10-08 12:41:54.866 | INFO     | __main__:get_information:55 - Logging in...
2025-10-08 12:41:56.829 | INFO     | __main__:get_information:58 - Retrieving cars...
2025-10-08 12:42:04.376 | INFO     | __main__:get_information:90 - Dashboard: {
    "odometer": 51305.0,
    "odometer_with_unit": {
        "value": 51305.0,
        "unit": "km"
    }, 

[CM000n]

I will definitely take a look at it. 😊 But it would probably be best if someone here who owns a Lexus could do some PR, test it against their own vehicle, and develop it.

[Paja-git]

Thanks, I've made changes offline and it looks promising. I'll try to do my very first PR. Please be patient with me if any mistakes.