SunnyDomoticz wrote: ↑Saturday 03 May 2025 11:28
The inverter is connected through WiFi (with an IP address), but doesn't have a separate LAN IP address.
I have the impression you are confusing LAN (Local Area Network) with the way you connect to your LAN: Ethernet cable or Wifi.
The way you connect is not relevant as long as you get an IP address on your LAN so you can reach the MODBUS over TCP/IP.
All you need to do is to install the
sunspec_ardexa and then run the command:
Code: Select all
sudo sunspec_ardexa -v discover 192.168.x.x 1
I didn't have to specify a port number on the command line as it uses the default 502 port. You can check this in the menu of your SolarEdge.
In the SolarEdge you will find the option for modbus of IP and need to enable it there.
I receive this output:
Code: Select all
Found a device at address: 1
Name: common Sunspec Id: 1 Label: Common
Manufacturer (Mn) SolarEdge
Model (Md) SE5000
Version (Vr) 0003.2537
Serial Number (SN) 731E7925
Device Address (DA) 1
Name: inverter Sunspec Id: 101 Label: Inverter (Single Phase)
Amps (A) 14.82 A
Amps PhaseA (AphA) 14.82 A
Phase Voltage AB (PPVphAB) 243.1 V
Watts (W) 3603 W
Hz (Hz) 50.032 Hz
VA (VA) 3609 VA
VAr (VAr) 199.48 var
PF (PF) 99.84 Pct
WattHours (WH) 35072340 Wh
DC Amps (DCA) 9.886 A
DC Voltage (DCV) 370.0 V
DC Watts (DCW) 3658 W
Heat Sink Temperature (TmpSnk) 51.15 C
Operating State (St) MPPT
Vendor Operating State (StVnd) 0
Vendor Event Bitfield 1 (EvtVnd1) 0
Vendor Event Bitfield 4 (EvtVnd4) 0
This request took: 0.60586810112 seconds.
I am running an LUA script that performs the above command and then strips the required data from the result to update a P1 device and text device showing the current Operating state.