Orange Live Object experiment

orange
Orange announced yesterday several things regarding IOT and LoRa deployment. Part of the announcement was the Orange IOT LiveObject API, described as « a personalized and secure service that connects your objects to your business applications». Basically, it’s a service to store data sent by connected objects.

Usage

To use the API, you need to register as an orange partner. This is not very complex, but things start to be harder when it came to the datavenue service

There is a concept of Template, Datasource and Prototype. A Datasource can contains several stream of data (like temperature, position, etc..) and should represent typically a connected object. A template can pre-defined what kind of source are available on an objet.

API :
The API is classical. You can send data associated in every datasource, and you can retrieve them in a paginate way. In fact all the function are available through the API (and for most of them only through the API). I think that it could have been simplified a lot.

Documentation :
It’s clearly the biggest lack of the service. There is no start guide, or tutorial. Juste the raw API and some FAQ. You need to dig into the FAQ to understand things. For instance, there is no « how to authenticate »FAQ , but in the « What is an Orange Key » FAQ, you will learn that this key must be included in every request…

There are some Curl example of the API usage, which is good, but they are hidden in the Website (they are at the bottom of the datasource detail, and you might need to refresh your browser to see them).

SDK

There are many ‘SDK’ available: Java, Node.js, iPhone, Android, C (which seems to be empty for now). In fact, too many regarding the current maturity of the product. They seems to have been done very fast and are not very explainatory. For instance, the one I’ve used (Node.js) was not fully debugged despite the fact it was not been modified since 7 month, and had on the other hand a quite good documentation.

Support

I had very good and reactive feedback from Orange support team, which is obviously great

Pricing
No information on it on the Web site
My feeling : Orange should have spent more time in creating documentation than various client

Conclusion
What is it for ?
That’s the biggest question. You can use this to store your information, but there is basically no way to extract some meaning from this information. There is no service around them, even the basic ones. For instance, you can’t even know how much data has been send to a specific stream.

I wanted to export some of the data generated from the OpenSensorCloud platform to the Orange one, but as it as impossible to do something with the data, I had to stop for now my experiment.

What is expected :
Just like other services available, the minmum should be the ability to extract some value of these data :
Display graphical value :

  • that’s usually the first service that come with such offering
  • Be able to trigger some event based on some condition
  • Be able to operate on large volume of data (both on the same stream, or on multiple stream). Example : average / stream, average on multiple stream, etc..
  • Etc…

The Orange site claim for instance that you can “View your connected objects’ data on your existing business applications or personalized interfaces », but no clue on how to do this. I assume that it should be possible using Orange services

The service seems to be far from being operationnal, at least for the average user (I guess it might be different for their « partner ») so let’s wait a little bit and see how this will evolve, and especially how the competition will react . Ovh launched his Time Paas serie a few month ago (in an experimental way) but was more mature than current Orange offering.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>