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
I'm encountering an issue related to setting the export limit on my energy system. My setup has an inverter capacity of 10kW, but the distributor-imposed export limit is only 6kW. Setting the export limit requires adjusting the number.solax_config_max_export entity to 600 to represent 6kW, referencing a separate bug (#922). However, this setting unexpectedly links and alters the ranges of other entities: number.solax_remotecontrol_active_power changes to <-15000; 600> Watts and number.solax_remotecontrol_import_limit shifts to <0; 600> Watts. For comparison, under normal conditions with number.solax_config_max_export set to 15000, the ranges for number.solax_remotecontrol_active_power are <-15000;15000> and for number.solax_remotecontrol_import_limit <0;15000>.
It appears that the number.solax_config_max_export entity acts as an upper limit for the operational ranges of the number.solax_remotecontrol_active_power and number.solax_remotecontrol_import_limit entities within the integration.
Currently, my workaround involves setting number.solax_config_max_export to 15000 under normal conditions and reducing it to 600 only to comply with export limits and avoid fines.
Ideally, these entities should operate independently to allow for precise control. For example in "Enabled Battery Control" mode, I would like to set the "Active Power" and "Import Limit" to 10000 for rapid battery charging, and to -6000 for discharging, aligning with system capabilities without unintended restrictions.
Please feel free to reach out if you have any questions or need further clarification.
Integration Version
2024.08.14
Homeassistant core version
2024.8.3
Inverter brand
SolaX Power
Plugin used
plugin_solax.py
Serial prefix
H34A10
Inverter firmware versions
DSP v1.35 ARM v1.34
Connection Method
Waveshare adapter
Dongle firmware
Unknown
Detailed Error Log
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
Hello,
I'm encountering an issue related to setting the export limit on my energy system. My setup has an inverter capacity of 10kW, but the distributor-imposed export limit is only 6kW. Setting the export limit requires adjusting the number.solax_config_max_export entity to 600 to represent 6kW, referencing a separate bug (#922). However, this setting unexpectedly links and alters the ranges of other entities: number.solax_remotecontrol_active_power changes to <-15000; 600> Watts and number.solax_remotecontrol_import_limit shifts to <0; 600> Watts. For comparison, under normal conditions with number.solax_config_max_export set to 15000, the ranges for number.solax_remotecontrol_active_power are <-15000;15000> and for number.solax_remotecontrol_import_limit <0;15000>.
It appears that the number.solax_config_max_export entity acts as an upper limit for the operational ranges of the number.solax_remotecontrol_active_power and number.solax_remotecontrol_import_limit entities within the integration.
Currently, my workaround involves setting number.solax_config_max_export to 15000 under normal conditions and reducing it to 600 only to comply with export limits and avoid fines.
Ideally, these entities should operate independently to allow for precise control. For example in "Enabled Battery Control" mode, I would like to set the "Active Power" and "Import Limit" to 10000 for rapid battery charging, and to -6000 for discharging, aligning with system capabilities without unintended restrictions.
Please feel free to reach out if you have any questions or need further clarification.
Integration Version
2024.08.14
Homeassistant core version
2024.8.3
Inverter brand
SolaX Power
Plugin used
plugin_solax.py
Serial prefix
H34A10
Inverter firmware versions
DSP v1.35 ARM v1.34
Connection Method
Waveshare adapter
Dongle firmware
Unknown
Detailed Error Log
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: