Monitor and automate your Sigenergy system from Homey: solar production, battery storage, grid import/export and EV charging. Everything runs locally over Modbus TCP, no cloud needed.
Before you start
Modbus TCP must be enabled on your Sigenergy system. Your installer can turn it on (for the EV AC charger it may need a support ticket to Sigenergy).
You need the IP address of your SigenStor / inverter. Port is 502 by default. Tip: give it a fixed IP in your router.
Homey must be able to reach it on your local network.
Which devices should I add?
All devices on the SigenStor use the same IP and port. Only the Modbus address differs:
Device
What it is
Modbus address
Homey Energy
Plant
The whole system, as shown on the house picture in the mySigen app: solar, battery, grid, home consumption and EV power. Battery control flow cards live here.
247 (fixed)
–
Inverter
Solar production, daily/total yield, PV voltages. Hybrid and PV inverters.
1 (typically)
Solar panel
Battery
State of charge, charge/discharge power, average and max cell temperature (min cell temperature on systems that report it), charged/discharged energy.
1 (typically)
Home battery
Energy meter
Grid power per phase, imported/exported energy. Works with a separate meter or the meter built into the Sigen Gateway.
247 (fixed)
Energy meter
EV DC Charger
The DC charger built into the SigenStor.
1 (typically)
EV charger
EV AC Charger
The separate Sigen AC charger, with its own IP address.
1 (typically)
EV charger
If you have several SigenStor stacks, the Plant device shows the combined values for all of them.
Battery control (Plant device)
Stop the battery discharging, e.g. while the car charges (v0.7.0+):
Hold the battery at its current level / Release the battery hold. Keeps AI mode running. Release restores your previous setting. While held, the house is also supplied from solar and the grid instead of the battery.
Example: when the car starts charging → Hold the battery; when it stops → Release the battery hold.
Other flow action cards:
Set max battery charge / discharge power, and remove the limit again. Note: AI mode ignores these limits; use the hold cards above instead.
Set max grid import / export power.
Remote EMS: turn it on/off and pick a mode: Standby, Max self consumption, Charge (grid or PV first) or Discharge. Turning remote EMS off puts the system in Max self consumption, not AI mode, so you need to switch back to AI mode in mySigen afterwards.
Force charge from grid at a chosen kW.
Troubleshooting
Device unavailable after a router restart? The inverter probably got a new IP. Update the IP address in the device’s settings, no need to re-add the device.
Something looks wrong? Turn on Detailed logging in the device settings, let it run while the problem happens, then send a diagnostic report from the app and post the code here (or in a GitHub issue). Turn logging off again afterwards.
Daily/total consumption is on the Plant device (v0.6.4+). Daily/total solar yield is on the Inverter device.
Do you know what the biggest differences from the SolarEdge + Growatt TCP modbus are? Are the different devices (inverter, battery, charger and smart meter) better registered in Homey using this app? Will I see all different parts of the stack as separate devices in Homey?
I developed this app for a few reasons. I recently installed a SigenStor stack with a DC charger; usually, I only develop apps I can use myself. The current app that supports many different brands isn’t compatible with Homey Energy. You need separate devices for each device type. The plan is to expand it over time with lots of control options.
The Modbus registries provided by Sigenergy are not well structured compared to, for instance, Victron. I hope they will spend some time restructuring and completing them.
I am eagerly waiting to get my Sigenstor solution to be installed so not there yet. I only have one small question if I may…. Does it matter if I set up my Sigenstor on a wired network or wireless(2.4)?
Both options work, but I prefer this type of equipment to be connected via wire. Regardless of the connection method, if possible, assign a static IP to the device so it doesn’t change if your router reboots. The static IP is mainly important for local integrations, such as with Homey.
Thanks! Good to know. I will set a static IP and also block the Sigenstor from connecting to the 5GHz band on the router. Might give you some more feedback when I am live…
Thank you for creating this amazing app! I’ve been using the “SolarEdge + Growatt TCP modbus” for some time now, which works well, but having an app dedicated to Sigenergy with Homey Energy support and a dashboard widget is a game changer for me!
I would like to make a small request though:
I’m currently changing all my flows to use your app, but I noticed that there’s one value that’s currently not present in your app, and that’s the “Consumed power”-value.
I use this in a calculation to only charge my EV with excessive solar using a third-party wallbox (Zaptec).
Right, I see that in the SolarEdge + Growatt TCP modbus app, they calculate that manually; solar -battery + grid.
For the widget, I calculate the home load as: solar + grid - battery - ev charger.
With the split of devices, it is not clear which device should get this home load/consumption capability. In the SMA app, I ended up with a summary device that displayed data from multiple other devices, including scenarios where, for instance, you had two solar inverters. I’ll have to think a little, but it may make sense here as well.
Regarding the Gateway, there is only one mention of it in the PDF spec, which is General Alarm 4. No other mention of the Gateway appears in the spec. I spoke with another user who has a Gateway, and according to his knowledge, it doesn’t have its own native Modbus address.
There’s little we can do except inform Sigenergy that they need to improve their Modbus API.
Hi, just to let u know that I have ordered the battery and inverter from sigenergy together with new pv panels. So, thx for this integration, will let u know how it goes. Will take some time.
One question, for the modbus integration, is there anything extra needed like an ew11? Or is it out of the box
Yes, each device separately. I have not spent any time trying to make the addition smarter, given that it is quick and a one-time effort.
I don’t have a Gateway myself and am not sure which information you associate with it. There are 0 (zero) Modbus registers for the Gateway in Sigenergy’s specification.
Thank you for adding consumption. I’ve now fully migrated all my flows and dashboards to use your app.
I have a new request, but this time for the widget:
Would it be possible to add an option to display the EV charger or not, and have the garage closed if no charger exists? I use a third party wallbox (Zaptec) so it will always be 0 usage and a bit confusing for family members when our car is actually charging.
Even better would be if the widget could be customizable so that I could add my Zaptec wallbox as the displayed charger in the widget. That would really make the widget complete and show all important loads in my home.
@Richard_B
Thanks for the app - really appreciate a specific one for SigEnergy. I have been able to add the inverter but I cannot find the IP addresses for the batteries to be able to add those. I checked my network and only the inverter has an IP address?
I’m trying to add my Sigenergy battery but it gives the following error message. My installer did eneble the Modbus TCP, so what does below means? What should I do?
