search

evcc-io / evcc

Sonne tanken ☀️🚘
https://evcc.io
MIT License
3.58k stars 661 forks source link

Fehlerhafte Berechnung der Ladeenergie #8503

Closed xrthommy closed 1 year ago

xrthommy commented 1 year ago

Describe the bug

Die Angezeigte Wert der Energie bei den Ladevorgängen weicht manchmal vom tatsächlichen Wert ab. Beispiel: grafik Die Zählerstände sind korrekt aber der "Geladen" Wert stimmt nicht. Habe den Verdacht, dass es nur auftritt wenn während des Ladevorganges eine Phasenumschaltung stattfindet.

Steps to reproduce

1. 2. 3. ...

Configuration details

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: homeassistant.local
  # port is the listening port for UI and api
  # evcc will listen on all available interfaces
  port: 7070

interval: 10s # control cycle interval

# database configuration for persisting charge sessions and settings
# database:
#   type: sqlite
#   dsn: <path-to-db-file>

# sponsor token enables optional features (request at https://sponsor.evcc.io)
sponsortoken: xxx

# telemetry enables aggregated statistics
#
# Telemetry allows collecting usage data (grid and green energy, charge power).
# Data is aggregated, no individual charging sessions are tracked. The collected,
# anonymous data can be retrieved using https://api.evcc.io.
#
# See https://github.com/evcc-io/evcc/pull/4343 or details.
#
# For time being, this is only available to sponsors, hence data is associated with
# the sponsor token's identity.
#
telemetry: true
plant: xxx

# log settings
log: info
levels:
  site: debug
  lp-1: debug
  lp-2: debug
  my_car_bmw_i3: debug
  cache: error
  db: error

# modbus proxy for allowing external programs to reuse the evcc modbus connection
# each entry will start a proxy instance at the given port speaking Modbus TCP and
# relaying to the given modbus downstream device (either TCP or RTU, RS485 or TCP)
modbusproxy:
#  - port: 5200
#    uri: homeassistant:502
#    rtu: true
#    readonly: true

################################################################################

######### 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:

### Grid ###

  - name: my_grid_GW_mqtt
    type: custom
    power:
      source: mqtt
      topic: homeassistant/sensor/active_power_total/state  #sensor.active_power_total
      # timeout: 30s # don't accept values older than timeout
      scale: -1

### PV ###

  - name: my_pv_total_mqtt
    type: custom
    power:
      source: mqtt
      topic: homeassistant/sensor/pv_power_total/state  #sensor.total_pv_power
      # timeout: 30s # don't accept values older than timeout

### Battery ###

  - name: my_battery_mqtt
    type: custom
    power:
      source: mqtt
      topic: homeassistant/sensor/battery_power/state  #sensor.battery_power
      # timeout: 30s # don't accept values older than timeout
    soc: # optional battery soc (%)
      source: mqtt
      topic: homeassistant/sensor/battery_state_of_charge/state  #sensor.battery_state_of_charge
      # timeout: 30s # don't accept values older than timeout
    capacity: 9.83  # Akkukapazität in kWh # Optional 

######### 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: my_charger_go # Wallbox Garage go-eCharger
    type: template
    template: go-e-v3
    host: xxx # IP-Adresse oder Hostname 

  - name: my_charger_bonfire # Bonfire X Ladegerät an Shelly Plug
    type: template
    standbypower: 10 # Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (Optional    
  # FritzDect
    template: fritzdect
    uri: https://fritz.box # HTTP(S) Adresse (Optional)
    user: homeassistant # Benutzerkonto (bspw. E-Mail Adresse, User Id, etc.)
    password: xxx # Passwort des Benutzerkontos (bei führenden Nullen bitte in einfache Hochkommata setzen)
    ain: xxx # Die AIN ist auf dem Typenschild auf der Geräterückseite aufgedruckt. Bei führenden Nullen bitte in doppelte Hochkommata setzen.  

######### vehicle definitions
# name can be freely chosen and is used as reference when assigning vehicle to loadpoint
# for documentation see https://docs.evcc.io/docs/devices/vehicles
vehicles:

  - name: my_car_bmw_i3
    type: bmw
    # type: template
    # template: bmw
    title: BMW i3 # Wird in der Benutzeroberfläche angezeigt # Optional
    user: xxx # Benutzerkonto (bspw. E-Mail Adresse, User Id, etc.)
    password: xxx # Passwort des Benutzerkontos (bei führenden Nullen bitte in einfache Hochkommata setzen)
    vin: xxx # Erforderlich, wenn mehrere Fahrzeuge des Herstellers vorhanden sind # Optional
    capacity: 27.2 # Akkukapazität in kWh # Optional 
    phases: 3
    # cache: 15m
    onIdentify: # set defaults when vehicle is identified  
      mode: pv
      mincurrent: 6
      maxcurrent: 16
      minSoc: 25
      targetSoc: 95
      priority: 1
    # identifiers:
    #   - 12345ABC # RFID token ID
    # features: ["coarsecurrent"]
    icon: car # car bike scooter moped motorcycle van bus tractor generic heater cooler waterheater

  - name: my_car_bmw_i3_mqtt
    type: custom
    title: BMW i3 (via MQTT)
    capacity: 27.2 # kWh
    phases: 3
    soc:
      source: mqtt
      topic: homeassistant/sensor/i3_94_remaining_battery_percent/state
    range:
      source: mqtt
      topic: homeassistant/sensor/i3_94_remaining_range_electric/state
    icon: car

  - name: my_bike_bonfire_x # E-Motorrad Bonfire X
    type: template
    template: offline
    title: Bonfire X # Wird in der Benutzeroberfläche angezeigt # Optional
    capacity: 3.6 # Akkukapazität in kWh # Optional 
    phases: 1
    # cache: 15m
    mode: pv
    mincurrent: 5
    maxcurrent: 16
    icon: motorcycle 

################################################################################

# site describes the EVU connection, PV and home battery
site:
  title: Zuhause # display name for UI
  meters:
    grid: my_grid_GW_mqtt # grid meter Goodwe SmartMeter

    pv:
      - my_pv_total_mqtt # PV total via mqtt

    battery: 
      - my_battery_mqtt

  bufferSoc: 95 # ignore home battery discharge above soc (empty to disable)
  prioritySoc: 50 # give home battery priority up to this soc (empty to disable)
  residualPower: 200 # Verbleibende Netzeinspeiseleistung (W)
  smartCostlimit: 0.08 # z.B 20 ct. Mit diesem Parameter kann eine Preis-Grenze festgelegt werden. Im PV-Modus startet die Ladung beim Unterschreiten dieser Grenze.
  maxGridSupplyWhileBatteryCharging: 200 # Schwellwert (W) Netzbezug bei Hybridwechselrichter

################################################################################

# loadpoint describes the charger, charge meter and connected vehicle
loadpoints:
  - title: Wallbox # display name for UI
    charger: my_charger_go # charger
    vehicle: my_car_bmw_i3 # set default vehicle (disables vehicle detection)    
    mode: pv # set default charge mode, use "off" to disable by default if charger is publicly available
    resetOnDisconnect: true # set defaults when vehicle disconnects
    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: charging
        # poll interval defines how often the vehicle API may be polled if NOT charging
        interval: 60m
      estimate: true # set false to disable interpolating between api updates (not recommended)
    phases: 0 # electrical connection (normal charger: default 3 for 3 phase, 1p3p charger: 0 for "auto" or 1/3 for fixed phases)
    enable: # pv mode enable behavior
      delay: 1m # 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: 3m # 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)
    minCurrent: 6 # minimum charge current (default 6A)
    maxCurrent: 16 # maximum charge current (default 16A)
    priority: 1 # Dient während der Ladung der Priorisierung von Loadpoints untereinander. Je höher der Wert, desto größer die Priorität.

  - title: Bonfire-Lader # display name for UI
    charger: my_charger_bonfire # charger
    vehicle: my_bike_bonfire_x # set default vehicle (disables vehicle detection)    
    mode: pv # set default charge mode, use "off" to disable by default if charger is publicly available
    resetOnDisconnect: true # set defaults when vehicle disconnects
    soc:
      #poll:
        #mode: connected
        #interval: 1m
      estimate: true # set false to disable interpolating between api updates (not recommended)
    phases: 1 # electrical connection (normal charger: default 3 for 3 phase, 1p3p charger: 0 for "auto" or 1/3 for fixed phases)
    enable: # pv mode enable behavior
      delay: 1m # 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: 3m # 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)
    minCurrent: 1 # minimum charge current (default 6A)
    maxCurrent: 16 # maximum charge current (default 16A)
    priority: 2 # Dient während der Ladung der Priorisierung von Loadpoints untereinander. Je höher der Wert, desto größer die Priorität.

################################################################################

# tariffs are the fixed or variable tariffs
# cheap (tibber/awattar) can be used to define a tariff rate considered cheap enough for charging
tariffs:
  currency: EUR # three letter ISO-4217 currency code (default EUR)

  grid:
    # either static grid price (or price zones)
    # type: fixed
    # price: 0.294 # EUR/kWh
    # zones:
    #   - days: Mo-Fr
    #     hours: 2-5
    #     price: 0.2 # EUR/kWh
    #   - days: Sa,So
    #     price: 0.15 # EUR/kWh

    # # or variable via tibber
    type: tibber
    token: xxx # access token
    # homeid: xxx # optional if multiple homes associated to account

    # # or variable via awattar
    # type: awattar
    # region: de # optional, choose at for Austria

  feedin:
    # rate for feeding excess (pv) energy to the grid
    type: fixed
    price: 0.0787 # EUR/kWh

  planner:
    # planner tariff can be used for target charging if not grid tariff is specified
    # GrünStromIndex (Germany only) or ElectricityMaps provide CO2 intensity forecast

    # type: grünstromindex
    # zip: <zip>

    # type: electricitymaps
    # uri: <uri>
    # token: <token>
    # zone: DE

################################################################################

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

# influx database
influx:
  # url: http://localhost:8086
  # database: evcc
  # user:
  # password:

# eebus credentials
eebus:
  # uri: # :4712
  # interfaces: # limit eebus to specific network interfaces
  # - en0
  # certificate: # local signed certificate, required, can be generated via `evcc eebus-cert`
  #   public: # public key
  #   private: # private key

################################################################################

# push messages
messaging:
  events:
    start: # charge start event
      title: Laden von {{.vehicleTitle}} gestartet
      msg: |
        {{.title}} hat laden gestartet von {{.vehicleTitle}} im Modus "${mode}".
        ---------------------------------------------------
        evcc Status {{printf `(%d-%02d-%02d %02d:%02d:%02d)` now.Year now.Month now.Day now.Hour now.Minute now.Second}}:
        - Netz-Leistung: {{round (divf .gridPower 1000) 3 }} kW
        - Solar-Leistung: {{round (divf .pvPower 1000) 3 }} kW
        - Eigenverbrauch: {{round (divf .homePower 1000) 3 }} kW
        - {{if .batteryConfigured}}Batteriespeicher-Status: {{round (divf .batteryPower 1000) 3 }} kW ({{.batterySoc }} %){{end}}
    stop: # charge stop event
      title: Laden von {{.vehicleTitle}} beendet
      msg: |
        {{.title}} hat laden beendet von {{.vehicleTitle}}. Geladen wurden ${chargedEnergy:%.1fk} kWh in ${chargeDuration}.
        ---------------------------------------------------
        evcc Status {{printf `(%d-%02d-%02d %02d:%02d:%02d)` now.Year now.Month now.Day now.Hour now.Minute now.Second}}:
        - Netz-Leistung: {{round (divf .gridPower 1000) 3 }} kW
        - Solar-Leistung: {{round (divf .pvPower 1000) 3 }} kW
        - Eigenverbrauch: {{round (divf .homePower 1000) 3 }} kW
        - {{if .batteryConfigured}}Batteriespeicher-Status: {{round (divf .batteryPower 1000) 3 }} kW ({{.batterySoc }} %){{end}}
    connect: # vehicle connect event
      title: "{{.vehicleTitle}} verbunden mit {{.title}}"
      msg: |
        {{.vehicleTitle}} verbunden mit {{.title}} bei ${pvPower:%.1fk} kW PV-Leistung.
        ---------------------------------------------------
        evcc Status {{printf `(%d-%02d-%02d %02d:%02d:%02d)` now.Year now.Month now.Day now.Hour now.Minute now.Second}}:
        - Netz-Leistung: {{round (divf .gridPower 1000) 3 }} kW
        - Solar-Leistung: {{round (divf .pvPower 1000) 3 }} kW
        - Eigenverbrauch: {{round (divf .homePower 1000) 3 }} kW
        - {{if .batteryConfigured}}Batteriespeicher-Status: {{round (divf .batteryPower 1000) 3 }} kW ({{.batterySoc }} %){{end}}
    disconnect: # vehicle connected event
      title: "{{.vehicleTitle}} getrennt von {{.title}}"
      msg: |
        {{.vehicleTitle}} getrennt von {{.title}} nach ${connectedDuration}.
        ---------------------------------------------------
        evcc Status {{printf `(%d-%02d-%02d %02d:%02d:%02d)` now.Year now.Month now.Day now.Hour now.Minute now.Second}}:
        - Netz-Leistung: {{round (divf .gridPower 1000) 3 }} kW
        - Solar-Leistung: {{round (divf .pvPower 1000) 3 }} kW
        - Eigenverbrauch: {{round (divf .homePower 1000) 3 }} kW
        - {{if .batteryConfigured}}Batteriespeicher-Status: {{round (divf .batteryPower 1000) 3 }} kW ({{.batterySoc }} %){{end}}
    guest: # vehicle could not be identified
      title: "Unbekanntes Fahrzeug verbunden mit {{.title}}"
      msg: |
        Unbekanntes Fahrzeug verbunden mit {{.title}}. Gastfahrzeug?
        ---------------------------------------------------
        evcc Status {{printf `(%d-%02d-%02d %02d:%02d:%02d)` now.Year now.Month now.Day now.Hour now.Minute now.Second}}:
        - Netz-Leistung: {{round (divf .gridPower 1000) 3 }} kW
        - Solar-Leistung: {{round (divf .pvPower 1000) 3 }} kW
        - Eigenverbrauch: {{round (divf .homePower 1000) 3 }} kW
        - {{if .batteryConfigured}}Batteriespeicher-Status: {{round (divf .batteryPower 1000) 3 }} kW ({{.batterySoc }} %){{end}}

#    start: # charge start event
#      title: Charge started
#      msg: Started charging in "${mode}" mode
#    stop: # charge stop event
#      title: Charge finished
#      msg: Finished charging ${chargedEnergy:%.1fk}kWh in ${chargeDuration}.
#    connect: # vehicle connect event
#      title: Car connected
#      msg: "Car connected at ${pvPower:%.1fk}kW PV"
#    disconnect: # vehicle connected event
#      title: Car disconnected
#      msg: Car disconnected after ${connectedDuration}
#    soc: # vehicle soc update event
#      title: Soc updated
#      msg: Battery charged to ${vehicleSoc:%.0f}%

  services:
   - type: pushover
     app: xxx # API Token/Key der in Pushover angelegten Aplication
     recipients: # Liste der Empfänger: entweder User Key or Delivery Group. In Pushover angelegte Gruppen können auf bestimmte Geräte eingeschränkt werden.
     - xxx
     devices:
     - mi9

  # - type: telegram
  #   token: # bot id
  #   chats:
  #   - # list of chat ids
  # - type: email
  #   uri: smtp://<user>:<password>@<host>:<port>/?fromAddress=<from>&toAddresses=<to>
  # - type: ntfy
  #   uri: https://<host>/<topics>
  #   priority: <priority>
  #   tags: <tags>

Log details

Using config file: /config/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc_20230401.db evcc --config /config/evcc.yaml'
[main  ] INFO 2023/06/16 22:13:23 evcc 0.118.0
[main  ] INFO 2023/06/16 22:13:23 using config file: /config/evcc.yaml
[main  ] INFO 2023/06/16 22:13:23 starting ui and api at :7070
[mqtt  ] INFO 2023/06/16 22:13:33 connecting evcc-252016826 at tcp://homeassistant:1883
[site  ] DEBUG 2023/06/16 22:13:43 dynamic grid tariff
[site  ] WARN 2023/06/16 22:13:43 vehicle 'Bonfire X' does not support automatic detection
[site  ] WARN 2023/06/16 22:13:43 vehicle 'BMW i3 (via MQTT)' does not support automatic detection
[site  ] INFO 2023/06/16 22:13:43 site config:
[site  ] INFO 2023/06/16 22:13:43   meters:      grid ✓ pv ✓ battery ✓
[site  ] INFO 2023/06/16 22:13:43     grid:      power ✓ energy ✗ currents ✗
[site  ] INFO 2023/06/16 22:13:43     pv 1:      power ✓ energy ✗ currents ✗
[site  ] INFO 2023/06/16 22:13:43     battery 1: power ✓ energy ✗ currents ✗ soc ✓ capacity ✓
[site  ] INFO 2023/06/16 22:13:43   vehicles:
[site  ] INFO 2023/06/16 22:13:43     vehicle 1: range ✗ finish ✗ status ✗ climate ✗ wakeup ✗
[site  ] INFO 2023/06/16 22:13:43     vehicle 2: range ✓ finish ✗ status ✓ climate ✗ wakeup ✗
[site  ] INFO 2023/06/16 22:13:43     vehicle 3: range ✓ finish ✗ status ✗ climate ✗ wakeup ✗
[lp-1  ] INFO 2023/06/16 22:13:43 loadpoint 1:
[lp-1  ] INFO 2023/06/16 22:13:43   mode:        pv
[lp-1  ] INFO 2023/06/16 22:13:43   charger:     power ✓ energy ✓ currents ✓ phases ✓ wakeup ✗
[lp-1  ] INFO 2023/06/16 22:13:43   meters:      charge ✓
[lp-1  ] INFO 2023/06/16 22:13:43     charge:    power ✓ energy ✓ currents ✓
[lp-2  ] INFO 2023/06/16 22:13:43 loadpoint 2:
[lp-2  ] INFO 2023/06/16 22:13:43   mode:        pv
[lp-2  ] INFO 2023/06/16 22:13:43   charger:     power ✓ energy ✓ currents ✗ phases ✗ wakeup ✗
[lp-2  ] INFO 2023/06/16 22:13:43   meters:      charge ✓
[lp-2  ] INFO 2023/06/16 22:13:43     charge:    power ✓ energy ✓ currents ✗
[site  ] DEBUG 2023/06/16 22:13:43 dynamic grid tariff
[lp-1  ] DEBUG 2023/06/16 22:13:43 phase timer inactive
[lp-1  ] DEBUG 2023/06/16 22:13:43 pv timer inactive
[lp-1  ] DEBUG 2023/06/16 22:13:43 guard timer inactive
[lp-1  ] INFO 2023/06/16 22:13:43 vehicle updated: unknown -> BMW i3
[lp-1  ] DEBUG 2023/06/16 22:13:43 set charge mode: pv
[lp-1  ] DEBUG 2023/06/16 22:13:43 set min current: 6
[lp-1  ] DEBUG 2023/06/16 22:13:43 set max current: 16
[lp-1  ] DEBUG 2023/06/16 22:13:43 set min soc: 25
[lp-1  ] DEBUG 2023/06/16 22:13:43 set target soc: 95
[lp-2  ] DEBUG 2023/06/16 22:13:43 phase timer inactive
[lp-2  ] DEBUG 2023/06/16 22:13:43 pv timer inactive
[lp-2  ] DEBUG 2023/06/16 22:13:43 guard timer inactive
[lp-2  ] INFO 2023/06/16 22:13:43 vehicle updated: unknown -> Bonfire X
[lp-2  ] DEBUG 2023/06/16 22:13:43 set charge mode: pv
[lp-2  ] DEBUG 2023/06/16 22:13:43 set min current: 5
[lp-2  ] DEBUG 2023/06/16 22:13:43 set max current: 16
[lp-2  ] DEBUG 2023/06/16 22:13:43 set min soc: 0
[lp-2  ] DEBUG 2023/06/16 22:13:43 set target soc: 100
[lp-2  ] ERROR 2023/06/16 22:13:44 charger: invalid user or password
[site  ] DEBUG 2023/06/16 22:13:44 ----
[lp-1  ] DEBUG 2023/06/16 22:13:44 charge power: 0W
[lp-2  ] DEBUG 2023/06/16 22:13:46 charge power: 0W
[site  ] DEBUG 2023/06/16 22:13:46 dynamic grid tariff
[site  ] DEBUG 2023/06/16 22:13:46 pv power: 0W
[site  ] DEBUG 2023/06/16 22:13:46 battery soc: 70%
[site  ] DEBUG 2023/06/16 22:13:46 battery power: 756W
[site  ] DEBUG 2023/06/16 22:13:46 grid power: 11W
[site  ] DEBUG 2023/06/16 22:13:46 site power: 967W
[lp-1  ] DEBUG 2023/06/16 22:13:47 vehicle odometer: 77941km
[lp-1  ] DEBUG 2023/06/16 22:13:47 charge currents: [0 0 0]A
[lp-1  ] DEBUG 2023/06/16 22:13:48 charge meter total import: 861.681kWh
[lp-1  ] DEBUG 2023/06/16 22:13:48 charger status: B
[lp-1  ] INFO 2023/06/16 22:13:48 car connected
[lp-1  ] DEBUG 2023/06/16 22:13:48 pv timer elapse
[lp-1  ] DEBUG 2023/06/16 22:13:48 pv timer inactive
[lp-1  ] DEBUG 2023/06/16 22:13:48 charger: guard elapse
[lp-1  ] DEBUG 2023/06/16 22:13:48 guard timer inactive
[lp-1  ] DEBUG 2023/06/16 22:13:48 charge meter total import: 861.681kWh
[lp-1  ] DEBUG 2023/06/16 22:13:48 vehicle status: B
[lp-1  ] DEBUG 2023/06/16 22:13:48 vehicle soc: 94%
[lp-1  ] DEBUG 2023/06/16 22:13:48 vehicle range: 177km
[lp-1  ] DEBUG 2023/06/16 22:13:48 available power -967W < 4140W min 3p threshold
[lp-1  ] DEBUG 2023/06/16 22:13:48 start phase scale1p timer
[lp-1  ] DEBUG 2023/06/16 22:13:48 phase scale1p in 3m0s
[lp-1  ] DEBUG 2023/06/16 22:13:48 pv charge current: 0A = 0A + -1.4A (967W @ 3p)
[lp-1  ] DEBUG 2023/06/16 22:13:48 pv enable timer reset
[lp-1  ] DEBUG 2023/06/16 22:13:48 pv timer inactive
[site  ] DEBUG 2023/06/16 22:13:48 ----
[lp-1  ] DEBUG 2023/06/16 22:13:48 charge power: 0W
[lp-2  ] DEBUG 2023/06/16 22:13:49 charge power: 0W
[site  ] DEBUG 2023/06/16 22:13:49 dynamic grid tariff
[site  ] DEBUG 2023/06/16 22:13:49 pv power: 0W
[site  ] DEBUG 2023/06/16 22:13:49 battery soc: 70%
[site  ] DEBUG 2023/06/16 22:13:49 battery power: 756W
[site  ] DEBUG 2023/06/16 22:13:49 grid power: 11W
[site  ] DEBUG 2023/06/16 22:13:49 site power: 967W
[lp-1  ] DEBUG 2023/06/16 22:13:49 vehicle odometer: 77941km
[lp-1  ] DEBUG 2023/06/16 22:13:49 charge currents: [0 0 0]A
[lp-1  ] DEBUG 2023/06/16 22:13:49 charge meter total import: 861.681kWh
[lp-1  ] DEBUG 2023/06/16 22:13:49 charger status: B
[lp-1  ] DEBUG 2023/06/16 22:13:49 available power -967W < 4140W min 3p threshold
[lp-1  ] DEBUG 2023/06/16 22:13:49 phase scale1p in 2m59s
[lp-1  ] DEBUG 2023/06/16 22:13:49 pv charge current: 0A = 0A + -1.4A (967W @ 3p)

What type of operating system are you running?

HomeAssistant Add-on

Version

0.118.0

premultiply commented 1 year ago

@andig Theoretisch wäre das denkbar falls die Box nach einer Umschaltung eine neue Session beginnt und wir dafür auch ChargedEnergy auswerten.

Habe den Eindruck, dass wir besser grundsätzlich ausschließlich TotalEnergy implementieren bzw. verarbeiten wenn das gibt und dann ChargedEnergy weglassen/ignorieren. ChargedEnergy nur wenn die Box sonst nix bietet. Dürfte zuverlässiger sein.

andig commented 1 year ago

Können wir gerne machen.

andig commented 1 year ago

Von welchem Charger reden wir überhaupt? Ist nur die Anzeige in evcc falsch oder kommt der falsche Wert vom Charger? Ich mache mal zu bis es mehr Klarheit des Problems gibt.

xrthommy commented 1 year ago

Der Charger ist ein go-e Charger Gemini flex (11kW). Hier der Eintrag für diese Ladung in der Log-Datei des Chargers. Da stimmt es, nur eben nicht in der Ladehistorie von evcc.

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns="http://www.w3.org/TR/REC-html40">

Session Number | Start | Ende | Dauer gesamt | Dauer aktiver Stromfluss | max. Leistung [kW] | max. Strom [A] | Energie [kWh] | Zaehlerstand Anfang [kWh] | Zaehlerstand Ende [kWh] -- | -- | -- | -- | -- | -- | -- | -- | -- | -- 129 | 16.06.2023 04:21 | 16.06.2023 12:35 | 08:14:00 | 03:17:38 | 7,613 | 16 | 14,904 | 845,557 | 860,461

andig commented 1 year ago

Ok, es geht also um den Go-E. Wir bräuchten bitte ein Log (go-e: trace) um zu verstehen, ob wir falsche Werte bekommen, vielleicht zum falschen Zeitpunkt fragen oder wo sonst die Ursache liegt. Wir holen die Daten ja schon vom Go-E API, es ist also unklar warum sie nicht stimmen :(

phrozen77 commented 1 year ago

Siehe auch #8017 - irgendwas ist da faul (ebenfalls Go-E Gemini Flex 11kW), auch heute wieder so einen Fall gehabt, Trace-Logs leider nicht vorhanden.

xrthommy commented 1 year ago

Hallo andig,

hier ein Trace:

[go-e ] TRACE 2023/06/30 20:00:52 GET http://xxx.xxx.xxx.xxx/api/status?filter=alw,car,eto,nrg,wh,trx,cards

[go-e ] TRACE 2023/06/30 20:00:52 {"alw":false,"eto":952005,"car":4,"wh":7885.926,"trx":null,"nrg":[232.5,232.81,232.81,2.79,0,0,0,0,0,0,0,0,0,0,0,0],"cards":[{"name":"n/a","energy":0,"cardId":true},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false}]}

Freundlichen Gruß

Thomas

Von: andig @.> Gesendet: Sonntag, 18. Juni 2023 10:52 An: evcc-io/evcc @.> Cc: xrthommy @.>; Author @.> Betreff: Re: [evcc-io/evcc] Fehlerhafte Berechnung der Ladeenergie (Issue #8503)

Ok, es geht also um den Go-E. Wir bräuchten bitte ein Log (go-e: trace) um zu verstehen, ob wir falsche Werte bekommen, vielleicht zum falschen Zeitpunkt fragen oder wo sonst die Ursache liegt. Wir holen die Daten ja schon vom Go-E API, es ist also unklar warum sie nicht stimmen :(

— Reply to this email directly, view it on GitHub https://github.com/evcc-io/evcc/issues/8503#issuecomment-1596039903 , or unsubscribe https://github.com/notifications/unsubscribe-auth/A47ERJDLAF7WUWUGL4CMMQ3XL26UBANCNFSM6AAAAAAZJWATJA . You are receiving this because you authored the thread. https://github.com/notifications/beacon/A47ERJHS7NG2M6TZU2GKZ7DXL26UBA5CNFSM6AAAAAAZJWATJCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS7EGRN6.gif Message ID: @. @.> >

andig commented 1 year ago

Damit ist ohne Kontext des Ladevorgangs und konkrete Fehlerbeschreibung leider nix anzufangen.