We had out new solar panels installed today, They were supplied by a company by Glow Green, although the install itself was handled by a subcontractor. I would recommend them, the experience I had was very smooth. I previously setup the network for the inverter’s data logging module but inevitably there were a few issues which this post is about.

First thing was that I had the newer S3-WIFI-ST installed, rather than the DLS-W I was expecting. This is both a blessing and a curse as the newer model connects to their Solis Cloud service however it loses the ability to read MQTT data locally which older models (such as DLS-W) had. There is some technical information and hardware photographs available on a GitHub project page with the “Solis inverter ESP8266 data logger, S3 WiFi stick reverse engineering and ESPhome firmware”.

As I had prepared my network for a different model, with different firewall, requirements. I, in good faith, referred back to the Solis firewall configuration guide and setup the firewall to allow access to:

  • 47.91.64.7 on port 1883
  • 47.254.187.5 on port 443

I found, via a page on configuring WiFi on this data logger device another, older, set of Firewall information for it which also had this same information.

After making these changes, we tried to setup the data logger which did not work. Examining the firewall log, I discovered that the data logger wasn’t using these IPs and ports at all. From the empirical data, I determined that these are the required firewall holes needed:

  • 47.91.64.15 on port 443
  • 223.5.5.5 on port 53
  • 223.6.6.6 on port 53

With just these 3 holes, it works fine. I am a little concerned that it is using some 3rd party for DNS, rather than my local (DHCP configured) DNS services.