-
-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Cannot setup intergration #711
Comments
Solved: After the update to 2025.1.1 I got the message that I had to reconfigure the intergration. So I entered my password again. But the intergration still not starting. Still the intergration was red and asked for configuration. On sending the setting it's saying 'unknow error'. looks simular as we have seen about a year ago. |
I’m having issues as well. My credentials and VW app works fine but can’t setup this integration. Anyone have any idea? |
I had the same after updating to 2025.1.1. tried several times to enter my password but the integration kept failing to login. After I logged in on my 'We connect' account on my PC and just looked arround in the setting (not actually doing something) I entered the password again and it was accepted.
It might be that I waited long enough to try again ??? I know if you access the server too often it gets blocked for some time...
BlueMail voor Android downloaden
Op 9 jan 2025 04:19, om 04:19, RobinJson90 ***@***.***> schreef:
…I’m having issues as well. My credentials and VW app works fine but
can’t setup this integration. Anyone have any idea?
--
Reply to this email directly or view it on GitHub:
#711 (comment)
You are receiving this because you authored the thread.
Message ID:
***@***.***>
|
Had same issue. Method of @Rotil66 worked for me as well. |
Ruud Robin, |
#683 (comment) solved the problem for me |
Before you post a new issue - you must first check the following (and check the boxes with an "X" below)
Environment
Describe the bug
Steps to Reproduce
Expected behavior
Screenshots
Traceback/Error logs
Debug information - all JSON responses from logfile
Additional context
Note
Issues lacking sufficient details or context may be subject to closure without prior notice. Detailed bug reports are essential for effective issue resolution. Thank you for your cooperation.
The text was updated successfully, but these errors were encountered: