Solax X3 Hybrid G4 Pro (Gen6) and remotecontrol

[mpi]

I own a Solax X3 Hybrid G4 Pro inverter, which is classified by homeassistant-solax-modbus as a GEN6 inverter.

I’m trying to integrate it with Predbat according to the following guide.

I noticed that remotecontrol_push_mode_power_8_9 is not enabled for the GEN6 inverters.

Is this an intentional limitation, or simply something that hasn’t been tested yet for this inverter generation?
If it’s the latter, I’d be happy to test it myself, but I’d like to ask first:

• "which entities would need to be enabled?"
• "what behaviour or values should I be looking for once they are enabled?"

If remotecontrol_push_mode_power_8_9 is not an option, what would be the recommended alternative for controlling the inverter?

At the moment, I’m using the REST interface of the Pocket WiFi + LAN dongle, but I’m concerned whether this might have a negative impact on EEPROM registers due to frequent writes.

I also noticed modbus_power_control_direct, but I’m not sure how it is intended to be used in practice.

I would really appreciate any guidance or recommendations from the community.

[wills106]

Thanks for the PR #1779
The only reason the newer Inverters (Gen6) are missing so many things is the lack of complete docs.
The Modbus docs for these later Inverters are missing a lot of information, so I have been adding in functionality slowly.

[RisaLpCz]

Hi,

I have the exact same inverter (Solax X3-Hyb-G4 PRO, classified as GEN6 by this integration) and wanted to share detailed test results confirming that VPP Remote Control (both Mode 1 and Mode 8 style) does not actually get applied by the inverter, even though the writes to the entities succeed on the Home Assistant / Modbus side.

Setup:

• Inverter: Solax X3-Hyb-G4 PRO
• Firmware: ARM 022.06-000-06, DSP 022.07
• Integration version: 2026.06.7

What I tested (Mode 8):

I set up an automation script that writes to:

• number.solax_inverter_remotecontrol_push_mode_power_mode_8_9
• number.solax_inverter_remotecontrol_pv_power_limit_mode_8_9
• number.solax_inverter_remotecontrol_target_soc_mode_8_9
• number.solax_inverter_remotecontrol_autorepeat_duration_mode_1_9
• number.solax_inverter_remotecontrol_timeout_mode_1_9
• select.solax_inverter_remotecontrol_power_control_mode_mode_8_9 -> "Mode 8 - PV and BAT control - Duration"
• select.solax_inverter_remotecontrol_set_type_mode_1_9 -> "Update"
• select.solax_inverter_remotecontrol_target_set_type_mode_8_9_direct -> "Set"

Test conditions were ideal for spotting an effect: PV producing ~9kW, house load ~700W, battery at 100% SOC. I requested Force Discharge at 2000W.

Result: The write to push_mode_power_mode_8_9 was accepted in HA (state correctly showed 2000), but the inverter itself never acted on it:

• sensor...remotecontrol_readback_mode stayed at "Disabled"
• sensor...remotecontrol_mode_8_battery_power_target_readback stayed at 0 W
• sensor...remotecontrol_current_pushmode_power stayed at 0 W
• Battery SOC did not move, no change visible in the SolaX app

I don't have a button.solax_powercontrolmode8_trigger entity available on my system at all (as noted in this discussion, this GEN6 inverter is missing that entity), so I tried both set_type selects ("Update" on mode_1_9, "Set" on mode_8_9_direct) as a possible substitute trigger - neither had any effect.

I also don't have separate "Mode 1" entities (like remotecontrol_active_power or a plain remotecontrol_power_control select with "Enabled Battery Control" etc.) - only the merged Mode 8/9 style entities plus the shared 1-9 parameters (duration, timeout, import limit, set type).

What does work as a workaround:

The classic select.solax_inverter_charger_use_mode -> "Manual Mode" + select.solax_inverter_manual_mode_select -> "Force Charge"/"Force Discharge", combined with number.solax_inverter_battery_charge_max_current / number.solax_inverter_battery_discharge_max_current (in Amps, converted from a target Watt value using nominal battery voltage) works reliably and immediately - confirmed by battery SOC actually changing. I understand this writes to EEPROM rather than RAM, so I'm being mindful of write frequency (this is for a Predbat integration which changes strategy roughly every 30 min at most).

Happy to test anything else if it would help narrow down whether this is simply unimplemented for GEN6, or something the inverter firmware itself rejects. Thanks for all the work on this integration!

[TCWORLD]

You should have a powercontrolmode8_trigger entry. That is what starts the remote control loop. This is definitely enabled for GEN6, so should exist. Sometimes they end up being inexplicably disabled by default, but you should still be able to search for it.