Epic: Load management enhancements #14261

andig · 2024-06-09T10:49:54Z

Fail-safe mode on errors (Circuits: assume overload if meter fails #14249)
Add circuits api to support SteuVE (§14a EnWG) [german law]
Handle timers (EVCC controlling Alfen to 0W without relay on/off? #14114 (reply in thread))
Honor priorities (Add circuits docs#567)
Support planner (Add circuits docs#567, Planner: Conflict with load management and suggestion for Solcast and consumption #14049)
Visualisation (Load management - visualisation ? #14323) Config UI: circuit status #15110
Better limiting in fast mode (Fast mode (with peak shaving configured) doesn't start at auto-switching phases #14827)

VolkerK62 · 2024-06-11T04:38:57Z

Frage: könnte man hier auch noch eine Schieflast-Überwachung mit reinnehmen?

premultiply · 2024-06-11T07:05:45Z

Hier noch nicht, da das eine genaue Zuordnung der Phasen der ersten einzelnen Circuits und Loadpoints erfordert.

VolkerK62 · 2024-06-30T13:22:34Z

Add circuits api to support SteuVE

Noch ein Problem entdeckt, oder ich habe einen Gedankenfehler?
2 Ladepunkte hängen am selben Kabelanschluss. Dieser Anschluss hat kein Meter.
Jeder Ladepunkt (hat sein eigenes Meter) bekommt seinen eigenen circuit. (Annahme von mir, dass darüber später die Regelung bzgl SteuVE läuft).
Beide Ladepunkte sind dem circuit "loadpoints" zugeordnet (wegen der Maximalleistung des Anschlusses).
Der circuit "loadpoints" ist somit nur eine Zusammenfassung der beiden Ladepunkte.
Es kommt der Fehler circuit loadpoints has no meter an no loadpoint assigned.

circuits:
  - name: main
    title: Hauptsicherung
    maxCurrent: 48
  - name: loadpoints
    title: Ladepunkte
    maxCurrent: 16
    parent: main
  - name: lp1
    title: LP1
    maxCurrent: 16
    parent: loadpoints
  - name: lp2
    title: LP2
    maxCurrent: 16
    parent: loadpoints

andig · 2024-06-30T13:26:07Z

Kein Denkfehler, aktuelle Restriktion. Die Prüflogik berücksichtigt keine Hierarchie von Circuits über 2 Ebenen hinaus. Würde ich auch erst angeben, wenn das wirklich relevant sein sollte- hier brauchst Du das ja nicht weil Du einfach beide Boxen an den loadpoints Circuit hängen kannst?

VolkerK62 · 2024-06-30T13:34:16Z

hier brauchst Du das ja nicht weil Du einfach beide Boxen an den loadpoints Circuit hängen kannst?

aktuell ja.
Aber der Hinweis auf "SteuVE" hat mich auf diesen Gedanken gebracht.
Diese Regulierung betrifft ja jede Wallbox einzeln und wenn die Regelung über den circuit laufen soll (was ja Sinn macht), dann braucht jede Wallbox einen eigenen.
Aber, stimmt, ist noch nicht relevant.

premultiply · 2024-06-30T13:50:08Z

Die Dimmung erfolgt pauschal für alle SteuVE am Anschluss über die netzrelevante Leistungsaufnahme.
Im Fall eines EMS gibt es dazu eine vglw. komplizierte Formel für die Summe.
Es wird dabei leider nicht nur einfach n * 4200 kW als SteuVE-Limit vorgegeben.

VolkerK62 · 2024-06-30T15:17:22Z

OK, "Gleichzeitigkeitsfaktor" ist das Stichwort. Danke

jeffborg · 2024-07-18T06:04:48Z

It would be good to allow use of plugins to set the values for circuit. Not sure if that would be a start to help support SteuVE

Roeland54 · 2024-07-20T09:25:49Z

I have created an english version of the documentation page for loadbalancing. (evcc-io/docs#584)

But I I have noticed a difference in behavior and how the documentation describes how it should work. This statement: "Alle Ladepunkte ohne explizite Stromkreiszuordnung werden diesem Hauptstromkreis zugeordnet. " I conclude from this that if I have only one circuit "main" I do not need to specify "circuit" on the loadpoint configuration. But if I try this loadmanagement does not work on mij loadpoints. I need to specify "circuit: main" on the loadpoints and then it works.

So is this a bug in loadmanagement or just wrong documentation?

Roeland54 · 2024-07-23T17:18:11Z

In my use-case these warnings are not needed. Overcurrent is expected when we start cooking so it happens almost every day.
I am wondering if these warning have any use to other people? Otherwise maybe they could be disabled by default?

TweetsOfNiklas · 2024-07-26T09:22:30Z

Ich habe auch noch ein Problem in Kombination von Lastmanagement und dem Homewizard P1 Meter gefunden. Der Homewizard gibt egal ob Einspeisung oder Bezug eine positive Amperezahl aus. Bedeutet wenn Einspeisung größer als die Limitierung ist, lädt gar nichts mehr. Soll ich dafür ein eigenes Issue erstellen?

[circuit-main] WARN 2024/07/26 11:15:46 over current detected: 21.7A > 10A
[site ] DEBUG 2024/07/26 11:15:46 pv power: 16079W
[site ] ERROR 2024/07/26 11:15:46 battery 1 soc: outdated
[site ] DEBUG 2024/07/26 11:15:46 battery soc: 0%
[site ] DEBUG 2024/07/26 11:15:46 battery power: 190W
[site ] DEBUG 2024/07/26 11:15:46 grid meter: -14162W
[site ] DEBUG 2024/07/26 11:15:46 grid currents: [21.7 21 16.6]A
[site ] DEBUG 2024/07/26 11:15:46 site power: -13822W
[lp-2 ] DEBUG 2024/07/26 11:15:46 charge voltages: [241 241 242]V
[lp-2 ] DEBUG 2024/07/26 11:15:46 detected connected phases: 3p
[lp-2 ] DEBUG 2024/07/26 11:15:47 charge total import: 1083.804kWh
[lp-2 ] DEBUG 2024/07/26 11:15:47 charger status: B
[circuit-main] DEBUG 2024/07/26 11:15:47 validate current: 21.7A + (0A -> 16A) > 10A capped at 0A
[lp-2 ] DEBUG 2024/07/26 11:15:47 !! active phases: 3p = min(0p measured 0p vehicle 3p physical 0p charger)
[site ] DEBUG 2024/07/26 11:15:55 ----
[lp-1 ] DEBUG 2024/07/26 11:15:55 charge power: 0W
[lp-1 ] DEBUG 2024/07/26 11:15:55 charge currents: [0 0 0]A
[lp-2 ] DEBUG 2024/07/26 11:15:55 charge power: 5W
[lp-2 ] DEBUG 2024/07/26 11:15:56 charge currents: [0 0.0442 0]A
[lp-3 ] DEBUG 2024/07/26 11:15:56 charge power: 0W
[lp-3 ] DEBUG 2024/07/26 11:15:56 charge currents: [0 0 0]A
[circuit-outdoor] DEBUG 2024/07/26 11:15:56 power: 5.3418W
[circuit-outdoor] DEBUG 2024/07/26 11:15:56 current: 0.0442A
[circuit-main] DEBUG 2024/07/26 11:15:56 power: -13970W

Roeland54 · 2024-07-26T10:10:18Z

This is a homewizard issue not a load management issue. So maybe better to open a new issue.
What you see is strange because I see negative currents in the messages from the homewizard api and the docs also show negative values are possible for current. If you open a separate issue we can discus it further. (if possible use english that would make it easier for me).

andig · 2024-07-28T10:12:57Z

But I I have noticed a difference in behavior and how the documentation describes how it should work

@Roeland54 lets move this discussion to evcc-io/docs#587

RenatusRo · 2024-10-23T15:29:07Z

It would be good to allow use of plugins to set the values for circuit. Not sure if that would be a start to help support SteuVE

Yes, would very much like to have a restful/mqtt api.

2 use cases in the frame of the flemish capacity tariff/peak shaving:

if the intended max already has been surpassed (by whatever reason) we can lift the limit for the remaining days of the month - it has to be paid for anyway
if we monitor the current quarter hourly peak, we can decide at minute 10 of 15 to give more power to the circuit for the remaining 5 minutes without hitting the intended limit (not really netzdienlich, but we are very liberalistic here).

see #16784

andig · 2024-10-23T16:28:42Z

This would be #16809. In deviation from the other plugins and given that max power/currents already are config values, this PR works by allowing the plugin to override the current value. If plugin fails, the configured value is acts as fallback.

hyperbart · 2024-10-28T12:03:35Z

This would be #16809. In deviation from the other plugins and given that max power/currents already are config values, this PR works by allowing the plugin to override the current value. If plugin fails, the configured value is acts as fallback.

Nice! I am most certainly going to enable this/test this. I had been working on a python script that pulls the latest peak of the month and modifies it accordingly in the evcc.yml but if you have exposed this via an API/HTTP Endpoint that would be even easier/better.

Looking forward to this @andig , super!

hyperbart · 2024-10-31T10:13:33Z

@andig Is the EVCC API documentation automatically updated?
How can I determine which endpoints and values can be used to modify this?

andig · 2024-10-31T10:20:33Z

No automation.

hyperbart · 2024-10-31T10:21:21Z

Allright, best to wait then for the documentation, correct?

andig · 2024-10-31T10:23:23Z

Sorry- for what?

hyperbart · 2024-10-31T10:27:07Z

I was/am under the assumption/understanding the recent pull request #16809 allows us to set the maxPower on the circuit externally via the HTTP API already(?).

I wanted to start experimenting with this but couldn't find the documentation yet, but maybe I have misunderstood the current status of said functionality.

andig · 2024-10-31T10:36:31Z

Just add https://github.com/evcc-io/evcc/pull/16809/files#diff-e558b29f57bfef72b6614f8a345c713e6fe64cd1e9032e99a7b7b998a0442271R49-R50. Docs to follow in evcc-io/docs#658. That's not an "api" but simply configuration of the hems device.

VolkerK62 · 2024-10-31T11:17:50Z

Example:

circuits: # Loadmanagement
- name: main
  title: Hausanschluss
  maxCurrent: 35
  GetMaxCurrent:
    source: mqtt
    topic: Haus/circuit/maxcurrent
  maxpower: 24000
  GetMaxPower:
    source: mqtt
    topic: Haus/circuit/maxpower
  meter: grid

andig added the backlog Things to do later label Jun 9, 2024

andig mentioned this issue Jun 20, 2024

Planner: Conflict with load management and suggestion for Solcast and consumption #14049

Closed

andig mentioned this issue Jul 28, 2024

How is loadpoint to root circuit assignment expected to work? evcc-io/docs#587

Closed

naltatis mentioned this issue Jul 28, 2024

Config UI: circuit status #15110

Merged

Roeland54 mentioned this issue Sep 23, 2024

Load management should not generate alarm notifications #16284

Closed

andig mentioned this issue Oct 23, 2024

Circuit: make max power and current externally updatable #16809

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Epic: Load management enhancements #14261

Epic: Load management enhancements #14261

andig commented Jun 9, 2024 •

edited

Loading

VolkerK62 commented Jun 11, 2024

premultiply commented Jun 11, 2024

VolkerK62 commented Jun 30, 2024

andig commented Jun 30, 2024

VolkerK62 commented Jun 30, 2024

premultiply commented Jun 30, 2024

VolkerK62 commented Jun 30, 2024

jeffborg commented Jul 18, 2024

Roeland54 commented Jul 20, 2024

Roeland54 commented Jul 23, 2024

TweetsOfNiklas commented Jul 26, 2024 •

edited

Loading

Roeland54 commented Jul 26, 2024

andig commented Jul 28, 2024

RenatusRo commented Oct 23, 2024

andig commented Oct 23, 2024

hyperbart commented Oct 28, 2024

hyperbart commented Oct 31, 2024 •

edited

Loading

andig commented Oct 31, 2024

hyperbart commented Oct 31, 2024

andig commented Oct 31, 2024

hyperbart commented Oct 31, 2024

andig commented Oct 31, 2024

VolkerK62 commented Oct 31, 2024

Epic: Load management enhancements #14261

Epic: Load management enhancements #14261

Comments

andig commented Jun 9, 2024 • edited Loading

VolkerK62 commented Jun 11, 2024

premultiply commented Jun 11, 2024

VolkerK62 commented Jun 30, 2024

andig commented Jun 30, 2024

VolkerK62 commented Jun 30, 2024

premultiply commented Jun 30, 2024

VolkerK62 commented Jun 30, 2024

jeffborg commented Jul 18, 2024

Roeland54 commented Jul 20, 2024

Roeland54 commented Jul 23, 2024

TweetsOfNiklas commented Jul 26, 2024 • edited Loading

Roeland54 commented Jul 26, 2024

andig commented Jul 28, 2024

RenatusRo commented Oct 23, 2024

andig commented Oct 23, 2024

hyperbart commented Oct 28, 2024

hyperbart commented Oct 31, 2024 • edited Loading

andig commented Oct 31, 2024

hyperbart commented Oct 31, 2024

andig commented Oct 31, 2024

hyperbart commented Oct 31, 2024

andig commented Oct 31, 2024

VolkerK62 commented Oct 31, 2024

andig commented Jun 9, 2024 •

edited

Loading

TweetsOfNiklas commented Jul 26, 2024 •

edited

Loading

hyperbart commented Oct 31, 2024 •

edited

Loading