Venus OS

I am running Venus-large and have a fairly extensive Node-Red flow consisting of about 100 nodes. My router is reporting a permanent TCP/IP session with one of the mqtt{1 to 128}.victronenergy.com servers with constant traffic of just over 10 kbit/s upload and just under 1 kbit/s download. This seems high to me but maybe it's because of my 100-node flow. Is this level of traffic to be expected?

Hello all,

As some of you know, something new is in the works, called "Venus OS large". This post is intented to start getting a large audience for it, as well as to recruite more help in further developing it.

This story is a bit longer than I usually type, here we go:

Introduction

Venus OS Large is an extended build of Venus OS, it adds Node-RED and Signal K server.

Node-RED is a tool for connecting hardware devices, APIs and online services. It provides a browser-based editor that makes it easy to wire together flows. With it, one can for example program something relatively simple such as a relay to open or close based on a temperature measurement. As well as make far more complex algorithms, tying voltage, current, power or other readings and other data available from Venus OS or elsewhere together with outputs such as relays or control points of the Victron system. All without having to write real source code.

Also Node-RED features a fully customisable dashboard, viewable in a webbrowser - both locally and remotely, via the VRM Servers.

Signal K server is aimed for yachts, and multiplexes data from NMEA0183, NMEA 2000, Signal K and other sensor inputs. It makes all that data available for Apps, such as WilhelmSK, a highly customizable boat instrument display. The Sailing with Signal K blogpost on our website is a great read for more information and ideas.

Customisation & automation without needing to be a software developer

The value of above is that now you can self configure and customise your GX Device to do many of the things asked for here. And doing so without having to posses software developer skills. It will require patience, time and to be not too afraid of trying things.

Its really extremely powerful and I'm super excited about the possibilities.

Documentation & how to install

See https://www.victronenergy.com/live/venus-os:large.

Venus OS Large is available for the Cerbo GX, Venus GX, MultiPlus-II GX and EasySolar-II GX as well as the RaspberryPi3 and RaspberryPi 4.

Want to help?

There are a few ways to help. First of all by simply installing and using it; and reporting any issues, or just that you're happily using it and what you are using it for.

The other is by helping others here on the Modifications section on Community. There is and will be no official support for Venus OS Large. Instead, we are referring users to turn here, the Modifications Space on Victron Community. You can help by answering questions.

Next, there is developing and improving the documentation; The manual needs further development, also the nodes and available measurements will need detailing and documenting, examples, screenshots, videos, it will all help adoptation and getting the best out of this. And we'll need more help for all of that that.

Lastly I am looking for help in development and support. First of all to further develop and support the Victron integration into Node-RED, ie. the node-red-contrib-victron package. Which will require nodejs experience, Linux experience, and preferably also experience with Victron products; ideally you'd be following and taking part of the discussions here on Community, (remotely-) debugging issues as well as suggesting and implementing new functionality in the said package.

Besides the node-red package, also the integration of Node-RED and Signal K in Venus OS needs to be maintained. Which requires a different skillset: deep experience and knowledge of Linux, but also the Open Embedded build system.

Conclusion

I can type a whole lot more about this, but have to stop now. Have a good Sunday! And if you have examples, or questions or comments, welcome to put them below.

Ps. Node-Red example flow:

[image]

Hi, I tested node red, but there are some faults in the installation because of me. I would like to start from the beginning. But when I install the original firmware and then the venus large image again all is like it was before. I would like to start with all wiped out. How to?

Thanks

getting an error when installing node red dashboard.

root@beaglebone:~# npm i node-red-dashboard
npm WARN saveError ENOENT: no such file or directory, open '/data/home/root/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/data/home/root/package.json'
npm WARN root No description
npm WARN root No repository field.
npm WARN root No README data
npm WARN root No license field.

How do I correct this ?

I'm using the Node Red feature in the Large version of venus os and buiding my own FUN Dashboard :) .I'm trying to access the 30-day history that one can see in Venus OS in the corresponding tab of Solarcharger that is connected to VenusGX and show it in some form on the Dashboard, but I can't seem to find the right building block. The Solarcharger block only contains the current value variables.

How to access and display History data with Node Red?

Hi

i have a raspi 4 with the large Venus OS image on it and a connected mppt100/30 .

output is a 7inch ips touch panel. This works very well.

Node red is activated and i use this to decode the serial output from a vortronic 400A Shunt so i have now following values in node-red at the moment:

- Voltage from the Board and Starter battery in V

- strength of the electrical current in A

-Battery level of the board battery in %

-size of the Boardbattery in AH

now i would like to send this as input to emulate a bmv7xx to the venus os to show it on the display as a bmv.

has someone a idea , best of would be directly in node-red itself

thanks in advance

I've read many threads but still cannot connect to Victron's MQTT server. I know I should be using mqtt62.victronenergy.com and have everything set as I understand it, including the venus-ca.crt but it fails to connect. Any help would be appreciated.

[image]

[image]

Hi Victron, we are discussing in several threads a nearly similar question without an expert comment by victron-staff:

https://community.victronenergy.com/questions/81114/ess-phase-compensation-not-working.html?childToView=81209#comment-81209

https://community.victronenergy.com/questions/80366/why-does-victron-experts-do-not-provide-an-update.html

https://community.victronenergy.com/questions/55480/ess-system-doesnt-react-not-balanced-to-high-ac-lo.html?childToView=71245#answer-71245

This main problem of an „symmetrical“ or „balanced“ ESS in a three phase grid-parallel setup is absolutely essential for the German and Austrian market. Please let us know what you think about it! Thank you very much!

I thought it might be helpful for others in the Venus OS extended image I found time based flows were all in UTC time even though I set the time zone in the Venus menu. i ended up linking my timezone to /etc/localtime from the command line and time worked as expected in Node-Red after a reboot. Might be good for Victron developers to make this link when the timezone is set in the Venus interface?

Update:

I've changed this to set the timezone in Node-Red instead of setting system wide

edit ~/.node-red/settings.js and this right above the module.exports = { line

process.env.TZ = 'America/Los_Angeles';

I have an interesting NodeRed project - based on next day weather, it is changing the minimum discharge SOC on the GX device. So if next day it is sunny, it will configure the SOC to a lower level, if it is cloudy it is increasing the SOC. At this moment I have only 4 levels, but it can be improved. How I'm doing this - you need to create a free account on https://openweathermap.org. After doing that use the API generated on that site, put it in the openweathermap node, add your city name or coordinates, and you will receive the details for the next 5 days. I'm looking only at next day, between 9AM-6PM and the value used is called visibility. Having the average value for next day, the system will decide (every day at 3PM) how the SOC should be for the next 24h. There are lots of things that can be added. If you need any other info, you can ask. Or if you have something similar, please share.

[image]

[image]

Raspberry pi 3B+, VenusOS Large V280.11/20

I clicked "update to 1.4.2" by the victron energy nodes in the node-red palette. I currently have 1.4.1 installed and working. The installation failed with the following output in the event log:

2021-09-07T04:44:28.988Z Install : @victronenergy/node-red-contrib-victron 1.4.2

2021-09-07T04:44:29.152Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict @victronenergy/node-red-contrib-victron@1.4.2

2021-09-07T04:45:08.431Z [err] npm

2021-09-07T04:45:08.432Z [err] WARN rollback Rolling back @victronenergy/node-red-contrib-victron@1.4.2 failed (this is probably harmless): ENOTDIR: not a directory, lstat '/data/home/root/.node-red/node_modules/@victronenergy/node-red-contrib-victron'

2021-09-07T04:45:09.965Z [err] npm

2021-09-07T04:45:09.965Z [err] ERR! code EEXIST

2021-09-07T04:45:09.966Z [err] npm ERR! syscall

2021-09-07T04:45:09.967Z [err] mkdir

2021-09-07T04:45:09.967Z [err] npm

2021-09-07T04:45:09.967Z [err] ERR! path /data/home/root/.node-red/node_modules/@victronenergy

2021-09-07T04:45:09.967Z [err] npm

2021-09-07T04:45:09.968Z [err] ERR! errno -17

2021-09-07T04:45:09.989Z [err] npm

2021-09-07T04:45:09.989Z [err] ERR! EEXIST: file already exists, mkdir '/data/home/root/.node-red/node_modules/@victronenergy'

2021-09-07T04:45:09.990Z [err] npm ERR! File exists: /data/home/root/.node-red/node_modules/@victronenergy

2021-09-07T04:45:09.990Z [err] npm

2021-09-07T04:45:09.991Z [err] ERR! Remove the existing file and try again, or run npm

2021-09-07T04:45:09.991Z [err] npm ERR!

2021-09-07T04:45:09.992Z [err] with --force to overwrite files recklessly.

2021-09-07T04:45:10.080Z [err]

2021-09-07T04:45:10.080Z [err] npm ERR! A complete log of this run can be found in:

2021-09-07T04:45:10.080Z [err] npm

2021-09-07T04:45:10.081Z [err] ERR! /home/root/.npm/_logs/2021-09-07T04_45_10_053Z-debug.log

2021-09-07T04:45:10.204Z rc=239

When I ssh into the raspi and go to the node_modules directory I see that @victronenergy is not a directory but a file with 0 bytes. The file config.nodes.json file, however, seems to point to "/usr/lib/node_modules/@victronenergy/node-red-contrib-victron/src/nodes/config-client.js" so maybe that's why the update do not work.

My question is, how do I make it work without screwing something up? :)

The node "VE Bus System", system "multiplus-II" chosen.

The measurement "Battery current" do not show positive charging current, only negative current pulled from batteries. While charging, msg.payload is strictly 0. I don't know if this is intentional, but it is in my view not logical. No big deal, I can calculate what I need from other input and output measurements of the multi, just wanted to report this if it is indeed a bug.

Love your work.

Is there a process for reinstalling node red on a gx via ssh, I have installed a node which seems to have crashed it

Hi All,

reading Github page for Node-Red:

https://github.com/victronenergy/node-red-contrib-victron#generating-the-node-specification-file-developers

It's possible to define new measurament for each Victron nodes available in Node-Red.

As described in Git, It is possible to have the 2 configuration files CSV:

- dataAttributes.csv

- dataAttributeEnums.csv

We want to insert new measuraments in Battery Monitor Node:

- Max Cell Voltage

- Min Cell Voltage

Thank you!

Hi, after manually updating the OS to the 2.80~large20 version I've noticed that there was also an update for the "@victronenergy/node-red-contrib-victron" NodeRED package, raising it up to the 1.4.2 from the 1.4.1.
The update procedure fails because it needs the "/data/home/root/.node-red/node-modules/@victronenergy" folder, but on the filesystem it is a file! Here is the failure log:

2021-08-27T08:34:16.028Z Install : @victronenergy/node-red-contrib-victron 1.4.2

2021-08-27T08:34:16.380Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict @victronenergy/node-red-contrib-victron@1.4.2
2021-08-27T08:34:53.239Z [err] npm
2021-08-27T08:34:53.241Z [err]  WARN rollback Rolling back ms@2.1.2 failed (this is probably harmless): ENOTDIR: not a directory, lstat '/data/home/root/.node-red/node_modules/@victronenergy/node-red-contrib-victron/node_modules/ms'
2021-08-27T08:34:53.858Z [err] npm
2021-08-27T08:34:53.859Z [err]  ERR! code ENOTDIR
2021-08-27T08:34:53.859Z [err] npm ERR! syscall mkdir
2021-08-27T08:34:53.859Z [err] npm ERR! path
2021-08-27T08:34:53.860Z [err]  /data/home/root/.node-red/node_modules/@victronenergy/node-red-contrib-victron/node_modules
2021-08-27T08:34:53.860Z [err] npm ERR! errno -20
2021-08-27T08:34:53.876Z [err] npm
2021-08-27T08:34:53.877Z [err]  ERR! ENOTDIR: not a directory, mkdir '/data/home/root/.node-red/node_modules/@victronenergy/node-red-contrib-victron/node_modules'
2021-08-27T08:34:53.955Z [err]
2021-08-27T08:34:53.957Z [err] npm ERR! A complete log of this run can be found in:
2021-08-27T08:34:53.957Z [err] npm ERR!     /home/root/.npm/_logs/2021-08-27T08_34_53_933Z-debug.log
2021-08-27T08:34:53.992Z rc=236

I've also tried to manually create the folder and re-issue the update, but some error and warnings about the downloaded code raise:

2021-08-27T08:43:12.742Z Install : @victronenergy/node-red-contrib-victron 1.4.2

2021-08-27T08:43:12.936Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict @victronenergy/node-red-contrib-victron@1.4.2
2021-08-27T08:43:46.776Z [out]
2021-08-27T08:43:46.776Z [out] > abstract-socket@2.1.1 install /data/home/root/.node-red/node_modules/abstract-socket
2021-08-27T08:43:46.776Z [out] > node-gyp rebuild
2021-08-27T08:43:46.776Z [out]
2021-08-27T08:44:12.468Z [out] make: Entering directory '/data/home/root/.node-red/node_modules/abstract-socket/build'
2021-08-27T08:44:12.472Z [out]   CXX(target) Release/obj.target/bindings/src/abstract_socket.o
2021-08-27T08:44:19.619Z [err] In file included from ../../nan/nan.h:58,
2021-08-27T08:44:19.619Z [err]                  from ../src/abstract_socket.cc:5:
2021-08-27T08:44:19.619Z [err] /home/root/.cache/node-gyp/12.21.0/include/node/node.h:737:43: warning: cast between incompatible function types from 'void (*)(v8::Local<v8::Object>)' to 'node::addon_register_func' {aka 'void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)'} [-Wcast-function-type]
2021-08-27T08:44:19.619Z [err]   737 |       (node::addon_register_func) (regfunc),                          \
2021-08-27T08:44:19.619Z [err]       |                                           ^
2021-08-27T08:44:19.619Z [err] /home/root/.cache/node-gyp/12.21.0/include/node/node.h:771:3: note: in expansion of macro 'NODE_MODULE_X'
2021-08-27T08:44:19.619Z [err]   771 |   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
2021-08-27T08:44:19.619Z [err]       |   ^~~~~~~~~~~~~
2021-08-27T08:44:19.619Z [err] ../src/abstract_socket.cc:181:1: note: in expansion of macro 'NODE_MODULE'
2021-08-27T08:44:19.619Z [err]   181 | NODE_MODULE(abstract_socket, Initialize)
2021-08-27T08:44:19.619Z [err]       | ^~~~~~~~~~~
2021-08-27T08:44:22.148Z [out]   SOLINK_MODULE(target) Release/obj.target/bindings.node
2021-08-27T08:44:22.800Z [out]   COPY Release/bindings.node
2021-08-27T08:44:22.843Z [out] make: Leaving directory '/data/home/root/.node-red/node_modules/abstract-socket/build'
2021-08-27T08:44:23.847Z [out] + @victronenergy/node-red-contrib-victron@1.4.2
2021-08-27T08:44:23.847Z [out] added 29 packages from 72 contributors and removed 13 packages in 58.326s
2021-08-27T08:44:23.904Z rc=0

After that I've tried to restart NodeRED (actually I've restarted the controller, if you can suggest how to do that I'll be really grateful) but it won't start anymore, always for the same problem about the file/folder "@victronenergy".

I've also tried from console, by running "npm install @victronenergy/node-red-contrib-victron" but the same problems verifies.

Someone has encountered the same problem?

Hi

Following the notes from here I've managed to get as many relays as I want configured on my RPi. These work on the GUI and in hardware.

https://community.victronenergy.com/questions/34195/make-more-than-two-relays-visible-on-rpi-rpi.html

The problem I'm having is that if I configure more than two relays, they stop apprearing as an option for me to control in Node-Red. Has anyone had a look at this or have a work around?

Thanks,

Dan

I have flashed the large 2.80-11-20 file to an SD-card, put it into a Raspberry Pi 3 B+, enabled node-red in console, followed the instructions on how to install the dashboard in palette and made some test nodes. VRM portal all working fine, but when I want to access the node-red dashboard by changing "/dashboard" to "/proxy" I don't get any node-red button to click, it jumps to "installation overview".

What am I doing wrongo?

This is not so much a question but more of offering what I have created to others in the community. I have been using the Node-Red add-on in Venus OS v2.70~5-large-18 to control my openEVSE car charger via MQTT. It maximises the available power from the PV array to charge the car. When there isn't enough power it will use what is stored in my BYD batteries and when they're depleted it uses the mains. It is now stable enough that I have placed the json file and a brief explanation on GitHub (https://github.com/thepaulcooper/victron-openEVSE).

Disclaimer: I am not an expert in JavaScript or Node-Red so I am sure there are more effective ways of coding what I have created. But it works and I am now charging my car from the sun.

I am having some problems using the node-red inject node to turn my Blue Solar mppt 150/70 -tr to turn it on and off - worked fine with can bus and mod bus through the venus gx but am trying to control direct from the raspberry pi node-red flow. My problem is getting the correct msg payload message to inject up the serial link - From the VE.DIRECT Protocol Blue and smart solar MPPT Chargers document (quite difficult for me to understand) I can see that register 0x0202 bit 1 needs to be set to 1 and register 0x0200 needs to be 4 for off and 1 for on - I just need to know the payload type and exact messages please - many thanks in advance

In the venus large installation guide ( https://www.victronenergy.com/live/venus-os:large ), it states for Multiplus II "Includes alarm relays as well as the AC-out 2 relay: its not possible to control those; and there is no plan to make them controllable from within Node-RED."

Is it still the case that AC-out-2 relay is not controllable and is not planned to be controllable? If so, is there a technical limitation to this, or what is the reason? Will it definitely never be supported, or is it merely "not yet" supported?

I use AC-out-2 on my Multiplus II for non-essentials, and currently it is turned off as soon as the grid input on AC-in fails. I know there are meant to be ways to change that default AC-out-2 behaviour using assistants, but it looks a bit daunting to edit those. If Node-RED supported being able to set AC-out-2, it looks like it could then be fairly simple (compared to the assistants) to allow it to provide power to non-essentials while SoC of batteries is above a certain level.

Hi there,

I've installed "venus-swu-einstein-20210416100626-v2.70~5-large-18.swu" image firmware to be able to use node-red.

All seems to be good. I can read different values with nodes like "ESS control" but impossible to change values !

Any ideas .....

Before I ruin my brand 'new' install of v2.71 on my Raspberry Pi 4 by 'just trying' I was wondering if someone can confirm how to add the Node Red option to it in an 'official' way. Can I simply take the latest large image from the dropbox share and add it via usb install as before on the release candidates?

I ask because there is no v2.71 specific large image located on the dropbox share referred to in this post (yet): https://www.victronenergy.com/live/venus-os:large

I’m only semi-computer literate - everything is trial and error and cut and paste and hours of google research… If the details include what software should be used and exactly what to type then I can usually muddle my way through. But when it comes to ‘just add a few lines of code in the xxx” I’m completely lost.

I have managed to burn an image to a sd card and install Venus Pi v2.60 large image on to a raspberryPi 3.

I have 1 Victron mppt 75/15 connected successfully to it vie ve-direct usb cable.

I have successfully got node-red running (and can even see it all via VRM Portal - including node-red which is amazing).

I’m still at beginnings of how node red works but can see its potential.

So far so good

But I’d really like to add more than 1 relay so I can control multiple external devices (like pumps, irrigation valves etc) and also control them through node red.

I’ve read the comments and half guides for adding extra relays - but they are incomplete or presume you know how to do certain un-explained steps. So I'm completely lost.

So - anyone have a step by step guide to add relays ? (and I’m on a Mac so Mac instructions would be great!)

Thanks in advance for all the amazing guides so far - and for the missing bits I hope someone will write soon…

Hi!

We are currently working on an electrical boat with Victron Energy systems installed.

The boat has a 15kw generator with a bunch of sensors which we have connected to the supported CAN-Bus system on Cerbo GX.

The generator is not a supported one in Venus OS, so for now we decided on installing Venus OS Large because of the simplicity of Node-RED.

We are receiving the CAN-frames as expected in both Node-RED and the bash-terminal through SSH and we now want to pass the translated information to D-Bus.

At this point we are going to attempt adding settings to the D-bus, using the Fischer Panda settings as a base-template.

What we do not know is how to pass this information from Node-RED to the D-bus.

Any help or ideas on the matter would be greatly appreciated.

Hi all!

A few weeks ago my Node Red (VenusOS v2.70_3-large-12) suddenly was broken on my Raspi 4B (4GB). A lot of files has been updated, which i can't understand. I'm sure, that the automatic updates has been deaticivated. Also the /opt/victronenergy/version hasn't been changed.

For example one of the updated qml files:

--- 20210507/opt/victronenergy/gui/qml/PageTankSensor.qml

--- v2.70_3-large-12/opt/victronenergy/gui/qml/PageTankSensor.qml

@@ -18,7 +18,7 @@

MbOption { description: qsTr("Black water (sewage)"); value: 5 }

]

- property VBusItem devInstance: VBusItem { bind: Utils.path(bindPrefix, "/DeviceInstance") }

+ property VBusItem connection: VBusItem { bind: Utils.path(bindPrefix, "/Mgmt/Connection") }

property VBusItem customName: VBusItem { bind: Utils.path(bindPrefix, "/CustomName") }

property VBusItem fluidType: VBusItem { bind: Utils.path(bindPrefix, "/FluidType") }

property VBusItem volumeUnit: VBusItem { bind: "com.victronenergy.settings/Settings/System/VolumeUnit" }

@@ -30,7 +30,7 @@

if (customName.valid && customName.value !== "")

return customName.value

- var inputNumber = devInstance.valid ? devInstance.value : ""

+ var inputNumber = connection.valid ? connection.value.replace(/\D/g,'') : ""

var inputNumberStr = ""

if (inputNumber !== "")

Any idea, what happend there? I will shortly update to the latest version. Will this fix this problem?

Thanks!

Hello,

I am using several Cerbo GX (HW Version 02 and 03). I've installed the node red venus-swu-einstein-20210416100626-v2.70~5-large-18.swu via usb-stick, how its described here to do:https://www.victronenergy.com/live/venus-os:large

Installation and so on is working without any problems. After reboot just sometimes I can connect to the node red interface via venus.local:1880 or IP:1880. And sometimes via VRM Remote with the ID of the Cerbo.

1) Unfortunately sometimes I can open the node red interface, and sometimes not. Then I get the notification that node red isnt installed. But it is installed and activated in the menu.

2) When its working, then just sometimes I can ad my flow (its about temperature to switch on the fans when system is getting to hot) and deploy/send to my Cerbo. Unfortunately here just sometimes happens that there will a notificatin of "connected" and sometimes not. I dont unterstand why its just sometimes working. When I change the Cerbo GX and try exactly the same procedere, its working. But then I get the next system with another Cerbo and its not working again. Attached you can find 2 pictures, how its looking like when not working (missing "connected") and when its working.

sometimes like this:

[image]

and sometimes its working like this:

[image]

Is there a dependence to the version of node red and Hardware version? I've tried also older versions of node red (16, and 10 and 12) and sometimes its working, sometimes not. Can't figure out whats wrong.

What I did after installing node red via usb stick:

1) Firmware -> online updates -> Auto update -> OFF
2) Remote control -> disable password check (do double click)
3) Remote control -> Enable on VRM -> ON
4) Remote control -> Enable on LAN -> ON
5) DVCC -> OFF
6) VRM online portal -> VRM two-way communication -> ON
7) Ethernet -> check if connected to network otherwise connect
8) I/O -> Analog inputs -> ALL OFF but temp input 1 (depends where connected)
9) I/O -> Digital inputs -> ALL OFF
10) Venus OS large features -> Node Red -> ON
Do a reboot (General -> reboot (double click)

I hope someone could help me with my 2 problems, which maybe related to each other.

Thank you.

Regards

Markus

Using an RPi 4 and Node-Red which works fine, my issue occurs when the Pi reboots.

On reboot Node-Red reverts to an an earlier state, by this I mean recent changes appear lost.

I have to install the backup JSON and delete the older flows that appear after boot.

This happens each time the Pi reboots. I have no idea why this happens and thought that once "Deploy" is pressed it would become the latest version and become the backup.

Dear Community,

I had a Automated Current limit flow set up on Node red with CCgx last year, this flow would subtract the Amps from 2 circuits that are directly connect to our generator , from the current limit so that we are able to get quickest charge times possible, while not over loading the generator when say ( oven , hob, dishwasher, 2x clothes washer , drier ) are on , in there various states of consumption.

My Question , can anyone please tell be the topic for Current limit on the Cerbo ? we have recently upgraded from CCgx, ( on the ccgx the topic was something like W/506583dbfda4/vebus/276/Ac/ActiveIn/CurrentLimit ) open to ideas ...

Many thanks

all the best

Ian

Hello
I'm very new to Venus OS large, just installed it and try to connect to signal K and Node Red to have a look. Unfortunately I'm not able to connect to the Node Red server at all. Seams there is a mistake I do. May someone can help me out, as I could not find any further infos.
I tried:

- via venus.local:1880
- via IP:1880

but both does not work at all. I'm able to connect to signalK via both methods :3000

I tried with switched on both signalK and Node Red and just one.
I tried on different browsers, all the same "access denied" error.
As it works with SignalK :3000 I'm don't believe it has something to do with browser setting.

Thanks for your help

Hi,

Node-Red is awesome, super flexible and allows amazing customisation and control of your Victron system, but it can also be complicated and many possibilities are completely untested.

It is considered a modification and only to be used at your own risk.

Victron does not provide any official support for Node-Red, so please keep questions in the modifications space on the community (and not to your dealers or sales managers).

If you are experiencing system issues and need help, please turn off Node-red and return your GX to the supported factory state before seeking support beyond the Victron modifications community.

Click here to see all the community content that uses the Node-Red topic.

Thanks :)