Skip to content

Ecoflow steam PV output too high, if combined with external PV #29180

@Metatron2k2

Description

@Metatron2k2

Describe the bug

When an Ecoflow Stream Mini-PV is combined with a normal PV, the output is reported too high. EVCC is using the PV Sum for the display in EVCC. For some reason Ecoflow is also counting the excess Power from other PVs towards PV Sum if it would otherwise go to the grid. When both Stream PV and external PV are put into EVCC the power basically gets powered twice.

Steps to reproduce

  1. Setup Ecoflow stream together with other PV.
  2. Obersve the power. It can by far exceed the maximum power of the panels connected to the Ecoflow Stream

Configuration details

interval: 30s 

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

meters:
  - name: shelly_main
    type: template
    template: shelly-pro-3em
    usage: grid
setzen (optional)
  - name: shelly_pv
    type: template
    template: shelly-pro-3em
    usage: pv
  - name: shelly_wp
    type: template
    template: shelly-pro-3em
    usage: ext
  - name: shelly_bkw
    type: template
    template: shelly-1pm
    usage: pv
  - name: ecoflow_grid
    type: template
    template: ecoflow-stream
    usage: grid
    region: auto 
    cache: 30s 
  - name: ecoflow_pv
    type: template
    template: ecoflow-stream
    usage: pv
  - name: ecoflow_battery
    type: template
    template: ecoflow-stream
    usage: battery
chargers:
  - name: links
    type: template
    template: openwb-pro
  - name: rechts
    type: template
    template: openwb-pro
vehicles:
  - name: tesla_rot
    type: template
    template: tesla-ble
    title: Tesla Rot # Titel, Wird in der Benutzeroberfläche angezeigt (optional)
    capacity: 75 # Akkukapazität (kWh), optional
    port: 8081 # Port, Port des Tesla BLE HTTP Proxy (optional)
    timeout: 90s # Zeitüberschreitung, optional
  - name: tesla_blau
    type: template
    template: tesla-ble
    title: Tesla Blau # Titel, Wird in der Benutzeroberfläche angezeigt (optional)
    capacity: 50 # Akkukapazität (kWh), optional
    timeout: 90s # Zeitüberschreitung, optional
site:
  title: Home # display name for UI
  meters:
    grid: shelly_main # grid meter
    pv:
      - shelly_pv
      - ecoflow_pv
    battery:
      - ecoflow_battery
    aux:
      - shelly_wp
  residualPower: 0 # additional household usage margin

loadpoints:
  - title: openWB Pro links # display name for UI
    charger: links # charger
    mode: "pv"
    priority: 0 # relative priority for concurrent charging in PV mode with multiple loadpoints (higher values have higher priority)
    soc:
      poll:
        mode: connected
        interval: 60m
      estimate: true 
    enable: # pv mode enable behavior
      delay: 1m # threshold must be exceeded for this long
      threshold: 0 #
    disable: # pv mode disable behavior
      delay: 3m # threshold must be exceeded for this long
      threshold: 0 # maximum import power (W)
  - title: openWB Pro rechts # display name for UI
    charger: rechts # charger
    mode: "pv"
    priority: 0 
    soc:
      poll:
        mode: connected
        interval: 60m
      estimate: true 
    enable: # pv mode enable behavior
      delay: 1m # threshold must be exceeded for this long
      threshold: 0 
    disable: # pv mode disable behavior
      delay: 3m # threshold must be exceeded for this long
      threshold: 0 # maximum import power (W)

tariffs:
  currency: EUR # three letter ISO-4217 currency code (default EUR)
  grid:
    # either static grid price (or price zones)
    type: fixed
    price: 0.2220 # EUR/kWh
  feedin:
    # rate for feeding excess (pv) energy to the grid
    type: fixed
    price: 0.0917 # EUR/kWh

Log details

No logs required

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

Docker container

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

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    devicesSpecific device supportstaleOutdated and ready to close

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions