How to

How to Connect Digi International Devices to TagoIO

Step-by-step guide to connecting Digi International gateways and Digi Remote Manager to TagoIO. Includes HTTPS, MQTT, and DataStreams setup for smart buildings, industrial, agriculture, and smart equipment applications.

Fabio Rosa ·
How to Connect Digi International Devices to TagoIO

Digi International builds some of the most reliable industrial gateways and cellular routers in the market. Their device line, from the IX15 LTE-M gateway to the IX30 serial router, connects field sensors and machines to the internet in environments where reliability is not optional.

TagoIO gives you the application layer: device management, data storage, real-time dashboards, automated alerts, and a full REST API to build on top of. The two platforms complement each other well.

But getting data from a Digi device into TagoIO is not automatic. You need to pick the right integration path, format the payload correctly, and configure both sides. This guide covers exactly that, with step-by-step instructions for each approach and examples across four application areas: smart buildings, industrial monitoring, agriculture, and smart equipment.

What you need before you start

  • A TagoIO account (free plan available)
  • A Digi gateway (IX15, IX20, IX30, or similar) or a Digi Remote Manager account
  • Network access from the Digi device to the internet

How the integration works

There are two main paths to get data from Digi devices into TagoIO:

Path 1: Digi Remote Manager DataStreams + HTTPS webhook This is the recommended path when you already use DRM to manage your fleet. DRM collects data from your Digi devices through DataStreams and can forward it to any HTTPS endpoint, including the TagoIO API.

Path 2: Direct MQTT from the Digi gateway If your Digi gateway runs a Python script or has a built-in MQTT client, you can connect it directly to TagoIO’s MQTT broker using TagoTiP. This skips DRM entirely and gives you lower latency.

Both paths work. Pick the one that fits your existing setup.

Path 1: Digi Remote Manager DataStreams to TagoIO

Step 1: Create a device in TagoIO

  1. Log in to admin.tago.io.
  2. Click Devices in the left sidebar.
  3. Click Add Device.
  4. Select HTTPS as the connector type.
  5. Give the device a name (for example, digi-ix15-building-a).
  6. Click Create Device.

Full device setup documentation: docs.tago.io/docs/tagoio/devices

Step 2: Copy the device token

After creating the device, go to the General tab and copy the Device Token. You will use this to authenticate requests from DRM.

More on tokens: docs.tago.io/docs/tagoio/devices/device-token

Step 3: Configure a DataStream subscription in Digi Remote Manager

In DRM, DataStreams are named data channels that your Digi device writes to (for example, temperature, humidity, battery_level). You can subscribe to those streams and push the data to an external HTTPS endpoint.

  1. Log in to your DRM account at devicecloud.digi.com.

  2. Navigate to Data Services > DataStreams.

  3. Find the data streams coming from your device. They follow the format /dia/channel/<device-id>/<stream-name>.

  4. Go to Monitor and create a new Monitor subscription.

  5. Set the topic to the data streams you want to forward.

  6. Set the delivery method to HTTP POST.

  7. Set the endpoint URL to:

    https://api.tago.io/data
  8. Add the following HTTP header:

    Device-Token: YOUR_DEVICE_TOKEN

DRM will now POST data to TagoIO every time a new value arrives on the subscribed streams.

Step 4: Map the DRM payload to TagoIO variables

DRM sends data in its own XML or JSON format. TagoIO expects the standard data format:

[
  {"variable": "temperature", "value": 23.5, "unit": "C"},
  {"variable": "humidity", "value": 65, "unit": "%"}
]

If DRM is sending a different structure, use a Payload Parser in TagoIO to transform the incoming payload before it gets stored.

To add a parser:

  1. Open your device in TagoIO.
  2. Go to the Payload Parser tab.
  3. Write a JavaScript function to extract the variables from the DRM payload and return them in the TagoIO format.

Step 5: Verify data in the Live Inspector

Open the Live Inspector tab on your device page in TagoIO. It shows every incoming request in real time. Send a test reading from DRM and confirm the data appears here before building your dashboard.

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

Path 2: Direct MQTT from the Digi gateway

Digi gateways running Digi firmware or Python scripts can connect directly to TagoIO via MQTT using the TagoTiP protocol.

Step 1: Create a TagoTiP device in TagoIO

  1. In TagoIO, go to Devices > Add Device.
  2. Search for TagoTiP and select it as the connector.
  3. Give the device a name and set its Serial Number (this maps to the MQTT topic).
  4. Save the device and note the Authorization Hash from the General tab.

Step 2: Connect the Digi gateway MQTT client

Configure the MQTT client on your Digi device with these settings:

SettingValue
Hostmqtt.tip.us-e1.tago.io (US) or mqtt.tip.eu-w1.tago.io (EU)
Port1883 (dev) or 8883 with TLS (production)
UsernameFirst 8 hex characters of your Authorization Hash
PasswordLast 8 hex characters of your Authorization Hash
Publish topic$tip/{serial}/push
Subscribe topic$tip/{serial}/ack

Step 3: Publish sensor data

The TagoTiP payload format is compact and human-readable:

[temperature:=23.5#C;humidity:=65#%]

For a Digi IX15 with a connected temperature sensor, a Python script running on the gateway would look like this:

import paho.mqtt.client as mqtt

SERIAL = "ix15-building-a"
AUTH_HASH = "4deedd7bab8817ec"  # replace with your hash
HOST = "mqtt.tip.us-e1.tago.io"

client = mqtt.Client()
client.username_pw_set(AUTH_HASH[:8], AUTH_HASH[8:])
client.connect(HOST, 1883)

payload = "[temperature:=23.5#C;humidity:=65#%]"
client.publish(f"$tip/{SERIAL}/push", payload)
client.disconnect()

TagoTiP full documentation: docs.tago.io/docs/tagotip/transports/mqtt

Step 6: Build your dashboard

Once data is flowing into TagoIO, go to Dashboards and click + to create a new one.

TagoIO provides pre-built dashboard templates you can start from. In the dashboard creation dialog, look for Templates to find ready-to-use layouts for common applications including environmental monitoring and asset tracking. You can then adapt the widgets to your Digi data variables.

Dashboard documentation: docs.tago.io/docs/tagoio/dashboards

For applications managing multiple Digi devices across locations, use a Blueprint Dashboard. Blueprint dashboards use tags to associate one dashboard layout with multiple devices automatically. You create the layout once; each device gets its own view.

Step 7: Set up alerts and automated actions

Use TagoIO Actions to trigger notifications or logic when sensor values cross thresholds. For example, send an email or SMS when a temperature sensor in a server room exceeds 30 C, or trigger a script when a machine goes offline.

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

Application examples

Smart buildings

Digi IX15 or IX20 gateways connect to BACnet/IP, Modbus RTU, or direct sensor inputs inside a building. Common variables to stream to TagoIO:

  • HVAC temperature and humidity per zone
  • Energy consumption (kWh) per circuit
  • Occupancy sensor counts
  • Water leak detection (binary alert)

On the dashboard, use time-series charts for energy trends and card widgets for current zone temperatures. Set up alerts to notify the facilities team when a zone falls outside the comfort band.

Industrial monitoring

Digi IX30 and IX40 routers have serial RS-232/RS-485 ports that connect to PLCs and legacy industrial equipment. Stream to TagoIO:

  • Machine cycle counts and OEE metrics
  • Motor current draw and vibration
  • Conveyor speed and throughput
  • Alarm codes from PLC registers

Use TagoIO Analysis scripts to calculate OEE from raw cycle data and write the result back to a dashboard variable. Alerts can trigger a work order system via the TagoIO API when a machine goes into fault state.

Agriculture

Digi IX15 with LTE-M connectivity works in areas with limited cellular coverage. Deploy it at a pump station or greenhouse and stream:

  • Soil moisture at multiple depths
  • Air temperature and relative humidity
  • Irrigation flow rate and valve state
  • Tank water level

Use the Blueprint Dashboard feature to create a single layout and apply it across every field station. Each station gets its own dashboard view without duplicating the configuration.

Smart equipment (fleet and asset)

Digi WR series routers and XBee cellular modules are common in mobile equipment. Stream to TagoIO:

  • GPS location
  • Engine hours and fuel consumption
  • Door and compartment sensor states
  • Battery voltage for electric equipment

TagoIO stores location data and can display it on a map widget. Combine with time-series data to correlate location with fuel consumption or maintenance events.

Taking it further with AI

TagoIO has an MCP server that connects AI assistants like Claude directly to your IoT data. Once your Digi devices are streaming to TagoIO, you can query that data in natural language: ask for anomalies, generate analysis scripts, or get a summary of what happened on the floor last week. Details at docs.tago.io/docs/tagoio/getting-started/tagoio-mcp-ai-powered-iot-data-integration.

Summary

Connecting Digi International devices to TagoIO takes three things: a device in TagoIO with a valid token, a data path (DRM DataStreams webhook or direct MQTT), and a payload in the right format. Everything after that, dashboards, alerts, and analysis, is built inside TagoIO.

The integration works for any Digi device that can reach the internet. Start with one device, validate the data in the Live Inspector, and build the dashboard from there.