Why a proprietary API library solution rather than an Open source one?
At Overkiz, we have chosen to offer our customers a proprietary API library solution rather than an Open Source solution, for several reasons:
- We control the accessibility of the source code, which makes our system less vulnerable to attacks than an Open source system.
- We develop our own CMS (Content Management System) and have designed it especially for home automation, which makes it more targeted and more efficient than an open source CMS subject to the community’s choices.
- With our proprietary API library solution, you are guaranteed 24/7 support by the Overkiz team.
What are the protocols and connected objects supported by the Overkiz IoT API library?
Overkiz home automation library APIs support 20 public and private protocols:
EnOcean, io-homecontrol®, KNX, Modbus, RTS, Wifi, Bluetooth®, Z-wave, Zigbee 3.0 and proprietary protocols.
The Overkiz IoT API library has already allowed to connect 2.5 million objects:
Overkiz is able to connect very disparate devices related to the world of home automation:
- Energy meters
- Lighting
- Openings
- Security systems
- Sensors and detectors
- Heating
- Ventilation
Overkiz’s home automation API libraries are compatible with more than 60 OEM brands:
Atlantic, Aurora, Avidsen, Danfoss, De Dietrich, Eltako, Ewattch, Hager, Hitachi, Honeywell, Micropelt, Nanosense, Nest, Netatmo, Nodon, Philips, Sauter, Schneider Electric, Siemens, Somfy, Thermokon, Thermor, TriO2sys, Ubiwizz, Vaillant, Velux, Yokis, and many others.
How Overkiz’s home automation APIs libraries manage interoperability?
The solution is based partly on a home automation controller (gateway/box) capable of supporting many protocols (e. g. EnOcean, io-homecontrol, RTS, etc.) but also a large number of connected objects (e. g. Somfy Protect locks and alarms, Philips Hue bulbs, etc.). The controller operates in cloud mode to manage real-time communications and data management between disparate products (heating, ventilation, opening, security, etc.), as well as between consumer applications and third-party environments.
In concrete terms, Overkiz uses home automation boxes as protocol gateways to make the Overkiz SaaS APIs and any other electrical or electronic element of the home or building concerned interoperable. Following your requests and existing devices, we develop new modules to enrich our API library and allow several systems to communicate with each other. You can then access your own entire system in real time and anywhere with the dedicated web server.
IoT API libraries make it possible for two incompatible protocols to be interoperable and thus allow disparate products and different manufacturers to interact with each other.
But for exchanges to be possible, OEMs must make their APIs libraries public.
What type of application can be created with the IoT API library?
- The control of household electrical appliances (by programmed actions or by motion detectors, remote controls…)
- Automation of sashes: shutters, entrance doors, garage doors and gates
- The management and control of watering of a remote garden
- Energy management (e.g. heating, air conditioning, ventilation, water)
- Security of property and people: alarms, motion detectors, Digicode…).
- Lighting automation
- Installations that provide better acoustic comfort, such as a set of loudspeakers that distribute sound and regulate sound intensity.
What applications have already been developed by our customers?
Thanks to our Overkiz API library, our customers have developed several applications, following some examples:
“Cozytouch” by Atlantic
“Energeasy Connect” by Rexel
“Hi-Kumo” by Hitachi
“Tahoma” by Somfy
What are you waiting for to create your own applications too?
