-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
when the car is really charging the plug status is:
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!
The text was updated successfully, but these errors were encountered: