Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow defining Circuits, which consist of two (or more) Loadpoints #14077

Closed
bodomenke opened this issue May 27, 2024 · 1 comment
Closed

Allow defining Circuits, which consist of two (or more) Loadpoints #14077

bodomenke opened this issue May 27, 2024 · 1 comment
Labels
duplicate This issue or pull request already exists

Comments

@bodomenke
Copy link

As-Is Situation
I have two easee wallboxes (each 11kW) on the same electrical circuit, which is limited to 11kW. Definition in easee cloud is as follows:

  • One circuit with 11kW (actually limited to 15A for each phase)
  • Two wallboxes with 11kW (actually limited to 15A for each phase) on the previous defined circuit

Loadbalancing between the two wallboxes and ensuring that both wallboxes combined do not consume more than 15A for each phase is being done by easee.

This setup is working pretty well with evcc: Even if both loadpoints have defined a max current of 16A per phase and two cars are charging, easee is taking care that current is not exceeding 15A per phase on the circuit.

Problem
If I define plans for both loadpoints, which are overlapping, then evcc doesn’t consider that, since it doesn’t know about the circuit limit. evcc assumes, that both loadpoints are capable to consume the max current of 16A for each phase. For this reason the plans, which evcc creates for hitting the departure time fail, since the loadpoints will only receive 50% of the current (which is balanced by easee).

Solution

  • Define a circuit entity in evcc, which has a „Max. Current“ setting
  • Allow to attach multiple loadpoints to one (the same) circuit
  • Consider „Max. Current“ setting of the circuit, when (overlapping) plans are being defined for the loadpoints

Alternatives / Workaround
A manual workaround is to limit temporarily the „Max. Current“ setting of the loadpoints to 7A for each loadpoint. This is not ideal.

@andig
Copy link
Member

andig commented May 27, 2024

Duplikat: #14049

@andig andig closed this as completed May 27, 2024
@andig andig added the duplicate This issue or pull request already exists label May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants