A combination of Solis Cloud, Home Assistant via RS485 (Modbus) communication. This repo is a documented workaround for Solis inverters to connect Solis Cloud and the local Home Assistant based on my own experience. It will include references and examples of the code, configurations, and required components.
My PV installation commenced back in August 2022. Since then, I started my journey with Home Assistant, and several Solis integrations made by some clever folks out there. My main goal was to keep Solis Cloud functionality and allow for advanced monitoring, remote control, and general automation of my home equipment. As I was going through my journey, I found many obstacles and limitations with Solis Cloud, dataloggers, and its design. Therefore, to get over those obstacles, I have designed the below, which meets my requirements and it works quite well.
Most importantly, my design doesn't disconnect the Solis cloud, and works (coexists) with your local Home Assistant integration in combination with any Solis datalogger.
The main goal is to ensure that a datalogger can work as normal and without any distruption. The datalogger acts as the Master device, and it talks directly to the inverter (Slave). Having an additional Master (e.g., Waveshare Gateway) on the same RS485 network is to create collisions, which could affect all RS485 devices. Some dataloggers don't accept multiple TCP connections (e.g., S2-WL-ST), and those will disconnect the Solis Cloud whenever used with an integration; others don't support Modbus TCP (e.g., DLS-W, S3-WIFI-ST), and some will fully rely on the cloud (S3-WIFI-ST). Some obsolete dataloggers couldn't provide remote functionality via Solis Cloud (e.g., DLS-W, DLS-L).
Here it comes the Waveshare gateway to query the inverter. It can serve multiple clients, keep the inverter's cloud reporting functionality, and is not limited by any datalogger. The below is my configuration, but the use case could differ per datalogger.
The main device is the Waveshare RS485 to PoE ETH (B) - the non-PoE version is described as per this guideline. There are no major differences between PoE and non-PoE devices, except for the convenience of powering those when you have multiple next in line.
I was trying different settings as I had some teething issues, and I noticed that it works better when the integration (I am using Home Assistant SolaX Modbus integration for my Solis inverter) is pulling data more often (e.g., every 5 seconds). There was an issue raised to resolve errors in reporting, and the solution to reduce the block size proposed by the author seems to be working well. You can find more at the following address.
I recommend using one of the pairs from the Ethernet cable for RS485 wiring. There is no need for 120 Ohms resistors at each end of the RS485. Both, Waveshare and the Inverter have resistors built-in.
-
The
TCP Serveron my diagram and presented here as 187 GW acts as a gateway for other devices (datalogger and HA integration), and it has a baud rate of 9600. TheModbus gateway typeisAuto query storage type, and I enabledmulti-host, so the datalogger queries will not create conflicts - at least that is my reasoning. -
The
TCP Clientpresented here as 171 DLG is pointing at the IP and the port of theTCP Serverwith the same Serial config - screenshots below -
Both
TCP ServerandTCP Clienthave theModbus_TCP Protocolas theTransfer Protocol- see the screenshot below.
TCP Server Config
More Advanced Settings for TCP Server
TCP Client Config
More Advanced Settings for TCP Client
- The Waveshare used for the batteries connection is the same device, but the
Transfer Protocolis set toNone. I use VirCom to extend its connection to COMX on my laptop, so the software can connect to batteries and monitor them. Looking into usingModbus_TCP Protocoland integrating with HA via MQTT or even setting the MQTT on the Waveshare, but that is not my priority at the moment.
Datalogger/Waveshare - Modbus TCP - direct connection - e.g., DLS-L, S2-WL-ST, Waveshare RS485 to PoE ETH (B)
Datalogger - Solarman based - direct connection - e.g., DLS-W
Cloud connection - any Solis datalogger
- SolisMon3 - advertising Solis' Inverter data to MQTT - compatible with
DLS-W
- DLS-W
- DLS-L
- S2-WL-ST
- S3-WIFI-ST
- 2 * £35.00 - Waveshare RS485 to PoE ETH (B) - https://www.waveshare.com/wiki/RS485_TO_POE_ETH_(B)
- 1 * £28.00 - PoE Switch - P-Link PoE Switch 5-Port 100 Mbps (TL-SF1005P)
- 1 * £12.00 - Exceedconn EC04681-2023-BF Male/Female for Solis/Ginlong Inverter RS-485 port
- 1 * £2.50 - DIN rail
- 1 * £20.00 - Sourcingmap 240mm x 160mm x 90mm Plastic Dustproof IP65 DIY Junction Box Power Protection Case - I recommend a bigger box = more expensive
- 1 * £6.00 - Pack M20 20mm IP68 Waterproof Red Cable Glands, Suitable for 6mm - 12mm Cables, Plastic Nylon Compression Glands Connectors with Locknut and Washer - AVARTEK
- around £10.00 for some RJ45 cabling and connectors
£148.50
Optional to connect batteries:
- 1 * £35.00 - Waveshare RS485 to PoE ETH (B) - https://www.waveshare.com/wiki/RS485_TO_POE_ETH_(B)
- Compatibility with other brands and inverters
- More Solution Concepts
- Battery Monitoring - HA, MQTT
I AM NOT RESPONSIBLE FOR ANY USE OR DAMAGE THIS DESIGN MAY CAUSE. THIS IS INTENDED FOR EDUCATIONAL PURPOSES ONLY. USE AT YOUR OWN RISK.
IF YOU FOUND THIS USEFUL, YOU CAN BUY ME A BEER
