We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug When I click on the button for open trunk in ioBroker, nothing happens. Only the following error message appears:
{"response":null,"error":"Tesla Vehicle Command Protocol required, please refer to the documentation here: https://developer.tesla.com/docs/fleet-api#2023-10-09-rest-api-vehicle-commands-endpoint-deprecation-warning","error_description":""}
tesla-motors.0 2024-01-14 15:27:45.358 error AxiosError: Request failed with status code 403
tesla-motors.0 2024-01-14 15:27:45.357 error https://owner-api.teslamotors.com/api/1/vehicles/929890198683643/command/actuate_trunk
However, data from the Tesla is retrieved and displayed, so the connection must be there
Greetings
Holger
The text was updated successfully, but these errors were encountered:
See here #93
Sorry, something went wrong.
is there a solution in sight?
No branches or pull requests
Describe the bug
When I click on the button for open trunk in ioBroker, nothing happens. Only the following error message appears:
{"response":null,"error":"Tesla Vehicle Command Protocol required, please refer to the documentation here: https://developer.tesla.com/docs/fleet-api#2023-10-09-rest-api-vehicle-commands-endpoint-deprecation-warning","error_description":""}
tesla-motors.0
2024-01-14 15:27:45.358 error AxiosError: Request failed with status code 403
tesla-motors.0
2024-01-14 15:27:45.357 error https://owner-api.teslamotors.com/api/1/vehicles/929890198683643/command/actuate_trunk
However, data from the Tesla is retrieved and displayed, so the connection must be there
Greetings
Holger
The text was updated successfully, but these errors were encountered: