Receiving HTTP 429 errors about ha_toyota HOT 24 CLOSED

See #204 for the reason it does not work, will publish a fixed version soon

from ha_toyota.

Can confirm fix works, will be releasing a new version shortly!

from ha_toyota.

thank you

from ha_toyota.

Same issue with my system. I've tried deleting both the integration and the HACS package while restarting HA with no effect. Following this issue, thanks for reporting

from ha_toyota.

Exactly the same here. All sensors unavailable:
Error fetching toyota data: HTTP: 429 - Too Many Requests. Please try again later.
Error fetching toyota data: Update canceled! Toyota's API was too slow to respond. Will try again later...

from ha_toyota.

Tried updating the integration using the github-repo (rather than the release in HACS).

After Disabling and Enabling the integration, there is an Failed to set up error on the integration screen.

Checking the logs, it shows the same 429, as well as an Update Cancelled error.

Log Output

This error originated from a custom integration.

Logger: custom_components.toyota
Source: helpers/update_coordinator.py:223
Integration: Toyota Connected Services (documentation, issues)
First occurred: 8:52:54 AM (139 occurrences)
Last logged: 11:58:46 AM

Error fetching toyota data: HTTP: 429 - Too Many Requests. Please try again later.
Error fetching toyota data: Update canceled! Toyota's API was too slow to respond. Will try again later...

from ha_toyota.

It's now taking forever to pull any data in their official app, somebody in Toyota needs to restart the NGINX ;)
Their infrastructure is in shambles, probably running on a potato, hopefully the problem will go away soon.

from ha_toyota.

It's now taking forever to pull any data in their official app, somebody in Toyota needs to restart the NGINX ;) Their infrastructure is in shambles, probably running on a potato, hopefully the problem will go away soon.

Toyota's servers are the worst things I have ever worked with 😆 😭 They crap out for no reason what so ever

from ha_toyota.

Same here. Could it be that they modified their api rate limiter?

from ha_toyota.

hello
same issue for me.

from ha_toyota.

Same issue for me. I can't get it work for several days...

from ha_toyota.

Same here

from ha_toyota.

same here for many hours...

from ha_toyota.

A possible explanation could be here: https://twitter.com/samwcyo/status/1597792097175674880

from ha_toyota.

The API for Toyota (MyT) is still online. Debuggning a HASS integration was a little bit too much for me. I tried my shot reverse-engineering the API and realised that this integration is an spinoff/inspired from the project https://github.com/calmjm/tojota.

I have now created a fork of the above project, which publishes data to MQTT when executed (this can be accomplished via an automation and Shell Command), from which HASS can automatically pick up the data. Note, I do not have any remote control functions, hence they are not present in the published MQTT data.

If @DurgNomis-drol could point me in the right direction for debug I can help try to solve this issue in this integration.

from ha_toyota.

even with testing just the simple example in https://github.com/DurgNomis-drol/mytoyota/tree/v0.7.7 i get 429 as soon as client.get_vehicle_status(car) is called which seems to issue 4 concurrent requests https://github.com/DurgNomis-drol/mytoyota/blob/v0.7.7/mytoyota/client.py#L248

I guess we need to limit the number of concurrent requests ?

from ha_toyota.

No, it doesn't work (I've tried this approach)
I just added an issue here:
DurgNomis-drol/mytoyota#204

from ha_toyota.

@Iture issue seems like a good reason as to why it does not work, or they have added aggressive rate limiting to their API to stop integrations like this from getting data from them. Either way, this will require substantial work to fix, if even possible.

from ha_toyota.

from ha_toyota.

The server endpoint seems to be oke. The mytoyota library that is being used is also connecting to: "https://myt-agg.toyota-europe.com/". Can you check or determine if the complete URL of the endpoint is still: "https://myt-agg.toyota-europe.com/cma/api" (including the 'cma/api' suffix?)

from ha_toyota.

from ha_toyota.

@joro75:
The server endpoint seems to be oke. The mytoyota library that is being used is also connecting to: "https://myt-agg.toyota-europe.com/". Can you check or determine if the complete URL of the endpoint is still: "https://myt-agg.toyota-europe.com/cma/api" (including the 'cma/api' suffix?)

There are essentially three different endpoints used:

• https://ssoms.toyota-europe.com/authenticate
  • Authentication
• https://cpb2cs.toyota-europe.com/api/
  • List of Vehicles w limited Metadata (https://cpb2cs.toyota-europe.com/vehicle/user/{UUID}/vehicles)
  • Vehicle Metadata (https://cpb2cs.toyota-europe.com/vehicle/user/{UUID}/vehicle/{VIN})
  • Workshop History
  • Location Status (https://cpb2cs.toyota-europe.com/api/user/{UUID}/cms/share/location/{VIN})
  • Trips (https://cpb2cs.toyota-europe.com/api/users/{UUID}/vehicles/{VIN}/workshop)
  • Statistics (Trip Summaries) (https://cpb2cs.toyota-europe.com/api/user/{UUID}/cms/trips/v2/history/vin/{VIN}/{INTERVAL={1,2,3}})
• https://myt-agg.toyota-europe.com/cma/api/
  • Odometer/Fuel
  • Remote control

from ha_toyota.

@ajain-93 : Thanks for the information. Most of the endpoint URL's are also being used by mytoyota. However (to my suprise), some of them are also slightly different. That's interesting, but no need to change it at this moment.

from ha_toyota.

@joro75:
https://ssoms.toyota-europe.com/authenticate and https://cpb2cs.toyota-europe.com/api/ones i mentioned above are the ones I was able to reverse-engineer by checking out the Swedish MyT portal on the web. The last one though, doesn't show up for me in my webbrowser.

from ha_toyota.