Sig Energy System Integration

So,

i had tried some of the provided settings and created a custom one:

My SigenApp gives me:
Daily total: 18,69 kWh
Charging: 8,82 kWh
Discharging: 5,2 kWh

and this is the information in HA using the modbus integration:

sensor.sigen_daily_pv_energy_production

Sigen Daily PV Energy production 30.821 state_class: total_increasing status: collecting last_period: 40.927 last_valid_state: 1567.162 last_reset: 2025-04-06T22:00:00.003913+00:00 next_reset: 2025-04-08T00:00:00+02:00 unit_of_measurement: kWh device_class: energy friendly_name: Sigen Daily PV Energy production
sensor.sigen_daily_pv_energy_production_hart

Sigen Daily PV Energy production HART 61.73 state_class: total_increasing status: collecting last_period: 177.68 last_valid_state: None last_reset: 2025-04-06T22:00:00.002737+00:00 next_reset: 2025-04-08T00:00:00+02:00 unit_of_measurement: W friendly_name: Sigen Daily PV Energy production HART
sensor.sigen_daily_pv_plant_energy_production

Sigen Daily PV Plant Energy production 27.273 state_class: total_increasing status: collecting last_period: 36.569 last_valid_state: 1037.311 last_reset: 2025-04-06T22:00:00.004526+00:00 next_reset: 2025-04-08T00:00:00+02:00 unit_of_measurement: kWh device_class: energy friendly_name: Sigen Daily PV Plant Energy production

i have tried it for the last 2 days. i am stock.
I don’t know what is missing, i just getting this:

Maybe somebody would be able to assist me?
THank you.

We’d need more information about what you’ve done.

  • How are you running HA? HAOS, Docker, etc?
  • Did you install the modbus_sigenergy.yaml from here?
  • Did you follow the instructions on folders?
  • Did you restart? Did you create the dashboard described here?
  • What exactly is the problem? I can see you have one metric on a dashboard you created. Is it accurate? Does the history look about right?

sadly not yet in contact with the installer seeing if the mod bus is okay

Hi there,

There is a known issue with double counting and this might be your issue. The solution is to not poll the modbus so often (which is why the energy value is being double counted). The author has updated the code to reflect this but I accept that it might not be readily accessible. Here’s the discussion thread on it. There’s also a summary here.

Responding to you looks like it may have also helped me. I’ve been having random shutdown’s without any notification. It appears I’m not the only one and it may be associated with firmware updates.

Hope this resolves your problem.

my “Set Sigen Independent phase power control” was set to disable and the result was:
I had 3000W to the grid and I wanted to use a single phase device with 2000W.
With setting Set Sigen Independent phase power control to disable the 3000W was splittet into 3x 1000W per phase (A, B & C).
So I used 2000W on a single phase (B) has was in result: 2000W to the grid via Phase A and C and 1000W from the grid on Phase B.
Result: 1000W from grid to be paid

with Set Sigen Independent phase power control “enable” the Sigen stor was providing the 2000W i was going to use on a single phase (Phase B) and the remaining 1000W was splittet to the rest of the phases (A and C) and pushed into the grid. So the function seems to be important to avoid usage from the grid.
Result: the 2000W device was using the full capacity available and only the reminaing power was pushed to the grid.

That is very important if you have a “Phase-accurate counter” in German known as a “phasengenauer Zähler”.

@HomerHH Thank you very much, so it enables the battery plant output to balance the phases’ power. This is indeed crucial if you want to reduce grid consumption and Maximize self-consumption, which is my primary goal and the stor’s settings. So I’ll keep it on “Enabled”

At the moment i’m facing some miner problems with the “Sigen Daily Grid Energy import”.
Every night it is set to 0kwh but hours later is is bumping up to some “random” values. Today it is jumped at 5:40 in the night to approx 5,5 kwh. But there was enough energy in the Battery.
Someone else are facing the same issue?

Hi Tim,

A: HAOS
B: yes
C: yes
D: yes

But I have just started all over with a new HAOS setup.

Might be best to rewrite your question with all the information in one place. Describing the problem and your setup well in one post makes it easier to help you. Include error messages and logs as appropriate.

Hello! Just got a Pointguard system provisioned today, and had the installer toggle Modbus on. I figured out its IP from my router’s UI, and got everything set up in HA from the TypQxQ GH repo, which did produce a ton of new Sensor and Helpers, but it doesn’t seem like they’re getting data. I scanned the IP with nmap and I don’t see port 502 (or anything else) open? I do have their myPointguard app set up on my phone and it is getting data (not sure if the app talks directly to the hub over the LAN or they both go back to Sig’s servers). Is it possible they’ve changed to using another port, not 502?

Just setup a new inverter. I have noticed that the ModBus TCP server only runs on the WiFi IP address, and not the LAN IP. I have both connected, and both reply to pings.

nmap <wifi-ip> -p 502
502/tcp open mbap

nmap <wired-ip> -p 502
502/tcp closed mbap

Currently trying to get SigEnergy to confirm if its their problem and whether they can fix it!

Is everyone still using this integration or the python one in the comments? i’m assuming the python one is the same but just available using HACS? It doesn’t have any screenshots so confused if i need both or just the python version?

@technophobe could you explain this a bit more precisely please? What is “the python one in the comments”? If there’s another integration for Sig Energy could you please link to it?

I’ve started using this one, it’s working really well:

1 Like

How is that one better than the current one based on modbus? The modbus one is a bit unusual, but it’s working quite well for me.

They are all based on the modbus data.

The PV generation energy the Sigenergy2MQTT calculates and reports matches what the Sig portal reports. The other one does not.

The difference is significant, so much so that the data from the other integration really isn’t an accurate representation of my system’s production. Errors in the order of 5+% are not acceptable. That flows through to inaccurate export and consumption data in HA.

The Sigenergy2MQTT add-on is giving me data which exactly matches the Sig portal, or may be different by 0.01 kWh (less than 0.1%).

The acid test however is how this data compares with my utility smart meter. The Sig portal and the Sigenergy2MQTT are pretty good with their alignment, within 0.5% of the utility meter. The other integration is just way off.

1 Like

That’s interesting, thanks @wattmatters . It’s true that the other integration doesn’t match perfectly, for me the difference is around 5% as well. That’s not ideal for me, but it’s also not really a problem.

It seems like a very new project. Once it’s a bit more mature and more tested I’ll give it a go. I’ll have to learn about MQTT, I’ve not had a need to use it before. The idea is simple enough.

I suspect what’s happening is the energy integration is being performed on different input power sensors.

One is using the combined DC output of the PV arrays while the other the AC output from the inverter after conversion.

The DC values will naturally be higher than after conversion to AC. It’s only a hypothesis, I can’t say for certain this is what’s going on.

However, some information to explain why I think this is the case…

When I look through the sensors the Sigenergy2MQTT add-on provides there are two different outputs for Daily PV Energy:

sensor.sigen_0_daily_pv_energy
which yesterday reported 22.27 kWh:

and

sensor.sigen_0_inverter_1_daily_pv_energy
which reported 24.84 kWh

Meanwhile the mySigen app reports daily production as 22.27 kWh, which matches the sensor.sigen_0_daily_pv_energy sensor, while the other sensor is 11.5% higher.

That’s not just some sampling rate error.

Then when I look at the sensors for the individual PV arrays, the outputs yesterday were:

PV1: 10.10 kWh
PV2:  6.03 kWh
PV3:  8.71 kWh

which totals 24.84 kWh, the same as the sensor.sigen_0_inverter_1_daily_pv_energy sensor above.

So I think perhaps another look at the inputs being used to calculate daily and other energy accumulation values is worthwhile.
.

We consume and are billed on the AC energy output of the inverter, not the DC side, so it’s the AC energy data that matters most, to me at least.

The DC data is of course interesting and helpful for diagnostics, comparing strings etc but as inputs into Home Assistant Energy Dashboard and other tracking, then it’s the AC data I want to use.

How do I know this data is the right one to use?

Well I compared what the outputs for energy we export to the grid with that reported by my Utility’s billing meter (a Class 1 smart meter sampling the data in the multiples of milliseconds). IOW any error in PV output will propagate to export energy values. Overstate PV output and export will also be overstated.

The mySigen app data and the Sigenergy2MQTT outputs (and hence the HA Energy Dashboard using these outputs) matches my Utility’s billing meter inside of 0.5% which is not the case with the other integration.
.

I had “got used to” MQTT from previous integrations for my off-grid solar/battery system at a previous home and also my car integration uses it as well, so using it for this was not a stretch.

2 Likes

I’m getting my Sigenstore batteries installed soon. With regard to the modbus settings? Does anything need to be entered into the “modbus server address” or is it just the “Modbus TCP Server Enabled” that need to be set?