search

TA2k / ioBroker.vw-connect

ioBroker Adapter for VW We connect and Skoda connect
MIT License
90 stars 22 forks source link

Cupra Born Internal Server error 500 #301

Open gz2k2 opened 6 months ago

gz2k2 commented 6 months ago

Describe the bug

Cupra Born is not working anymore.

To Reproduce
Steps to reproduce the behavior: Just add Cupra Born and start Adapter

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots & Logfiles 


vw-connect.0 | 2023-12-25 11:11:45.589 | error | Get Vehicles Failed
vw-connect.0 | 2023-12-25 11:11:45.589 | error | 500
vw-connect.0 | 2023-12-25 11:11:45.589 | error | {"code":"internal-error","message":"Internal server error","rootMessage":null,"timestamp":"2023-12-25T10:11:45.580337079Z"}
vw-connect.0 | 2023-12-25 11:11:42.812 | info | Login successful
vw-connect.0 | 2023-12-25 11:11:42.672 | debug | Error: Invalid protocol: cupra:
vw-connect.0 | 2023-12-25 11:11:42.362 | debug | {"date":"Mon,  25 Dec 2023 10:11:42  GMT","content-length":"0","connection":"close","apigw-requestid":"QfpGwhnyFiAEMgg=","x-content-type-options":"nosniff","x-xss-protection":"0","cache-control":"no-cache,  no-store, max-age=0,  must-revalidate","pragma":"no-cache","expires":"0","strict-transport-security":"max-age=31536000;  includeSubDomains;  preload","x-frame-options":"DENY","location":"https://identity.vwgroup.io/oidc/v1/oauth/sso?clientId=3c756d46-f1ba-4d78-9f9a-cff0d5292d51@apps_vw-dilab_com&relayState=fb57f0176ab8c9f184f683e36aa1a493278c04b4&userId=4e8e1e4d-c4df-4bfb-818d-5186d8996a2c&HMAC=2df96860ce0bffbaf5a17875202fc1556e01f58d5ce07ac21b6103ab2cbe2ecb","content-language":"en-US"}
vw-connect.0 | 2023-12-25 11:11:42.362 | debug | ""
vw-connect.0 | 2023-12-25 11:11:42.122 | debug | emailPasswordForm2
vw-connect.0 | 2023-12-25 11:11:41.905 | debug | parseEmailForm
vw-connect.0 | 2023-12-25 11:11:41.499 | info | Login in with seatcupra
vw-connect.0 | 2023-12-25 11:11:41.482 | info | starting. Version 0.5.1 in /opt/iobroker/node_modules/iobroker.vw-connect, node: v18.19.0, js-controller: 5.0.16

Versions:

Additional context
Add any other context about the problem here.

g-l-i-t-z-i commented 6 months ago

Same Problem

Adapter version: 0.5.1 JS-Controller version: 5.0.17 Node version: 18.19.0 Operating system: Linux Virtual Machine

` vw-connect.0 2024-01-03 16:52:23.664 error get seat status Failed

vw-connect.0 2024-01-03 16:52:23.664 error {"code":"internal-error","message":"Internal server error","rootMessage":null,"timestamp":"2024-01-03T15:52:23.655644854Z"}

vw-connect.0 2024-01-03 16:52:23.663 error 500

vw-connect.0 2024-01-03 16:52:19.611 info Found 1 vehicles

vw-connect.0 2024-01-03 16:52:19.303 info Login successful

vw-connect.0 2024-01-03 16:52:17.685 info Login in with seatcupra

vw-connect.0 2024-01-03 16:52:17.679 info starting. Version 0.5.1 (non-npm: ta2k/ioBroker.vw-connect) in /opt/iobroker/node_modules/iobroker.vw-connect, node: v18.19.0, js-controller: 5.0.17`

disaster123 commented 6 months ago

Same for me


vw-connect.0
2024-01-07 15:51:40.099 error   get seat status Failed

vw-connect.0
2024-01-07 15:51:40.099 error   {"code":"internal-error","message":"Internal server error","rootMessage":null,"timestamp":"2024-01-07T14:51:11.760836385Z"}

vw-connect.0
2024-01-07 15:51:40.098 error   500

vw-connect.0
2024-01-07 15:51:37.739 error   get cupra status Failed

vw-connect.0
2024-01-07 15:51:37.739 error   {"code":"internal-error","message":"Internal server error","rootMessage":null,"timestamp":"2024-01-07T14:51:09.399779552Z"}

vw-connect.0
2024-01-07 15:51:37.738 error   500

vw-connect.0
2024-01-07 15:51:37.573 info    Found 1 vehicles

vw-connect.0
2024-01-07 15:51:36.543 info    Login successful

vw-connect.0
2024-01-07 15:51:34.844 info    Login in with seatcupra
TA2k commented 6 months ago

Ich bräuchte ein Login um das zu fixen tombox2020@gmail.com

disaster123 commented 6 months ago

Es scheint "nur" am Token zu liegen. Im Debug Log sieht es so aus, als wenn der 500er ausgelöst wird, dann ein Token Refresh statt findet und es dann klappt.


vw-connect.0
2024-01-07 15:55:12.442 debug   {"status":{"battery":{"carCapturedTimestamp":"2024-01-06T20:01:21Z","currentSOC_pct":93,"cruisingRangeElectric_km":377},"charging":{"carCapturedTimestamp":"2024-01-06T20:01:21Z","chargingState":"notReadyForCharging","chargeType":"invalid","chargeMode":"manual","chargingSettings":"default","remainingChargingTimeToComplete_min":0,"chargePower_kW":0,"chargeRate_kmph":0},"plug":{"carCapturedTimestamp":"2024-01-06T19:59:29Z","plugConnectionState":"disconnected","plugLockState":"unlocked","externalPower":"unavailable"}}}

vw-connect.0
2024-01-07 15:55:11.687 debug   Token Refresh successful

vw-connect.0
2024-01-07 15:55:11.503 debug   Token Refresh started

vw-connect.0
2024-01-07 15:55:11.503 error   get seat status Failed

vw-connect.0
2024-01-07 15:55:11.502 error   {"code":"internal-error","message":"Internal server error","rootMessage":null,"timestamp":"2024-01-07T14:54:43.163018225Z"}

vw-connect.0
2024-01-07 15:55:11.502 error   500
nicomania commented 3 months ago

Bei mir funktioniert der Adapter mit dem Cupra Born durchgehend prima. v0.5.4 Ich habe wegen fehlender Datenpunkte @TA2k hier #313 mein Login angeboten. Vielleicht kann er dieses issue gleich mit fixen.