Skip to content

EVCC Ladeenergieanzeige im Ladevorgang fehlerhaft #19879

Open
@BastiZ0

Description

@BastiZ0

Describe the bug

Beim manuellen sowie automatischen Start des Ladevorgangs kommt es regelmäßig zu keiner Aktualisierung der geladenen Energie in der Übersicht des Ladepunktes.

Gleichzeitig wird auch der Ladevorgang nicht korrekt in der Ladevorgängeübersicht angezeigt.

Dieser Fehler tritt nicht jedes Mal auf. Er kann meist mit einem Neustart des Addons in Home Assistant behoben werden. Allerdings kommt es beim Umschalten von 1 auf 3-Phasenbetrieb oder auch umgekehrt wieder zum selbigen Fehler.

Es kommt vor, dass die Lademenge nach einer unbestimmten Zeit dann doch anfängt hochzuzählen. Die Ladeleistung und die Energie, die in der Übersicht beim Energiezähler der Wallbox stehen, sind korrekt. Nur die geladene Energie und damit auch die Verhältnisse von Solar, Netz, Co2 etc, stimmen nicht.

Steps to reproduce

  1. Starten des Ladevorgangs
  2. Fehler tritt direkt mit sehr hoher Wahrscheinlichkeit auf
  3. neustart kann Problem beheben, muss aber nicht.

Configuration details

gibt es nicht mehr. meine migrierte war

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

interval: 30s # control cycle interval. Interval <30s can lead to unexpected behavior, see https://docs.evcc.io/docs/reference/configuration/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)
# trial token, valid until 2065-10-09
sponsortoken: 

# 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: 
# log settings
log: info
levels:
  site: debug
  lp-1: debug
  lp-2: 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: solar-edge:502
  #    # rtu: true
  #    # readonly: true # use `deny` to raise modbus errors

# 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: my_grid
#    type: template
#    template: sungrow-hybrid
#    usage: grid
#    
#    # Modbus TCP
#    modbus: tcpip
#    id: 1
#    host: 192.168.79.1 # Hostname
#    port: 502 # Port
#    timeout: 10s # optional
#
#  - name: my_pv
#    type: template
#    template: sungrow-hybrid
#    usage: pv
#    
#    # Modbus TCP
#    modbus: tcpip
#    id: 1
#    host: 192.168.79.1 # Hostname
#    port: 502 # Port
#    timeout: 10s # optional
#
#  - name: my_battery
#    type: template
#    template: sungrow-hybrid
#    usage: battery
#    
#    # Modbus TCP
#    modbus: tcpip
#    id: 1
#    host: 192.168.79.1 # Hostname
#    port: 502 # Port
#    timeout: 10s # 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: Sungrow
    type: template
    template: sungrow

    # Modbus TCP
    modbus: tcpip
    id: 248
    host: 192.168.79.6 # Hostname
    port: 502 # Port
    
#  - name: my_charger
#    type: template
#    template: go-e-v3
#    host: 192.168.79.4 # IP-Adresse oder Hostname
    
    
#  - name: SungrowOCPP
#    type: template
#    template: ocpp
#    stationid: A22A1445410 # Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)
#    remotestart: # Diese Option nur aktivieren wenn keinerlei Möglichkeit besteht Transaktionen seitens des Ladepunktes zu initiieren! Das ist nur der Fall wenn z. B. kein RFID-Lesegerät vorhanden ist und Ladevorgänge grundsätzlich einzeln per App freigeschaltet werden müssten. Normalerweise sollte der Ladepunkt am Gerät immer so konfiguriert werden, dass entweder eine RFID-Karte zur Freischaltung verwendet wird oder der Ladepunkt auf "Autostart", "Freies Laden" o.ä. eingestellt ist. Zunächst die Dokumentation und die Konfigurationsmöglichkeiten des Ladepunktes prüfen, ggf. beim Hersteller nachfragen! (optional)
#    idtag: evcc




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

# site describes the EVU connection, PV and home battery
#site:
#  title: Home # display name for UI
#  meters:
#    grid: my_grid # grid meter
#    pv:
#      - my_pv # list of pv inverters/ meters
#    battery:
#      - my_battery # list of battery meters
#  residualPower: 200 # additional household usage margin
#  maxGridSupplyWhileBatteryCharging: 0 # ignore battery charging if AC consumption is above this value

# loadpoint describes the charger, charge meter and connected vehicle
loadpoints:
  - title: Sungrow
    charger: Sungrow
    mode: off
    
#  - title: SungrowOCPP
#    charger: SungrowOCPP
#    mode: off

    
#  - title: go-e # display name for UI
#    charger: my_charger # charger
#    mode: off # default charge mode to apply when vehicle is disconnected; use "off" to disable by default if charger is publicly available

    # remaining settings are experts-only and best left at default values
    priority: 0 # relative priority for concurrent charging in PV mode with multiple loadpoints (higher values have higher priority)
    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)
    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)

# tariffs are the fixed or variable tariffs
tariffs:
  #currency: EUR # three letter ISO-4217 currency code (default EUR)
  #grid:
    # either static grid price (or price zones)
    #type: fixed
   # price: 0.3437 # EUR/kWh
    
    # or variable tariffs
    #type: tibber
    #token: "" # access token
    # homeid: "" # optional if multiple homes associated to account

    # type: awattar
    # region: de # optional, choose at for Austria
    # charges: # optional, additional charges per kWh
    # tax: # optional, additional tax (0.1 for 10%)

    # type: octopusenergy
    # tariff: AGILE-FLEX-22-11-25 # Tariff code
    # region: A # optional

    # type: elering # Nordpool
    # region: ee # or lt, lv, fi
    # charges: # optional, additional charges per kWh
    # tax: # optional, additional tax (0.1 for 10%)

    # type: energinet # Energinet using the price in DKK
    # region: dk1 # or dk2
    # charges: # optional, additional charges per kWh
    # tax: # optional, additional tax (0.1 for 10%)

    # type: entsoe # Entso-E european market data
    # domain: BZN|DE-LU # https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas
    # securitytoken: # api token
    # charges: # optional, additional charges per kWh
    # tax: # optional, additional tax (0.1 for 10%)

    # type: pun # PUN - Prezzo unico nazionale - Hourly Italian wholesale prices
    # charges: 0 # optional, additional charges per kWh
    # tax: 0 # optional, additional tax (0.1 for 10%)

    # type: amber
    # token: # api token from https://app.amber.com.au/developers/
    # siteid: # site ID returned by the API
    # channel: general

    # type: custom # price from a plugin source; see https://docs.evcc.io/docs/reference/plugins
    # price:
    #   source: http
    #   uri: https://example.org/price.json
    #   jq: .price.current

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

    # type: octopusenergy
    # tariff: AGILE-FLEX-22-11-25 # Tariff code
    # region: A # optional

    # type: amber
    # token: # api token from https://app.amber.com.au/developers/
    # siteid: # site ID returned by the API
    # channel: feedIn
#  co2:
#    #co2 tariff provides co2 intensity forecast and is for co2-optimized target charging if no variable grid tariff is specified
#    type: grünstromindex # GrünStromIndex (Germany only)
#    zip: 

    # type: electricitymaps # https://app.electricitymaps.com/map
    # uri: <uri>
    # token: <token> # needs to be a token with forecast (not in the free tier)
    # zone: DE

    # type: ngeso # National Grid Electricity System Operator data (Great Britain only) https://carbonintensity.org.uk/
    # provides national data if both region and postcode are omitted - Choose ONE only!
    # region: 1 # optional, coarser than using a postcode - The region details are at https://carbon-intensity.github.io/api-definitions/#region-list
    # postcode: SW1 # optional - Outward postcode i.e. RG41 or SW1 or TF8. Do not include full postcode, outward postcode only

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

# influx database
#influx:
#   url: http://192.168.79.1:8086
#   database: home_assistant
#   user: Basti
#   password: !secret influxdb_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: 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}%
    guest: # vehicle could not be identified
      title: Unknown vehicle
      msg: Unknown vehicle, guest connected?
  services:
  # - type: pushover
  #   app: # app id
  #   recipients:
  #   - # list of recipient ids
  # - 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

wird nachgereicht

What type of operating system or environment does evcc run on?

HomeAssistant Add-on

External automation

  • I have made sure that no external automation like HomeAssistant or Node-RED is active or accessing any of the mentioned devices when this issue occurs.

Nightly build

  • I have verified that the issue is reproducible with the latest nightly build

Version

0.201.0

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionRather clarification than issue

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions