2026.05.4 / 2026.05.5 / 2026.05.6 Release - Issue Reporting Thread

[TCWORLD]

Summary

I'm opening this issue to track the work we've been doing to hande differences in Modbus register maps based on inverter firmware version.

Recent versions of SolaX GEN6 firmware upgrades and (potentially GEN4/GEN5 as they are updated) led to incompatabilities in the register maps causing problems.

Thanks to @rosenrot00's for PR #2054 which allows the SolaX plugin to distiguish between the firmware versions based on an entity called "Modbus Protocol Version". Specifically:

• Inverters with a value <100 (seems to be usually 5, 6 or 7) are the old protocol version where we don't have full documentation.
• Inverters with a value >=100 are using the new protocol version where we have a largely documented register map.

Related PRs

The following PRs are related to this register map handling:

• Introduce Solax registers depending on the inverters modbus version #2054 (base PR, released as 2026.05.4b1)
• Fix (Total) Battery Capacity for SolaX GEN5 (protocol<100) #2069
• Add export limit exceptions for SolaX G4-Pro #2070
• Fix scaling of SolaX X3 G4-Pro Inverter Temperature (protocol≥100) #2072
• Fix SolaX Battery Input/Output Energy (protocol<100) and Total Energy Sensors (protocol≥100) #2073
• Fix handling for SolaX GEN6 MPPT3 and MPPT4 registers (protocol<100) #2076
• Reinstate PV Total Register for newer GEN6 (protocol≥100) #2077
• Re-enable EPS Mute Sensor for GEN4/5 #2089
• Remove Duplicate Registers (proto≥100) #2093

Testing

Users with a GEN6 inverter in particular (X3-HYB-G4 PRO, X1-VAST, X3-VAST, etc,) if you are willing to give feedback on the changes that would be great.

If you wish to help us test this release, you'll need to have 2026.05.5 installed.

If you find an issue, please post here, and include:

1. The value of "Modbus Protocol Version" entity (under Diagnostics)
2. Software version number from "SolaX Software Version" entity (under Diagnostics)
3. Your inverter serial number prefix (first 6 digits, e.g. 10K0F1).
4. Details of any registers which have inaccurate or unexpected values (e.g. unknown, incorrect scale factor, always 0, etc.) compared to what they used to be, please let us know so that we can make sure they are fixed.

[rosenrot00]

@TCWORLD great, this will help. I created a Github action that would generate pre-releases from an open PR. This would help to test much faster with the users without them editing files manually.

[wills106]

Just released 2026.05.4b2 with the latest changes.

[rosenrot00]

With the great work of @TCWORLD I think we are ready to leave beta?

Several issues were closed as solved. No flaws on my system. Due to the massive changes I made to introduce the modbus version I thought it to cause more issues.

@TCWORLD what do you think - can @wills106 pull it off?

[TCWORLD]

Definitely proved less breaking that I worried it would be.

There are a couple more sensors that stopped being exposed on mine (version min added where not needed). I'll try and get the change committed this evening.

[TCWORLD]

Turned out to only be one sensor in the end (added in #2089) - the other one actually never worked I'd just not noticed.
Tested now for a full day and seems that everything is working as it used to on my end.

[rosenrot00]

@TCWORLD great news. Great work, we got this not trivial change smoothly implemented.