ConnectedCar Binding myAudi, Volkswagen, VW ID, Skoda, Enyaq, Seat, Ford, WeCharge

markus7017 · July 22, 2021, 7:46pm

I completed a first version of the ConnectedCar binding. This replaces the CarNet binding. I have added 2 more APIs (WeConnect.ID, Skoda Enyaq) to it doesn’t make sense to keep the CarNet name.

For existing users there are only

some minor changes to the channel layout,
but you need to re-create and re-link things (channels + items), because the binding got a new name (carnet -> connectedcar), which is included in the Thing UIDs and therefore UIDs for channel names and item names changed.
the vehicle thing was renamed to cnhevicle (beside idvehicle for VW.ID and enyaqvehicle)
if you have textual definitions you could try to do a find and replace or edit JSON DB
I fixed some minor bugs

VW.ID and Skoda Enyaq provide a way smaller integration, e.g. now door/window status, no lock/unlock. I tried to integrate as much as possible and stay as close as possible to the CarNet implementation (channels etc.). The README is not updated to give a clear overview on which vehicle thing provides which channels, but for the moment it’s good enough. You see them after adding the thing and include also enhanced channels when adding equipment to the model.

In fact carnet and connectedcar binding could run in parallel for evaluation. Once you are fine with connectedcar you could drop carnet binding, this will no longer be maintained.

Keep in mind, it’s a first version so there could be bugs, missing features or stuff not working. Provide feedback and I’ll try to fix those issues. Please make sure to include suitable log extracts (activate DEBUG or TRACE logging on the OH console: "log:set TRACE org.openhab.binding.connectedcar - carnet users: don’t forget to activate logging for the new connectedcar binding)

@Joost_Westra Could you please test the binding in general, but also if the charging features are working as expected

rainstar · July 25, 2021, 9:30pm

Hi,

great work, this binding!
I recently upgraded from OH2.5 and doing this came across this binding. I formerly used the org.openhab.binding.vwweconnect binding which has worked well but is stated to be outdated.
Unfortunately, I’ve got problems getting this new binding using OH3.1 to work. (version: org.openhab.binding.connectedcar-3.2.0-SNAPSHOT.jar)

I’ve got a Golf (2018) and Passat (2020), both registred on the VW site. After configuring the bridge (“Volkswagen Account (Carnet)”), both cars appeared in my inbox, so I created a thing for each car. All things immediately went “online”.

As only the Passat has these “always connected” features, I’m mainly interested to get its thing to work. So I created items for the few (8) available channels, but they all stayed ‘NULL’. The only thing working was the vehicle picture. But when calling the image url it showed a picture of the Golf!

So I deleted the three things (2 cars + bridge) and recreated the bridge. After this I only created a thing for the Passat. Now the Passat thing stated, there were no channels at all. After adding the Golf again and disabling and re-enabling the Passat thing, it got the same channels as before (and still the wrong car picture).

To me it seems as if the binding does not handle the channels correctly when multiple cars are available. At least the wrong image is a hint on that. And after using features like geo position or single door status with the formerly used binding, I’d be expecting similar features to be usable with this binding (showing appropriate channels), too.

Maybe there is a bug in the binding in handling multiple cars on the VW site?
By the way: the VIN for the two cars were correctly shown in the car things.

Another test would be to to remove the Golf from the VW site.
But perhaps you’ve got an idea of what might have gone wrong? Maybe I should adjust the log level?

Thanks in advance!

markus7017 · July 26, 2021, 3:18pm

Hi,

the binding defiantly supports multiple accounts of different brands and multiple vehicles at the same time, but you are right, so far I don’t know of a user having more than 1 car on an account. Keep the status, don’t remove the 2nd one from the account so we could diagnose and fix this.

I’ll send you a PM

cwi · August 3, 2021, 12:18pm

Hi @markus7017, just saw your updated README.md. Here adjustment for textual thing/item definitions, proven to work well in my deployment:
.things:

Bridge connectedcar:volkswagen:vw   "VW" [user="<username>", password="<password>" ] {
    Thing cnvehicle   WAUZZZXXXXXXXXXXX   "My Car"    [ vin="WAUZZZXXXXXXXXXXX", pin="<s-pin>", pollingInterval=15, enableAddressLookup=true ]
}

.items:

Switch                      Locked               "Vehicle Locked"                      { channel="connectedcar:cnvehicle:vw:WAUZZZXXXXXXXXXXX:general#vehicleLocked" }
Switch                      AllWindowsClosed     "All Windows Closed"                  { channel="connectedcar:cnvehicle:vw:WAUZZZXXXXXXXXXXX:general#windowsClosed" }
Switch                      TirePressureOk       "Tire Pressure OK"                    { channel="connectedcar:cnvehicle:vw:WAUZZZXXXXXXXXXXX:general#tiresOk" }
...

markus7017 · August 3, 2021, 1:10pm

ist übernommen, danke

Hast Du mit dem Build von gestern Abend getestet? Alle Funktionen?

cwi · August 3, 2021, 9:58pm

Yes. Tested binding 3.2.0.202108022209 on openHAB 3.2.0.M1. Everthing worked smooth to the extent of what my car offers through carnet - just as the builds before.

markus7017 · August 3, 2021, 10:27pm

good to know. In fact I did various refactoring to improve maintainability and separate the OAuth flow, which was required for Ford implementation. Just testing with @J-N-K to add the electrical infos

DPL · August 7, 2021, 12:50pm

Hi from a new german user in this channel!
Having an ID3 as well as a We Charger Connect I am interested in linking both to my openHAB environment (currently on openHAB 3.1.0). To begin, I have downloaded and installed the binding in version 3.2.0.202108022209.
Status of the account thing in UI is ‘unknown’, vehicle thing shows ‘online’ - but as shown in log:

14:32:42.898 [DEBUG] [onnectedcar.internal.api.TokenManager] - WVWZZZE1ZXXXXXXXX: Get Access Token
14:32:42.898 [DEBUG] [nnectedcar.internal.api.ApiHttpClient] - HTTP POST …mbboauth-1d.prd.ece.vwg-connect.com/mbbcoauth/mobile/oauth2/v1/token

14:32:42.930 [DEBUG] [nnectedcar.internal.api.ApiHttpClient] - HTTP GET …vehicle-image.apps.emea.vwapps.io/vehicleimages/exterior/WVWZZZE1ZXXXXXXXX

14:32:43.117 [DEBUG] [onnectedcar.internal.api.TokenManager] - VW: accessToken was created, valid for 2880sec
14:32:43.117 [DEBUG] [nnectedcar.internal.api.ApiHttpClient] - HTTP GET …msg.volkswagen.de/fs-car/usermanagement/users/v1/VW/DE/vehicles

14:32:43.367 [DEBUG] [nnectedcar.internal.api.ApiHttpClient] - HTTP GET …mal-1a.prd.ece.vwg-connect.com/api/cs/vds/v1/vehicles/WVWZZZE1ZXXXXXXXX/homeRegion

14:32:43.430 [WARN ] [ommon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception:
java.lang.NullPointerException: null
at org.openhab.binding.connectedcar.internal.api.carnet.CarNetApi.getVehicles(CarNetApi.java:190) ~[?:?]
at org.openhab.binding.connectedcar.internal.handler.AccountHandler.initializeThing(AccountHandler.java:171) ~[?:?]
at org.openhab.binding.connectedcar.internal.handler.AccountHandler.lambda$2(AccountHandler.java:145) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) ~[?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
at java.lang.Thread.run(Thread.java:834) [?:?]
14:32:43.835 [DEBUG] [nnectedcar.internal.api.ApiHttpClient] - HTTP GET …mal-3a.prd.eu.dp.vwg-connect.com/api/rolesrights/operationlist/v3/vehicles/WVWZZZE1ZXXXXXXXX?scope=ALL

14:32:44.179 [DEBUG] [ing.connectedcar.internal.api.ApiBase] - WVWZZZE1ZXXXXXXXX: API call getOperationList failed: API call failed GET …mal-3a.prd.eu.dp.vwg-connect.com/api/rolesrights/operationlist/v3/vehicles/WVWZZZE1ZXXXXXXXX?scope=ALL (HTTP 404 Not Found), result = {“error”:{“errorCode”:“mbbc.rolesandrights.unknownVehicle”,“description”:“The referenced vehicle with VIN: WVWZZZE1ZXXXXXXXX could not be found or has no association to the given User”}}
14:32:44.179 [INFO ] [r.internal.handler.VehicleBaseHandler] - WVWZZZE1ZXXXXXXXX: API Call failed: API call failed
14:32:44.194 [DEBUG] [r.internal.handler.VehicleBaseHandler] - WVWZZZE1ZXXXXXXXX: HTTP response: {“error”:{“errorCode”:“mbbc.rolesandrights.unknownVehicle”,“description”:“The referenced vehicle with VIN: WVWZZZE1ZXXXXXXXX could not be found or has no association to the given User”}}
14:32:44.194 [DEBUG] [r.internal.handler.VehicleBaseHandler] - WVWZZZE1ZXXXXXXXX: message.api-status.mbbc.rolesandrights.unknownVehicle
14:32:44.194 [DEBUG] [r.internal.handler.VehicleBaseHandler] - WVWZZZE1ZXXXXXXXX: Thing is now online

the vehicle could not be found and it also shows no channels… (I have double checked that the VIN is correct).
Any ideas what I did wrong?

PS: If I get it running, I could assist in testing functionality of the binding for the VW ID integration and/or the VW Charger Connect integration, if you are interested.

scha · August 7, 2021, 2:49pm

Hi there!

Tried to get this running for a Skoda CitigoE, but was not successfull. Can add a the carnet-thing, fill in the credentials and ending up after a few seconds after aktivating with an error "COMMUNICATION_ERROR Unknown brand for base URL ".
Never get the bridge up and running…

I´m running OH 3.1.0 Release Build and tried both, the 3.1.0 as well as 3.2.0 jar-file from Github.
Login into skoda-connect.com as well as the iPhone-App from skoda are running well with the same credentials.

Tried also the Enyak-Thing with the same credentials and get also an (other) error (HANDLER_MISSING_ERROR).

any hints??

markus7017 · August 8, 2021, 9:44am

@DPL @scha I suppose both of you started with the carnet bindig. This is depricated, but still the latest stable release. I’m almost done with successor: ConnectedCar Binding

Nevertheless, I think you used the rong accounrt things.

ID.3 requires VW VD Account (WeConnect)
the CitygoE most likely the Skoda Enyaq (which is in fact Skoda-E - I’ll rename that thing)

we could test this with the new binding

@DPL I’m also interested in a WeCharge integration. I have the wallbox here, but waiting for an Electrician for installation…

scha · August 8, 2021, 11:19am

Thans for response @markus7017 !

You are not wrong at all; I used the “old” org.openhab.binding.carnet-3.2.0-SNAPSHOT.jar for which which I found the link anywhere above.
Now I´ve found org.openhab.binding.connectedcar-3.2.0-SNAPSHOT.jar, installed it and got the Bridge-Thing up and online.
Then I added a “Enyak-Vehicle”, but do not get this running. It tells me, the Bridge is not initialzed

even the Bridge show “ONLINE”

scha · August 8, 2021, 11:31am

have to add:

Got it a bit more running now: I´ve NOT used the Enyak-Thing, but instead the “Skoda Connect-Account” and immediately a new vehicle-thing was discovered, which reflects my citigoE. Unfortunately the new vehicle-thing has not an single channel.

In my log, I see that there are a lot of channels coming in up to the “Heater Source”, which brakes the reading down:
2021-08-08 13:27:55.011 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: KILOMETER_STATUS=10469 (channel status#odometer)

2021-08-08 13:27:55.013 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: MAINT_OIL_DISTANCE_CHANGE=-1700km (channel maintenance#distanceOilChange)

2021-08-08 13:27:55.015 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: MAINT_OIL_TIME_CHANGE=-17d (channel maintenance#intervalOilChange)

2021-08-08 13:27:55.017 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: MAINT_DISTANCE_INSPECTION=-19700km (channel maintenance#distanceToInspection)

2021-08-08 13:27:55.019 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: MAINT_INSPECTION_TIME=-175d (channel maintenance#timeToInspection)

2021-08-08 13:27:55.021 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: MAINT_ALARM_OIL_CHANGE=1 (channel maintenance#oilWarningChange)

2021-08-08 13:27:55.024 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: MAINT_ALARM_INSPECTION=1 (channel maintenance#alarmInspection)

2021-08-08 13:27:55.025 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: MAINT_MONTHLY_MILEAGE=257km (channel status#monthlyMilage)

2021-08-08 13:27:55.027 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: STATE3_PARKING_LIGHT=2 (channel status#parkingLight)

2021-08-08 13:27:55.029 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: TEMPERATURE_OUTSIDE=2945dK (channel status#tempOutside)

2021-08-08 13:27:55.031 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: STATE30_PARKING_BRAKE=0 (channel status#parkingBrake)

2021-08-08 13:27:55.033 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: CHARGING_LEVEL_PERCENT=89% (channel charger#chargingLevel)

2021-08-08 13:27:55.035 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: CURRENT_SPEED=0km/h (channel status#currentSpeed)

2021-08-08 13:27:55.037 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: PRIMARY_RANGE=275km (channel range#primaryRange)

2021-08-08 13:27:55.039 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: FUEL_LEVEL_PERCENT=100% (channel range#fuelPercentage)

2021-08-08 13:27:55.041 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: FUEL_METHOD=0 (channel range#fuelMethod)

2021-08-08 13:27:55.042 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: LOCK2_LEFT_FRONT_DOOR=3 (channel doors#doorFrontLeftLocked)

2021-08-08 13:27:55.045 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: STATE3_LEFT_FRONT_DOOR=3 (channel doors#doorFrontLeftState)

2021-08-08 13:27:55.046 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: LOCK2_LEFT_REAR_DOOR=3 (channel doors#doorRearLeftLocked)

2021-08-08 13:27:55.049 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: STATE3_LEFT_REAR_DOOR=3 (channel doors#doorRearLeftState)

2021-08-08 13:27:55.051 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: LOCK2_RIGHT_FRONT_DOOR=3 (channel doors#doorFrontRightLocked)

2021-08-08 13:27:55.053 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: STATE3_RIGHT_FRONT_DOOR=3 (channel doors#doorFrontRightState)

2021-08-08 13:27:55.055 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: LOCK2_RIGHT_REAR_DOOR=3 (channel doors#doorRearRightLocked)

2021-08-08 13:27:55.058 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: STATE3_RIGHT_REAR_DOOR=3 (channel doors#doorRearRightState)

2021-08-08 13:27:55.060 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: LOCK2_TRUNK_LID=3 (channel doors#trunkLidLocked)

2021-08-08 13:27:55.063 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: STATE3_TRUNK_LID=3 (channel doors#trunkLidState)

2021-08-08 13:27:55.065 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: LOCK3_HOOD=3 (channel doors#hoodLocked)

2021-08-08 13:27:55.067 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: STATE3_HOOD=3 (channel doors#hoodState)

2021-08-08 13:27:55.069 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: STATE3_LEFT_FRONT_WINDOW=0 (channel windows#windowFrontLeftState)

2021-08-08 13:27:55.071 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: STATE3_LEFT_REAR_WINDOW=0 (channel windows#windowRearLeftState)

2021-08-08 13:27:55.072 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: STATE3_RIGHT_FRONT_WINDOW=0 (channel windows#windowFrontRightState)

2021-08-08 13:27:55.075 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: STATE3_RIGHT_REAR_WINDOW=0 (channel windows#windowRearRightState)

2021-08-08 13:27:55.076 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: STATE3_CONVERTIBLE_TOP=0 (channel doors#covertibleTopState)

2021-08-08 13:27:55.078 [INFO ] [ernal.api.carnet.CarNetServiceStatus] - TMBZZZAAZLD801077: STATE3_ROOF_FRONT_COVER=0 (channel windows#roofFrontCoverState)

2021-08-08 13:27:55.089 [WARN ] [.internal.handler.VehicleBaseHandler] - TMBZZZAAZLD801077: General Error: Missing channel definition for heaterSource

java.lang.IllegalArgumentException: Missing channel definition for heaterSource

at org.openhab.binding.connectedcar.internal.api.ApiBaseService.addChannels(ApiBaseService.java:133) ~[?:?]

at org.openhab.binding.connectedcar.internal.api.ApiBaseService.addChannels(ApiBaseService.java:121) ~[?:?]

at org.openhab.binding.connectedcar.internal.api.carnet.CarNetServiceClimater.createChannels(CarNetServiceClimater.java:68) ~[?:?]

at org.openhab.binding.connectedcar.internal.handler.VehicleBaseHandler.initializeThing(VehicleBaseHandler.java:227) ~[?:?]

at org.openhab.binding.connectedcar.internal.handler.VehicleBaseHandler.lambda$1(VehicleBaseHandler.java:458) ~[?:?]

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]

at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) [?:?]

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) [?:?]

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]

at java.lang.Thread.run(Thread.java:834) [?:?]

==> /var/log/openhab/events.log <==

2021-08-08 13:27:55.101 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘connectedcar:cnvehicle:f50cd11927:TMBZZZAAZLD801077’ changed from UNKNOWN: Initializing to OFFLINE (COMMUNICATION_ERROR): General Error: Missing channel definition for heaterSource

2021-08-08 13:28:03.808 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘connectedcar:cnvehicle:f50cd11927:TMBZZZAAZLD801077’ changed from OFFLINE (COMMUNICATION_ERROR): General Error: Missing channel definition for heaterSource to ONLINE

DPL · August 8, 2021, 12:08pm

Thanks for quick answer as well to @markus7017 !
In fact, I had installed the correct binding but it was a wrong sequence in the .things file for the We Connect account… - fixed it and my ID.3 as well as the channels came up now!
Now looking more into details of the channels - will let you know if anything strange comes up.

We Charger Connect here working since nearly a month now - so I keep fingers crossed for you, that the electrician finds time soon!

markus7017 · August 10, 2021, 8:46pm

I’m wondering about the log messages. It seems that you combined a Enyak Account Thing is a CarNet vehicle thing. Do you create the things in the UI or by a .things file?

I’m almost done with the new version. Need to fix 1 bug.

scha · August 11, 2021, 5:48am

I created the Skoda-Connect-Account via the UI and the “car-thing” was then auto discovered.

Nothing done via files at all.
Looks like Skoda mixed up some stuff, maybe because e eCitigo WAS a gas-car in the past

Let me know, if I can help anywhere.

MathiasK · August 12, 2021, 6:32pm

@markus7017 I tried the latest ConnectedCar Binding but I’m not getting any channels.
(myAudi Login / etron) . Waited 30 min.

The log shows

2021-08-12 19:49:00.523 [DEBUG] [g.connectedcar.internal.ChannelCache] - WAUZZZGE0MB027113: Channel tripLong1#timestamp updated with 2021-08-12T17:29:48.000+0200 (type class org.openhab.core.library.types.DateTimeType).
2021-08-12 19:49:00.525 [DEBUG] [g.connectedcar.internal.ChannelCache] - WAUZZZGE0MB027113: Channel tripLong1#avgFuelConsumption updated with 0 l (type class org.openhab.core.library.types.QuantityType).
2021-08-12 19:49:00.526 [DEBUG] [g.connectedcar.internal.ChannelCache] - WAUZZZGE0MB027113: Channel tripLong1#avgElectricConsumption updated with 26 kWh (type class org.openhab.core.library.types.QuantityType).
2021-08-12 19:49:00.528 [DEBUG] [g.connectedcar.internal.ChannelCache] - WAUZZZGE0MB027113: Channel tripLong1#avgSpeed updated with 60 km/h (type class org.openhab.core.library.types.QuantityType).
2021-08-12 19:49:00.529 [DEBUG] [g.connectedcar.internal.ChannelCache] - WAUZZZGE0MB027113: Channel tripLong1#startMileage updated with 0 km (type class org.openhab.core.library.types.QuantityType).
2021-08-12 19:49:00.531 [DEBUG] [g.connectedcar.internal.ChannelCache] - WAUZZZGE0MB027113: Channel tripLong1#mileage updated with 10008 km (type class org.openhab.core.library.types.QuantityType).
2021-08-12 19:49:00.532 [DEBUG] [g.connectedcar.internal.ChannelCache] - WAUZZZGE0MB027113: Channel tripLong1#overallMileage updated with 10008 km (type class org.openhab.core.library.types.QuantityType).
2021-08-12 19:49:00.534 [DEBUG] [g.connectedcar.internal.ChannelCache] - WAUZZZGE0MB027113: Channel general#lastUpdate updated with 2021-08-12T19:49:00.000+0200 (type class org.openhab.core.library.types.DateTimeType).
2021-08-12 19:49:00.535 [DEBUG] [.internal.handler.VehicleBaseHandler] - WAUZZZGE0MB027113: Thing is now online
2021-08-12 19:49:00.541 [DEBUG] [.internal.handler.VehicleBaseHandler] - WAUZZZGE0MB027113: Enabling channel cache

scha · August 14, 2021, 11:32am

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.

BTW: Markus suggested to share my visualization:

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.

scha · August 14, 2021, 11:37am

Oh, sorry. Just found out in the advanced-settings of the car-thing, there is the possibility to adjust the poll-frequency.

→ It´s an huge advantage to be able to read

markus7017 · August 14, 2021, 12:18pm

there are 3 types of refresh

regular polling (you found the interval)
request a refresh from the vehicle (take care on the rate limit, the is a channel which gets updated by the action response)
after an action completed the binding triggers a regular poll

markus7017 · August 26, 2021, 6:25pm

I updated the DEV build - an important one!!

The latest build brings

Integration of the FordPass API
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

Thing	Description	Portal	API
myaudi	myAudi Account thing (bridge)	https://myaudi.de	CarNet
volkswagen	myVolkswagen Account (bridge)	https://myvolkswagen.de	CarNet
skoda	Skoda Connect Account (bridge)	https://www.skoda-connect.com	CarNet
seat	myVolkswagen Account (bridge)	myVolkswagen │Anmelden & Volkswagen ID │ Volkswagen Deutschland	CarNet
vwid	VW ID. Account (bridge)	https://myvolkswagen.de	WeConnect.ID
skoda-e	Skoda Enyaq Account (bridge)	https://www.skoda-connect.com	Skoda Native + CarNet
ford	FordPass Account (bridge)	https://fordpass.com	FordPass
wecharge	VW ID.Charger Account (bridge)	https://web-home-mobile.apps.emea.vwapps.io/	WeCharge

Note that the VW ID. uses a different account thing than other Volkswagen and same for the Skoda Enyaq compared to other Skoda models.

Thing	Description
cnvehicle	CarNet Thing (Audi, VW, Skoda, SEAT
idvehicle	VW ID. vehicle, e.g. ID.3/ID.4
sevehicle	Skoda Enyaq vehicle
fordvehicle	Ford vehicle
wcbox	VW Wallbox with WeCharge service

You could also provide infos on your vehicle. I could add those to the list of verified vehicles.

Have fun