The IJENKO Platform combines the power of the Internet of Energy with the Internet of Everything, i.e. the interaction between the “Things”, Data, Events, the Process and People, which truly creates the value of the IoT. This is what we have called the IoE². Our APIs provide access to the IoE² Platform resources to manage the Smart home and build B2B and B2C applications for the benefit of end users and business verticals.
Since 2008, we have led the way for the creation of simple and meaningful home automation and energy management services for a variety of Service Providers using different technologies and protocols. From the start, the Data Model we have invented has abstracted a number of non-IP protocols such as ZigBee, Zwave, EnOcean, KNX, Wireless MBus, in one model to give you the freedom to develop and evolve over time without being locked into a single solution. We have looked at the new IoT eco-systems, Clouds and best sellers as existing resources in the home to collect data, send additional commands and build new services by interacting with them. The Data Model and API you will discover through this developers site are the result of years experiencing both the digital, the physical and the energy worlds in the home, across different countries and with multiple Service Providers for you to create service value, simply!
Whilst being scalable, secure, interoperable and open is essential, it is not sufficient. New innovation fields are necessary to unlock the mass adoption of a new generation of IoT devices and smart home services.
The emergence of the Internet of Everything starts with the "Things": devices, IP or non-IP, physical (sensors and actuators) or virtual (e.g. weather data available through a cloud). As the cost of sensing technologies declines, we are shifting from mono-functional devices, e.g. a motion detector to detect a presence, to what we call "polymorphic" devices. This was already the case of high end devices such as the nest thermostat which includes light and proximity detection, as an example of all-in-one device centric strategy. Lately it starts to reach low-end sensors as typically a smart plug with a temperature/humidity and/or air-quality embedded sensor. Furthermore, as we move towards devices which will decide to publish some of their data capabilities and not all of them, locally or via their Cloud APIs, we believe that a future proof IoE² Data Model should manage first and foremost "functionalities" and their associated data & events/actions capabilities instead of looking at devices.
This is what we have anticipated at IJENKO: we have built a "functionality-centric" Data Model. It gives you direct access to functionalities which can come from polymorphic devices without depending on this device specification. All you need to know it that you have "Temperature" functionality, whether it comes from a motion sensor or from a nest, Netatmo, tado° or Lyric thermostat. That means for you that your applications and services will be "device-agnostic". Hence, they will be compatible with a broader set of devices without any change of code.
So we are focusing on adding as many functionalities as possible to our platform. We have made them as simple as possible for you to discover and use in order to build end user and B2B applications and services.
When we launched our initial services in 2009, our first Data Model was inspired by the amazing work done by the ZigBee Alliance with its profiles, clusters and attributes. Still, even then we had to manage seamlessly two other protocols in a model which had to be technology agnostic. So we invented our abstraction model and have continuously integrated new protocols and unified them in a single Data Model.
While we are providing high level services on energy management, (e.g. predictive analysis, Demand Response, etc.), we have always kept the lower levels of the platform (data collection and automation) accessible for Service Providers to invent home automation such as security services. Our ambition has been all along to make sure that developers did not need to get into the specificity of any technology to develop rapidly from our set of services.
The new Data Model release we are presenting here is even more comprehensive as it opens up to the broader context of the new IoT alliances and languages such as AllSeen, Weave and Homekit. Defining semantics is always challenging, as you know. We have designed ours from our own expertise, as well as from best-of-breed models such as the Data Model of Sensor Web Enablement framework by the Open Geospatial Consortium, and others. Our Data Model provides self-descriptive data for an easy understanding and adoption:
The world of the IoEverything we all want to create in the home is diverse and keeps evolving. Some are interested in the Smart Home data to deliver end-user services. Others aim for data to crunch, make analytics and use predictive algorithms. Some, like Utilities, want to bring more value to their B2B operations by managing the energy usage for downstream and upstream services, or learn the household’s daily routine to perform automated and adaptive actions.
If you are more interested in getting raw data and interaction between devices capabilities, then the IoT API is more appropriate for you.
If you need to build energy efficiency engagement programs from metering or sub-metering data, active Demand Management solutions, monitoring services for local generation and residential storage, then the IoEnergy API is for you. It provides you with a high level set of algorithms, services and structured data, at the individual or aggregated level to create value both for your end-customers and for your business ecosystem.
In both cases, we have designed our APIs to be a gain of time and value for you, relying on our expertise and everyday efforts to make it simple.
IJENKO’s IoE² platform provides 2 API products: the IoT API and the IoEnergy API.
Our API are REST and use JSON format.
For authorization and authentication, we use the standards OAuth2.0 and SSL.
The IJENKO APIs are private and available to our B2B partners, who want to create their own user experiences or build their own developer communities.Contact us