Thanks again for the great integrations.
I use Volco Core and HACS integrations. The only thing I need from the HACS is “lock-controls and status”.
Will that be also in Core integration?
Has anybody experienced problems since updating to Core 2025.11? The integration worked perfectly before I updated, but after updating I got an error that I needed to re-authenticate. After that is asked me to re enter the api-key, but it won’t accept it. I keep getting the error “unable to retrieve vehicles”.
Is this an issue with the update, or is ther something else that I might be doing wrong?
Lock will be added in 2025.12. It’s already approved, but it didn’t make it into 2025.11.
3 Likes
Are you using your own application credentials? Try moving to the Home Assistant Cloud credentials. This gives you also the benefit of not having to re-authenticate every 6 days.
If it still fails, please enable debug logging, try again, disable debug logging, and upload the logs to https://www.dropbox.com/request/SdxkVf0OIWJCDjgcKtRj.
I didn’t need to fill in any credentials before. Ik just filled in my Volvo account details, and the api key, without any credentials (and I hadn’t even published yest, so I didn’t even háve credentials) and it worked!
So the question likely is why it worked in the first place!
I’ve nou published the application and tried to use that API key, but I get the same error.
Should I delete the integration and start from scratch?
I’ve uploaded the debug logs. I’m probably doing something stupid, but I hope you can help me out!
You probably don’t need to delete the integration.
There seems to be something wrong with the given API key:
2025-11-06 10:52:32.508 DEBUG (MainThread) [volvocarsapi.api] Request [vehicles]: GET https://api.volvocars.com/connected-vehicle/v2/vehicles
2025-11-06 10:52:32.809 DEBUG (MainThread) [volvocarsapi.api] Request [vehicles] status: 401
2025-11-06 10:52:32.809 DEBUG (MainThread) [volvocarsapi.api] Request [vehicles] response: {'status': 401, 'error': {'message': 'Access denied due to invalid VCC-API-KEY. Make sure to provide a valid key for an active application.'}}
2025-11-06 10:52:32.810 DEBUG (MainThread) [volvocarsapi.api] Request [vehicles] error: Unauthorized
Try to delete the Volvo API application and create a new one. You don’t need to publish it. Use the new API key in HA. Make sure not have any leading or trailing spaces.
If you have added a client id and client secret to HA from the now deleted Volvo API application, then also remove it from HA. Use the Home Assistant Cloud credentials when asked.
Thanks, I’ll try that!
Do you have any idea why it won’t accept that api key anymore? It worked fine before yesterday…
Creating a new api key worked! I tried that oned before, but on my phone. No I did it on my pc and this time it worked.
First time around I also needed tot authorise from my pc instead of my phone…
Thanks again!
I get to this point on the installation and it stopped. I am using the hacs version,
I’d like to get the official to install, but can’t get past this point.
I’ve tried generating new keys, etc with no luck.
Thanks, Craig
That error message appears when you are trying to add an already existing vehicle (VIN).
Make sure to remove all integration entries first (both HACS and core), and then try again. Preferably with the core integration. The HACS version will be abandoned very soon.
Ok, I removed the Hacs integration and still have the same error.
Can I delete the cloud connection as I do not have the core one installed?
I had it once and deleted it, but am trying the core again…
It’s probably the core integration then. You don’t need personal application credentials, just an API key. In fact, using Home Assistant’s provided application credentials is strongly recommended.
I would try to delete everything that is Volvo and Volvo Cars related. And then start again from there.
Ok, I did that and deleted my Volvo developer account. I created a new account with the same username and it wouldn’t get past the API key saying there were no VINs. I added and API key and got the same error.
I feel like somehow the cloud connection is not cleared.
We’re getting somewhere I think! When the integration brings you to the Volvo sign in page, you need to fill in the same credentials as you use for the Volvo app (and not those of the developer account). Then you should be able to select your vin.
After deleting the HA link in Volvo, then using the integration install for volvo using my app credentials, I get the permissions approval and we are good.
After entering bogus API key:
After entering real key:
Can you perform the following steps, please?
- Remove all existing Volvo entries (both HACS and core).
- In
Settings > Devices & servicesthere should be nothing Volvo related. - In the
Application Credentialsoverview (accessible through the 3 vertical dots on theDevices & servicespage) delete everything Volvo related. - Reboot HA.
- Follow the steps exactly as outlined on Volvo - Home Assistant to add your Volvo.
If you still run into the same problem, you’ll need to enable debug logging. This will need to be done in configuration.yaml as you don’t have a working integration entry.
It should look something like this:
logger:
default: info
logs:
homeassistant.components.volvo: debug
Reboot HA again, and try to add your Volvo. Then upload the logs to https://www.dropbox.com/request/SdxkVf0OIWJCDjgcKtRj.
Afterwards undo your changes to configuration.yaml and reboot HA.
1 Like
Now I get to say, “Oops, my bad…” While going through the steps you outlined it told me that the Volvo app was disabled… I went and found it to enable and all seems to be working… On another note, do I need to publish the app on the Volvo developer portal?
Great to hear it’s all working now! No, you don’t need to publish the app on the Volvo developer portal.
Just curious - do you think it will be possible to make this work?
I really liked it because I could have a check as part of an automation to make sure the car had started as requested. I had it in the “start car” automation so it would start the car, then wait like 3 minutes, then confirm it the engine was running. It was also nice to have the alert if the engine started when the garage was closed.