Back to monogoto website

Ubidots

Integrate IoT data with Ubidots

Ubidots is an IoT platform, allowing IoT developers to rapidly assemble and launch applications without having to write complicated code. It supports multiple protocols to integrate data, including UDP, TCP, HTTP(S) and MQTT.

Quick Navigation

Prerequisites

  • Monogoto SIM

  • Access to an IoT modem

  • Account on Ubidots

Set up your Ubidots account

You can get started with Ubidots free of charge by signing up for a STEM account.

In order to send data to Ubidots, you need the following parameters to create the data string:

  • Ubidots Token starting with BBFF e.g. BBFF-ABCDEFGHIJKLMNOPQRSTUVWXYZ0123 You can find your token when selecting your profile in the top-right corner and select API Credentials.

  • User agent You can think of name that will help you identify the IoT application you are working on, e.g. iotfleet1

  • Device Label e.g. iot-sensor The device label is the name of your device as registered in Ubidots. Visit your Devices page in the Ubidots console, and select the + sign at the top right corner to add a new device and provide its name.

Send data using UDP

The example below is created for the u-blox SARA R412 modem. When using a different IoT modem, have a look at the AT Commands manual of your modem vendor as the commands might slightly differ.

Detailed information about using UDP to integrate data, see the Ubidots API documentation.

In order to send data using UDP, 3 AT Commands needs to be sent:

  1. Create UDP socket AT+USOCR

  2. Connect socket AT+USOCO

  3. Send UDP data AT+USOST

1. Create UDP socket

AT Command:AT+USOCR=<protocol> Replace <protocol> with 17 for UDP, use 6 for TCP.

AT+USOCR=17

Example response: +USOCR: 0

2. Connect socket

AT Command:AT+USOCO=<socket>,"<remote_addr>",<remote_port>

  • Replace <socket> with an identifier, e.g. 0

  • Replace <remote_addr> with Ubidots' IP address or domain name: 169.55.61.243, or industrial.api.ubidots.com

  • Replace <remote_port> with 9012 (no TLS) or 9812 (TLS)

To connect your IoT modem to Ubidots without TLS, use the following command:

AT+USOCO=0,"169.55.61.243",9012

Expected response: OK

3. Send UDP data

In order to send data to Ubidots, you need the following parameters to create the data string:

  • User agent, e.g. iotfleet1

  • Ubidots Token e.g. BBFF-ABCDEFGHIJKLMNOPQRSTUVWXYZ0123

  • Device Label e.g. iotsensor

  • Variable Label e.g. temperature

  • Value e.g. 21

To send data to Ubidots, a data string needs to be created with all the parameters discussed above:

{user agent}|POST|{token}|{device label}=>{variable label}:{value}|end

For example:

iotfleet1|POST|BBFF-ABCDEFGHIJKLMNOPQRSTUVWXYZ0123|iotsensor=>temperature:21|end

AT Command The AT Command to send UDP data is:

AT+USOST=<socket>,"<remote_addr>",<remote_port>,<length>,"<data>"

When adding all the parameters to the AT Command, the command becomes:

AT+USOST=0,"169.55.61.243",9012,80,"iotfleet1|POST|BBFF-ABCDEFGHIJKLMNOPQRSTUVWXYZ0123|iotsensor=>temperature:21|end"

Expected response: +USOST: 0,80

Make sure to exactly count the number of characters you send, or you will receive an error.

If all went well, the Ubidots platform will visualize and store your data:

Send data using HTTP

The example below is created for the u-blox SARA R412 modem. When using a different IoT modem, have a look at the AT Commands manual of your modem vendor as the commands might slightly differ.

Detailed information about using HTTP(S) to integrate data, see the Ubidots API documentation.

In order to send data using HTTP, 4 AT Commands needs to be sent:

  1. Set the HTTP base url AT+UHTTP

  2. Set custom headers AT+UHTTP

  3. Create a JSON file containing the data you want to send AT+UDWNFILE

  4. Send data AT+UHTTPC

1. Set the HTTP base url

AT Command:

AT+UHTTP=<profile_id>,1,"<param_val>"

  • Replace <profile_id> with an identifier, e.g. 0

  • Replace <param_val> with Ubidots' IP address or domain name: industrial.api.ubidots.com

The AT Command becomes:

AT+UHTTP=0,1,"industrial.api.ubidots.com"

To test if the base url was set correctly, enter: AT+UHTTP=0,1. Expected response:

+UHTTP: 0,1,"industrial.api.ubidots.com"
OK

2. Set custom headers

AT Command:

AT+UHTTP=<profile_id>,0,"<param_val>"

  • Replace <profile_id> with the same identifier you used before, e.g. 0

  • Replace <param_val> with a counter, going up for each new header you set, followed by the custom header, e.g. "0:X-Auth-Token:BBFF-ABCDEFGHIJKLMNOPQRSTUVWXYZ0123"

Set the first header, containing the Ubidots authentication token:

AT+UHTTP=0,9,"0:X-Auth-Token:BBFF-ABCDEFGHIJKLMNOPQRSTUVWXYZ0123"

The second header, contains the content type JSON:

AT+UHTTP=0,9,"1:Content-Type:application/json"

3. Create a JSON file containing the data you want to send

AT Command:

AT+UDWNFILE="<file_name>",<size>

  • Replace <file_name> with any name, e.g. sensordata.json

  • Replace <size> with the exact number of characters in the file.

To create a new file with 49 characters, called sensordata.json and add the sensordata, for example: {"temperature": 19,"humidity": 90,"pressure": 78}

AT+UDWNFILE="sensordata.json",49
> {"temperature": 19,"humidity": 90,"pressure": 78}

Read the contents of the file you just created:

AT+URDFILE="sensordata.json"

4. Send data

AT Command: 

AT+UHTTPC=<profile_id>,4,"<url path>","<responseFilename>","<filesystemName>",4

  • Replace <profile_id> with the same identifier you used before, e.g. 0

  • Replace <url path> starting with /, e.g. /api/v1.6/devices/{Device Label}

  • Replace <responseFilename> with any name to store the server response, e.g. data.txt

  • Replace <filesystemName> with the file containing the data you want to send, e.g. sensordata.json

For example:

AT+UHTTPC=0,4,"/api/v1.6/devices/iotsensor","data.txt","sensordata.json",4

Expected response: +UUHTTPCR: 0,4,1

If the message was sent correctly, the Ubidots platform will visualize and store your data.

Optionally, delete the created file so you can recreate it when collecting new sensordata:

AT+UDELFILE="sensordata.json"

Useful links

PreviousAWS IoT CoreNextIntroduction to Private LTE

Last updated