Interface on a server that bridges to the local network. Through an ethernet hub, or the inverter could be connected to a dedicated network The local server are connected to an ethernet switch. In order to do this the network traffic between them mustīe monitored by a server on the network. This requires temporarily connecting via the RS232 interface.ĭata sent between an inverter and the SolarEdge monitoring portal is captured andįed into semonitor.py. Using the -k option, or the inverter must be set to unencrypted mode. The encryption key for the inverter must first be obtained and given to semonitor.py So monitoring services and firmware updates will no longer be available. In this mode, the inverter will no longer be communicating with the SolarEdge server
#Solaredge inverter how to#
The network could be made to resolve the address, but how to do that is beyond the To the inverter on the dedicated interface. Of the inverter to a dedicated ethernet interface on the server running semonitor.pyĪnd specifying the -n option which will run a simplified DHCP/DNS server that responds This may be done by connecting the ethernet interface Portal by resolving its hostname (usually ) to the IP address of The inverter is made to connect to semonitor.py instead of the SolarEdge monitoring Where the data that is being sent to the SolarEdge monitoring portal is captured. Mode, where semonitor.py interacts with the inverter directly, or in a passive mode Data can be parsed by semonitor.py either in an active SolarEdge inverter monitoring data can be accessed by any of 3 hardware interfaces -Įthernet, RS232, or RS485. Solaredge publishes an API that allows access to their portal, however thisĪlso does not include module level data. Solaredge supports the open Sunspec Alliance logging protocols, however this data is onlyĪccessible via an RS485 interface on the inverter and does not include module level (optimizer)ĭata. This project enables monitoring the performance data of SolarEdge inverters and optimizers.
#Solaredge inverter software#
Contributors are only familiar with the particular SolarEdge equipment that they personally own and are not motivated to maintain the software beyond their particular needs. If you use it and have a problem that you can't solve, you can open an issue, however there may not be a response, given the relatively small number of contributors and the fact that SolarEdge does not support this project in any way. This means that if you have a newer inverter or if the firmware in your older inverter is up to date, the only way to access performance data is going to be via the RS485 interface.Īlso, please note that this software is made available here without any expectation of support.
In the years since then, SolarEdge has introduced new products which no longer support the RS232 interface, and they have dropped their encryption algorithm and are now using the far more secure and mainstream SSL/TLS encryption method which is essentially not hackable.
A few years later, SolarEdge implemented a homegrown encryption algorithm for the communications to their monitoring server, which prevented access for a while until an effort by a number of contributors to this project was successful in figuring out the algorithm which got it working again. The same data was also available on the RS232 and RS485 interfaces which were provided on their inverters. It was possible to reverse engineer most of the messages in order to obtain the optimizer level data which was not otherwise available. When this project was started ten years ago, SolarEdge inverters communicated with their monitoring server using a proprietary data format that was sent in the clear.
0 kommentar(er)
