DALI · Interface guide
Cloud upload
The Cloud Upload tab of the Network page. The upload to Aeron Cloud (Live3), and Destinations that send the station's data to your own services.
Cloud Upload is the last tab on the Network page. It shows where the station sends its data and lets you add your own receivers.
Who can open it: Admin and Factory. Editing the Aeron Cloud connection is Factory only.
The tab has two cards: Aeron Cloud (Live3) and Destinations.
Aeron Cloud (Live3)
The station's upload to Aeron's own monitoring service. The station already knows where to send its data, so there is nothing to set up for normal use.
| Column | What it shows |
|---|---|
| Name | Aeron Cloud (the original upload), and on some stations Aeron Cloud New, a newer connection to Live3 that runs alongside the original while it is proven. |
| Type | HTTPS and the server address. |
| Data | Minute data, and 1-second data if it is turned on, with the upload interval. |
| Status | Delivering, Enabled, Disabled, Server unreachable, or Clock behind last send when the station's clock is earlier than the last upload. |
| Last delivered | When data last went through, or "never". |
| Waiting to send | Files waiting. A + means there are more than the count shows. |
| Button | Who | What it does |
|---|---|---|
| Enable / Disable | Admin, Factory | Turns the upload on or off. |
| Edit | Factory | Opens the connection settings (below). |
| Set up | Factory | Sets up Aeron Cloud New on a station that does not have it yet. |
Servers added with the original FTP / SFTP or HTTP uploaders appear in the Destinations list below, marked Legacy.
Edit Aeron Cloud (Factory)
| Field | Allowed values | What it does |
|---|---|---|
| Active | Yes or No | Same as Enable and Disable. |
| Upload Interval (min) | 1 to 1440 | How often the station uploads. |
| Send 1-sec data | Yes or No | Also upload the per-second data. |
| Server Address | Up to 128 characters | Where to upload. |
| Port | 1 to 65535 | The server port. |
| Retry Count | 0 to 10 | Retries after a failed upload. |
| Connect Timeout (s) | 1 to 120 | How long to wait for the server. |
Destinations
On firmware 4.1 and later, Destinations send the station's data to your own systems as well as to Live3: your own web service, Azure, AWS, an MQTT broker, an SFTP server or a TCP receiver. A station can have up to 16 destinations.
Destination list
The table has the same columns as the Aeron Cloud card. Status is one of:
| Status | Meaning |
|---|---|
| Delivering | Sending normally. |
| Retrying | The last attempt failed; the station is trying again. |
| Waiting for first send | Set up, nothing sent yet. |
| Disabled | Sends nothing while disabled. |
| Not running | The upload engine is not running on the station. |
| Not reporting | The upload engine has not reported on this destination recently. |
| Credentials refused | The service rejected the key, password or certificate. |
| Paused: server refusing data | The service keeps rejecting the data, so the station stopped for now. |
The Data column also estimates how much data the destination uses in a month. Under the status, the last error is shown if there is one.
| Button | What it does |
|---|---|
| + Add destination | Opens the destination picker. |
| Edit | Opens the destination's settings. |
| Test | Tries to connect with the saved settings, and shows Connected or Failed. |
| Disable / Enable | Stops or restarts sending. Disabling asks you to confirm, because the station may delete readings the destination has not received yet when its storage runs low. |
| Delete | Removes the destination and its stored credentials and certificates, after you confirm. Readings it has not received are not sent. |
Choosing a type
+ Add destination shows the types in three groups.
| Group | Type | What it sends to |
|---|---|---|
| Cloud platforms | Azure IoT Hub | Device-to-cloud messages to an IoT Hub device, over HTTPS with the device key or MQTT with an X.509 device certificate. |
| Azure Event Hubs | Events to an Event Hub with a shared access policy. | |
| AWS IoT Core | Messages to an AWS IoT thing with its device certificate, over MQTT (port 8883) or HTTPS (port 8443). | |
| Your own servers | HTTPS webhook | POSTs each batch to a URL you give. |
| MQTT broker | Publishes each batch to a topic (MQTT 3.1.1, QoS 1). | |
| SFTP | One file per batch in a folder on an SFTP server. | |
| TCP socket | Each batch written to a TCP connection, with or without TLS. | |
| Original uploaders | FTP / SFTP, HTTP (marked Legacy) | The older uploaders, kept for existing setups. Prefer the types above for anything new: the original FTP uploader does not check the server's identity, and the original HTTP uploader sends unencrypted. |
Settings every destination has
| Field | Allowed values | What it does |
|---|---|---|
| Name | Up to 64 characters | Your own label, shown in the list. |
| Minute data (logged readings) | On by default | The readings the station logs at its logging interval. What most people want. |
| 1-second data | Off by default | A reading every second. About 60 times more data; think twice on a cellular link. |
| Send every | 1 minute, 5 minutes, 15 minutes, 1 hour, 6 hours, 1 day | How often the station connects and uploads everything waiting. |
| Group readings into | Whatever is new at each send, or 1, 5, 15 or 60 minute blocks. Advanced. | How many minutes of readings go in one message. |
| Payload format | JSON, one object per reading (default); JSON with parameter names on every value; JSON, compact columns; Aeron Cloud JSON lines; CSV (same columns as a DALI download); Aeron Live3 ingest document. Advanced. | The shape of the data. Keep the default unless your receiver expects something else. |
| Compress (gzip) | Off by default. Advanced. | Much smaller uploads. The receiver must be able to unzip them. |
| Also send the parameter list | On by default. Advanced. | Sends parameter names and units, and again when they change. |
| Start from | Now (no history), the oldest reading stored on the station, or a date and time. Advanced, only when adding. | Whether to send history the station already holds. |
While you fill in the form, the page shows an estimate of the monthly data volume. Fields marked advanced are under the advanced settings.
Settings per type
| Type | Main fields |
|---|---|
| HTTPS webhook | URL (may include {{usn}} for the station serial, {{stream}} for interval or inst, {{kind}} for data or catalog), Authorization header (for example a Bearer token). Advanced: secret query string, method (POST or PUT), other headers, an Idempotency-Key header (on by default), server certificate authority, device certificate and key. |
| Azure IoT Hub | Connect with (HTTPS with the device key, or MQTT with an X.509 certificate), Hub host name (ends in .azure-devices.net), Device primary key or certificate. Advanced: device ID (blank uses the station serial). With the key, the station signs a fresh one-hour token for each message. |
| Azure Event Hubs | Namespace host name (ends in .servicebus.windows.net), Event hub name, Shared access policy name, Policy key. |
| AWS IoT Core | Device data endpoint (ends in .amazonaws.com), Topic (default aeron/{{usn}}/{{stream}}), Device certificate and key. Advanced: protocol, client ID. |
| MQTT broker | Broker host, Port (default 8883), Use TLS (on by default), Topic (default aeron/{{usn}}/{{stream}}), Username, Password. Advanced: client ID, largest message size. |
| SFTP | Server host, Port (default 22), Username, Sign in with (password or private key), Server host key fingerprint, Remote folder (must already exist). |
| TCP socket | Host, Port, Use TLS (on by default). Advanced: framing (4-byte length prefix, newline, or one connection per batch), the reply that means delivered. |
Turning TLS off on MQTT or TCP needs a tick confirming that the receiver is on a private network, because readings and passwords then travel unencrypted.
Passwords, keys and tokens are stored on the station and never shown again. To replace one, type a new value; to remove it, tick Remove the stored value. Certificates and keys are uploaded as PEM files, and the form then shows the file's fingerprint.
| Button | What it does |
|---|---|
| Add destination / Save | Stores the destination. |
| Test connection | Tries the settings in the form and shows which step failed, if any: looking up the host name, connecting, checking the server certificate, checking the server identity, or signing in. |
| Cancel | Closes the form. |
Confirming an SFTP server
Leave the host key fingerprint blank and press Test connection. The result shows the fingerprint the server offers. Compare it with the one the server's administrator gives you, and only enter it if they match. The station accepts ECDSA and RSA host keys, not Ed25519.
Banners on the Destinations card
| Banner | Meaning |
|---|---|
| The upload engine is not installed on this station yet. | The station's firmware predates Destinations. A firmware update installs it. |
| The upload engine is not running. | Destinations are kept, but nothing is sent until it starts again. |
| A red configuration error, with Restore the previous configuration (Factory) | The destination settings on the station could not be read. Restoring puts back the settings from before the last change. |
Messages you may see
| Message | What it means |
|---|---|
| A station can have at most 16 destinations. | Delete one before adding another. |
| Connection test failed / The credentials were refused. | The server answered but did not accept the settings. Check the key, password or certificate. |
| The server's identity does not match the fingerprint. | The SFTP server's host key is not the one you entered. Check with its administrator before going on. |
| Failed while connecting. | The station could not reach the server. Check the host, port and the station's internet connection. |