Skip to main content

Working with IoT Devices

Connect IoT sensors and gateways to Infodeck for real-time monitoring, automated alerts, and data-driven maintenance.

Quick Summary

IoT devices are assets with a UUID and Integration Service connection. They send real-time data that appears in the Status tab and can trigger automated alerts.


Before You Begin

Requirements
  • You must have an Integration Service configured (LoRaWAN network server, AWS IoT, etc.)
  • The device must be registered in your network server
  • You need the device UUID/DevEUI

What Makes an Asset an "IoT Device"?

An asset becomes an IoT device when:

  1. Its Asset Type is marked as IoT-enabled, OR
  2. It has an Integration Service assigned

IoT devices have additional features:

  • UUID field — Device identifier
  • Connection status — Active/Inactive indicator
  • Status tab — Real-time sensor data
  • Status thresholds — Automated alert conditions

Registering an IoT Device

Step 1: Create the Asset

  1. Click Create Asset
  2. Select an IoT-enabled Asset Type
  3. Choose the Location where the device is installed

Step 2: Enter Device Information

FieldRequiredDescription
NameYesDescriptive name (e.g., "Temp Sensor - Server Room")
UUIDYesDevice EUI from your network server (3-90 alphanumeric chars)
Integration ServiceYesThe IoT platform managing this device
Active TimeoutNoMinutes without data before marking inactive (min 10)

Step 3: Save

Click Create to register the device.

Finding Your UUID

The UUID (also called DevEUI) is typically found:

  • On the device label/sticker
  • In your LoRaWAN network server console
  • In the manufacturer's documentation

Monitoring Device Status

Connection Status

IoT devices show connection status in the asset list:

StatusMeaning
ActiveDevice has sent data recently
InactiveNo data received within the timeout period

Viewing Real-Time Data

  1. Open the IoT device asset
  2. Click the Status tab
  3. View:
    • Current values — Latest sensor readings
    • Historical charts — Data trends over time
    • Raw telemetry — Device uplink messages

Setting Up Alert Thresholds

Configure automatic status changes based on sensor values.

Step 1: Open Thresholds

  1. Open the IoT device
  2. Go to the Profile tab
  3. Find Status Thresholds section
  4. Click Edit Thresholds

Step 2: Define Critical Conditions

Set conditions that trigger Critical status (red):

  1. Click Add Condition
  2. Select the Data Field (property to monitor)
  3. Choose the Operator (>, <, =, etc.)
  4. Enter the Value threshold
  5. For multiple conditions, set AND or OR logic

Step 3: Define Warning Conditions

Set conditions that trigger Warning status (yellow):

Follow the same steps for warning-level thresholds.

Step 4: Save

Click Update to activate the thresholds.


Threshold Operators

OperatorMeaningExample
=Equal totemperature = 30
!=Not equal tostatus != "OK"
>Greater thantemperature > 28
>=Greater than or equalhumidity >= 80
<Less thanbattery < 20
<=Less than or equalpressure <= 1000

Real-World Examples

Example 1: Register a Cold Storage Temperature Sensor

Situation: You need to monitor temperature in a cold storage room that must stay below 4°C.

Solution:

  1. Click Create Asset
  2. Asset Type: Select "Temperature Sensor" (IoT-enabled)
  3. Location: "Warehouse > Cold Storage Room 1"
  4. Name: Cold Storage Temp - Room 1
  5. UUID: A81758FFFE042ABC (from device label)
  6. Integration Service: Select your LoRaWAN network server
  7. Active Timeout: 15 minutes
  8. Click Create

Setting Up Alerts:

  1. Open the newly created sensor
  2. Go to ProfileStatus ThresholdsEdit
  3. Add Critical condition: temperature > 6
  4. Add Warning condition: temperature > 4
  5. Click Update

Result: The sensor reports real-time temperature. If it exceeds 4°C, status changes to Warning. Above 6°C triggers Critical status, alerting your team immediately.


Example 2: Monitor Server Room Humidity

Situation: Your server room requires humidity between 40-60% for optimal equipment operation.

Solution:

  1. Register a humidity sensor with IoT asset type
  2. Set up thresholds:
    • Critical: humidity > 70 OR humidity < 30
    • Warning: humidity > 60 OR humidity < 40

Result: You're alerted before humidity levels damage sensitive equipment.


Example 3: Track Device Battery Levels

Situation: You want to be notified when sensor batteries are running low.

Solution:

  1. Open any battery-powered IoT sensor
  2. Edit status thresholds
  3. Add conditions:
    • Warning: battery < 30
    • Critical: battery < 10

Result: You can proactively replace batteries before devices go offline.


Example 4: Troubleshoot an Offline Sensor

Situation: A temperature sensor is showing "Inactive" status.

Troubleshooting Steps:

  1. Check connection status — Open the device, look at "Last seen" timestamp
  2. Verify in network server — Confirm the device is transmitting in your LoRaWAN console
  3. Check Active Timeout — If set too short, device may appear inactive between readings
  4. Check UUID — Ensure the UUID in Infodeck matches the actual device EUI
  5. Check integration — Verify the Integration Service connection is healthy
  6. Physical check — Device may have lost power, moved out of range, or failed

Common Fixes:

  • Increase Active Timeout if device reports infrequently
  • Power cycle the device
  • Check gateway coverage for the device location
  • Re-register the device if UUID was entered incorrectly

Active Timeout Explained

The Active Timeout setting controls when a device is marked inactive:

SettingGood For
10-15 minDevices sending data every few minutes
30-60 minDevices sending data hourly
120+ minDevices sending data daily
tip

Set timeout to 2-3x your device's reporting interval to avoid false "Inactive" alerts.


Supported IoT Protocols

Infodeck integrates with:

ProtocolDescription
LoRaWANLong-range, low-power sensor networks
AWS IoTAmazon Web Services IoT Core
HTTPCustom webhooks and REST APIs

IoT Device Limits

PlanMax IoT Devices
Lite10 devices
Basic50 devices
Professional500 devices
EnterpriseUnlimited


Need help? Contact Infodeck Support

Was this page helpful?