How can I install vcgencmd in VenusOS?
I want to use it to read data from the Raspbbery Pi.

Ik ben bezig met node red maar ik vrees dat ik er gewoonweg te weinig van snap.

Voor dat ik heel veel verkeerd doet is mijn vraag, is er iemand in de positie en de mogelijkheid om mij even te helpen met een aantal instellingen.

Ik wil een instelling maken dat mijn grid feed in veranderd door de soc van de batterij.

En ik wil dat er een relai schakeld op de cerbo bij een soc van >95%

En ik wil een relai schakeling maken op basis van temperatuur.

Ik hoor het graag :)

Attached are two flows required to integrate ESP into node red for those that want to get load shedding forecasts and then use this data to automate behaviour in response to outages.

I have not got far enough to create a flow for auto-charging/topup yet, but will get there.

You will need to sign up for an API key at: https://eskomsepush.gumroad.com/l/api?layout=profile.

This is put into the "set header to token value" node.

You will also, using postman and the instructions available at ESP or online, find your region code URL and put that into the "check forecast status node".

Thanks to Phil Gavin for the ESP flow which I have modified.

The Load shedding flow will put the following on a dashboard.

[image]

You can then use the various outputs to develop whichever behaviour you require in order to automate for load shedding.

I will post mine once available.

I am sure there are more efficient ways of doing this for those more experienced, but it works.

As soon as from 1.12 firmware there is an option for ESS External Control, Im wondering if I can implement the following scenario: charge battery during night time only (except cases when SoC is low). Thats what's my plan:

1. Switch MultiRS Mode to ESS External Control

2. Using integrated Node set ESS State to "10 - Optimized mode w/o BatteryLife: self consumption, SoC at or above minimum SoC"

3. When SoC is down less than 30% change ESS State to "12 - Optimized mode w/o BatteryLife: recharging, SoC dropped by 5% or more below minimum SoC"

4. As soon as night time came (after 23:00 till 7:00) change ESS state to "9 - 'Keep batteries charged' mode is enabled" until full charge

5. As charge is full change it State back to 10.

Is it a good idea overall? Will it work?

Hi,

iam using the venus OS Large image (raspberry4 v.2.92) and i want to enable the "project-function" as described here: https://nodered.org/docs/user-guide/projects/

But i cant find the correct "setting.js"

I set "project enbale: true" here:

./usr/lib/node_modules/node-red/settings.js

./usr/lib/node_modules/node-red/venus-settings.js

but nothing happens. Is it possible at all in the large image?

Thanks

Stephan

Hi

I just eant to hear if anyone has done some Nordpool integration to get prices into the NodeRed and control i.e. to stop/deactivate feedin when price is under at chosen value?

I have already done a little to get daily prices into an array, but I simply cant figure out how to work with arrays.

1) I want it to pick the price in the array(price per hour) for the hour(clock) of the system, so I can turn on and off the feedin. I also need to figure out how to read to the system to disable/enable feedin excess.

2) it could be great to calculate the feedin excess kwh and multiply with the price of the hour. This gives a sum of earned money of sold power to grid.

BR,

Lars (Denmark)

VRM has not worked properly for weeks and today I've lost my installation from the menu, it's just a blank screen saying Add Installation.

Does anyone at Victron have an idea of timeframe when it will be back or know how I can see my system in the meantime? I guess I do need a backup of some sort.

Does anyone have a Node-RED dashboard showing ESS basics for example. Most of my flows are solar forecasts or modifying ESS behaviour for utility tarrifs, I didn't expect to need to use the dashboard to see VRM-like stats.

Hello,

**on edit: for some reason posting inline links are not working for me, so I posed the links as plain text**

I'm trying to enable persistent context stores on a Cerbo GX for Node Red, per this article.

https://nodered.org/docs/user-guide/context#:~:text=Node%2DRED%20provides%20a%20way,This%20is%20called%20'context'.

Apparently, there are a couple (few?) different settings.js files in the Cerbo and I was modifying the default one at the default NR path:

/usr/lib/node_modules/node-red

Modifying that file broke NR. I had to reload the regular then large firmware to get NR working again. Restoring my changes did not seem to work.

I then saw this article

https://community.victronenergy.com/questions/139691/where-did-my-node-red-flows-go-after-firmware-upda.html

which indicates that the correct path to settings.js should be:

/data/home/nodered/.node-red/

Modifying that file by un-commenting the contextStorage section as follows:

/** Context Storage
      * The following property can be used to enable context storage. The confi                                                                                                                                                             >
      * provided here will enable file-based context that flushes to disk every                                                                                                                                                             >
      * Refer to the documentation for further options: https://nodered.org/doc                                                                                                                                                             >
      */
     contextStorage: {
         default: {
             module:"localfilesystem"
         },
     },

worked and my context values survive a reboot.

I then tried to modify settings.js to have memory and file storage options (also per the above article) like so:

contextStorage: {
   default: "memoryOnly",
   memoryOnly: { module: 'memory' },
   file: { module: 'localfilesystem' }
}

When I do that, NR won't launch, throwing the error:

Error: remote installation does not seem to have a running Node Red service.

Any Idea why this won't work?

The reason for all of this is I have setpoints to run fans, battery heat, etc. that I can adjust via a NR dashboard. I want the last settings to be saved in the event of a reboot. I thought the second method would be nice so only the contexts that I explicitly need would be written to disk, but I suppose it's no big deal to write them all.

Is this the best way to do this in a Cerbo NR deployment? Any issues writing the files to the Cerbo file system? I understand that because I'm writing to the /data partition, the files should be safe from a firmware upgrade.

Thanks.

Hi,

I've read many discussions, articles etc regarding firmware updating of Victron devices.

This is what I understood:

• if it works, don't update it
• never ever update Multiplus, unless you know how to configure it back since it goes to factory setting after the update (I have 3F system)
• if needed you can update MPPT and Cerbo GX, it shouldn't delete any settings

Now my questions are:

• did I understood it correctly?
• I'd like to install Node-RED on Cerbo GX. If I do that will it preserve the settings if I use the full version of FW? Or will I need to do anything else after the update?
• there was a new OS v3.00 yesterday. Is it safe to update the FW to the full version of v3.00 with Node-Red if I have v2.92 now?

Thanks a lot.

I have a Mopeka TD40, which I now realize isn't supported natively on the Cerbo. Is it possible to get a connection and read data from it using Node-RED?

I have set up a single phase ESS (Multiplus2) which is working as expected so far.

I would like to control the charging from the grid flexibly via nodered while relying on the gx ess functionality to provide zero feed-in functionality.

I found that I can control "disable charging" via nodered but that works only during the scheduled charging times. And while a charge is scheduled zero feed-in functionality is not working although charging is disabled.

What is the best way to achieve charging control via nodered while in ess mode?

Max charge current is set depending on a variety of factors using NodeRed, and has been working flawlessly for months. I recently noticed that it stopped fluctuating as expected, and checked the code to see if it was still set correctly, as well as whether or not it made it into the "remote console" (in DVCC -> "Maximum charge current"). I also checked that there was no interference from the BMS, and that the current voltage wasn't close to any of the limits either.

When disabling the NodeRed code and setting the charge current manually in remote console, this didn't have an effect either.

Ultimately, since I couldn't make sense of the situation and none of the data I reviewed gave any explanation, I decided to restart the VE.Bus system which - as expected - returned things to normal.

The MPs are running firmware 498, I checked the changelog and it doesn't seem that there have been any changes pointing to what I'm describing above (except maybe for "miscellaneous changes"). Is anyone aware of a firmware change that would fix the issue I have described?
Thanks!

I have a EM24 Ethernet as part of an ESS. Is it possible to gather data from the EM24 via nodered through one of the Victron nodes?

If not, is there an example anywhere of how to poll data from the EM24 Ethernet in parallel to the GX via Modbus TCP from nodered?

Hello! Is it supported and/or possible to upgrade node.js on a Cerbo to something more recent than v14.17.6? There are some interesting flows that I would like to add, but they rely on newer versions of node.

VRM hasn't connected all afternoon for me. I can't get a remote Console either. I also just noticed Venus is showing as offline by my router.

Unfortunately this means that I can't control my system without being physically present. I have Node-RED code running for example, but can't access it.

Any thoughts on how I might connect? All has worked since install last year.

Is something still going on at Victron to cause this? Why would venus be offline in that case. It's like it doesn't connect to WiFi anymore.