I'm using Node Red on Cerbo GX.
Now is Node Red unavailable from VRM Venus OS Large.
The system reported: "Too many sessions for site 166223".
Now it doesn't report anything anymore, it just loads the page.
I restarted the computer and the router, nothing helps.
I'm working on some customizations to my Venus/Pi setup and running into some issues.
(A) Does leaving my desktop connected to Node Red (https://192.168.1.125:1881/#flow/xxxxxxxxxxxx) for long periods (overnight) lead to problems that would not occur if I close the browser window when I'm not actively editing Flows?
Hunting around the Raspberry/Venus filesystem I'm not finding detailed logs so far.
(B) Where do I find detailed log files on Venus OS Large 2.92
Can Node Red log locally (on Pi3+ under /data) what appears remotely in the browser "debug" window pane?
(C) If, by default, Venus is not keeping detailed / debug logs, can someone tell me how to enable them?
(D) Does Venus OS Large v3.00~15 fix bugs in 2.92 that would make it a better choice now than continuing with 2.92? (I'd keep 2.92 SD card as-is for fallback and use a new SD card for 3.00)
Raspberry Pi 3+ - re-installed fresh in January 2023
Brand new SanDisk SD Card
apt update / upgrade done
Venus OS 2.92 - installed fresh
Node Red & Signal K enabled
Programming Node Red
Working as intended
Disabled MQTT via Remote Console at end of day
Had experimented with it, but didn't really need it
Left Node Red desktop browser window open overnight
In the morning, Node-Red in desktop browser unresponsive
SSH connection from Desktop to Pi3+ "broken pipe"
SSH reconnect attempt timed-out
Attempt to reload Node Red webpage (on desktop PC)
Refreshing web page very slow
took much longer than I was willing to wait for
Left for 2 hours
Checked Pi3+ again
Pi3+ does show up on router as connected device
Router shows Pi3+ is still sending/receiving data
Router indicates 2+ days connection time to Pi3+
Desktop browser to Pi3+ Venus Remote Console DOES respond
Checked Node Red
Responding, showing messages in debug panel again
Responding, now it does connect to Pi3+ successfully
Seems like everything has returned to normal...?
How can I change "Scheduled charging" in Node-Red?
eg: /settings/0/Settings/CGwacs/BatteryLife/Schedule/Charge/0/Soc to 80%?
Does anyone know a way to simulate an energy meter with NodeRed (Large OS)?
That must be theoretically possible.
Via Tasmota I get my yield from the PV system sent via MQTT.
ich habe eine kleine Victron Anlage und möchte Daten aus dem Cerbo in Node Red laden. Mir gelingt es aber nicht, da ich nur die Seriennummer zurück bekomme, was wohl normal ist. Mein Programmierkenntnisse sind gleich null.
Wie kann ich denn den Cerbo konkret dazu ermuntern, mir dauerhaft Daten zu senden. In einem anderen Forum habe ich gelesen, das man ihn alle 30 - 60 Sekunden ansprechen muss, dann würde es wohl funktionieren.
Ich habe hier eine Homematic Installation auf einem Raspberry, welche auch schon ein Node Red als Addon hat. Mir erschließt sich aber nicht, wie ich den Raspi alle 30 Sekunden einen Nachricht senden lassen kann. Geht das vielleicht auch aus Node Red?
Danke für eure Hilfe...
I would like to add some more virtual relay/switches to the controls on the dashboard. The controls is a convenient connection to ‘Venus OS Lage/node red’.
after I upgraded to VenusOs Large 3.00 Node Red seems to have switched to https and port 1881 and is not accessible via http and port 1880 anymore.
Is there a possibility to activate http again?
I know that https is preferred but there are reasons why this is not possible in my system.
I attempted to build my Node-red dashboard using the System parameters, however, I was unable to locate the ET112 parameter alongside other options like PF and MD.
Please give the solution for build own node-red dashboard
I am considering installing a 3 x 48/5000/70-50 multiplus 2 in 3 phase configuration (UK) with a large battery to enable profitable export to grid at times of high income. My understanding that this is difficult without NodeRed, but possible with NodeRed. Am I correct in this assumption? Further, does the NodeRed flow work with a 3 phase setup? I currently use NodeRed, but cannot play with the Victron flows as you need a physical inverter connected to the VenusOS to progress. Thanks in anticipation.
I want to publish the data from a EM24 gridmeter to MQTT, but i could not select L3 current in the drop down menu.
Any ideas ?
i'm new to Victron but long term smarthome user/DIY developer and know something about modbus. But i didn'nt understand some relationships of setting in my ESS System.
I have 3 Multiplus2, Pylontech Battery and CerboGX running large image.
ESS mode is 1, Optimized mode or 'keep batteries charged' and phase compensation enabled
ESS State = 5, Optimized Mode /w BatteryLife: SoC below dynamic SoC limit
I want to disable discharge battery when my e-car is charged by an go-e Charger.
My idea was to set the related state through MQTT and the Victron Nodes.
But i was not able to figure out which are the right/best settings i have to change.
Is it ok to set just the ESS state to 9 - 'Keep batteries charged' mode is enabled?
I'm operating a Multiplus 2 GX with activated Modbus TCP (see Picture 1). A separate Raspberry Pi which is running Node-Red connects to the Modbus/TCP endpoint. The modbus TCP connection is used to read information from the Multiplus and to control the ESS based on my dynamic energy tariff. While the communication itself works quite well, the connection to the Multiplus is unstable and breaks regularly (see Picture 2). To be able to reconnect I have to move the the modbus connection in the editor slightly and re-deploy in Node-Red. I've tried to optimize the connection settings (see Picture 3) towards the Multiplus but without any impact.
From my current perspective there is no reason for the instability. Within the VRM portal there are no connection issued and the state of the Multiplus is reported without data gaps or connection issues.
Hi, I'm startet into the venus large nod red adventure, run on a cerbo gx. I got some programming background though no nod red.
I'd like to build my own dashboard but are not really sure how to get hold of the historical data of my system.
Could someone please point out where the logging is saved or do I have to save manually into a database? Some hints where to start?
I read something about creating a nod red flow using MQTT and writing values into a influx database, but somehow the cerbo is already logging. Doesn't seem reasonable to me Programming a second logging routine...
I have node red running on a Cerbo, which is working just fine in all respects but 1.
When accessing the unit I get an HTTPS error, presumably because of a certificate issue, and have to select advanced>go to site (Unsafe), or simmilar depending on the browser.
I probably just need to download/generate/install a certificate but cant see where to do that!
Since its only ever going to be local I guess HTTP would be a potential option but that seems like a defeetest fix and I dont know it it is possible anyway.
If anyone has any insight I would apriciate a leg up as it were,