Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix inverter and measured power for older SolaX MIC inverters #1154

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

Kars-de-Jong
Copy link

@Kars-de-Jong Kars-de-Jong commented Dec 2, 2024

Correct inverter and measurement entities for older SolaX MIC inverters

  • The Measured Power entity for Gen1 and Gen2 MIC inverters is actually the Inverter Power.
  • The Inverter Power entity for Gen1 and Gen2 MIC inverters is actually the Measured Power
  • The Measured Power Lx entity for Gen1 X3-MIC inverters is actually the Lx Inverter Power.

Enable house load entity for MIC inverters

House load can be calculated for MIC inverters that have a meter connected.

Enable Inverter Power Lx entities for X3 Gen2


Tested with a Gen1 X3-MIC with an emulated SDM230 meter connected.

Please note that this change breaks the history of the existing entities. Not sure if an upgrade script is possible / needed.

 - The Measured Power entity for Gen1 and Gen2 MIC inverters is actually the Inverter Power.
 - The Inverter Power entity for Gen1 and Gen2 MIC inverters is actually the Measured Power.
 - The Measured Power Lx entity for Gen1 X3-MIC inverters is actually the Lx Inverter Power.
House load can be calculated for MIC inverters that have a meter connected.
@Kars-de-Jong Kars-de-Jong changed the title Fix SolaX MIC inverter and measured power Fix inverter and measured power for older SolaX MIC inverters Dec 2, 2024
@Kars-de-Jong
Copy link
Author

@wills106 Could you please have a look at this?

@mrichtarsky
Copy link

Thanks @Kars-de-Jong for the fix, I will test this locally

@mrichtarsky
Copy link

@Kars-de-Jong Looks good to me. Except for Measured Power L1, which still does not make sense to me (i.e. it stays at 0 even when charging with 11kW). But that might be a problem of the inverter.

@Kars-de-Jong
Copy link
Author

Kars-de-Jong commented Dec 6, 2024

@mrichtarsky
It looks like the entities you want ("Inverter Power Lx") are not mapped on Gen2, but when I look at the documentation you provided they should be available at the same address as Gen1.
I will update this PR to include Gen2.

@Kars-de-Jong
Copy link
Author

@mrichtarsky Done. Could you please test?

The fact that "Measured Power L1" is 0 in your case might indicate a problem with your kWh meter. Maybe the L1 CT is not connected properly?

@wills106
Copy link
Owner

wills106 commented Dec 7, 2024

Thanks for working on this. Once mrichtarsky has confirmed the latest changes are ok I'll merge it.

@mrichtarsky
Copy link

Thanks @Kars-de-Jong!
Currently it looks like this

Screenshot_20241211_084343_Home Assistant

Inverter Power L1-3 are zero although current and voltage are not, perhaps the value must be calculated and is not available directly?

@Kars-de-Jong
Copy link
Author

Kars-de-Jong commented Dec 11, 2024

@mrichtarsky Thanks for testing again.

I see now in your original issue report that you already tried reading 0x410, 0x411 and 0x412 and that they always return 0 in your case.
That's quite odd, those addresses match with the documentation of X3-MIC Pro-G2 V2.7.
In that case I'm at a loss. You can't derive active power from the other available values, only apparent power (which is not the same).

All I can suggest is for you to try and read all input registers using pymodbus or for instance mbpoll and see if we can find values on addresses that match with the individual phase powers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants