Эта страница является
переводом страницы
I3 KNX Config. Перевод выполнен на 100%.
Config
i3 KNX config is an interface to set devices, routines, user access rights and other thingsa connected with configuration of the server and the interface in i3 KNX app. All settings and changes in a project are done in the config.
The config consists of:
You can enter the configurator with the help of the system menu, by pressing the three dots and selecting Config in the menu.
General
General settings of a project are located in the General:
Regional settings:
Settings of the panel:
Name
Name - the name of a project that is displayed in the list of projects on entering the app.
Project Report
Project report - information about added devices - names, location in rooms, types of devices.
Control of Project Versions
Control of project versions is a capability to restore backup versions of a project after every change (Save to server). For example, you can restore a previous backup version after saving unwanted changes on the server.
10 backup copies of a project can be stored at the same time. 3 backup copies can be protected from deleting. (protected backup copies are marked with a lock). The first backup copy in the list (grey color) is always the current version of a project (the last version saved on the server), that's why it can't be restores. You can update a list of backup copies with the help of Refresh button.
- Number - the ordinal number of a backup copy;
- Creation date - date and time when a project version was saved on the server;
- Author - a user's account where changed were made in a project;
- Do not delete - protection of a backup from deletion;
- Delete - delete a selected backup copy;
- Restore - restore a selected backup copy.
App Version
App. version is the version of the app.
Project Style
Project style - the style of a project that is displayed on all panels connected to it. Project style is the same for all devices.
An example of a ready-made iOS style interface:
An example of a ready-made iOS Black style interface:
Language
Language - the language of the interface. Available languages :
- Chinese simplified,
- English,
- German,
- Nederlands,
- Portuguese,
- Russian,
- Spanish,
- French,
- Czech,
- Polish,
- Slovak.
Temperature
Temperature - units to measure temperature used in the project: °C - degrees Celsius, °F - degrees Fahrenheit. To change the setting press on Temperature.
Date
Date - format of date used in the project: DD.MM.YYYY, MM.DD.YYYY, YYYY.DD.MM, YYYY.MM.DD. To change the date format press on Date.
Time
Time - format of project time: 12-hour or 24-hour. To change the time format press on Time.
Location
Location - geographical coordinates of an automation object. The setting is required to calculate time of sunrise and sunset. Coordinated can be determined automatically on mobile devices via GPS. If it is unavailable, enter the coordinates manually.
Display
Display is a mode to display the screen (Project, DPI, PX).
Screen Brightness
Brightness - a setting of screen brightness (Available only for Android).
Full Screen Mode
Full screen mode is a capability to open the app full screen without limits (available onyl on Win OS).
Screensaver
Screensaver is a setting of darkening the screen of a PC or a mobile device. This function can be turned off when a motion sensor is activated (available only for tablets and stationary panels and mobile devices based on Android). The screensaver setting is also available in the gear icon before and after authorization in the app (read more here)
DPI Settings
DPI Settings is a manual setting of the DPI resolution. If the size of items is too small, DPI must be increased in width and height, if items are too large, DPI must be decreased (available only for Android):
- Width / Height - change DPI in width / height,
- Reset to default values - restore default values.
Type of Device
Type of device is a change of the screen orientation (horizontal orientation is used mostly for tablets and a vertical one is used for smartphones). It is available only for Android devices.
Floors and rooms
Floors & Rooms tab contains a list of floors and rooms addes by a user. Press + to add floors and rooms.
Select creating a floor or a room in the window that appears or import data from ETS project.
After pressing the Floor button there appears a window to create floors. Select a floor from the offered ones or add your own one be pressing Add custom floor:
After a floor is creates there appears a window to create rooms where you can select rooms from the list or create your own room by pressing Add custom floor.
You can interrupt creating rooms by pressing the Add button. And a floor will be created without rooms. A room can be added to a floor with the help of + button.
Devices
Devices section includes automation systems and devices that you control with the help of i3 KNX. Some Devices are united in Modules, such as KNX module.
To add a Module to a project, press + or Add device.
Select a module to add in the window that appears.
But for specific settings that are individual for any device, there are some standard settings typical of all devices:
- Activation/Deactivation;
- Name;
- Icon;
- Location;
- Additional information;
- Widgets.
Activation/Deactivation - mode of device activity. A deactivated device can't be controlled. To activate or to deactivate a device, press Active. A green button means that a device is activated and a gray one means that it is deactivated.
Name - parameter responsible for naming a device.
Icon - minimalistic graphic image next to the device name. By pressing on it you can change the image and the color of an icon (or delete the icon) and return a default icon by pressing Default.
Location - place of a widget in the rooms of a control interface. To change the location, press on Location field.
Additional information - to enter comments in the information about a device, press on “Description” field and fill it in.
Widgets - graphic display of device status or its control buttons. Some widgets have several variants of appearance. For a widget to become active a project must be made public on the server. After publication a widget in the config and on a project page is unblocked and a user can control a device connected with it.
More detailed information about types of devices anf their settings here.
Server
Server - an interface to the hardware part of i3 KNX Home Server. It contains connection information, a software version and server settings.
Information about server:
- Name - server name;
- Internal Host - server addresses in the network;
- Port - server port;
- Version of KNX Home Server - version installed on the server.
- Check server update - check if there are updates and install a new version of the software on the server. To do it, press Update now.
Server settings:
- Network - server network settings:
- Network connection - network interface that work by default;
- Get IP-address automatically - turn on/off gettin IP-address via DHCP automatically;
- MAC address - MAC-addresss.
- Time & Date - settings of date, time and time zone;
- Work Mode - a mode when a server is connected to i3 KNX control panels: via the cloud and/or locally:
- Local and External - i3 KNX control panel connects to the server via a local IP-address if they are located in the same network and via the cloud (remote access) if direct connection is unavailable. Enter the name of the local Wi-Fi network in the Local and External mode for i3 KNX app to switch to the local mode when it enters home network;
- Local - only local work, remote access ot the servr is impossible;
- Eternal only - only remote work via the cloud, connection via the local IP-address is not used.
Replacing Defective Server
If a server is defective, replace it.
1 Enter the server section and press Change.
2 Select a new inactivated server in the window that appears.
3 Enter the password of your account. Enter (or scan) the key of a new server.
ETS Remote
ETS Remote provides remote connection to the KNX bus via UMC C3. The following is required for its work: UMC C3 with KNX module, a WIN client with the i3 KNX app and a license with ETS Remote addon.
To connect to the KNX bus remotely, do the following steps:
1 Check that you selected the "TP1 interface" option as a way of connection in the Devices tab.
2 Go to the ETS Remote tab and click the Purchase the addon button, if you have not bought it previously. Follow the link to the website, where you can select and buy an additional license for ETS Remote.
3 After purchasing a license, activate the ETS Remote parameter.
Attention! When ETS Remote works, local connection to the server as the IP-interface of the bus is not available.
There can be errors in working with ETS Remote. A list of errors is given below:
- ETS Remote connection is already in use from another PC. If you continue, the other connection will be closed.
This error appears as a popup in the i3 KNX project, if there is an attempt to turn on ETS Remote on a second client whereas there is already an active connection on another client. 1 minute later on of the clients will turn off ETS Remote with an error "Server has been offline longer than 60 seconds. ETS Remote is deactivated".
- Connection to the server is lost.
This error appears in the client log journal (F4), if ETS remote loses connection with the server. 1 minute later, if the client does not restore connection with the server, another error appears in the client. If connection is restored ETS Remote continues its work.
- Server has been offline longer than 60 seconds. ETS Remote is deactivated.
This error appears as a popup in the workspace of the i3 KNX client, if connection between the server and the client is not restored after 1 minute since the moment the connection was lost. After this error appears, ETS Remote is automatically turned off.
- Server is Offline. This error appears as a popup in the i3 KNX project, when there is an attempt to turn on ETS Remote, if there is no connection with the server. After ETS Remote is turned on, the servеr waits for 1 minute. If connection appears, ETS Remote works on the usual mode. If there is no connection, the error appears.
Schedules
Schedules - a component of the config events scheduled at a certain time that can be used to call Routines.
1 Press “+” or Add schedule to create a new schedule.
2 Name a schedule and there appears a window to set events of the schedule.
3 Create an event by pressing Add event.
4 Enter the name of the event, the start and the end of the event.
Parameters of event start are date and time. Time can be set to the minute, astro timer can be used (activation at sunrise, noon, sunset).
For an event to happen at sunrise, noon, sunset, set the coordinates of your location in the General menu.
Repetition can be set for an event. Press Repetition and select the repetition period.
Each schedule can be edited or deletes, there are corresponding buttons in the menu.
Routines
Routines - a logic component of a project that keeps track of changes in equipment state and reacts to changes according to the set logic. A routine can be activated by a schedule, set in the Schedule tab, or by turning on/off a mode, set in the Mode tab.
Each routine has several conditions: WHEN - a list of events. When they are activated commands, set in the DO list, are done but only if all conditions set in the BUT ONLY IF list are fulfilled.
Creating a Push Notification
Here is an example how to create a Push notification set to a climate device. Select an action that will cause a push notification to appear, In our example it's temperature drop below 20 degrees.
1 Press When and select Climate device.
2 Select Temperature is lower than.
3 Set 20 degrees and press Done.
“When” action is ready.
4 Add Do action by pressing a corresponding button.
5 Select Log event.
6 Enter the text of the notification in the corresponding line and select a type of notification. Then press Done.
The routine is ready.
7 Start the project and make the changes public.
Creating a Routine for a Mode
An example of assigning a single mode to a routine.
1 Set a single mode. Read more about Modes setting.
2 Then create a routine.
3 Go to the When field and select Modes, then select the mode you created.
4 Select mode action for On.
5 Select in Routine an action that must be done DO.
Control of iRidium panel 7 Edge Lighting
iRidium panel 7 has an edge lighting. It can be access from a project for i3 KNX via macros and routines.
Example 1. How to sett routines to turn on the edge lighting and to log in yhe journal if a smoke detector is activated:
1 Go to the Routines tab, press + to create a new routine to turn on the edge lighting;
2 Choose Device > Binary display > On in the WHEN field.
3 Go to the DO field, choose Log event and enter a message that will be logged in the journal;
4 Stay in the same DO field and add turning on edge lighting System > Edge lighting of iRidium panel > Red.
When a smoke detector is activated, the edge lighting will be red and a message about the activation of the detector will be logged in the journal.
5 Go to the Routines tab, press + to create a new routine to turn off the edge lighting;
6 Choose Device > Binary display > On in the WHEN field.
7 Go to the DO field and choose System > Edge lighting of iRidium panel > Off.
After a smoke detector is turned off, the edge lighting is also turned off.
Example 2. How to set routines to turn on edge lighting when the door is opened:
1 Go to the Routines tab, press + to create a new routine to turn on the edge lighting;
2 Go to the WHEN field, choose Device > Intercom (in this example DoorBird) > "Open door" is pressed in i3KNX;
3 Go to the DO field and choose turning on edge lighting System > Edge lighting of iRidium panel > Blue.
4 Go to the DO field and add a dealy System > Delay > 01sec;
5 Stay in the same DO field and add turning off edge lighting System > Edge lighting of iRidium panel > Off.
6 Stay in the DO field and add a dealy System > Delay > 01sec;
7 Repeat points from 3 to 6 several times for the lighting to blink.
When a button to open the door is pressed the edge lightin will become blue.
Macros
Macro - a sequence of command that is activated by pressing a Macro widget located in any page. It contains an action (Do) and excluding conditions (But only if).
Create a macro.
Add an action that must be done when a macro is pressed. To do it press Do and select a required action in the menu that appears.
You can also add a condition for the action to be done. To add a condition, press But only if.
Turning on a dimmer with a condition
An example of a macro that turns on a dimmer but only if it is Friday.
1 Create a macro with the name "Dimmer On".
2 Select Device, then Dimmer (that is set beforehand and is in working condition) in Add action .
3 Select On.
4 Set an additional condition in the BUT ONLY IF parameter. Without the additional condition the dimmer is turned on when a macro is pressed.
Press “Add condition”. We'll select Friday for our example. It means that the macro will work only on Fridays, On all other days of the week the macro won't turn on the dimmer.
5 Place the ready macro in a room by pressing Place, and selecting a suitable room. Press Done.
6 Start the project and make the changes public by pressing Save to server.
Modes
Mode - an interface widger that can do actions set with the help of Routines. A Mode that is not connected to a Routine is a trigger-widger that has no sense. There are two types of modes:
- Single mode - a trigger- widget that has two states;
- Group mode - a widget that looks like a group of radio buttons consisting of at lest 2 modes.
Single Mode
Single mode - a trigger-widget that has two sates. Its actions can be set with the help of Routines.
Settings of Single Mode:
- Name - the name of a mode;
- Icon - an icon to display;
- Place - a place where the mode is located.
After a Mode is created create a Routine for it.
Group Mode
Group mode- a widget that looks like a group of radio-buttons consisting of at least two modes. Their actions can be set with the help of Routines.
A Mode can control a Routine or work only to display data, as an indicator of feedback, if it's setting is Display only. For example:
A group of modes has 3 types of widgets.
1 Create a group of modes and select its name.
2 Place it in required rooms with the help of Place.
Users
Users - a section of the config that controls a list of users and settings that deal with informing about events that happen. It consists of several sections:
- Access rights;
- Push notifications;
- E-mail notifications.
To add a user press +. Then enter the user's e-mail an press Ok. If a user is not registered yet, he'll get an invitation.
Access Rights
Access rights - control of a user's capabilities to edit a project. The first user is your account, the account is the owner of the project and it has all rights to edit the project. Every user can have individual access rights, full or limited.
- Only quest access - only guest access;
- Editing list of users and access right - changing a list of users and user access rights;
- Setting server, devices, floors and rooms - setting the server, devices, floors and rooms;
- Setting routines, schedules, timers, macros, modes - setting routines, schedules, timers, macros, modes;
- Room editor, adding voice assistants - Room editor, adding voice assistants.
Guest Access
Each added user can be limited access to editing and controlling a project with the help of guest access. After changing access rights, the project does not have to be made public on the server, all changes are updated automatically.
- Only quest access - guest access;
- Room access - access to rooms;
- Timer settings - allow to set timers;
- Remote control - allow remote control.
Push Notifications
Push notifications - notifications that the app sends to a user's device. Set them for your and users' accounts.
Notifications are created with the help of Routines.
E-mail Notifications
When this type of notification is on, a notification is also sent to the email that was used to create a certain user's account.
