I used the old API before and yesterday I switch to the new, works! But not Engine_start as a command.
I get this error “JSON parse error: Unrecognized token 'object: was expecting (JSON String, Number, Array, Object or token ‘null’, ‘true’ or ‘false’)”.
Any idea?
Will take a look. I can’t use that API on my car, so it is untested.
There is a new test version; please try it out. Attempts to fix the start engine command.
Worked great! Fantastic!
Hi everyone,
First of all, big thanks to Richard_B of the Volvo on Call / Connected Cars app for Homey – I just set it up and I can now see my EC40 in Homey. Super cool!
Really appreciate the work that has already gone into this app! 
Great app, but I have to repair it every few days and authenticate myself, because it stops working.
Any clues how to solve this?
I have had some issues last few days.
The climatetization start and engine start stoped working on both of my cars.
The location of the cars in homey changes as usual so there is no problem with the connection or the API?
Any Idea what it might be?
I used the Homey Oauth2 app for the Oauth2 part, and thought this covered all bases … it clearly seems that is not the case. I will have a look at what needs to be done.
Good afternoon, I can no longer open and close the car from Homey. And the location only updates intermittently. Could this be due to the app or Volvo? Repairing the device doesn’t help.
New test version, looks promising. The car is still available three days later.
Thanks, just installed it. Will see.
Just to be sure, I don’t have to enter the VCC API-key anywhere?
You still need a VCC API key, but if you’ve entered one before, it will still be there.
And when speaking of the de…. I just got the OAuth2 error on my car 
I haven’t entered a API-key and it’s working. Just authenticated it via the Volvo site.
I have an API with test credentials on the Volvo Site, and I used authentication with my “real” credentials on the volvo site.
Hi,
Do you believe the OAuth-problem is on Volvos part or the app?
Best,
Zack
I’m uncertain about the current version. We aren’t using their authentication as intended because we share the client ID and secret, but use different VCC API keys. If you encounter an expired token, it might help to send me a diagnostic report.
I have only encountered an expired token once with the current version, and it was just after I upgraded the firmware on my EX30. Coincidence or not 
Device Unavailable
OAuth2 session has expired. Please repair the device to re-authorize with Volvo…….. and after authorize it is gone again after half a day
Half a day with the current version of the app sounds strange, but … me and Claude did another attempt and it seems there may be problem with using the refresh token if there is connectivity problems. So if your home network is very spotty then maybe this could cause problems continously.
Good morning,
My EX30 just became unavailable again.
App V1.5.6
21f2dbf5-98b2-445d-980d-f33b4a7d744f
Haven’t had an issue for weeks now.
But yesterday I turned off wifi to replace my modem. (While my volvo was on wifi)
And my volvo now fails roconnect.
Just did a re-auth
So re-connect issue? Yes that might be the case
