Domoticz

After adding hardware (Setup -> Hardware -> SolarEdge via LAN interface), it does not want to appear under Setup -> Devices.

What am I doing wrong

Have you read this?

http://www.domoticz.com/wiki/SolarEdge

I think I've done everything according to the roadmap.

RPI 3B RASPBIAN JESSIE
Domoticz V3.587

See screenshots

Why does there not listening any thing on port 2222

pi@raspberrypi:~ $ netstat -an |grep 22
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 192.168.106.8:22 192.168.106.14:53647 ESTABLISHED
tcp6 0 0 :::22 :::* LISTEN
unix 3 [ ] STREAM CONNECTED 10622 /var/run/dhcpcd.unpriv.sock
pi@raspberrypi:~ $ netstat -an |grep -i LIST
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp6 0 0 :::8080 :::* LISTEN
tcp6 0 0 :::22 :::* LISTEN
tcp6 0 0 :::443 :::* LISTEN
tcp6 0 0 :::6144 :::* LISTEN
unix 2 [ ACC ] STREAM LISTENING 6154 /run/systemd/private
unix 2 [ ACC ] SEQPACKET LISTENING 6176 /run/udev/control
unix 2 [ ACC ] STREAM LISTENING 10383 @/tmp/.X11-unix/X0
unix 2 [ ACC ] STREAM LISTENING 6180 /run/systemd/journal/stdout
unix 2 [ ACC ] STREAM LISTENING 10384 /tmp/.X11-unix/X0
unix 2 [ ACC ] STREAM LISTENING 11393 /tmp/ssh-dlHzru82H4tO/agent.636
unix 2 [ ACC ] STREAM LISTENING 9015 /var/run/avahi-daemon/socket
unix 2 [ ACC ] STREAM LISTENING 9018 /var/run/dbus/system_bus_socket
unix 2 [ ACC ] STREAM LISTENING 11647 /tmp/.menu-cached-:0-pi
unix 2 [ ACC ] STREAM LISTENING 8017 /var/run/dhcpcd.sock
unix 2 [ ACC ] STREAM LISTENING 8019 /var/run/dhcpcd.unpriv.sock
unix 2 [ ACC ] STREAM LISTENING 1692 /run/user/1000/systemd/private
unix 2 [ ACC ] STREAM LISTENING 9674 /tmp/.pcmanfm-socket--0-pi
unix 2 [ ACC ] STREAM LISTENING 11398 @/tmp/dbus-zNZIoD6Mr6
unix 2 [ ACC ] STREAM LISTENING 10572 /tmp/ssh-nDsUlVkVJRup/agent.738

SolarEdge via lan does not work for 6 Months. Use SolarEdge via Web API instead.

I'm assuming that it has worked in an older version of Domoticz.
Can I use an older version? And so which version would this be?

If i'm right, the LAN method has more options than the API method, is this correct?

Is there a solution to fix this in the new version of Domoticz?

Reverse engineer the new protocol solaredge has implemented. Me and gizmocuz allready spent 100 hours on this, now someone else turn.

BTW, My SolarEdge system was installed a month ago, and the URL for the data log is prod2.solaredge.com port 22222.

Thought I would pass this along in case it has any bearing on the module. Maybe it's where the new formatted data must be uploaded?

Some updates regarding this issue ? I would love to monitor the solar edge system using the (W)LAN option

Silince ;( no updates / fixes

Sent from my SM-G935F using Tapatalk

I would be VERY interested TOO !

I love reverse engineering, I do have some coding knowledge ( Old plain C ) but can work with python and that sort of stuff.

Can we create a new team trying to get this to live again ?
Who else can help ?

Cheers,

Frank ( netherlands )

freijn wrote:I would be VERY interested TOO !

I love reverse engineering, I do have some coding knowledge ( Old plain C ) but can work with python and that sort of stuff.

Can we create a new team trying to get this to live again ?
Who else can help ?

Cheers,

Frank ( netherlands )

I would love to help where possible (also the NL)

How can we " reverse engineer" this ?

Sent from my SM-G935F using Tapatalk

afaik and understand the process the SolarEdge is "chatting" home and dumps al the data there.
So if we caputure the stream of data and then decode the messages we can putting them in our own database instead of SolarEdge home db.

I have understood it worked before so major work has already been done, but if SE decided to move a message or rename it, the previous reverse engineering is lost and won't work anymore.

Makes sense?

Greetings Frank

freijn wrote:afaik and understand the process the SolarEdge is "chatting" home and dumps al the data there.
So if we caputure the stream of data and then decode the messages we can putting them in our own database instead of SolarEdge home db.

I have understood it worked before so major work has already been done, but if SE decided to move a message or rename it, the previous reverse engineering is lost and won't work anymore.

Makes sense?

Greetings Frank

Maybe the people who already reverse engineered this could help with this. But an can't find out who they where

@freijn: did you make some progress ?

Sent from my SM-G935F using Tapatalk

I have no Clue where to start....

Anybody can point us in the correct direction please?

@antwan / @Gizmocuz maybe you could help us start the research of re-intergration of this function

What kind of connection do I have to use to edit the SolarEdge inverter with the SolarEdge configuration tool version2?
Is it possible to connect over the LAN interface or is it only possible with a serial connector or USB? And what kind of cable do I have to get?

freijn wrote: ↑Monday 02 October 2017 21:27 I have no Clue where to start....

Anybody can point us in the correct direction please?

I have been searching on this subject for sometime. If you have a TCP and LAN cable connection on your SolarEdge inverter this document might be interesting.
A test with the Shortbus Modbus Scanner tool shows it is possible to read/scan the output of your SolarEdge via the local-ip port 502. This proofs that reading your SolarEdge via TCP configuration works. See pages 7/8 of the above mentioned document.
I hope this gives you a starting point

freijn wrote: ↑Monday 02 October 2017 21:27 I have no Clue where to start....

Anybody can point us in the correct direction please?

Here is another starting point for you.
Finally, I have a working solution to get data direct from my SolarEdge The Sunspec-Monitor Although it is a Perl script it works OK. Next step is to get it running every 5 minutes within Domoticz.

It reads the complete registers and this is the output I think this is more like it, instead of being depended on the SolarEdge website