JuanH

This is where I am scared to sound dumb now... do I edit the py file before installing it?

Not yet, I looked at the link you shared the other day, and just ended up feeling real dumb 😅 I'll look at the updated docs when I get home this evening to see if I can figure it out.

@kellerzaI finally got around to replacing Bloubul's original NR flows and custom HA entities with your Sunsynk add-on. One thing I'm not quiet figuring out is that it only added PV1 sensors, but not any sensors for my second PV2 array. I went through the documentation on your GitHub repo, but cannot find any reason there. I'm sure I'm just doing something stupid, but hope you can guide me in the right direction?

I went through all the suggestions. This was the one that was easiest and worked the best for me: https://solar-assistant.io/shop/products/sunsynk_rs485

Awesome, that did it. Thank you. For future posterity, it is the "Modbus SN" setting in the advanced menu. Will require a restart of the inverter to take effect,

Hi all, It's been almost a year since I started using these NR flows, and had no issues to date. However, this week I had my installer update my Sunsynk firmware, and now the flows are no longer working. These are the errors I am getting. Any idea where to start troubleshooting, or what might have changed in the more recent inverter firmware?: 2022, 12:29:49 AMnode: d6b15ede.669a7 msg : string[60] "Modbus Failure On State sending Get More About It By Logging" 11/13/2022, 12:29:49 AMnode: Inverter msg : error "Error: Timed out" 11/13/2022, 12:29:49 AMnode: Inverter msg : error "Error: Client Not Ready To Read At State reconnecting" 11/13/2022, 12:29:49 AMnode: Inverter msg : error "Error: Client Not Ready To Read At State reconnecting" 11/13/2022, 12:29:49 AMnode: Inverter msg : error "Error: Client Not Ready To Read At State reconnecting" 11/13/2022, 12:29:50 AMnode: Inverter msg : error "Error: Client Not Ready To Read At State reconnecting" 11/13/2022, 12:29:50 AMnode: Inverter msg : error "Error: Client Not Ready To Read At State reconnecting" 11/13/2022, 12:29:50 AMnode: Inverter msg : error "Error: Client Not Ready To Read At State reconnecting" 11/13/2022, 12:29:51 AMnode: Inverter msg : error "Error: Client Not Ready To Read At State reconnecting" 11/13/2022, 12:29:51 AMnode: Inverter msg : error Below is the Modbus settings I've always used:

Noticed my Sunsynk data wasn't updating since this morning. For anyone else who noticed the same, there is an upstream issue with the HA add-on, and using the serial port on a RPi: https://github.com/hassio-addons/addon-node-red/issues/1312

Can't speak for the one you linked to, but personally, after fiddling and faffing with adapters, connectors, and raspberry pi HATs, evetnually got one of these, and have had no issues for almost a year later: https://solar-assistant.io/shop/products/sunsynk_rs485

@finch6I got all the mentioned adapters and HATs in this thread. The easiest, simplest, most reliable, and neatest solution was just getting the cables from Solar Assistant: https://solar-assistant.io/shop Unless you want to go with any of the DIY options so you can learn from the experience, this would be my recomendation.

I've removed my WiFi dongle, just incase SunSynk decides to mass push this update out, in a ploy to get everyone to use their new cloud platform... Or maybe I'm just paranoid

A friend of mine has an Axpert inverter, and is looking into monitoring options, similar to what I did with my SunSynk and Home Assistant. I was going to suggest something like this to him: https://github.com/BionicWeb/AxpertPi But, his supplier has told him that he cannot have more than one serial/usb device on his inverter at a time, and since he has a BMS system hooked up to it, he thus cannot achieve any sort of monitoring. Can someone confirm is this is correct? He sent me this picture of his BMS connection (excuse the image quality):

The USB will most likely fail pretty soon if you keep it as the main drive, due to the amount of reads/writes. Look through the Everything Smart Home channel I mentioned earlier. There is a good guide on moving your installation onto an external (or internal if you can with the NUC) SSD drive.

I tried about 4-5 different options mentioned on this thread. However, the simplest and most reliable option I found was the cable for sale on the Solar Assistant website: https://solar-assistant.io/shop

Hey Saliegh. My recomendation would be to install HA OS: https://www.home-assistant.io/installation/generic-x86-64 Once done, install the Node Red add-on from the included add-on store. Then you can start with the flows in this thread. I also recomend the Everything Smart Home channel on Youtube. Loads of useful guides for HA on there: https://www.youtube.com/c/EverythingSmartHome/featured

Thanks, @Bloubul7 I've given your new flow a try, but I've noticed that the entities don't update with the "last_reset_topic". I've checked the topic value, and it definitely sends an updated value over MQTT, either as scheduled, or when done manually, but the subscribing entities don't seem to pick it up. Not sure what I am doing wrong? Example of manually triggering the inject: Entity's last_rest stays the same:

Ok, something's gone wrong, and maybe you guys can help me figure it out. The above values stopped working at midnight last night. My guess is it has something to do woth the last_reset? Maybe I need to be passing it a value at midnight to update it as having re-initialized?

An alternative approach to the above is to add these values into your config file instead: homeassistant: customize: sensor.sunsynk_grid_gridbuy_day: last_reset: "1970-01-01T00:00:00+00:00" device_class: energy state_class: measurement sensor.sunsynk_solar_pv_day: last_reset: "1970-01-01T00:00:00+00:00" device_class: energy state_class: measurement

Tried it last night. One thing that is missing from our flows to have this work is state_class and last_reset properties. They are needed for Long Term Statistics, which the new system uses: https://developers.home-assistant.io/docs/core/entity/sensor/#long-term-statistics Once I added these in the the necesarry values, I was able to use them in the new HA Energy configuration:

I had an interesting issue today, and hoping someone might be able to shed some insight. I noticed that my solar system wasn't sending any power to my batteries, which were sitting on 54% SOC, according to my Sunsynk inverter. When I checked the batteries' individual SOC, the master, a US2000C, was on 99% SOC, and the second battery, a US2000B, was on 10% SOC. I then did a physical check of the batteries, and noticed the master had a red error light on. I switched them both off, as well as the inverter, waited 2 minutes, and switched everything back on. This seems to have cleared the error state on the master, however they were obviously exteemely imbalanced. I've since disconected the battery array from the inverter, and I am allowing them to balance each other out at the moment, but I'm wondering what could have caused the error state on the master in the first place, and also concerned on why it would not have reported the error state to the inverter thus halting use of the slave battery as well, instead of over depleting it like has happened.

The way I understand it, this is just a UI change. before, you would specify a Time Zone, and then the next Time Zone would signify the end of the previous one. The first time zone would go in MB Register 250, and the end zone would be in MB Register 251. With the new update, the start and end time are explicitly set, but for example on the first Time Zone range, would still occupy MB Registers 250 and 251. That is my guess, at least. Will test when I eventually get the update myself.

Someone posted this on another thread. Not sure how accurate it is, however:

Has anyone got any thoughts on how to get or calculate the total kWh for each of the PV1 and PV2 arrays? There's a "Day PV PowerWh" register at address 108, but nothing for each of the individual ones. I'm hoping to push this info back into Solcast to train it's solar forecasting algorithm for my rooftop.

Took a while to figure it out, but managed to slap a solution together, for anyone who is interested:

For anyone interested in how they can monitor battery statistics from their Pylons directly, I've created the following Node-RED flows for this. I'm very new to Node-RED, so any constructive feedback is welcomed: https://github.com/juanhaywood/nodered-pylontech-console-reader/blob/main/README.md

Hey @Bloubul7. Do you have any experience setting up monitoring of Pylontech batteries with Node Red that you can share with us? I'd like to get individual sets of data from each of my batteries in my battery bank, which the BMS doesn't report to SunSynk, so hoping to get it directly from the batteries themselves.