-
-
Notifications
You must be signed in to change notification settings - Fork 9
Cant remote start the engine #32
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
Comments
It's a shortcoming of the public Volvo API. We need to use a certain scope, but we're not allowed to use that scope. I mailed to Volvo mid December, but no response so far. |
Engine buttons will be removed in the next release. |
Hi |
@snp88 Your car probably doesn't support the climate endpoint. |
can you give more details, i could swore volvo2mqtt had ability to start, also developer api docs mention engine start stop |
The API indeed mentions the start/stop engine, but it requires the use of a certain scope. However, the API user I’m using (the same as volvo2mqtt) is not allowed to use that scope. This means we’re unable to use that endpoint. |
This reverts commit e3d6c00.
This reverts commit e92a128.
Uh oh!
There was an error while loading. Please reload this page.
What happened?
Hello!
I try to start the engine on a XC60 PHEV MY24 with the remote start button from the integration but I get an error all the time.
I get an popup in the button of Home Assistant that states:
"Couldn't perform the action button/press, unknown error"
I saw this in the debug log (complete below):
aiohttp.client_exceptions.ClientResponseError: 403, message='Forbidden', url='https://api.volvocars.com/connected-vehicle/v2/vehicles/YV1UZH5V3R1793016/commands/engine-start'
I have the latest 1.0.2 release of the integration and Home Assistant is on 25.1.2.
Any ideas? All other entities works, like the climatization start has no problem.
Br
Fredrik
API availability
OK
Car connection
Available
Installed integration version
1.0.2
Additional information
No response
Diagnostics
The text was updated successfully, but these errors were encountered: