Data Connectors · Environment

E+H Floodmonitoring

The node fetches the current values of a list of configured measuring points (instrumentations) from the Endress+Hauser Netilion cloud. From water level and distance, the configured thresholds and optional flood classes it builds one FloodMonitoring entity per measuring point and emits all entities together in one message.

Data source
Trigger-based
FloodMonitoring

Node type: eh-floodmonitoring
Package: @htag/node-red-contrib-hypertegrity-environment
Inputs / outputs: 1 / 1
Data source: Endress+Hauser Netilion API (api.netilion.endress.com)

When to use this node

Municipalities that operate their own Endress+Hauser radar or ultrasonic sensors on brooks, culverts or retention basins receive the readings via the Netilion cloud. The E+H Floodmonitoring node brings these values into a Node-RED flow, converts them to centimetres and evaluates them against the thresholds you set.

Typical use cases are:

Flood monitoring of small watercourses that are not covered by state or federal gauges.
Alert dashboards with status Normal or Critical, a picture of the measuring point and a link to a detail page.
Adaptive polling intervals, where critical measuring points are queried more often than unremarkable ones.

How the node works

Trigger

An incoming message starts the fetch. Optionally it brings its own sensor list or the fastInterval flag.

Authenticate

Depending on the method, API key and user are sent via Basic Auth, or an OAuth token is requested and refreshed automatically.

Fetch values

For each measuring point the endpoint instrumentations/ID/values is queried one after another. Errors of single measuring points are logged as warnings.

Evaluate and emit

Water level and distance are converted from millimetres to centimetres, compared with thresholds and sent as an array of FloodMonitoring entities.

Result: One message with an array of FloodMonitoring entities, each with water level, status, flood class, location and links.

The node is trigger-based. Combine it with one or two Inject nodes: a slow interval for all measuring points and optionally a fast interval with msg.fastInterval = true that only queries the currently critical measuring points. The node remembers which measuring points are critical in the node context.

Configuration

The edit dialog is divided into the tabs General, Sensors and Authentication.

General tab

Field	Type	Default	Meaning
Name	Text	empty	Display name of the node in the flow. Without a name the node shows "E+H Floodmonitoring".

Sensors tab

The tab contains an editable list. Each entry describes one measuring point and is stored as an object in the array sensors.

Field	Type	Default	Meaning
Sensor ID	Select with refresh button	empty	ID of the instrumentation in Netilion. The button loads up to 100 instrumentations of your account; tag and serial number are displayed. Stored as `id`.
Name	Text	empty	Display name of the measuring point. Carried over into the entity. Stored as `name`.
Distance Value	Select	empty (equals `distance`)	Key of the value that provides the measured distance. The Werte button loads the available keys of the selected instrumentation. Stored as `distanceKey`.
Level Value	Select	empty (equals `level`)	Key of the value that provides the water level. Stored as `levelKey`.
Latitude (Lat), Longitude (Lon)	Number	empty	Coordinates of the measuring point in decimal degrees. Missing values are emitted as `0`. Stored as `lat` and `lon`.
Threshold Level (cm)	Number	empty	Water level in centimetres from which the status `Critical` is set. `0` or empty disables the check. Stored as `thresholdLevel`.
Threshold Distance (cm)	Number	empty	Distance threshold in centimetres. Stored as `thresholdDistance`.
HQ Thresholds	Checkbox	off	Enables classification into flood classes. Stored as `useHQThresholds`.
HQ Thresholds (comma separated)	Text	empty	Six ascending limits in millimetres, separated by commas (example below). Stored as `hqThresholds`.
Image URL	Text	empty	Address of a picture of the measuring point. Supports the placeholders `{{id}}` and `{{name}}` as well as environment variables in the form `${NAME}`. Stored as `imageLink`.
Dashboard URL	Text	empty	Address of a detail page. Same placeholders as the image URL. Stored as `dashboardLink`.

Example of six HQ thresholds:

1412,1686,1891,2100,2300,2500

Authentication tab

Field	Type	Default	Meaning
Authentication Method	Select (`basic`, `oauth`)	`basic`	Basic Auth (API Key + User) sends API key and user credentials with every request. OAuth Token (API Key + Secret + User) requests a short-lived token with API key and secret that is refreshed automatically. Stored as `authMethod`.
API Key	Password (credential)	empty	API key of your Netilion application. Stored encrypted and sent in the header `Api-Key` with every request.
API Secret	Password (credential, OAuth only)	empty	Secret of your Netilion application for the token request. Stored encrypted.
Username	Text (credential)	empty	Username of your Netilion account.
Password	Password (credential)	empty	Password of your Netilion account. Stored encrypted.

Registration with Netilion

Access requires an Endress+Hauser Netilion account in which your devices are set up as instrumentations, plus the API key and, if applicable, secret of an application registered there. Both are obtained in the Netilion developer portal. All four credential fields accept environment variables in the form ${NAME}, which the node resolves at startup.

Credentials already stored are shown as placeholders in the dialog; leave the field empty to keep the stored value. The refresh buttons in the dialog fall back to the stored credentials via the Node-RED server, so you do not have to enter them again.

Input

Property	Type	Meaning
`msg`	any	Every message starts a fetch. All properties of the message are kept in the output; `payload` is overwritten.
`msg.payload`	Array (optional)	Replaces the configured sensor list if it is a non-empty array whose first element has a field `id`. Per element `id`, `name`, `coordinates.latitude`, `coordinates.longitude`, `thresholds.level`, `thresholds.distance`, `hq_thresholds` (array, enables HQ classification), `imageLink` and `dashboardLink` are evaluated. For distance and level value the keys `distance` and `level` apply.
`msg.fastInterval = true`	Boolean (optional)	Fast interval: only measuring points that had the status `Critical` in the last fetch are queried.
`msg.fastInterval = false`	Boolean (optional)	Slow interval: all measuring points except the currently critical ones are queried.
`msg.fastInterval` not set	–	All configured or provided measuring points are queried.

Output

The node sends one message per fetch, provided at least one measuring point was queried successfully. msg.payload is an array of FloodMonitoring entities.

{
  "payload": [
    {
      "id": "urn:ngsi-ld:FloodMonitoring:551018",
      "type": "FloodMonitoring",
      "name": "Gauge Example Brook Bridge",
      "alertLevel": 120,
      "location": {
        "value": {"type": "Point", "coordinates": [7.4701, 51.3602]}
      },
      "dateObserved": "2026-10-01T08:12:00.000Z",
      "floodLevelStatus": "Normal",
      "hq": 0,
      "measuredDistance": 245.3,
      "currentLevel": 54.7,
      "picture": "https://images.example.org/sites/551018.jpg",
      "link": "https://dashboard.example.org/waterlevel551018"
    }
  ]
}

Field	Meaning
`id`	`urn:ngsi-ld:FloodMonitoring:` followed by the instrumentation ID.
`type`	Always `FloodMonitoring`.
`name`	Configured name of the measuring point.
`alertLevel`	Configured threshold level in centimetres; `0` if none is set.
`location`	Location in NGSI-v2 style with a GeoJSON point under `value`, order longitude, latitude.
`dateObserved`	Timestamp of the level value from Netilion; if the level value is missing, the time of the fetch.
`floodLevelStatus`	`Critical` if a threshold greater than `0` is set and `currentLevel` reaches or exceeds it; otherwise `Normal`.
`hq`	Flood class `0`, `5`, `10`, `25`, `50`, `100` or `150` based on the six HQ limits; `0` if classification is disabled or fewer than six limits are given.
`measuredDistance`	Measured distance in centimetres (Netilion delivers millimetres). Omitted if the distance value was not found.
`currentLevel`	Water level in centimetres (Netilion delivers millimetres). Omitted if the level value was not found.
`picture`	Image URL after placeholder substitution; omitted if empty.
`link`	Dashboard URL after placeholder substitution; omitted if empty.

Example flow

The package ships with an example flow. Import it in Node-RED via Menu → Import → Examples → @htag/node-red-contrib-hypertegrity-environment → eh-floodmonitoring. Alternatively download eh-floodmonitoring.json and import it via Menu → Import.

Step 1

Two Inject nodes

'Go!' triggers the full fetch every hour; 'fastInterval' sets msg.fastInterval to true every 15 minutes and queries only critical measuring points.

Step 2