Monnit Edge - 02 Path (Sensors UI vs Flows)

Big picture — Edge Gateway + Node-RED

There are two UIs on a Monnit Edge. Do not mix them up:

Open the Edge in a browser (usually https://<edge-ip>/ ). Log in with an Edge user.

Then open Flows from the Edge nav when you are ready for Node-RED (this editor).

1. End-to-end data path

  Wireless sensors
        │
        ▼
  Edge radio + Monnit Edge software
        │
        ├──► Edge UI: Sensors / Gateways / Settings   ← humans manage devices here
        │
        └──► Node-RED: [iMonnit-Edge] ──► BACnet / Modbus / MQTT / filter
                                          ↑
                                   this lab (Flows)

iMonnit-Edge only forwards what the Edge already knows about.

If a sensor is missing or Offline in the Edge Sensors UI, it will not magically appear in Flows.

2. Edge Gateway UI (not Node-RED) — learn this first

Main nav on the Edge local site:

Sensors

Purpose: inventory and live data for wireless sensors.

• Sensors list — each row is a sensor (name, id, Online/Offline, last reading)
• Add Device / Add sensor — enter Device ID and Security Code from the sensor label / packaging, then save
• After pairing, confirm the sensor shows Online and a recent reading (temperature, humidity, …)
• Open a sensor — view history/readings, rename, and open configuration
• Edit configuration — heartbeats, aware thresholds, calibration, and other profile fields the Edge exposes for that Application ID

(exactly which fields appear depends on sensor type)

Rule of thumb: get sensors Online and updating readings here before debugging BACnet/Modbus in Flows.

Gateways

Purpose: this Edge and any linked Ethernet/child gateways.

• Confirm this Edge shows Online
• If you use child gateways, confirm they appear and are Online too

Flows

Purpose: opens Node-RED (the canvas you are in now).

• This is where iMonnit-Edge, BACnet, Modbus, MQTT, and Status live
• Deploying Flows does not replace pairing sensors — pairing stays on Sensors

Settings

Purpose: system / appliance configuration (not per-sensor datums).

Typical areas:

• Network — IP / DHCP / hostname
• Date & Time — clock / timezone (matters for timestamps)
• Users — who can log into the Edge UI
• Services — platform services
• About — firmware / identity

Use Settings when the Edge itself needs network or account setup — not for day-to-day sensor heartbeats (those are under Sensors → edit sensor).

3. What Node-RED adds (Flows)

Once sensors are Online in the Edge UI:

1. iMonnit-Edge emits a message on each report
2. You wire that into BACnet / Modbus / MQTT / sensor filter
3. Building systems poll or subscribe outside the Edge

4. Before you touch outputs

Pair the sensor in Edge UI → Sensors and confirm it is Online with a recent reading.

Then use iMonnit-Edge in Flows. Do not debug BACnet / Modbus / MQTT until that is true.