You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/solax-mode1-modbus-power-control.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -88,6 +88,8 @@ With these parameters a power control dashboard card can be created:
88
88
89
89
Before issuing a `remotecontrol_trigger` button activation, an automation should make sure that the other remotecontrol_* parameters have the correct values. This also applies to manual interactions with the `remotecontrol_trigger` button.
90
90
91
+
When using the autorepeat function, checks are in place to ensure that you cannot request the battery discharge below the minimum SoC limit set by the `selfuse_discharge_min_soc` entity. Once this SoC level is reached, any modes which would normally discharge the battery will be prevented from further discharging the battery.
92
+
91
93
### Related read-only sensors
92
94
The state of the modbus power control can be monitored by examining following sensors:
Copy file name to clipboardExpand all lines: docs/solax-mode8-modbus-power-control.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,14 +44,15 @@ The integration hides this complexity and implements one button to trigger a sin
44
44
***Mode 8 - PV and BAT control - Duration**: this is the manual mode that uses fixed `remeotecontrol_pv_power_limit` and fixed `remotecontrol_push_mode_8_9` settings. The same behavior can probably be achieved with the _direct version of the entities (without autorepeat loop)
45
45
***Negative Injection Price**: in this submode, PV will charge the battery and feed the house load, but once the battery is fully charged, PV will be reduced to house load so that no export takes place. The autorepeat mechanism is essential to adapt to the varying PV power or house load. If there is still some remaining export (probably because there is a limit on the possible charging power), reduce the `remotecontrol_pv_power_limit` parameter. In this submode, `remotecontrol_pv_power_limit` will be interpreted as maximum battery charge power, and `remotecontrol_target_soc_8_9` sets the upper SoC limit on charging the battery to allow leaving some spare capacity if desired.
46
46
***Negative Injection and Consumption Price**: In this submode, PV will be limited to zero and battery will be charged from the grid (house load also from grid)
47
-
***Export-First Battery Limit**: This submode prioritises feeding excess energy to the grid up to the defined export limit. Surplus power beyond that is used to charge the battery, with charging power adjustable via the Export-First Battery Charge Limit (mode 8/9) parameter. It enables Home Assistant to run logic similar to the SolaX Datahub — using solar forecasts to prioritise grid feed-in when high solar production is expected, while allowing slower charging to protect battery health.
47
+
***Export-First Battery Limit**: This submode prioritises feeding excess energy to the grid up to the defined export limit. Surplus power beyond that is used to charge the battery, with charging power adjustable via the Export-First Battery Charge Limit (mode 8/9) parameter. It enables Home Assistant to run logic similar to the SolaX Datahub — using solar forecasts to prioritise grid feed-in when high solar production is expected, while allowing slower charging to protect battery health. The `remotecontrol_target_soc_8_9` parameter sets the upper SoC limit when the battery is being charging with excess solar.
48
48
***Enabled Grid Control**: In this submode, the `push_mode_power_8_9` parameter represents the target at the grid interface: positive means export, negative means import
49
-
***Enabled Feedin Priority**: In this mode, solar power will serve the house load and the excess power will go to the grid. Battery will not be charged and will only discharge if there is insufficient solar power
49
+
***Enabled Feedin Priority**: In this mode, solar power will serve the house load and the excess power will go to the grid. Battery will not be charged and will only discharge if there is insufficient solar power and the battery is above the minimum SoC limits.
50
50
***Enabled No Discharge**: With this submode, the goal is to stop the battery from being discharged. The `push_mode_power_8_9` is ignored. House load will be provided by PV, and any surplus will be used to charge the battery. When PV is insufficient, the deficit is provided from the Grid to ensure the battery holds its SoC.
51
51
***remotecontrol_pv_power_limit**: maximum PV power; is automatically recomputed in the Negative Price submodes. An initial max value is needed however
52
52
***remotecontrol_push_mode_power_8_9**: positive numbers are discharge, negative numbers charge; is automatically computed in the Negative Price submodes
53
53
***remotecontrol_import_limit**: can be used to limit the maximum import from grid. This limitation is active in all submodes, so make sure to set this parameter to a proper value. Please note that the import limitation will only work as long as the battery is not empty. In regions where the maximum import has a financial impact (e.g. part of Belgium), the autorepeat approach may have an advantage over the _direct alternative.
54
-
***remotecontrol_target_soc_8_9**: Used in some submodes to limit the maximum SoC of the battery while charging where noted above
54
+
***remotecontrol_target_soc_8_9**: Used in some submodes to limit the maximum SoC of the battery while charging where noted above.
55
+
***remotecontrol_minimum_soc_8_9**: Used to set the limit for minimum SoC of the battery while discharging in remote control mode. Mode 8 will not allow the battery to discharge below this SoC level when running. Please note the minimum SoC will be the higher value of this entity and the `selfuse_discharge_min_soc` entity. In other words this option allows increasing the minimum SoC, not forcing it below the existing work mode limits.
55
56
***remotecontrol_duration**: we recommend keeping the default value of 20s
56
57
***remotecontrol_autorepeat_duration**: typically a couple of hours - e.g. duration of the negative price
57
58
***remotecontrol_timeout**: can be left 0 or set to a few seconds more than the polling interval; unclear how to use this
0 commit comments