-
Notifications
You must be signed in to change notification settings - Fork 118
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
Hyundai Tucson PHEV Charging Issues #894
Comments
blaxer
changed the title
Hyundai Tucson PHEV Chaging Issues
Hyundai Tucson PHEV Charging Issues
Aug 19, 2024
Can you try to set the EVSE / "Pause mode" to disabled instead of sleep ? |
I have a very similar issue with status bouncing on my Chevrolet Volt. Versions same as blaxer's. But my status is bouncing one time per second. Here is some communication data from OpenEVSE console, maybe it could help?
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Having some major issues getting a 2024 Hyundai Tucson PHEV to charge correctly on a brand new OpenEVSE charger. When the vehicle is initially plugged in, the vehicle status just starts bouncing like crazy (see below). Through trial and error the only way I can get it to charge is to reset the evse and then the esp32/wifi at which point it will start charging at 6a and then I have to drag the slider to any other value and then back to 48a in order to get it up to ~36amp charging.
The real problem is that as soon as the charging has completed the status bouncing starts all over again, this seems to be keeping the car "alive" which is killing the 12volt battery and we arrive at a dead car in the morning.
I am pretty confident the charger is working fine as I have a fully electric vehicle that charges with no issues at all on the same charger. I am on EVSE 8.2.2 and using the "modified" 5.x firnware for OpenEVSE Wifi.
I would greatly appreciate any thoughts or fixes, I have read through a huge number of issues on here trying to make some sense of this but haven't found anything that seems to be the same issue.
TIA!
The text was updated successfully, but these errors were encountered: