-
Notifications
You must be signed in to change notification settings - Fork 38
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
PV charging for dummies #181
Comments
The relation between power (W) and current (A) is power = voltage * current (P = U * I). The lowest possible setting where the charging actually starts is 6A, so that means 62303 = 4140W with 3-phase charging. With that approach, you could typically calculate the new limit something like this: Typically I would say, update your dynamic circuit limit every 20 or 30 seconds. Depends a bit on how often you get new values from your electrical meters though. If you only get new values once a minute, it makes no sense to update more often that that. |
First of all thanks a lot for taking the time for such an in depth answer. |
|
Thanks a ton. |
I do not recall saying that, but it sounds reasonable. :) |
I'm on a 3 phase grid in Denmark (seens as TN net by Eassee) and does not yes have an interface to neither my main meter or my solar inverter - but i'm exploring the possibilities :-) But for power calculation the real voltage is important. It does make a difference. In many places you will see the voltage drops significantly when adding 11-22kW for an ev charger. And the neighbours on the same transformator may also draw power unevenly. Right now i can in the Easee app see that i have 229V on L1 while only 220V on L3 - with the house "idling" without major power drawn (only light, pc etc - but no heating or ev charging) In the ha implementation only the L1 voltage is available. I have not checked whether it is a restriction in the API but when i looked at the 3 voltages they were so different that i'm pretty sure that it is not an average but the L1 voltage |
I have since switched over to evcc.io which takes care of all the calculating of the voltages, amperes, etc. |
All the different voltages are available as attributes in the voltage sensor. |
Found it :-) the HA rabbit hole is deep and there is a lot to comprehend. Now i just need to learn how to address it |
In a template you can access an attribute like this:
|
Assumption: I use 90% of solar produced power from my solaredge system to charge the car. The SolarEdge system ist controlled through cloud API and therefore only updated every 15 minutes (see https://www.home-assistant.io/integrations/solaredge), that's why updating the Easee Wallbox every minute is enough. This is what I did to add the automations (2 separate):
You need to replace the charger_id with the ID of your Easee Wallbox. This is as simple YAML setup for charge control. If the current power alias: Solar Charge Control
description: Calculate Solar Charging
mode: single
trigger:
- platform: time_pattern
minutes: "/1"
condition:
- condition: numeric_state
entity_id: sensor.solaredge_current_power
above: "5000"
action:
- service: easee.set_charger_circuit_dynamic_limit
data:
charger_id: 123456
currentP1: >-
{{ ((states('sensor.solaredge_current_power') | float) /(230*3) * 0.9) }}
currentP2: >-
{{ ((states('sensor.solaredge_current_power') | float) /(230*3) * 0.9) }}
currentP3: >-
{{ ((states('sensor.solaredge_current_power') | float) /(230*3) * 0.9) }}
If I don't have enough power to load the car, just set all 3 lines to zero. Therefore I've created a second Automation, which I can disable separately. If the production in watt goes below 4999 Watt (follow the steps above and insert this YAML code): alias: Solar Charge Disable
description: Disable Charging on Low Solar Power
mode: single
trigger:
- platform: time_pattern
minutes: "/1"
condition:
- condition: numeric_state
entity_id: sensor.solaredge_current_power
below: "4999"
action:
- service: easee.set_charger_circuit_dynamic_limit
data:
charger_id: 123456
currentP1: 0
currentP2: 0
currentP3: 0 We don't have any other long running consumers yet. This is enough for my setup. I've written a more detailed block post in German on my site: https://konstantin.filtschew.de/blog/2022/08/24/ladeleistung-ueber-die-easee-wallbox-in-verbindung-mit-solaredge-wechselrichter-ueber-home-assistant-steuern/ |
Question
First of all thanks a ton for this intergration!
I'm trying to setup my easee wallbox to charge from excess PV from my solaredge system.
I have read issue #120 but I fear I'm just a tad to stupid when it comes to electricity.
My solaredge reports how much kw are being produced and I can see how much the house is using.
Say I'm producing 7kw and the house is using 0.5kw then I would like to limit charging from the easee to say 6kw (to keep a small overhead in case the house needs more)
Now the only thing I see in the integration is the option to change the A via "set_charger_circuit_dynamic_limit".
I can see the A produced from my solaredge as well but how do I calculate how much A I should set for the easee charger? How much A do I have to deduct for the 1kw buffer for the house?
Also do I just have to limit the A on one phase or on all three phases via set_charger_circuit_dynamic_limit? Or is the dynamic_limit the cumulation of whats available for all three phases?
I'm just pretty confused and hope someone already has something similar neatly set up and would be willing to share his setup. Maybe even make a small wiki entry for other dummies like me ;)
Thanks a ton!
What version of the integration are you using?
easee-0.9.42
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: