Differences

This shows you the differences between two versions of the page.

--- venus-os:large [2025-08-18 12:01] – Added 5.12 Node-RED files, folders & settings warwickchapman
+++ venus-os:large [2025-08-29 09:09] (current) – support edit warwickchapman
@@ Line 26: / Line 26: @@
 ===== 2. Where to find support =====
-Victron maintains the integration of Node-RED and SignalK into Venus OS for GX-devices.  However, Victron does not provide support for systems which make use of these extended features to implement advanced solutions.
+Node-RED and SignalK are a stable and reliable features in Venus OS Large for GX devices.  There are tens of thousands of systems running Node-RED or SignalK in the field.  However, Victron does not provide support for systems which make use of these extended features to implement advanced solutions.
 **Node-RED support**
@@ Line 235: / Line 235: @@
 The only charger which has a relay that is controllable is the Smart IP43 Charger. To use that for remote control, set its mode, using the VictronConnect app, to be remote controllable. Note that its use is limited: the relay is only powered (and thus only controllable) when the charger is switched on. It doesn't work when it's turned off with AC connected. This limitation applies to the 230V models as well as the later 120V/240V models.
-==== 5.8 Node-RED Dashboard ====
+==== 5.8 Virtual devices ====
+Virtual devices make it possible to connect equipment and data sources that are not natively supported by Victron to a GX device. Once created in Node-RED, these devices appear on the GX-device and behave like real Victron-supported hardware, becoming part of the larger Victron-based solution.
+=== Purpose and Examples ===
+Virtual devices are ideal for integrating third-party or DIY equipment:
+  * **Virtual meteo** – weather data from an unsupported or custom weather system with an API can be injected into a virtual meteo device. The data (e.g. wind speed, temperature, humidity) then becomes visible to the GX and in VRM.
+  * **Virtual grid meter** – calculated grid import/export values can be published to the GX device, allowing systems without a supported grid meter to present grid data.
+  * **Virtual GPS** – GPSd or another data sources can be used to provide live positional data.
+  * **Virtual tank/temperature sensor** – integrate LoRa, MQTT, or custom sensors.
+=== Supported Virtual Devices ===
+Currently supported device types include:
+  * **Battery**
+  * **Generator**
+  * **GPS**
+  * **Grid meter**
+  * **Meteo** (eg. weather station data)
+  * **Motor drive** (eg. electric boats)
+  * **PV inverter**
+  * **Tank sensor**
+  * **Temperature sensor**
+=== Setup ===
+  - Update to the latest version of Venus OS.
+  - Add the relevant **Virtual Device node** in the Node-RED flow.
+  - Configure the device type.
+  - Connect it to a data source or control logic.
+==== 5.9 Node-RED Dashboard ====
 Besides the flow and automation functionally, Node-RED also offers a fully customisable dashboard. Including graphs, indicators as well as controls such as switches and sliders.
@@ Line 248: / Line 280: @@
 {{ :venus-os:vrm_node_red_ui_step_3.png?direct&600 |VRM Node-RED UI - Step 3}}
-==== 5.9 Configuration files ====
+==== 5.10 Configuration files ====
 WARNING: the vast majority of systems using Node-RED will not, and should not (!), have to modify any of the files here described. Venus OS itself, including Venus OS large and Node-RED, is made such that its not necessary to dive into the command line.
@@ Line 267: / Line 299: @@
 For more information on such Node-RED configuration customisations, see https://nodered.org/docs/user-guide/runtime/configuration.
-==== 5.10 Ready-to-use solutions ====
+==== 5.11 Ready-to-use solutions ====
 Node-RED can also be used for doing more advanced tasks. Some examples of ready-to-use solutions are:
@@ Line 273: / Line 305: @@
   * [[https://flows.nodered.org/node/node-red-contrib-eskomsepush|EskomSePush]] - use Node-RED for charging the batteries before the next load shedding happens (for South African users)
-==== 5.11 Using data from VRM  ====
+==== 5.12 Using data from VRM  ====
 For some flows it can be useful to retrieve data from the VRM Portal Database. For example to retrieve de Solar irradiation or yield forecasts.
@@ Line 298: / Line 330: @@
 The [[https://flows.nodered.org/node/victron-vrm-api|Victron VRM API node]] makes it easy to use the VRM API from a Node-RED flow. Alternatively take a look at above mentioned Dynamic-ESS flow.
-==== 5.12 Node-RED files, folders & settings  ====
+==== 5.13 Node-RED files, folders & settings  ====
 On GX devices, the ''nodered'' system user has its home in ''/data/home/nodered/''. The actual Node-RED runtime (flows, nodes, configuration, and ''settings-user.js'') lives in ''/data/home/nodered/.node-red/''.
@@ Line 325: / Line 357: @@
 <code>background-image: url(/image.png);</code>
-NOTE: All files are stored on ''/data'', which has limited space. Do not store large media files, logs, or large images in ''/data''. Consider hosting such data externally and reference via URL or another Node-RED supported external storage mechanism (database, cloud storage, MQTT, FTP, etc).
+Restart Node-RED to apply the changes:
-Managing the Node-RED service:
 **Stop**
@@ Line 338: / Line 368: @@
 <code>svc -t /service/node-red-venus</code>
-==== 5.13 Node-RED FAQ ====
+NOTE: All files are stored on ''/data'', which has limited space. Do not store large media files, logs, or large images in ''/data''. Consider hosting such data externally and reference via URL or another Node-RED supported external storage mechanism (database, cloud storage, MQTT, FTP, etc).
+==== 5.14 Node-RED FAQ ====
 === Q1: Write/read file gives "Error: EACCESS: permission denied' ===