[APP][Pro] SolarEdge + Growatt TCP modbus

Although you did not mention it, can you clarify on whether or not you also have the Modbus app running on Homey (or any other Modbus app outside of Homey trying to connect to the inverter)?

AFAIK, the standalone Modbus app is not required to use the SolarEdge + Growatt TCP modbus app, but when both apps are running at the same time, they can interfere with each other. It is possible to run the apps side by side, but does require your to manually manage the connection from the Modbus app

Only Solaredge app is running, no other modbus stuff. Also tried device ID 2 but that isn’t it. I can check the installer settings on the inverter and it show ID 1.

not really sure what’s going on or what next steps I can take. Any suggestions ?

I don’t have access to the Modbus settings for my setup. I had to ask my installer to enable it. I don’t know about the protocol, but I did have to ask him to set the Modbus TCP parameter to “Enabled (unrestricted)”. I sent him the following instructions:

https://uni002eu5.fusionsolar.huawei.com/hedex/hedex.do?lib=DP_en&pidid=pid_neteco_faq&topicid=TOPIC_0000001543186965&locale=en-us&hdxsrc=original&keyword=MODBUS&keyword=modbus

Title: Issue adding KOSTAL Plenticore Plus via “SolarEdge + Growatt TCP modbus” (timeout)

Hi,

I’m trying to add my KOSTAL Plenticore Plus inverter to my Homey Pro 2023 using the “SolarEdge + Growatt TCP modbus” app.

My setup:

  • Inverter: KOSTAL Plenticore Plus
  • Homey: Homey Pro 2023
  • Network: Same LAN, inverter reachable via ping
  • Modbus TCP on the inverter:
    • Enabled
    • Port: 1502
    • Unit ID: 71

What happens:

  • I install the “SolarEdge + Growatt TCP modbus” app.
  • I go to Devices → + → select the app → choose the KOSTAL / inverter driver.
  • During the pairing process, Homey shows the error:
    “Die Installation ist vielleicht fehlgeschlagen, weil sie zu lange gedauert hat.”
    (roughly: “Installation may have failed because it took too long”)
  • The device sometimes appears in the device list, but it shows 0 W and does not seem to update.

Additional info:

  • The inverter responds to ping on its IP address.
  • No other system should be using Modbus TCP on this inverter at the same time.
  • Homey app version: [your mobile app version, if you want]
  • SolarEdge + Growatt TCP modbus app version: v3.0.169

I’ve created a diagnostics report from the app:
Diagnostics ID: 341153f1-b2a0-4404-befc-e74a33ec4af5

Could you please check what’s going wrong with the Modbus connection / pairing for the KOSTAL Plenticore Plus?

Thanks a lot!

Welcome,

Note:
Unsolicited sending of diagnostic reports often is not appreciated

Note2:
kudos for the very detailed information provided!

Ontopic

Try changing modbus port 1502 to 502, which is the standard port number

Please don’t reply here, move your post to the Solaredge+Growatt topic, thank you.

I try do bring my Emma and the Rest of my Photovoltaik in Emma with the solaeEdge + growatt ap. But it did Not work. I get Kontakt with Emma, modbus is on, but all I get is this:

Can anybody help?

Danke !

René

Welcome, René,

The Solaredge+Growatt app has it’s own special topic, like many apps have.
When you post your Q in there, you’ll reach fellow device owners and the developer.
And often the first post has lots of howto’s, FAQ and troubleshooting guides!

Hi Peter,

Thank you, will try it!

René

I’m so sorry that you have removed flowcards BatteryFirst Timeslot2 and TimeSlot 3 in the Growatt SPH version 3.0.223. I used them both in my flows :weary_face:

But it have also corrupted the existing device. By adding a new device helped, but still only with Battery First TimeSlot1


My device doesn’t get updated anymore? Some values do get updated but the current power is not updated for 18 days now. The connection itself seems fine. Anyone a solution? Telnet on this port to this device works fine.

To anyone using Sungrow solar panels + battery:

Weird question, but is anyone else experiencing a difference in battery charging? For the last two years, “Forced mode” “Stop 10” would fully stop the battery from charging. Nothing in, nothing out. Since last week, the battery has suddenly started to trickle-charge at exactly 100W when I give these commands. Not a huge problem, but definitely unexpected
 O.o

I don’t have 1 but the trick with emma is

default there is somewhere 0.0.0.0

switch to Modbus in the installer menu and then enter your Homey’s IP address there.

see [APP][Pro] SolarEdge + Growatt TCP modbus - #1696 by JayR

you got some firmware update?

I think you solved it by now but it is always some dhcp ip change, firewall rule, vlan , using wifi

using a 2nd app which holds the port occupied.

I heard reinstalled helped , somehow the auto update caused some corruption

Yes I solved it. Thank you. I am running homey and ha. tried Solaredge jn ha as well. This caused the problems.

Hello everybody!

@Janalyzer Any luck in solving the issue you faced?

I have a similar Huawei SUN2000-4KTL-L1 inverter that I’d like to integrate in Homey Pro.

The inverter has no dongle and it’s connected to the router via WiFi.

Is a wired ethernet connection needed to make this app work?

Has anyone succeded in making a SUN2000-L1 inverter work with this app?

Thanks a lot!

Unfortunately no. No solution so far. I even made things worse by messing with my inverter settings and now I can’t connect to it at all. I’m thinking about forking the other app for Huawei web data readings, because that’s what Homewizard uses and it works fine. It’s just a matter of fixing the app to allow the new login method.

Hi @Edwin_Biemond ,

I have your app running for some time now and everything worked well until 2-3 weeks ago.

I have a sungrow inverter, but the data doesn’t come through anymore.

I tried several things: reinstall the device, deleted the app and installed the official version, I tried also the test version of the app,
 Nothing does the trick.

Any suggestions maybe?

Thanks!

All the best,

Geert

Although your question is addressed to Edwin,

Did you check the actual IP address of the device as it should be a LAN fixed IP address. It is forgotten so many times. Just to make sure, check →