An introduction to running Node Red on the Cerbo GX 

You seem to have an issue with your controllers that could be resolved with more troubleshooting and without having to resort to Node Red. Unless you are a programmer familiar with the language Node Red is going to be a bit cumbersome for one off uses like this. We envisage it being used in industrial applications where there are multiple iterations of the same installation.

@@pkysinc This is the 3rd year these Victron SmartSolar 100/50 have been in service for my Offgrid solar. One of the six has already developed an issue with its current sensor and got sent back for warranty service. Of the other 5x, they are connected via Bluetooth plus the VE Direct connection. Whether this is running with the Smart BMS 712 or now the Lynx Shunt, the random inactive charging issue still persists. Sometimes it is one, other times two units, but i have not seen three. They don't have CAN bus communication to the Cerbo GX, like my other 150/100 do, that is one main difference. And the 150/100 never developed this issue, despite running on the same network and serving the same period of operation. I am not sure, but i think there may be a QC issue with these 100/50. They are not as robust as the 150/100. Obviously they run different firmware. As a software developer, i have the technical background to develop software solutions to address problems. I don't mind doing so. I tried pinging with others but few run as many controllers concurrently like my system, so they have not encountered this problem yet. I did encountered the random temp compensation issue that Andy ( from Offgrid garage) mentioned which stopped the controller from charging... this happened out of nowhere one morning. But overall, i am familiar with the type of tantrum these 100/50 can throw at me now, so if there is an easy way to develop counter measures against them, it would be the easiest approach i can take to ensure that the system continues to run 24x7 with minimal supervision. Unfortunately i do not have visibility to the firmware code for the 100/50. But it wouldn't be difficult to add a sanity check when the PV voltage is Not zero or a certain threshold, and the controller has NOT been disabled that the controller should NOT be in the OFF charging state. It should be reset to start the Bulk/Absorption charging state. The funny thing is, even if i go through the menu to disable the charger when i see this problem, if i don't wait until the pop up reminder to suggest enabling the changer, before re-enabling the charger again, it won't fix the problem. The re-enabling MUST be done AFTER the pop up reminder appears... so this is one observation i noted. It definitely looks to me like a software /firmware bug. And the problem can occur in any of my 6x 100/50 controllers, it is not localised. Compare this to the 150/100 that runs a different firmware and never experiences this issue, it further reinforces this speculation that it is firmware specific issue.

This is not the correct place to be discussing this