Tagged: stream

Carriots new features: APIKEY management

Hi all!
We are pleased to announce a bunch of new features and interesting stuff at Carriots.

APIKEY management is now available for free account users. Fine grained visibility and privilege customization that allows to define a lot of combinations like:

  • A device that only send streamsCarriots APIKEy management
  • External Javascript application that wants to check for device’s streams
  • Manage any entity with full privileges below a specific service (down to the streams)
  • Only read any information below a specific project

Also related to this topic you can now scan your APIKEY with your smartphone using QR codes. Check it in your control panel at My settings -> My account -> Show/Hide QrCode

There is a new option for optional stream persistence. You can now avoid streams to be persisted after data received event is fired. It can be useful to keep your data streams clean when working with raw data. More details in our documentation page: API -> Data management -> Streams

You may also have noticed that there is a new logo trailing down in our webpage footer. Yes, that’s it! You will find our Carriots Github account (https://github.com/carriots) full of code ready to use:

Carriots Github account

  • Arduino
  • Arduino YUN
  • Arduino librairies
  • Beagle bone
  • Fez Cerbuino

And that’s not all. All this code is released with some easy tutorials that you will want to check:

Of course, some minor bug fixes are continuously released. Ask us in the forum!

More features to come in the next days.

Enjoy Carriots!

New Feature: Wizard to send data streams to Carriots

We have begun deploying a new feature at Carriots: Wizards. By its name it is easy to guess what they do. They are assistants that will help you do some tasks that are complex, infrequently performed, or unfamiliar when you’re a new developer at Carriots. Especially when you are new to Carriots it may be easier to start performing some tasks using a wizard because the sequence of steps through the web control panel also teach you which are the requests to the API and what are the actual responses from Carriots.

Right now we have just deployed one wizard to help send data streams to Carriots. More wizards will be available during the next weeks to help (and teach how to use Carriots API) with other tasks like creating business rules and logic.

The first Wizard we have created simulates how a device should send a Data Stream to Carriots. This assistant is 3 clicks long because each step represents an important concept:

  • Step 1: Choose your device. In Carriots all Data Streams have a Device as the origin of the data. To help new developers at Carriots we have created for them a “defaultDevice” that is ready to play with. Also note that in Carriots the unique id of a device is the name_of_device@name_of_user . Obviously you can create more devices (up to 10 with your free account) and they will be listed on the display box.
  • Step 2: This step is about filling the information that your simulated device will send to Carriots. A device can send an unlimited number of pairs of Data Key and Value. Data Key will be like the name of your variable (like humidity) and Value, guess what, the data of the variable. In this step you have an “add more data” button, so you can data to your stream. You also have a section to add information to the body of the Data Stream although it is optional. When you are finished adding pairs of Data Key and Values click Next Step.
  • Step 3: This step represents the actual Data Stream the Wizard is going to send to simulate your device sending data to Carriots. We thought it is important to show this summary to help you understand how your device should behave and how it should send information to Carriots. As you can see the APIKEY (unique to each developer) is sent in the Header and the data of the device is sent in the body of the HTTP request. Don’t forget to click the “Send stream” button, otherwise the data won’t be sent to Carriots.
  • Step 4: A final page shows the expected response from Carriots API when everything is fine and your Data Stream is stored in Carriots and you get a HTTP/1.1 200 OK { “response”: “OK” }. You also have a tab to review the HTTP request to Carriots API where the Data Stream was sent.

Here is the process on images:

Step 1:

Wizards Send Data Stream Step 1

Step 2:

Wizards Send Data Stream Step 2

Step 3:

Wizards Send Data Stream Step 3

Step 4:

Wizards Send Data Stream Step 4

We hope you enjoy this Wizard while we finish some more!