Adblue is the additive for Diesel engine to get “cleaner” emissions
representing here the range >2400km
I suppose you got a Gasoline (Super) engine on your car and by building the binding forgot the adblue value for Diesel in the API(hope this is the issue)
I’ve built a new jar-file, and updated my original post, that will change the behaviour if one of many status requests fail, it will still update the vehicle thing with the status that it managed to query.
This leads to uglier code but it will hopefully be more easy to track down which status requests that fails and then try to find out why.
I will also update the original post of how to create a separate log file for a binding, if you do not already know. That then gives you much easier way of sending me the debug logs!
It looks like something is wrong with your username or password. S-PIN is only needed for actions and not for fecthing status, so the binding should support having S-PIN unset/absent.
Does the same credentials work to log on to: https://www.portal.volkswagen-we.com/
I’ve compiled a new jar-file, and updated my original post, that hopefully will handle wrong credentials and failed login in a better way, so that the Bridge status states that is it a credentials problem.
If you could test the new jar-file it would be great.
If you then could send me the DEBUG logs in a PM, I can take a look whats happening. Please mask credentials and VIN info from the logs.
Hi, thanks for the fast response. I can login on the site without problems. I will try your new version as fast as possible. I use only the we connect app and use the vw credentials in it.
Thank you for the binding. He works fine with me now. Is it also possible to send functions to the car? for example closing the doors?
Has anyone already come up with nice features that you can make with the binding?
Fuel consumption is not calclulated by the binding, it is also fetched from VW We Connect portal.
Can you compare the figures with the portal or the App?
Look in the README, there two ways of accessing actions, either using Switches in sitemaps as described, or you can try out using actions from a rule.
I have not tested actions in depth, that was something that I took from the VolvoOnCall binding, I have created items and a sitemap that I can access from the OH IOS App, from that App I can control lock/unlock of my vehicle and also start the heater.
Since I also use Google Home and the OH Google Home action, I can tell Google to unlock my vehicle or star the heater
But as I wrote in the original post, the API is kind of fussy, to be able to start the heater you must sometime turn on/off the ignition for some reason. That is not a fault in the binding, the VW We Connect App has exactly the same behaviour.
i think my problem is that i use a vw account but not the portal.
my app we connect go is logging on on this website https://vwid.vwgroup.io/
there is all my data stored. this account is connect to all vw.
but my we connect go seems not the same use for we connect.
the portal seems for buying new cars, i cant add a car via vin there.
but my car is stored in the account above.