MobiusFlow® connects, controls and communicates with 1000s of sensors and control devices to provide actionable insights and automated responses. Developed and successfully deployed with many projects over the past 17 years by engineers with first-hand experience in project management and installation such as CBRE, Ingram Micro, TD Synnex and IBM.

Whether you are looking for a full walkthrough or just dipping in to get more information about a single topic, our documentation site is the perfect companion to the training courses on our main site.

📖 User Guides

The user guides are instructional walkthroughs. Follow these guides from start to finish or jump to a section to learn how to perform specific tasks.

⚙️ Technical Docs

Looking for more detailed technical information? These articles dive deeper into the more technical aspects of MobiusFlow®, from Architecture to API details, ports, protocols, configuring services creating flows, and more.

MobiusFlow® is a middleware software application

MobiusFlow® connects, controls and communicates with 1000s of sensors and control devices to provide actionable insights and automated responses. Developed and successfully deployed with many projects over the past 17 years by engineers with first-hand experience in project management and installation such as CBRE, Ingram Micro, TD Synnex and IBM.

The Administration page covers user management, backup and restore, licence settings, security as well as setting the node's Hub ID. The page is divided into corresponding tabs accordingly.

User administration

Users can be added, modified and deleted from within the User Management Tab on the Administration page.

Backup/Restore

Setting the Hub ID

1. The main menu

2. The services palette

3. The objects palette

4. The configuration tree

5. The service and object configuration section

The main menu

The main menu is displayed on all pages. It allows switching between Configuration, Diagnostics, Node-RED Flows and Administration. The Administration option is only shown for users who have admin privileges.

The services palette

The services palette shows the list of Mobius services that can be added to the configuration. To add a service to your configuration drag it from the services palette and drop it on to the configuration tree.

The objects palette

The objects palette shows the list of Mobius objects that can be added to the configuration. To add an object to your configuration drag it from the objects palette and drop it on to a service in the configuration tree.

The configuration tree

The configuration tree shows the services and objects currently added to the configuration. Clicking on the triangles on the left of the tree either expands or contracts a branch of the tree. The currently selected item is shown as highlighted in orange.

To delete a service or object, hover over the item and click on the dustbin icon which appears to the right of the item.

Deleting a service deletes all associated objects

The service and object configuration section

This section is dynamic and updates depending on which item has been selected in the configuration tree. If a service has been selected the service's configuration properties are displayed. Similarly, selecting an object or object resource shows the relevant configuration options.

Always click the Save Changes button to persist changes to a service, object or resource configuration. Any changes to a service, object or resource only become active after the service has been restarted on the diagnostics page.

Service diagnostics and control

The service diagnostics and control page shows all of the configured services, their current status and controls to start and stop services.

Run state column

The Run State column (2) shows the current run state of the services in a traffic light. The colours are defined as follows:

• Grey - Not running, never started

• Red - Not running, manually stopped

• Amber - Starting or attempting to start

• Green - Running

Actions column

The Actions column (3) has start / stop buttons for each service. Services can be manually started or stopped by clicking on the action buttons.

Service status column

The service status column (4) shows the current status of all running services. In addition to a text message, the statuses are colour coded as follows:

• Amber - starting or status unknown

• Red - service is running but in fault (see text message for details)

• Green - service is running and not in fault

The values shown in the Service Status column are tied to the service status object associated with the service. These status objects are automatically created and updated by the services as object profile ID 0001 with instance 0001. You can read the status of these objects but should not write to them.

View objects column

The View Objects column (5) are hot-links to the Objects Diagnostics page, but filtered to only show objects belonging the the relevant service.

Object and resource diagnostics

The Objects diagnostics page can be shown by clicking on the Objects button on the left of the screen (section 1 in image below) or by clicking on the View Objects hot-link described above. To view all objects belonging to all services use the Objects button (section 1 in image below).

Clicking on the plus sign (3) next to an object expands it to show all of its resources and their current values (2).

Modifying a resource value

Resource value modifications are temporary and could be overwritten by a service or Node-RED flow, and do not persist between service restarts or node reboots.

MobiusFlow has been containerised and is run via docker.

Mobius v1.X.X

Below is an example docker-compose.yml file you could use when running MobiusFlow. In this example, an online version of MobiusFlow 1.19.1 is used. Note that, as well as the MobiusFlow service (labelled simply 'mobius'), the file also containers a reference to an nginx and mongodb containers.

The nginx container is used for port mapping, and mongodb container used as a database. Neither of these are required to run MobiusFlow.

This file can also be downloaded here:

Licensing

It is important to include the correct licensing information within the environment variables of your docker-compose.yml file.

Page coming soon. Please contact support@mobiusflow.com to arrange a support call on this topic.

What You Will Need?

1. A device with a web browser such as a laptop, tablet or smart phone, capable of connecting to a 2.4GHz WiFi access point

2. A SIM card removal tool, large paper clip or pin to push the configuration mode button

3. A powered MobiusFlow® connector

4. The connector's Serial Number

Enabling Configuration Mode

The connector's configuration mode can be enabled in two ways:

Using the Configuration button

Using a pin hold in the configuration mode button (inside the small hole to the right of the USB connector) on the front panel for 2 seconds

Release the button and the green LED will flash rapidly

Using your laptop / tablet / smartphone look for a WiFi network with the same name as the connectors serial number

Connect to this network and enter the connector's Config Mode Password. The default is mobiusflow

Open a web browser on your laptop / tablet / smartphone and enter http://192.168.4.1 into the browsers address bar and hit enter

The web browser will show the connector's configuration Home page

Using a Web Browser

Make sure that the connector and your laptop / tablet / smart phone are connected to the same Ethernet network

Open a web browser and browse to <your connector IP address>:8080 e.g. 192.168.1.20:8080

You will need to enter a user name and password. The user name is admin and the password is the same as the connector's Config Mode Password. The default is mobiusflow

After a short delay the web browser will redirect to the connector's configuration Home page

What You Will Need?

1. A balenaCloud account with Microservices access (this requires a paid account)

Creating a New Fleet

Navigate to the Fleets page

Click on the Create Fleet button

Enter a fleet name

Choose device type Raspberry Pi 4 (using 64bit OS)

Select fleet type Microservices

Click on the Create new fleet button

What is balenaCloud?

What Device Types are Supported?

MobiusFlow

We currently have software images for thee different device types for balenaCloud. These are:

MobiusFlow RPI Connector

The MobiusFlow RPI Connector works with the following Raspberry Pi types:

• Raspberry Pi 4

• Raspberry Pi 5

MobiusFlow Device Variables

The image below shows the Device Variables created when MobiusFlow® is deployed to balenaCloud.

Expand the items below for detailed information on each Device Variable

What You Will Need?

1. A valid MobiusFlow® licence (licences can only be used on one device)

Adding Your Licence to a BalenaCloud Device

Navigate to the correct fleet and device

Select the Device Variables page. You will see a list of all of the device's variables with override buttons next to each variable

Click the override button next to the MOBIUS_LICENCE variable

In the popup delete the text <replace with your licence code> and enter your licence code

Leave all other settings as their default values and click the Add button

MobiusFlow® will restart to install the licence

Updating or Replacing a Licence

Under some circumstances it may be necessary to enter a new licence code. In order to make the new licence code work follow the procedure above to enter a new code

You will also need to tell MobiusFlow® to renew its licence by setting the Device Variable MOBIUS_LICENCE_RENEW to true

Click the override button next to the MOBIUS_LICENCE_RENEW variable

In the popup change the value from false to true

Leave all other settings as their default values and click the Add button

Wait for MobiusFlow® to restart, confirm that the new licence is working and reset the Device Variable MOBIUS_LICENCE_RENEW to false

Click the override button next to the MOBIUS_LICENCE_RENEW variable

In the popup change the value from true to false

Leave all other settings as their default values and click the Add button

What You Will Need?

1. A balenaCloud account with Microservices access (this requires a paid account)

2. A compatible balenaCloud fleet (Up Board, Intel NUC or Raspberry Pi 4)

Deploying from balenaHub

Navigate to the Apps page

Search for MobiusFlow

Select the correct device type

Click on the Deploy button

Balena will switch to your balenaCloud dashboard

If you already have a new fleet or want to upgrade the MobiusFlow® version on existing devices, select Use an existing fleet instead

Select the fleet from the drop down and click on the Deploy to fleet button

After a few seconds you will see the new release being built for your fleet

This will take a minute or two. Once the build is complete you will see the release on the dashboard. All devices, which have not been pinned to a specific release, in your fleet will automatically start to update to the new release.

You can also view the release history in the Releases page of your fleet.

Click on a device Summary to see which release it is running. You can also pin device to specific releases on this screen

The configuration of the network interfaces of a MobiusFlow® balenaCloud device is handled by the manage microservice. All configuration is stored in a JSON file which can be updated by plugging in a properly configured USB memory stick or through the balenaCloud device terminal.

Network Configuration File Structure

Editing the Network Configuration

Using the balenaCloud Device Terminal

Navigate to the Device Summary page of the device you want to configure

Open a terminal in the manage microservice

Change to the /data/.mobius/manage directory and edit the networks.json file by running the following commands:

This will open the network configuration file for editing using the vi editor

Make any required changes and save the file

Exit the terminal and restart the manage microservice by clicking on the restart icon next to the manage service

Using a USB Memory Stick

Using a USB memory stick to update the network interfaces is useful when none of the network interfaces is configured to connect to the internet so it is not possible to use the balenaCloud device terminal. You will obviously need physical access to the device to use this method.

Format the USB memory stick as FAT32

Rename the USB memory to MOBIUSCONF

Create a file on the USB memory stick called networks.json

Open the file on your laptop or PC in your favourite text editor and paste in the correct JSON configuration from the examples above

Make any required changes

Save the file and unplug the USB memory stick from your laptop or PC

Plug the USB memory stick into any of the USB ports on your device

Reboot your device

When the device reboots it will copy the networks.json onto the device and use the new configuration for its network interfaces (this will take a minute or two)

You can then remove the USB memory stick and your device will continue to use the new network configuration.

balenaCloud devices can run multiple microservices in separate Docker containers. Deploying MobiusFlow® to your device will create three microservices. You can start, stop and view logs for each service on the balenaCloud device summary page.

mobius

This microservice runs the MobiusFlow® application.

manage

mongodb

A full version of MongoDB which you can use to store / retrieve data in flows.

The default settings are

The Home page has the following buttons

Configure Network

Configure the wired or wireless Ethernet network settings

Manage Certificates

Manage all certificates for TLS connections. The default certificates are for MobiusFlow® cloud hosted instances but you can add your own if required

Configure MQTT

Set Config Mode Password

Change the configuration mode password

About

See information about the connector such as the software version, serial number, andwhich modules are installed

You can also update the firmware on this page

Reboot Device

Reboot the device to exit configuration mode and use the new settings

The Connector collects data from sensors and sends data to actuators via standard wireless sensor protocols such as EnOcean and Workplace Occupancy, and sends this data securely to a MobiusFlow using an MQTT based Protocol.

Once the data has been received by a MobiusFlow instance, it is decoded and the associated MobiusFlow object is updated with the latest sensor readings which can then be processed by the gateway.

Connector Options

There are several hardware options for the MobiusFlow Connector software:

Power Options

You have three options to power the connector

Network Options

You can connect to your network via wired Ethernet or 2.4GHz WiFi

Front Panel

The image and table below describe the connections and LED indicators on the front panel of the connector.

Product Label

Part Numbers

It is possible to have up to two radios for wireless sensors in a single connector. This is useful when you have combination of sensors using different protocols.

The current options are EnOcean and Workplace Occupancy using either 868MHz for the EMEA region of 915MHz for the USA and Canada.

Download Connector Firmware

v3.1.1

v3.2.0

If you forget your connector's Config Mode Password or want to fully reset all settings to the factory default follow the procedure below

What You Will Need?

1. A SIM card removal tool, large paper clip or pin to push the configuration mode button

Factory Reset

Using a pin hold in the configuration mode button (inside the small hole to the right of the USB connector) on the front panel for 10 seconds

While you are holding the button in the green LED will start to flash rapidly and after 10 seconds the connector will reboot. Once you see the power on LED sequence release the configuration mode button

Setting CA / Server Certificates

When using TLS you will need to set the correct CA / Server certificates. You can have up to three certificates set. If the connector fails to connect using one of the certificates it will cycle through all three, trying each one until it connects

The default certificates are ISRG Root X1 certificates which are used when connecting to MobiusFlow® hosted instances of MobiusFlow®

You can set the certificate by pasting the certificate text into the selected certificate slot

Setting Client Certificate and Keys

If your setup requires the use of Client certificates you can set up to four different certificates and keys. Paset these into the selected certificate and key slots

Hardware Requirements

Raspberry Pi

A Raspberry Pi is required. Currently supported Raspberry Pi models include:

• Raspberry Pi 4

• Raspberry Pi 5

An SD card for each Raspberry Pi is required to store the connector image. We recommend a minimum storage of 8GB.

Transceiver Hardware

Most protocol types require specific hardware to translate that protocol to the Raspberry Pi.

EnOcean

The following transceiver types are supported. Only 1 is required per Pi:

Etching SD Image

BalenaCloud

MobiusFlow Raspberry Pi connectors run Balena OS. Athlough not required, if your organisation registers with BalenaCloud, Balena OS grants a direct VPN link to the connector, allowing configuration changes to be made over the internet.

When using more than 5 devices, BalenaCloud becomes a piad service. As such, we offer versions of the Balena images which do not support remote access and therefore do not require a subscription to BalneaCloud.

Without Remote Access

The following, no remote access images can be downloaded:

With Remote Acccess

The following is an overview of the steps involved to use BalenaCloud with MobiusFlow RPI connectors:

1. Create BalenaCloud Account

2. Create BalenaCloud Fleet

3. Attach BalenaCloud Fleet to the corresponding MobiusFlow Connector Balena Application
4. Add a new device to the fleet and download the subsequent Balena image

5. Etch the image

Etching

BalenaCloud charges hosting fees when more than 5 devices are associated to the account. If remote access to the Connector confiruation is not required, the device can be deleted from the BalenCloud fleet. The Connector software running on the device will remain, and the device will operate as normal.

Accessing Configuration Page

Via Balena Fleet

If the Connector is hosted via BalenaCloud and has an internet connection, the configuration can be accessed anywhere via the BalenaCloud Public Device URL.

MobiusFlow Hosted

If the connector is hosted by MobiusFlow, please contact support to receive the Public Device URL.

Self Hosted

The BalenaCloud Public Device URL can be found by Navigating to the connector device on the BalenaCloud fleet.

Via Raspberry Pi Access Point

By default, the MobiusFlow connector will broadcast a WiFi access point, the name of which matches the connector's serial number (in the form of MF_XXXXX). Connect to this access point on a computer or mobile device. Then the configuration window is accessible by browsing to 10.42.0.1.

Via Local Network

If the connector is connected to a local network via Ethernet or WiFi (with a known IP address) and you're able to also connect to this network using a computer or mobile device, then simple browse to the local IP of the connector.

Login & Home

Login

When browsed to the configuration window of the connector, a login screen is presented.

The default password of all new MobiusFlow connectors is:

mobiusflow

Note that, if the connector is not new, this login password may have been changed.

Home Page

When on the the home page, the current status of the connector is shown. This includes:

The main menu also allows navigation to the connectors configuration pages. These includes those for Network Configuration, MQTT Configuration, Certification Configuration, and the Change Password page (allows the connector configuration password to be changed).

Configure Network

It is critical that the MobiusFlow connector's network situation is such that it can access the target MobiusFlow instance over the network. This may be over the internet or simply over a local network.

In either situation, the connector must be connected to the network and the configure network page allows for this.

Connection Type

The connection type allows choosing between a Wired or WiFi connection.

If using a Wired connection, ensure the Raspberry Pi is plugged in via Ethernet.

If using WiFi mode, the WiFi SSID and corresponding password must be populated.

TCP/IP Settings

The TCP/IP settings allow switching between DHCP and Static IP allocation. Unless there are specific reasons to set the connector on a static IP address, using DHCP is recommended.

If using the connector in Static mode, the Subnet Mask, Default Gateway and DNS 1 can be set. If it is not clear what to use here, use the default settings as shown below.

Note that, the default gateway is not required however if the connector required access to the internet, the local IP address of the internet providing gateway (Network router / modem) must be populated here. This is often in the form XXX.XXX.XXX.1 or XXX.XXX.XXX.0 .

WiFi Access Point

Setting the connector up to be a WiFi access point is useful for two reasons.

Firstly, it allows you to connect to it, allowing for easy wireless access to its configuration page. Secondly, if this connector has internet access via ethernet, it can act as an internet enabled hotspot to connect WiFi device to, in-turn giving them internet access.

If the WiFi access point is enabled, a WiFi SSID and Password must be set. It is recommended the default SSID is used (This matches the the connectors Serial Number)

Saving Changes

To save the changes click the save button. If there are an issues with the configuration, such as an invalid input in one of the fields, the form will show this and the changes will not be saved. If the settings were saved correctly, a pop up will show this after the save button has been clicked.

Configure MQTT

Overview

Connectors use MQTT to communicate with MobiusFlow. As such, the Configure MQTT page allows the connector to be pointed at a specific MQTT broker. In almost all cases, the broker will be running the MobiusFlow instance itself.

Configuration Window

The configuration window shows the key 6 properties which must configured to allow an authorised connection to the MQTT broker.

Explanation of Properties

Saving Changes

To save the changes click the save button. If there are an issue with the configuration, such as an invalid input in one of the fields, the form will show this and the changes will not be saved. If the settings were saved correctly, a pop up will show this after the save button has been clicked.

Realising Changes

Once the changes have been made locally, to implement the changes within the connector, click the Reconfigure and Reboot button.

This will cause the connector to reboot. As such, the configuration window's connection to the connector will be lost. This may automatically be restored once the connector reboots, but this may not be the case if the connector's configuration has changed such that it is no longer accessible over the network.

The Config Mode Password is used to login to the configuration pages of the connector. The default password is mobiusflow

You can change the password on this page

Save Settings

Click the Save button

Click the Home button on the settings saved confirmation page to return to the Home page

Technologies Referenced

This section outlines the major technologies reference in this training. Learning about this technologies is recommended.

MQTT

MQTT (Message Queuing Telemetry Transport) is a lightweight and efficient publish-subscribe messaging protocol, commonly used in IoT (Internet of Things) applications.

MQTT is widely used for data transport throughout the MobiusFlow software.

JSON

JSON (JavaScript Object Notation) is a lightweight data interchange format that is easy for humans to read and write, and easy for machines to parse and generate.

A basic knowledge of JSON is required when using the Flows (logic engine) within MobiusFlow.

EnOcean

EnOcean is a short distance wireless communication protocol used widely within the IoT space. Each EnOcean device has a unique identifier (UID) which is used to identify the sender of all EnOcean wireless telegrams.

During this training, EnOcean will be used as an exemplar IoT technology to demonstrate MobiusFlow from the device level.

MobiusFlow Overview

Structure

A MobiusFlow instance runs a central MobiusFlow Hub. Services, each of which have a function within the overall solution, reside on the hub, and use it as a relay to communicate information.

A MobiusFlow object often represents a virtual equivalent of a real-world device, however can represent non-physical entities such as calculated data.

Some services can have MobiusFlow objects reside on them, often when the service needs to directly interact with those objects in some way. For example, objects representing EnOcean devices will always reside on an EnOcean devices service.

Points / Resources

A MobiusFlow object contains many resources, each being its own individual data stream representing something about that object.

Below shows a screenshot from the MobiusFlow software of the list of resources associated to an EnOcean Temperature / Humidity / C02 sensor.

A point is a chargeable resource. Notice in the above screenshot, the points column is only populated for Temperature, Humidity and CO2.

Also notice how the MobiusFlow software calculates your total point usage and displays this at the bottom right hand corner.

URIs

All parts of the MobiusFlow hierarchy are assigned a unique URI with the following structure:

HID/SID/PID/INS/RID

Example URIs

Service

Full example URI of a service:

000001/020

Representing service 020 on hub 000001.

Object

Full example URI of an object:

000001/020/0028/0001

Representing instance 0001 of object type (profile) 0028 on service 020 on hub 000001.

Resource

Full example URI of a resource:

000001/020/0028/0001/40

Representing resource 40 on instance 0001 of object type (profile) 0028 on service 020 on hub 000001.

Conclusion

Using the URI system, it is therefore possible to reference any component of a given MobiusFlow configuration.

Configuration Example

Example Overview

This aims to show how data taken from EnOcean sensors at a hardware level, is brought into and through the MobiusFlow system, and then presented in the form of a dashboard.

Project Schematic

The following shows a colorless project schematic representing lack of implementation. As the project is implemented, this diagram will be colored in so progress can easily shown.

Explanation of Services

MobiusFlow Configuration

MQTT Broker

Add and start MQTT Broker service:

Connector Service

Add connectors service, add a connector to the service, and finally start the service.

Add and start service:

Add a MobiusFlow connector object to the connectors service and configure:

EnOcean Devices Service

Add EnOcean Devices service, add EnOcean device objects to the service, and finally start the service.

Connecting Hardware

Service Status and Data

The status of all service can viewed. This is a helpful insight into the current state of the solution as well as aiding with diagnostics.

The data of any live object can viewed by navigating to that object and then clicking on resources.

Flows

Dashboard

In this example, the live state of the buttons on a 4-Rocker EnOcean switch is shown on a basic dashboard.

The MobiusFlow software has been developed as an MQTT object bus which normalises all device data into standardised MobiusFlow objects which allow interoperability between all devices either real or virtual in the field or Cloud.

MobiusFlow enables actuators, sensors & controllers to connect, control and communicate with each other and to the Cloud so that IoT solutions using scalable monitoring, visualisation and predictive analytics can provide valuable insights into your business and act upon them automatically.

• A complete control and communications platform

• Microservice based architecture

• Secure, open protocol based on MQTT

• Scalable to 1000s of devices

• Platform and language independent

• Does not depend on a network connection for local control

• Provides full discovery of nodes, objects and resources in all directions

• Pub / Sub change of value notifications

MobiusFlow has been designed from the ground up as a micro service based design with a simple but common set of API commands. All communication between micro services is performed using the MQTT protocol, ensuring that micro services can be written in any programming language and will run on any device capable of TCP/IP network communications. The only requirement for any MobiusFlow system is that it contains at least one Node. This Node consists of a MobiusFlow Hub which initiates and facilitates communication between micro services in a secure way. Micro services can run on the same device as the Hub, or on another device such as a temperature sensor, connected to the Hub via a connection capable of transmitting via TCP/IP (provision has been made for future expansion, by adding translation services, to allow micro services to communicate with the Hub over any transmission medium capable to transmitting binary data).

Each Node is typically a stand-alone island which does not require any connection to any other device in order to perform local control. Nodes can be connected together via secure MobiusFlow Routers allowing the creation of a network of interconnected Nodes. When used in this configuration, Nodes can share data with each other and influence the control algorithms running on any connected Node.

Vanilla MQTT has some limitations in its usefulness as a peer to peer messaging and control protocol. It is based around the Publish / Subscribe pattern which is ideal where multiple devices are sending data to a single end point for logging etc. MQTT can be used where devices or services need to have a two way peer to peer flow of communication but the different services need to be aware of each other at design time. MobiusFlow defines a protocol layer above MQTT which enables discovery of devices and services at runtime and then allows two way peer to peer communication to take place, ensuring that new devices and services can be added at any time without having any design time knowledge of the other devices and services in a system.

MobiusFlow with LoRaWAN Stack

Port Mappings (Simple)

The table below shows a simple overview illustrating how the ports are mapped. This is a simple overview suitable for most users.

Port Mappings (Advance)

Docker & Docker Routing

Different parts of the MobiusFlow solution run in different docker containers. These communicate via docker routing. Docker routing allows container names to be resolved in the Host OS, for example, to refer to the Mobius Engine API from the Host OS or a container that is not the mobius container, one could use mobius:8442 (container name followed by Host OS Port).

This means that, if communication between containers is required, the Host OS port and container is required. As such, these are included in the advanced port mappings table below.

Full Mappings

The table below gives a full description of the port mappings a MobiusFlow Cloud hosted environment is subject to.

Mobius system

A typical MobiusFlow system consists of a single or multiple MobiusFlow nodes connected together via a TCP/IP network. Each node is capable of operating independently of the rest of the system, but nodes can interact with each other to form a complex system. All node interaction takes place through one or more brokers via a node’s router.In a multi-node system, the location of the broker is not important. It can reside on the same device as one of the nodes or on an independent device.

Mobius nodes

A Mobius node consists of a central Mobius hub, one or more Mobius services and optionally one or more Mobius routers.

Services contain the service logic and an object data store. Connections to sensors, actuators and other communication interfaces such as Modbus or BACnet can be added depending on the service’s purpose and controlled through the service's logic.

The object data store models the physical or virtual connections and provides a standardised method for services and other nodes to communicate and share data with each other through Mobius objects.

Routers are used to cross node boundaries. They provide a secure mechanism for nodes to share data using the MobiusFlow protocol.

Logical structure of a node

The logical structure of a node is detailed below. This diagram shows the hierarchical relationship between all of the parts which make up a node and how objects contain resources, services contain objects and hubs connect to services and routers.

The Mobius URI structure allows addressing any part of a node at any depth.

Hubs

A Mobius hub is the foundation of a node. At its heart, a Mobius hub is just an MQTT broker which manages and links Mobius services and Mobius routers. Hubs are responsible for ensuring that all services and routers are valid members of a node by verifying their pre-shared authentication key on connection.

When service or router connects to a hub, and has been validated, the hub provides it with a copy of the Mobius object profiles and pre-shared keys files, ensuring that all services and routers connected to the hub are able to communicate and understand one another.

Services

Mobius services are the engines which drive MobiusFlow. Each service is essentially a microservice performing a specific task and possibly acting as an interface to a piece of hardware or a 3rd party service such as Microsoft's Azure platform or the IBM Cloud.

All services MUST implement the full MobiusFlow protocol to enable them to connect to hub and communicate with other services. In addition to implementing the MobiusFlow protocol, services can create Mobius objects to store and share data and can also contain service specific logic to perform the task that they are designed for. When creating services, try an keep them focused on one task and create additional services to perform other tasks. This ensures that services are reusable and Mobius systems can be configured to only contain the logic that they require.

Routers

Mobius routers control all MobiusFlow communication into and out of a node. This ensures that nodes are secure and allows nodes to discover each other within a MobiusFlow system.

Routers are capable of routing messages between services belonging to different nodes, essentially allowing a service on one node to read, write and subscribe to change-of-value events on objects in another node.

Mobius objects

Mobius objects are predefined in an object profiles file which is passed to a services by the hub when a service connects.

Object resources

Mobius objects contain one or more resources. It is these resources which are used to define objects that mimic or represent real-world objects. An example of a single object is a room temperature sensor. This object may have resources which define the sensor’s name, location, asset reference, engineering units, set point and actual measured value.

Each resource is capable of storing a single value which can currently be of type Boolean, Number, String, DateTime or TimeSpan. Resources also store meta-data about the value. The actual meta-data depends on the value type chosen. Resources can be read only or read/write. Read only resources have their values set when they are created.

Present value and the priority array

When reading the value of a resource the actual value is returned in the PV(present value) property. The PV is always equal to the value of the highest active (non null) priority in the resource's priority array.

Within a MobiusFlow system all hubs, services, objects and resources are identified by a unique address known as a Uniform Resource Identifier or URI. These URIs are hierarchical so given the URI for a Mobius resource it is possible to identify which object the resource belongs to, what the object type is, which service the object belongs to and which Mobius node the service is running on.

Mobius URI Definition

An object’s URI (or name) is defined in 4 parts, namely the hub ID (HID), service ID (SID), object profile ID (PID) and instance number (INS). A fifth part is added when accessing a specific resource, the resource ID (RID).

A full URI is typically defined as HID/SID/PID/INS/RID.

It is possible to address any part of the system by only using the required parts of the URI. e.g. to address a service only the first two parts of the URI are used HID/SID and to address an object only the first four parts are used HID/SID/PID/INS.

An example of an object URI for an object of instance 1, profile 3A, created by service 1F connected to hub 1 is:

000001/01F/003A/0001

and if addressing resource 40 on that object the full URI would be:

000001/01F/003A/0001/40

Mobius URI Wildcards

Under certain conditions, such as subscribing to a resource’s change of value event, it is possible to use wildcards in the URI. These wildcards are described in the table below and follow the MQTT standard.

The ports in used by Mobius Gateways. These are for services that can be hosted on the Gateway.

The physical gateways fleet management and remote connectivity service require outbound access to these services

The discover calls are used to learn about the present state of a given MobiusFlow instance

The authorization controller is used to login to the API, in addition user management.

When a login call is completed, the API will return a bearer token which should be used in the auth header of all future calls. This token is set to expire 10 minutes after its generation.

A refresh token is also included in the login response, and this is used in the body of the refresh call to get new tokens with refreshed expiry times. Ensure a refresh call is made prior to any given bearer token's expiry to avoid having to login again.

Introduction

Node Internal Communication

With Each node consisting of the base of a hub and one or more services, and optionally routers. If for the purpose of this initial discussion assume that the services are only communicating with local hardware, or handling logic, therefore having no mechanism for communicating off of the local hardware. We will discuss how this can be achieved later on.

Service Authentication

If the service signs its JWT with the same psk as is stored in the hub's psk file it will successfully complete the authentication process to the hub. On doing this it will be sent a copy of the hubs psk file, giving the service the ability to the received directly signed messages from authorised services.

After successful authentication the service will have a copy of the psk of all services that are authorised to communicate through the hub. The service will then with no further action from the hub be able to validate the authenticity and integrity of messages that have come from a service on the same node.

Service Communication

Once passing traffic the MQTT message will consist of:

The time stamp will allow for the message to have a validity life span that can be configured for all services connected to the hub. Internally all messages will be signed in this way and therefore provide a high degree of integrity to the internal communication.

Services may be intentionally created to connect to external interfaces such as a service the connects to remote I/O via TCP/IP or an Azure IoT hub Client, if it is desired to configure a node in this scenario, it is recommended to utilise two interconnected nodes one that handles the external communications and one that handles the more trusted internal communication, the nodes could exist on the same hardware. doing so would allow the creation of multiple trust boundaries

Node External Communication

The internal side of the router acts in exactly the same way as a service, but will automatically subscribe to all messages from every other service within that node.

The external side of the router will have the ability to sign its messages in the same fashion as the services do for internal communication, it will have two pre shared keys and internal or service psk and an external psk.

Node Peering

To allow router to validate the authenticity and integrity of messages form other routers, the external psks will be required to be manually shared between all the routers that want to take part in this communication. the result is that the external psk file will contain the keys of all authorised routers and therefore nodes.

This communication is done over the WebSocket protocol as it reduces the need to configure firewalls to allow MQTT communication. node peering is best used in an enclosed environment where there is a high degree of confidence in the integrity of the network with which the communication is taking place. This is like to require the input of network and cyber security professionals.

Larger Node Deployments

In larger deployments of nodes peering may not be viable because of the administrative overhead, or there may be low confidence in the network integrity. there may also be a require to not only ensure Authenticity and Integrity of messages, but also confidentiality.

In this case it will almost always be easier to provide the node with access to the public internet where things like server name resolution and certificate control are well practised and understood.

Due to the large complexity in provisioning the system in this scenario, It is envisaged at this stage that IAconnects will provide the service that provides the functions of the architecture shown above.

The MobiusFlow Engine API is used interface with MobiusFlow via http and https. The API allows clients to perform all functions within MobiusFlow, from managing user accounts, to getting and setting data, as well as manipulating the MobiusFlow configuration by adding, removing and editing MobiusFlow objects, services and flows.

Controllers

Protocols, Endpoints and Ports

If connecting to a local instance of MobiusFlow, the http protocol can be used. If connecting to an instance of MobiusFlow via the internet, https should be used. The API is always exposed on port 8443.

All endpoints lead with:

{{protocol}}://{{hostname}}:8443/api/v1

Where the protocol and hostname parameters are replaced with the true protocol and hostname. For example, in the case of connecting to a local instance of MobiusFlow, the leading path would look like:

http://localhost:8443/api/v1

Further Documentation & Postman Collection

The object calls are used to read, add, remove and manipulate MobiusFlow objects and resources.

The service calls are used to read, add, remove and manipulate MobiusFlow services.

The node calls are for reading a MobiusFlow hub as well as resetting the pre-shared keys on a given hub

Backup

Full functionality of Subscription Websocket is described in the connect call below.

Used get and set the full configuration the flows.

You can use the backup and restore feature to backup the full configuration of a MobiusFlow instance, and to restore the configuration of a MobiusFlow instance to a previously saved backup.

Overview

In summary, all configuration data of a MobiusFlow instance can be stored within a single .zip file. This means the current configuration of any MobiusFlow instance can be backed up by simply downloading this backup file and saving it in a safe location of your choice. Similarly, the configuration of any MobiusFlow instance can restored by uploading one of your previously saved backup files.

All backup and restore functionality is accessed through the 'Backup/Restore' menu located on the 'Administration' Tab.

Backup

On the 'Backup/Restore' menu, you can create a backup by clicking 'Backup'.

Once the backup file has been created, click 'Download Zip' to download it.

Alternatively, the you can click 'Request new backup' to return to the previous menu and generate an updated backup file.

Be sure to save your backup file in a safe location! There is nothing worse than not being able to find a much needed backup file.

Restore

The restore feature is particularly useful if you want to copy a MobiusFlow configuration onto to other MobiusFlow instances, however it also useful if you've managed to break everything.

The 'Backup/Restore' menu is also used for restoring. You can restore by first clicking 'Upload Zip' and then browsing to the .zip backup file you previously saved in a safe place.

Once uploaded, the menu will show the backup information as well as allowing you to click 'Restore'.

Accept the a confirmation dialog to proceed.

You will be notified that the restoration process has started and then MobiusFlow will then reboot, completing the restore process.

Congratulations for completing your restore!

Overview

The MobiusFlow INGY integration implements the following features:

• Changing lighting level set points of group scenes

• Switching between lighting scenes of a given group

• Adding / removing devices from groups

• Acquisition of data from INGY devices

• Direct interfacing with INGY API and Datastream

This article explains how to use the INGY service to achieve all of the above.

Connecting to INGY Gateway

To interface with an INGY system, an INGY gateway must be present on the project site. These INGY gateways can be acquired directly from INGY.

MQTT

The INGY gateway host's and MQTT broker, and as such, MobiusFlow uses an MQTT connection to this broker to allow two-way communication between MobiusFlow and INGY.

INGY gateways create 3 MQTT users, each with different sets of permissions. MobiusFlow requires usage of the datastream and MQTT JSON server (API) users. These user credentials can be found in the Gateway MQTT server section of the INGY gateway configuration page.

Network Requirements

Ensure the INGY gateway is accessible by MobiusFlow over an on-site (or otherwise) network. As it is likely the local IP address of the INGY gateway will be directly referenced within MobiusFlow, it is recommended that this should be set up on the network with a static local IP address. This means the connection will not break due to DHCP reassignment.

INGY Service Settings / Requirements

Once the INGY service has been added, the following configuration window is shown:

The following fields must be populated to allow MobiusFlow the connect the INGY gateway.

Checking connection

The INGY service will attempt to connect via MQTT to the INGY gateway when the service is started. As such, to test the connection, start the service and observe the service status:

Lighting Control

Lighting control is exclusively performed by commanding lighting groups to change to different scenes.

For every INGY lighting group, add an ingy_group (PID 028A) MobiusFlow object to represent the group within MobiusFlow. The group number of the INGY group can be set in the object settings.

Viewing the resources on an INGY group object shows:

Groups pre-configured using INGY App

If using a group the has been pre-configured using the INGY App, ensure the group number is MobiusFlow is set equal to the group number of the group previously created in the INGY App.

If a group with a matching group number has been set up within the INGY App, MobiusFlow will automatically pull (given some time) the sceneSetLevel values of any scenes which have already been set up using the app.

The scene number matches the display order shown in the INGY App. As such, the first scene shown in the list on the INGY App is scene 0, the second is scene 1, the third is scene 2, and so on.

Scene Settings

Each lighting group supports 8 different scenes (numbered 0 - 7). These may have been previously set up using the INGY app. MobiusFlow will automatically query the level set point of each scene and will display this in the corresponding knownLevel resource. MobiusFlow can also be used to change each scene's level set point (0% - 100%) by setting that scene's corresponding setLevel resource.

It may be possible that the real-world scene setting levels or MobiusFlow have become out of synchronous. This could have been caused if they were changed by something that was not MobiusFlow, such the INGY app or INGY API. To ensure the real-world scene level settings do match the settings within MobiusFlow, set the resendSetLevelCommands (RID 83) to true. Note that MobiusFlow will immediately reset this back to false, whilst also resending the command to set the scene level settings of all scenes.

Changing Scene

MobiusFlow automatically queries which scene is currently being exhibited by the group, and shows this information in the knownScene resource.

Changing the currently exhibited scene on a given group is done in two steps:

1. Set the sceneSetting resource to scene number of the desired scene (if the resource currently shows the desired scene, this step can be skipped)

2. Set the send trigger to true (the service will automatically set this back to false immediately afterwards). This will cause MobiusFlow to command the INGY group to change to the desired scene.

Alternatively, these steps can be handled in one by using the INGY Set Scene flows node.

When configured, this node is pointed at an INGY group object, and will receive an input payload (0 - 7) representing the desired scene number. The node automatically handles the resource changes to cause the group to change scene.

Devices and Querying

MobiusFlow objects can added to represent real-world INGY devices. These objects are used to query and encapsulate the data coming from these devices in addition to control which group a given device is a member of.

Searching ingy in the objects library will display the list of options of MobiusFlow objects that can represent the real-world INGY devices.

Add these options in the correct quantities to represent the INGY devices within MobiusFlow.

Every INGY object type will require the entry of the INGY node address (wirepas address) as well some other information:

If knowing the current lighting level of any lighting device is required, ensure Auto Query Level is checked to ensure MobiusFlow automatically pulls current level data from this device.

INGY Partition

Some INGY nodes can be partitioned to act as separate controllable devices. Represent these partitions using multiple MobiusFlow objects with the same Node Address but different partition numbers. If the INGY node has not been partitioned, the partition number should be set to the default of 0.

Grouping

The known group membership of all devices is automatically queried by MobiusFlow and this data is stored into knownGroupMembership resource.

The group membership of a given device can be changed by setting the setGroup resource. The knownGroupMembership resource should reflect this change after a period of time.

Sometimes it may be required that the command to group a given INGY device needs to be re-sent. This often can occur if the device is offline when the original setGroup command is sent. In this situation, set the sendRegroup resource to true. Note that, MobiusFlow will immediately set this resource back to false whilst sending the regroup command.

Data

MobiusFlow will automatically pull all possible data from the known INGY nodes into corresponding MobiusFlow objects.

Direct interfacing with INGY API

Two flow nodes have been written to aid direct interfacing with the INGY API.

INGY Spy Node

The INGY Spy node is used to view all the Datastream and API messages coming from INGY gateway. This includes data sent out over the INGY gateway's datastream as well as directly viewing all API commands and responses.

The INGY spy node can be aimed to a given MobiusFlow INGY service within it's config, and set up with debug nodes as shown above. The two outputs map to the datastream and api respectively.

INGY Send API Command Node

The INGY send raw command node is used to send direct API command to the INGY API.

The node must be aimed at a specific MobiusFlow INGY service within the node's configuration.

The node takes input messages who's payload must be formatted to be a valid INGY API command as shown in the INGY API documentation. The response to this command will be outputted from the nodes output.

It is recommended a function is used to set the command body as shown in the example flow below:

In the above example the code in the function node is a as follows:

Switches and Rocker Profiles (F6-XX-XX)

• F6-02-XX: Standardized rocker switch functionality, perfect for wireless and battery-free light switches.

• F6-01-01: Classic single rocker switch for versatile applications.

• F6-05-01 & F6-05-02: Advanced switches supporting multi-rocker configurations.

• F6-04-01: Specialised profile for unique switch requirements.

Temperature and Humidity Sensors (A5-XX-XX)

• A5-02-01 to A5-02-20: Comprehensive profiles for temperature and humidity sensing across varied ranges and resolutions.

• A5-04-01 to A5-04-03: Focused on precise temperature monitoring for HVAC and building automation.

• A5-06-02: Compact profile for humidity measurement.

• A5-07-01 to A5-07-03: Temperature and humidity combined for indoor climate monitoring.

• A5-08-01 & A5-08-08: Advanced temperature sensors for outdoor and industrial use.

Light and Occupancy Sensors

• A5-09-04 & A5-09-02: Profiles for daylight harvesting and light level monitoring.

• A5-10-03, A5-10-06, A5-10-12, A5-10-19: Advanced occupancy and motion detection sensors.

• A5-11-01 & A5-11-02: Multi-functional sensors for light, motion, and temperature.

Energy and Utility Monitoring

• A5-12-01 to A5-12-03: Profiles tailored for energy consumption and utility monitoring.

• A5-14-58 & A5-14-05: Energy efficiency sensors for load and power monitoring.

• A5-20-01: Compact profile for energy harvesting applications.

People Counting and Building Analytics

• IMBUILDINGS PEOPLE COUNTER: A specialised profile for tracking occupancy and people flow in smart buildings.

• D1-03-C1, D1-03-C2, D1-03-C0: Advanced profiles for presence detection and people counting.

Advanced Actuator and HVAC Controls

• D2-32-00 to D2-32-02: Actuator profiles for heating, ventilation, and air conditioning systems.

• D2-14-5C, D2-14-40 to D2-14-53: Comprehensive profiles for valve and motorised actuator control.

• D2-03-OA: Specialised actuator profile for unique applications.

Miscellaneous Profiles

• D2-05-00: General-purpose profile for binary data transmission.

• D2-01-0A to D2-01-12: Profiles for advanced control systems.

• D2-15-00: Versatile profile for industrial applications.

Specialised Devices

• ECHOFLEX MOS MT: Tailored profile for motion sensing in smart building environments.

Why Use MobiusFlow for EnOcean EEPs?

MobiusFlow provides a powerful and flexible platform for integrating EnOcean devices. Its library’s support for a wide range of EEPs ensures compatibility with various devices and applications, making it ideal for:

• Smart Building Automation: Efficiently manage lighting, HVAC, and energy systems.

• Industrial Automation: Enhance operational efficiency with precision monitoring and control.

• Energy Efficiency: Monitor and reduce energy consumption with advanced sensors.

By leveraging MobiusFlow’s extensive EEP library, businesses can create scalable, efficient, and energy-saving IoT solutions tailored to their needs. Whether you’re looking to optimise a single building or manage a global network of properties, MobiusFlow and its EnOcean integration make it possible.

Overview

You can add the LoRaWAN LNS Service (labelled as lorawan local network server) to the MobiusFlow from the service library.

The service requires the region to be set. If mulitple regions are required, using muliple LoRaWAN LNS services is neccessary.

Integrated Device Types

If a device is integrated, MobiusFlow will atomically handle the decoding of device data and the movement of this data into corresponding MobiusFlow objects (Uplink). Some devices also support downlink, i.e. sending data from MobiusFlow to the device. For integrated device types, if there is a public downlink encoder available, MobiusFlow will automatically handle the encoding and sending of data to devices of that type.

List of Integrated Device Types

The list will be populated soon. Please contact support for enquires about specific devices.

Unintegrated Device Types

All LoRaWAN devices intend to be integrated in future. To request integration of a new device type, please contact MobiusFlow support at info@mobiusflow.com.

Supported Regions

Currently supported regions are shown in the following list:

• EU868

• US915_0

• US915_1

Support for all regions is planned for the near future. To request support for a specific region, please contact MobiusFlow support at info@mobiusflow.com.

Connecting a LoRaWAN Gateway to MobiusFlow

Adding the Gateway to MobiusFlow

LoRaWAN gateways are added as MobiusFlow objects to the LoRaWAN LNS service. When viewing the configuration of LoRaWAN LNS service, search for lorawan_gateway in the object library. A lorawan_gateway object (PID 028D) should be added for each physical LoRaWAN gateway MobiusFlow will connect to.

For each lorawan_gateway object, the 16 character (Hex) Gateway ID must be populated to match that of the ID of the physical LoRaWAN gateway. Ensure the object settings are saved. As with all MobiusFlow services, a stop/start cycle or hot reload must be performed if any settings are changed or objects are added or removed.

Setting up the Connection on the Gateway

Ensure the MobiusFlow is accessible by the LoRaWAN gateway, i.e. if MobiusFlow is running in the cloud, ensure the gateway has an internet connection. Alternatively, if MobiusFlow is running on-prem, ensure the LoRaWAN gateway has access to it over the local network.

The connection between LoRaWAN gateway and MobiusFlow uses Semtech UDP. Set up a Semtech UDP packet forwarder on each gateway with the following paramaters.

Hostname

Use the standard TCP/IP hostname of the gateway. If the gateway is running in the cloud and hosted by MobiusFlow, it will be in the form xxx.mobiusflow.io e.g. grand-eagle-11.mobiusflow.io. If MobiusFlow is being hosted on-prem or elsewhere, use the IP address of the host or DNS designation of the host. Do not include any protocol or a port in the hostname.

Port Number

The Semtech UDP packet forwarded allows both an inbound and outbound port to be specified in the configuration. Ensure the same port number is used for both inbound and outbound.

The exact port number depends on which region the gateway is operating in. See the table below for all port numbers by region.

Opening of Network Ports

Ensure the required ports are open on the gateway's network. Also ensure the required ports are open on the network where MobiusFlow is running. If the instance of MobiusFlow is hosted in the MobiusFlow cloud, the ports for all region types will be open by default.

Connecting a LoRaWAN Device

To add a device, when inside the LoRaWAN LNS Service's configuration, search for that device type in the objects library and add instance of it.

For each new object, the Device EUI and Device App Key (OTAA Key) must be populate to match that of the device.

Ensure the settings are saved. As with all MobiusFlow services, a stop/start cycle or hot reload must be performed if any settings are changed or objects are added or removed.

If the credentials are set correctly, the device is in range of the LoRaWAN gateway, and the LoRaWAN gateway is connected to MobiusFlow, live decoded data from the device will now appear within the new object's resources.

Downlink (Sending commands to a device)

The flows can be used to enqueue downlink messages to some device types. MobiusFlow is packaged with a set of MobiusFlow/LoRaWAN specific nodes designed to work with the LoRaWAN LNS service.

LoRaWAN Send Downlink Node

To enqueue downlink messages to device types that have been integrated with MobiusFlow, use the lorawan send downlink node type shown below.

This node will accept into its input an incoming unencoded payload as per how the manufacture's downlink encoder accepts the messages.

Inside the node's configuration allows specification of which device the downlink messages will be enqueued on. This is done by specifying the device's MobiusFlow URI which can either be pasted in or searched for.

The node's output will send messages informing the user of the result of the attempted downlink enqueue action.

Results include a success, a failure due to an incorrectly structured input payload (included in the error message is information regarding the correct payload structure), or failure due to this device type not supporting downlink all together.

Checking Enqueued Messages

The number of currently enqueued messages can be found for each device by viewing resource 21 of that object representing that device.

Example Flow

The following example uses an inject input to trigger the inital message. Then a function node formats to message's payload into the correct format for the device type. The lorawan send downlink node has been set to connect to a specific MobiusFlow object. The debug is used to monitor the output of the lorawan send downlink node so the user is informed if the action was a success or failure.

The contents of the function node using to format the payload is follows:

// this is an example
msg.payload = {
    config1: 0,
    config2: 3,
    mode: 'normal',
    action: 'open'
}
return msg;

Raw Downlink

For some device types, manufactures do not release downlink encoders, and as such it is not possible to integrate this functionality into MobiusFlow. It is however possible to write your own in the flows and then send this via the LoRaWAN LNS service to be enqueued directly to a LoRaWAN device. This is done using same basic flow as regular downlink however using the lorawan send raw node.

The lorawan send raw node bypasses helpers and checks provided by MobiusFlow objects. As such, the node's configuration requires the specification of a LoRaWAN device EUI instead of a MobiusFlow object's URI.

The node does not have an output. This is because it uses a 'fire-and-forget' style mechanism and therefore cannot monitor if the enqueue action was successful or not.

The message payload must be built inside the function node. The result of this encoding must be an object containing the required LoRaWAN fPort as well the data property. This data property contains the raw data that will be enqueued (hex bytes in string).

The contents of the above example function node are shown below.

// ensure payload contains fPort and data (hex bytes in string format)
msg.payload = {
    fPort: 0,
    data: '0C1A01230024',
    confirmed: true
}
return msg;

Using Unintegrated Device Types

For unintegrated device types, that is device types that MobiusFlow does not feature inbuilt uplink decoders, downlink encoders and shaped MobiusFlow objects, the lorawan_generic_device object type can be used.

As with all LoRaWAN object, the device EUI and App Key must be set to match of the LoRaWAN device.

Uplink

To the object's configuration is set with the correct device EUI and App Key, data will be pulled into the MobiusFlow object as with all other LoRaWAN object types. Unlike these object types, the data will not be decoded and left a raw string in resource 40. The data can then be handled / post-processed by the user in the flows at will.

Downlink

Downlink is handled in the same manner as for integrated device types. If using the lorawan_send_downlink node, for the lorawan_generic_device object type, no checks are made regarding the format of the payload. As such, ensure the message is pre-encoded into an object containing the fPort and data (hex bytes as string) properties.

The lorawan_send_raw node can also be used as before, to enqueue downlink message to unintegrated device types.

LNS Backend (Chirpstack)

The MobiusFlow LNS Service uses Chirpstack V4 as an LNS backend. As such, for debugging purposes it is possible to log into this backend if required. Chirpstack runs on port 8081, to browse to this port to access chirpstack.

Every MobiusFlow LNS Service contains a statistics object. This includes some information about the health of the LNS as well as the chirpstack login credentials.

Understanding the following articles is recommended before reading this article:

This article includes information on the following nodes:

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:

{"pid":"0028","ins":"0002","profileName":"enocean_A5-09-04","description":"EnOcean temperature, humidity and CO2 sensor","resources":{"40":{"rid":"40","type":"number","pv":19.2,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,19.2,0],"name":"temperature","settings":{"access":"r","min":0,"max":51,"precision":1,"units":"C"},"config":{"access":"r","min":0,"max":51,"precision":1,"units":"C"}},"41":{"rid":"41","type":"number","pv":54.5,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,54.5,0],"name":"humidity","settings":{"access":"r","min":0,"max":100,"precision":1,"units":"%"},"config":{"access":"r","min":0,"max":100,"precision":1,"units":"%"}},"42":{"rid":"42","type":"number","pv":2550,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,2550,0],"name":"co2","settings":{"access":"r","min":0,"max":2550,"precision":0,"units":"ppm"},"config":{"access":"r","min":0,"max":2550,"precision":0,"units":"ppm"}},"43":{"rid":"43","type":"bool","pv":false,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,false,false],"name":"hasTemperatureSensor","settings":{"access":"r"},"config":{"access":"r"}},"44":{"rid":"44","type":"bool","pv":false,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,false,false],"name":"hasHumiditySensor","settings":{"access":"r"},"config":{"access":"r"}},"00":{"rid":"00","type":"string","pv":"","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"",""],"name":"parentObject","settings":{"access":"rw","tags":{"attribute":"true"}},"config":{"access":"rw","tags":{"attribute":"true"}}},"01":{"rid":"01","type":"string","pv":"Air Quality Sensor 2","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"Air Quality Sensor 2",""],"name":"name","settings":{"access":"r","tags":{"attribute":"true"}},"config":{"access":"r","tags":{"attribute":"true"},"pv":"Air Quality Sensor 2"}},"02":{"rid":"02","type":"datetime","pv":"2024-12-10T19:12:47.430Z","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"2024-12-10T19:12:47.430Z","1970-01-01T00:00:00.000Z"],"name":"objectLastUpdated","settings":{"access":"r"},"config":{"access":"r"}},"03":{"rid":"03","type":"string","pv":"Air Quality Sensor","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"Air Quality Sensor",""],"name":"description","settings":{"access":"r","tags":{"attribute":"true"}},"config":{"access":"r","tags":{"attribute":"true"},"pv":"Air Quality Sensor"}},"04":{"rid":"04","type":"string","pv":"MobiusFlow Studio Henley","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"MobiusFlow Studio Henley",""],"name":"location","settings":{"access":"r","tags":{"attribute":"true"}},"config":{"access":"r","tags":{"attribute":"true"},"pv":"MobiusFlow Studio Henley"}},"0A":{"rid":"0A","type":"string","pv":"A5-09-04","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"A5-09-04",""],"name":"eep","settings":{"access":"r","tags":{"attribute":"true"}},"config":{"access":"r","pv":"A5-09-04","tags":{"attribute":"true"}}},"0B":{"rid":"0B","type":"string","pv":"01879DE6","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"01879DE6",""],"name":"uid","settings":{"access":"r","maxlen":8,"tags":{"attribute":"true"}},"config":{"access":"r","maxlen":8,"tags":{"attribute":"true"},"pv":"01879DE6"}},"0C":{"rid":"0C","type":"number","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"name":"status","settings":{"access":"r"},"config":{"access":"r"}},"0D":{"rid":"0D","type":"number","pv":-77,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,-77,0],"name":"dBm","settings":{"access":"r","units":"dBm"},"config":{"access":"r","units":"dBm"}},"0E":{"rid":"0E","type":"bool","pv":true,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,true,false],"name":"lrn","settings":{"access":"r"},"config":{"access":"r"}}},"families":["EnOcean","CO2Sensor","HumiditySensor","TemperatureSensor"],"timestamp":"2024-12-10T19:12:47.431Z","changed":["02"]}

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:

[{"pid":"FFC0","ins":"0001","profileName":"mobiusFlowConnector","description":"","resources":[{"rid":"00","type":"string","name":"parentObject","pv":"","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"",""],"settings":{"access":"rw","tags":{"attribute":"true"}}},{"rid":"01","type":"string","name":"name","pv":"Elliot's Connector","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"Elliot's Connector",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"02","type":"datetime","name":"objectLastUpdated","pv":"2024-12-11T17:07:49.628Z","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"2024-12-11T17:07:49.628Z","1970-01-01T00:00:00.000Z"],"settings":{"access":"r"}},{"rid":"03","type":"string","name":"description","pv":"EnOcean + WorkOcc connector for Elliot's house","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"EnOcean + WorkOcc connector for Elliot's house",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"04","type":"string","name":"location","pv":"Elliot's desk","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"Elliot's desk",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"0A","type":"string","name":"partNumber","pv":"EXT00112","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"EXT00112",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"0B","type":"string","name":"serialNumber","pv":"MF_00BCC0","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"MF_00BCC0",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"0C","type":"string","name":"psk","pv":"elliotConnector","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"elliotConnector",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"0D","type":"string","name":"firmwareVersion","pv":"3.2.1","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"3.2.1",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"0E","type":"string","name":"module1Type","pv":"WorkOcc","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"WorkOcc",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"0F","type":"string","name":"module2Type","pv":"EnOcean","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"EnOcean",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"10","type":"string","name":"enOceanChipID","pv":"FFC23F80","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"FFC23F80",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"11","type":"string","name":"macAddress","pv":"24:0A:C4:8A:C0:BF","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"24:0A:C4:8A:C0:BF",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"12","type":"string","name":"ipAddress","pv":"192.168.0.88","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"192.168.0.88",""],"settings":{"access":"r"}},{"rid":"13","type":"string","name":"subnetMask","pv":"255.255.255.0","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"255.255.255.0",""],"settings":{"access":"r"}},{"rid":"14","type":"string","name":"dnsAddress","pv":"194.168.4.100","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"194.168.4.100",""],"settings":{"access":"r"}},{"rid":"15","type":"string","name":"defaultGateway","pv":"192.168.0.1","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"192.168.0.1",""],"settings":{"access":"r"}},{"rid":"16","type":"string","name":"ssid","pv":"","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"",""],"settings":{"access":"r"}},{"rid":"17","type":"number","name":"rssi","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r"}},{"rid":"18","type":"string","name":"bssid","pv":"","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"",""],"settings":{"access":"r"}},{"rid":"40","type":"bool","name":"online","pv":true,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,true,false],"settings":{"access":"r"}},{"rid":"41","type":"string","name":"uptime","pv":"2:04:19","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"2:04:19",""],"settings":{"access":"r"}},{"rid":"42","type":"string","name":"lastEnOceanUID","pv":"002E236A","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"002E236A",""],"settings":{"access":"r"}},{"rid":"43","type":"string","name":"lastWorkOccUID","pv":"","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"",""],"settings":{"access":"r"}}],"families":[],"isFromConfig":1},{"pid":"0279","ins":"0001","profileName":"lorawan_MileSight_VS121_OccupancySensor","description":"LoRaWAN MileSight VS121 Occupancy Sensor","resources":[{"rid":"00","type":"string","name":"parentObject","pv":"","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"",""],"settings":{"access":"rw","tags":{"attribute":"true"}}},{"rid":"01","type":"string","name":"name","pv":"","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"02","type":"datetime","name":"objectLastUpdated","pv":"2024-12-10T17:42:07.184Z","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"2024-12-10T17:42:07.184Z","1970-01-01T00:00:00.000Z"],"settings":{"access":"r"}},{"rid":"03","type":"string","name":"description","pv":"Occupancy sensor in Elliot's room","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"Occupancy sensor in Elliot's room",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"04","type":"string","name":"location","pv":"Elliot's room","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"Elliot's room",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"0A","type":"string","name":"eui","pv":"24E124600C124962","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"24E124600C124962",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"0B","type":"string","name":"deviceName","pv":"","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"0C","type":"string","name":"applicationName","pv":"","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"0D","type":"string","name":"gatewayName","pv":"","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"0E","type":"string","name":"gatewayID","pv":"","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"0F","type":"number","name":"rssi","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","units":"dBm"}},{"rid":"10","type":"number","name":"loraSNR","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r"}},{"rid":"20","type":"string","name":"appKey","pv":"5572404C696E6B4C6F52613230313823","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"5572404C696E6B4C6F52613230313823",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"21","type":"number","name":"enqueuedCount","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"precision":0}},{"rid":"40","type":"string","name":"protocolVersion","pv":"","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"",""],"settings":{"access":"r"}},{"rid":"41","type":"string","name":"serialNumber","pv":"","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"",""],"settings":{"access":"r"}},{"rid":"42","type":"string","name":"hardwareVersion","pv":"","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"",""],"settings":{"access":"r"}},{"rid":"43","type":"string","name":"firmwareVersion","pv":"","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"",""],"settings":{"access":"r"}},{"rid":"44","type":"number","name":"peopleCountAll","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":255,"precision":0}},{"rid":"45","type":"number","name":"regionCount","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":16,"precision":0}},{"rid":"46","type":"number","name":"peopleIn","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":65536,"precision":0}},{"rid":"47","type":"number","name":"peopleOut","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":65536,"precision":0}},{"rid":"48","type":"number","name":"poepleCountMax","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":255,"precision":0}},{"rid":"49","type":"number","name":"region1Count","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":255,"precision":0}},{"rid":"4A","type":"number","name":"region2Count","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":255,"precision":0}},{"rid":"4B","type":"number","name":"region3Count","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":255,"precision":0}},{"rid":"4C","type":"number","name":"region4Count","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":255,"precision":0}},{"rid":"4D","type":"number","name":"region5Count","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":255,"precision":0}},{"rid":"4E","type":"number","name":"region6Count","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":255,"precision":0}},{"rid":"4F","type":"number","name":"region7Count","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":255,"precision":0}},{"rid":"50","type":"number","name":"region8Count","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":255,"precision":0}},{"rid":"51","type":"number","name":"region9Count","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":255,"precision":0}},{"rid":"52","type":"number","name":"region10Count","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":255,"precision":0}},{"rid":"53","type":"number","name":"region11Count","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":255,"precision":0}},{"rid":"54","type":"number","name":"region12Count","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":255,"precision":0}},{"rid":"55","type":"number","name":"region13Count","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":255,"precision":0}},{"rid":"56","type":"number","name":"region14Count","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":255,"precision":0}},{"rid":"57","type":"number","name":"region15Count","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":255,"precision":0}},{"rid":"58","type":"number","name":"region16Count","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":255,"precision":0}},{"rid":"59","type":"number","name":"flowAtoA","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":65536,"precision":0}},{"rid":"5A","type":"number","name":"flowAtoB","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":65536,"precision":0}},{"rid":"5B","type":"number","name":"flowAtoC","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":65536,"precision":0}},{"rid":"5C","type":"number","name":"flowAtoD","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":65536,"precision":0}},{"rid":"5D","type":"number","name":"flowBtoA","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":65536,"precision":0}},{"rid":"5E","type":"number","name":"flowBtoB","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":65536,"precision":0}},{"rid":"5F","type":"number","name":"flowBtoC","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":65536,"precision":0}},{"rid":"60","type":"number","name":"flowBtoD","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":65536,"precision":0}},{"rid":"61","type":"number","name":"flowCtoA","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":65536,"precision":0}},{"rid":"62","type":"number","name":"flowCtoB","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":65536,"precision":0}},{"rid":"63","type":"number","name":"flowCtoC","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":65536,"precision":0}},{"rid":"64","type":"number","name":"flowCtoD","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":65536,"precision":0}},{"rid":"65","type":"number","name":"flowDtoA","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":65536,"precision":0}},{"rid":"66","type":"number","name":"flowDtoB","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":65536,"precision":0}},{"rid":"67","type":"number","name":"flowDtoC","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":65536,"precision":0}},{"rid":"68","type":"number","name":"flowDtoD","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":65536,"precision":0}}],"families":["LoRaWAN","OccupancySensor"],"isFromConfig":1},{"pid":"028B","ins":"0001","profileName":"ingy_dimmable_relay","description":"INGY Dimmable Relay","resources":[{"rid":"00","type":"string","name":"parentObject","pv":"","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"",""],"settings":{"access":"rw","tags":{"attribute":"true"}}},{"rid":"01","type":"string","name":"name","pv":"Elliot's Lamp","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"Elliot's Lamp",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"02","type":"datetime","name":"objectLastUpdated","pv":"2024-12-06T13:23:52.259Z","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"2024-12-06T13:23:52.259Z","1970-01-01T00:00:00.000Z"],"settings":{"access":"r"}},{"rid":"03","type":"string","name":"description","pv":"Elliot's Lamp","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"Elliot's Lamp",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"04","type":"string","name":"location","pv":"Elliot's Room","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"Elliot's Room",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"0A","type":"number","name":"nodeAddress","pv":337395361,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,337395361,0],"settings":{"access":"r","min":0,"max":4294967295,"precision":0,"tags":{"attribute":"true"}}},{"rid":"0B","type":"number","name":"partition","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":15,"precision":0,"tags":{"attribute":"true"}}},{"rid":"0C","type":"number","name":"setGroup","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,0],"settings":{"access":"rw","min":0,"max":4294967295,"precision":0,"tags":{"attribute":"true","pv":0}}},{"rid":"0E","type":"bool","name":"autoQueryLevel","pv":true,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,true,false],"settings":{"access":"r"}},{"rid":"40","type":"number","name":"knownLevel","pv":100,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,100,0],"settings":{"access":"r","min":0,"max":100,"precision":0,"unit":"%"}},{"rid":"42","type":"number","name":"knownGroupMembership","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":4294967295,"precision":0}},{"rid":"43","type":"number","name":"activePower","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":5000,"precision":0,"unit":"W"}},{"rid":"44","type":"bool","name":"relayState","pv":false,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,false,false],"settings":{"access":"rw"}},{"rid":"4E","type":"bool","name":"sendRegroup","pv":false,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,false,false],"settings":{"access":"rw"}}],"families":["INGY","Luminaire"],"isFromConfig":1}]

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:

["059663D1",0,"Elliot's Lamp"]

PV, Name & URI

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

{"000001/025/0028/0002/0B":{"pv":"059663D1","name":"uid"},"000001/026/028A/0001/41":{"pv":0,"name":"sceneSetting"},"000001/026/028B/0001/03":{"pv":"Elliot's Lamp","name":"description"}}

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

{"error":false,"response":{"ts":"2024-12-11T13:13:24.325Z","uri":"000001/022","data":["0001","000B","0028","002E","0030"]}}

Service

{"error":false,"response":{"ts":"2024-12-11T13:05:27.824Z","uri":"000001/022","data":["0001","000B","0028","002E","0030"]}}

Profile

{"error":false,"response":{"ts":"2024-12-11T13:16:06.751Z","uri":"000001/022/000B","data":["0001","0002"]}}

Instance

{"error":false,"response":{"ts":"2024-12-11T13:16:46.213Z","uri":"000001/022/000B/0001","data":[{"pid":"000B","ins":"0001","profileName":"enocean_F6-02-XX","description":"EnOcean 4 way switch","resources":[{"rid":"00","type":"string","name":"parentObject","pv":"","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"",""],"settings":{"access":"rw","tags":{"attribute":"true"}}},{"rid":"01","type":"string","name":"name","pv":"Elliot's Switch","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"Elliot's Switch",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"02","type":"datetime","name":"objectLastUpdated","pv":"2024-12-11T11:13:34.964Z","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"2024-12-11T11:13:34.964Z","1970-01-01T00:00:00.000Z"],"settings":{"access":"r"}},{"rid":"03","type":"string","name":"description","pv":"","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"04","type":"string","name":"location","pv":"Elliot House","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"Elliot House",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"0A","type":"string","name":"eep","pv":"F6-02-XX","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"F6-02-XX",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"0B","type":"string","name":"uid","pv":"002E236A","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"002E236A",""],"settings":{"access":"r","maxlen":8,"tags":{"attribute":"true"}}},{"rid":"0C","type":"number","name":"status","pv":32,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,32,0],"settings":{"access":"r"}},{"rid":"0D","type":"number","name":"dBm","pv":-49,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,-49,0],"settings":{"access":"r","units":"dBm"}},{"rid":"40","type":"bool","name":"button_A0","pv":false,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,false,false],"settings":{"access":"r"}},{"rid":"41","type":"bool","name":"button_AI","pv":false,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,false,false],"settings":{"access":"r"}},{"rid":"42","type":"bool","name":"button_B0","pv":false,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,false,false],"settings":{"access":"r"}},{"rid":"43","type":"bool","name":"button_BI","pv":false,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,false,false],"settings":{"access":"r"}},{"rid":"44","type":"bool","name":"bowPushed","pv":false,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,false,false],"settings":{"access":"r"}}],"families":["EnOcean","Switch"],"isFromConfig":1}]}}

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

["000001/022/0001/0001","000001/022/000B/0001","000001/022/000B/0002","000001/022/0028/0001","000001/022/0028/0002","000001/022/0028/0003","000001/022/002E/0001","000001/022/0030/0001"]

MobiusFlow Objects

[{"pid":"0001","ins":"0001","profileName":"serviceStatus","description":"","resources":[{"rid":"00","type":"string","name":"parentObject","pv":"","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"",""],"settings":{"access":"rw","tags":{"attribute":"true"}}},{"rid":"01","type":"enum","name":"status","pv":"OK","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"OK","UNKNOWN"],"settings":{"access":"r","enum":{"Unknown":-1,"Fault":0,"OK":1}}},{"rid":"02","type":"string","name":"statusText","pv":"Listening for EnOcean devices","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"Listening for EnOcean devices",""],"settings":{"access":"r"}},{"rid":"03","type":"datetime","name":"lastChanged","pv":"2024-11-18T17:43:47.609Z","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"2024-11-18T17:43:47.609Z","1970-01-01T00:00:00.000Z"],"settings":{"access":"r"}}],"families":[],"isFromConfig":0,"uri":"000001/022/0001/0001"},{"pid":"000B","ins":"0001","profileName":"enocean_F6-02-XX","description":"EnOcean 4 way switch","resources":[{"rid":"00","type":"string","name":"parentObject","pv":"","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"",""],"settings":{"access":"rw","tags":{"attribute":"true"}}},{"rid":"01","type":"string","name":"name","pv":"Elliot's Switch","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"Elliot's Switch",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"02","type":"datetime","name":"objectLastUpdated","pv":"2024-12-11T11:13:34.964Z","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"2024-12-11T11:13:34.964Z","1970-01-01T00:00:00.000Z"],"settings":{"access":"r"}},{"rid":"03","type":"string","name":"description","pv":"","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"04","type":"string","name":"location","pv":"Elliot House","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"Elliot House",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"0A","type":"string","name":"eep","pv":"F6-02-XX","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"F6-02-XX",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"0B","type":"string","name":"uid","pv":"002E236A","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"002E236A",""],"settings":{"access":"r","maxlen":8,"tags":{"attribute":"true"}}},{"rid":"0C","type":"number","name":"status","pv":32,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,32,0],"settings":{"access":"r"}},{"rid":"0D","type":"number","name":"dBm","pv":-49,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,-49,0],"settings":{"access":"r","units":"dBm"}},{"rid":"40","type":"bool","name":"button_A0","pv":false,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,false,false],"settings":{"access":"r"}},{"rid":"41","type":"bool","name":"button_AI","pv":false,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,false,false],"settings":{"access":"r"}},{"rid":"42","type":"bool","name":"button_B0","pv":false,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,false,false],"settings":{"access":"r"}},{"rid":"43","type":"bool","name":"button_BI","pv":false,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,false,false],"settings":{"access":"r"}},{"rid":"44","type":"bool","name":"bowPushed","pv":false,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,false,false],"settings":{"access":"r"}}],"families":["EnOcean","Switch"],"isFromConfig":1,"uri":"000001/022/000B/0001"},{"pid":"000B","ins":"0002","profileName":"enocean_F6-02-XX","description":"EnOcean 4 way switch","resources":[{"rid":"00","type":"string","name":"parentObject","pv":"","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"",""],"settings":{"access":"rw","tags":{"attribute":"true"}}},{"rid":"01","type":"string","name":"name","pv":"Office Blue Switch","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"Office Blue Switch",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"02","type":"datetime","name":"objectLastUpdated","pv":"1970-01-01T00:00:00.000Z","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"1970-01-01T00:00:00.000Z","1970-01-01T00:00:00.000Z"],"settings":{"access":"r"}},{"rid":"03","type":"string","name":"description","pv":"","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"04","type":"string","name":"location","pv":"MF Office","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"MF Office",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"0A","type":"string","name":"eep","pv":"F6-02-XX","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"F6-02-XX",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"0B","type":"string","name":"uid","pv":"0031C26E","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"0031C26E",""],"settings":{"access":"r","maxlen":8,"tags":{"attribute":"true"}}},{"rid":"0C","type":"number","name":"status","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r"}},{"rid":"0D","type":"number","name":"dBm","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","units":"dBm"}},{"rid":"40","type":"bool","name":"button_A0","pv":false,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,false,false],"settings":{"access":"r"}},{"rid":"41","type":"bool","name":"button_AI","pv":false,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,false,false],"settings":{"access":"r"}},{"rid":"42","type":"bool","name":"button_B0","pv":false,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,false,false],"settings":{"access":"r"}},{"rid":"43","type":"bool","name":"button_BI","pv":false,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,false,false],"settings":{"access":"r"}},{"rid":"44","type":"bool","name":"bowPushed","pv":false,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,false,false],"settings":{"access":"r"}}],"families":["EnOcean","Switch"],"isFromConfig":1,"uri":"000001/022/000B/0002"},{"pid":"0028","ins":"0001","profileName":"enocean_A5-09-04","description":"EnOcean temperature, humidity and CO2 sensor","resources":[{"rid":"00","type":"string","name":"parentObject","pv":"","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"",""],"settings":{"access":"rw","tags":{"attribute":"true"}}},{"rid":"01","type":"string","name":"name","pv":"Air Quality Sensor 1","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"Air Quality Sensor 1",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"02","type":"datetime","name":"objectLastUpdated","pv":"2024-12-11T14:38:09.169Z","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"2024-12-11T14:38:09.169Z","1970-01-01T00:00:00.000Z"],"settings":{"access":"r"}},{"rid":"03","type":"string","name":"description","pv":"Air Quality Sensor","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"Air Quality Sensor",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"04","type":"string","name":"location","pv":"MobiusFlow Office Henley","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"MobiusFlow Office Henley",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"0A","type":"string","name":"eep","pv":"A5-09-04","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"A5-09-04",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"0B","type":"string","name":"uid","pv":"018C18E9","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"018C18E9",""],"settings":{"access":"r","maxlen":8,"tags":{"attribute":"true"}}},{"rid":"0C","type":"number","name":"status","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r"}},{"rid":"0D","type":"number","name":"dBm","pv":-79,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,-79,0],"settings":{"access":"r","units":"dBm"}},{"rid":"0E","type":"bool","name":"lrn","pv":false,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,false,false],"settings":{"access":"r"}},{"rid":"40","type":"number","name":"temperature","pv":19.2,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,19.2,0],"settings":{"access":"r","min":0,"max":51,"precision":1,"units":"C"}},{"rid":"41","type":"number","name":"humidity","pv":56.5,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,56.5,0],"settings":{"access":"r","min":0,"max":100,"precision":1,"units":"%"}},{"rid":"42","type":"number","name":"co2","pv":1910,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,1910,0],"settings":{"access":"r","min":0,"max":2550,"precision":0,"units":"ppm"}},{"rid":"43","type":"bool","name":"hasTemperatureSensor","pv":true,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,true,false],"settings":{"access":"r"}},{"rid":"44","type":"bool","name":"hasHumiditySensor","pv":true,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,true,false],"settings":{"access":"r"}}],"families":["EnOcean","CO2Sensor","HumiditySensor","TemperatureSensor"],"isFromConfig":1,"uri":"000001/022/0028/0001"},{"pid":"0028","ins":"0002","profileName":"enocean_A5-09-04","description":"EnOcean temperature, humidity and CO2 sensor","resources":[{"rid":"00","type":"string","name":"parentObject","pv":"","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"",""],"settings":{"access":"rw","tags":{"attribute":"true"}}},{"rid":"01","type":"string","name":"name","pv":"Air Quality Sensor 2","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"Air Quality Sensor 2",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"02","type":"datetime","name":"objectLastUpdated","pv":"2024-12-11T14:31:23.591Z","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"2024-12-11T14:31:23.591Z","1970-01-01T00:00:00.000Z"],"settings":{"access":"r"}},{"rid":"03","type":"string","name":"description","pv":"Air Quality Sensor","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"Air Quality Sensor",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"04","type":"string","name":"location","pv":"MobiusFlow Studio Henley","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"MobiusFlow Studio Henley",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"0A","type":"string","name":"eep","pv":"A5-09-04","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"A5-09-04",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"0B","type":"string","name":"uid","pv":"01879DE6","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"01879DE6",""],"settings":{"access":"r","maxlen":8,"tags":{"attribute":"true"}}},{"rid":"0C","type":"number","name":"status","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r"}},{"rid":"0D","type":"number","name":"dBm","pv":-77,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,-77,0],"settings":{"access":"r","units":"dBm"}},{"rid":"0E","type":"bool","name":"lrn","pv":true,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,true,false],"settings":{"access":"r"}},{"rid":"40","type":"number","name":"temperature","pv":19.2,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,19.2,0],"settings":{"access":"r","min":0,"max":51,"precision":1,"units":"C"}},{"rid":"41","type":"number","name":"humidity","pv":56,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,56,0],"settings":{"access":"r","min":0,"max":100,"precision":1,"units":"%"}},{"rid":"42","type":"number","name":"co2","pv":2550,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,2550,0],"settings":{"access":"r","min":0,"max":2550,"precision":0,"units":"ppm"}},{"rid":"43","type":"bool","name":"hasTemperatureSensor","pv":false,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,false,false],"settings":{"access":"r"}},{"rid":"44","type":"bool","name":"hasHumiditySensor","pv":false,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,false,false],"settings":{"access":"r"}}],"families":["EnOcean","CO2Sensor","HumiditySensor","TemperatureSensor"],"isFromConfig":1,"uri":"000001/022/0028/0002"},{"pid":"0028","ins":"0003","profileName":"enocean_A5-09-04","description":"EnOcean temperature, humidity and CO2 sensor","resources":[{"rid":"00","type":"string","name":"parentObject","pv":"","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"",""],"settings":{"access":"rw","tags":{"attribute":"true"}}},{"rid":"01","type":"string","name":"name","pv":"","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"02","type":"datetime","name":"objectLastUpdated","pv":"1970-01-01T00:00:00.000Z","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"1970-01-01T00:00:00.000Z","1970-01-01T00:00:00.000Z"],"settings":{"access":"r"}},{"rid":"03","type":"string","name":"description","pv":"Air Quality Sensor","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"Air Quality Sensor",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"04","type":"string","name":"location","pv":"MobiusFlow Office Henley","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"MobiusFlow Office Henley",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"0A","type":"string","name":"eep","pv":"A5-09-04","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"A5-09-04",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"0B","type":"string","name":"uid","pv":"018C18E7","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"018C18E7",""],"settings":{"access":"r","maxlen":8,"tags":{"attribute":"true"}}},{"rid":"0C","type":"number","name":"status","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r"}},{"rid":"0D","type":"number","name":"dBm","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","units":"dBm"}},{"rid":"0E","type":"bool","name":"lrn","pv":false,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,false,false],"settings":{"access":"r"}},{"rid":"40","type":"number","name":"temperature","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":51,"precision":1,"units":"C"}},{"rid":"41","type":"number","name":"humidity","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":100,"precision":1,"units":"%"}},{"rid":"42","type":"number","name":"co2","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r","min":0,"max":2550,"precision":0,"units":"ppm"}},{"rid":"43","type":"bool","name":"hasTemperatureSensor","pv":false,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,false,false],"settings":{"access":"r"}},{"rid":"44","type":"bool","name":"hasHumiditySensor","pv":false,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,false,false],"settings":{"access":"r"}}],"families":["EnOcean","CO2Sensor","HumiditySensor","TemperatureSensor"],"isFromConfig":1,"uri":"000001/022/0028/0003"},{"pid":"002E","ins":"0001","profileName":"enocean_A5-07-01","description":"EnOcean occupancy sensor","resources":[{"rid":"00","type":"string","name":"parentObject","pv":"","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"",""],"settings":{"access":"rw","tags":{"attribute":"true"}}},{"rid":"01","type":"string","name":"name","pv":"Occupancy Sensor","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"Occupancy Sensor",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"02","type":"datetime","name":"objectLastUpdated","pv":"2024-12-08T02:51:34.061Z","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"2024-12-08T02:51:34.061Z","1970-01-01T00:00:00.000Z"],"settings":{"access":"r"}},{"rid":"03","type":"string","name":"description","pv":"Occupancy Sensor","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"Occupancy Sensor",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"04","type":"string","name":"location","pv":"MobiusFlow Office Henley","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"MobiusFlow Office Henley",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"0A","type":"string","name":"eep","pv":"A5-07-01","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"A5-07-01",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"0B","type":"string","name":"uid","pv":"01A90FC7","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"01A90FC7",""],"settings":{"access":"r","maxlen":8,"tags":{"attribute":"true"}}},{"rid":"0C","type":"number","name":"status","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r"}},{"rid":"0D","type":"number","name":"dBm","pv":-74,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,-74,0],"settings":{"access":"r","units":"dBm"}},{"rid":"0E","type":"bool","name":"lrn","pv":false,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,false,false],"settings":{"access":"r"}},{"rid":"40","type":"bool","name":"occupancy","pv":false,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,false,false],"settings":{"access":"r"}},{"rid":"41","type":"bool","name":"supplyVoltageAvailable","pv":true,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,true,false],"settings":{"access":"r"}},{"rid":"42","type":"number","name":"supplyVoltage","pv":3.1,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,3.1,0],"settings":{"access":"r","min":0,"max":5,"precision":1,"units":"V"}}],"families":["EnOcean","OccupancySensor"],"isFromConfig":1,"uri":"000001/022/002E/0001"},{"pid":"0030","ins":"0001","profileName":"enocean_A5-07-03","description":"EnOcean occupancy and lux sensor","resources":[{"rid":"00","type":"string","name":"parentObject","pv":"","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"",""],"settings":{"access":"rw","tags":{"attribute":"true"}}},{"rid":"01","type":"string","name":"name","pv":"Occupancy Sensor 2","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"Occupancy Sensor 2",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"02","type":"datetime","name":"objectLastUpdated","pv":"2024-12-11T14:11:01.819Z","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"2024-12-11T14:11:01.819Z","1970-01-01T00:00:00.000Z"],"settings":{"access":"r"}},{"rid":"03","type":"string","name":"description","pv":"PIR Motion Sensor","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"PIR Motion Sensor",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"04","type":"string","name":"location","pv":"MobiusFlow Office Henley","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"MobiusFlow Office Henley",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"0A","type":"string","name":"eep","pv":"A5-07-03","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"A5-07-03",""],"settings":{"access":"r","tags":{"attribute":"true"}}},{"rid":"0B","type":"string","name":"uid","pv":"018AFE2B","prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,"018AFE2B",""],"settings":{"access":"r","maxlen":8,"tags":{"attribute":"true"}}},{"rid":"0C","type":"number","name":"status","pv":0,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,0],"settings":{"access":"r"}},{"rid":"0D","type":"number","name":"dBm","pv":-82,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,-82,0],"settings":{"access":"r","units":"dBm"}},{"rid":"0E","type":"bool","name":"lrn","pv":false,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,false,false],"settings":{"access":"r"}},{"rid":"40","type":"bool","name":"occupancy","pv":false,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,false,false],"settings":{"access":"r"}},{"rid":"41","type":"number","name":"lux","pv":7,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,7,0],"settings":{"access":"r","min":0,"max":1000,"precision":1,"units":"lx"}},{"rid":"42","type":"number","name":"supplyVoltage","pv":3,"prar":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,3,0],"settings":{"access":"r","min":0,"max":5,"precision":1,"units":"V"}}],"families":["EnOcean","OccupancySensor","LightSensor"],"isFromConfig":1,"uri":"000001/022/0030/0001"}]

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:

(v) => {
    return v > 0;
}

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.

rchitecture Overview

The ADFWeb HD67941-B2 DALI/MQTT bridge acts as a converter between MQTT and DALI protocols. The bridge connects to an MQTT broker via either ethernet or WiFi. The bridge acts as a DALI master and therefore the pair of DALI lines is run directly into it. This completes the DALI/MQTT connection.

MobiusFlow can be connected to the same MQTT broker as DALI/MQTT bridge, allowing the two the communicate via MQTT. This allows MobiusFlow achieve to two-way communication with a given DALI circuit, hence allowing control, querying and configuration to be achieved.

The overall architecture is shown in the diagram below.

Service - adfweb dali mqtt

A MobiusFlow service called 'adfweb dali mqtt' has been made to specifically to allow control, querying and configuration to be performed simply and easily from MobiusFlow. Each adfweb dali mqtt service connects to a single HD67941-B2, so if your application uses mutliple HD67941-B2 then multiple adfweb dali mqtt services should be used.

For some use cases that will be covered later in this article, MobiusFlow direct commands (DCMDs) can be used to control some functions of service. These DCMDs are sent via the MobiusFlow engine API most commonly from the Flows, however direct HTTP requests can also be used.

As such, a lower-level system architecture diagram looks as follows:

MQTT Broker

The MQTT broker can be run anywhere which is accessible over a network to both the HD67941-B2 and MobiusFlow. For ease, in most cases the MQTT broker is run within MobiusFlow itself. As such, the architecture diagram becomes the following:

HD67941-B2 Configuration

Navigate to the the MQTT Set Topic menu:

MQTT Publish

Once on the MQTT Set Topic menu, navigate to the MQTT publish tab. Create a single entry the following settings:

Topic

mobiusDALIquery/{MACID}

Note that {MACID} should be replaced with the MAC ID of the HD67941-B2 you're using. For example:

mobiusDALIquery/1064E209AD03

Template

The template should be set to the following JSON string:

{
    "channel": $CHANNEL$, 
    "adv": $ADV$, 
    "grp1": $GRP1$, 
    "grp2": $GRP2$, 
    "ans": $ANSWER$, 
    "status": $STATUS$, 
    "type": $TYPE$, 
    "min": $MIN$, 
    "max": $MAX$  
}

All remaining fields should be populated as shown in the screenshot below:

MQTT Subscribe

Navigate to the MQTT Subscribe tab.

Topic

The topic should be set as follows

mobiusDALIwrite/{MACID}

As before, {MACID} should be replaced with the MAC ID of the HD67941-B2 you're using. For example:

mobiusDALIwrite/1064E209AD03

The remainder of the row should be populated as shown in the screenshot below:

This completes the configuration required for MobiusFlow. Ensure all MQTT changes are saved before flashing the new configuration to the HD67941-B2.

Luminaires and Groups

Overview

Within MobiusFlow, a given DALI luminaire or DALI group is represented by an equivalent luminaire and group object. Both object types are designed to reside on the adfweb dali mqtt. This service is shown configured and running in the screenshot below.