Verfügbare Leistung "schätzen"

[MehrCurry]

Hallo ich habe eine ACE3000 Zähler, der zwar eine optische S0 Schnittstelle hat, aber die Daten ohne Vorzeichen liefert. Ich kann also nicht zwischen Bezug und Einspeisung unterscheiden.

Also ist meine nächste Idee, die Einspeisung zu schätzen: PV - EVCC-Ladeleistung - geschätzter Verbrauch des Hauses.

In meiner Config sieht das so aus:

meters:
  - type: default
    name: solarlog
    power:
      type: mqtt
      topic: solarlog/ac
      timeout: 30s # don't accept values older than timeout
      scale: 1000 # floating point factor applied to result, e.g. for Wh to kWh conversion
  - type: custom
    name: guessed
    power:
      source: calc
      add:
        - source: mqtt
          topic: solarlog/ac
          timeout: 30s # don't accept values older than timeout
          scale: -1000 # floating point factor applied to result, e.g. for Wh to kWh conversion
        - source: mqtt
          topic: evcc/loadpoints/1/chargePower
          timeout: 120s # don't accept values older than timeout
        - source: js
          script: |
            600;

Die ChargePower aus dem eigenen MQTT Topic zu lesen ist irgendwie nicht so elegant, und funktioniert auch nicht zuverlässig. Auf der EVCC Rest API habe ich ich keine Möglichkeit gefunden darauf zuzugreifen. Gibt es nicht noch einen anderen Weg?

[premultiply]

Einfach die D0-Schnittstelle initialisieren:
https://wiki.volkszaehler.org/hardware/channels/meters/power/edl-ehz/itron_ace3000_type_260

[premultiply]

Mittels residualPower: unter site:
residualPower // PV meter only: household usage. Grid meter: household safety margin

[MehrCurry]

Das mag er gar nicht:

Mai 21 13:15:23 evcc evcc[6166]: [main  ] FATAL 2021/05/21 13:15:23 failed configuring site: missing grid meter

[MehrCurry]

residualPower

Ah, den kannte ich noch nicht

[premultiply]

Das mag er gar nicht:

Mai 21 13:15:23 evcc evcc[6166]: [main  ] FATAL 2021/05/21 13:15:23 failed configuring site: missing grid meter

@andig Warum?

[andig]

Weil #953

[andig]

Zur Lösung bitte mal #1064 ausprobieren- ich bin mir mit dem Vorzeichen noch unsicher ob das so rum passt?

[MehrCurry]

Hab ich gemacht. Branch ausgecheckt und gebaut.

site:
  title: Zuhause # display name for UI
  residualPower: 600
  meters:
    pv: solarlog
#    grid: grid

[main  ] INFO 2021/05/22 12:16:13 evcc 0.55 (74c75e4)
[main  ] INFO 2021/05/22 12:16:13 using config file /home/pi/wrk/evcc/evcc.yaml
[main  ] INFO 2021/05/22 12:16:13 listening at 0.0.0.0:7070
[mqtt  ] INFO 2021/05/22 12:16:13 connecting evcc-175835197 at 192.168.187.36:1883
[mqtt  ] DEBUG 2021/05/22 12:16:13 192.168.187.36:1883 connected
[lp-1  ] WARN 2021/05/22 12:16:13 poll mode '{always 5m0s}' may deplete your battery or lead to API misuse. USE AT YOUR OWN RISK.
[lp-1  ] WARN 2021/05/22 12:16:13 poll interval '5m0s' is lower than 1h0m0s and may deplete your battery or lead to API misuse. USE AT YOUR OWN RISK.
[lp-1  ] ERROR 2021/05/22 12:16:14 charger: dial tcp 192.168.0.8:502: i/o timeout
[site  ] INFO 2021/05/22 12:16:14 site config:
[site  ] INFO 2021/05/22 12:16:14   meters:    grid ✗ pv ✓ battery ✗
[site  ] INFO 2021/05/22 12:16:14     pv:      power ✓ energy ✗ currents ✗
[lp-1  ] INFO 2021/05/22 12:16:14 loadpoint 1:
[lp-1  ] INFO 2021/05/22 12:16:14   mode:      pv
[lp-1  ] INFO 2021/05/22 12:16:14   charger:   power ✗ energy ✗ currents ✗ timer ✓
[lp-1  ] INFO 2021/05/22 12:16:14   meters:    charge ✗
[lp-1  ] INFO 2021/05/22 12:16:14   vehicles:  ✓
[lp-1  ] INFO 2021/05/22 12:16:14     car 0:   range ✗ finish ✗ status ✓ climate ✗
[lp-1  ] INFO 2021/05/22 12:16:14     car 1:   range ✗ finish ✗ status ✓ climate ✗
[site  ] DEBUG 2021/05/22 12:16:14 ----
[site  ] DEBUG 2021/05/22 12:16:16 pv power: 727W
[site  ] DEBUG 2021/05/22 12:16:16 site power: 1327W
[lp-1  ] DEBUG 2021/05/22 12:16:16 charge power: 0W
[lp-1  ] ERROR 2021/05/22 12:16:17 charge timer: dial tcp 192.168.0.8:502: i/o timeout
[lp-1  ] ERROR 2021/05/22 12:16:18 charger: dial tcp 192.168.0.8:502: i/o timeout
[site  ] DEBUG 2021/05/22 12:16:24 ----
[site  ] DEBUG 2021/05/22 12:16:24 pv power: 727W
[site  ] DEBUG 2021/05/22 12:16:24 site power: 1327W
[lp-1  ] DEBUG 2021/05/22 12:16:24 charge power: 0W
[lp-1  ] ERROR 2021/05/22 12:16:25 charge timer: dial tcp 192.168.0.8:502: i/o timeout
[lp-1  ] ERROR 2021/05/22 12:16:26 charger: dial tcp 192.168.0.8:502: i/o timeout
[site  ] DEBUG 2021/05/22 12:16:34 ----
[site  ] DEBUG 2021/05/22 12:16:34 pv power: 705W
[site  ] DEBUG 2021/05/22 12:16:34 site power: 1305W
[lp-1  ] DEBUG 2021/05/22 12:16:34 charge power: 0W
[lp-1  ] ERROR 2021/05/22 12:16:35 charge timer: dial tcp 192.168.0.8:502: i/o timeout
[lp-1  ] ERROR 2021/05/22 12:16:36 charger: dial tcp 192.168.0.8:502: i/o timeout

Vorzeichen ist IMHO falsch. 705 - 600 = 105 (und nicht 1305). Oder muss ich residualPower: -600 setzen?

[MehrCurry]

Achso, die 105 wären ja Einspeisung, also müssten dass -105 sein ... als eher 600 - 705 = -105

[andig]

Es müssten dann sein:

-727 (=Erzeugung!) + 600 (Hausverbrauch) = -127.

Ich korrigiere das Vorzeichen nochmal. Passt auch zur Doku:

EVCC uses positive (+) sign for incoming energy (grid consumption, PV inverter production or home battery discharge) and negative (-) sign for outgoing energy (grid feed-in, PV inverter remaining usage or home battery charge). All remaining home power usage, including the charger, is always of positive (+) sign.

[andig]

Ist korrigiert

[MehrCurry]

Ich hab jetzt den Master gebaut. Das passt so für mich. Danke!

[main  ] INFO 2021/05/23 07:12:12 evcc 0.55 (e283a37)
[main  ] INFO 2021/05/23 07:12:12 using config file /home/pi/wrk/evcc/evcc.yaml
[main  ] INFO 2021/05/23 07:12:12 listening at 0.0.0.0:7070
[mqtt  ] INFO 2021/05/23 07:12:12 connecting evcc-1981550062 at 192.168.187.36:1883
[mqtt  ] DEBUG 2021/05/23 07:12:12 192.168.187.36:1883 connected
[lp-1  ] WARN 2021/05/23 07:12:12 poll mode '{always 5m0s}' may deplete your battery or lead to API misuse. USE AT YOUR OWN RISK.
[lp-1  ] WARN 2021/05/23 07:12:12 poll interval '5m0s' is lower than 1h0m0s and may deplete your battery or lead to API misuse. USE AT YOUR OWN RISK.
[lp-1  ] ERROR 2021/05/23 07:12:13 charger: dial tcp 192.168.0.8:502: i/o timeout
[site  ] INFO 2021/05/23 07:12:13 site config:
[site  ] INFO 2021/05/23 07:12:13   meters:    grid ✗ pv ✓ battery ✗
[site  ] INFO 2021/05/23 07:12:13     pv:      power ✓ energy ✗ currents ✗
[lp-1  ] INFO 2021/05/23 07:12:13 loadpoint 1:
[lp-1  ] INFO 2021/05/23 07:12:13   mode:      pv
[lp-1  ] INFO 2021/05/23 07:12:13   charger:   power ✗ energy ✗ currents ✗ timer ✓
[lp-1  ] INFO 2021/05/23 07:12:13   meters:    charge ✗
[lp-1  ] INFO 2021/05/23 07:12:13   vehicles:  ✓
[lp-1  ] INFO 2021/05/23 07:12:13     car 0:   range ✗ finish ✗ status ✓ climate ✗
[lp-1  ] INFO 2021/05/23 07:12:13     car 1:   range ✗ finish ✗ status ✓ climate ✗
[site  ] DEBUG 2021/05/23 07:12:13 ----
[site  ] DEBUG 2021/05/23 07:12:15 pv power: 840W
[site  ] DEBUG 2021/05/23 07:12:15 site power: -240W
[lp-1  ] DEBUG 2021/05/23 07:12:15 charge power: 0W
[lp-1  ] ERROR 2021/05/23 07:12:16 charge timer: dial tcp 192.168.0.8:502: i/o timeout
[lp-1  ] ERROR 2021/05/23 07:12:17 charger: dial tcp 192.168.0.8:502: i/o timeout
[site  ] DEBUG 2021/05/23 07:12:23 ----
[site  ] DEBUG 2021/05/23 07:12:23 pv power: 802W
[site  ] DEBUG 2021/05/23 07:12:23 site power: -202W
[lp-1  ] DEBUG 2021/05/23 07:12:23 charge power: 0W
[lp-1  ] ERROR 2021/05/23 07:12:24 charge timer: dial tcp 192.168.0.8:502: i/o timeout
[lp-1  ] ERROR 2021/05/23 07:12:25 charger: dial tcp 192.168.0.8:502: i/o timeout