English 
Français 
Español 
Deutsch 
Português 
Italiano 
العربية Remote Control
Remote device control that proves the device acted
Define typed commands once, send downlink commands over MQTT or LoRaWAN, and operate everything from dashboard widgets or autonomous rules. Kilo tracks every execution until the device reports the state you asked for.
Device Commands
Downlink commands over MQTT and LoRaWAN
A command is a named action with typed parameters — define it once, run it from anywhere.
Switch a relay, dim a luminaire, push a new setpoint, open a valve. Every command carries typed parameters — integers and floats with min/max limits, strings with allowed values, booleans — so an operator can never send a value the device would reject.
The same command concept covers an MQTT message to a smart plug and a LoRaWAN downlink to a Class C controller, which listens continuously and receives commands immediately. Kilo handles encoding and delivery for each — and a built-in encoder test shows the exact bytes before anything reaches a device.
app.kiloiot.io · Control widgets
Real productTyped parameters
Min/max limits, allowed values, and defaults — an invalid value never leaves the platform.
MQTT & LoRaWAN routing
Publish to a broker topic or address a LoRaWAN fPort, with optional confirmed downlinks.
Test before you send
Preview the encoded payload as hex and Base64, with size and logs, before saving.
Full execution history
Every dispatch is recorded with its outcome — a complete record of control activity.
Control Widgets
Six control widgets for IoT device control on any dashboard
Bind a widget to a device command and anyone with dashboard access can operate the device — right next to the readings that tell them whether they need to.
Switch
Flip a lasting two-state condition — pump on or off, valve open or closed — and see which state is actually active.
Button
Fire a one-shot action: reset a controller, trigger a calibration, start a process. One press, one command.
Simple Slider
Drag a horizontal track to set a numeric value — a fan speed, a dimming level, a setpoint.
Circular Slider
Set a headline value on a radial dial with an instrument feel — color temperature or valve position.
Vertical Slider
An upright track that reads like a level — tank-fill targets and values you picture by height.
Input
Type an exact value and press Apply — for setpoints and thresholds where precision matters.
Every control follows the device's reported metric, so it shows the real state — not just the last command sent.
Widgets are disabled when the device is offline — they never send into the void.
Closed-Loop Verification
Remote device management with confirmed execution
A downlink can be accepted for delivery and still never change the physical device. That's why every Kilo command can carry a verification strategy: wait for the device's next uplink, or actively query it after the acknowledgment — and match its reported state against what you expected.
An execution is only marked Confirmed when the reported values match — "set brightness to 60" is verified by the device reporting brightness 60. Everything lands in the execution history, with a plain-language reason behind every outcome.
Execution history
-
Pending
In flight: the command has been dispatched and is moving through delivery and verification.
-
Confirmed
Verified success: the device's reported state matched what was expected.
-
Failed
The command didn't go through — with the reason in plain language, from a full downlink queue to an offline device.
Autonomous Control
Rules that act: the full sense → decide → act loop
The Rules Engine can dispatch the same commands automatically with an Execute Command node. A leak sensor trips at 3 a.m. — the rule shuts the valve in the same evaluation that detected the leak, then raises the alarm so the team knows it happened.
Parameters can be computed from the very reading that triggered the rule, so one rule reacts to a threshold and responds proportionally. And because the rule uses the standard command pipeline, verification and execution history apply to every autonomous action too.
Sense
A condition is met — a leak detected, a temperature drifting out of range, a tank hitting its high mark.
Act
The rule sends the command itself: close the valve, push a lower setpoint, shut the inlet.
Notify
The same rule raises the alarm, so the problem is contained and the right people still know.
Keep exploring
Control is one part of the platform
FAQ
Remote control FAQ
Which devices can I control remotely?
Any device connected over MQTT, and Class C LoRaWAN devices. Class C devices listen continuously, so downlink commands reach them immediately; Class A devices only open a brief receive window after each uplink, so they aren't eligible for on-demand control.
How does Kilo verify that a command worked?
Per command you choose a strategy: wait for the device's next uplink, or send a query right after the acknowledgment. Either way, the device's reported state is matched against the values you expect — an execution is only marked Confirmed on real evidence.
What happens when a device is offline?
Dashboard control widgets are shown disabled, and the device page warns you before you send. Queued commands are delivered automatically when the device reconnects, so control intent isn't silently lost.
Can rules send commands without a person in the loop?
Yes. The Execute Command node dispatches any defined command when a rule's conditions are met, with parameters as fixed values or expressions computed from live readings. The same validation, verification, and execution history apply.
Stop watching. Start acting.
Connect a device, define a command, put a switch on the dashboard — and let Kilo confirm every action took effect. Free for 5 devices.