-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't force data update anymore #830
Comments
I was hit with this myself this morning, I think it's safe to say this is #774 ? |
No this is not really the same as #774. This is caused by a change in the owner API for an endpoint that the Tesla App is not using anymore. For the fleet API they apparently maintain this endpoint for backwards compatibility. The list of vehicles is no longer available at |
Thanks for the info. |
If you're happy to make a Pull Request to fix it then by all means, otherwise you'll have to wait for someone else to get round to doing it |
If I have followed the codeflow correctly, the changes to the API must be made in the external package teslajsonpy (https://github.com/zabuldon/teslajsonpy/blob/master/teslajsonpy/endpoints.json). As soon as a new version is available, it must be used in this plugin and a new release must be made. |
Sadly my coding skills are less than basic. Otherwise I’d be happy to do so. Let’s hope someone will come with a solution. If needed I’ll be available to test! |
If the wake up command works this might kick off an update. Or turn sentry on/off. |
This comment has been minimized.
This comment has been minimized.
I removed offending step from automation and Steering wheel and seat heater - heat level / auto also prevented script running, issues seems too coincidental. Debug looks similar. |
Yesyerday I was having the same issue too... I then tried the
I do use the API a lot when checking for charging rates to make sure I control my charging amps to only use what excess solar is available. So lots of calls every couple of minutes.. starts with a 'force data refresh'.. This morning tried again with and got this error:
Not sure what this means, but I guess they may have changed access to some of the API's? |
Asleep state also doesn't update since the same date, probably relates to the same issue. |
Looks like this problem has been reported at teslajsonpy (where it belongs) as well. |
Seems like only 'leasing' cars have this issue. I have one Y (owned) and 3 (leased). Y works fine but issue with 3 |
That is not the case. My owned Y is not working :( Maybe don’t draw conclusions from a sample of two cars. |
Please be advised .. I have mentioned 'seems'. No conclusions drawn... Keep the 'tone' appropriate !! |
Closing as this is all #774. Please follow that. |
Version of the custom_component
3.19.5
Configuration
/
Describe the bug
I've been using this integration to connect to my Model S and charge it on solar power with the following script: https://github.com/flashg1/TeslaSolarCharger
It's been working fine for a couple of months (with some errors on the script's side) but since this morning I noticed the car not charging. I checked and all data from the integration were available, however I received an unknown error when clicking the
force data update
-button. As the script heavily relies on this button to be able to work this seems to be the issue at this point.I checked the logs and there are multiple API errors (see logs). I tried reinstalling the integration, using a new refresh token. I can add the car without any issues but still the
force data update
-button isn't working.Any idea's?
Debug log
The text was updated successfully, but these errors were encountered: