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

[HSorgYves (Dr. Yves Kreis)]

Another release to

• jump to the next development cycle;
• solve the bug reported by @nignac (ConnectedCar Binding myAudi, Volkswagen, VW ID, Skoda, Enyaq, Seat, Ford, WeCharge - #1106 by nignac);
• add three new channels for Audi fuel cars: range#fuelPercentage, maintenance#distanceAdBlue, and maintenance#oilWarningLevel.

Release ConnectedCar Snapshot 20230727 · HSorgYves/openhab-addons

[RalphSester]

Thank you for your updates !!!

i can’t see the 3 new audi-channels and i am missing the “maintenance#oilPercentage” channel, which it was there in the old binding…can you please check this ?

[MFI-Net1 (Martin Fischer)]

Hi HSorgYves,
first of all thank you for picking this up

I’m now using the connected car binding 3.4.6.

After choosing myAudi_Acount (WebAcount) I receive the following error message:
COMMUNICATION_ERROR

Initialization failed: API call failed GET https://emea.bff.cariad.digital/vehicle/v1/signin-service/v1/f4d0934f-32bf-4ce4-b3c4-699a7049ad26@apps_vw-dilab_com/login/authenticate?relayState=679fce0385e2032119c8bb9144857e7e534ab00d&nextButtonDisabled=true&enableNextButtonAfterSeconds=256&error=login.error.throttled (HTTP 404 Not Found), result = default backend - 404

Can you help me?
Thanks in advance Martin

[HSorgYves (Dr. Yves Kreis)]

@RalphSester

The three new channels are only there if provided in the answer by the api. Which car do you have?
I guess they are not available for your car. You can turn on debugging for the connectedcar addon and look for a HTTP 207 Response: {"access": ... line which you can sent me via PM.

@MFI-Net1

You need to provide more information. Did you use MainUI? Did you provide a username/password?

[RalphSester]

i have an Audi Q3 Sportback - “Benziner”
so the channels should be there ?!

Update: OK - i checked the 207 response in my logfile. It seems that my car does not provide these information anymore…no handbrake, no tirepressure, no window openlevels anymore…seems that was part of the old “audi” interface…but not the VW-interface…

[HSorgYves (Dr. Yves Kreis)]

@RalphSester

Unfortunately the old Audi connection is down and the one used by e-tron does provide less data. Sorry!

[MFI-Net1 (Martin Fischer)]

Hi, yes , I provided usernam + password

[HSorgYves (Dr. Yves Kreis)]

@MFI-Net1:
The call you pasted refers to getting the vehicles. Are vehicles in your account?
The easiest way would be to enable debug logging for the bundle and sent me a complete log via PM.

[KenkiCK]

Is there any plan to create a version for OH 4 ? I’m really happy that it goes forward with the binding!

[HSorgYves (Dr. Yves Kreis)]

@KenkiCK: Yes, will hopefully be ready before the end of the week, cf. ConnectedCar Binding myAudi, Volkswagen, VW ID, Skoda, Enyaq, Seat, Ford, WeCharge - #1103 by HSorgYves

[fennepa (Alex)]

Hi HSorgYves,
appreciating your efforts to get things to work again! However, I’m having some issues with the weConnect for my Audi A3 Spb PHEV1.4 (hybrid). I have deleted all my old stuff and created new bridge, car and items, but the only update that has been succesfull seems to be at initial connection. The item for general_lastupdate did get an initial value, but was never updated since. there is also no .previousState in my db. bridge and thing show “online”. Polling interval has been set to 10min.

Is it correct that the Thing Type has been set to VW ID Vehicle? or did I make a wrong turn during setup?

apparently this is not a new problem:

@Sebastian1

The same problem what has been there for a long time is still there. The query about the current state does not work anymore. If I deactivate the Things (Account and Auto) and activate them again, it queries exactly 1x and then never again. Does anyone have an idea or maybe the same problem?

[HSorgYves (Dr. Yves Kreis)]

@fennepa: Without log it’s hard to say anything… set log level to debug for conectedcar (Console → log:set debug org.openhab.binding.connectedcar) and sent the log via PM.

P.S.: Audi Bridge is the ID Bridge by now, so we need an ID Vehicle.

[hermann59 (Hermann Matthes)]

Hello,
I’m a newbie to this binding and have a problem with it’s installation.

I copied org.openhab.binding.connectedcar-3.4.6-SNAPSHOT.jar to /usr/share/openhab/addons, restarted openhab and got the following error:

2023-08-02 01:20:22.841 [WARN ] [org.apache.felix.fileinstall ] - Error while starting bundle: file:/usr/share/openhab/addons/org.openhab.binding.connectedcar-3.4.6-SNAPSHOT.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.connectedcar [263]

What’s my fault?

Sorry, I forgot to tell that I’m on OH4.

[fennepa (Alex)]

Hi, did you transfer as ‘binary’ when you copied the file into it’s location?

[HSorgYves (Dr. Yves Kreis)]

@hermann59: The binding is for 3.4.5 (as the filename suggests) only. A 4.0.x binding will be available soon.

[Felix_Schneider]

@fennepa

However, I’m having some issues with the weConnect for my Audi A3 Spb PHEV1.4 (hybrid). I have deleted all my old stuff and created new bridge, car and items, but the only update that has been succesfull seems to be at initial connection. The item for general_lastupdate did get an initial value, but was never updated since

I experience the same behaviour.

I am on holidays right now and thus cannot debug or access any logs. On 11.08. I should be able to do so if you still need logs by then.

[hermann59 (Hermann Matthes)]

I used the upload feature from MobaXTerm and that worked by now.

[hermann59 (Hermann Matthes)]

@HSorgYves

@hermann59: The binding is for 3.4.5 (as the filename suggests) only. A 4.0.x binding will be available soon.

Ok thanks. I will wait for it’s availability.

[fennepa (Alex)]

reviewing the debuglog for my Audi A3, the binding is receiving the channelupdates, but for some reason the associated items do not receive a status change. no changes are listed in event.log.

additionally I have 2 weird warnings in the log:

2023-08-02 18:59:15.056 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: AudiA3_general_LastUpdate
2023-08-02 18:59:15.057 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: AudiA3_general_APIRateLimit

these might actually be leftovers from the previous binding. I do not recall if I used to have items for these channels. If so, I probably did not actively use them. they are not visible in the MainUI nor as textual item in a file, so I cannot delete them (again). These warnings seem to appear without a clear pattern.

I therefor created the item ‘AudiA3_general_LastUpdate’, associated to the channel, which gave no conficts. Even better, the item was populated with the channel value immediately, and my actual item Audi_A3_Spb_general_LastUpdate was updated, too:

2023-08-03 14:01:11.399 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Audi_A3_Spb_general_LastUpdate' changed from 2023-07-28T20:05:26.000+0200 to 2023-08-03T13:47:48.000+0200
2023-08-03 14:01:11.400 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'AudiA3_general_LastUpdate' changed from NULL to 2023-08-03T13:47:48.000+0200

unfortunately, It was only a one time success, because at the next polling interval I see this in the debug:log:

2023-08-03 14:18:07.444 [DEBUG] [ar.internal.handler.ThingBaseHandler] - WAUZZZXXXXXXXXXXX: updateChannel -> general#lastUpdate = 2023-08-03T14:18:07.000+0200`

while the items are still at:

I unlinked and deleted the ghost item. I will check if I have now only one warning left…
update: deleting the item, causes the warning to return.

[HSorgYves (Dr. Yves Kreis)]

In events.log you will only see changes of items while in openhab.log you will see the log as defined in the console for the bundle.

#lastUpdate will only be updated if something changed for your car. If all values remain the same, then #lastUpdate won’t change either.