No, I focused on what I could test and I don’t have an Audi account to test. So far I only looked at VW in CarNet. If you are willing to share your credentials for testing purpose, please send them via PM and I get a look soon. If not, I need to debug further to solve this issue which takes more time.
Thank you! Finally, my ID. 3 is open to HAB again 
Frankly I don’t feel comfortable sharing my credentials, however I am more than willing to test a (or multiple) snapshot(s) and send you debug output you might need =)
You would also make me very happy if you are able to resolve the RS.security.9007 error.
I will try to get a look into CarNet (Audi) this weekend.
1 Like
Maybe a hint from ioBroker will help you. With the Connectec car adapter and the switch to etron, you get at least some data from your Audi. It may be a reference to the API.
Gruß Joe
Does the binding already work with OH4?
Tried latest release yesterday and no, it did not.
No, it does not (yet). Still working on Audi connection problem. Then I will recompile for OH4.
2 Likes
Great, that to take an eye on this - thank you!
Good and Bad News!
As always, bad news first: the connection for audi seems to be dead.
While looking at the ioBroker.vw-connect, the evcc and the audi_connect_ha code, I discovered that an audietron connection exists which is quite close to a vwid connection.
This leads to the good news: I managed to create a new audi connection based on vwid. At first sight, the only change for you as users will be to switch your thing from cnvehicle to idvehicle. I will try to finish my tests tomorrow and release an updated 3.4 binding as soon as possible.
Next steps:
- Release an updated 3.4 binding for audi
- Release a final 3.4 binding without compilation warnings
- Release a first 4.0 binding
5 Likes
That sounds great! Thank you for your work =)
Please find the link to today’s release solving the Audi login problem. Remember to rename cnvehicle to idvehicle in your thing file for your Audi vehicle!
1 Like
Thank you for bringing the Binding for Audi back to life
I have added the Binding.
Seems like some channels are updating …
I get the following error on my 2019 etron:
2023-07-27 12:08:39.171 [DEBUG] [nectedcar.internal.util.ChannelCache] - WAUZZZXXXXXXXXXXX: Channel control#charge updated with OFF (type class org.openhab.core.library.types.OnOffType).
2023-07-27 12:08:39.172 [DEBUG] [ar.internal.handler.ThingBaseHandler] - WAUZZZXXXXXXXXXXX: updateChannel -> charger#chargingState = notReadyForCharging
2023-07-27 12:08:39.172 [DEBUG] [nectedcar.internal.util.ChannelCache] - WAUZZZXXXXXXXXXXX: Channel charger#chargingState updated with notReadyForCharging (type class org.openhab.core.library.types.StringType).
2023-07-27 12:08:39.172 [DEBUG] [ar.internal.handler.ThingBaseHandler] - WAUZZZXXXXXXXXXXX: updateChannel -> charger#chargingMode = manual
2023-07-27 12:08:39.173 [DEBUG] [nectedcar.internal.util.ChannelCache] - WAUZZZXXXXXXXXXXX: Channel charger#chargingMode updated with manual (type class org.openhab.core.library.types.StringType).
2023-07-27 12:08:39.173 [DEBUG] [ar.internal.handler.ThingBaseHandler] - WAUZZZXXXXXXXXXXX: updateChannel -> charger#remainingChargingTime = 0
2023-07-27 12:08:39.174 [DEBUG] [nectedcar.internal.util.ChannelCache] - WAUZZZXXXXXXXXXXX: Channel charger#remainingChargingTime updated with 0 min (type class org.openhab.core.library.types.QuantityType).
2023-07-27 12:08:39.174 [DEBUG] [ar.internal.handler.ThingBaseHandler] - WAUZZZXXXXXXXXXXX: updateChannel -> charger#chargingPower = 0
2023-07-27 12:08:39.174 [DEBUG] [nectedcar.internal.util.ChannelCache] - WAUZZZXXXXXXXXXXX: Channel charger#chargingPower updated with 0 (type class org.openhab.core.library.types.DecimalType).
2023-07-27 12:08:39.174 [DEBUG] [ar.internal.handler.ThingBaseHandler] - WAUZZZXXXXXXXXXXX: updateChannel -> charger#chargingRate = 0
2023-07-27 12:08:39.175 [DEBUG] [nectedcar.internal.util.ChannelCache] - WAUZZZXXXXXXXXXXX: Channel charger#chargingRate updated with 0 (type class org.openhab.core.library.types.DecimalType).
2023-07-27 12:08:39.175 [DEBUG] [ar.internal.handler.ThingBaseHandler] - WAUZZZXXXXXXXXXXX: updateChannel -> charger#targetChgLvl = 100
2023-07-27 12:08:39.175 [DEBUG] [nectedcar.internal.util.ChannelCache] - WAUZZZXXXXXXXXXXX: Channel charger#targetChgLvl updated with 100 % (type class org.openhab.core.library.types.QuantityType).
2023-07-27 12:08:39.176 [WARN ] [ar.internal.handler.ThingBaseHandler] - WAUZZZXXXXXXXXXXX: General Error: String index out of range: 0
java.lang.StringIndexOutOfBoundsException: String index out of range: 0
at java.lang.StringLatin1.charAt(StringLatin1.java:47) ~[?:?]
at java.lang.String.charAt(String.java:693) ~[?:?]
at org.openhab.binding.connectedcar.internal.api.weconnect.WeConnectServiceStatus.updateChargingStatus(WeConnectServiceStatus.java:200) ~[?:?]
at org.openhab.binding.connectedcar.internal.api.weconnect.WeConnectServiceStatus.serviceUpdate(WeConnectServiceStatus.java:152) ~[?:?]
at org.openhab.binding.connectedcar.internal.api.ApiBaseService.update(ApiBaseService.java:90) ~[?:?]
at org.openhab.binding.connectedcar.internal.handler.ThingBaseHandler.updateVehicleStatus(ThingBaseHandler.java:476) ~[?:?]
at org.openhab.binding.connectedcar.internal.handler.ThingBaseHandler.lambda$1(ThingBaseHandler.java:420) ~[?:?]
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:829) [?:?]
I’ve had a quick look into it:
Looks like there’s no status.charging.chargingSettings.value.maxChargeCurrentAC delivered via API.
Niklas
Thank you! Works like a charm with my Audi A3 2022 (MildHybrid).
A few things I noticed while implementing the new binding:
- Some of the channel names changed (e.g. odometer). This is nothing problematic, just something to keep in mind when you change the binding and wonder why the item states don’t update.
- Some channels are missing compared to the last binding (e.g. fuel percentage, oil percentage, image url). I don’t blame @HSorgYves in any way, I guess the endpoint just doesn’t provide these details.
I didn’t encounter the error that @nignac saw or any other errors by that matter.
→ I am so happy that there is a new working binding again. Thank you for your work @HSorgYves ! =) 
Thanks for pointing this out @Felix_Schneider.
- I have no clue how the channels where before the change. The current channels for Volkswagen ID.3 and Audi A7 Sportback can be found in the readme file:
- I didn’t look into the images yet. However missing channels are reported by users of ioBroker.vw-connect and evcc too. Currently I don’t see a solution for these.
Thank you very much @HSorgYves for bringing the binding back to life! In comparison with the previous binding the following channels are not available anymore for my vehicle:
general#rateLimit
general#lastAction
general#lastActionStatus
general#lastActionPending
control#lock (see comment that I could not configure a PIN code)
status#vehicleLocked
status#maintenanceRequired
status#windowsClosed
status#tiresOk
status#odometer
status#monthlyMilage
status#parkingLight
status#tempOutside
status#parkingBrake
status#currentSpeed
status#carMoving
location#locationPosition
location#locationLastUpdate
location#locationAddress
range#fuelPercentage
maintenance#oilWarningChange
maintenance#alarmInspection
maintenance#oilWarningLevel
maintenance#oilPercentage
maintenance#distanceAdBlue
doors#hoodLocked
windows#windowFrontLeftPos
windows#windowRearLeftPos
windows#windowFrontRightPos
windows#windowRearRightPos
tires#tirePresFrontLeft
tires#tirePresRearLeft
tires#tirePresFrontRight
tires#tirePresRearRight
tires#tirePresSpare
rluHistory1#rluOperation
rluHistory1#rluTimestamp
rluHistory1#rluResult
I fully understand that this is most likely a result of the reduced functionality by the manufacturar. Not missing a lot, however some information (maintenance#distanceAdBlue, maintenance#oilWarningLevel) must still be available as it is shown in the Audi app.
I am using MainUI to define things and items an I cannot enter a PIN (no configutration option). Consequently the lock / unlock functionality is not available.
Nevertheless very happy to have the binding back!!
Dear @mvbergen,
status#vehicleLocked should be available.
status#odometer has been renamed to maintenance.odometer.
Will get a look into MainUI as I am using configuration files only. Will keep you posted.
Best Regards,
Yves
1 Like
hi @mvbergen/ @HSorgYves I have overwritten the .jar file in my installation (also using mainUI here):
I have a new thing discovered sitting in my inbox, but I also noticed that both the bridge and the thing I already had have become online instantly again. These seem to be false positives, because they do not update even after a force update with control_UpdateVehicleStatus. I’m assuming the old Thing is dead.
I can confirm the PIN is missing in the mainUI. I’m confused as to how I can validate the new binding is working. Can I force an update somehow?
edit: the items are updating now. I guess it needs a bit of TLC
Dear all,
VW Connect ID does not seem to use an S-Pin. Any other information is welcome.
Best Regards,
Yves