Charging session reported by the EVCC doubles the energy reported by the charger template "evsewifi".

[pjpeartree]

Hi all,

I require assistance in understanding why the charging session reported by the EVCC shows double the energy compared to what is reported by the "evsewifi" charger template.

The EVCC Charging Session reports 32.0 kWh, in 3h06min (~10.3kw). This value isn't correct. I only have available ~5.1kW.

Total Energy (16.0kWh) and Power usage(~5.12) during the charging session reported by evsewifi charge into HA;

Car state at end of charging 67% SoC:

EVCC logs:

docker exec evcc evcc -l debug vehicle

[main  ] INFO 2024/04/05 07:19:07 evcc 0.124.10 (d47f97d2)
[main  ] INFO 2024/04/05 07:19:07 using config file: /etc/evcc.yaml
leaf
----
.....Soc:      67%
Capacity:      40.0kWh
Charge status: B
Range:         164km
Finish time:   not available
OnIdentified:  Mode:pv
Features:      []

docker exec evcc evcc -l debug meter
[main  ] INFO 2024/04/05 07:21:02 evcc 0.124.10 (d47f97d2)
[main  ] INFO 2024/04/05 07:21:02 using config file: /etc/evcc.yaml
grid
----
Power: 210W

pv
--
Power: 70W

battery
-------
Power:    0W
Soc:      20%
Capacity: 14.0kWh

docker exec evcc evcc -l debug charger
[main  ] INFO 2024/04/05 07:22:10 evcc 0.124.10 (d47f97d2)
[main  ] INFO 2024/04/05 07:22:10 using config file: /etc/evcc.yaml
Power:          0W
Energy:         0.0kWh
Current L1..L3: 0A 0A 0A
Voltage L1..L3: 0V 0V 0V
Charge status:  B
Enabled:        false

evcc log file:

_evcc_logs_log.txt

evcc.yaml:

# site describes the EVU connection, PV and home battery
site:
  - title: EVCC # display name for UI
    meters:
      grid: grid # grid meter
      pv: pv # list of pv inverters/ meters
      battery: battery # battery meter
    residualPower: 300  
    # bufferSoc: 70 # ignore home battery discharge above soc (empty to disable) !!! DEPRECATED IN YAML
    # prioritySoc: 60 # give home battery priority up to this soc (empty to disable) !!! DEPRECATED IN YAML
    # bufferStartSoc: 80 # When the house battery has reached Soc ​​the charging process starts  
    maxGridSupplyWhileBatteryCharging: 50

# loadpoint describes the charger, charge meter and connected vehicle
loadpoints:
  - title: Carport # display name for UI
    charger: evse # charger
    vehicle: modely
    mode: pv # set default charge mode, use "off" to disable by default if charger is publicly available
    soc:
      # polling defines usage of the vehicle APIs
      # Modifying the default settings it NOT recommended. It MAY deplete your vehicle's battery
      # or lead to vehicle manufacturer banning you from API use. USE AT YOUR OWN RISK.
      poll:
        # poll mode defines under which condition the vehicle API is called:
        #   charging: update vehicle ONLY when charging (this is the recommended default)
        #   connected: update vehicle when connected (not only charging), interval defines how often
        #   always: always update vehicle regardless of connection state, interval defines how often (only supported for single vehicle)
        mode: connected
        # poll interval defines how often the vehicle API may be polled if NOT charging
        interval: 120m
      estimate: true # set false to disable interpolating between api updates (not recommended)
    enable: # pv mode enable behavior
      delay: 2m # threshold must be exceeded for this long
      threshold: 0 # grid power threshold (in Watts, negative=export). If zero, export must exceed minimum charge power to enable
    disable: # pv mode disable behavior
      delay: 2m # threshold must be exceeded for this long
      threshold: 0 # maximum import power (W)
    guardDuration: 5m # switch charger contactor not more often than this (default 5m)
    # phases: 1 # electrical connection (normal charger: default 3 for 3 phase, 1p3p charger: 0 for "auto" or 1/3 for fixed phases)
    # minCurrent: 6 # minimum charge current (default 6A)
    # maxCurrent: 28 # maximum charge current (default 16A)

# charger definitions
# name can be freely chosen and is used as reference when assigning charger to vehicle
# for documentation see https://docs.evcc.io/docs/devices/chargers
chargers:
  - name: evse
    type: template
    template: evsewifi
    host: 192.168.1.120 # IP-Adresse oder Hostname

# meter definitions
# name can be freely chosen and is used as reference when assigning meters to site and loadpoints
# for documentation see https://docs.evcc.io/docs/devices/meters
meters:
  - name: grid
    type: custom
    power: # Leistung (W)
      source: mqtt # Plugin Typ
      topic: homeassistant/sensor/gridmeter_power/state
      # timeout: 300s # don't accept values older than timeout
      scale: 1.0 # floating point factor applied to result, e.g. for Wh to kWh conversion

  - name: pv
    type: custom
    power: # Leistung (W)
      source: mqtt # Plugin Typ
      topic: homeassistant/sensor/pv_power/state
      # timeout: 300s # don't accept values older than timeout
      scale: 1.0 # floating point factor applied to result, e.g. for Wh to kWh conversion
    
  - name: battery
    type: custom
    power: # Leistung (W)
      source: mqtt # Plugin Typ
      topic: homeassistant/sensor/battery_power/state
      # timeout: 300s # don't accept values older than timeout
      scale: 1.0 # floating point factor applied to result, e.g. for Wh to kWh conversion
    soc: # Batterie SOC (%)
      source: mqtt # Plugin Typ
      topic: homeassistant/sensor/battery_state_of_charge/state
      # timeout: 300s # don't accept values older than timeout
    capacity: 14.0 # optional Batterie Kapazität (kWh)

vehicles:
  - name: leaf
    type: template
    template: nissan
    title: Nissan Leaf # Wird in der Benutzeroberfläche angezeigt # Optional
    user: secret # Benutzerkonto (bspw. E-Mail Adresse, User Id, etc.)
    password: secret # Passwort des Benutzerkontos (bei führenden Nullen bitte in einfache Hochkommata setzen)
    vin: secret # Erforderlich, wenn mehrere Fahrzeuge des Herstellers vorhanden sind # Optional
    capacity: 40 # Akku-Kapazität in kWh # Optional
    # phases: 1
    mode: pv
    # minCurrent: 6
    # maxCurrent: 28
    icon: car
  - name: modely
    type: template
    template: tesla-command
    title: Tesla Model Y # Wird in der Benutzeroberfläche angezeigt (optional)
    accessToken: secret
	refreshToken: secret 
	vin: secret 
	capacity: 75 # Akkukapazität in kWh (optional) 
    # phases: 1
    mode: pv
    # minCurrent: 6
    # maxCurrent: 28

tariffs:
  currency: EUR # (default EUR)
  grid:
    # static grid price with price zones)
    type: fixed
    price: 0.1451 # EUR/kWh
    zones:
      - days: Mo-So
        hours: 0-8
        price: 0.1027 # EUR/kWh
      - days: Mo-So
        hours: 8-22
        price: 0.1451 # EUR/kWh
      - days: Mo-So
        hours: 22-0
        price: 0.1027 # EUR/kWh

# mqtt message broker
mqtt:
  broker: xxx.xxx.xxx.xxx:1883
  topic: evcc # root topic for publishing, set empty to disable

network:
  # schema is the HTTP schema
  # setting to `https` does not enable https, it only changes the way URLs are generated
  schema: http
  # host is the hostname or IP address
  # if the host name contains a `.local` suffix, the name will be announced on MDNS
  # docker: MDNS announcements don't work. host must be set to the docker host's name.
  host: evcc.local
  # port is the listening port for UI and api
  # evcc will listen on all available interfaces
  port: 7070

interval: 10s # control cycle interval

# log settings
log: debug
levels:
  site: debug
  lp-1: debug
  cache: error
  db: error
  mqtt: error

[andig]

Im Log stehen die Werte unter

final charge energy: 6.19kWh

Jetzt müsste man man rausfinden wo die her kommen. Dafür bräuchte es ein trace log für die evsewifi.

[VolkerK62]

charge total import kommt doch von der Wallbox, oder?
Im letzten Interval vor disable kommen 16 kWh, im ersten nach disable kommen 32 kWh.

[lp-1  ] DEBUG 2024/04/05 05:50:21 charge total import: 16.000kWh
[lp-1  ] DEBUG 2024/04/05 05:50:22 charger disable
[lp-1  ] DEBUG 2024/04/05 05:50:31 charge total import: 32.010kWh

Bedingt dadurch geht natürlich auch das Soc estimate durch die Decke.

[lp-1  ] DEBUG 2024/04/05 05:49:51 soc estimated: 65.90% (vehicle: 63.00%)
[lp-1  ] DEBUG 2024/04/05 05:50:31 soc estimated: 100.00% (vehicle: 67.00%)

[pjpeartree]

Got the same issue with another vehicle.

EVCC Session reports 72.3 kWh and evsewifi reports 36.15 kWh.

I've tweaked my evcc.yaml log settings to include trace for evsewifi. Let's see how it performs in the next charging session! Will share the results afterward.

[andig]

Jetzt müsste man man rausfinden wo die her kommen. Dafür bräuchte es ein trace log für die evsewifi.

[pjpeartree]

Please find attached the log with evsewifi trace.
_evcc_logs (5).txt

This is a new charging session:

[lp-1  ] INFO 2024/04/06 13:32:57 start charging ->
[lp-1  ] DEBUG 2024/04/06 13:32:57 wake-up timer: stop
[lp-1  ] DEBUG 2024/04/06 13:32:57 soc estimated: 61.00% (vehicle: 61.00%)
[lp-1  ] DEBUG 2024/04/06 13:32:57 vehicle soc: 61%
[lp-1  ] DEBUG 2024/04/06 13:32:57 vehicle range: 148km
[lp-1  ] DEBUG 2024/04/06 13:32:57 pv charge current: 0A = 6A + -17.5A (4016W @ 1p)

...

[evse  ] TRACE 2024/04/06 15:05:27 GET http://192.168.1.120/getParameters
[evse  ] TRACE 2024/04/06 15:05:27 {"type":"parameters","list":[{"vehicleState":3,"evseState":true,"maxCurrent":32,"actualCurrent":6,"actualPower":1.4,"duration":5557000,"alwaysActive":true,"lastActionUser":"vehicle","lastActionUID":"vehicle","energy":2.17,"mileage":13.5,"meterReading":2.17,"currentP1":6.17,"currentP2":0,"currentP3":0,"useMeter":true}]}
[lp-1  ] DEBUG 2024/04/06 15:05:27 charge power: 1400W
[site  ] DEBUG 2024/04/06 15:05:27 pv power: 1090W
[site  ] DEBUG 2024/04/06 15:05:27 battery soc: 34%
[site  ] DEBUG 2024/04/06 15:05:27 battery power: 1458W
[site  ] DEBUG 2024/04/06 15:05:27 grid meter: 14W
[site  ] DEBUG 2024/04/06 15:05:27 site power: 1772W
[lp-1  ] DEBUG 2024/04/06 15:05:27 charge voltages: [0 0 0]V
[lp-1  ] DEBUG 2024/04/06 15:05:27 charge currents: [6.17 0 0]A
[lp-1  ] DEBUG 2024/04/06 15:05:27 detected active phases: 1p
[lp-1  ] DEBUG 2024/04/06 15:05:27 charge total import: 2.170kWh
[lp-1  ] DEBUG 2024/04/06 15:05:27 charger status: C
[lp-1  ] DEBUG 2024/04/06 15:05:27 vehicle status: B
[lp-1  ] DEBUG 2024/04/06 15:05:27 vehicle soc: 65%
[lp-1  ] DEBUG 2024/04/06 15:05:27 vehicle range: 156km
[lp-1  ] DEBUG 2024/04/06 15:05:27 limitSoc reached: 65.0% > 65%
[evse  ] TRACE 2024/04/06 15:05:27 GET http://192.168.1.120/setCurrent?current=0
[evse  ] TRACE 2024/04/06 15:05:27 S0_set current to given value
[lp-1  ] DEBUG 2024/04/06 15:05:27 charger disable
[lp-1  ] DEBUG 2024/04/06 15:05:27 wake-up timer: stop
[site  ] DEBUG 2024/04/06 15:05:37 ----
[evse  ] TRACE 2024/04/06 15:05:37 GET http://192.168.1.120/getParameters
[evse  ] TRACE 2024/04/06 15:05:37 {"type":"parameters","list":[{"vehicleState":2,"evseState":false,"maxCurrent":32,"actualCurrent":0,"actualPower":0,"duration":5559000,"alwaysActive":true,"lastActionUser":"API","lastActionUID":"API","energy":2.17,"mileage":13.5,"meterReading":4.33,"currentP1":0,"currentP2":0,"currentP3":0,"useMeter":true}]}
[lp-1  ] DEBUG 2024/04/06 15:05:37 charge power: 0W
[site  ] DEBUG 2024/04/06 15:05:37 pv power: 1109W
[site  ] DEBUG 2024/04/06 15:05:37 battery soc: 34%
[site  ] DEBUG 2024/04/06 15:05:37 battery power: 1045W
[site  ] DEBUG 2024/04/06 15:05:37 grid meter: -996W
[site  ] DEBUG 2024/04/06 15:05:37 site power: 349W
[lp-1  ] DEBUG 2024/04/06 15:05:37 charge voltages: [0 0 0]V
[lp-1  ] DEBUG 2024/04/06 15:05:37 charge currents: [0 0 0]A
[lp-1  ] DEBUG 2024/04/06 15:05:37 charge total import: 4.330kWh
[lp-1  ] DEBUG 2024/04/06 15:05:37 charger status: B
[lp-1  ] DEBUG 2024/04/06 15:05:37 final charge energy: 4.33kWh
[lp-1  ] INFO 2024/04/06 15:05:37 stop charging <-
[evse  ] TRACE 2024/04/06 15:05:37 GET http://192.168.1.120/getParameters
[evse  ] TRACE 2024/04/06 15:05:37 {"type":"parameters","list":[{"vehicleState":2,"evseState":false,"maxCurrent":32,"actualCurrent":0,"actualPower":0,"duration":5559000,"alwaysActive":true,"lastActionUser":"API","lastActionUID":"API","energy":2.17,"mileage":13.5,"meterReading":4.33,"currentP1":0,"currentP2":0,"currentP3":0,"useMeter":true}]}
[lp-1  ] DEBUG 2024/04/06 15:05:37 charge total import: 4.330kWh

[pjpeartree]

Looks like something related with the meterReading before and after stop charging.

Line 10211: [evse  ] TRACE 2024/04/06 15:05:27 {"type":"parameters","list":[{"vehicleState":3,"evseState":true,"maxCurrent":32,"actualCurrent":6,"actualPower":1.4,"duration":5557000,"alwaysActive":true,"lastActionUser":"vehicle","lastActionUID":"vehicle","**energy":2.17**,"mileage":13.5,"**meterReading":2.17**,"currentP1":6.17,"currentP2":0,"currentP3":0,"useMeter":true}]}
..
[evse  ] TRACE 2024/04/06 15:05:27 GET http://192.168.1.120/setCurrent?current=0
[evse  ] TRACE 2024/04/06 15:05:27 S0_set current to given value
[lp-1  ] DEBUG 2024/04/06 15:05:27 charger disable
..
Line 10233: [evse  ] TRACE 2024/04/06 15:05:37 {"type":"parameters","list":[{"vehicleState":2,"evseState":false,"maxCurrent":32,"actualCurrent":0,"actualPower":0,"duration":5559000,"alwaysActive":true,"lastActionUser":"API","lastActionUID":"API",**"energy":2.17**,"mileage":13.5,**"meterReading":4.33**,"currentP1":0,"currentP2":0,"currentP3":0,"useMeter":true}]}

evsewifi Meter Settings

[pjpeartree]

Does anyone know why the wallbox doubles the meter reading after stopping charging?

[andig]

why the wallbox doubles the meter reading after stopping charging

@pjpeartree I assume that's your analysis because of this log?

[lp-1  ] DEBUG 2024/04/06 15:05:27 charge total import: 2.170kWh
[lp-1  ] DEBUG 2024/04/06 15:05:37 charge total import: 4.330kWh

I would suggest to contact the vendor to find out.

[pjpeartree]

The charger trace log indicates that the activity to disable the charger occurs between that two log entries.

Line 10211: [evse  ] TRACE 2024/04/06 15:05:27 {"type":"parameters","list":[{"vehicleState":3,"evseState":true,"maxCurrent":32,"actualCurrent":6,"actualPower":1.4,"duration":5557000,"alwaysActive":true,"lastActionUser":"vehicle","lastActionUID":"vehicle","**energy":2.17**,"mileage":13.5,"**meterReading":2.17**,"currentP1":6.17,"currentP2":0,"currentP3":0,"useMeter":true}]}
..
[evse  ] TRACE 2024/04/06 15:05:27 GET http://192.168.1.120/setCurrent?current=0
[evse  ] TRACE 2024/04/06 15:05:27 S0_set current to given value
[lp-1  ] DEBUG 2024/04/06 15:05:27 charger disable
..
Line 10233: [evse  ] TRACE 2024/04/06 15:05:37 {"type":"parameters","list":[{"vehicleState":2,"evseState":false,"maxCurrent":32,"actualCurrent":0,"actualPower":0,"duration":5559000,"alwaysActive":true,"lastActionUser":"API","lastActionUID":"API",**"energy":2.17**,"mileage":13.5,**"meterReading":4.33**,"currentP1":0,"currentP2":0,"currentP3":0,"useMeter":true}]}

[schenlap]

Hi,

I had the same problem a long time ago. At that time it was due to an error in the evsewifi together with an S0 meter. Are you using the latest evsewifi firmware? The Bug was fixed with evsewifi v2.2.0.

#788
CurtRod/SimpleEVSE-WiFi#67

[pjpeartree]

Hi,

Thank you for your feedback.

I am using the latest version for ESP8266, Firmware Version: 1.1.1, available at https://www.smartwb.de/firmware-downloads/