-
Notifications
You must be signed in to change notification settings - Fork 10
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
Login Error #46
Comments
It's all fine for me so we can assume the integration is working fine. Taking the integration out of the picture, can you connect via the native My CUPRA app OK? How about your My CUPRA account on their website, is that OK? |
I can log into my Cupra app without any problems and it works perfectly in ioBroker. I have Seat Integration running in parallel on my HA and it also works without any problems. |
and now: File "/usr/local/lib/python3.12/site-packages/weconnect_cupra/api/cupra/elements/charging_status.py", line 32, in init |
I suspect you're hitting some incompatabilities with your newer car here. Do you have all of the capabilities enabled in the official app? Can you run the integration in debug and let me have some of the trace? Add something like this to configuration.yaml and restart:
Feel free to obfuscate VIN or other personal data as needed. |
Now I'm confused xD where can I set something in the app/enable functions? |
Open the app, scroll down and go to "service management". Make sure everything is activated. Also make sure that the app is not reported that the vehicle is "offline" and is showing sensible data. |
VSSZZXXXXXXXXXX70 = Cupra Born 2024-04-10 10:58:45.429 WARNING (SyncWorker_7) [homeassistant.loader] We found a custom integration cupra_we_connect which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant |
everything was correct 👍 |
Lot of nulls that don't look right here. Looks like your car is plugged in - might be worth unplugging it, waiting until it updates on the official app and then capture some more debug around this to see if it works without error. |
exactly seat is plugged in and born not |
OK, that doesn't work yet, I'll make a new log this evening and post it here 2024-04-10 12:21:07.853 DEBUG (SyncWorker_20) [weconnect_cupra] Retrieved data from url: https://ola.prod.code.seat.cloud.vwgroup.com/vehicles/VSSZxxxxxx301/charging/status |
2024-04-10 18:49:48.064 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration cupra_we_connect which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant |
I had the same issue with the login today. |
Hello lucas-dumartin, |
same error here, login failed, I tried:
none of them worked, maybe the problem was updating HA? 😕 |
I have the same problem "Unerwarteter Fehler" when I try to login Homeassistant |
I experience the same issue still. I had it set up and working, but my sensors have become unavailable. When I want to add another instance and login with my credentials, I get an 'Unexpected error' or 'Onverwachte fout'. In the logging I see something like: File "/usr/local/lib/python3.12/site-packages/weconnect_cupra/api/cupra/auth/my_cupra_session.py", line 191, in doWebAuth |
I have Cupra Born (v4 2024) the integration worked once and since then not anymore, I can't log in, the same error always comes up
The text was updated successfully, but these errors were encountered: