CloudLocate Device-to-Service access using MQTT

Device to Service access - Step-by-Step Guide


Device-to-Service access allows to access to the service requesting the location estimation directly from your from your devices. This approach is preferred, for example,  whenever you do not want to implement additional logic server side to handle the location request.

The Location in the Cloud option offers additional saving of energy and data, by limiting the handshake with the device  and thus the on-time of the modem that consumes energy.


To use the service you need

Procedure overview

The mains steps of this procedure are

Here below an extensive explanation for each step.

Create a CloudLocate Thing

The first step is to create a CloudLocate Thing that provides you all the required parameters for the API:

The Thing let also you to:

Sign-in into the Thingstream portal and select the Location Things item from the Location Services section. Click the button to create a new Location Thing and browse to the CloudLocate section from where you can select the wizard to create CloudLocate Thing.  

During the creation steps you are suggested to assign a price plan. If you skip this step the Thing will not be automatically activated and cannot be used. When you are ready to assign a plan, open the Thing panel and assign the preferred one. A free developer plan is available.

Configure the MQTT client

RAW data shall be sent to the service using the MQTT protocol. 

CloudLocate/GNSS/request  (request topic)

CloudLocate/<deviceID>/GNSS/response  (response topic)

Send a measurement and get a position

The service supports multiple format:

In both cases to get a location you need to publish the RAW data in the request topic and subscribe to the response topic to get the estimated location.

Sample API response

A succesfull location response provides the position estimation as long as the date and time of the request, a copy of the RequestId if provided in input, and a LocationSource that indicates which source (Cellular, Wi-Fi or GNSS) have been used for the provided estimation.


    "Location": {

        "Lat": 51.496268,

        "Lon": -0.0949408,

        "Unc68": 27.0


    "DateTime": "2023-09-14T13:02:01",

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

    "LocationSource": "WiFi"


Location in the Cloud

The Location in the Cloud option allows you to save additional device energy and deliver faster the device location to the end user that might be your cloud application or another system/device using this information according to your business needs. 

As shown in the picture at the beginning of this slide, the RAW data can be sent by the IoT device to the service endpoint exactly in the same way just explained above. 

To send the estimated position directly to your cloud application, few additional step are required. 

There are many free MQTT client that you can use to do an initial tests. If you need support please contact

There are also several other options to retrieve the position server side  by using the http(s), sms, email, ftp, amqp functions embedded in Thingstream Data Flow Manager that allows also to manipulate and transform data in the most convenient way before delivering to your cloud application.

Zero Touch provisioning

If using the Device to Service access, when going in production it becomes complex to deal with MQTT credential configuration in the device as well as for  Location Things creation in the Thingstream platform, because these are all manual tasks.

To simplify and automate this activity you can refer to Zero Touch Provisioning solution.