Charger Logic Error - warum, was ich machen kann? EVCC, CFOS, Peugeot e-208

[Glexu]

Hallo an Alle EVCC-Fan

Bin relativ neu in EVCC-Gruppe. Seit eine woche habe ich erste machine erstellt uns teste ich verschiedene Funktionen und Möglichkeiten.
Erstmal alles funktioniert aber sind einige kleinigkeiten wo ich ratlos bin....

• während Ladevorgang sehe ich immer Ausrufezeichen oben rechts mit solche Info:

Garage: charger logic error: current mismatch (got 10.9A measured, expected 6A)
vor 14 Sekunden
Garage: charger logic error: current mismatch (got 10.6A measured, expected 6A)
vor 23 Sekunden
Garage: charger logic error: current mismatch (got 9A measured, expected 7.37A)
vor 47 Sekunden
Garage: charger logic error: current mismatch (got 10.1A measured, expected 6.45A)
vor 53 Sekunden
Garage: charger logic error: current mismatch (got 11.6A measured, expected 6A)
vor 1 Minute
Garage: charger logic error: current mismatch (got 8.9A measured, expected 6A)
vor 1 Minute
Garage: charger logic error: current mismatch (got 12.2A measured, expected 8.73A)
vor 1 Minute
Garage: charger logic error: current mismatch (got 9.3A measured, expected 6A)
vor 2 Minuten
Garage: charger logic error: current mismatch (got 8.4A measured, expected 7.11A)
vor 2 Minuten
Garage: charger logic error: current mismatch (got 9.3A measured, expected 6A)

Was ich einstellen / verbessern muss um sowas zu vermeiden?

Mein config shiet so aus:

`# open evcc at http://evcc.local:7070
network:
schema: http
host: evcc.local # .local suffix announces the hostname on MDNS
port: 7070
mqtt:
broker: 192.168.178.6:1883
log: debug
levels:
cache: error
tariffs:
grid:
type: template
template: tibber
token: ********************************************
#unique installation id
plant: 5cc*******************************************850bfeb6fbf37d6c5
#trial token, valid until 2024-08-23
sponsortoken: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJldmNjLmlvIiwic3ViIjoidHJpYWwiLCJleHAiOjE3MjQ0MDM2MDAsI
interval: 3s # control cycle interval
site:
title: Casa
meters:
pv: pv
battery: battery
grid: grid

meters:

• name: grid
  type: custom
  power:
  source: mqtt
  topic: solar_assistant/inverter_1/grid_power_ct/state

• name: pv
  type: custom
  power:
  source: mqtt
  topic: solar_assistant/inverter_1/pv_power/state

• name: battery
  type: custom
  power:
  source: mqtt
  topic: solar_assistant/total/battery_power/state
  scale: -1
  soc:
  source: mqtt
  topic: solar_assistant/total/battery_state_of_charge/state

vehicles:

• name: e208
  type: template
  template: peugeot
  title: Peugeot e-208
  user: ********
  password: *******
  accessToken: *********
  refreshToken: **********
  vin: ********
  capacity: 46
  phases: 3
  icon: car
  mode: pv
  minCurrent: 6
  maxCurrent: 16
  priority: 1

chargers:

• type: template
  template: cfos
  host: 192.168.178.10
  name: cfos
  loadpoints:
• title: Garage
  charger: cfos`

[StefanSchoof]

interval: 3s

Das ist schon sehr kurz. Probiere mal ob die Fehler auch bei 30s auftreten und dann kannst du langsam wieder runter gehen. Am besten nur ein bisschen und dann ein paar Tage laufen lassen und schauen, ob es irgendwelche Auffälligkeiten gibt.

[Glexu]

Ok, probiere ich aus. Dane für den Tip

[7even-up]

And? Did it solve the issue? I have the same and am worried if it can harm my car or charger. Is there a risk in harming the car or charger? Is it and information delay or a setting delay?

[mfuchs1984]

Default interval is 30 seconds, in standard setups, there is no reason to modify it. No, it cannot harm anything, it is just the interval in which evcc calculates new charge powers and sends them to the charger. In case the interval is too short, you will see those error messages because the charger / car cannot adjust the power so fast.

In case you have this issue even with the default settings, you should open a separate discussion including your configuration file and complete log files.

[Glexu]

I changed to 30 seconds and these errors are less but still appear. I don't have time to test longer at the moment. Don't worry - you won't damage the car or the charger.

[typxxi]

Default interval is 30 seconds, in standard setups, there is no reason to modify it. No, it cannot harm anything, it is just the interval in which evcc calculates new charge powers and sends them to the charger. In case the interval is too short, you will see those error messages because the charger / car cannot adjust the power so fast.

In case you have this issue even with the default settings, you should open a separate discussion including your configuration file and complete log files.

@mfuchs1984
I have the same issue out of nowhere after the new 1.30.13 had been working fine with the Pulsar Plus Wallbox and now there is such warning. Meanwhile I had learned to ignore all warning signs unless they are red.

This one was orange and the only change in the past 2 or 3 days after the system was finally working again was the downgrade of the e-GOLF from 3 to 2 phases in the vehicle section which I guess you had recommanded to me in a different topic .

But I have checked the intervall: 12s
and increased the meterintervall: 10s to also 12s to hope to avoid this error I had gotten out of nowhere.

Garage: charger logic error: current mismatch (got 11.2A measured, expected 8.73A)

My usual modbus update rate on the growatt inverter receiving smartmeter data from the SDM630 is 8 seconds on a 10 year old windows laptop running growatts installer software called shinebus. So far over the past 100 days that has been reliable since I had installed the LFP battery.

Keep fingers crossed and I have also noted in my yaml that in case of such a mismatch error I would have to increase the meter values a bit.

Right or did I miss something ?

[mfuchs1984]

No need to change the meterinterval, just set the general interval to 30.

[typxxi]

interval

Really ?
I had a general intervall of 12s and since I had upgraded the meterintervall from 10 to 12s too I had no more issues so far and there was maybe a 3 min break at max when the addon restarted while the car was still charging.

For now I will let the values leave as they are and write in my yaml that in case of further issues or error with not matching Amp I have to increase the general time more.

thanks a lot