@tknaller Thanks alot for your quick fix. Our ID.3 is back online. Fix works on my side with OH 3.1.
Independent of the fix, I could not make the pre-heater work. Status is shown, but I cannot trigger it to “ON”.
Just to be sure, have you put the jar and sources file in the addon directory and got the Enyaq working?
Mine is still giving me a problem.
COMMUNICATION_ERROR
API call failed
Hello @Joachim_Wilke ,
We own an ID.3 as well. The update behavior is as follows: The status values and the timestamp represents when the CAR updated the values to VW cloud last time. You can poll as often as you want from OH in the meantime without seeing a change in the timestamp.
As far as I observed, ID.3 updates data to the cloud not regularly, but on leaving and locking the car.
Short time after that, the update can be polled manually or after the OH polling interval.
During charging the Car sends updates to cloud in certain intervals.
The ID Connect app, however, seems to get updates any time upon start.
Hello @Marijn_Oudijk,
I usually stop the old binding from working before I uninstall or replace it.
The easiest way is to stop the complete openhab service:
sudo systemctl stop openhab
Then I clear the cache
sudo openhab-cli clean-cache
and put the single jar file (no sources) in the addons directory.
Finaly I start the openhab service again.
sudo systemctl start openhab
Bindings, which are installed in the addon-folder cannot be seen
in the web-interface under bindings as installed.
But you are able to add a thing using the binding.
Hope that helps. BR.
I’ll give it a new try. Thx
Confirming our ID.3 as well as our WeCharge Wallbox is online again and gets updated.
Switching climater and similar things ON/OFF never worked here for ID.3.
We have two ID.4 cars connected to the same account and it seems the ranges are not updated correctly. Sometimes the same range from one car is shown for the other, sometimes they are interchanged. Any ideas?
Hello ,
Can someone help me how to connect to the id charger Pro. The bridge for Id und car connect works fine and I have no problem to set up everything. However the wallbridge does not work at all. Do you need separate account at VW for that because everything else I use the VW ID without problems. The funny thing is that I can see my Wallbox details under https://web-home-mobile.apps.emea.vwapps.io/ After login with my ID account at the VW page.
Thanks a lot for your help
Nochmals, tolle Arbeit @tknaller und @markus7017, vielen Dank!
Schade dass beim Enyaq der Kanal “Conrol_Charge” nur “read-only” ist. In der Skoda App kann man den Ladevorgang manuell starten/beenden. Wäre extrem hilfreich wenn man das über den Kanal erreichen könnte. Danke!
Hi Sebastian,
did you create a Volkswagen ID Charge Account thing first (via “add a new thing - connectedcar”)?
Once the thing is created and online it should detect your wallbox the same way as the idvehicle and you can start to configure the items.
Yes it did and I used the same user and password for the other bridges. It is still unknown … I have no idea . Is there anything else I can check ?
Hi,
please try this version: https://github.com/tknaller/openhab-addons/releases/tag/connectedcar_snapshot_20220225
3 Likes
Awesome, thanks mate! Works perfect now! Have a great weekend!
1 Like
does the pre-heater control work for someone? car: VW Golf 7 GTE
HeaterSource shows heatingAuxiliary if i start the pre-heater with the remote or VW App.
carMoving also does not work. Anyone who can help me, please.
I’m almost there I guess.
The Enyaq account is online, but when adding the vehicle it’s not coming online. I’ve noticed there’s no reference to the bridge ( the account) in the thing. See the code below for reference
BRIDGE_UNINITIALIZED
Account Thing is not initialized!
UID: connectedcar:sevehicle:0cd35c0fc1
label: Skoda Enyak Vehicle
thingTypeUID: connectedcar:sevehicle
configuration:
pollingInterval: 15
vin: xxxxxxxxxxxxxxxx
enableAddressLookup: true
Update: I had to login the Skoda App again (enter credentials) and now it’s working. The car was found automatically after scanning.
Is that the build we. created together? Important info, because this build includes a lot of code improvements and fixes some bugs under the hood
Hello,
I have a Skoda Enyaq. After the update it now runs correctly. I have noticed only 3 small problems:
-
control#update if you activate the switch here, then the data is retrieved and the switch is automatically set back to off. unfortunately, this works only 1x, then the switch remains active and I have to deactivate and reactivate the Thing. Then I can do it again exactly 1x. I already understood that there is a limit of queries here, but here I rather guess a bug.
-
climater#climatisationState is always NULL
-
charger#MaxChargingCurrent is zero, but I can select different currents, but this has no effect. In the Skoda app it is just a switch with 2 positions (Full charging power and reduced charging power).
Do you have any ideas what can be the problem here?
Here is a hint because of the read only issues, some items are wrong in the list. With more items than specified, the status can be changed.
Thanks and greetings
1 Like
Is the Fiat implementation still on track?
I could test and support with this vendor.
There is an adapter for iobroker available: Test Adapter Fiat v0.0.x
2 Likes
Hi @tknaller,
thanks for the updated version from last week. I tried it again with my Skoda Enyaq and can confirm it updates states correctly. But not able to enable the climate yet. When I turn the switch for climateControl on, I get an error in log “API call failed” (including my VIN).
Not important to be fixed for me - I am happy with the states. But potentially at some point…
BR
SJ
Hi
i also use the iobroker solution for now.
what are you missing?