ok than I will wait
thx a lot Guijter and merry christmas
Hi @RM_de_Gruijter ,
I just installed your app and logged on via iSolarCloud. That worked.
But when I wanted to select the device, I could chose from 77 inverters!
I found the one that had my name, but I saw also 76 other inverters from other people.
Is that the way it supposed to be??
All the best,
Geert
No. It is a ‘feature’ of the Sungrow API. I will try to find a way to make the pairing view only show relevant devices.
I am in Australia and I really would like the Sungrow app to work here … it would make automations such as charging my EV and running the 3 phase ducted air conditioner much more intelligent. I’m only allowed one image as I’m a “new user” (I’m not but what the heck) so please email me for more images if needed.
Me too, could you add support for New Zealand? App looks great - just can’t get it to work.
Same here, need to repair after s while. Enoying. Homey Pro 2026
Same here. Looked for me to unsafe:(. I don‘t want others to see my data - and the personal name of my inverter and system. Till now I was using the Solaredge Modbus Plugin working on the LAN-port, but it stopped suddenly working for me.
unfortunately it’s disconnecting every day for me
Is there a possibility to fix that instead of me clicking “repair” all the time?
Icloud is always online - seems to forget the login data
Hi everyone,
I installed the app, clicked on add inverter and authorized my isolar account successfully. Next page it is trying to find devices and I always get a timeout.
Do I have to configure anything within sungrow as well? The isolar app on my phone works and shows my inverter, Battery and charger, but the homey sungrow does not.
I tried this App, but I am concerned about the privacy of the app. When I tried to add my Inverter I saw many inverters that wasn’t mine. Was able to add them and see their production data.
The Sungrow API indeed has a security issue. It cannot be solved in the Homey app. I am working with Sungrow to get the issue fixed.
TEST CREDENTIALS NEEDED!
I am working on an app update for which I need test systems in regions EU, AU and International. When I have a login to your site details I will probably be able to add support for more regions, devices and device data.
Please send me a direct message if you are willing to share your (temporary) login details.
A completely new version 2.0.0 of the app is available: Sungrow | Homey
- Added support for multiple accounts and regions (EU, AU, International)
- Added battery temperature monitoring
- Fixed showing non-owned systems
- Added improved rate limit handling
- Added translations
- Fixed minor memory leaks
This is a major rewrite that solves a number of serious issues, and also expands the functionality and international/AU region support.
New version 2.0.1 was just released: Sungrow | Homey
- Added data fallback logic when iHomeManager is installed.
- Increase unavailable timeout to 24 hrs.
- Auto token sync between sessions for same account.
This should fix the device unavailable messages during nighttime. Also it adds better support to installations where a iHomemanager is installed.
Hi. Thanks for all the hard work. I can confirm that, having installed the latest app 2.0.1 I still experience nightly, almost precisely timed, disconnection of my inverter. It requires repair and reauthorisation of the plant every morning and then it works flawlessly until the next night. No network issues on my end. I can access plant via sungrow app without issues. Homey integration is where it fails.
interestingly utilising home assistant and connecting the inverter via their app works flawlessly. Not sure why but sungrow just does not like this particular app(?).
Thanks for the work again and please do let m know if you have any other tips!
Thx for the feedback @Elvinas_Hunger !
I created and released a new version 2.0.2
It should fix the non-standard way SunGrow is using oAuth.
If the app doesnt upgrade itself please install it again from the appstore (that will force an update). Let me know tomorrow if it still works ![]()

