Toyota Connect

CM000n · December 4, 2023, 10:27pm

I do not have the possibility or authorization to publish a new version with the hotfix. Only @DurgNomis-drol can do that.

But be warned, the current version with the hotfix has lost some of its functionality in preparation for major changes!

We are also currently in the process of rewriting the mytoyota Python lib, on which the custom component is based, to the new API endpoints. However, this is a major undertaking:

github.com/DurgNomis-drol/mytoyota

New API Endpoints: Basics working. Thoughts & Help needed

DurgNomis-drol:master ← GitOldGrumpy:master

opened 12:14AM - 18 Nov 23 UTC

GitOldGrumpy

+37255 -4102

### Status This is the initial work on interfacing with the new API/Endpoints…/application. It is very much a WIP(work in progress) but it does work to pull the basic information. No statistics, trips or HVAC all of which are possible and currently nothing can be sent back to the car(e.g. turn on your de-foggers) but again is possible when I work out the endpoint. However I've pushed it up for discussion as I want to propose a change and am after peoples thoughts. ### Proposed Change It currently seems that getting details about a car is split between interfaces `Vehicle` and `MyT`. For example, if I want to know what the fuel level I call `get_vehicle_status` with the VIN and inspect the returned `Vehicle` object **BUT** if I want trip details I call `get_trip` on `MyT` with the VIN and a trip_id. I think a better approach is that all functionality for a Vehicle is called on a Vehicle object. This would mean that `MyT` only has two methods `login` and `get_vehicles`. The new `get_vehicles` method returns a list of `Vehicle` objects. For example, ``` client = MyT("username", "password") client.login() vehicles = client.get_vehicles() vehicle = vehicles[0] # Get Fuel Level vehicle.dashboard.fuel_level # Or just vehicle.fuel_level # Get trips vehicle.trips(from=yesterday, to=tomorrow) # Or some such arguments ``` Why make this change: - Better encapsulates a Vehicle. For example, unless the user wants to know the VIN then they never have to use it. - Vehicle becomes responsive. Currently once you've got the vehicle status it does not change but with this change a call to `vehicle.evRange` could update as it could make another call to the API to check. (I've noticed the new API is more responsive then the old) - It solves a problem with the new endpoints(and possibly the old) that the vehicle can check if the vehicle supports a given endpoint before its called. For example `get_vehicle_electric_status_endpoint` does not exist on cars that are not electic/hybrid so the call fails, so why call it? All the capabilities are returned with the initial vehicle information in the `extendedCapabilities` field this will be easy to manage when everything is handled in the one Vehicle class. - There are 76 of these capabilites **BUT NOT** all relate to an endpoint. ### Help needed In the merge request there is a new file `simple_client_test.py` it would be helpful if people run it and tell me if it works. 1. just to know it works on more than two cars ;-) 2. to check if other cars return less/more information 3. to see what other cars have what capabilities ### Finally Thanks to wide wings and his work on another project that helped nail the authorisation(which is only slightly different). Unfortunately many of the endpoints are totally different.

Perhaps @DurgNomis-drol would like to wait with the release of a new version until this preliminary work has been completed and a custom component based on the new mytoyota API endpoints can be created.

Piggyback · December 5, 2023, 8:11am

Fully understood. I´d be happy to help testing! I´m thinking if it would be helpful to have this as a separate repository (for those migrated to the new Toyota app) which allows to use this beta version or have it as a development branch in HACS to test.

Worst case logically I can copy the code manually and help testing, but having it available through HACS would just simplify and you can go back to older versions easily if needed.

CM000n · December 5, 2023, 9:41am

We have no need for a separate repo. HACS already supports the download of beta versions. But someone would have to publish one first

Piggyback · December 5, 2023, 9:54am

Ok! I’ll just patiently wait for @DurgNomis-drol to post it if possible so I can support!

DurgNomis-drol · December 14, 2023, 4:18pm

As @CM000n says, no need for a separate repo. You can just choose master at the bottom of the list to get the cutting edge.

Piggyback · December 15, 2023, 12:05pm

Thanks @DurgNomis-drol! Did you already post the new code as beta master? It does not seem to work yet. Don´t want to complain or put pressure. Just would like to help if I can.

CM000n · December 15, 2023, 9:12pm

See my comment from above: Toyota Connect - #82 by CM000n

The hotfix is already in the main/master branch but will lack some functionallity.

There is currently no development for the custom component for the new Toyota API. First we have to get it functional in the underlying Python Lib.

Piggyback · December 16, 2023, 9:19am

Thanks. I’ve got it loaded and although initially it did not connect now it does and I do get limited data so perfect. Looking forward to help testing if needed.

CM000n · January 14, 2024, 9:56pm

Breaking changes ahead
Read carefully!

Version 2.0.0 of the toyota Custom Component now includes all customizations for the new Toyota oneapi!
This also means that this version is no longer compatible with your vehicle if you are still using the old MyT app! Before updating, please make sure that you are already using the new MyToyota app and that your vehicle has already been migrated to the new API.

The changes may not look big to you in terms of the Home Assistant sensors and entities, but there have been huge changes in the background!
Especially due to the great support of @GitOldGrumpy and @CM000n , there were more than 50,000 lines of code changed in the mytoyota Python Lib and the ha_toyota Home Assistant Custom Component to ensure compatibility with the new Toyota API.
But of course, as the initiator of the two projects, we should not forget to mention @DurgNomis-drol.

All these changes make it necessary for you to completely remove the previous Custom Component installation from your Home Assistant devices and HACS!
You should then perform a reboot and can then reinstall the custom component via HACS again.

If you encounter any problems, please create an issue at: Issues · DurgNomis-drol/ha_toyota · GitHub

jztan79 · August 16, 2024, 3:24am

Any chance in the future this addon will be update with EV info for hybrid plugin cars. And remote start button.