Bloubul7

No need to reflash. There is an integration for HA that allows the Sonoff devices (Ewelink) to incorporated into HA.

I would also suggest a combination of HA and Node Red. HA provides you the ability to control items via the mobile App and Node Red is stronger on the automation side

Agreed, initially also looked at the ESP32 devices. But with the Pi Zero being cheap and more powerful it was the beter solution for me. https://github.com/andresarmento/modbus-arduino

The pin out table is incorrect. The pin out diagrams is correct

Just check and make sure which ttyUSB has been assigned to your cable

The problem is most likely your adapter.

Have a look at the Deye and SunSynk inverters. Yes they do cost a little bit more but will provide you with more flexibility, stability and options in the future. The Axpert and Infinisolar inverters do work well but are not hassle free and does require some tinkering normally.

Would it not be possible to switch your battery to the CAN port and then utilize the RS485 port for the Pi?

Yes, the Pi next to the inverter will run a dedicated instance Node Red. The flows in Node Red will publish the information to your Home Assistant Pi via MQTT. OS - You can run the official Pi OS.

Hi, Yes, reading the settings will retrieve the current settings from the inverter and populate the dashboard. You can then make changes if you like and press write settings to push back the changes to the inverter. Some explanation on the different dashboards: System Settings - Provides you with the ability to read and write the live settings from the inverter Default Settings - This stores a set of default settings to the file system on Pi. This was utilized to store my non-loadshedding settings. These settings are automatically pushed to the inverter based on the loadshedding status Loadshedding Settings - This stores a set of loadshedding settings to the file system on Pi. This was utilized to store my loadshedding settings. These settings are automatically pushed to the inverter based on the loadshedding status Time Mode - I use the Time Mode to trigger feeding back into my non-essential loads on certain days of the week. Due to my solar setup currently being undersized to power the entire house on days when my domestic worker (higher loads due to washing, tumble dryer, ironing etc) is here, this allows me to save some additional power on the alternate days by feeding back into the non-essentials. A note for everybody else, if you want to access the dashboards then go to the following address http://[your pi's IP]:1880/ui

Mine has been set to indefinite and haven't had any issues. Need to log in and check the database size just for interest sakes. The JSON is attached hereto. Sorry I couldn't help more actively during your setup, work has been crazy for the past 6 months (can't moan during the current economic state). One interesting new Node Red feature I have seen recently is a Whatsapp integration. This could be quite useful to set up a couple of warning flows and have the system send you a Whatapp message should they be triggered. SunSynk-1617804388751.json

That is correct, I use the Loadshedding flows to alter the inverter settings to be more conservative during loadshedding periods. The settings are stored to the local file system on your operating system. This however needs to be enabled in the Node Red configurations. My slowdown was resolved by upgrading to a Raspberry Pi 4 with a M.2 drive. This is a bit of overkill, but I know that my data is safe.

Hi Scoobs, Well done, below is my current Grafana Dashboard to give you some ideas.

Have you tried changing the Unit-ID under the Flex-Getter? Unfortuantely I only have a single unit, can't test out the parralel functionality

You shouldn't be working on a live inverter. The inverter should be fed by a double pole circuit breaker (fed directly from the mains) sized in accordance with the cable used and the inverter limits.

The inverter shouldn't be fed by an EL. The EL should be downstream of the Inverter

Post reserved for InlfuxDB + Grafana setup

Post reserved for Home Assistant integration

Post reserved for Node Red setup

Post reserved for Hardware requirements

Good day All, Over the past couple of months I have received numerous requests to share my NodeRed flows used for monitoring the status of the SunSynk inverter. My initial idea was to package all of the flows into an easy to use package and user interface, however my work loads have not provided me the luxury of time to play around and make it a fool proof system. Please note that the use of these flows are at your own discretion with no liability to either myself, this site nor any members of this site. Do not attempt implement these flows if you are unfamiliar with the working of the ModBus protocol or basic programming. Brief overview of the flows: LoadShedStatus - This flow determines the loadshedding status through a webscraper. I use this information to trigger a secondary set of settings to the inverter in case of load shedding. ModBusRead - This flow is responsible for reading information from the Inverter via the Modbus Flex getter ModBusWrite - This flow is responsible for writing settings back to the inverter via the Modbus flex getter Inverter Monitoring - This flow is responsible for obtaining all of the inverter monitoring values. The values are then send to Home Asssistant via MQTT as well as logged to an InfluxDB for monitoring via Grafana SSFormRead - This flow reads the current system settings from the inverter and display it via the NodeRed UI SSFormWrite - This flow writes any changes made to the system settings via the NodeRed UI back to inverter SSDSRead - This flow reads the "Default Settings" from storage and displays it via the NodeRed UI. I use the "Default Settings" to store my optimal system settings when there is no Load Shedding. SSDSWrite - This flow writes the "Default Settings" from the storage to the Inverter. The flow is also triggered automatically from the LoadShedding status flow SSLSRead - This flow reads the "Load Shedding Settings" from storage and displays it via the NodeRed UI. I use the "Default Settings" to store my optimal system settings when there is no Load Shedding. SSLSWrite - This flow writes the "Load Shedding Settings" from the storage to the Inverter. The flow is also triggered automatically from the LoadShedding status flow TimeMode - This flow triggers different settings on different days of the week. My PV Solar is currently not big enough to carry my whole house, I utilize this flow to feed electricity back into the non-essential loads on the days which my domestic worker is not working. This helps me to optimize my savings on certain days of the week while maintaining healthy battery levels. NodeRed Palettes required for the flows: node-red-contrib-actionflows node-red-contrib-influxdb node-red-contrib-modbus node-red-contrib-queue-gate node-red-contrib-schedex node-red-contrib-simple-gate node-red-dashboard The next couple of posts have been reserved to further expand on the hardware requirements and basic set up of the monitoring. The idea of sharing my flows is to contribute to the community, let us keep this going as a community project by assisting and contributing to project. flows (5).json sunsynk_modbus.docx

Fully agreed, I bet most of us have horror installer stories to share.

Another solution would be to optimize your loads to utilize the additional solar. For instance try put your geysers on timers and have them heat up during the day.

You will only receive data once you have polled the modbus address.

Use the bottom diagram, the table is incorrect.