Hi All, was wondering if anyone had worked out how to toggle the reduced charging setting in a vwID3 via this binding. Its possible from the app so not sure if its available in this binding. Cheers James
English Version: (thanks for telling me)
Well, Iāve copied the jar file into my Openhab addon Folder, running on a Raspberry.
By connecting through a webbrowser to the openHAB interface, I was able to select de bridge. Unfortunately, when entering my credentials, I was given back an API Error in return (see screenshot). Is there something to authorize on the volkswagen.io page fir third party apps?
Thanks
My Car is a VW ID.3 Model.
Hallo,
Ich kenne mich noch nicht so gut aus mit den ganzen Bindings, Things und Items.
Ich habe das aktuelleste Binding (jar Datei) Ć¼ber smb Service in den Addon Folder der Rasp-pi gesetzt und konnte dann Ć¼ber die openHAB(3.2) Grafik OberflƤche im Browser das Thing installieren. Jedoch bekomme ich (wie im Screenshot) immer einen API Fehler. Username und PW sind die gleichen, mit denen ich mich auch bei volkswagen.io einloggen kann?
Muss ich irgendwie wegen API noch was bei VW freischalten?
English please, this is an international community !
thanks, done
Which jar file did you copy ??? Original from Markus ? If so, you got the wrong one. There is a patched version available here
Edit:
Problem 1 solved, by restarting RasbPi.
Edit 2: Wallbox Problem solved
I never logged in to the Elli Webshop Portal, mainly coz I bought the ID.Charger from my VW Dealer. So, I logged into the Elli Webpage, with same credentials as for the ID Portal. Logged into the ID Portal and under āconnceted Appsā is now listed the Elli Webshop. And that was enough to get the Connected Car Wallbox Bridge working (ONLINE).
Hi,
I deleted my jar file (it was a 3.2.0 Snapshot from 20220225) and reinstalled it from github (the patched from your link). Now, the bridge (Volkswagen ID Account) is working. Thanks
Then I added the Thing (VW ID vehicle) and it is Online. Fine.
Now, for the items, Iām lost because my Channel list for the Thing does not show up and is empty.
It keeps saying āThis thing has no channels. Either the thing type doesnāt define channels, or they may be detected and appear later.ā Maybe just wait for it?
By the way, I have same problem then other users here for the Id.Charger bridge. When trying to install the bridge (ID.Charge Account) I use the same user/pw combi as for the We.Connect bridge (ID Account).
The message here is: COMMUNICATION_ERROR Missing localtion on redirect
Anybody willing to help or giving me links to documentation? Many thanks.
I had the same issue (with Skoda Enyaq).
Logging out and in of the Skoda App solved the problem for me.
Hi, I think it is not possible to control charging e.g. with MaxChargingCurrent. My ID3 provide only āreduced ACā (with 5 kW) and āfull ACā (with 11kW, max of my wallbox). Therefore I think the API is not able to control in smaller steps like think MaxChargingCurrent (5 amp, 10 amp, 13 amp, ā¦) suggests.
Maybe SKODA or other has this possibilty.
Btw. @markus7017 and @tknaller thanks to get the binding running again. Top.
1 Like
@tknaller +1
1 Like
@tknaller thanks for the updated version. Now i can switch off the climate controll but still not able to switch it on. Not sure what āsettings are missingā?
2021 e tron
2022-03-19 13:00:50.172 [DEBUG] [ar.internal.handler.ThingBaseHandler] - WAUZZZGE0MB027113: Channel climater received command ON
2022-03-19 13:00:50.174 [DEBUG] [tedcar.internal.api.carnet.CarNetApi] - WAUZZZGE0MB027113: Sending action request for rclima_v1.P_START_CLIMA_EL, reqSecToken=false, contentType=application/vnd.vwg.mbb.ClimaterAction_v1_0_0+xml;charset=utf-8
2022-03-19 13:00:50.175 [DEBUG] [nectedcar.internal.api.ApiHttpClient] - WAUZZZGE0MB027113: HTTP POST https://fal-3a.prd.eu.dp.vwg-connect.com/fs-car/bs/climatisation/v1/Audi/DE/vehicles/WAUZZZGE0MB027113/climater/actions
2022-03-19 13:00:50.176 [TRACE] [nectedcar.internal.api.ApiHttpClient] - Headers:
Accept-Encoding: gzip
User-Agent: okhttp/3.11.0
X-App-Name: myAudi
X-App-Version: 3.9.1
Content-Type: application/vnd.vwg.mbb.ClimaterAction_v1_0_0+xml;charset=utf-8
Accept: application/json, application/vnd.vwg.mbb.ChargerAction_v1_0_0+xml,application/vnd.volkswagenag.com-error-v1+xml,application/vnd.vwg.mbb.genericError_v1_0_2+xml,application/vnd.vwg.mbb.RemoteStandheizung_v2_0_0+xml,application/vnd.vwg.mbb.genericError_v1_0_2+xml,application/vnd.vwg.mbb.RemoteLockUnlock_v1_0_0+xml,application/vnd.vwg.mbb.operationList_v3_0_2+xml,application/vnd.vwg.mbb.genericError_v1_0_2+xml,*/*
Accept-Charset: UTF-8
Authorization: Bearer eyJraWQiOiJNQkIwMSIsImFsZyI6IlJTMjU2In0.eyJzY3AiOlsiZmFsIl0sInN1YiI6Imp6SXNoYmFRVHJNSVBtQ2lCT2xlVWdCenJKSyIsInZlciI6IjEiLCJjb3IiOiJERSIsImlzcyI6IlZXR01CQjAxREVMSVYxIiwiY250IjoiNzc4NjllMjEtZTMwYS00YTkyLWIwMTYtNDhhYjdkM2RiMWQ4IiwiY2NoIjoiYXBwIiwidHlwIjoiQVQiLCJzeXMiOiJYSURfQVBQX0FVREkiLCJzdHlwIjoiVDIiLCJhdWQiOiJtYWwucHJkLmVjZS52d2ctY29ubmVjdC5jb20iLCJ0bnQiOiJBdWRpLERFRkFVTFQiLCJleHAiOjE2NDc2OTM4ODcsImlhdCI6MTY0NzY5MDI4NywicnQtaWQiOiIxNTUyMjQyYi0yMzg3LTQ4ZjEtYjYxYS00ZTIxZWJhMWNiMjMiLCJqdGkiOiJkZmRjYjA3OS0xOWM0LTRiMTgtOTkzNy03ZWRlMzMzMzBlNWMifQ.UgdirkrBuhr7wB4XGTsI6yNb-yMucD3peVTDD7e_-npqxjKbdVJbmE80fXRONWqDwErG1jPLRMkEs22xsrO64tyS9MhSfq5ita0bAV_BsaFHpcM0gdGXtG1DnHfIU7MP-_Xv9BXKHc2CPXs9sR1Dny2XA9IPxBHWeLB_yc_YJSe7XaUk8RSZlPLkjyUsdAOKn7NDvO42Ms4lYgGMpcovGuFBPDx9EOD8y5pX3TxL-SMR1NPh_xAt9rt2Jdccn04lgR_I6xNZm3hwu4_MJ3XA-tpLT_hMoThLyYmULSIi24qhimk-Z9bYWRQGpPKilHkoodyGYt7lQdj9nVDLWHU3PA
Host: msg.audi.de
Content-Length: 87
2022-03-19 13:00:50.177 [TRACE] [nectedcar.internal.api.ApiHttpClient] - Body/Data: <?xml version="1.0" encoding="UTF-8" ?><action><type>startClimatisation</type></action>
2022-03-19 13:00:50.330 [DEBUG] [nectedcar.internal.api.ApiHttpClient] - WAUZZZGE0MB027113: HTTP 400 Response: {"error":{"errorCode":"climatisation.bs.invalid-parameter","description":"invalid parameter : 'settings are missing'"}}
2022-03-19 13:00:50.332 [TRACE] [nectedcar.internal.api.ApiHttpClient] - Headers:
x-fault-id: f5e7802d-d5bb-44fe-af2a-27bc20850c15
X-FS-Tracking-ID: 871cbbab-c04b-4650-a52a-5e01ae0c526d
X-FS-Error-Code: GW400
Content-Type: application/json
Content-Length: 119
Date: Sat, 19 Mar 2022 12:00:49 GMT
Connection: close
Server: www
2022-03-19 13:00:50.333 [DEBUG] [nternal.handler.CarNetVehicleHandler] - WAUZZZGE0MB027113: Action startClimater submitted, initial status=rejected
one would need to sniff that from the app from a smartphone with a fiddler proxy to find out - for my enyaq sending on and off commands to control_climater channel works, just the switch connected to the item sometimes has the wrong state
Great work!! Just like to ask again if itās intend on plan to integrate Fiat uConnect into this general ConnectedCar Binding? And while Iām waiting for second EV, Kia also would be great 
Cheers,
int5749
@INT5749
If you need data from all car manufactures you have to use ioBroker native or pushing in via MQTT where all vehicles and brand are supported
Hi, what kind of apps do you use for the id charger ? I still do. To get any connection to the wall box bridge even not by using the Elli app or die we connect id app. In both apps everything is working fine and I can see my cars as well as the link to Elli Webshop. Thanks for your answer
Do you know if there is a way via the binding to switch between reduced and full speed (on my 7kW charger reduced is 2.4kw and full is 7kw)?
Some days before I get carnet stops work. In log is this API errors. VW changes API?
2022-04-13 10:18:06.830 [WARN ] [dcar.internal.handler.AccountHandler] - message.init-fialed: 98fcc4b7e9
org.openhab.binding.connectedcar.internal.api.ApiException: API call failed
at org.openhab.binding.connectedcar.internal.api.ApiHttpClient.request(ApiHttpClient.java:200) ~[?:?]
at org.openhab.binding.connectedcar.internal.api.ApiHttpClient.post(ApiHttpClient.java:111) ~[?:?]
at org.openhab.binding.connectedcar.internal.api.IdentityOAuthFlow.post(IdentityOAuthFlow.java:121) ~[?:?]
at org.openhab.binding.connectedcar.internal.api.ApiWithOAuth.login(ApiWithOAuth.java:111) ~[?:?]
at org.openhab.binding.connectedcar.internal.api.IdentityManager.createAccessToken(IdentityManager.java:103) ~[?:?]
at org.openhab.binding.connectedcar.internal.api.ApiBase.createAccessToken(ApiBase.java:204) ~[?:?]
at org.openhab.binding.connectedcar.internal.api.ApiBase.fillAppHeaders(ApiBase.java:200) ~[?:?]
at org.openhab.binding.connectedcar.internal.api.ApiBase.callApi(ApiBase.java:130) ~[?:?]
at org.openhab.binding.connectedcar.internal.api.carnet.CarNetApi.getVehicles(CarNetApi.java:199) ~[?:?]
at org.openhab.binding.connectedcar.internal.handler.AccountHandler.initializeThing(AccountHandler.java:173) ~[?:?]
at org.openhab.binding.connectedcar.internal.handler.AccountHandler.handleConfigurationUpdate(AccountHandler.java:199) ~[?:?]
at org.openhab.core.thing.internal.ThingRegistryImpl.updateConfiguration(ThingRegistryImpl.java:94) ~[?:?]
at org.openhab.core.io.rest.core.internal.thing.ThingResource.updateConfiguration(ThingResource.java:498) ~[?:?]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
As of today, I see no such trouble on my end, with binding version 3.2.0.202202230038. What version of binding you are running on? Maybe re-authorization towards VW is required?
Update to snapshot 20220225 solve this.
Any chance of getting the Jaguar / Land Rover API integrated? API info is here: Jaguar InControl API