After running some tests it seems that the inverter resets its output limit to 110% every time mpvmode changes to 2 (Normal). This PR is meant to reflect that behavior in the following ways:
When mpvmode is not 2, disable the Limit Power number entity
When mpvmode changes to 2, set the Limit Power number entity to 110% (internally only, no data is sent to the inverter)
While mpvmode remains 2, track the power limit internally
One potential issue with this method is that the Limit Power entity may de-synchronize from the actual limit. This will happen in case of a re-load of the integration after setting a lower limit while mpvmode remains 2 in the inverter.
A possible solution to this would be to actively set the limit to 110% when mpvmode changes to 2. If this is deemed desirable then I will update the PR. Otherwise users can do this with a simple automation.
After running some tests it seems that the inverter resets its output limit to
110%
every timempvmode
changes to2
(Normal
). This PR is meant to reflect that behavior in the following ways:mpvmode
is not2
, disable theLimit Power
number entitympvmode
changes to2
, set theLimit Power
number entity to110%
(internally only, no data is sent to the inverter)mpvmode
remains2
, track the power limit internallyOne potential issue with this method is that the
Limit Power
entity may de-synchronize from the actual limit. This will happen in case of a re-load of the integration after setting a lower limit whilempvmode
remains2
in the inverter. A possible solution to this would be to actively set the limit to110%
whenmpvmode
changes to2
. If this is deemed desirable then I will update the PR. Otherwise users can do this with a simple automation.fixes #86