Эта страница является переводом страницы Config lite. Перевод выполнен на 98%.

i3 lite configurator

Tool to create i3 lite projects

i3 lite config is a part of i3 lite app for integrators and installers that is used to create projects for smart homes and buildings. Config can be launched on a PC, as well as on mobile devices: tablets and smart phones. You do not have to go to the office to make changes in a project by your customer's request. Simplu launch "Config" on your mobile device and make required changes.

There are 9 tabs in the app:

General,
Floors and rooms,
Devices,
Sever,
Schedules,
Routines,
Macros,
Modes,
Users.

We recommend that you create yout first project following this manual "Creating i3 lite projet", to learn how to work with i3 lite Config.

General

There are general project settings in the "General" tab.

Name - project name that is displayed to an end-user when he downloads a project on a mobile device,
Project report - here you can see project devices and a license required for them,
i3 lite version - before creating a new project make sure that you use the latest verions of i3 lite,
Project style - the color scheme of the config and the end-user's template.
Display - a way to display the config and the template on end-users' mobile devices:
- DPI - scaling on the basis of dots per inch of a given model of a mobile device, proportions are saved (by default),
- Pixel (PX) - scalling with streching to fit the screen size, proportions are not saved (recommended for devices with a small screen, for example, iPad mini).
Full-screen mode - turn on/off the full-screen mode of the config and the template.

Renaming a project:

Changing style:

iOS style is the default style. There are other available styles (free and commercial) in iRidium store.

Selecting project display (allows to adapt the interface for different panels):

Full-screen mode:

Project report

The short report about the Smart home devices shows the number of licensed subdevices in the project

Detailed report about project devices allows to see individual information about devices - names, location in rooms, types.

Regional settings

Language - the language of an integrator's and end-user's interfaces. Available languages:
- English,
- Chinese,
- Russian,
- Dutch,
- German,
- Spanish,
- Portugese,
- French,
- Greek.
Temperature - temperature measure units used in the project: °C - degrees Celsius, °F - degrees Fahrenheit,
Date - date format used in the project: DD.MM.YYYY, MM.DD.YYYY, YYYY.DD.MM, YYYY.MM.DD,
Time - format of project time: 12-hour or 24-hour.
Location - geographical coordinates of the automation object. The setting is required to calculate the time of sinrise and sunset.

Changing language:

Selecting measure units of temperature:

Selecting date format:

Selecting time format:

Selecting geographical location:

You can enter longitude and latitude manually by pressing "Enter".

If there is no GPS- tracker in a mobile device, there is no "GPS" button, you can enter location only manually.

Floors and rooms

You can create a list of floors and rooms in the "Floors and rooms" tab. Later on you can place devices in the rooms. As a result it is easier for an end-user to find a device if he knows a room where it is located.

Floors

Name - the floor name,
Icon - the floor icon.

Rooms

Name - the room name,
Icon - the room icon,
Floor - the floor where the room is located.

Devices

A device is real automation equipment that an integrator installs in the customer's object. A "module", a special program of i3 lite is responsible for working with every device.

Some modules can work only with a definite type of equipment, others - with a whole class of equipment, for example, KNX or HDL devices.

You can display a list of devices in 2 ways:

by modules (sorting by name),
by location (grouping by floors and rooms).

Settings:

Name: name of a module,
Module settings: open the window of module settings.

Module settings

iRidium store: read the module description in the store,
Feedback: leave a comment on the module work,
Update: download the latest module version from iRidium store (the button is not displayed if a module is updated),
Server mode:
- no - a module works only on a control panel,
- yes - a module works on a server (a device can be controlled 24/7),
Delete module: delete a module and all subdevices.

Setting connection with a device

By pressing on you can go to “Setup”.

Setting connection with a device is done in a separate menu, as these settigns are done once and are not changed later on.

Host: IP-address of a device,
Port: port of a device.

Connection settings differ greatly depending on the type of a device.

Subdevice settings

Some devices can consist of several simpler devices that are called "subdevices" in i3 lite.

Active: turning on/off a subdevice,
Name of device
Type: type of subdevice,
Icon: an image to recongnize a subdevice,
Location: place of a subdevice (floor/room),
Info: descriptioin of a subdevice.

Server

Name: server name,
Internal Host: server IP-address in the local net,
Port: server internal port,
Update:
Work mode:
- Auto switch -
Local mode:
External IP: server IP-address in the internet,
External API Port (8443): global port for remote access of integrators,
External Protocol Port(30464): global port for panel access ot the server,
Project synchronization': updating a project on the server,
Activate': connecting a server to the project.

Example of setting server work iRidium server lite.

Schedule

Schedule settigns

Name: schedule name.

Event settings

Name: name of event,
Time: date and time of event start and end,
Repetition:
- Never - an event is active only one time in the selected time of event start,
- Every day, Every week, Every month, Every year - event repetition with a certain period,
- Custom - flexible setting of the repetition period.

The event can be

activated/deactivated ,

rename,

change date and time,

set repetition.

Routines

Routine is a logocal component of a project that keeps track of changes in the equipment state and reacts to the changes according to the set logics.

Routines can be server and panel ones.

A panel routine works on users' panels when i3 lite app is on. A server routine works on the server even is the app is closed.
Here are the common properties of routines:

Active: turning on/off a routine,
Name: routine name,
"WHEN" event': each routine can be set one or more "WHEN" events, that trigger a certain action.
Action: each event can be set one or more actions that are done one after another when at least on "WHEN" event happens.
"BUT ONLY IF condition': a number of conditions that must be true for the routines to start.

You can set several "BUT ONYL IF" conditions of one routine, but they can be absent, as well.

If there is no server on the object, the routines will work only when there is an open i3 lite project on the panel where the routines are set up. If the project is closed or the panel is off, the routines will not work. In this case you can use the Working on all panels property:

on - the routine will work on all panels which download the project from the cloud;
off - the routine will work only on this panel.

If the property is activated and, at least one panel has an open i3 lite project, the routines will work.This way you can set up the project on the panel and if you have no server on the object but have a PC where the i3 lite project is constantly running, you can download the project on the PC. In this case the PC will serve as a server and all routines will work.
If the object is controlled from several devices, then with the help of this property you can also simplify editing of routines in the project. For example, there is a routine in the project: turn on the audio system and play music at 8 am each Saturday. You need to change the time from 8 am to 9 am but have no access to the panel with the routine. If the Working on all panels property is activated, then you can edit the routine from any panel with the running project. Also, if the property is active, you can set up routines in projects on your device and you don't have to set them up on the user's device. The user will just have to download the project from the cloud and all routines will work on his device. Here is an example for the deactivated state of the property. Let's say the project is controlled from 2 panels and they have a routine: to charge the battery of the control panel if it is 5% and disconnect power at 100%. If we activate the Working on all panels property, then when one of the panels is charged 100%, the power will be disconnected disregarding if the second panel is charged 100% or not. In this case it is recommended to create separate routines for each panel.

"WHEN" types of events

There are the following types of the "WHEN" events:

Device - events connected with devices (activation of a sensor, etc.),
Modes - changing the mode,
Schedule - an event that happens in a project schedule,
Battery level - an event that happens when the battery level is high or low (not in server routines),
Day&Time - events, set at a certain time.

Day&Time event can be set to happen at sunrise and sunset in server routines.

To do it, first set the location of an automation object. It can be done in the regional settings of the General tab in the Config.

Types of actions

There are the following types of actions:

Device - send a command to a device,
System - do a system fucntion (time delay, open a browser, etc.),
Modes - changing a mode,
Macros - do a macro (not in server routines),
Log event - log in the journal (not in local routines),
Routine - change the work of another routine (activate, deactivate, stop).

Local routines

Server routines

"BUT ONLY IF" types of conditions

"Device", "Modes" and "Schedules" types of conditions do the same functions as "WHEN" event.
In the Day&Time condition you can set time and day of the week. Routines can also be set to work on workdays and in the weekend.