Alfen Eve: invalid status: E

[hardoverflow]

Describe the bug

After updated from 0.117.4 to 0.118.0 i got the the following error message:

Jun 10 13:26:33 raspberrypi evcc[1426]: [lp-1  ] ERROR 2023/06/10 13:26:33 charger: invalid status: E
Jun 10 13:26:43 raspberrypi evcc[1426]: [lp-1  ] ERROR 2023/06/10 13:26:43 charger: invalid status: E
Jun 10 13:26:53 raspberrypi evcc[1426]: [lp-1  ] ERROR 2023/06/10 13:26:53 charger: invalid status: E

Wallbox: Alfen Eve Single Pro-line 3PH T2 (NG9xx 6.3.0-4185-B) with feature "Active Load Balancing"

Steps to reproduce

Update from 0.117.4 to 0.118.0.

Configuration details

---
network:
  schema: http
  host: ***redacted***
  port: 7070

log: info
levels:
  cache: error

plant: ***redacted***

interval: 10s

meters:
  - type: template
    template: solaredge-inverter
    id: 1
    host: ***redacted***
    port: 1502
    usage: grid
    modbus: tcpip
    name: grid1
  - type: template
    template: solaredge-inverter
    id: 1
    host: ***redacted***
    port: 1502
    usage: pv
    modbus: tcpip
    name: pv1

chargers:
  - name: alfen
    type: template
    template: alfen
    modbus: tcpip
    id: 1
    host: ***redacted***
    port: 502
loadpoints:
  - title: Carport
    charger: alfen
    mode: pv
    phases: 0
    mincurrent: 6
    maxcurrent: 16
    resetOnDisconnect: true

tariffs:
  currency: EUR
  grid:
    type: fixed
    price: 0.4588
  feedin:
    type: fixed
    price: 0.0673
  co2:
    type: grünstromindex
    zip: ***redacted***

site:
  title: My home
  meters:
    grid: grid1
    pv: pv1

modbusproxy:
  - port: 1502
    uri: ***redacted***:1502

mqtt:
  broker: localhost:1883
  topic: evcc
  user: evcc
  password: ***redacted***

influx:
  url: ***redacted***
  database: evcc
  token: ***redacted***
  org: ***redacted***

telemetry: true

sponsortoken: ***redacted***

Log details

root@raspberrypi:~# evcc --log debug
[main  ] INFO 2023/06/10 13:30:40 evcc 0.118.0
[main  ] INFO 2023/06/10 13:30:40 using config file: /etc/evcc.yaml
[main  ] INFO 2023/06/10 13:30:40 starting ui and api at :7070
[db    ] INFO 2023/06/10 13:30:50 using sqlite database: /root/.evcc/evcc.db
[mqtt  ] INFO 2023/06/10 13:30:50 connecting evcc-1382451112 at tcp://localhost:1883
[mqtt  ] DEBUG 2023/06/10 13:30:50 tcp://localhost:1883 connected
[proxy-1502] DEBUG 2023/06/10 13:30:50 modbus proxy for 10.189.21.220:1502 listening at :1502
[alfen ] DEBUG 2023/06/10 13:30:52 detected 3p alfen
[site  ] DEBUG 2023/06/10 13:30:52 co2 tariff
[site  ] INFO 2023/06/10 13:30:52 site config:
[site  ] INFO 2023/06/10 13:30:52   meters:      grid ✓ pv ✓ battery ✗
[site  ] INFO 2023/06/10 13:30:52     grid:      power ✓ energy ✗ currents ✗
[site  ] INFO 2023/06/10 13:30:52     pv 1:      power ✓ energy ✗ currents ✗
[lp-1  ] INFO 2023/06/10 13:30:52 loadpoint 1:
[lp-1  ] INFO 2023/06/10 13:30:52   mode:        pv
[lp-1  ] INFO 2023/06/10 13:30:52   charger:     power ✓ energy ✓ currents ✓ phases ✓ wakeup ✗
[lp-1  ] INFO 2023/06/10 13:30:52   meters:      charge ✓
[lp-1  ] INFO 2023/06/10 13:30:52     charge:    power ✓ energy ✓ currents ✓
[site  ] DEBUG 2023/06/10 13:30:52 co2 tariff
[lp-1  ] DEBUG 2023/06/10 13:30:52 phase timer inactive
[lp-1  ] DEBUG 2023/06/10 13:30:52 pv timer inactive
[lp-1  ] DEBUG 2023/06/10 13:30:52 guard timer inactive
[site  ] DEBUG 2023/06/10 13:30:53 ----
[lp-1  ] DEBUG 2023/06/10 13:30:53 charge power: 0W
[site  ] DEBUG 2023/06/10 13:30:53 co2 tariff
[site  ] DEBUG 2023/06/10 13:30:53 pv power: 6829W
[site  ] DEBUG 2023/06/10 13:30:53 grid power: -6448W
[site  ] DEBUG 2023/06/10 13:30:53 site power: -6448W
[lp-1  ] DEBUG 2023/06/10 13:30:53 charge currents: [0 0 0]A
[lp-1  ] DEBUG 2023/06/10 13:30:53 charge meter total import: 10.322kWh
[lp-1  ] ERROR 2023/06/10 13:30:53 charger: invalid status: E

What type of operating system are you running?

Linux raspberrypi 6.1.29-v8+ #1652 SMP PREEMPT Wed May 24 14:46:55 BST 2023 aarch64 GNU/Linux

Version

evcc version 0.118.0

[200Puls]

Im encoutering the same issue after Update.

Using ABB Terra AC with OCPP.

[hardoverflow]

May be related to #8073

[andig]

That is intentional since evcc doesn't handle status E at all. According to https://www.goingelectric.de/forum/viewtopic.php?t=36700&start=10:

In der Anleitung von Mennekes liest man für Zustand E "Kurzschluß in der Leitung".

/cc @premultiply

[premultiply]

Ja, was soll man da auch machen?
Da ist der Anwender erstmal gefragt die Sache zu prüfen und das Problem ggf. manuell vor Ort am Ladepunkt zu lösen.

[hardoverflow]

I have checked the wallbox. I can confirm that it works perfectly. Screenshot attached. Next steps for me:

• take a look into manual
• contact customer support

[hardoverflow]

A quick view in the Implementation of Modbus Slave TCPIP for Alfen NG9xx platform.pdf section 3.4.1.

IMHO this is not an "Error". Only state "F" is an error state. Does anyone see this differently?

[andig]

IMHO this is not an "Error". Only state "F" is an error state. Does anyone see this differently?

Im Zweifel gilt der Standard.

Aus https://evsim.gonium.net:

Die Zustände E und F sind Fehlerzustände, in denen die Stromversorgung zum Elektroauto unterbrochen wird. E zeigt einen Kurzschluss zwischen CP und PE an. Der Zustand F kennzeichnet einen Ausfall der Wallbox: Zwischen CP und PE besteht keine Verbindung.

Selbst wenn E kein Fehlerzustand wäre: wir wüssten nichts damit anzufangen. Das ist jetzt ein echtes Dilemma :(

[andig]

@hardoverflow Vorschlag: Frage an den Support: WB sagt E, laut Standard ist E Fehler, was ist los...

[hardoverflow]

I have contacted the Alfen Support with the following content:

Greetings,

i use a smart charging management software (evcc.io) together with Alfen Eve Single-line Pro and LBA (Load Balancing Active) and i have a general question about the standard.

The thing is, that the wallbox default mode 3 listening state (without a car connection) is “State E”. I found different meanings or statements about the states. First i have found, that State E and F are error states.

“The states E and F are fault states in which the power supply to the electric car is interrupted. E indicates a short circuit between CP and PE. State F indicates a failure of the wallbox: There is no connection between CP and PE.”

https://evsim.gonium.net/#der-control-pilot-cp

In the Alfen documentation about Modbus TCP/IP section 3.4.1. (table) i have found that “State F” is only a error state.

Implementation of Modbus Slave TCPIP for Alfen NG9xx platform.pdf

Could you please bring a little light into the dark here? Which standard do you adhere to? Or is there a deviation from the standard here and why? Where can I read about this? (Reference of ..)

Many thanks to you!

[engelchrisi]

Same issue happy with Innogy Ebox since 1.18. A regression.
Because of the state it seems that the box never realizes that a cable was unlocked/removed and therefore always "thinks" that it is loading.

[hardoverflow]

Just ask ChatGPT. (Without rating!)

[premultiply]

Klingt solide ist aber völliger Blödsinn der sich in keinem Standard abbildet.