{"id":586,"date":"2018-01-25T00:00:00","date_gmt":"2018-01-24T21:00:00","guid":{"rendered":"http:\/\/blog.iridi.com\/en\/2018\/01\/25\/iridium-lite-new-quot-dream-app-quot-for-home-automation-professionals-2\/"},"modified":"2018-07-26T12:57:14","modified_gmt":"2018-07-26T09:57:14","slug":"iridium-lite-new-quot-dream-app-quot-for-home-automation-professionals-2","status":"publish","type":"post","link":"https:\/\/blog.iridi.com\/en\/iridium-lite-new-quot-dream-app-quot-for-home-automation-professionals-2\/","title":{"rendered":"iRidium lite: new "dream app" for home automation professionals"},"content":{"rendered":"

iRidium lite claims to lead in the field of multiprotocol applications for Connected Home (or Smart Home) systems of professional installation. It acts in some other segments, as well. iRidium lite application, as well as other products by the company, is intended for installers of home \/ building automation systems and system integrators. In this article I will try to describe the capabilities of the new product in detail and its differences from other applications of the company.<\/p>\n

START USING IRIDIUM LITE<\/a><\/p>\n

<\/p>\n

Distinctive features of i3 lite application (iOS, Android, Windows)<\/h3>\n

– compatible with dozens of systems and hundreds of smart devices (KNX, Modbus, HDL, Samsung SmartHome, Duotecno, Domintell, Philips HUE, Fibaro, Kramer, Sonos, Kodi, Netatmo, Gmail, Apple TV, Global Cach\u00e9, CoolAutomation, iRoom, Ekey, Mobotix , 2N and others).
\n– expandable thanks to iRidium store \u2013 a module marketplace. Open API allows third-party developers to create and monetize modules.
\n– capability to work in the Panel mode (without a central controller) and in the Server mode (with “iRidium server lite” hub for Windows, Linux, Raspberry Pi and some hardware controllers).
\n– work with Internet connection or locally.
\n– capability to customize a visual interface and logics from the application itself without external editors.
\n– capability to translate the App to your native language. The App is available in 8 the most common languages.<\/p>\n

\n

Example 1: Smart home
\nfor a new country house<\/h3>\n

<\/p>\n

A control system is laid already on the design stage of this kind of sites. Let\u2019s suppose that lighting and room thermostats are controlled by some KNX bus devices, the boiler and the ventilation work using the Modbus protocol, air conditioners are connected via the Coolmaster controller, the color lights to the music in the entertainment room are Philips HUE, Mobotix door entry is used, Kramer HDMI matrix switch, Apple TV And Kodi are used as video sources, a projector is installed with a PJLink protocol and a TV is controlled via Global Cach\u00e9 IP2IR converter.<\/p>\n

If the customer does not want to spend time or pay for the development \/ configuration of the individual interface, i3 lite with a central controller is perfect. The integrator creates a configuration of rooms, adds devices and sets them the right way. The application will automatically configure iRidium server so that logics and schedules work round the clock. Usually fixed control panels are installed on such an object. In the future they are supplemented with personal gadgets of the customer. The application automatically adapts the project when it loaded on tablets or smart phones.<\/p>\n

After a project is completed, an integrator buys a license for the object and adds a end-user\u2019s account to the list of its users. In the future a user enters their data and password when installing the i3 lite application on a new mobile device and the control project is immediately downloaded on the smart phone or tablet.<\/p>\n

Intel NUC based on Atom processor, with Windows 10 IoT enterprise (LTSB) of Linux OS can be used as a hardware controller. The cost is about 250 USD. The cost of i3 lite license for an end-user is about 450 USD.<\/p>\n

Example 2: Home Theater<\/h3>\n

A one-page remote control is usually required for a home theater. Curtains and lighting are controlled via Fibaro hub, Kramer matrix, a PJLink projector, the rest via IR through Global Cach\u00e9 iFlex.<\/p>\n

The cost of the license for an end-user for one object is 150 USD.<\/p>\n

<\/p>\n

Example 3: 2-bedroom apartment<\/h3>\n

Such a project typically features HDL lighting and climate control system, Netatmo weather station and a client might use a robot vacuum cleaner, an air conditioner and a dishwasher of Samsung Smarthome product line. The client wants to manage his Smart home from two tablets, one computer and three smart phones. Schedules are also required, and the client wants to edit existing schedules and create new ones. He is not ready for big expenses.<\/p>\n

i3 lite is used with the iRidium server installed on Raspberry Pi 3, the cost is 70 USD in assembly with the power supply.<\/p>\n

One time cost of a license for an end-user for an object is about 300 USD.<\/p>\n

<\/p>\n

Example 4: CCTV and barriers control for all residents of a house (or a village)<\/h3>\n

The task is to give inhabitants of apartments an opportunity to open barriers in the yard from their smart phones and to have access to video streams of cameras in the same yards. To control the barriers, a Modbus TCP controller is used. The controller is assigned an open external IP address.<\/p>\n

iRidium store already has a universal module for the ModBus TCP protocol and a camera module. The process of creating the right project for a particular house takes several minutes. Next the project is assigned a unique login and password, to which the license is activated.<\/p>\n

Any resident of the house downloads the i3 lite application, enters the login and password for his home once, and then receives the functions provided by the management company.<\/p>\n

The cost of the license is paid once by the management company: 150 USD for the whole house (not important, 10 apartments, 1000 apartments or 200 private houses in the village).<\/p>\n

\n
<\/div>\n
<\/div>\n
<\/div>\n<\/div>\n

Setup process<\/h2>\n

After configuration the result looks like this on the tablet for an end-user:
\n<\/p>\n

And it looks like this on a smart phone:<\/p>\n

<\/p>\n

You can create a project with one room. In this case the interface is simply a set of widgets arranged as required:<\/h5>\n

<\/p>\n

\n
After creating a project, the installer can change graphical interface of the project.<\/h5>\n

<\/p>\n

<\/h3>\n

Integrator work with iRidium lite<\/h3>\n

Let\u2019s stress once again it is an application for professionals who develop projects and sell the results to an end-user, after installing an automation system on the object. To create and edit a project, you need an iRidium dealer account.<\/p>\n

<\/p>\n

After logging in the app a list of available projects is seen and new projects can be created. The created configurations can be saved in the cloud. The list shows which ones are already downloaded on the device and which are not.<\/p>\n

<\/p>\n

When creating a new project, you can select a mode – with or without a server. The central controller, if present in the system, is used for rules, schedules and remote access via the Internet. It also provides better quality feedback from devices, especially if a large number of panels \/ gadgets are used. The controller can be added any time later.<\/p>\n

<\/p>\n

After creating a new project, we get to the configuration section. The application offers to add a standard set of rooms or add each room manually. Rooms and floors can be added or deleted in the Floors and Rooms section.<\/p>\n

<\/p>\n

After setting rooms and floors we move to the most important section – Devices. Its name is relative. Drivers\/Modules of interaction with various services and “smart modules” that provide various functions are added here. You can add a new module from the iRidium store or setup modules that you have already added.<\/p>\n

This is one of the first marketplaces of IoT control modules, available to third-party developers. Modules are created using SDK based on javascript and iRidium API. If you are interested in this process, start developing and selling modules for iRidium lite at this link<\/a>.<\/p>\n

At the time of launching the application, more than 200 modules are already available in the store, including very common systems for the automation market.<\/p>\n

<\/p>\n

iRidium store<\/a><\/p>\n

After you add a module, it is downloaded to the device. In most case it requires configuration, authorization, or, at least, a choice of location of the device widgets. It is important to understand the term “subdevice”, which is used to describe the functional elements of a module. The authors of the application could not find a more suitable term, which collectively describes this entity.<\/p>\n

A subdevice is a part of a software module, designed to interact with some of its functions. For example, we have a 6-channel HDL dimmer. To control it, the HDL Dimmer module is used, automatically creating 6 identical subdevices, designed to control the channels. Another example is Netatmo weather station, which measures temperature, humidity, noise and CO2.<\/p>\n

Each subdevice has its own widget, which can be located in the right areas of a graphic interface. Also, subdevices can be deactivated if they are not used. This is important, because the number of subdevices determines the cost of the license (the basic one includes up to 40).<\/p>\n

<\/p>\n

After adding and setting modules (you can see this process in this playlist on youtube<\/a>), you can start customizing pages – adding images, titles, moving widgets.<\/p>\n

<\/p>\n

<\/h3>\n

Working with macros<\/h3>\n

In i3 lite you can create macros actions. This is a set of commands for modules, which can be activated by a separate button or are used in schedules \/routines. A separate place is provided for macros on the main page below the main image. The installer can allow or restrict an end-user to create their own macros in their project.<\/p>\n

<\/p>\n

<\/h3>\n

Working with rules<\/h3>\n

Rules are the routines. In i3 lite you can create routines. It is a set of actions, which will be done when the specified condition is fulfilled. For example, the routine\/rule will turn on the light in the room, IF the motion sensor goes off.<\/p>\n

There are two types of routines: those which work on the server and those which work on the panel.<\/p>\n

Server routines work on the iRidium server. They can operate even if the control panel is off.<\/p>\n

Panel routines work on the control panels and stop working, if you turn off the App i3 lite. Panel routines need for sensors of the control panel. For example, the panel routine can check the battery level of the control panel and if it is low, the routine will turn on charging by the relay, or turn off the relay, if the battery is fully charged. This routine will extend the lifetime of the battery.<\/p>\n

The installer can allow or restrict an end-user to create their own rules in their project.<\/p>\n

<\/p>\n

<\/h3>\n

Working with schedules<\/h3>\n

If the installer connected iRidium server and the project, he can create schedules. The schedule is the time interval in which macros can work on. What\u2019s more this interval can be the trigger for the routines. Schedules can be one-time or repeated.<\/p>\n

<\/p>\n

<\/h3>\n

Working with modes<\/h3>\n

The mode is a button, by which the user can make the system run the chosen macros und routines. For example, you can create the mode \u201cI left\u201d and the routine, which will turn on the security system, if the user turns on this mode and vice versa.<\/p>\n

<\/p>\n

<\/h3>\n

Linking iRidium server central controller<\/h3>\n

When you create a project, you can attach a server to it. Almost any Windows device, Raspberry Pi or some other controllers by different manufacturers can work as iRidium server.<\/p>\n

The server provides that the project will work 24\/7 even if all control panels are turned off. Also the server allows you to control devices on the Internet, save the condition of the equipment and information about accidents in the event log.<\/p>\n

<\/p>\n

<\/h3>\n

Examples of module operation<\/h3>\n

Cameras<\/h4>\n

The camera module includes a database of common brands with settings. If the model is not available, you can insert a link to the video stream. Each camera is added as a separate subdevice. Full-screen mode is available to display on tablets.<\/h5>\n

<\/p>\n

Gmail<\/h4>\n

The Gmail module allows you to interact with a mail service. After installation, you select an interval to check the e-mail and log in. In general the module capabilities are used in the Routines section:
\nIF the leakage sensor is in the “Alarm” mode, then close the shut-off valve relay and send a “Warning, water leakage!” message to a definite address.<\/p>\n

<\/h2>\n

Differences between iRidium pro and iRidium lite<\/h2>\n

iRidium currently produces two products that are created on the same platform, but are designed for different types of projects.<\/p>\n

iRidium lite is designed for home\/AV automation that does not require a unique GUI or free logics programming. But they require quick setup and can be flexibly changed in the hands of users. The number of users and control devices can also constantly change.<\/p>\n

iRidium pro is more suitable for projects that implement a unique vision of a certain integrator, a freehand GUI and free programming of automation. These projects suggest that once set the system works for many years precisely in the way the integrator made it.<\/p>\n

<\/h3>\n

The table below explains the differences between the two products<\/h3>\n
\n
<\/div>\n

\niRidium lite<\/div>\n

\niRidium pro<\/div>\n<\/div>\n
\n
\n
\n

Usually used for<\/h4>\n<\/div>\n
Standard installations, standard GUI and logics. Control from a user\u2019s gadgets, that are constantly changed.<\/div>\n
Complicated installations, unique GUI and logics, Control from wall-mounted panels, that are changed seldom.<\/div>\n<\/div>\n
\n
\n
\n

Product components<\/h4>\n<\/div>\n
i3 lite app (iOS\/Android\/Windows), cloud service, store of modules, optional iRidium server (hardware and software for Windows, Linux, Raspbian)<\/div>\n
Editor for PC (iRidium studio), i3 pro app (iOS\/Android\/Windows), cloud service, optional iRidium server (hardware and software for Windows, Linux, Raspbian)<\/div>\n<\/div>\n
\n

Control project creation<\/h3>\n
\n
\n
\n

GUI design<\/h4>\n<\/div>\n
Fixed, standard (support of numerous styles and themes in the next version)<\/div>\n
Flexible \u2013 set in the editor on PC<\/div>\n<\/div>\n
\n
\n
\n

Project configuration<\/h4>\n<\/div>\n
In i3 lite app<\/div>\n
In the editor on PC
\n(iRidium studio)<\/div>\n<\/div>\n
\n
\n
\n

Free programming (JS)<\/h4>\n<\/div>\n
No<\/div>\n
Yes<\/div>\n<\/div>\n
\n
\n
\n

Drivers<\/h4>\n<\/div>\n
As ready modules
\nin iRidium store<\/div>\n
Connected and set in the editor
\non PC as native drivers
\nor JS modules<\/div>\n<\/div>\n
\n
\n
\n

Scanning functions<\/h4>\n<\/div>\n
Yes, available to installers and end-users in the app<\/div>\n
Yes, available only to installers in the editor on PC<\/div>\n<\/div>\n
\n

Logic<\/h3>\n
\n
\n
\n

Macros<\/h4>\n<\/div>\n
Yes, available to installers and end-users in the app<\/div>\n
Yes, available only to installers in the editor on PC<\/div>\n<\/div>\n
\n
\n
\n

Rules and schedules<\/h4>\n<\/div>\n
Yes, available to installers and end-users in the app<\/div>\n
Yes, available only to installers in the editor on PC<\/div>\n<\/div>\n
\n
\n
\n

Work with the central controller (iRidium server)<\/h4>\n<\/div>\n
Works with and without the central controller. If a controller is used, there is no need to set it, the app sets it automatically. Free programming is not supported.<\/div>\n
Works with and without the central controller. If a controller is used, it is separately configured in the editor on PC. Free programming is supported.<\/div>\n<\/div>\n
\n

Licensing<\/h3>\n
\n
\n
\n

Free use for installers<\/h4>\n<\/div>\n
All tests are free for an installer
\naccount. Free 60-day trial period
\nfor the server after activation.<\/div>\n
Free 60-day trial period (one
\nlicense per object), free 365-day
\nlicense for a showroom (one
\nper company)<\/div>\n<\/div>\n
\n
\n
\n

Licensing parameter<\/h4>\n<\/div>\n
By the number of \u201csubdevices\u201d
\nfor an object<\/div>\n
By panels and
\n\u201cdata points\u201d<\/div>\n<\/div>\n
\n
\n
\n

License 1 (KNX, 1 control panel)<\/h4>\n<\/div>\n
180 USD (retail price, up to 40 subdevices) + 20 subdevices \u2013 90 USD + 150 USD if iRidium server is used. All drivers and free modules are included<\/div>\n
300 USD (retail price) includes iRidium server up to 50 tags\/data points. AV&Custom Systems driver, IP cameras and SIP intercom are included by default<\/div>\n<\/div>\n
\n
\n
\n

License 2 (KNX, any number of control panel)<\/h4>\n<\/div>\n
180 USD (retail price, up to 40 subdevices) + 20 subdevices \u2013 90 USD + 150 USD if iRidium server is used. All drivers and free modules are included<\/div>\n
4 500 USD (retail price) includes iRidium server up to 10 000 tags\/data points. AV&Custom Systems driver, IP cameras and SIP intercom are included by default<\/div>\n<\/div>\n
\n

 <\/p>\n

START USING IRIDIUM LITE<\/a><\/p>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

iRidium lite claims to lead in the field of multiprotocol applications for Connected Home (or Smart Home) systems of professional installation. It acts in some<\/p>\n","protected":false},"author":2,"featured_media":725,"comment_status":"open","ping_status":"open","sticky":false,"template":"template-centered.php","format":"standard","meta":[],"categories":[3],"tags":[26],"_links":{"self":[{"href":"https:\/\/blog.iridi.com\/en\/wp-json\/wp\/v2\/posts\/586"}],"collection":[{"href":"https:\/\/blog.iridi.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.iridi.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.iridi.com\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.iridi.com\/en\/wp-json\/wp\/v2\/comments?post=586"}],"version-history":[{"count":7,"href":"https:\/\/blog.iridi.com\/en\/wp-json\/wp\/v2\/posts\/586\/revisions"}],"predecessor-version":[{"id":1253,"href":"https:\/\/blog.iridi.com\/en\/wp-json\/wp\/v2\/posts\/586\/revisions\/1253"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.iridi.com\/en\/wp-json\/wp\/v2\/media\/725"}],"wp:attachment":[{"href":"https:\/\/blog.iridi.com\/en\/wp-json\/wp\/v2\/media?parent=586"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.iridi.com\/en\/wp-json\/wp\/v2\/categories?post=586"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.iridi.com\/en\/wp-json\/wp\/v2\/tags?post=586"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}