According to https://github.com/markus7017/myfiles/tree/master/connectedcar there should be a channel called control_charge. There is no channel with that name in my installation. Also not when I activate “Show Advanced”.
Also, when looking at the docs, this and also the maxcurrent values are read only. But I also tried to set the current to i.e. 5 Amps, but this has no effect.
The should indeed be a channel called “charge” that should be able to be switched. Maybe you should post a screenshot of your visible channels (including advanced)?
Do other control channels work for you? For example the channel “climater”
For me the “maxCurrent” is a selection dropdown in the newest version that also works.
(I have a VW Passat GTE)
I will check if the climater control works later, because my car isn‘t sufficiently charged right now. But if I remember correctly, then the „normal“ VW cars use a different part of the binding compared to the ID cars. So maybe that is the reason why those things are not there or not working.
If you scroll up a bit I see an ID4 with much more control channnels. So I think it should works but somethings is wrong on your setup.
Another new Enyaq here, and I was looking forward to setting up this binding almost as much as I was looking forward to getting the car. 
Sadly, I am running into the same issues as so many others: first I got the thing online, but got only NULL values. Now, more recently, the bridge doesn’t even go online any longer.
I’m getting this in the trace logs when I enable the bridge (after a lot of other stuff):
2022-02-11 11:21:48.636 [DEBUG] [nectedcar.internal.api.ApiHttpClient] - Skoda-E: HTTP 404 Response: 404 Not Found: Requested route ('identity.vwgroup.io') does not exist.
2022-02-11 11:21:48.637 [TRACE] [nectedcar.internal.api.ApiHttpClient] - Headers:
Date: Fri, 11 Feb 2022 10:21:48 GMT
Content-Type: text/plain; charset=UTF-8
Content-Length: 71
Connection: keep-alive
Cache-Control: no-cache, no-store
X-Cf-Routererror: unknown_route
X-Content-Type-Options: nosniff
2022-02-11 11:21:48.637 [DEBUG] [dcar.internal.handler.AccountHandler] - Skoda-E: Initialization failed: API call failed
hello,
I tried this binding with my VW E-Golf. I tried the carnet account and weconnect. both say:
00:43:09.288 [DEBUG] [nnectedcar.internal.api.ApiHttpClient] - VW: HTTP POST https://identity.vwgroup.io
00:43:09.333 [DEBUG] [nnectedcar.internal.api.ApiHttpClient] - VW: HTTP 404 Response: 404 Not Found: Requested route ('identity.vwgroup.io') does not exist.
00:43:09.334 [DEBUG] [edcar.internal.handler.AccountHandler] - VW: Initialization failed: API call failed
00:43:09.334 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'connectedcar:volkswagen:2640fa560c' changed from UNKNOWN to OFFLINE (COMMUNICATION_ERROR): API call failed
Does this mean it doesn`t work with E-Golf? The we-connect app is working fine.
It seems that there is an issue again on VW side - I get the same error message. Usually, the eGolf works perfectly fine with this binding 
yes…the “API-Call failed” - Error is back again… 
And this time it’s not just over the weekend. Apparently something changed?
last message I got from my eGolf was on 12.02.2022, 10:01.
Before, it worked perfectly since september last year, with one break and similar symptoms as now: the bridge suddenly went offline. But last time it didn’t stay offline that long!
Same here vor VW - no update on thing / binding.
can confirm here as well… Volkswagen ID. Account (WeConnect) bridge error since 12-2
I did notice when logging in to the VW app I needed to login again and that it asked for some new permissions (acces to the driver licence info etc). Dunno if that is causing the issue?
not working here since 14-2… for WeConnect and WeCharge, both bridges offline with API error.
I assume problem is on VW side - when logging on to myVolkswagen the whole car is reported to have mobile online services disabled (whereas in WeConnect ID App on mobile phone everything is working and the car is online!)
It seems, that VW and Audi have actived a new feature which requires a “Release Consens” for providing data to third-party applications (like openHAB) ???
So I think, it is necessary to modify the binding…???
Same issue here. VW passat gte. No update since 12/02
Binding is dead for the ENYAQ now, offline both bridge and thing. I guess the binding needs a complete rework. Unfortunately @markus7017 is not responding anymore… kind of sad cause the binding really rocks (if it works)!
Im still here, but still have no time to work on this. Is there someone who wants to help on the code side?
I expect it’s all about authorizing the account.
VW, Audi, Skoda, Enyaq - all of them share the basic implementation. If VW makes a change all of them are affected.
Hi @markus7017 , great to hear you again :).
I offer my help and time, but I don’t have much experience in programming bindings. I have good Python and C++ knowledge, rather than html or Java. However, programmed my house in Java so it’s not too bad :). Happy to help where I can.
Cheers
Hi,
FYI I also have an installation of Home Assistant and there I have a integration to “Volkswagen We Connect” that is working fine. Perhaps it would be possible to get some ideas from that code.
It can be found at github
