Charge Power must not be negativ

[Presl1983]

Was bedeutet das und warum lädt er nicht bei überschuss?

[VolkerK62]

Wenn du nicht gerade aus dem Auto heraus das Haus versorgst, dann bedeutet das, dass der Zähler deine Wallbox falsch angeschlossen ist.
Oder der Zähler deine Wallbox in evcc falsch implementiert ist.

[Presl1983]

Hmmm wundert mich ist ein go echarger.... Und es hat ja mal funktioniert...

[VolkerK62]

Zeig doch mal bitte deine Konfig.

Und es hat ja mal funktioniert...

wurde etwas geändert? (irgendwelche updates?)

[Presl1983]

eigentlich mach ich immer die Updates von evcc :/

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.178.128
  # 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>

# trial token, valid until 2024-02-08
sponsortoken: verrate ich nicht

# 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

# 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_pv
    type: template
    template: kostal-plenticore-gen2
    usage: pv

    # Modbus TCP
    modbus: tcpip
    id: 71
    host: 192.168.178.88 # Hostname
    port: 1502 # Port

  - name: my_grid
    type: template
    template: kostal-ksem-inverter
    usage: grid

    # Modbus TCP
    modbus: tcpip
    id: 71
    host: 192.168.178.88 # Hostname
    port: 1502 # Port

  - name: my_battery
    type: template
    template: kostal-plenticore-gen2
    usage: battery

    modbus: tcpip
    id: 71
    host: 192.168.178.88 # Hostname
    port: 1502 # Port
#    endianness: little # optional
#    capacity: 7.7 # Akkukapazität in kWh (optional)
#    minsoc: 10 # Ladung mit maximaler Geschwindigkeit bis zu dem angegeben Ladestand unabhängig PV-Erzeugung, wenn der Lademodus nicht auf 'Aus' steht (optional)
#    maxsoc: 95 # optional
#    watchdog: 60s # optional

#  - name: my_grid
#    type: template
#    template: kostal-ksem
#    usage: grid

# Modbus TCP
#    modbus: tcpip
#    id: 71
#    host: 192.168.178.120 # Hostname
#    port: 502 # Port

# Modbus TCP
#    modbus: tcpip
#    id: 71
#    host: 192.168.178.88 # Hostname
#    port: 1502 # Port

# 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
    type: template
    template: go-e-v3
    host: 192.168.178.25 # IP-Adresse oder Hostname

# 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
    type: template
    template: tesla-command
    title: Tesla # Wird in der Benutzeroberfläche angezeigt (optional)
    accessToken: verrate ich nicht
    refreshToken: verrate ich nicht
    capacity: 50 # Akkukapazität in kWh (optional)

# 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: 0 # 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: Garage # display name for UI
    charger: my_charger # charger
    meter: my_grid # charge meter
    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)
    guardDuration: 5m # switch charger contactor not more often than this (default 5m)

# tariffs are the fixed or variable tariffs
tariffs:
  currency: EUR # three letter ISO-4217 currency code (default EUR)
  grid:
    type: awattar
    region: at # optional, choose at for Austria
    charges: 0.0144 # optional, additional charges per kWh
    tax: 0.2 # optional, additional tax (0.1 for 10%)

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

    # type: octopusenergy
    # tariff: AGILE-FLEX-22-11-25 # Tariff code
    # region: A # optional
  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: <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 (United Kingdom only) https://carbonintensity.org.uk/
    # provides national data if both region and postcode are omitted - do not supply both at the same time!
    # region: 1 # optional, coarser than using a postcode - see https://api.carbonintensity.org.uk/ for full list
    # postcode: SW1A1AA # optional

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

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

[0x3d13f]

Du hast das Grid Meter beim Loadpoint mit drin. Das kann eigentlich keinen Sinn machen:
meter: my_grid # charge meter

[Presl1983]

dann hau ich das mal raus.
hab da eigentlich nie was geändert...

[VolkerK62]

Grid Meter als Charge Meter, kann nie funktioniert haben.

[andig]

hab da eigentlich nie was geändert...

Das ist meine Lieblingserklärung bei plötzlichen Fehlern :)