Domoticz

Posted: **Monday 24 February 2020 21:16**

No luck

@freijn You did say

I do not have computed but from device

What Sensor Type is your device SolarEdge Power Kwh

I do have Sensor Type Electric (Instant+Counter) and with from device the update command needs to be an other than below?
urlmessage = 'http://'+domoip+':'+domoport+'/json.htm?type=command&param=udevice&idx='+str(domoidx)+'&svalue='+str(domovalue)

Posted: **Monday 24 February 2020 21:57**

: Capture.JPG (16.21 KiB) Viewed 3199 times

: Capture.JPG (16.21 KiB) Viewed 3199 times

let me check the url

Posted: **Tuesday 25 February 2020 7:43**

Running update every 10 second now and so far there seems to be a difference.

Unlike me you do have SolarEdge_Modbus Hardware i.e. I've missed to add Hardware
Can you share yours including settings?

: 2020-02-25 080009.jpg (7.16 KiB) Viewed 3188 times

Posted: **Tuesday 25 February 2020 22:05**

rogerthn wrote: ↑Tuesday 25 February 2020 7:43 Running update every 10 second now and so far there seems to be a difference.

Unlike me you do have SolarEdge_Modbus Hardware i.e. I've missed to add Hardware
Can you share yours including settings?
2020-02-25 080009.jpg

Roger,

I have no clue what you are asking now

Can you please help me to understand which include settings you are looking for?

b.t.w. Are you running the Perl code or the Python code?

Posted: **Tuesday 25 February 2020 22:13**

freijn wrote: ↑Tuesday 25 February 2020 22:05 Roger,

I have no clue what you are asking now Can you please help me to understand which include settings you are looking for?

b.t.w. Are you running the Perl code or the Python code?

Never mind

I am running the Perl code and the only minor issue is the diff on daily production compared with SolarEdge monitoring.

Posted: **Thursday 16 April 2020 15:40**

Hej there,

I'm a newbie to domoticz and scripting - but i finally got the perl script working on my rasperry connected to a SolardEdge Se7k by modbus TCP. Actually, there is only one problem: How can I get the real power value (describing in/out of power to the grid) or alternatively incoming and outgoing grid power into the script and finally into domoticz?

Regards

Hagen

Posted: **Tuesday 28 April 2020 16:51**

Micha123 wrote: ↑Tuesday 15 October 2019 16:19 I found sunspec_ardexa

It ia a python script and is working much faster then the pearl script

https://pypi.org/project/sunspec-ardexa/

And you dont need to install much librarys for it

$ sunspec_ardexa discover 192.168.102.41 1

Output is

Name: common Sunspec Id: 1 Label: Common
Manufacturer (Mn) SolarEdge
Model (Md) SE4000
Version (Vr) 0003.2221
Serial Number (SN) 73133F27
Device Address (DA) 1

Name: inverter Sunspec Id: 101 Label: Inverter (Single Phase)
Amps (A) 1.74 A
Amps PhaseA (AphA) 1.74 A
Phase Voltage AB (PPVphAB) 236.0 V
Watts (W) 383.1 W
Hz (Hz) 50.02 Hz
VA (VA) 412.5 VA
VAr (VAr) 152.88 var
PF (PF) 92.87 Pct
WattHours (WH) 9371992 Wh
DC Amps (DCA) 1.0329 A
DC Voltage (DCV) 376.5 V
DC Watts (DCW) 388.9 W
Heat Sink Temperature (TmpSnk) 41.79 C
Operating State (St) MPPT
Vendor Operating State (StVnd) 0
Vendor Event Bitfield 1 (EvtVnd1) 1
Vendor Event Bitfield 4 (EvtVnd4) 0

I can install it on my Pi where also Domoticz is running on that's no problem but it is not clear to me how to get it in Domoticz.

Posted: **Tuesday 28 April 2020 21:40**

I can install it on my Pi where also Domoticz is running on that's no problem but it is not clear to me how to get it in Domoticz.

There's a description on this post

viewtopic.php?f=65&t=31455

Posted: **Friday 02 May 2025 18:05**

Hello all,

Has anyone figured how to connect to an inverter with display? The inverters with display don't have the web-configuration tool.

I've read through the solaredge wiki and the github discussions.

I found this manual https://knowledge-center.solaredge.com/ ... _above.pdf. Nowhere does it show where to configure the port. I know the IP address and the Solar Edge consumer monitoring portal is working. Also I have the API plugin working, but would like the LAN statistics.

I have the SE3000 inverter with wifi module. RS485-1 is configured to SE (Dev) S (Prot), RS485-2 is unconfigured.

Sorry if the question has been asked before!

Posted: **Friday 02 May 2025 20:14**

SunnyDomoticz wrote: ↑Friday 02 May 2025 18:05 Hello all,

Has anyone figured how to connect to an inverter with display? The inverters with display don't have the web-configuration tool.

I've read through the solaredge wiki and the github discussions.

I have an se5000h with display and have modbus via network enabled via the display. An script using sunspec_ardexa retrieves the info every 15 seconds running via crontab and updating some dummy devices to track the state and the production. This is working nicely for 4 years now.

Posted: **Friday 02 May 2025 21:09**

jvdz wrote: ↑Friday 02 May 2025 20:14
SunnyDomoticz wrote: ↑Friday 02 May 2025 18:05 Hello all,

Has anyone figured how to connect to an inverter with display? The inverters with display don't have the web-configuration tool.

I've read through the solaredge wiki and the github discussions.
I have an se5000h with display and have modbus via network enabled via the display. An script using sunspec_ardexa retrieves the info every 15 seconds running via crontab and updating some dummy devices to track the state and the production. This is working nicely for 4 years now.

Good to hear! Could you share your RS485 settings? Mine look like this at the moment.

Posted: **Friday 02 May 2025 21:41**

Looks like there is no image attached, but i am using the modbus protocol over ip so there is no serial connection.

Posted: **Friday 02 May 2025 21:54**

jvdz wrote: ↑Friday 02 May 2025 21:41 Looks like there is no image attached, but i am using the modbus protocol over ip so there is no serial connection.

https://i.imgur.com/K9SNrBe.jpeg

Do you need to enable the modbus protocol, or is it always on? In the Wiki (https://wiki.domoticz.com/SolarEdge) it states for non display inverters you have to enable modbus TCP, but I can't find the corresponding setting on my display inverter.

Posted: **Friday 02 May 2025 22:46**

Yes you need to enable it in the menu and think to remember you need to use it or else it will disable again.

I can look at the details tomorrow in case you need more specifics.

Posted: **Saturday 03 May 2025 11:28**

jvdz wrote: ↑Friday 02 May 2025 22:46 Yes you need to enable it in the menu and think to remember you need to use it or else it will disable again.

I can look at the details tomorrow in case you need more specifics.

Thanks! I found the Modbus TCP setting under LAN settings. I can't seem to enable it. The inverter is connected through WiFi (with an IP address), but doesn't have a separate LAN IP address. I am interested what your settings are.

edit: I ran an ethernet cable to the inverter. Now it gets an IP address on both WiFi and LAN. I still can't enable Modbus TCP it seems.
edit2: I had to apply the port first. Now Modbus is enabled!

Posted: **Saturday 03 May 2025 17:13**

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.

Posted: **Saturday 03 May 2025 17:47**

SunnyDomoticz wrote: ↑Saturday 03 May 2025 11:28 ... The inverter is connected through WiFi (with an IP address) ...

Might not be relevant for you but I've a SE7K and after an upgrade modbus over WiFi was disabled due to "security concerns"

I now have a cable connected

Posted: **Saturday 03 May 2025 17:51**

Good to know as I might have to upgrade the firmware this year as well on my current se5000k. I have it connected to Ethernet since a year as the wifi was giving me regular issues, losing the network connection and having to restart the network on the se5000k.
Didn't have any issues since using the Ethernet port.

Posted: **Saturday 03 May 2025 18:28**

No issues with the cable connection but WiFi is WiFi

Posted: **Monday 05 May 2025 12:07**

jvdz wrote: ↑Saturday 03 May 2025 17:13
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.

Thanks for your help so far. It seems to be two steps forward and one back. I can't seem to be able to install sunspec_ardexa or the SolarEdge_ModbusTCP plugin due to changes in the latest OS (Bookworm Debian). I get the same error on both tries. I did a forum and Google search, but can't really get a good answer. More people seem the have the problem (on the Github discussions also: https://github.com/addiejanssen/domotic ... ussions/70)

× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
python3-xyz, where xyz is the package you are trying to
install.

Domoticz

SolarEdge via LAN interface

Re: SolarEdge via LAN interface

Re: SolarEdge via LAN interface

Re: SolarEdge via LAN interface

Re: SolarEdge via LAN interface

Re: SolarEdge via LAN interface

Re: SolarEdge via LAN interface

Re: SolarEdge via LAN interface

Re: SolarEdge via LAN interface

Re: SolarEdge via LAN interface

Re: SolarEdge via LAN interface

Re: SolarEdge via LAN interface

Re: SolarEdge via LAN interface

Re: SolarEdge via LAN interface

Re: SolarEdge via LAN interface

Re: SolarEdge via LAN interface

Re: SolarEdge via LAN interface

Re: SolarEdge via LAN interface

Re: SolarEdge via LAN interface

Re: SolarEdge via LAN interface

Re: SolarEdge via LAN interface