Beyond reading telemetry, ICP can push configuration to your equipment through the edge gateway — writing a setpoint, pushing config, or rebooting a device. Every write passes through the remote device commands and write-safety controls that you operate.
Commands
Queue a command to a gateway. Command kinds:
| Kind | What it does |
|---|---|
| Set point | Write a value to a telemetry point |
| Config | Push a configuration change |
| Reboot | Restart a device |
| Custom | A device-specific command |
A command is pending until it's delivered, and you can cancel it while it's still pending. The result — success or error — is reported back and kept in the command history.
Write-safety gates
Writing to live equipment is deliberately guarded. Every write must clear all of these, which you control:
Site write-lockout is off
A site can be put into write-lockout to block all writes to it. Writes are refused while a site is locked.
Device write mode allows it
Each gateway has a write mode — Read-only, Write-enabled, or Lockout. It must be write-enabled.
The target asset is write-allowed
For a command aimed at a specific asset, that asset must be flagged write-allowed.
Operators can toggle a site's write-lockout, a device's write mode, and an asset's write-allowed flag as needed.
Warning
Pushing configuration to live infrastructure can affect service. The layered write-safety controls exist so a write only ever happens where you've explicitly enabled it — keep sites and assets locked down until you intend to change them.
Firmware updates
Signed firmware updates are delivered to gateways as part of fleet management, so the devices in the field stay current.