Take complete control of your Sigenergy energy ecosystem with this comprehensive Homey integration. Monitor and automate your solar production, battery storage, grid consumption, and EV charging - all from one powerful app.
Need to know before adding a GX Device to your Homey
You must have Modbus enabled on your Sigenergy devices (SigenStor/Sigen EV AC Charger).
You need to know the IP addresses of your Sigenergy devices. Port is 502 by default.
Your Homey needs to be able to connect to your Sigenergy devices via your local network.
If you have a SigenStor battery, the connection details are the same for the Inverter, Battery, Energy meter and EV DC charger (if you have one). Typically, the Modbus native address is 1.
Devices
Inverter
Should work on both hybrid and PV inverters.
Classified as a solarpanel by Homey Energy
Battery
Tested on SigenStor
Classified as a home battery by Homey Energy
Energy meter (grid)
Classified as an energy meter by Homey Energy
EV DC Charger
Compatible with DC chargers, a part of your SigenStor unit. This device uses the exact connection details as the Inverter and Battery.
Classified as an ev charger by Homey Energy
EV AC Charger
It has its own connection details, and from what I have read online, it seems difficult to enable Modbus on it - requiring a support ticket to Sigenergy.
Classified as an ev charger by Homey Energy
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?
