Skip to main content

How to Send Downlink Commands

Send configuration commands (downlinks) to your IoT devices to change settings, trigger actions, or request data.

Quick Summary

Open any IoT device, find Downlink Action in the Data Overview tab, select an action from the dropdown, and click Send.

Before You Begin​

Requirements
  • Device must be online or able to receive queued commands
  • Asset Type must have Actions defined
  • Your Integration Service must support downlinks
  • You need permission to manage IoT devices

Downlink commands are messages sent to your IoT device (opposite of uplinks which come from the device).

Common uses:

  • Change reporting interval
  • Adjust sensor thresholds
  • Trigger immediate reading
  • Reset device configuration
  • Control actuators (relays, switches)

Step 1: Open the Device​

  1. Click the Settings gear icon in the sidebar
  2. Select IoT Management from the dropdown
  3. Click on the device name
  1. Go to the Data Overview tab
  2. Locate the Downlink Action section

Step 3: Select and Send​

  1. Click the Action dropdown
  2. Select the command you want to send
  3. Click Send

You'll see:

  • ✅ "Send successful" — Command queued
  • ❌ "Send failed" — Check connectivity

Understanding Actions​

Actions are defined in the Asset Type:

Action PropertyDescription
NameAction label (e.g., "Set Interval 5min")
fPortLoRaWAN port number (1-223)
ConfirmedWhether delivery confirmation is required
Payload TypeHexString, JSON, or Base64
PayloadThe command data

Reporting Interval​

ActionEffect
Set Interval 5minDevice reports every 5 minutes
Set Interval 15minDevice reports every 15 minutes
Set Interval 1hrDevice reports every hour

Sensor Configuration​

ActionEffect
Set Threshold High 30°CAlert when temp > 30°C
Set Threshold Low 0°CAlert when temp < 0°C
Enable Motion DetectionTurn on motion sensor

Device Control​

ActionEffect
Request StatusDevice sends immediate uplink
Reboot DeviceRestarts the device
Factory ResetRestores default settings

Real-World Examples​

Example 1: Increase Reporting Frequency​

Situation: A cold storage sensor reports every hour, but you need more frequent readings during a heat wave.

Solution:

  1. Click the Settings gear → IoT Management
  2. Find the cold storage temperature sensor
  3. Open device details → Data Overview
  4. In Downlink Action, select "Set Interval 5min"
  5. Click Send
  6. Wait for the next uplink (within current interval)
  7. Verify device now reports every 5 minutes

Result: You now receive temperature updates every 5 minutes to closely monitor cold storage during the heat wave.

Example 2: Trigger Immediate Reading​

Situation: You just repaired an HVAC unit and want to verify the temperature sensor is working before leaving.

Solution:

  1. Go to Settings gear → IoT Management and open the HVAC temperature sensor
  2. Find Downlink Action
  3. Select "Request Status" or "Force Uplink"
  4. Click Send
  5. Wait 30 seconds to 2 minutes
  6. Refresh the page
  7. Check if new data appears in Last Message

Result: Device sends an immediate reading, confirming it's operational without waiting for the normal interval.

Example 3: Adjust Alert Threshold​

Situation: A server room sensor alerts at 25°C, but after upgrading cooling, you want to set it to 28°C.

Solution:

  1. Find the server room sensor
  2. Open device details
  3. In Downlink Action, select "Set Threshold High 28°C"
  4. Click Send
  5. Confirm success message

Result: The device now alerts only when temperature exceeds 28°C, reducing false alarms.

Example 4: Control a Smart Relay​

Situation: You need to remotely turn on a ventilation fan connected to a smart relay.

Solution:

  1. Go to Settings gear → IoT Management and find the smart relay device
  2. Open device details
  3. In Downlink Action, select "Turn On Relay 1"
  4. Click Send
  5. Verify the fan starts (via camera or site visit)

Result: Ventilation fan turns on remotely without requiring someone on-site.

When Commands Are Delivered​

LoRaWAN Class A Devices (Most Common)​

  • Commands are queued on the network server
  • Delivered on the next uplink from the device
  • If device reports every 15 minutes, command arrives within 15 minutes

LoRaWAN Class C Devices​

  • Devices listen continuously
  • Commands delivered immediately (within seconds)
  • Higher power consumption

Command Queue​

Commands remain queued until:

  • Device receives them (on next uplink)
  • Command expires (typically 24-48 hours)
  • You send a new command (may replace the queue)

Troubleshooting​

Command Not Working​

IssueCauseSolution
"Send failed"Network errorCheck Integration Service status
Command queued but no effectDevice offlineWait for device to come online
Wrong behaviorIncorrect actionVerify Asset Type action definition
No actions availableActions not definedAdd actions to the Asset Type

Verifying Command Delivery​

  1. Note the current settings
  2. Send the command
  3. Wait for next uplink (check Last Message time)
  4. Verify settings changed via device response or behavior

Adding Custom Actions​

To add new actions to a device type:

  1. Go to Settings gear → Asset Type
  2. Find and edit the asset type
  3. Scroll to Actions section
  4. Click Add Action
  5. Configure:
    • Name: Descriptive label
    • fPort: LoRaWAN port (check device documentation)
    • Confirmed: Whether to require acknowledgment
    • Payload Type: HexString, JSON, or Base64
    • Payload: Command data
  6. Save the asset type

All devices of this type now have the new action available.

Payload Types​

TypeFormatExample
HexStringRaw bytes as hex01050F
JSONStructured data{"interval": 300}
Base64Base64 encodedAQUv

Check your device's documentation for the correct format.

Need help? Contact Infodeck Support

Was this page helpful?