Easiest way for a newbie for SolarEdge integration?

[imautohuttraeger]

I have a brand new SolarEdge installation with the inverter "SE 10K", connected via LAN cable to my LAN. Now I am looking for the easiest and most flawless integration with local data into Domoticz, preferably without having to involve my installing company too much or having total admin rights (I don't want to mess up anything).

In the hardware list, there are "SolarEdge via LAN interface" and "SolarEdge via Web API" available. But in the Wiki it says "Modbus TCP" including installation of a python plugin.

The LAN Interface option, which seems to be the easiest way for me, is not named in the Wiki. Is there a reason why?

Searching the forum has not helped me so far. Any Tipps and hints for me as a newbie?

[psubiaco]

When you say "is not named in the Wiki" you should specify the URL of the wiki pages.
I'm using both plugins, the "SolarEdge via LAN interface" is better because you can get data every 10s (vI got it from https://github.com/addiejanssen/domotic ... tcp-plugin ), while the plugin that uses API can get data only every 5 minutes.
You know that WiKi permits to anyone to improve documentation, so you're encouraged to integrate missing information and fix the bad ones

[imautohuttraeger]

Thanks for your quick reply! I'm not quite sure if I have got you right: You say you are using "SolarEdge via LAN interface" (compare screenshot of the build-in hardware option) but refer to the plugin that creates a new hardware called "SolarEdge ModbusTCP". So I guess you are using the last one - right?

The Wiki page I refer to is https://wiki.domoticz.com/SolarEdge where "SolarEdge via LAN interface" is not mentioned (but it would be the easiest option for me if it works)

Believe me, a guy like me who more/less is only using "copy/paste" solutions without real knowledge is not a good option to improve Wiki pages

[psubiaco]

I suggest to try the "Solaredge via LAN interface" already integrated in Domoticz (I didn't know about it), verify how it works and let us know replying in this forum.

You can also install the Python Plugin manager that permits to add new unofficial plugins for new hardware.
Have a nice day.

[imautohuttraeger]

I did try "Solaredge via LAN interface" by typing in the IP (tried port 502 and also 1502) but nothing happens. Neither automation detection of devices nor an option to create devices.

Maybe an outdated hardware that no longer works?

I guess that is the reason why "SolarEdge ModbusTCP" exists.

[psubiaco]

My Inverter was installed in 2019, HD-wave SE6000H-RW000BNN4, has already the 11502 TCP port active.
I can stop the plugin, and telnet IPnumber 11502 and it works.
In the wiki page you mentioned it's written how to connect to your inverter by WiFi and enable the ModbusTCP port. I'm not sure that procedure is still working.

[imautohuttraeger]

OK. I will ask the installer to ensure that modbus TCP is really activated.

[RonkA]

Steps i used to enable modbus on my SE9K inverter:

• Enable wifi direct on the inverter by switching the red toggle switch on the inverter to "P" position for at least 1 second but less than 5 seconds..

• Connect to the inverter access point like you would for a normal wifi network. The wifi password is published at the right side of the inverter.

• Open up a browser and go to http://172.16.0.1 > Site Communication. From this webpage you can enable modbus TCP without setApp or installer account

[imautohuttraeger]

@RonkA : With your instructions I could verify that modbus TCP was already activated - thank you!

Installed the SolarEdge Modbus TCP Hardware but at first the Devices where not created. I then asked ChatGPT to check the Error Log and it gave me right hint. Now it works and I am happy!

This is the solution:

The plugin uses the outdated import structure of pymodbus
This structure has been removed/changed in newer pymodbus versions starting with version 3.0. As a result, the plugin no longer works correctly with the latest pymodbus version.

Solution: Install an old pymodbus version (e.g. 2.5.3)

Code: Select all

sudo pip3 install pymodbus==2.5.3

Then restart Domoticz.

[imautohuttraeger]

One thing I still have to find out is how to get the SolarEdge Batterie into Domoticz because no such device has been created. Anyone?

[imautohuttraeger]

Sigh! The Power figures are much too low. What could be the cause?

[RonkA]

I don't have the answer, i can only guess..
But could it be that in Domoticz the device Total Energy is the value of what in the second screenshot is exported to the grid? the usage/deliver-values between modbus and app can totally be different because of new 'instant' values from modbus and old 'average' values given from the app.

[imautohuttraeger]

Update: Found the Solution in this post:

viewtopic.php?p=326370#p326370

Now the figures are correct.

Quoting the instructions that worked for me:

by jannl » Monday 05 May 2025 14:20

This is how I got the modbus connection working, in buster.

Code: Select all

pip3 install modbus==0.8.0
pip3 uninstall pymodbus
pip3 install pymodbus==3.6.9

The code used runs in my customstartup.sh I use in docker.

The problem for me is more computing the correct value for raw sun production, escpecially when using a battery and ev-charger. There is actually no value in the modbus registers for the raw sun production. But I am getting there and may be I will take the occasional miscalculculation for granted.