Sigenergy Sigenstor and EVCC - example

[Chr1892]

I successfully configured a evcc.yaml to work with the SigenStor Hybrid PV/Battery System

I connected the SigenStor and my EVCC Server (running on a Macbook) to the same Wifi Network. I use Modbus TCP to read the Battery SOC and power, and the PV1 and 2 Voltage and Current. Each Voltage and Current are multiplied, then PV1 power and PV2 power are added to get the total PV power. (The modbus documentation shows PV3 and 4, too, but PV 3 is not used in my case and I think PV4 can be ignored). I use an efficiency factor of .97 to calculate the AC power from the DC power.

Your system installer has to activate the Modbus TCP protocoll in the MySigen App.
Click the Device button to switch to Device panel. Click on the SigenStor Settings button, and go into the SigenStor Settings panel. Turn on the Modbus TCP Server Enable button, and click on the Save button on the right. (See [[kp_installationsinstruktioner_sigenergy_1_.pdf]])

Here's the configuration for the PV production meter:

- type: custom
  name: Sigenstor-PV
  power:
    source: calc
    add:
    - source: calc
      mul:
      - source: modbus # PV1 voltage
        id: 1
        uri: 192.168.0.182:502
        timeout: 1s
        register:
          address: 31027
          type: holding
          decode: int16
        scale: 0.097 # Value in Volts
      - source: modbus # PV1 current
        id: 1
        uri: 192.168.0.182:502
        timeout: 1s
        register:
          address: 31028
          type: holding
          decode: int16
        scale: 0.0097 # Value in Ampere
    - source: calc
      mul:
      - source: modbus # PV2voltage
        id: 1
        uri: 192.168.0.182:502
        timeout: 1s
        register:
          address: 31029
          type: holding
          decode: int16
        scale: 0.097
      - source: modbus # PV2current
        id: 1
        uri: 192.168.0.182:502
        timeout: 1s
        register:
          address: 31030
          type: holding
          decode: int16
        scale: 0.0097

Here's the configuration for the Battery:

- type: custom
  name: Sigenstor
  power:
    source: modbus
    id: 247
    uri: 192.168.0.182:502
    timeout: 1s
    register:
      address: 30037
      type: holding
      decode: int32
    scale: -1 # ESS power in W
  soc:
    source: modbus
    id: 247
    uri: 192.168.0.182:502
    timeout: 1s
    register:
      address: 30014
      type: holding
      decode: int16
    scale: 0.1 # SOC in %
  capacity: 10.4 # kWh

Add both the configurations to your evcc.yaml file in the "meters" section, then add the PV-meter and battery-meter to your "site":

site:
  title: My Home
  meters:
    grid: # name of your grid sensor
    pv: Sigenstor-PV
    battery: Sigenstor

For further reading, here's the Modbus Documentation that I used, and a user Manual for the modbus activation (remote EMS scheduling is not required):
Sigenergy Modbus Protocol - 20240409.pdf
kp_installationsinstruktioner_sigenergy_1_.pdf

[andig]

Do you want to wrap this in a meter template? Also seems grid is missing- all hybrid inverters should have those measurements somewhere.

[Chr1892]

Yes, I could add the grid measurements. I didn't need it for my own purposes, because I have a Keba E10 grid meter. How do I create a meter template for the Sigenstor system?

[MepLab]

Thank you for this example! 😊
It would be great to have grid measurements included.
Does anyone know how to set up a Sigen EV AC Charger with evcc?

[wunderer1990]

Has anyone a configuration for adding the grid measurement to the yaml file?

[lhw]

Here is my meter block with grid, pv and battery. I only have one PV port connected so i didnt bother doing any VA calculations:

meters:
  - name: grid1
    type: custom
    power:
      source: modbus
      id: 247
      uri: 192.168.1.X:502
      register:
        address: 30005 # Grid Power +/-
        type: holding
        decode: int32
  - name: pv1
    type: custom
    power:
      source: modbus
      id: 247
      uri: 192.168.1.X:502
      register:
        address: 30035 # PV Plant Power
        type: holding
        decode: int32
  - name: battery1
    type: custom
    power:
      source: modbus
      id: 247
      uri: 192.168.1.X:502
      register:
        address: 30037 # Battery Plant Power +/-
        type: holding
        decode: int32
      scale: -1
    soc:
      source: modbus
      id: 247
      uri: 192.168.1.X:502
      register:
        address: 30014
        type: holding
        decode: uint16
      scale: 0.1

site:
  title: Home
  meters:
    grid: grid1
    pv: pv1
    battery: battery1

[andig]

Happy to tale a PR for a template

[lhw]

I will create one. We have all the values I think. Just need to adapt one of the templates. Should be easy enough.

[wunderer1990]

Thank you very much for sharing ;)

[lhw]

Now with a proper template #21302

[wunderer1990]

Does anyone think it´s possible to manage the battery system like it is explained in on this site? https://docs.evcc.io/en/docs/features/battery for example charging the battery from the grid if the energy is cheap

[jellevanerven]

It is possible with sigenergy Home Assistant integration so modbus can also be used to control the battery. I hope anyone can make this work with evcc as well😃

[ZombieApps]

Does anyone think it´s possible to manage the battery system like it is explained in on this site? https://docs.evcc.io/en/docs/features/battery for example charging the battery from the grid if the energy is cheap

I've added active battery control in #24426 and tested the "grid charging" and "Prevent discharge in fast mode and planned charging" evcc features with my Sigenergy battery.

The PR has been merged into master, which means it will be in the next release of evcc.

I'd appreciate it if you could test it and let me know your experiences.

[windshear84]

I’m planning a PV installation with a Sigenergy SigenStor EC30 inverter + 6 kWh battery.
The installer proposes an additional Solar Manager (CHF 1,290) to enable PV surplus charging of my Easee wallboxes and to control a Stiebel Eltron heat pump (SG-Ready).

Before I buy it, I’d like to clarify if the Solar Manager is actually required – or if the SigenStor system itself (via Modbus TCP or SunSpec) can already provide the necessary live data (PV generation, battery, grid import/export) to EVCC, so that EVCC alone can handle surplus charging.

In short:
-Does SigenStor expose all needed Modbus registers for EVCC surplus-based charging?
-Can EVCC directly read grid power (import/export) and PV production from the inverter or its Home Meter, without the Solar Manager?

• Or is the Solar Manager mandatory for those values to be made available via Modbus or MQTT?

Thanks in advance for clarifying whether the Solar Manager is technically required, or if the same functionality can be achieved via Modbus TCP integration with EVCC directly.
Christian

[ZombieApps]

By "solar manager" do you mean the products available from solarmanager.ch ?

I can't find much info about it outside of German-language websites, but I can tell you that Modbus gives you access to everything you need.

See here for an example of all the information that's accessible via Modbus

https://github.com/seud0nym/sigenergy2mqtt/blob/main/sigenergy2mqtt/sensors/README.md

The evcc integration uses the grid active power, lifetime imported energy, Phase A/B/C currents, PV and battery power, battery discharge energy and SoC to allow the EV to charge from solar energy only.

And my small modification gives evcc write access to the discharge cut-off SoC so that you can also charge directly from the grid without depleting the battery.

[eikewink]

i have a sigenstore pv installed with a 16 kw battery. i'm ready to test whatsever we have to test

is there maybe a way to read out all the infos from the netgateway ? so i can see how much i really use from the net and or from the battery?

my shelly pro 3em does not really work and told me all the time wrong data.

[eikewink]

I can’t tell you how Modbus is enabled on the server because I’m not the one who installed the app, but I do have a user account. But please keep in mind that I’m just a regular user and don’t have any programming experience. I can certainly help you, but you’ll need to tell me exactly what to do to make this work.

eike

[eikewink]

What I’ve noticed with the integration in EVCC is that when you adjust the levels for how much the battery should discharge, or up to which level it should be charged — for example, if you set both to 10% — then, at strange and irregular intervals, the entire level suddenly changes to 20%. This means that what should have been charging from the grid up to 10% becomes 20%. I have the feeling that it somehow merges or confuses those two data points.

I also believe that recharging based on the CO₂ limit doesn’t really work properly. When the CO₂ limit is set to “none,” it still continues charging, or it doesn’t behave as expected. In fact, when it’s set to “none,” it doesn’t charge at all. Only when I set the limit above 210 grams, or choose another value, does it start charging again — otherwise, it doesn’t charge.

[windshear84]

Thanks again, Eikewink — that’s really valuable feedback!

What you’re describing (charge/discharge level changing from 10% to 20% automatically) sounds like EVCC might be mixing up two different registers or receiving overlapping updates from SigenStor (e.g. one for “minimum SOC” and one for “grid-charge SOC”).
That could explain the jump from 10 → 20 %.

The CO₂-limit behaviour you’re seeing also sounds like EVCC’s logic doesn’t fully match the SigenStor’s internal control logic — probably because EVCC expects standard SunSpec registers, while SigenStor seems to use its own scheme.

So this strongly suggests that:
Modbus TCP communication is working to some extent (otherwise those controls wouldn’t react).
But the mapping of the data points is inconsistent, and EVCC developers probably need to adjust the register map for SigenStor.

If you’re okay with it, maybe we can share your observation with the EVCC maintainers — it would help them fix the mapping and confirm whether this behaviour requires the Solar Manager as a middle layer.

Best regards. Chris

[eikewink]

for sure we can........if i can help make this product better and maybe also with a smart meter gateway which i had allready ordered to use modul 1 and 3 in germany i'm glad to help.
just guide me what i have to do and i will do it :)

[eikewink]

so just that you know what i have installes here:
sigen 16 KW Battery with 20 kw hybrid "wechselrichter" and a 21 kw pv installation include a ahoy dtu balkonkraft with 1500w hoymiles. 2 webasto unite wallboxes and one nrg kick gen2 loader.
i have planned to install in the next 4 week (everything is allready here) 3 heating elements from TA (Aton) .....they are also running modbus (other topic if you want to search for)

[jellevanerven]

Hi, Installed the new version today. It seems to work. It holds the battery while charging the car. But still have to test it the coming days. 3 things i want to mention: * If the car is in the ready or waiting state when full, it is still holding the battery. So i had to switch it off when ready manually. * The switch says prevent discharge in fast mode and scheduled mode. But in my case i doent want to discharge to the car under any circumstance. When actively charging the car, doent discharge homebattery. Not sure if i can achieve this in the actual setup? * It seems to take over control of the ai from Sygenergie. It doesnt plan to charge on cheap moments. But have to check this the next few days. Thanks so far. Regards Jelle Verzonden vanaf Outlook voor Android<https://aka.ms/AAb9ysg>

…

________________________________ Van: Zombie ***@***.***> Verstuurd: donderdag, oktober 16, 2025 3:19:21 a.m. Aan: evcc-io/evcc ***@***.***> CC: jellevanerven ***@***.***>; Comment ***@***.***> Onderwerp: Re: [evcc-io/evcc] Sigenergy Sigenstor and EVCC - example (Discussion #16246) Does anyone think it´s possible to manage the battery system like it is explained in on this site? https://docs.evcc.io/en/docs/features/battery for example charging the battery from the grid if the energy is cheap I've added active battery control in #24426<#24426> and tested the "grid charging" and "Prevent discharge in fast mode and planned charging" evcc features with my Sigenergy battery. The PR has been merged into master, which means it will be in the next release of evcc. I'd appreciate it if you could test it and let me know your experiences. — Reply to this email directly, view it on GitHub<#16246 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMCZZ6PJY62X4K2HEIWL6FT3X3XBPAVCNFSM6AAAAABOSJQL7GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINRZGI4DIOA>. You are receiving this because you commented.

[ZombieApps]

If the car is in the ready or waiting state when full, it is still holding the battery. So i had to switch it off when ready manually.

Is this using evcc or the car itself to set the charge limit?
If the latter, does evcc know that your car is "full" ?

I have my car's limit set to 100% and evcc set to limit the car to 90% and I've had no issues with evcc allowing the sigenergy battery to charge as soon as the car is done.

The switch says prevent discharge in fast mode and scheduled mode. But in my case i doent want to discharge to the car under any circumstance.

When you're charging from solar evcc automatically adjusts the charge rate to ensure the battery doesn't get discharged - except for up to 100W or so because the battery reacts faster than the evse.

The switch for fast mode / scheduled mode is so that the battery doesn't get discharged even when you're not charging from solar.

evcc achieves this by looking at what the battery's SoC is right now and setting the minimum SoC to that value.
But I noticed that it seems to round down to the nearest % so I see up to 1% discharge before the "hold" kicks in - but in my case that's a max of 240Wh or a few cents worth of energy.

[jellevanerven]

@ZombieApps Now i read all my old feedback, i think this all might have to do with changing the min and Max soc.
Problem is i think, i use peakshaving, not specific for peakshaving but the same setting in sigenergy also helps limeting the peak grid usage, it is the only place where you can set the max grid power.
When changing the min soc, from 0% tot 80 or whateverb to hold the battery when charging the car, it also changes the min peakshaving soc because that has to higher then the min soc. I think that is why it keeps holding my battery when the car is full. It does change the soc to the lower min soc it was before, but it then leaves the peak shaving soc on the higher percentage, preventing it from discharging.

Would be great if it also changes the peakshaving soc to the old value, or evcc takes over the load management for the sigenergy as well, so i can switch off peakshaving in the sig app.

[jellevanerven]

@ZombieApps see the screenshot, min peakshaving soc was 3% it also raises that automatically when evcc changes the min soc when charging the car.

[jellevanerven]

It keeps setting the min soc at 100%, while the car is already full a long time, so evcc doesnt give the charge status correctly.
Would it be possible to read the charge status from the charger or to stop holding the battery if the charger is draining les then 1kw of power, die might be an alternative way to check if the car battery is full. Now it only stops holding when i disconnect the car.

[jellevanerven]

Grid charging also worked last night. Pre set it to 14,5 cent or lower. One other thing, maybe i should make a new feature request for this: you can enable grid charging when the price is under a pre defined level. But what would be nicer, if you could define a price difference between highest and lowest. So for example, if the price difference between high and low is at least for example 5 cent, it charges only, when during the day the difference is at least 5 cent, when at lowest point and discharges when the difference is 5 cent or higher. When grid charging during daytime it should keep enough space for expected solar charge. Keep up the good work. I will register for sponsership token now this is working 😃 Regards Jelle Verzonden vanaf Outlook voor Android<https://aka.ms/AAb9ysg>

…

________________________________ Van: Jelle van Erven ***@***.***> Verstuurd: zondag, oktober 26, 2025 11:02:32 p.m. Aan: evcc-io/evcc ***@***.***>; evcc-io/evcc ***@***.***> CC: Comment ***@***.***> Onderwerp: Re: [evcc-io/evcc] Sigenergy Sigenstor and EVCC - example (Discussion #16246) Hi, Installed the new version today. It seems to work. It holds the battery while charging the car. But still have to test it the coming days. 3 things i want to mention: * If the car is in the ready or waiting state when full, it is still holding the battery. So i had to switch it off when ready manually. * The switch says prevent discharge in fast mode and scheduled mode. But in my case i doent want to discharge to the car under any circumstance. When actively charging the car, doent discharge homebattery. Not sure if i can achieve this in the actual setup? * It seems to take over control of the ai from Sygenergie. It doesnt plan to charge on cheap moments. But have to check this the next few days. Thanks so far. Regards Jelle Verzonden vanaf Outlook voor Android<https://aka.ms/AAb9ysg>

________________________________ Van: Zombie ***@***.***> Verstuurd: donderdag, oktober 16, 2025 3:19:21 a.m. Aan: evcc-io/evcc ***@***.***> CC: jellevanerven ***@***.***>; Comment ***@***.***> Onderwerp: Re: [evcc-io/evcc] Sigenergy Sigenstor and EVCC - example (Discussion #16246) Does anyone think it´s possible to manage the battery system like it is explained in on this site? https://docs.evcc.io/en/docs/features/battery for example charging the battery from the grid if the energy is cheap I've added active battery control in #24426<#24426> and tested the "grid charging" and "Prevent discharge in fast mode and planned charging" evcc features with my Sigenergy battery. The PR has been merged into master, which means it will be in the next release of evcc. I'd appreciate it if you could test it and let me know your experiences. — Reply to this email directly, view it on GitHub<#16246 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMCZZ6PJY62X4K2HEIWL6FT3X3XBPAVCNFSM6AAAAABOSJQL7GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINRZGI4DIOA>. You are receiving this because you commented.

[jellevanerven]

@eikewink I missed your feedback from a couple of days ago. But it seems the same indeed. Needs a little tweaking. @windshear84 if i can help testing etc let me know.

[windshear84]

Thanks @jellevanerven and @eikewink — great to see you both observe the same SOC behaviour.
That confirms it’s not a local config but likely a mapping or sync issue between the two SOC registers in the SigenStor.

I don’t have a Sigenergy system running yet — I’m currently planning my installation with a SigenStor EC30 — but I’m following this thread closely.
Once the register mapping is stable, I’ll also be able to test the integration on a fresh setup.

Best,
Chris

[jellevanerven]

@ZombieApps don't know if you already red this, so just i add you to this conversation to keep you informed about @eikewink and my experiences with the sigenergy integration.

[ZombieApps]

Hello @jellevanerven and @eikewink

I had the same issue with evcc automatically setting my battery minimum SOC to 20%, and I found this discussion #11509 where evcc now has a default of minsoc: 20

To avoid this you need to set minsoc in your config file

- name: battery                                                
  usage: battery                                               
  type: template
  template: sigenergy
  host: 10.60.0.13
  port: 502
  capacity: 24
  minsoc: 1
  maxsoc: 100

I don't use sigenergy's AI, but I'm not surprised that changing things via modbus messes with the AI config.

I would think that you have to either let the AI do everything for you, or let a third party app like evcc and/or home assistant take control.

what would be nicer, if you could define a price difference between highest and lowest.

I think this would be best as a feature request for evcc, because it's not Sigenergy specific.

[jellevanerven]

@ZombieApps Thanks for this info, will add this to the config.
Adding support for load management when grid charging the sigenergy and the possibility to switch off grid charging the sigenergy (to let this handle by sigenergy AI), should this also be a feature request? @andig

[eikewink]

It would also be nice if we had a way to access or measure the power from the SIG Energy Gateway, so that we have a proper overview and can take a closer look at the power flow.

[eikewink]

as you can see here ....the battery is charging from the grid but is it not counting in evcc.

[eikewink]

and after opeing up the app and check the setting in soc it's shown correct in the app but after this its stops charging and sucks from the battery:

[eikewink]

and in the app is 10% as it was before.
in evcc stands the same 25 % in both register. after saving it again it going to charge...in my eys the app overrules evcc

[RoanRossey]

Hi so to control the sigstor battery does it also need to be in ems mode instead of the AI mode?