Ubidots Overview
Ubidots makes it easy to white-label visualizations to produce a branded version of your service for end customers. You can also create end-users who have access to their own custom dashboards.
Ubidots Specific Attributes
For each Output Stream type, there is a set of specified attributes. Here are the ones for Ubidots:
Attribute | Type | Required | Description |
---|---|---|---|
HTTPS endpoint URL | string | ✅ | URL where events are sent via POST request |
Ubidots auth token | string | ✅ | Ubidots authentication token |
Overview
To use this integration, you need to:
- Have an Ubidots account
- Create an instance of the Golioth plugin in your Ubidots account
- Create an instance of the Ubidots output stream in your Golioth account
Setup the Ubidots Output Stream
1. Create an Ubidots account
Create your account if you don't have one yet.
2. Create an integration between Ubidots and Golioth
Follow this tutorial to create a complete integration between Golioth and Ubidots through an Ubidots output stream.
In this tutorial you will see how to:
- Create a Golioth plugin on Ubidots
- Create the Ubidots integration in Golioth
Example Data
Golioth Output Streams use the Cloud Events format. For Ubidots, this means some metadata of the event are sent as HTTP headers.
Here is an example of an event arriving on Ubidots. Headers prefixed with Ce-
are related to Cloud Events and the message body is the event payload.
POST {your-uri-path} HTTP/1.1
Host: {your-uri-host}
Content-Length: 137
Accept-Encoding: gzip
Ce-Id: baa51655-c067-444c-a91c-6dcea73abc70
Ce-Source: golioth/app/gateway/coap
Ce-Specversion: 1.0
Ce-Subject: stream
Ce-Time: 2022-03-18T17:25:08.795194496Z
Ce-Type: DEVICE_STREAM_TYPE
Content-Type: application/json
{
"data": { "msg":"testing ubidots output stream"},
"device_id":"61a4cfdfb2b45578105aeca5",
"project_id":"my-first-project",
"timestamp":{"nanos":346519550,"seconds":1647624308}
}
Resources
For more information on the Ubidots integration, please see our blog post.