Skip to content

Commit ad2cce6

Browse files
authored
Update solax-mode8-modbus-power-control.md
1 parent e4d8c96 commit ad2cce6

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

docs/solax-mode8-modbus-power-control.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ A similar autorepeat mechanism is available for mode 1; see the dedicated wiki p
3535

3636
The Solax Gen4 inverters and higher use a modbus write_multiple_registers command.
3737
On the Gen4, these actions are not stored in EEPROM, so they can be executed frequently.
38-
The integration hides this complexity and implements one button to trigger a single or repeated update(s). The action behind this button is configurable through 6 parameter entities.
38+
The integration hides this complexity and implements one button to trigger a single or repeated update(s). The action behind this button is configurable through following parameter entities:
3939

4040
* **powercontrolmode8_trigger**: trigger button for activating mode 8 loop
4141
* **remotecontrol_power_control_mode**: Select the submode:
@@ -61,6 +61,8 @@ With these parameters a power control dashboard card can be created:
6161
Modifying these parameters has no direct effect, the autorepeat loop is only activated when the trigger button is pressed.
6262
For deactivating these modes, select "Disabled"; clicking the trigger button again is normally not needed for deactivation of the loop.
6363

64+
The current state of the modbus power control mechanism can be examined with entity `solax_modbus_power_control`. If Mode 8 is active, it will show `Individual Setting - Duration Mode`
65+
6466
## Example automation: Negative injection prices
6567
This sample automation will activate the 'Negative Injection Price' mode when the battery is nearly full. We deliberately do not activate it whenever injection prices are negative, to reduce the inaccuracies of the relatively slow autorepeat loop.
6668
These examples assume you have an integration that provides the current injection and consumption price (in my case dynamic_grid_prices).

0 commit comments

Comments
 (0)