Downlinks tab on every asset
Add, edit, delete and send named downlinks. Choose template fields (Default) or your own encoder code (Custom).
Platform · Downlinks
Remote device control with LoRaWAN downlinks
Close a valve, switch a relay or change a thermostat setpoint from Widgelix. Define the command once, then send it with one click from a dashboard or let an Action send it automatically when a condition is met.
Define once
commands live in the asset template
One click
from the asset page or a dashboard
Automatic
as a response in Actions
The problem
Monitoring without control means someone has to drive there
A leak sensor that only sends an alert still needs a person to close the valve. Many platforms show data but leave commands to the network server console, where encoding payloads by hand is slow and error-prone.
- Commands are built by hand in network server consoles
- Operators need to know device-specific byte formats
- Alerts arrive, but nothing happens until someone acts
- Control and monitoring live in different tools
How it works
From command definition to closed-loop control
- 01
Encode once in the template
A JavaScript downlink encoder in the asset template turns a JSON command into the bytes the device expects. Test it in the built-in console.
- 02
Name your commands
On the asset's Downlinks tab, add named downlinks such as “Close valve” or “Relay on”. They are stored on the template, so every asset of that model gets them.
- 03
Send manually or automatically
Click Send on the asset page, use a Downlink Button widget on a dashboard, or add a Downlink response to an Action.
Capabilities
Control built into the platform
Commands use the same templates, dashboards and Actions as your monitoring.
Downlink Button widget
Put a coloured button for any command on asset or site dashboards, so operators control devices without opening settings.
Downlinks in Actions
An Action can send a downlink when its conditions are met, and the target can be a different asset from the one that triggered it, for example a leak sensor closing a valve controller.
Class A devices
“Activate after uplink” queues the command to be sent right after the device's next uplink, when Class A devices listen.
Use live data in commands
“Pass payload data to downlink” lets the command include values from the device's payload.
Downlink encoder with test console
Write the encoder in JavaScript, run it against a sample JSON command and check the HEX output before saving.
Works through the network you use
Downlinks are sent through The Things Stack, Actility ThingPark, Helium, LORIOT, Loxone Miniserver and the GreenMesh LoRaWAN Network Server, with the fPort you configure per integration.
See all integrations
At a glance
Downlink features
| Where commands live | Asset template (shared by all assets of the model) |
|---|---|
| Encoding | JavaScript encoder: JSON command → HEX payload, with test console |
| Manual sending | Asset Downlinks tab, Downlink Button widget |
| Automatic sending | Downlink response in Actions, to the same or another asset |
| Options | Activate after uplink, pass payload data to downlink |
| Integrations | The Things Stack, Actility ThingPark, Helium, LORIOT, Loxone, GreenMesh LNS |
“When the leak sensor in the plant room reports water, send “Close valve” to the main shut-off controller and notify the facility team.”
Remote control in practice
Questions about downlinks and remote control
+Which networks support downlinks in Widgelix?
The Things Stack, Actility ThingPark, Helium, LORIOT, Loxone Miniserver and the GreenMesh LoRaWAN Network Server. Other integrations deliver uplink data only.
+Do I need to know the device's byte format?
Only once, when writing the downlink encoder in the asset template. After that, operators send named commands like “Close valve”.
+Can a sensor trigger a command on a different device?
Yes. A Downlink response in an Action can target any asset, so a leak sensor can close a valve controlled by another device.
+How does it work with Class A devices?
Turn on “Activate after uplink” so the command is sent after the device's next uplink, when it is listening.
More platform features
IoT Alerts & AutomationActions that react to sustained real-world conditions, not noisy single readings.Payload DecodersHow asset templates work, and how to write your own JavaScript decoder for any device.IoT DashboardsNo-code dashboards for every device, site and role, with 20+ widget types.Geofencing & GPS TrackingAssets on a live map, route history and alerts when something enters or leaves an area.IntegrationsThe Things Stack, ChirpStack, Actility, LORIOT, Helium, Sigfox, MQTT, webhooks and more.
Close the loop between sensors and actuators
Tell us which devices you need to control and when. We'll show you downlinks and automatic responses on your own hardware.
- Encoder check for your actuators
- Dashboard buttons for operators
- Actions that act without a human in the loop