How to Connect Multitech Conduit to TagoIO

The Multitech Conduit is one of the most established LoRaWAN gateways in North American industrial and commercial deployments. The Conduit AEP (Application Enablement Platform) model runs a local Linux environment with a built-in LoRaWAN Network Server and supports both HTTPS and MQTT data forwarding.

TagoIO is the application layer: it stores sensor readings, drives dashboards, fires alerts, and exposes your data through a REST API. Connecting the Conduit AEP to TagoIO gives you a complete on-premise-to-cloud stack with no third-party cloud dependency between the gateway and your application.

This guide covers two integration paths: HTTPS push from the Conduit AEP to TagoIO directly, and MQTT forwarding using TagoTiP.

What you need before you start

• A TagoIO account (free plan available)
• A Multitech Conduit AEP (MTCAP, MTCDTIP, or compatible model)
• The mPower® firmware (comes pre-installed on Conduit AEP)
• Registered end devices (LoRaWAN OTAA or ABP)

Architecture overview

The Conduit AEP runs a LoRaWAN Network Server locally. End devices join the network through the gateway, and the AEP LNS decodes and routes application payloads. You configure the AEP to push those payloads to TagoIO via HTTPS or MQTT.

[LoRaWAN sensors] → [Conduit AEP LNS] → [TagoIO via HTTPS or MQTT]

Path 1: Conduit AEP → HTTPS → TagoIO

This path uses the mPower web interface to create a Custom App that POSTs data to the TagoIO API.

Step 1: Create a device in TagoIO

1. Log in to admin.tago.io.
2. Go to Devices → Add Device.
3. Select HTTPS as the connector.
4. Name the device (e.g., conduit-sensor-node-01).
5. Copy the Device Token from the General tab.

Device docs: docs.tago.io/docs/tagoio/devices

Step 2: Register end devices on the Conduit AEP

1. Log in to your Conduit mPower web UI (default: https://192.168.2.1).
2. Go to LoRaWAN → Network Server.
3. Click Add Device and enter the DevEUI, AppEUI, and AppKey for each sensor.
4. Assign each device to an Application.

Step 3: Create a Custom App on the Conduit AEP

The Conduit AEP supports Node-RED or custom Python/Node.js scripts via the App Framework. Here we use the built-in Node-RED flow to forward data.

1. In the mPower UI, go to App → Node-RED and launch it.
2. Create a flow:
   • Input: LoRa Node (receives uplink from the AEP LNS)
   • Function node: Parse the payload and format it for TagoIO
   • HTTP request node: POST to https://api.tago.io/data with Device-Token header

Example function node code:

const loraMsg = msg.payload;
const rawHex = loraMsg.data;

// Example: 2-byte temperature, 2-byte humidity
const buf = Buffer.from(rawHex, "hex");
const temperature = buf.readInt16BE(0) / 100;
const humidity = buf.readInt16BE(2) / 100;

msg.payload = JSON.stringify([
  { variable: "temperature", value: temperature, unit: "C" },
  { variable: "humidity", value: humidity, unit: "%" },
  { variable: "rssi", value: loraMsg.rssi },
  { variable: "snr", value: loraMsg.snr }
]);

msg.headers = {
  "Content-Type": "application/json",
  "Device-Token": "YOUR_TAGOIO_DEVICE_TOKEN"
};

msg.url = "https://api.tago.io/data";

return msg;

3. Deploy the flow. Data will now flow from the Conduit AEP to TagoIO on each uplink.

Path 2: Conduit AEP → MQTT → TagoIO (TagoTiP)

For lower-latency applications or if you prefer MQTT over HTTP, use TagoTiP: TagoIO’s MQTT protocol.

Step 1: Create a TagoTiP device in TagoIO

1. In TagoIO, go to Devices → Add Device.
2. Search for TagoTiP and select it.
3. Set the Serial Number for this device (this maps to the MQTT topic).
4. Save and note the Authorization Hash from the General tab.

TagoTiP MQTT docs: docs.tago.io/docs/tagotip/transports/mqtt

Step 2: Configure MQTT forwarding on the Conduit AEP

In the Node-RED function node, change the output to publish to TagoTiP:

const SERIAL = "conduit-node-01";
const AUTH_HASH = "your_auth_hash_here";

const loraMsg = msg.payload;
const buf = Buffer.from(loraMsg.data, "hex");
const temperature = buf.readInt16BE(0) / 100;
const humidity = buf.readInt16BE(2) / 100;

msg.topic = `$tip/${SERIAL}/push`;
msg.payload = `[temperature:=${temperature}#C;humidity:=${humidity}#%]`;

return msg;

Connect an MQTT out node to this function node, configured with:

Step 3: Verify in the Live Inspector

Open the Live Inspector on your TagoIO device and confirm variables arrive correctly on each uplink cycle.

Live Inspector docs: docs.tago.io/docs/tagoio/devices/live-inspector

Step 4: Build dashboards and alerts

Create dashboards from Dashboards → +. The Conduit AEP is commonly used in:

• Industrial environments: show machine health metrics on a per-asset basis
• Building automation: HVAC, lighting, and energy monitoring across floors
• Remote sites: cellular-connected Conduit with solar-powered sensors

For multi-site Conduit deployments, use Blueprint Dashboards to create one layout that applies automatically to each site based on device tags.

Set up Actions for:

• Threshold breach notifications
• Offline device alerts when no data arrives within a configurable window
• Automated reporting exports

Actions docs: docs.tago.io/docs/tagoio/actions

Use case examples

Industrial monitoring

Conduit AEP installed in a manufacturing facility with LoRaWAN vibration sensors on motors and pumps. Node-RED on the Conduit parses and forwards data to TagoIO. TagoIO Analysis scripts run anomaly detection on vibration signatures and trigger maintenance tickets when early wear patterns are detected.

Building automation with HVAC sensors

Multiple LoRaWAN temperature and humidity sensors throughout a commercial building. Conduit AEP routes readings to TagoIO. TagoIO drives a Blueprint Dashboard showing per-zone comfort levels and integrates with BMS systems via API calls in Actions.

Remote environmental monitoring

Conduit MTCDTIP (with cellular backup) at a water utility monitoring station. LoRaWAN water level and quality sensors report to TagoIO. If cellular connectivity is lost, the Conduit buffers readings locally (via Node-RED SQLite) and re-syncs when connectivity returns.

Taking it further with AI

TagoIO’s MCP server connects AI assistants like Claude to your Conduit sensor data. Once integrated, you can ask natural language questions about your deployment without writing queries manually.

MCP docs: docs.tago.io/docs/tagoio/getting-started/tagoio-mcp-ai-powered-iot-data-integration

Summary

The Multitech Conduit AEP connects to TagoIO via HTTPS or MQTT. Node-RED on the Conduit handles the integration logic: parsing raw LoRaWAN payloads from the AEP LNS and forwarding clean data to TagoIO. Once data flows, TagoIO manages storage, dashboards, and alerting.

• TagoIO Devices: docs.tago.io/docs/tagoio/devices
• Sending Data format: docs.tago.io/docs/tagoio/devices/sending-data
• TagoTiP MQTT: docs.tago.io/docs/tagotip/transports/mqtt
• Dashboards: docs.tago.io/docs/tagoio/dashboards
• Actions: docs.tago.io/docs/tagoio/actions