-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add option to change "max. grid supply to grid from battery" #9
Comments
@heikone Log in to the app with the factory password. The registry name of the rctclient is always displayed there. Unfortunately, I'm not at home, otherwise I would check it myself. |
Refer to pull request #10. |
Can you describe why I should discharge my battery into the grid? Doesn't that only make sense with dynamic prices for the feed-in tariff? |
And how does the inverter behave in emergency power mode? |
Because my wallbox is installed between inverter and grid. The wallbox's clamps measure the power, that is transferred from inverter into the grid. Whit this setup, the wallbox can load on surplus only (Zappi calls this ECO+). But to drain the battery, I need to create a "virtual" surplus as power from battery to grid.
Not testet. I guess you mean island mode. In the mode, the inverter is disconnected from grid a therefore not export to grid shall be possible. Hope this clarifies your questions. |
I'm using strategy
power_mng.soc_strategy = 0
("SOC Target") in combination with a certain value to drain by settingpower_mng.soc_target_set
.What I've learned is, that additionally, I have to specify the power, the battery can supply to the grid.
This setting is available in the app by the following setting:
Question: Can we add this options to the parameters of
rct.py
?Already checked documentation of
rctclient
(direct link) but could not identify the right parameter name.Additionally, I found out that the parameter
power_mng.soc_charge_power
(Charging power to reach SOC target) is not the right parameter.Can anybody give advice and shall we implement this?
Greettings
Heiko
The text was updated successfully, but these errors were encountered: