Skip to content
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

Please add e-up support #615

Open
ra2806 opened this issue Mar 11, 2024 · 0 comments
Open

Please add e-up support #615

ra2806 opened this issue Mar 11, 2024 · 0 comments

Comments

@ra2806
Copy link

ra2806 commented Mar 11, 2024

vwsfriend works pretty well with my id.3 but I also have an e-up which is not (yet) well supported by vwsfriend.
The main problem seems to be that every time the e-up goes online, vwsfriend recognises this as the beginning of a new charging session. I checked this with weconnect-cli which shows that the plug status is alway "locked"
example:
python weconnect-cli.exe --username xxx --password xxx get /vehicles/xxx/domains/charging

[batteryStatus] (last captured 2024-03-10T09:25:26+00:00)
        Current SoC: 36%
        Range: 89km
[chargingStatus] (last captured 2024-03-09T07:58:13+00:00)
        State: notReadyForCharging
        Remaining Charging Time: 20 minutes
[chargingSettings] (last captured 2023-11-03T16:30:02+00:00)
        Maximum Charge Current AC: maximum
[chargeMode]
        Error:  Error 4111: Bad Gateway
                info: Upstream service responded with an unexpected status. If the problem persists, please contact our support.
                timestamp: 2024-03-10 15:35:51+00:00
[plugStatus] (last captured 2024-03-09T07:58:13+00:00)
        Plug: **disconnected, locked**, External Power: unavailable, Led color: none

when the car is really charging the plug status is:

[plugStatus] (last captured 2024-03-11T15:09:50+00:00)
        Plug: **connected, locked**, External Power: ready, Led color: none

The result of this behaviour is that trips are not recorded as trips but as "open end" charging sessions. The e-up plug status always seems to be "locked" (even if it is disconnected - which does not make sense and confuses vwsfriend).

I would be very grateful if this could be fixed. I could provide more information if needed. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant