Lädt im Min+PV obwohl nicht genügend Sonne vorhanden

Kenterfie commented 7 months ago

Describe the bug

Seit dem Wechsel von v0.124.4 auf v0.124.6 lädt evcc trotz zu wenig PV Leistung weiter. Wenn ich auf die PV Stellung gehe, kommt wie zu erwarten, der Timer und das Laden wird beendet. Gab es eine Änderung im Verhalten die ich übersehen habe?

Steps to reproduce

Auto wurde angeschlossen als genug PV Überschuss vorhanden war und wechselte direkt in den Lademodus. Nach einiger Zeit verringerte sich die PV Leistung stark, aber der Ladevorgang wurde weiterhin mit voller Leistung fortgeführt.

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

# log settings
log: debug
levels:
  site: debug
  lp-1: debug
  lp-2: debug
  cache: error
  db: error
  ocpp: trace

# 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: pv
    type: template
    template: huawei-dongle
    usage: pv

    # Modbus TCP
    modbus: tcpip
    id: 1
    host: 192.168.2.199 # Hostname
    port: 502 # Port
    timeout: 15s # optional
  - name: grid
    type: custom
    power: # power reading (W)
      source: http
      uri: http://192.168.2.23/cm?cmnd=Status%208
      jq: .StatusSNS.ENERGY.Power
    energy: # Power_curr (Wh), for chargemeter usage only
      source: http
      uri: http://192.168.2.23/cm?cmnd=Status%208
      jq: .StatusSNS.ENERGY.Total
      #  - name: grid
      #    type: template
      #    template: tasmota
      #    usage: grid
      #    host: 192.168.2.23 # IP-Adresse oder Hostname
      #    user: # Standard-User ist admin (optional)
      #    password: # Passwort des Benutzerkontos (bei führenden Nullen bitte in einfache Hochkommata setzen) (optional)
      #    channel: 1 # Meterkanal (1-8)
#  - name: pv
#    type: ...
#  - name: battery
#    type: ...
#  - name: charge
#    type: ...
#  - name: aux
#    type: ...

# 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: wallbox
    type: template
    template: pulsarplus
    stationid: sn435152
    timeout: 5m # optional

# 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: car1
    type: template
    title: citigo
    template: skoda
    capacity: 36.8
    phases: 2

# site describes the EVU connection, PV and home battery
site:
  title: Home # display name for UI
  meters:
    grid: grid
    pv:
      - pv # list of pv inverters/ 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: Carport # display name for UI
    charger: wallbox # charger
    vehicle: car1
      #grid: grid
      #meter: pv # charge meter
    mode: "off" # default charge mode to apply when vehicle is disconnected; use "off" to disable by default if charger is publicly available
      #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.37 # EUR/kWh
      #zones:
      #  - days: Mon-Fri
      #    hours: 2-5
      #    price: 0.2 # EUR/kWh
      #  - days: Sat,Sun
      #    price: 0.15 # EUR/kWh

    # or variable tariffs
    # type: tibber
    # token: "476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4" # access token
    # homeid: "cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c" # 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: 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
  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

# 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

What type of operating system are you running?

Linux

Version

0.124.6

VolkerK62 commented 7 months ago

Voll normal. Min+PV lädt immer. https://docs.evcc.io/docs/guides/charging#was-bedeuten-die-verschiedenen-lademodi

Kenterfie commented 7 months ago

Ok, danke für die Richtigstellung. Nutze evcc noch nicht all zu lange und hatte eher angenommen, dass er bei "min+PV" nur bis zum Minimalwert den normalen Hausstrom nutzt. Das hätte den Vorteil das der Wagen dann mindestens bis zum Minimalwert geladen ist, aber wenn genug PV Leistung vorhanden ist er dann auch das Auto weiter lädt, aber wenn das nicht der Fall ist schade.

VolkerK62 commented 7 months ago

Das was du meinst, nennt sich minSoc. Lässt sich wie folgt einstellen: In der Benutzeroberfläche (UI) im Loadpoint Mitte unten auf "Plan" klicken. Dann den Tab "Ankunft" auswählen. Dort kannst du dann das Minimal- und das Standartziel einstellen.

Kenterfie commented 7 months ago

Vielen Dank für die schnelle und kompetente Hilfe. Dann ist das Issue hiermit geschlossen.

evcc-io / evcc