Thanks to @markus7017 its working like a charm now with the new jar-file. Great Work, really appreciated!
I have one additional question, I´m not sure about: Is the binding doing an automatic reload/sync of the car-data? I´m doing this manually from time to time (when I expect, that there are interesting changes), but want to avoid this silly 50-download-limit.
No rocket-science at all, just a openHAB-Page as a floor-plan which I open as a pop-up from the Overview, with a fancy background and some markers. Let me know, if someone need some hints.
Integration of the WeCharge API for the VW ID.Charger
Refactoring of the OAuth flow to simplify the integration of new APIs
Some bug fixes
Some channels have been moved from general to status group
README updated
This build has been tested to come up with 10 accounts of different brands and vehicles and some testing was already performed by other people. This doesn’t mean it’s bug free, but I have a good feeling. Please help to verify so I could open the PR.
Make sure to removed the CarNet binding if you still use this (deprecated, upgrade to ConnectedCar binding
Remove all things
Add the account thing, discovers vehicle thing
Add vehicle thing from Inbox, link channels (some of them are advanced) and add to model
Skoda Enyaq and VW.ID users: Make sure to select the specific Account Thins
There are 2 types of things
Account Thing implements the online access to the service backend
Vehicle Thing provides status data and remote control functions
Hi there!
I own a VW eGolf and would be keen to integrate that into my openHAB system!
I use the VW “weconnect” software so an accound is existing.
What do I have to do to install the carnet-thing? An approriate binding does not exist in my version. I use the openHAB 3.1.0 Release Build. Maybe I have to upgrade!?
Does someone uses the WeConnect App and sees things like odometer (km), maintenance info or light status? This info seems to be available at least for some models
@markus7017 Yes, WeConnect App can present such data, but not in all the details that are available through API and binding, e.g. level of open windows:
I connected an eGolf.
The binding provides channels for many things as
windows state closed/not closed as well as %
lock state
battery state (very important)
range, based on battery state and last consumption
in total, there are ~100 information points…
CarNet: Follow http redirects helped to get an A3 e-tron online. I hope this has no side effects to other APIs/models, but so far it looks good
WeConnect: Added support for door/window, light status, odometer, maintenance infos and parking position. However, this depends on capabilities provided by the car. ID.3 seems to offer non of them.
WeCharge: Combine charging records from home and public/pay charging into one list. I implemented the lookup for charging stations nearby. The problem is: this requires the geo location of the car to provide meaningful results. If someone is interested in this feature, we could discuss how to implement it. I’m thinking on adding a channel and then a rule could fetch the geo position from the vehicle thing, set the location and then the WeCharge thing will run the query and provide the results a channel groups. This can then be used to display them on a map.
README updated, some re-factoring and cleanup
@cwi does currently initial testing and will give an update
anybody else welcome
Update: WeConnect (vwid+idvehicle) establishes connection well and reports a good range of information that I also have available through CarNet. WeConnect is faster than CarNet, which requires a whole lot of API calls to gather all the information. Yet, no controls were identified to be sent to my car, e.g. Lock/Unlock, probably a limitation of my account.
Some issues or inconsistencies with WeConnect were identified and reported to @markus7017 . Whomever needs to rely on WeConnect today, it is great to also have this option now in the binding - thanks to Markus’ continued efforts. I wonder when he finds a way to offer a channel like “control#ignite”, to start the car, or “control#silentmode” to mute my Diesel.
I wanted to visualize the data from my AUDI. I have set up the items and can also see the values and states. So far everything is ok. Now I want to show the data in Basic UI. Unfortunately, the values are not displayed there. The other items from other devices such as my heating, etc. are displayed correctly there. I just can’t do it with the vehicle data.
Does anyone have any idea why it is? The display of the values on the OH homepage also works without any problems.
I am using the current version of openHAB 3.1.0 and connectedcar-3.2.0-SNAPSHOT
Greetings and thank you in advance for your effort.