SolarEdge Local Access (Without Admin)

Hardware
,
1

Greetings!
During my configuring of a smart system with HA i wanted to add my SolarEdge inverter but i ran into the issue of not having admin access. I noticed that there’s a Local & Online option yet i have no access to the Site API etc.
Is there a way around this as i’m fairly certain our provider won’t be down to give us the IP / API or Admin access.

SolarEdge Inverter:
Inverter SolarEdge 100kW, on-grid, 3-phase, 1 mppt, no display, wifi

2

I have the same situation and managed to access admin interface through local wifi connection.

See, e.g., Solaredge - Activate Modbus TCP - Sourceful Energy Knowledge Base

3

Am i able to access the IP or API thru the admin interface via the Address?
I’d need
LOCAL:

image
image899×513 31.7 KB

And if i were to go online:
image
image657×437 14.2 KB

4

I use a custom component that allows to reach the solaredge locally through modbus (once you enable it on solaredge)

image
image1336×520 29.8 KB

5

This wold have to be an ethernet connected device right, so it’s not wireless direct connection / data from the inverter itself?

6

Indeed, my inverter is ethernet wired. Not tested wifi myself, but according to the link I shared, it should work as well (as long as you can reach the inverter from HA, ofc)

7

You can use wired or wireless connections with modbus on a SolarEdge inverter, but there are reports of wifi being less stable than wired ethernet, which causes connection errors. Wired is always best but you can still try with wifi and see if it will work well enough or not.

I personally do not use wifi and never test with wifi when developing since my inverters have always had a wired ethernet connection.

8

image
image1039×357 25.8 KB

Would you possibly know why it’s coming to this issue?
I’m trying to do it wireless now and i have read the IP Config from 172.16.0.1 - at the same time i didn’t put a static IP it’s dynamic would that impact this?
Should i set a static one?

9

Make sure Modbus TCP is enabled:

If it was already on then try turning the setting off, save, and then back on again.

10

What do you mean by that?
172.16.x.x is typically the docker range, under which HA is running.
Your solaredge will have an adress in the range provided by your main router (typically 192.168.x.x)

Try to check on your router what is the actual IP. If it’s the one you specified, and it’s responding to ping, then indeed check if modbus is actually enabled on the solaredge (it is not by default), see SolarEdge Local Access (Without Admin) - #2 by koying

If you have linux knowledge, use netcat to confirm you can connect

❯ nc -zv <solaredge ip> 1502
Connection to solaredge.lan 1502 port [tcp/*] succeeded!
11

We have enabled TCP Modbus and configured a static IP but during input into HA it doesn’t connect to it keeps throwing out errors.
Even when trying with the API provided by the installers it doesn’t seem to want to work it throws out “Could not connect to the SolarEdge API” error.

image
image971×401 25.2 KB