andig
commented
2 years ago Bei der Berechnung werden veraltete Wert der ChargePower abgezogen, dies führt dann zum ungewollten hoch/abregeln der Ladesteuerung.
Die Frage ist immer wann die ChargePower nach Stromänderungen enable/disable "korrekt" eingeschwungen ist. Eine Möglichkeit wäre, diese vor jedem Regelintervall neu über alle Ladepunkte auszulesen.
Du siehst vmtl. grad die Änderung aus https://github.com/evcc-io/evcc/commit/b81c267d3cb53911d42eb17617313380383734ba#diff-c456526d4bd9022a488ce32de208b40d86016e2c40b0c81a2dffe557c186377dL1548-L1553 wo wir bisher relativ willkürlich 100ms gewartet hatten. Das lässt sich zurück drehen, war aber auch keine "richtige" Lösung.
/cc @premultiply
bluegaspode
VolkerK62
RTTTC
Describe the bug Ich habe EVCC (nur) mit einer PV konfiguriert. EVCC berechnet die sitePower basierend auf PV Generierung. Bei der Berechnung werden veraltete Wert der ChargePower abgezogen, dies führt dann zum ungewollten hoch/abregeln der Ladesteuerung.
Beispiel: Zyklus1:
Zyklus 2:
Zyklus 3:
Im hier gezeigten Ablauf wird die Ladesäule in Zyklus 1+2 auf 16A gestellt, obwohl das bei einer PV-Leistung von 3kW viel zu hoch ist. Im Zyklus 3 wird korrekt heruntergeregelt, im kommenden Zyklus 4 wird weiter heruntergeregelt, weil evcc weiterhin mit falschen Werten rechnet.
Weiter unten sind vollständige Logs von 3 Zyklen (habe Kommentare ergänzt)
To Reproduce
Expected behavior
EVCC details: Show output of
evcc -v:Show evcc configuration file
evcc.yaml:uri: 0.0.0.0:7070 # uri for ui interval: 30s # control cycle interval # sponsor token enables optional features (request at https://cloud.evcc.io) # sponsortoken: # log settings log: debug levels: core: debug lp-1: debug lp-2: debug # meter definitions # name can be freely chosen and is used as reference when assigning meters to site and loadpoints # for examples see https://github.com/evcc-io/config#meters meters: - name: pv type: modbus model: sunspec uri: 192.168.1.108:1502 id: 71 # charger definitions # name can be freely chosen and is used as reference when assigning charger to vehicle # for examples see https://github.com/evcc-io/config#chargers chargers: - name: go-e type: go-e uri: http://192.168.1.109 # vehicle definitions # name can be freely chosen and is used as reference when assigning vehicle to loadpoint # for examples see https://github.com/evcc-io/config#vehicles vehicles: - name: kia type: kia title: e-Niro capacity: 64 user: # user password: # password # site describes the EVU connection, PV and home battery site: title: Home # display name for UI meters: # grid: grid # grid meter pvs: pv # battery: battery # battery meter # prioritySoC: 60 # give home battery priority up to this soc (0 to disable) residualPower: 0 # loadpoint describes the charger, charge meter and connected vehicle loadpoints: - title: Carport # display name for UI charger: go-e # charger # meters: # charge: charge # charge meter # vehicle: kia # vehicles: # use if multiple vehicles allowed to charge on this loadpoint # - ID.3 # - e-Up mode: minpv 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 min: 0 # immediately charge to 0% regardless of mode unless "off" (disabled) target: 100 # always charge to 100% estimate: false # set true to interpolate between api updates onDisconnect: # set defaults when vehicle disconnects mode: pv # switch back to pv mode targetSoC: 100 # charge to 100% onIdentify: # set defaults when vehicle is identified - e-Up: mode: pv # switch back to pv mode targetSoC: 100 # charge to 100% phases: 1 # ev phases (default 3) 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: 10m # threshold must be exceeded for this long threshold: 200 # maximum import power (W) guardduration: 5m # switch charger contactor not more often than this (default 10m) mincurrent: 6 # minimum charge current (default 6A) maxcurrent: 16 # maximum charge current (default 16A) # tariffs are the fixed or variable tariffs # cheap can be used to define a tariff rate considered cheap enough for charging tariffs: grid: # # either # type: tibber # cheap: 20 # ct/kWh # token: "476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4" # access token # homeid: "cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c" # optional if multiple homes associated to account # # or # type: awattar # cheap: 20 # ct/kWh # region: de # optional, choose at for Austria # mqtt message broker mqtt: # broker: localhost:1883 # topic: evcc # root topic for publishing, set empty to disable # user: # password: # influx database influx: # url: http://localhost:8086 # database: evcc # user: # password: # eebus credentials eebus: # uri: # :4712 # 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} 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://:@:/?fromAddress=&toAddresses=
Show evcc log output with
--log debug: