hi, is there any information about inverters by manufacturer sungrow?
3 Likes
I am also interested in having an option to connect my Sungrow inverter. There seem to be Modbus-projects at GitHub, but it likely would be easier to have an connection to the iSolar CloudWebservice.
Modbus
German thread
Yours,
Thomas
In addition:
There is a user, who analyzed the Sungrow API instead of connecting to the Modus:
He builded an implementation to access the Sungrow API
and made a plugin for HomeAssistant:
1 Like
I have also a Sungrow inverter and I use Home Assistant to read data from iSolarCloud. It would be great if this could be done in Homey.
1 Like
I would love to have a isolar/sungrow integration for homey and would be willing to donate/pay for an integration
1 Like
+1 here!
MickMake/GoSungrow: GoLang implementation to access the iSolarCloud API updated by SunGrow inverters. (github.com) gives access to Sungrow data via MQTT. I had MQTT installed on Homey already anyway. Just make sure you change the gateway in the config to the EU gateway (if you have EU Account): ./bin/GoSungrow config write --host=https://gateway.isolarcloud.eu
I’m still trying to figure out how I use the energy data though 
Hi, I’ve just switched to evcc. Very easy to use. Install it on Raspberry and active MQTT. then on Homey I’ve created virtual devices that are updated via MQTT every 30s. To use it with Sungrow make sure you connect the LAN port behind the Wifi dongle to your LAN as well.
I think you can use EVCC only if you also have Wallboxes. Which I have installed. EVCC supports pretty much every solar converter. so maybe an option for others as well.
Enjoy!
App is ready for testing:
1 Like
I just released an app for the hybrid inverters and their associated smartmeter and battery.
Sensor data for important metrics like PV power, battery power, grid import/export is updated every 4-6 seconds. Fast enough to do peak shaving, main fuse protection per phase etc.
It is using Modbus TCP locally for quick data transfer. I don’t see how iSolarCloud API can compete in any regard. The app will autodetect the device if Modbus is active on port 502 and not encrypted (default settings). Note that the app assumes Homey and Sungrow device is on a class C subnet (/24) so if Homey is on 192.168.1.54 for example the Sungrow device must be on 192.168.1.1-192.168.1.254. Manual IP entry will be added eventually. Most users seem to be using /24 network.
The separate battery, pv and smartmeter devices show up properly in Energy, both instant power and accumulated energy.
My plan is to add paid features for more difficult things like peak shaving and spot price optimized charge/discharge eventually so that complicated flows do not need to be created.
The app for Garo GLB EV chargers will be moved into this app as well as other EV charger that will also be planned by AI feature and used to handle peak shaving on facililty as a whole.
App is available here:
