-
-
Notifications
You must be signed in to change notification settings - Fork 508
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
WebUI and MQTT AC Total Limit #849
Comments
If you have two HM-800 with two 300W panels on each inverter. |
In the first monet I would say that it is enough to sum up the configured power limits. I think if you would still take into account the DC power, you would still have to consider a lot about the self-consumption of the inverters and the conversion factor. This would miss the idea. I am only concerned with the sum of the configured AC limits. |
@tbnobody I second this Feature request, as the current Power Limits should be summed up and shown next to the current total power. In case no power limit is set this will default to 100% or the total capacity of the inverters. It is a good question if in your given example one would like to also calculate the installed maximum ?
Could be given as 195.1W / (Capacity Panels 1200 Wp / Channels 1600 Wp) So in your example when you have 50% Power Limit for Inv1 and 75% for Inv2:
Could be given as 195.1W / (Capacity Panels 1200 Wp / Channels 1000 Wp) That is the Channel Wp is limited by the Power Limit in % / absolut W. |
Is your feature request related to a problem? Please describe.
No response
Describe the solution you'd like
It would be nice if the web interface could optionally display the Total Limit in addition to the Total Power. Example: 199.5W / 900W. 900W would be an example for e.g. three 300W inverters.
I would also appreciate if this value could be retrieved in the MQTT of the AC Total to display it in the Grafana monitoring without performing further mathematical operations here.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: