Skip to content
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

[tesla binding] API not responsive to invoking vehicle_config, drive_state, vehicle state: error 404: not found. #14894

Closed
hlemmens opened this issue Apr 28, 2023 · 22 comments · Fixed by #14922
Labels
bug An unexpected problem or unintended behavior of an add-on

Comments

@hlemmens
Copy link

hlemmens commented Apr 28, 2023

2023-04-28 11:03:55.636 [DEBUG] [internal.handler.TeslaAccountHandler] - Invoking: vehicle_config
2023-04-28 11:03:55.815 [DEBUG] [internal.handler.TeslaAccountHandler] - An error occurred while communicating with the vehicle during request vehicle_config: 404: Not Found
2023-04-28 11:03:58.470 [DEBUG] [internal.handler.TeslaAccountHandler] - Invoking: drive_state
2023-04-28 11:03:58.654 [DEBUG] [internal.handler.TeslaAccountHandler] - An error occurred while communicating with the vehicle during request drive_state: 404: Not Found
2023-04-28 11:03:59.471 [DEBUG] [internal.handler.TeslaAccountHandler] - Invoking: vehicle_state
2023-04-28 11:03:59.655 [DEBUG] [internal.handler.TeslaAccountHandler] - An error occurred while communicating with the vehicle during request vehicle_state: 404: Not Found
2023-04-28 11:04:13.470 [DEBUG] [internal.handler.TeslaAccountHandler] - Invoking: drive_state
2023-04-28 11:04:13.653 [WARN ] [internal.handler.TeslaAccountHandler] - Reached the maximum number of errors (3) for the current interval (15 seconds)
2023-04-28 11:04:13.660 [DEBUG] [internal.handler.TeslaAccountHandler] - An error occurred while communicating with the vehicle during request drive_state: 404: Not Found- 

Expected Behavior

Current Behavior

Possible Solution

Steps to Reproduce (for Bugs)

Context

Your Environment

  • Version used: (e.g., openHAB and add-on versions)
  • Environment name and version (e.g. Chrome 76, Java 8, Node.js 12.9, ...):
  • Operating System and version (desktop or mobile, Windows 10, Raspbian Buster, ...):
@hlemmens hlemmens added the bug An unexpected problem or unintended behavior of an add-on label Apr 28, 2023
@theater
Copy link
Contributor

theater commented Apr 28, 2023

Just wanted to confirm that since today I have the same issue. Probably they have changed some endpoints or the structure of the response... :(

@theater
Copy link
Contributor

theater commented Apr 28, 2023

Probably this is related. Not sure if this repo is used as an API source: timdorr/tesla-api#711

@humphreysl
Copy link

<!-2023-04-28 11:03:55.636 [DEBUG] [internal.handler.TeslaAccountHandler] - Invoking: vehicle_config 2023-04-28 11:03:55.815 [DEBUG] [internal.handler.TeslaAccountHandler] - An error occurred while communicating with the vehicle during request vehicle_config: 404: Not Found 2023-04-28 11:03:58.470 [DEBUG] [internal.handler.TeslaAccountHandler] - Invoking: drive_state 2023-04-28 11:03:58.654 [DEBUG] [internal.handler.TeslaAccountHandler] - An error occurred while communicating with the vehicle during request drive_state: 404: Not Found 2023-04-28 11:03:59.471 [DEBUG] [internal.handler.TeslaAccountHandler] - Invoking: vehicle_state 2023-04-28 11:03:59.655 [DEBUG] [internal.handler.TeslaAccountHandler] - An error occurred while communicating with the vehicle during request vehicle_state: 404: Not Found 2023-04-28 11:04:13.470 [DEBUG] [internal.handler.TeslaAccountHandler] - Invoking: drive_state 2023-04-28 11:04:13.653 [WARN ] [internal.handler.TeslaAccountHandler] - Reached the maximum number of errors (3) for the current interval (15 seconds) 2023-04-28 11:04:13.660 [DEBUG] [internal.handler.TeslaAccountHandler] - An error occurred while communicating with the vehicle during request drive_state: 404: Not Found- Provide a general summary of the issue in the Title above -->

Expected Behavior

Current Behavior

Possible Solution

Steps to Reproduce (for Bugs)

Context

Your Environment

  • Version used: (e.g., openHAB and add-on versions)
  • Environment name and version (e.g. Chrome 76, Java 8, Node.js 12.9, ...):
  • Operating System and version (desktop or mobile, Windows 10, Raspbian Buster, ...):

I have exactly the same issue as here on my OpenHAB instance. Only started last night (27/4/2023 at 9pm UK time).

@thekev
Copy link

thekev commented Apr 28, 2023

Another confirmation here. A number of projects are scrambling to fix their implementations today.

@hlemmens
Copy link
Author

hlemmens commented May 1, 2023

It seems a new endpoint has been created by Tesla. See jonasman/TeslaSwift#138

Anyone able to implement thos in the binding?

@kaikreuzer
Copy link
Member

I just noticed that issues in the logs as well (didn't see this issue here the past days).
I'll have a look at what I can do - not sure yet, what impact the API changes will have on the functionality of the binding...

@openhab-bot
Copy link
Collaborator

This issue has been mentioned on openHAB Community. There might be relevant details there:

https://community.openhab.org/t/tesla-binding-updates-stopped-suddenly/146389/12

@kaikreuzer
Copy link
Member

I think I managed to fix it and have created #14922 for it.

@phuongpham
Copy link

I think I managed to fix it and have created #14922 for it.

Great! Will this fix work for 3.4.x as well?

@kaikreuzer
Copy link
Member

Once merged, I will check whether it is feasible to backport it to 3.4.x.

@kaikreuzer
Copy link
Member

@phuongpham You might want to test the jar that I attached to #14924.

@phuongpham
Copy link

@phuongpham You might want to test the jar that I attached to #14924.

great! I'm testing it now.
Will give you some update tommorow.
thanks for the great job!

@phuongpham
Copy link

@kaikreuzer ok it has been running for a while now.
Everything looks fine

@maisun
Copy link

maisun commented May 3, 2023

Is the jar only compatible with OH 4 or does it work with 3.4 as well?

@phuongpham
Copy link

phuongpham commented May 3, 2023

Is the jar only compatible with OH 4 or does it work with 3.4 as well?

You can download the snapshot for 3.4.x from here #14924
This one will work with OH 3.4

Or just run this command in karaf

bundle:update org.openhab.binding.tesla https://github.com/phuongpham/temp/raw/main/org.openhab.binding.tesla-3.4.4-SNAPSHOT.jar

@maisun
Copy link

maisun commented May 3, 2023

Is the jar only compatible with OH 4 or does it work with 3.4 as well?

You can download the snapshot for 3.4.x from here #14924 This one will work with OH 3.4

Or just run this command in karaf

bundle:update org.openhab.binding.tesla https://github.com/phuongpham/temp/raw/main/org.openhab.binding.tesla-3.4.4-SNAPSHOT.jar

Thank you! I just download and drop the jar file into add-on folder (before I removed the official Tesla add-on). Everything works again, many thanks for the fix!

@openhab-bot
Copy link
Collaborator

This issue has been mentioned on openHAB Community. There might be relevant details there:

https://community.openhab.org/t/tesla-binding-updates-stopped-suddenly/146389/14

@kojid0
Copy link

kojid0 commented May 5, 2023

First, thank you for fixing the binding! I've installed the jar and it started to work again.
The only thing I have trouble with is channel "shiftstate". It seems to be stuck at "D".
Any one else facing this bug?

@cauer71
Copy link

cauer71 commented May 6, 2023

also for me the channel eventstamp and shiftstare are not updated with the fixed version.
thx for the fast fix :-)

@phuongpham
Copy link

phuongpham commented May 6, 2023

also for me the channel eventstamp and shiftstare are not updated with the fixed version. thx for the fast fix :-)

I notice the same. At least everything else working :)
I also see this error in the log:

TeslaEventEndpoint-tesla:modely:fe75f569dc:VIN : An error occurred in the session : java.util.concurrent.TimeoutException: Idle timeout expired: 30001/30000 ms

@cauer71
Copy link

cauer71 commented May 9, 2023

with the released version 3.4.4 the channel eventstamp and shiftstate are broken

@kojid0
Copy link

kojid0 commented May 10, 2023

FYI, I created a new issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An unexpected problem or unintended behavior of an add-on
Projects
None yet
Development

Successfully merging a pull request may close this issue.

10 participants