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
- 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:
- Its Asset Type is marked as IoT-enabled, OR
- 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
- Click Create Asset
- Select an IoT-enabled Asset Type
- Choose the Location where the device is installed
Step 2: Enter Device Information
| Field | Required | Description |
|---|---|---|
| Name | Yes | Descriptive name (e.g., "Temp Sensor - Server Room") |
| UUID | Yes | Device EUI from your network server (3-90 alphanumeric chars) |
| Integration Service | Yes | The IoT platform managing this device |
| Active Timeout | No | Minutes without data before marking inactive (min 10) |
Step 3: Save
Click Create to register the device.
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:
| Status | Meaning |
|---|---|
| Active | Device has sent data recently |
| Inactive | No data received within the timeout period |
Viewing Real-Time Data
- Open the IoT device asset
- Click the Status tab
- 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
- Open the IoT device
- Go to the Profile tab
- Find Status Thresholds section
- Click Edit Thresholds
Step 2: Define Critical Conditions
Set conditions that trigger Critical status (red):
- Click Add Condition
- Select the Data Field (property to monitor)
- Choose the Operator (>, <, =, etc.)
- Enter the Value threshold
- 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
| Operator | Meaning | Example |
|---|---|---|
= | Equal to | temperature = 30 |
!= | Not equal to | status != "OK" |
> | Greater than | temperature > 28 |
>= | Greater than or equal | humidity >= 80 |
< | Less than | battery < 20 |
<= | Less than or equal | pressure <= 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:
- Click Create Asset
- Asset Type: Select "Temperature Sensor" (IoT-enabled)
- Location: "Warehouse > Cold Storage Room 1"
- Name:
Cold Storage Temp - Room 1 - UUID:
A81758FFFE042ABC(from device label) - Integration Service: Select your LoRaWAN network server
- Active Timeout:
15minutes - Click Create
Setting Up Alerts:
- Open the newly created sensor
- Go to Profile → Status Thresholds → Edit
- Add Critical condition:
temperature > 6 - Add Warning condition:
temperature > 4 - 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:
- Register a humidity sensor with IoT asset type
- Set up thresholds:
- Critical:
humidity > 70ORhumidity < 30 - Warning:
humidity > 60ORhumidity < 40
- Critical:
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:
- Open any battery-powered IoT sensor
- Edit status thresholds
- Add conditions:
- Warning:
battery < 30 - Critical:
battery < 10
- Warning:
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:
- Check connection status — Open the device, look at "Last seen" timestamp
- Verify in network server — Confirm the device is transmitting in your LoRaWAN console
- Check Active Timeout — If set too short, device may appear inactive between readings
- Check UUID — Ensure the UUID in Infodeck matches the actual device EUI
- Check integration — Verify the Integration Service connection is healthy
- 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:
| Setting | Good For |
|---|---|
| 10-15 min | Devices sending data every few minutes |
| 30-60 min | Devices sending data hourly |
| 120+ min | Devices sending data daily |
Set timeout to 2-3x your device's reporting interval to avoid false "Inactive" alerts.
Supported IoT Protocols
Infodeck integrates with:
| Protocol | Description |
|---|---|
| LoRaWAN | Long-range, low-power sensor networks |
| AWS IoT | Amazon Web Services IoT Core |
| HTTP | Custom webhooks and REST APIs |
IoT Device Limits
| Plan | Max IoT Devices |
|---|---|
| Lite | 10 devices |
| Basic | 50 devices |
| Professional | 500 devices |
| Enterprise | Unlimited |
Related Articles
Need help? Contact Infodeck Support