Skip to main content

Remote Command

Securely send SSH or HTTP instructions from the cloud to your IoT devices.

Copy/Save

Overview

Pricing for Remote Command will be announced at a later date. Until then, these APIs are available for free.

Remote Command enables downlink communications from the cloud to IoT devices.

Traditionally, cloud-to-device downlink communication has been challenging due to security concerns and network configuration complexities. Remote Command addresses these challenges by accepting SSH, HTTP, TCP, UDP or RTSP commands and associated data through the Soracom API, and securely transmitting the commands or data to devices via Soracom's secure private network. This architecture ensures a simple and secure communication channel.

With Remote Command, even legacy IoT devices can seamlessly integrate with the cloud as long as they accept communication over SSH, HTTP, TCP, UDP or RTSP. Furthermore, when combined with low-code development environments like Soracom Flux, it enables the creation of more sophisticated IoT systems, such as automatically sending commands to devices triggered by sensor data or cloud-based events.

A diagram illustrating Remote Command workflow between IoT devices and the cloud via Soracom API

Comparison with Other Features

Soracom offers multiple options for downlink communication. The table below compares Remote Command with other features:

FeatureRemote CommandSend SMS to DeviceSoracom NapterRemote Device Access using Soracom Gate
DescriptionSends commands or data to devices and receives execution results
Note: UDP only supports data transmission
Note: RTSP only supports snapshot capture
Sends data to devicesProvides on-demand remote access to devicesAllows continuous remote access to devices
Supported Communication ProtocolSSH, HTTP, TCP, UDP, RTSPSMSTCP such as SSH, HTTP, VNCAny
Max Data Size to Device
  • SSH: 8 KiB
  • HTTP: 5 MiB
  • TCP: 5 MiB
  • UDP: Approximately 1,400 B or less *1
  • RTSP: N/A (snapshot command only)
140 BUnlimitedUnlimited
Uplink Response to DownlinkHTTP, SSH, TCP, and RTSP (snapshot image) only-
Connection DurationUntil the API call completes-Until the on-demand remote access expiresPersistent
**\*1** - Although UDP theoretically supports up to 65,507 B, practical limitations restrict it to approximately 1,400 B or less depending on the network path. Data exceeding this limit may be dropped.

Remote Command has a 10-second timeout. If the device does not respond in time, the API returns a 422 HTTP error.

Use Cases

Remote Command is intended for the following use cases:

Use CaseDescription
Initial Parameter Setting (Provisioning)Set the necessary configuration for manufacturing and deployment (Wi-Fi settings, authentication credentials, sensor thresholds, etc.) for each device.
FOTA (Firmware Over-the-Air) UpdatesRemotely trigger firmware updates on devices, apply security patches, and add new features.
ONVIF-Compatible CamerasUse the ONVIF (Open Network Video Interface Forum) protocol to control pan-tilt-zoom (PTZ) operations on IP cameras.
Configuration ChangesModify settings of devices such as PLCs (Programmable Logic Controllers).
Accessing Device REST APIsInteract with REST APIs on IoT gateways to retrieve sensor data and control relays.
Industrial Equipment Control (e.g., Traffic Lights)Remotely control traffic lights in factories and warehouses (on/off, blinking, etc.).
IoT Lock/UnlockRemotely control electronic locks for remote access management.
Log CollectionRetrieve device operation logs and error logs for monitoring and analysis.
Accessing Other Devices on a Local NetworkUse the target device as a gateway to access other connected devices in the local network.
Alive MonitoringPeriodically check the operational status of devices and trigger alerts upon detecting anomalies.
Send data to devices in low-power mode with eDRXUDP is suitable for sending data remotely to devices even when they are in low-power mode. Refer to eDRX and PSM Timers.
TCP can also be used for similar use cases, but the device must wake up and respond within a maximum of 300 seconds after the Remote Command is sent.

Source IP Address

The source IP address for Remote Command varies depending on the connection type:

Connection TypeSource IP Address
Soracom Air100.127.10.16
Soracom Arc100.127.10.17

For Soracom Arc users, ensure that the WireGuard AllowedIPs configuration includes the source IP addresses above.

Search Esc to close / Enter to view results