Someone that really uses EVCC can check if all conditions need are considered on my test configuration.
Dear Thomas, I have installed your Volvo integration in homeassistant. At first I did not understand how to copy the api key, but now it is functioning fine. Nice integration.
My api interval was initially set on 135 seconds. I did not change that.
After a few day I wanted to access my car and that was not possible because the start-battery was empty. The car was completely dead. No warning from the VOLVO app.
The question is why was my startbattery was totally empty. The volvo assitance (realised by the ANWB) measured 3.8 volt in the battery, crazy low, never saw that before.
Mayby the api interval of 135 seconds was too short?
There is another possiblity. Often I leave the ACCU cable for the hybrid battery permantly connected. That also maybe the reason why the start battery was not charged by the hybrid system.
AT the VOLVO dealer I have heard that its possible to read out the voltage of start battery. That one is missing in your list. Is it possible to add that voltage to your integration? It would bij nice to monitor that voltage and generate a message when it gets too low.
@thomas_be @rubinox355
If I want to use this automation that optimises the API calls, how do I then disable the API calls in the integration? I simply put the 135 sconds to 0?
Thanks for your advise.
JanN.
Battery issue cannot be caused by the integration. Please read https://github.com/thomasddn/ha-volvo-cars/issues/18#issuecomment-2572636277 (and the rest of the thread) to learn more about this topic.
Do not lower the interval, I even think 135 is the lowest value you can enter.
Executing the action will reset the current active interval. So each time the automation is run, the 135 seconds start counting down again.
Forgot to mention that there is no API that returns the 12V battery state.
Put a value higher than your manual refresh.
If you will make one update per hour (3600) put the default refresh as higher like 7200.
You indeed can’t put it to 0. I set it to 3600 (which seems to be the maximum). Together with the optimization automation from @rubinox355 the number of API call still remains well below 10K.
@thomas_be forgot to mention and thank you for your work on this great integration. I come from the MQTTVolvo one and this is more than an outstanding alternative.
1 Like
thanks, at the dealer they told me they have that possibility of monitoring the start- battery power. I am not sure if that is true
I will now use a seperate Bluetooth meter on the battery to check it
No, the actual charging speed is not available in the API.
What will be available in a later version is the configured target battery level and the configured ampere limit.
1 Like
It’s possible that they have access to more sensors than we do. The official app can also do stuff that is not available in the public API.
1 Like
Ok clear, thanks for your answers (and integration of course)
Thank you Thomas for this work ! It’s working perfectly with my XC90 T8 Plug-in hybrid.
Would it be possible to initiate the charge from the API ? Use case, I plug my car to the charger but I would like to initiate the charge only if the Electricity Rate is at night rate (after 10PM and during weekend).
Thank you
Nice to hear you are enjoying the integration!
The API does not support managing charging sessions. If there is an integration for your charger, you could use that to start and stop charging.
1 Like
Love the integration. Works really nice except the login seems to expire after a few hours which means that every day i need to provide my login details to re-activate the Integration.
People have reported this before. One cause is having the number of API requests going over 10.000 per day. Can you check that please?
Otherwise I would need the debug logs so I can investigate. Enable debug logging and wait for it to happen again. Then provide me those logs.
Also see Authorization Expired · Issue #128 · thomasddn/ha-volvo-cars · GitHub.
Just wanted to say thank you for this integration! Unfortunately it doesn’t seem to work in Australia 
2025-04-04 20:58:18.797 DEBUG (MainThread) [custom_components.volvo_cars.volvo.api] Request []: GET https://api.volvocars.com/connected-vehicle/v2/vehicles/**REDACTED**
2025-04-04 20:58:19.674 DEBUG (MainThread) [custom_components.volvo_cars.volvo.api] Request [] status: 404
2025-04-04 20:58:19.675 DEBUG (MainThread) [custom_components.volvo_cars.volvo.api] Request [] response: {'error': {'message': 'NOT_FOUND', 'description': 'Does not belong to allowed markets'}}
2025-04-04 20:58:19.676 ERROR (MainThread) [custom_components.volvo_cars.coordinator] Unable to retrieve vehicle details
And yep, looking at the Volvo API documentation, Australia and New Zealand are not listed!
I’d love to know why all those countries get access to the API but Aussies and Kiwis don’t
Aaw, I feel your pain! 
No idea why it’s not world wide available.
Glad to hear you are picking up the Amp limit and target battery level! These could be the most useful API’s to put into an automation to optimize power usage.
1 Like