Can't login

[Preventlow]

Hello,

I'm getting the following error messages when trying to get info about my ID.3 using latest version of WeConnect-Cli. I've run the update which installed WeConnect 0.54, but that didn't help. Running macOS 12.6.3.

Traceback (most recent call last): File "/Users/zzz/Library/Python/3.9/bin/weconnect-cli", line 8, in sys.exit(main()) File "/Users/zzz/Library/Python/3.9/lib/python/site-packages/weconnect_cli/weconnect_cli_base.py", line 209, in main weConnect.login() File "/Users/zzz/Library/Python/3.9/lib/python/site-packages/weconnect/weconnect.py", line 182, in login self.session.login() File "/Users/zzz/Library/Python/3.9/lib/python/site-packages/weconnect/auth/we_connect_session.py", line 75, in login authorizationUrl = self.authorizationUrl(url='https://identity.vwgroup.io/oidc/v1/authorize') File "/Users/zzz/Library/Python/3.9/lib/python/site-packages/weconnect/auth/we_connect_session.py", line 96, in authorizationUrl redirect = tryLoginResponse.headers['Location'] File "/Users/zzz/Library/Python/3.9/lib/python/site-packages/requests/structures.py", line 52, in getitem__ return self._store[key.lower()][1] KeyError: 'location'

[gapthorpe]

I am hitting the same issue - had raised https://github.com/tillsteinbach/VWsFriend/issues/435

[monojk]

Same issue here, using python3.7

[tillsteinbach]

URLs in the API changed. Will fix it tomorrow.

[Preventlow]

Thank you so much!

[Preventlow]

@tillsteinbach I can confirm that the new version of WeConnect-Cli works again. Thank you so much for the quick fix and for your great work!

[monojk]

Is it available now? I still get the error. I did a pip3 install weconnect-cli --upgrade

[tillsteinbach]

You don’t see the update because python 3.7 support was dropped some months ago. You need to install at least python 3.8.

[monojk]

Thanks, it works with Python3.9 now. Btw as a heads up, I installed Python3.11 first but got an error in the PIL (pillow) component while running pip3 install weconnect-cli --upgrade complaining about a missing configuration file in pillow (I can't remember which).

[Sh0n]

Any chance to (re)add compatibility with python 3.7 for those we use weconnect-cli on Raspberry Buster ? :)

[tillsteinbach]

What is the problem with python 3.8 on raspberry?

[Sh0n]

Unless I am mistaken, in Debian 10 (Buster) the latest version available with simple command (like apt-get install python3) is python 3.7

[tillsteinbach]

Ah, ok. Yes, single command is not possible, but there are nice scripts like this one: https://itheo.tech/install-python-38-on-a-raspberry-pi

[gerhard1951]

Many thanks for your immediate update. Unfortunately it does not work in my case. Originally I worked with python 3.7. Then I updated to python 3.8 using the (useful) script you mentioned above. But weconnect-cli is still not working. The commands "pip3 install weconnect-cli" and "pip3 install weconnect-cli ---upgrade" run without any warning. Do you have an idea what could be wrong? logfile pip3 install weconnect-cli.txt

[tillsteinbach]

that looks fine. What does weconnect-cli --version say?

[gerhard1951]

Surprising: weconnect-cli 0.33.4 (using WeConnect-python 0.49.0) Using "pip3 install weconnect-cli --upgrade" didnt't change anything. Still same version.

[tillsteinbach]

then you probably have still python3.7 as your default version. You can check with python --version

[gerhard1951]

pi@raspberrypi:~ $ python --version Python 3.8.0 pi@raspberrypi:~ $

[tillsteinbach]

somehow it is still trying to use your old weconnect-cli installation. What does which weconnect-cli say?

[gerhard1951]

@.***:~ $ which weconnect-cli

/home/pi/.local/bin/weconnect-cli

@.***:~ $

Von: Till Steinbach @.> Gesendet: Mittwoch, 1. März 2023 11:10 An: tillsteinbach/WeConnect-cli @.> Cc: gerhard1951 @.>; Comment @.> Betreff: Re: [tillsteinbach/WeConnect-cli] Can't login (Issue #102)

somehow it is still trying to use your old weconnect-cli installation. What does which weconnect-cli say?

— Reply to this email directly, view it on GitHub https://github.com/tillsteinbach/WeConnect-cli/issues/102#issuecomment-1449775589 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AL435QR4YPJW7U5MRQWOA3TWZ4OBHANCNFSM6AAAAAAVJRGDFY . You are receiving this because you commented.Message ID: @.***>

[gerhard1951]

pi@raspberrypi:~ $ which weconnect-cli /home/pi/.local/bin/weconnect-cli pi@raspberrypi:~ $

[essjmcb]

Hi! I also have problems upgrading weconnect-cli with "pip3 install weconnect-cli ---upgrade" command. I can't say what's going on looking at the logs (attached). The new package is downloaded but the installation fails.

My current weconnect-cli version is "weconnect-cli 0.33.3 (usingWeConnect-python0.48.3)". I need to upgrade due to the same access problem. I am using Python ver3.9.

Thanks!

failed_weconnectupgrade.txt

[essjmcb]

Hi again! Problem solved. I had to reinstall Pydroid3 (weconnect-cli running over Android). Now working as before. Thanks!

[gerhard1951]

Problem solved! After using the command line to key-in a command I got the request to agree (again) to "... terms and conditions... " at the "myvolkswagen" homepage. I did this and everything runs as usual. Sorry for the confusion.

[Sh0n]

Ah, ok. Yes, single command is not possible, but there are nice scripts like this one: https://itheo.tech/install-python-38-on-a-raspberry-pi

Thanks but I can't do this, all my system depend to Python 2 and python 3.7 so I can't simply update python easily. Is a lot of differences bewteen lastest python3.7 compatible version and lastest version python3 compatible ?

Any chance to re-add python 3.7 compatibility in your roadmap ?

[tillsteinbach]

I definitely won’t have time for that, sorry. But you can install several python versions in parallel.

[Sh0n]

ok, I understand, I will deal with it, and try another solution.

Another question, I have the feeling that when we use password with special caracters, login failed with message "CRITICAL:There was a problem when authenticating with WeConnect: Password is invalid".

Any idea about that ? there is escape character to use ?

Thanks !

[tillsteinbach]

yes, probably some characters need to be escaped.

[gerhard1951]

Hi, since yesterday evening my weconnect-cli does not work any longer. Sending the command (which worked up to now)

"weconnect-cli --username xxxx@xxxxxxxxx.de --password xxxxxxxxx get /vehicles/WVWXXXXXXXXX/domains/charging/batteryStatus/currentSOC_pct" I get the response: "023-03-16T16:16:53+0100:CRITICAL:There was a problem when communicating with WeConnect: Status Code from WeConnect while refreshing tokens was: 400".

What might be the reason for this mentioned error?

My actual version: sudo weconnect-cli --version weconnect-cli 0.33.9 (using WeConnect-python 0.54.2)" Thanks for your help gerhard

[essjmcb]

Hi, I have the same problem. I am using weconnect-cli 0.33.8 (using WeConnect-python 0.54.1). Thanks. BR/ Juan

[tillsteinbach]

I have the suspicion that there might be again new terms and conditions to be accepted.

[essjmcb]

I do not get any terms and conditions acceptance request when login to myVolkswagen. Shall I login to a different site? Thanks.

[gerhard1951]

Same for me. This time no terms and conditions or similar to confirm at "www.volkswagen.de/de/besitzer-und-nutzer/myvolkswagen.html/__app/detailxxxxx".

[tillsteinbach]

Can you try logging out and in again inside the WeConnect ID app?

[essjmcb]

I logged out and in again with WeConnect ID app. Same error: 1772/domains/vehicleHealthInspection/maintenanceStatus/mileage_km < 2023-03-16T18:59:13+0100:CRITICAL:There was a problem when communicating with WeConnect: Status Code from WeConnect while refreshing tokens was: 400 Thanks!

[tillsteinbach]

And if you delete the token file on your harddrive?

[essjmcb]

I authenticate using user/pwd (./weconnect-cli --username xxxxxxxxxxxxxxx --password xxxxxxxxxxx get ......). I was not aware of any token, unless it is generated during the installation.. Where should I find it?

[monojk]

I also had the problem since yesterday. It is gone after rebooting my raspberry where I run the command from....

[essjmcb]

A restart on my Android phone did not help.

[tillsteinbach]

It is stored on the hardisk. You can see the path when you use the —help option. The token is obtained after login and used between several requests. It prevents that you log in every time you use weconnect-cli

[gerhard1951]

... deleting "weconnect.token" helped. Now weconnect-cli works again as usual. But what is the reason that deleting of "weconect.token" became necessary? Anyway, Till, thanks again for your great help

Gerhard

[tillsteinbach]

Seems the server did not like the token that was invalidated on server side. I will add that in such a case a new login is tried.

[essjmcb]

Also fixed here removing the token file. Many thanks for your support.

[Alkaramazov]

Hello, Just want to confirm I had the same issue (CRITICAL:There was a problem when communicating with WeConnect: Status Code from WeConnect while refreshing tokens was: 400) and that it was solved by deleting "weconnect.token" located in /tmp . Thanks for your good job and support, really appreciated !

[tillsteinbach]

Perfect. I close this one then