Site: add smart feed-in disable (aka zero feed-in)

[andig]

Fix https://github.com/evcc-io/evcc/issues/21747, depends on https://github.com/evcc-io/evcc/pull/21813 Also fixes https://github.com/evcc-io/evcc/issues/21832

Disable solar feed-in when feed-in becomes expensive for the user (i.e. network restriction visible due to feed-in tariff). Implemented by restricting the PV inverter to 0W feed-in power. Requires supported inverter.

💸 add feed-in visualization to forecast modal 👇 proper handling of negative prices (aligned 0-axis)

TODO

• [x] UI @naltatis
• [ ] finalise api, look into https://github.com/evcc-io/evcc/discussions/19422#discussioncomment-13817712
• [x] do we need to control batteries or only pv? Batteries shouldn't feed-in, so no?
• [x] add e2e tests @naltatis
• [x] highlight affected time slots @naltatis
• [x] implement correct price options @naltatis

/cc @Maschga wenn Du magst könntest Du hier branchen und einen PR für RCT erstellen und testen.

Out of scope

• Migrate "battery grid charge" feature to forecast modal
• Make forecast a top-level page (not a modal) > introduce bottom bar app nav

grid feedin.webm

[andig]

@naltatis diesmal ein neuer Fehler:

·

  1) [chromium] › tests/config-loadpoint.spec.js:420:3 › loadpoint › user-defined charger ──────────

    Error: Timed out 5000ms waiting for expect(locator).toContainText(expected)

    Locator: getByTestId('charger-modal').getByTestId('test-result')
    Expected string: "Status: successful"
    Received string: "Status: failedvalidateyaml: line 14: mapping values are not allowed in this context"
    Call log:
      - expect.toContainText with timeout 5000ms
      - waiting for getByTestId('charger-modal').getByTestId('test-result')
        9 × locator resolved to <div errorline="14" data-v-f8692870="" data-testid="test-result" class="test-result my-4 p-4">…</div>
          - unexpected value "Status: failedvalidateyaml: line 14: mapping values are not allowed in this context"


      453 |     await expect(restResult).toContainText("Status: unknown");
      454 |     await restResult.getByRole("link", { name: "validate" }).click();
    > 455 |     await expect(restResult).toContainText("Status: successful");
          |                              ^
      456 |     await expect(restResult).toContainText(["Status", "charging"].join(""));
      457 |     await expect(restResult).toContainText(["Enabled", "yes"].join(""));
      458 |     await expect(restResult).toContainText(["Power", "11.0 kW"].join(""));
        at /home/runner/work/evcc/evcc/tests/config-loadpoint.spec.js:455:30

Vmtl. aus https://github.com/evcc-io/evcc/pull/21813?

[naltatis]

@andig hier kommst scheinbar beim Ersetzen der YAML-Vorlage durch den eigentlichen Code zur Fehlverhalten. Aber immer unterschiedlich. Ich schau mal was hier die Ursache ist.

[andig]

@naltatis kannst du mit dem Merge helfen?

[andig]

UI pack ich nicht…

[naltatis]

@andig resolve the conflict - mostly. I've left one for you :D

[naltatis]

do we need to control batteries or only pv? Batteries shouldn't feed-in, so no?

yes, for me it's an pv feature. Requirements for showing it in the ui: dynamic tariff + controllable pv inverter Makes placement of the feature a little tricky since it does not fit in the existing "Battery settings" model. Guess we need a dedicate "Solar settings" modal only for this feature.

[andig]

@naltatis back over to you?

[naltatis]

Added the option/limit to the forecast dialog since we dont have a global place for pv-based settings. In a future iteration we should promote forecast (together with other charts) to a top level page and also move battery grid charge there. So one place to see all your forecasted data (production, price, ...) and can make decisions based on this. Future optimizer hints or effects could also live there.

[naltatis]

@andig magst du den Konflikt hier auflösen?

[andig]

Done

[naltatis]

Done

But broken

[naltatis]

Should be fixed now.

[naltatis]

Added highlighting of affected time slots. See updated screenshots and video in description 👆

[naltatis]

Matching limit options:

[naltatis]

Reflect active limit in energy flow

[naltatis]

@andig all done from my side

[jeffborg]

I have a question/maybe a complication about this, currently doing this function from home assistant if evcc isn't active solar and the feed in price is negative (ie: paying to export power to grid) then I flip the load following register on my solar inverter, But from evcc I set the export price to 0 always as I consider evcc to be consuming solar power which has no value and not a negative value.

See the example below the export price is actually -2.9c a kwh but in evcc by using custom forecast the current period is set to 0 just so the charging sessions cost is increasing in price and not decreasing.

So in relation to this pr, if evcc can prevent export costing $$ then consideration probably should be given that this is actually 0 in value when calculating charging sessions cost. I'm not seeing anything related to the charging sessions cost in the pr.

[andig]

See the example below the export price is actually -2.9c a kwh but in evcc by using custom forecast the current period is set to 0

Why? Forecast wrong? Seems OT here.

[jeffborg]

Why? Forecast wrong? Seems OT here.

No -2.9c is the actual feedin price for the current 5 minute interval (IE you pay to export), I just use some jq on the feedin forecast to ensure evcc never sees negative prices for the current feedin interval as that mucks up the charging session cost calculations. (car is not earning money by charging because if it wasn't charging the solar would be automatically curtailed and I wouldn't be paying to export - hence being calculated as 0 is correct) Might be better off discussed on #21747