jacauc

[{"id":"be3ebae7.6ed828","type":"function","z":"28c7d530.54db9a","name":"Assemble Config","func":"//var fulltopic\nmsg.topic = \"homeassistant/sensor/SunSynk\" + \"/\" + \"/\" + msg.shorttopic + \"/\" + \"config\";\nmsg.topic = msg.topic.replace(\"//\", \"/\");\nmsg.payload = {\n \"unit_of_measurement\": msg.unit,\n \"state_topic\": \"homeassistant/sensor/SunSynk\" + \"/\" + msg.shorttopic + \"/\" + \"value\",\n \"name\": \"SunSynk_\" + msg.shorttopic,\n \"unique_id\": msg.shorttopic,\n \"device\": {\n \"identifiers\": [\n \"SunSynk\"\n ],\n \"name\": \"SunSynk\",\n \"model\": \"SynSynk\",\n \"manufacturer\": \"SunSynk\"\n } \n}\n if (msg.deviceclass != \"\") {\n msg.payload.device_class = msg.deviceclass\n }\nreturn msg;","outputs":1,"noerr":0,"initialize":"","finalize":"","libs":[],"x":710,"y":280,"wires":[["cf57d2c1.c918f","d329b5a1.56bb08"]]}] Updated code of the Assemble Config Node to allow all entities to be grouped under the same device in HA. Also fixed the frequency values which did not show up in HA. Files uploaded. Due to continuous tweaks, I think I'll put it on my github page going forward. Inverter Monitor.json Publish to MQTT and DB.json

Be aware that it will change some of the names of the tables in your influxdb, so dashboards may be affected. Let me know if you need help transferring data from the old tables to the lowercase tables.

https://flows.nodered.org/node/node-red-contrib-cycle Forgot to mention 🙂

Doh! Noticed my file names vs flow names are swapped.

Thought I'd share my current flows for anyone interested. Removed all Solar Readings (nodes) as I do not have PV (yet) Split the data output into a separate flow to simplify changes Set msg values for each of the nodes so they can be reused later Cycle through each reading one by one to avoid parallel requests to modbus - seems to work a slight bit better. Format MQTT topics using the home assistant MQTT discovery protocol, to allow HA to pick up the entities automatically https://www.home-assistant.io/docs/mqtt/discovery/ Feel free to comment - I'm not exactly a node-red or MQTT expert, but this seems to work for now. inverter monitoring.json publish externally.json

For the moment I just set up the timeout value to 100ms (fail fast) and disabled the error logging. All of the values make it to mqtt and influx about 9/10 cycles, so even though imperfect, it's not hampering my ability to use the data. Ignorance is bliss for the moment

More debug Linux raspberrypi 5.10.17-v7+ #1414 SMP Fri Apr 30 13:18:35 BST 2021 armv7l The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Wed May 19 11:46:19 2021 from 192.168.1.70 pi@raspberrypi:~ $ sudo node-red-start Start Node-RED Once Node-RED has started, point a browser at http://192.168.1.121:1880 On Pi Node-RED works better with the Firefox or Chrome browser Use sudo systemctl enable nodered.service to autostart Node-RED at every boot Use sudo systemctl disable nodered.service to disable autostart on boot To find more nodes and example flows - go to http://flows.nodered.org Starting as root systemd service. 19 May 11:49:48 - [warn] [modbus-flex-getter:Inverter] Modbus Failure On State sending Get More About It By Logging 19 May 11:49:48 - [error] [modbus-flex-getter:Inverter] Error: Timed out 19 May 11:49:49 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:49 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:49 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:49 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:49 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:49 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:49 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:49 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:49 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:49 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:49 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:49 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:49 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:49 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:49 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:49 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:49 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:49 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:49 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:49 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:49 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:49 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:50 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:50 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:50 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:50 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:50 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:50 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:50 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:50 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:50 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:50 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:50 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:50 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:50 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:50 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:50 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:50 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:50 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:51 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:51 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:51 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:51 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:51 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State reconnecting 19 May 11:49:52 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State init 19 May 11:49:52 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State init 19 May 11:49:52 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State init 19 May 11:49:52 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State init 19 May 11:49:52 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State init 19 May 11:49:52 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State init 19 May 11:49:52 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State init 19 May 11:49:52 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State init 19 May 11:49:52 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State init 19 May 11:49:52 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State init 19 May 11:49:52 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State init 19 May 11:49:52 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State init 19 May 11:49:52 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State init 19 May 11:49:52 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State init 19 May 11:49:52 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State init 19 May 11:49:52 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State init 19 May 11:49:52 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State init 19 May 11:49:52 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State init 19 May 11:49:52 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State init 19 May 11:49:52 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State init 19 May 11:49:52 - [error] [modbus-flex-getter:Inverter] Error: Client Not Ready To Read At State init ^C pi@raspberrypi:~ $

I'll try a third USB device to see if that works any better. Will hold off for now with the other devices. FWIW, I updated all packages on the Pi and also reinstalled nodejs using the script on the node red site. Everything now on latest versions. Same result.

@Sc00bs, I know you said you are using the same cheap adapter. Was there any specific driver that had to be installed in Linux for it to work as expected?

I have a few of these as per attached picture. I'm doing inverter rs485 port to Cat 6 to usb converter A/B and connected directly in the Pi 3B. I'm also thinking that the influx and mqtt connections are irrelevant since the timeout is between pi and inverter.

Well, I did it exactly as I was explained. Wires 2 and 7 in A and 1 and 8 in B. Have a few of those usb converters, so tried another also to see if that eliminates the issue. Exact same results. I'm also guessing that if the polarity was wrong it wouldn't work at all. Mine works, just times out every few seconds

It's ttyusb0. No other USB devices are connected to the Pi. When clicking the search button on node red, I'm given only two options: ttyusb0 and ttyama0 Could it be the power supply? Saw an undervolt warning. Will change power supply and see if it is any better.

I'm running on a raspberry pi 3b. The influx dB is on my Synology NAS and the mqtt broker is on my Home Assistant Pi4. Also brings me to another point. Is it possible to get all entities from mqtt automatically added to my home assistant? Should I change the topics to have a "homeassistant/sensor/" prefix? Or is there another simpler way?

On @Bloubul7 flow it's 1.5 seconds, on @Sc00bsflow it's 5. Is that too frequent?

I tried serial expert - made no discernable difference. Looking at my ModBusRead flow I can see the inverter going from: Initialize Init Connected Queuing Active Timeout Non-stop in a loop with about 2-5 seconds between each state. All values populate into grafana and MQTT very well - albeit with about 1 minute delay. So inbetween all the errors, something is working but for some reason it seems to timeout soon thereafter. Debug Errors range in the below: Error: Client Not Ready To Read At State init Error: Client Not Ready To Read At State reconnecting Error: Timed out Modbus Failure On State sending Get More About It By Logging Not sure if this is supposed to be normal? @Sc00bs is your debug log empty?

Cool, i've done all that. Still getting all the errors like before, but MQTT is populating as well as influxdb. Will try serial expert

I have yes, really helpful stuff everywhere! Would you mind sharing json for your latest grafana dashboard?

Got the cable connected to inverter RS485 port, port 2+7 and 1+8 of the other end of the cable connected to by USB-RS485 converter and it's connected to my PI running Node-Red. Clean node-red installation, with the required pallettes installed and the flows from Bloubul imported and deployed. Trying to configure my modbus-client, but it cycles very quickly between init, connected, timeout etc... Any ideas here? Occasionally also seeing: Modbus Failure On State sending Get More About It By Logging

@Bloubul7 @Sc00bs I'm about to get started with this as I got my RS485 converter recently. Is there a central repository somewhere (such as github) with the latest json, dashboards or useful content? Thanks again!

Hi, I have a single Sunsynk 5.5 inverter and a single Hubble AM2 battery (no PV) purely for minimizing impact of loadshedding. It's currently running in AGM% mode since I'm still waiting on the Canbus cable to be installed. Can someone please supply me with the correct inverter settings for this use case? I would like to double check the values programmed by the installer since last night I only lasted an hour during loadshedding with very few appliances on in the house. The battery also charges at about 1% per hour which is ridiculous. I have reason to believe my battery may have been exporting to the grid during loadshedding. How can I double check all of the settings to ensure this doesn't happen? Thanks Jacques

Hi @Sc00bs, I tried following your wiring instructions, but I am still a little unclear which 2 pins of the ethernet cable should be wired into the rs485 converter? Can you advise the pin numbers and which pins (A/B) they connect into the converter? Does it mean that both wires 2&7 connect to A and both 1&8 into B? Any help would be much appreciated

I already have Home Assistant, MQTT, Node Red and Grafana running on a dedicated rPI for home automation. If I install another Pi next to the inverter, will this run a separate dedicated instance of Node Red? What OS image should I be using on this Pi as a platform?

Interesting, thank you! Will check it out. So I'm assuming there's no way to poll it natively over TCP/IP from the data logger web-interface? My Hubble AM2 lithium battery cable will only be installed next week. I'm assuming that if this uses the modbus port, I'm stuck?

Recently got a sunsynk 5 and Hubble AM2 battery installed to help with loadshedding. Planning to add some PV's later when the budget allows for it. I'm an avid fan of all things automation, and have been toying with Home Assistant, Node Red, MQTT, Arduino, Raspberry PI's and the likes, for years. What would be the simplest way to get basic information from the Inverter/Battery to my Home Assistant setup? At the moment, I'm interested in only a few options, such as determining whether the house is running off the inverter/battery or off the grid, plus some graphing of voltages/wattages/frequencies. I have a few PI's and Arduinos lying around the house, but preferred would be to somehome poll directly from the Wifi Data Logger. Any advice would be appreciated!