search

TA2k / ioBroker.vw-connect

ioBroker Adapter for VW We connect and Skoda connect
MIT License
93 stars 23 forks source link

Support for Skoda Enyaq? #98

Closed aslten closed 3 years ago

aslten commented 3 years ago

Just got my Skoda Enyaq and tried to configure the adapter to connect with it. Login works fine but Get vehicles fails with the error that no vehicles are found. I have the MySkoda app working ok with a connection to the car. I am new to the IoBroker platform so it may be that I have got some configuration wrong. I selected Skoda as vehicle type.

Does the adapter currently support Enyaq? If not this issue should be changed into a feature request.

If needed I can help out with testing on my car.

See attached log file

logfile.txt

TA2k commented 3 years ago

Please contact me via iobroker forum https://forum.iobroker.net/user/tombox

andig commented 3 years ago

Same problem here. The vehicles are not listed in /fs-car/usermanagement/users/v1/VW/CZ/vehicles

andig commented 3 years ago

I've just tried configuring the Enyaq as ID in https://github.com/andig/evcc which seems to work. Can you confirm?

Nvm. Faulty test.

aslten commented 3 years ago

I had a look at https://github.com/lendy007/skodaconnect. Seems to work for getting status. It seems that vehicles can be listed using https://api.connect.skoda-auto.cz/api/v2/garage/vehicles Status is returned by https://api.connect.skoda-auto.cz/api/v1/charging//status Real car data https://customer-profile.apps.emea.vwapps.io/v2/customers//realCarData Still needs to find endpoint for getting status of climatisation and how to control charging and climatisation.

andig commented 3 years ago

I've not dug in in detail yet, but it seems to use the normal VW login flow and then the Skoda "native" api. When I try that to retrieve the vehicles I get:

GET /api/v2/garage/vehicles HTTP/1.1
Host: api.connect.skoda-auto.cz
Accept: application/json
Authorization: Bearer ey...

HTTP/2.0 401 Unauthorized

{"error":"invalid_token","error_description":"Invalid JOSE Header kid (MBB01)"}

Couldn't figure out yet what the difference in the login flow is apart from other client/x-client id?

Update

Figured it out. There are indeed two different tokens at play, both obtained by doing a full login flow. Client id 7f045eee-7003-4379-9968-9355ed2adb06 gives access to the car apis at api.connect.skoda-auto.cz while Client id f9a2359a-b776-46d9-bd0c-db1904343117 is exclusively used to retrieve the list of vehicles.

heckmic commented 3 years ago

Ok, so what do i have to do to get the Enyaq working?

andig commented 3 years ago

Ok, so what do i have to do to get the Enyaq working?

It has a unique login flow and api, see https://github.com/TA2k/ioBroker.vw-connect/issues/98#issuecomment-841791870

heckmic commented 3 years ago

Any News?

TA2k commented 3 years ago

If you provide me login data I can add this

heckmic commented 3 years ago

If you provide me login data I can add this

Ok, contact me (german)

TA2k commented 3 years ago

On github you can install a version which supports Skoda Enyaq please install and test the new version. Please test the objects under settings and remote if changing is working properly

TA2k commented 3 years ago

added in 0.0.36