Hi,
Just installed Volvo on call and I added my VCC API primary key.
When trying to add the car I receive this message « token refresh failed »
Any idea?
Hi,
My car just got unavailable again (I think it’s once a week or so by now) and I sent in a log if it’s of any help: 07e398bf-7916-4405-b2e6-f3b1df73ffb4
all the best
1 Like
My cars become unavailable approximately every 6 hour… 
Is there a solution to this? I have to login with my volvo ID credentials to have them online again for about 6 hour
As you may have noticed, there have been several releases attempting to solve the problem, the most recent one being yesterday. If it were an easy problem to fix, it would have been resolved by now. I appreciate the diagnostic reports some users send me, but even with those, it is hard to understand what is happening. We have a refresh token that is supposed to be valid for a certain period, but then it suddenly becomes invalid. I still appreciate getting the diag reports; the latest version has even more logging.
As I mentioned before, we are using the client ID and secret from one account (mine) and the VCC API key from everyone’s account. This is not the intended usage and might be the reason for the issues we are facing. Feel free to encourage Volvo to allow my Easee app registration to make a large number of API calls per day so that we can use the official client ID/secret/VCC API key setup. They didn’t bother replying to my email.
3 Likes
Richard. It doesnt matter if you manage to solve this or not. We still appreciate all the work you put into this. Thank you 
I agree with Albin. Thanks a lot for the time and dedication you put in to this. 
My car became unavailable approximately 1 week after the new update: 60ddd627-9128-47d5-b9d7-e6f7685fad70
Wanted to install on HP23, but encountered this::
{“code”:429,“error”:“too_many_requests”,“error_description”:“Too many requests.”}
