Understanding the following articles is recommended before reading this article:

This article includes information on the following nodes:

All nodes are part of the Node-RED package. All the nodes require a connection to the MobiusFlow Engine.

MobiusFlow Inject

The MobiusFlow inject node injects MobiusFlow objects into the flows based on when there is a change of value within that object. The object range the MobiusFlow inject node covers is specified as a list of included / excluded URIs or wildcard URIs.

Config

The node allows a list of subscriptions to be specified in the subscriptions table. These subscriptions tell the node which objects to subscribe to change of value events from. As such, this table is specified as a list of URIs or URI wildcards.

Each subscription can be specified as an include or an exclude. This will either include or exclude that subscription group from the object selection respectively.

In the config window screenshot above, the 1st subscription row is used to select everything on service 022. The 2nd subscription row is then used to exclude specifically instance 000001/022/000B/0001 from the selection.

Output

The flow below is used to demonstrate the out of the MobiusFlow inject node:

Following a COV event, the debug window showed the following output:

The full JSON response is copyable in the code block below:

Get Multi-Object

The get Multi-Object node gets multiple objects based on a defined set of object URIs.

Config

The Get-Multi Object requires a list of object URIs to be specified within the objects table. Each row will point to a single object URI.

More URI rows can be added using the add button at the bottom left of the Objects table. The following screenshot shows an example node's config populated with 3 object URIs:

Input

Any input message can trigger the node.

Output

The node outputs an array of MobiusFlow objects. The following code block is a copyable JSON response example:

Get Multi-Resource

The get Multi-Resource node returns multiple resources based on a specified set of resource URIs.

Config

The node requires of one or more resource URIs to be defined in the resources table.

Additionally, the send property allows control of how the resources are outputted.

Input

Any input message can trigger the node.

Output

The format of outputted resources can be switched between simply showing the resource values, or including the resources name and URI with each resource. Example JSON outputs are as follows:

PV (present value) Only

Simple array of PVs, one for each resource defined in the nodes config:

PV, Name & URI

Object keyed by URI, one key for each resource defined in the node's config. Each containing resources PV and name:

Discover

The discover node returns a list of children of a given Hub, Service, Profile or Instance, specified by URI. The following table shows the return type based on which level the URI is specified to.

Config

The node allows the discovery URI to be specified via the configuration window.

Input

Any input message can trigger the node. It also possible to define the discovery URI in the topic of the input message. This allows the discovery URI to be dynamically changed. If a valid URI is found in both the input topic, and the node's configuration, the node's configuration takes precedence.

Output

The output type of the discover node varies depending on which level the discovery is made. For all types, the data is packaged within data sub property of the response property of the output payload. See the following screenshot as an example:

Here are example copyable JSON responses at all discovery levels:

Hub

Service

Profile

Instance

Discover Object List

The discover object list node returns a list of MobiusFlow objects based on a URI or URIs (including wildcards).

Config

The node takes the following config properties:

Input

The node can be triggered by any input message.

Output

Depending on the setting of the output property in the node's configuration, the node will either send whole MobiusFlow objects, or just their URIs. Below are copyable example JSON responses in both cases, based on the following example:

URIs

MobiusFlow Objects

The node type also allows the output to be in the form of a single message, or a message for each discovered object. This is controlled by the send configuration property. The screenshots below show this action via use of the following flow:

Single Message (Array format)

Multiple Messages (Individual format)

Filter By Rid Value

The Filter By Rid Value node returns a list of object URIs on a specified service, filtered by a user defined filtering function. This filtering function is applied to a user specified resource on each object and is written in Javascript.

Config

The node takes the following configuration properties:

Input

The node is triggered via any input message.

Output

The node will return a list of resources matching the criteria specified in the configuration.

The following is a simple flow to trigger the Filter By Rid Value node and display the output in the debug window.

In this example, the config of the Filter By Rid Value node is set to the following:

The filtering function is also shown in the following code block:

The node has been setup to search on MobiusFlow Hub 000001, service 02A. The search has been specified to only cover PID 0201. Resource 40 has been selected as the resource to which the filtering function will be applied.

In this example, the filtering functional itself has been coded to return a true result if the resource's value is greater than 0.

Triggering flow yields the following in the debug panel:

The results is the URIs of the objects which passed the filtering function when applied to resource 40 on each object.

Clear Resource

The clear resource node clears the value of a resource at a specified priority.

Config

The node takes the following configuration:

Input

The node is triggered via any input message. The URI of the resource to be cleared can be specified in the topic of the input message. This allows the target resource of the node to become dynamic.

Output

Following the use of this node, the node will output the new value of the resource. If priority 15 was cleared, this will likely be the falling back value residing in priority slot 16.