Are you sure, that your logon data (userID, Passwd) is correct?
I’m running 3.1 on rpi4 and getting a warning, too. But a diffenrent on:
2021-02-27 20:05:25.602 [INFO ] [econnect.internal.VWWeConnectSession] - Attempting to log in to https://www.portal.volkswagen-we.com
2021-02-27 20:05:34.414 [WARN ] [econnect.internal.VWWeConnectSession] - Error code or JSON is null or empty on POST: url https://www.portal.volkswagen-we.com//portal/delegate/dashboard/xxxxx/-/rah/get-status, response {"errorCode":"2","timerCount":3}
==> /var/log/openhab/events.log <==
2021-02-27 20:05:36.968 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'vwweconnect:vwweconnectapi:c2f1483569' changed from UNKNOWN to ONLINE
2021-02-27 20:05:37.890 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'vwweconnect:vehicle:c2f1483569:24656b7cb0' changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
2021-02-27 20:05:37.894 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Arteon_TotalTripDistance' changed from 119.0 km to 0.0 km
2021-02-27 20:05:37.897 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Arteon_TotalDuration' changed from 488 min to 0 min
2021-02-27 20:05:37.900 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Arteon_Location' changed from 52.00,10.000 to 52.0,10.0
2021-02-27 20:05:37.903 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Arteon_Temperature' changed from 5.0 °C to 0.0 °C
2
I can read the data / items from we-connet, but I can’t start teh remoteHeater:
2021-02-27 21:05:18.169 [WARN ] [.internal.handler.VWWeConnectHandler] - Failed to send https://www.portal.volkswagen-we.com//portal/delegate/dashboard/xxxxxx/-/rah/quick-start to the vehicle WVWZZZ3HZME501921 HTTP response: 302
2021-02-27 21:05:18.174 [WARN ] [.internal.handler.VWWeConnectHandler] - The vehicle xxxxxx failed to handle action remoteHeater true
Hi @jannegpriv , sorry for my delayed answer. In the meantime it worked sometimes and sometimes not, now it is working fine, I think it cause by VW.
Strange was only, that the binding and the WeConnect Appl was getting actual data, but activating remote heater was not possible.
This binding will be based on the Web API since I’m able to easily reverse engineer it, I’ve not been able to do that for the app API due to certificate pinning, but I think that Markus has succeded in doing that.
For the moment I have no plans for making the binding official but I will continue to support it. I hope that Markus binding in the future can be developed to support both Skoda, VW, Audi, one binding to rule them all
Please see my comment on github. Since openHAB 3 has removed support for org.apache.commons*, your Binding does not start any longer. Tested with openHAB 3.1 M3.
Would it be possible to update to apache.commons 3 ???
I’m still running 3.0.1 in my sandbox but I can make a try to upgrade the coming week-end so that I have somewhere to test it besides my Eclipse environment, I’ll keep you posted!
I think that it is maybe better to have one binding to rule them all, there is another binding that uses the App API that @markus7017 is developing, that also could be ported to support VW.
But I will continue to support this binding.
Hmmm, as far as I understood, the Carnet API he is using is not compatible with Volkswagen We Connect.
I really prefer a separate binding.
In the meantime, glad that you‘re further supporting your binding.
With the existing binding I use CarNet to get access to myAudi. CarNet is also available for Volkswagen, Skoda and other brands. Even all of them seems to use the same API there are differences with authentication (token management), service points (http endpoints & parameteers), but also car models, e.g. the ID.3 requires special handling. This is PIAS and the reason why I didn’t made the move to support VW or other brands so far. Fiddling out those things is time consuming (even I’m in contact with some other developers) and then from time to time things get changed The ioBroker guy already has an implementation, which supports multiple brand, but with limited spare time…
This binding was working wonderfully for me, but it looks like VW just killed the WeConnect portal, which makes the binding useless at the moment. Does anybody know a solution for this?
As @hmerk wrote above, Volkswagen has closed down the We Connect portal 27 of April, hence my binding will no longer work.
I think we should work for one binding for all VW owned brands and that also uses the App API instead of web API, I have my hope to the binding that @markus7017 has started on.
I have not received any information from VW regarding this close down, if anyone has more info on this please send me a PM!
The ioBroker guy already has an implementation, which supports multiple brand, but with limited spare time…