CloudLocate premium extension

The  logic behind a flow is that:

• all devices (Things) send the data to the platform on a given MQTT topic using one of the above mentioned Communication services

• thejust created flow subscribe to this given topic using the thingstream subscribe node. All data that comes on this topic, triggers the execution of the flow. Of course the device can publish data also on other topics not connected to that flow

• you can connect multiple nodes, with a simple drag and drop, creating complex functions and logic, manipulating data before sending it to your cloud application, and using multiple channels (SMS, mail, MQTT, https, ftp etc) to send out data.

Simulate a device

After that you have created the above flow, as next step you need to simulate your device to be able to inject/publish data in the flow and trigger the execution. The easiest way to do that is to create an IP Thing (you can also create more than one to simulate a fleet): 

• Select the Communication Things item on the left sidebar 

• Click on Add Thing and then on 'Add new IP Thing'; give it a name

• Select a plan. For test purpose you can select the developer plan

In the credential section of each IP Thing you can find the MQTT credentials and endpoint. Use these information to configure an MQTT client in your laptop o in your real device.

In the next steps you will get also the information about the topic to be used to publish data

In the following sections you can get more information about each node used in the sample flow in the picture

Thingstream inject node

This node is used to test the flow by injecting sample data directly to the flow from the user interface (just filling the proper fields in the configuration panel of the node). This is very helpful as a very first step, especially if you do not have an MQTT client in your PC/device

 You can position this node anywhere in your flow and use it to test without the need to deploy the flow. 

To configure this node, double-click on it:

1.  In the search field type the name of the IP thing that you have just created before to filter the list of the Things available in the box below and select it

2. specify the MQTT topic where your message would be published to . This is a mandatory field for this node,  but for the on going test you can specify any topic/string, like 'CloudLocate/mytestopic'

3. select JSON as Payload Format

4. give a JSON payload of the measurement (you can simply copy and paste the sample measurement given here below)

5. Click "Save Flow" to save your changes

To run this node, simply click on the filled square on the left-hand side of the node. You'll be able to review any debug output in the debug tab on the right-hand side of the editor.

Before running the flow, you will be asked to save it (the Save button is on the top right of the editor window).

{

"RequestId": "82cb34c9-88c9",

"GNSSMeasurements": {

"Payload":"tWIChjIAG/M7CcimDqBmvpr+A9pGYVEPdxhiyIqPToNAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAyAA==",

  "DateTime": "2023-04-05T12:50:16"

 }

}

Thingstream subscribe node

Instead of using the 'thingstream  inject'  node, in a real use case you want to send the measurement from your devices. This node acts as an input to the flow.

This subscription represents the MQTT topic(s) that will trigger the flow when a message from a device  is pushed on that topic.  In other wards, all the devices shall publish the raw measurements into this topic. 

The topic selection happens during the flow deployment phase: you will be asked to create a subscription for this node. You can change the topic at any time by clicking on Manage button

CloudLocate node

This node calls the CloudLocate service to calculate a position based on incoming measurement data.  The result becomes an input to the next node in the flow.

The node accepts the input in two format:

1. a pure binary payload:

2. the JSON format with or without date and time field, depending if you are sending fresh data or measurements generated more  than 60 seconds ago

   • the body shall contain the Base64 encoded measurements.

Set email recipient (function) node

This JavaScript function node can be used to set an email address to be used by the email node by using the following code

/* 

Set the email "to" address to the 

domain owners email address.

*/

msg.to = msg.domainOwner.email;

return msg; 

You can also specify any email address if you want to send an email to a recipient other than the domain owner, like:

msg.to ="me@mydomain.com";

return msg; 

You need to add the above code in the function node by double-clicking on the node to open the configuration options and click "Done" to save your changes.

Msg.payload (debug) node

This node is used for debugging purposes.  It will output debug data to the "debug" tab on the right-hand side, so that you can immediately see if the position has been calculated

Email payload node

This node will send an email with the estimated position.  You don't need to configure the email recipient details directly in the node as they are set in the previous JavaScript function node.

Deploy and test the flow

When you have finished setting up and testing your flow with the thingstream inject node, you can deploy the flow to start using it with real devices. For detailed information about deploying Flows, have a look at the Flows documentation. The steps are listed here in summary:

1. Click "Deploy" at top right corner of the screen

2. In the panel that appears, click "Edit" in the "Subscription" option to configure it. 

   • Enter the topic that your device will publish to.  If the topic already exists it will appear in the search results, otherwise just click Add and create a new one, like for example 'Mytest/MyTopic'.

3. Click "Done"

4.  Click "Deploy" to deploy the flow.

5. You'll see a warning that the flow contains premium extension nodes with a link to the pricing page for details of the costs.  

6. If you're fine, click "Deploy".  

You can see the topic (i.e. 'Mytest/MyTopic') that the flow is subscribed to at the top of the editor screen. To change it, use the manage button at the top-right corner and repeat the procedure