API Availability #71
Comments
|
Tried some stuff and it's similar to the VoC API we are using. Biggest differences are:
From an XC40 I retrieved the following resources: |
|
I tried some of our requests as well on the new api, like /preclimatization/stop but they really do not work (yet)... Additionally, I also tried the /resources call on the VoC API to see what resources are supported in a car, but that doesn't work either... |
|
Hi
Sending commands to your Volvo is not (yet) implemented in the Extended API specification.
That has worked for me always, but you need the correct authorization. I created a Node Red flow to read the data for Domoticz, but with some modification this can of course be used by any other Home Automation system, that supports MQTT or a HTTP call. More information is available at: https://www.domoticz.com/forum/viewtopic.php?f=38&t=26549&hilit=connected+cars&start=60, starting March 9, 2021. Another developer has in the same period created a native Volvo application. The biggest problem, we have is that Volvo does not respond to our request of providing a valid key for permanent use. However you are invited to test the Node Red flow and see if it is possible to modify for your OpenHAB (as I believe you use). |
|
I have a new Android based Volvo and the old VoC API does not work for this car (yet?) It just says "vehicle not found". |
|
Correct, same for me. Android received an update though which supposedly fixes it. Screens totally change in the app, so I kind of expect the app might take a different route too. When I select the XC40 plugin hybride, it works fine and the old screens are back. With the P8 the screens are different again. In my case much doesn't work yet, because it also requires an OTA in the car which is released / rolled out depending on VIN and I have not yet received it... |
|
Good to know, I added the new P8 (XC40 Pure Electric) to my Volvo Oncall account and it does not show up in the vehiclelist. As you can see from the screenshots it's an entire different look and feel, and I expect they have also switched from the voc api to the new connected-vehicle API (not extended-vehicle API): See also the following json: |
|
Do You plan to integrate this api or not? |
|
Hi all, For those interested in these API's. I implemented both the Extended Vehicle API and the Connected Vehicle API for my Volvo in Node Red and prepared the interface to Domoticz using MQTT. As I may guess, the Extended Vehicle API is targeted to companies, which has a fleet ownership, such as leasing companies and perhaps also assurance companies. This API is only capable of reading sensors and has no possibility to send commands to the car. I guess, that the Connected Vehicle API is targeted to car owners and sooner or later will replace the old Volvo on Call API, as used by the Volvo on Call IOS and Android app. This API supports commands to the car. (It has been tested and it works). If this happens the Python script of molobrakos will also stop functioning. As another developer, who created a native component for Domoticz with the Extended API, tried to get contact with Volvo has been asked to submit a business plan. etc, I guess that the Extended API is targeted to companies and the Connected API to individuals. Unfortunately the Connected API is in early beta stage and I have no idea how to get a permanent authorization to access my car. If someone is interested in the flow, let me know. Regards |
|
Ok, I am interested in the mqtt / NodeRed. |
|
It should be possible to simple show all values above in the app on the central display, right? |
|
Hi all interested users, As already mentioned above in this thread, Volvo has published a Volvo Extended Vehicle API. The Node Red flow has been published there as well, but you also can find it at: Full documentation about the Extended API, you can find at: Very recently, Volvo has also made available a Volvo Connected Vehicle API, which is currently in early beta. Full documentation about the Connected API, you can find at: Remember that both API's are in (early) beta stage. Regards |
|
Hi, |
|
Hi, @elestedt Where did you find that information? I did not received any mail, nor saw it in the, now called, Volvo Cars app. Regards |
|
I have no idea. But I can try to find out. I got emails because I was a user of the old side and android app. I have no idea if the API will be shut down as well - it's just a guess and that if things stop working during this week - we all know why. If it doesn't stop working, that's great. |
|
The mail is in swedish, but here is the content: |
|
Has nobody an technical contact to Volvo to solve the key problem? |
|
Wrote to openinnovationportal.swe@volvocars.com that is available on the https://developer.volvocars.com/volvo-api/connected-vehicle/, but no response. Using the API does not return other results other then Vehicle List & Details. Have XC60 2022. |
mattiaskagstrom
added a commit
to mattiaskagstrom/core
that referenced
this issue
Dec 23, 2021
Added the externalTemp resource. I haven't tried running the change since i don't know how. but the added resource name is based on this: molobrakos/volvooncall#71
22 tasks
|
I have been trying to get in contact with Volvo for 6+ months now. They won't "accept" my request to make my own "application" published. Has anyone else had success in solving the 1hr expire demo-key problem for your vehicle? Or getting an published application accepted? |
Can you share the legal disclaimer used in the intake? |
|
The ioBroker guys did the job... perhaps an inspiration? |
|
Hi, Have you been able to generate a key, which last longer than 1 hour? Because that was the problem in the past. Volvo Extended Vehicle API and Volvo Connected Vehicle API existed for about 2 years. Regards |
|
My 2cts... use Selenium to emulate the clicks going into the portal and (re)generate the 1 hour tokens when you need them... |
|
As I assume while reading, they used an alternative way of authorisation. |
|
I don't think there is a way to get a token that lasts for more than 1 hour. According to https://developer.volvocars.com/apis/docs/authorisation/ you have to refresh the token (section 3) |
|
It's the same oath2 authentication as described in the API. No clue where they got the key from but I assume it was somehow found in the current Volvo On Call app. Use that key and it works fine. Make sure to refresh the token and do not regenerate it all the time as it has weird results. Check my sample code here: I've been using it for a few weeks and it works great 👍
|
|
While reviewing the HASS MQTT plugin code I noticed they have location too! I hadn't realised/noticed it yet, but also published the location API: Regards, Nika. |
|
Hello @nikagl , Nice that this has been added to the collection of API's. Question. Have you been able to solve the 1 hour expiration of the key or did you find a solution to refresh the key? Regards |
|
Yes, read the post above and check my code, it works with the authorization code that was part of the iobroker |
|
Not sure what Home Automation you use, but several have plugins already. Depending on the language you want to use i have provided several examples on my repo as well. Javascript, python and DSL rules of OpenHAB. For instance getting the token with python is as follows:
|
|
Hi! Maybe someone can tell me, which Nodes palette in NodeRed is missing for the two config nodes (I am not using Domoticz, so I think I only need the left one)? Thanks a lot!!
|
|
Hello @toogitter, You asked:
The 2 nodes used in my flow are: "node-red-contrib-config¨ However I do not use this contrib node anymore, as I prefer as much as possible to use default available core nodes, although this node still works. This node can be replaced by an "Inject" node followed by a "Change" node, as follows
The complete flow for these 2 nodes:
Be aware that this application once has been made for the "Connected" API, version 1. Note also that this configuration requires you to copy the data from the Volvo developer site into the Change node. If you need more info, please ask. Regards |
|
@FireWizard52 I have a question, how do I fix a authenticationsoultion that doesn't expire in 1 hour? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Not really an issue, but I saw Volvo published their API:
https://developer.volvocars.com/volvo-api/extended-vehicle/
The text was updated successfully, but these errors were encountered: