Closed jpwenzel closed 8 months ago
Recently (I assume after the upgrade to 0.124.7?) this leads to a malfunction status in the wallbox (red indicator ring).
Similar to get configuration, that sounds like another bug in the Elvi firmware, probably triggered by https://github.com/evcc-io/evcc/pull/12459. We could make that configurable (which would add yet another variable) but I'd rather prefer to have Elvi fix their boxes.
What does Elvi support say?
@jpwenzel could you also check if 0.124.6 works for you? Then we'd know that #12459 causes this.
@jpwenzel could you also check if 0.124.6 works for you? Then we'd know that #12459 causes this.
Yes, I will downgrade and check.
Works as expected with version 0.124.6. I can even hear the socket unlock shortly after switching to "Off" mode. No red ring on the wallbox.
Logs: evcc-0.124.6.log
So this is triggered by https://github.com/evcc-io/evcc/pull/12459. Afaikt nothing forbids #12459. It's up to Elvi to fix their software or explain why this should be an error condition.
/cc @cheerfulalex sieht aus als müssten wir das zurück drehen :(
I can even hear the socket unlock shortly after switching to "Off" mode.
This should NOT happen as the session should not be closed in this case. Session should only be terminated by unplugging of the car. The car releases its cable and unplugging it should stop the session and release the cable at the station side (if not fixed cable setup).
Yes, we know that this is the old OCPP behavior but the new behavior is better, more "correct" and streamlined with other Modbus implementations. The session is paused now but not ended.
@premultiply es nutzt ja nix- mindestens ABB und Elvi haben Probleme damit. Wir müssen es wohl optional machen :(
Closed in https://github.com/evcc-io/evcc/commit/1580857163d006d744319aaf79570175161ecb50, follow-up in https://github.com/evcc-io/evcc/pull/12861.
What does Elvi support say?
Opened a ticket with them, waiting for reply:
I am running my Elvi EVBox wallbox connected to the evcc OCPP implementation. During testing, we realized that there is in issue in the implementation of the setChargingProfile method.
In evcc, we’d like to use „zero charging profile“ to pause/end charging. That profile is sent to EVBox.
When the user now unplugs their car (on the vehicle side), the charger turns into an error state (red ring) and locks up. Cable is not released, Bluetooth connection is not possible. In order to recover, one has to power cycle by flipping the circuit breaker.
Please pass this on to your product development/engineering team and ask them for a fix.
For the record: I have just updated to 0.124.10 and saw that the EVBox charger goes into error state even in Min+PV when the cable is unplugged on vehicle side!
I never noticed this behavior before, because I used to manually set charging to "off" in the UI before unplugging and that always worked fine.
As sad this is for the Elvi software it's actually good news. The 0A Ocpp change is not part of 0.124.10, so it seems we can re-apply it ;) /cc @cheerfulalex
What does Elvi support say?
Well...
EVCC has not been network integrated with our backend system server management platform EVBox Everon and therefore is not fully compatible with our API unless fully integrated. This is a process only available for EVBox partners, please contact your asset account owner at Fastplug Energy GmbH for further procedure on this matter.
I have no idea what that should mean. Ocpp is a standard, not something you need to get onboarded on…
I think the poor support guy had no idea what I was talking about. I'll try to reach out to some more technical staff at EVBox through LinkedIn... HTH.
@jpwenzel Did you hear back from them yet?
No, they are absolutely unresponsive.
I am so frustrated right now that I am actually considering throwing the EVBox away and to tell anyone to not even consider one of their (not) "OCPP compliant" products.
Describe the bug
After stopping the charging process on our Hyundai Kona in Min+PV mode (stopped by setting charge mode to "Off" in the UI), I unplug the cable from the car first, and then from the EVBox socket.
Recently (I assume after the upgrade to 0.124.7?) this leads to a malfunction status in the wallbox (red indicator ring).
As a result, the cable is not released, and in order to unlock it, the wallbox needs to be either rebooted through the smartphone app or by power cycling it in the breaker box.
Steps to reproduce
Configuration details
Log details
What type of operating system are you running?
Docker container
Version
0.124.7