Operations › Interfaces

Open Operations and pick Interfaces, or press Interfaces on a project page to see the ones that apply there. Add one with + › Interface.

Interfaces page with an MQTT, a JSON push and a LoRaWAN interfaceInterfaces page with an MQTT, a JSON push and a LoRaWAN interface
Every interface with its kind, where it applies and its last message.
KindAccessLimit
MQTTUsername and secret for mqtt.hydronode.tech, topics under your own area5 per account
JSON pushA URL with a token (hpi_), or the token in a header10 per account
LoRaWANA webhook URL with a token (wht_) for TTN, ChirpStack or HeliumYour account webhook plus 5 of their own

The secret or token is shown once. New secret (MQTT) or New token (JSON push, LoRaWAN) replaces it; the old one stops at once.

Overview, Access, Live, Mappings, Outgoing, Downlinks, Discovered

SectionShows
OverviewCounts of mappings, sensors, outgoing values and discovered devices, the last message.
AccessHost, username or URL, New secret or New token, for MQTT the Mosquitto bridge.
LiveWhat arrived: MQTT topics with their last payload, the last JSON input, LoRaWAN uplinks.
MappingsWhich field fills which data point (MQTT and JSON push).
OutgoingMQTT only: values HydroNode publishes when you switch them.
DownlinksLoRaWAN only: TTN or ChirpStack access for this interface.
DiscoveredDevices without a sensor, also the ones ignored in a project.
Overview of an MQTT interface with counts and the last messagesOverview of an MQTT interface with counts and the last messages
One interface: counts, access and what came in.

Global or one project

A global interface feeds sensors in every project of its owner, and its devices are suggested everywhere. A project interface feeds only that project; members with Manage there can see and change it. Default pool sets where Add puts a new sensor. Only the owner can change where an interface applies: Change shows first which sensors move, which links, virtual sensors and automations are affected and who gains or loses access, then applies it in one step.

Change where this interface applies, with the sensors that moveChange where this interface applies, with the sensors that move
The preview before an interface changes project.

Devices that show up by themselves

Whatever reaches an interface without a sensor becomes a discovered device: Zigbee2MQTT, Tasmota, Shelly and Home Assistant discovery are recognised, any other MQTT topic with a value or a JSON object counts too, a JSON push input once per value of its device field, and every unknown LoRaWAN DevEUI. They appear greyed at the top of the project's sensor list (for owners and Manage members) and under Discovered of the interface.

Sensor list of a project with two greyed discovered devices and AddSensor list of a project with two greyed discovered devices and Add
Discovered devices at the top of the sensor list.

Add opens a small window: name, pool and the data points to take. Known switches are settable right away. LoRaWAN devices need their decoder afterwards. Ignore hides a device in this project only; Show brings it back. A device leaves the list once every field is mapped.

Add sensor window for a discovered Zigbee2MQTT deviceAdd sensor window for a discovered Zigbee2MQTT device
Adding a discovered device as a sensor.

When a device shows up for the first time you get a message in the message center, one per interface that counts up: “3 new devices on Home broker”, with a push to the apps that support it. It goes to the owner and, for a project interface, to members with Manage.

One field, one data point

A mapping takes one field of an MQTT topic or a JSON input and writes it into one data point. A sensor may mix fields of several interfaces. A field that already fills a data point cannot fill a second one; the window names the sensor that has it. To show the same value in another place, use a reference of a virtual sensor. A sensor's settings list its interfaces and fields under Sources.

Map a field window with topic, field, sensor and data pointMap a field window with topic, field, sensor and data point
Map a field into a data point.

Webhook and downlinks per interface

A LoRaWAN interface has no mappings: its devices are sensors with an fPort decoder. Its Downlinks section connects The Things Network or ChirpStack, so settings and commands reach devices whose last uplink came through this interface. A key entered for one interface never reaches devices of another. Step by step in LoRaWAN and Downlinks.

Downlinks section of a LoRaWAN interface with ChirpStack connectedDownlinks section of a LoRaWAN interface with ChirpStack connected
Downlinks belong to the LoRaWAN interface.

Connect a device

MQTT, JSON push and LoRaWAN walk through the first device.

NextVirtual sensors and external data