Libelium's Cloud Air Quality Station Service
You can use the Libelium's Air Quality Station Service to configure your nodes and to receive data from them. Using the Air Quality Station Service, you do not need any software infrastructure on your side.
The Air Quality Station Service can be understood as one of the services that we offer on our Libelium Cloud (officialy called Services Cloud Manager - SCM). Other services hosted on the SCM are the Programming Cloud Service or the Bridge. The SCM permits devices management and allows access to the different services. The Air Quality Station Service includes the Remote Configuration Form to manage the configuration values of the Air Quality Station nodes, that deals with the LoRaWAN network server requests, sending back a response if needed. The data sent from the Air Quality Station devices will be sent to any compatible final IoT cloud service (Amazon Web Services, Microsoft Azure, etc) using the Libelium's Bridge service (you will need a license to use the Bridge).

Air Quality Station Service

Once logged on the Services Cloud Manager, users can access the Air Quality Station Service by clicking on the "Air Quality Station" button on the left-side menu under the section.
Figure: Accessing the Air Quality Station Service
Once the user has acceded the following features will be available accessing the Air Quality Station Service: configure nodes remotely, OTA, configure the LoRaWAN service, check the logs for the configured service and generate the tokens and keys needed for the LoRaWAN network server.
Figure: Air Quality Station landing page

Remote configuration

This tab shows a drop-down menu to select one or several devices. Each one is identified by their unique Serial ID. The nodes displayed in the drop-down menu correspond to the nodes you have claimed for on your Services Cloud Manager account. You can also deselect previously selected nodes using the cross in the node's identification.
Once a node or more are selected, the current configuration of this node is displayed and you can modify it.
Figure: Drop-down node selection
Figure: Node params configuration
The Params section allows the user to update the "Loop Time" parameter just as the Smart Devices App does. However, using the Smart Devices App requires physical access to the node: it must be plugged to your computer via a USB cable.
Once you have selected the desired loop time for the selected node or nodes, press the update configuration button to apply the configuration. A message will appear confirming that a configuration change has been requested.
Figure: Configuration change was requested message
The next time the device sends data to the Cloud (in any of the communication modes: LTE or LoRaWAN), the new configuration will be downloaded, applied and saved into the device. Notice that configurations are only performed when LTE is properly configured in the node.
Remote Configuration Form does not permit to update any LoRaWAN parameter. The Smart Devices App must be used instead.

Over the Air programming (OTA)

The OTA feature permits to perform over-the-air updates that will change its firmware version. These updates are released by Libelium and are intended to improve the device software with new features and functionalities.
There are 2 OTA possibilities:
    Immediate: OTA is triggered the next time the device sends data.
    At programmed time: OTA is triggered at a specified timestamp.
In the control panel, the user can see the current reported firmware version and the state of OTA updates.

"Firmware up to date" status

When there is no pending OTA to be applied, you will see the next indication in the control panel:
Figure: "Up-to-date" message

"OTA available" status

The next status is displayed when the Air Quality Station device has been enabled to upgrade a new firmware version by Libelium administrator. However the OTA action is pending to be triggered. The user has the ability to trigger the OTA programming immediately or at a desired time.
Figure: "Immediate" OTA
Figure: "At programmed time" OTA

"OTA requested" status

This status is triggered after the user clicks on the "Request OTA" button. Thus, over-the-air programming will be performed by the device following the corresponding method (immediate or programmed).
Figure: "OTA requested" status

"OTA in progress" status

When the Air Quality Station Node receives the command to perform an OTA upgrade, it sends a new status to the Cloud just before entering the Bootloader to perform a flash memory upgrade.
Figure: "OTA requested" message

When OTA is finished...

When the OTA operation finishes the Control panel shows you the "Firmware up-to-date" status indicating that the process has finished.
Figure: "Up-to-date" message

Reboot device

The user has the ability to remotely reboot a device at anytime. After a reboot the node reports current state, firmware version, and gets notified of new OTA update requests. This operation is needed when a new Sensor Cartridge is connected.
Figure: Reboot Device
Once the button is pressed, a message will appear in a pop-up window indicating that the process has been carried out correctly.
Figure: "Reboot requested" message
When you have closed the confirmation window after requesting the reboot of the device, a message will appear indicating the date and time the reboot was requested.
Figure: Rebooting device

Node's hardware information

Once you have turned on the Air Quality Station node, it will automatically detect the sensors installed in the device.
A list of all available sensors will be displayed. Red color indicates that the device is not connected, and green color indicates that the sensor is connected and functional.
Figure: Node's hardware information view
If you have selected 2 or more devices, this section will not be available and a message is displayed showing that this section is only avaiable on single node selection.
Figure: Node's hardware information is unavailable

Node's software Information

As in the "Hardware information" section, once the node has been turned on, made a firmware update or a change in the Radio Configuration Mode, it will be notified showing the current status of the node.
Figure: Node's software information view
If you have selected 2 or more devices, this section will not be available and a message is displayed showing that this section is only avaiable on single node selection.
Figure: Node's software information is unavailable

LoRaWAN Service Configuration

Configuration

The Air Quality Station Service is compatible with the following LoRaWAN Network Servers: Loriot, The Things Network (TTN) and The Things Industries (TTI).
These are the URLs to be configured on the LoRaWAN Network Server:
Note: Only one of these services can be active at the same time.
If you want to use Loriot as your LoRaWAN Network Server, you have to select it on the drop-down menu and complete the required fields. To find the information on the Loriot panel, you can follow the instructions described on "How to configure Loriot" the section.
Figure: LoRaWAN parameters config panel, Loriot
If you want to use TTN as your LoRaWAN Network Server, you have to select it on the drop-down menu and complete the required fields. To find the information on the TTN panel, you can follow the instructions described on the "How to configure The Things Network (TTN)" section.
Figure: LoRaWAN parameters config panel, The Things Network
Please, be aware that there are a set of regions to choose, click on the regions dropdown to see all choices. The current regions to send the data are:
    Europe: Uses value ttn-eu
    USA: Uses value ttn-us-west
    Brazil: Uses value ttn-brazil
    Asia: Uses value ttn-asia-se
For further information about TTN regions, please see TTN documentation.
If you want to use TTI as your LoRaWAN Network Server, you have to select it on the drop-down menu and complete the required fields. To find the information on the TTI panel, you can follow the instructions described on the “How to configure The Things Industries (TTI)" section.
Figure: LoRaWAN parameters config panel, The Things Industries
Regardless of the service you have configured, click the button to save your LoRaWAN service configuration. Then a message will be displayed indicating that the service has been updated or saved correctly.
Figure: "Service configuration saved" message

Authentication token for HTTP integration with TTN

The Air Quality Station Service uses tokens for authentication. The user must 1st create a token (an API key) and then use it on TTN.
The first thing you will have to do is create an authentication token for that go to "Generate Token setion" on Token for Loriot Services step to know how to create one.
Step 1: Paste the API key on the "Authorization" field of HTTP TTN integration. This field must have: Bearer CLOUD_LIBELIUM_TOKEN.
Figure: Step 4 - Authorization field on TTN HTTP integration

Authentication token for HTTP integration with TTI

The Air Quality Station Service uses tokens for authentication. The user must 1st create a token (an API key) and then use it on TTI.
The first thing you will have to do is create an authentication token for that go to "Generate Token setion" on Token for Loriot Services step to know how to create one.
Step 1: Paste the API key on the "Authorization" field of HTTP TTI integration. This field must have: Bearer CLOUD_LIBELIUM_TOKEN.
Figure: Step 1 - Authorization field on TTI HTTP integration

Connector Information

On the right side of the "Remote Configuration" tab you will find the information regarding the configuration of the active connector. Among them we can see if the connector is active or stopped. The name of the selected service as well as the date the connector was last updated.
Figure: "Show logs" button

Logs

The "Logs" tab shows the information and error messages registering the result of the communication requests of the LoRaWAN services. Different communication protocols are used to configure the service. All messages related to the transport layer of the service are identified as INFO or ERROR. User intervention may be required to analyse the meaning of the messages generated in the application layer and decide if some actions are required.
Figure: LoRaWAN logs
Click the button to update the log view and load new messages available. The latest messages appear at the bottom of the viewer.
Figure: "Refresh" button
If you want back to connector configuration, simply presh de "Back to Configuration" button.
Figure: "Back to Configuration" button

API keys

The "API Keys" tab allows users to generate API keys to authenticate the device when sending data to Libelium Cloud SCM. The API key is mandatory and must be configured in the Air Quality Station Node via USB wire as explained in the "Smart Devices App" section.
Also, the API keys are needed to configure your Loriot network server correctly when using LoRaWAN radio module instead of the LTE module.
Figure: API keys panel

How to create a new API key

Finally, a new key must be generated clicking on the "Create New Key" button:
Figure: "Create new key" button
A pop-up window will be displayed, in which users must introduce a name to identify the new key. Then, clicking the button shows two keys in a new window, ready to be used in the Loriot service or the Smart Devices App.

API key for Loriot services

The first one is to be able to configure the Loriot service.
Figure: API key for Loriot service

API key for the Smart Devices App

The 2nd one is necessary to be able to configure the device through the "Smart Devices App" to be able to use the device to send data to the Libelium Cloud.
Figure: API key for the Smart Devices App
Last modified 4mo ago