DALI · How-to guides

Send data to your cloud

Add a destination so the station sends its readings to your own web service, Azure, AWS, an MQTT broker, an SFTP server or a TCP receiver.

Goal: on firmware 4.1 and later, the station sends its readings to your own system as well as to Live3, and the destination shows Delivering.

Before you start

You need the Admin role.
Firmware 4.1 or later. On older firmware the Destinations card says the upload engine is not installed.
The receiving side set up, and its details to hand. For example a webhook URL and token, an Azure IoT Hub host name and device key, an AWS IoT endpoint and device certificate, or an SFTP host, login and host key fingerprint. What each type needs is on Cloud destinations overview.
Internet on the station.

Steps

1
Open Destinations. Go to Network, Cloud Upload tab. The Destinations card is under Aeron Cloud.
2
Pick a type. Click + Add destination and choose the type: Azure IoT Hub, Azure Event Hubs, AWS IoT Core, HTTPS webhook, MQTT broker, SFTP or TCP socket.
3
Fill in the connection. Give it a Name, then the fields for that type. Certificates and keys are uploaded as PEM files. Keep TLS on unless the receiver is on a private network.
4
Choose what and how often. Minute data (logged readings) is on by default; turn on 1-second data only if you need it, as it is about 60 times more data. Set Send every. Under the advanced settings you can change the payload format, compression and Start from (now, the oldest reading stored, or a date and time).
5
Test. Click Test connection. If a step fails, the result says which: looking up the host name, connecting, checking the certificate or identity, or signing in.
6
Save. Click Add destination.

Check it worked

In the destination list, Status moves from Waiting for first send to Delivering, and Last delivered shows a time. The same row appears on the Dashboard under Destinations. Check that data arrives on your side.

If something goes wrong

Status or message	What to do
Credentials refused	Check the key, password or certificate.
Failed while connecting.	Check the host, port and the station's internet.
The server's identity does not match the fingerprint.	For SFTP, check the host key with the server's administrator before going on.
Paused: server refusing data	The receiver keeps rejecting the data. Check its logs and the payload format it expects.
Retrying	The last attempt failed and the station is trying again.
A station can have at most 16 destinations.	Delete one before adding another.

Confirming an SFTP server

Leave the host key fingerprint blank and press Test connection. The result shows the fingerprint the server offers. Enter it only if it matches the one the server's administrator gives you.