Documentation plan1

Introduction1.1

This chapter presents how the contents of the DELÉGO SERVER manual are organized, so that a reader can go straight to the part that covers the technology or the function at hand.

List of chapters1.2

This manual gathers the whole DELÉGO SERVER application manual suite into a single document. The contents are organized in the following chapters:

System configuration

• General Functions
• Project
• Settings
• Account
• Users
• Notifications
• Cloud

Field technologies

• KNX
• MODBUS
• MATTER
• MQTT

Integrations

• M-Bus
• Philips Hue
• Sonos
• Sentio
• Security
• VoIP Intercom
• Video surveillance

Automations

• Connections
• Logics
• Scripting

Applications

• Energy
• Trends
• Guest Room Management

Abbreviations and Acronyms1.3

Conventions1.4

The following conventions are used in this manual:

Safety information1.5

DELÉGO SERVER is a product intended for trained and specialized personnel only; before interacting with this device you must first read this user manual, in particular this safety information. This document supplements and does not replace any legislation or legal directives on safety.

The device has been developed following the safety regulations currently in force; however, it is not possible to exclude with certainty possible damage or interactions with other devices during its operation. The device complies with EMC guidelines and harmonized European standards; any modification to the device may affect its electromagnetic compatibility.

The supply voltage must be strictly within the range indicated in the General Functions chapter and on the device; risk of fire or explosion if powered outside this range. The CE declaration of conformity of the device can be requested from EKINEX®, at the references on the site www.ekinex-delego.com.

In compliance with Directive 2002/96/EC the DELÉGO SERVER electronic device must be disposed of in the appropriate facilities and not in the collection of solid urban waste.

Warnings1.6

• This application manual is aimed at installers, system integrators and designers.
• The assembly, electrical connection, configuration and commissioning of the appliance can only be carried out by specialized personnel in compliance with the applicable technical standards and the laws in force in the respective countries
• Opening the appliance case causes the immediate interruption of the warranty period
• In the event of tampering, compliance with the essential requirements of the applicable directives for which the appliance has been certified is no longer guaranteed.
• EKINEX defective appliances must be returned to the manufacturer at the following address: Ekinex S.p.A. Via Novara 37, 28010 Vaprio d'Agogna (NO)

Copyright1.7

© Ekinex S.p.A. 2026. This application manual, the DELÉGO SERVER software and the DELÉGO iOS and Android apps are subject to copyright; all rights are reserved. Copying, reproduction, translation and/or modification, even partial, are expressly prohibited unless approved in writing by EKINEX®.

Open Source Licenses1.8

DELÉGO SERVER contains open source software, such as the Linux operating system and its kernel. These software components are subject to various open-source licenses, including:

• GNU General Public License (GPL), https://www.gnu.org/licenses/gpl-2.0.html
• GNU Lesser General Public License (LGPL), https://www.gnu.org/licenses/lgpl-2.0.en.html

If you own a product, for a period of 3 years from the last production date, you can request from EKINEX the source code of the software components licensed under the GNU General Public License (GPL) or the GNU Lesser General Public License (LGPL), and use, distribute and modify them in accordance with the respective licenses. EKINEX cannot be considered responsible in any way for the source code thus distributed, which is provided without guarantees. Nor can EKINEX be held responsible for any damage or consequence resulting from modifications (additions / removals) made to this software by third parties, unless specifically authorized.

More information1.9

• For further information on the product, you can contact EKINEX® technical support to the e-mail address: support@ekinex.com or consult the website www.ekinex.com
• EKINEX® is a registered trademark of Ekinex S.p.A.
• KNX® and ETS® are registered trademarks of KNX Association cvba, Brussels
• MATTER is a registered trademark of CSA Connectivity Standards Alliance, Davis CA (United States)

The company reserves the right to make changes to this documentation without notice.

Revision history1.10

The following table gathers, chapter by chapter, the most relevant changes introduced by the DELÉGO SERVER software releases:

The table starts from software release 2.7. Before that release the DELÉGO SERVER application manuals were organized differently, and an exact correspondence with the previous versions of the documents is not possible.

General Functions2

Introduction2.1

This chapter is the guide to the main application of DELÉGO SERVER, and contains all the necessary information for its configuration and use.

General overview2.2

What is Delégo Server2.2.1

DELÉGO SERVER is a powerful visualization server for connected buildings; it natively supports KNX, MODBUS and other communication protocols.

DELÉGO SERVER is not only a visualization tool, but offers a rich set of automations to installers and system integrators. Being a webserver, it can be configured and used entirely with a web browser; end users are encouraged to interact with it by means of DELÉGO mobile app, available free of charge on the Apple App Store for iOS and Google Play Store for Android-powered mobile devices.

DELÉGO SERVER is designed to be installed in an electrical cabinet and physically connected to the field buses (KNX, MODBUS…) and the local network. Although it can operate (and can be used via the app) locally, if connected to the internet it can be extended by the Ekinex cloud with additional functions and services, like the voice control (with Alexa and Google) or the remote programming not only of the webserver, but also of the KNX and other devices.

System architecture2.2.2

DELÉGO SERVER must be connected to the local network and the other technologies which require a physical connection, like the KNX bus, a MODBUS RTU line etc.

Thanks to the integrated support for several protocols, DELÉGO SERVER can interact and coordinate multiple technological systems, and present a unique interface for the control of the building, to the mobile app, PC/Mac with a web browser, and one or more DELÉGO PANEL.

Technical data2.2.3

Licenses and vouchers2.2.4

After purchasing DELÉGO SERVER, most of the functions are already available in the product, but some of them require activation with a license voucher, as does extending the number of KNX addresses beyond the default limit. To redeem a voucher, log in to the technical portal on EKINEX's website

https://voucher.ekinex.com

In the Redeem voucher section it is possible to:

• enter the voucher code;
• enter the unique serial number of the DELÉGO webserver;
• specify which license is to be activated. If the voucher covers several options, a third drop-down menu appears for the choice.

The serial number of the webserver is printed on the label on the side of the product. If the device is not physically at hand, it can also be read from the Administration, by opening

Settings → Vouchers

where it is the first entry of the page. Once the license has been generated, proceed as follows:

• for KNX point upgrades, paste the code in the field of the product itself, the one labeled Delégo;
• to enable an additional module (a proprietary alarm system, for instance) paste the code in the field of that module further down the page.

Once the licenses have been entered, confirm with the SAVE button and wait for the page to reload. At the end of the procedure, check that limits and modules have been applied:

The list of systems compatible with DELÉGO SERVER keeps growing. For an up-to-date list, see www.ekinex.com.

Preliminary setup2.3

Overview2.3.1

DELÉGO SERVER is equipped with 2 status LEDs, terminals for connecting the power supply, the KNX bus line, the Ethernet network, the RS485 bus line and a USB port.

The front panel offers two LED indicators:

• POWER LED: indicates the presence of 12-24 Vdc power at the terminals
• SERVICE LED: normally off, it activates in steady or flashing mode during IP address or factory configuration restoration sequences

The RESET button is used for the recovery operations described later in this chapter.

Connection to the KNX bus2.3.2

The connection to the KNX system is made with an ordinary KNX certified cable, plugged directly into the server through the standard red and black connector supplied with it.

The KNX system can also be supervised over the network, if an IP router is present: in that case a physical connection of the server to the bus is not needed, and a specific communication setting is required instead, described in Communication settings.

The bus connection is not strictly necessary in order to configure the server. Without it, however, there is no way to verify that the project is correct, nor to try out the automation functions that have been configured.

Network connection2.3.3

The configuration and use of the DELÉGO SERVER requires a connection to the home or company network.

From software version 2.6.0 DELÉGO SERVER provides full support for DHCP addressing. Servers produced with this version preinstalled ship with DHCP as their default configuration.; in the previous versions of the servers the IP was statically managed.

Please refer to the instruction sheets inside the packaging, to determine in which of the two conditions your server falls, and follow the corresponding instructions below.

Connect the server to a network with a DHCP server (normally the local networks have it) and perform one of the following actions to discover its IP address:

• If your PC is in the same network, enter the following address in a web browser:

http://delego.local

• Look for DELÉGO SERVER in the client list of the DHCP server, or run an IP scan (or ask the network administrator).

If more than one server is connected to the same network, each of them may be reachable at one of the following addresses: delego.local, delego-2.local, delego-3.local and so on. To assign a different IP address to the server, follow the instructions given under Settings → Network; see Network. In the past DELÉGO SERVER had a static IP address by default; refer to the quick start guide printed on the packaging to identify the address of your unit.

First access2.3.4

For an optimal browsing experience, we recommend using the GOOGLE CHROME browser.

By opening the browser at the default address, as explained in the previous section, the following login screen is displayed:

DELÉGO SERVER comes with the following factory-set users:

Enter admin as username and password and confirm. The Visualization opens on its homepage; from there, the Configuration entry of the navigation menu leads to the Administration.

Manual IP address restore2.3.5

If necessary, it is possible to assign the predefined STATIC IP ADDRESS 192.168.0.110 to DELÉGO SERVER using the RESET button:

• Locate the RESET button on the rear side of the device.
• Press the button for at least 10 seconds, until the SERVICE LED on the front of the device starts flashing.
• Within the next 5 seconds, press the button for 1 second and release; after one or two seconds the front LED lights up steadily for about two seconds.
• When the LED turns off, the device is reachable at the factory IP address (192.168.0.110)

If the LED turns off after the first step, repeat the entire procedure. This procedure resets the IP address and maintains all the data relating to the previously carried out configuration of the automation system.

In the older 2-module DIN-rail hardware version, it was necessary to remove the front panel in order to access the reset button.

Database reset2.3.6

If the configuration in the database makes it impossible to access the DELÉGO SERVER or its correct use, it is possible to restore the server to its factory state (empty project database) by restoring the empty database with the RESET button.

Starting from software version 2.6.0 the following procedure does not change the IP address. In previous versions, the static IP address 192.168.0.110 was also set.

• Locate the RESET button on the rear side of the device
• Press the RESET button for at least 10 seconds, until the SERVICE LED on the front side of the device starts flashing, then release the button.
• Within the next 5 seconds, press and hold the button for at least 10 seconds.
• When the LED lights up steadily, release the button and wait for it to switch off.
• When the LED turns off, restart the server.
• Wait 1 minute and log in to the server with its last IP address (or the predefined static IP address 192.168.0.110 if the server is equipped with a software version older than 2.6.0).

In the old 2-DIN rail module size hardware version, it was necessary to remove the front panel in order to access the reset button.

Graphical interface and navigation2.4

Spaces2.4.1

DELÉGO SERVER offers two different graphical SPACES: the Visualization, used by the end user through the browser or the app, and the Administration, used by installers and system integrators to configure the system.

Both are served by the same address. Opening the server address leads straight to the Visualization; the Administration is reached by authenticating as a user belonging to an administration group.

From the Administration you return to the Visualization at any time with Frontend, in the Configuration menu at the top right, so you can check the result of the configuration you have just performed.

Administration2.4.2

The Administration is the space where installers and system integrators configure the Visualization and all the home automation functions the server supervises. It is organized as a bar of sections across the top and, below it, a constant three-panel layout. The same arrangement is reused in every section, so once you have learned one section you can find your way in all the others.

1. Navigation bar: the Project button, the sections of the Administration, the user menu and the Configuration menu. It is described in the following sections.
2. Context tree: the elements of the current section, that is the building with its floors and rooms in Project, or the objects grouped by category in the field technology sections.
3. Workspace: the card of the element selected in the tree. When the element has several pages, they appear as tabs across the top of the workspace.
4. Source panel: the Library of object models that can be inserted, alternating with Widgets, Discovered or ETS depending on the section. New objects are created by dragging a model from here into the tree or into the workspace.

The workspace stays empty until you select an element in the tree: this is the normal state of a section you have just opened, not an error.

Navigation bar2.4.2.1

The bar across the top of the Administration gives access to every part of the server. From left to right it holds the Project button, the sections, the user menu and the Configuration menu.

Only the enabled sections appear. Add …, at the end of the bar, opens a panel of switches that shows or hides the optional modules; MQTT is off by default and does not appear in the bar until it is enabled here.

Pressing the Project button on the left opens the settings of the project, the project card described in Project card; the arrow next to it opens the views of the project, to switch between Project view and Guest room management view.

Guest room management view replaces the sections of the bar with those of the access control module: Structure, Rooms and gates, Guests, Timetables, Access log and FIAS. It is described in Guest room management view; Project view brings back the sections listed above.

This topic is shown in the Administration environment and Search video tutorials.

Search2.4.2.2

Search is a way of working offered by the side panels, to filter their content quickly by keyword. A search field sits above the project tree in the left panel, and at the top of the source panel on the right, under the Library and Widgets tabs. Typing one or more keywords filters the tree below the field, leaving only the entries whose name matches; clearing the field restores the whole list. In the source panel, the button beside the field narrows the filter to a specific category.

1. Search above the project tree, in the left panel.
2. Search in the source panel, with the button that narrows the filter to a category.

The filter applies to the panel where it appears, and therefore to the section you are working in: searching in KNX looks through the KNX library, searching in Modbus through the Modbus one.

This topic is also covered in the Administration environment and Widget association video tutorials.

Workspace2.4.2.3

The workspace is the central panel and shows the card of the element selected in the context tree. When the element has more than one page of settings, the pages appear as tabs across the top of the workspace, and you move between them by clicking the tab.

1. Tabs: the pages of the selected element. Click a tab to move to that page.
2. Body: the fields of the page currently open, here Project info.

Changes are applied with the button at the bottom of the card, where the card provides one. Selecting another element in the tree replaces the content of the workspace.

Status bar

The cards of the elements that run a communication process of their own have a status bar across the top of the workspace, above the first group of fields.

On the left, Execution state is shown as a coloured dot:

On the right, RESTART stops the process and starts it again with the settings currently on the card.

The cards without a process of their own, such as a widget or a security panel, have no status bar.

System messages2.4.2.4

Messages generated by the server appear as a band at the bottom of the workspace, with a button on the right to dismiss them. They report the outcome of an operation, or a condition that needs attention: for example the reminder that one or more predefined users still have their default password.

These messages are transient: they are shown when the event occurs and disappear once dismissed or once the page is reloaded.

Notifications addressed to the end user are a different matter: they are configured in the Notifications section and delivered through the channels set up there, not shown in this band.

Visualization2.4.3

Navigation2.4.3.1

The Visualization opens on the home page. Its background image is chosen in the Administration, in the Homepage tab of the project card, and around it three areas give access to the whole project.

1. Buildings and floors: the floors of each building, one round button each, grouped under the name of the building they belong to. Pressing one opens its rooms.
2. Functions: one icon per function present in the project, lighting, HVAC, shades, scenes, security, multimedia, gates, sockets, technologic, irrigation. The bar filters the widgets shown on the page you are on.
3. Navigation menu: the services that are not tied to a room, favorites, security, energy, notifications, weather, scenes, schedules and the configuration of the Visualization.

The navigation menu opens as a panel on the right-hand side.

From any page or popup you go back one step with the arrow in the top-left corner, and reach the home page again with the home entry of the menu.

Building structure2.4.3.2

The project can be organized on the following levels:

• Buildings, each of them a set of floors.
  • Floors, each of them a physical story of a building, seen as a set of rooms.
    • Rooms, each of them a physical space, seen as a set of widgets.
      • Widgets, the building functions themselves: a light, a thermostat, a shutter, and so on.

Normally a single building is used, and the home page shows its floors directly. With the ADD BUILDING button further buildings can be created; new in version 2.9, the home page then shows the building level too, as in the Visualization home with two buildings shown in Navigation and at the end of this chapter.

Pressing a floor on the home page opens its rooms, each one shown as a tile carrying the picture set as its preview in the Administration.

Buildings are added in the Project section of the Administration, with ADD BUILDING at the bottom of the project tree. Each building appears on the home page as an entry with its name, above the symbols of its floors, so that the floors are grouped by building.

1. Name of the first building, Villa.
2. Its floors, F0 and F1: pressing one opens its rooms.
3. Second building, Building 2, just added and still without floors.

Widgets2.4.3.3

The functions of the systems are normally represented in the Visualization as widgets. A widget is a graphical element tied to a specific technology (KNX, MODBUS and so on) that carries the state of a device of the installation and the commands for it. Widgets appear as rows inside a room or inside a function page: each row gives a synthesis of the state and offers a quick command, the switching on and off of a light for instance.

When the function supports it, pressing the name or the symbol on the left of the row opens a popup with all the details and all the commands of that device.

1. The widget in the list: symbol, name and, on the right, the synthesis of the state.
2. Quick command: acts directly from the list, without opening anything.
3. Main commands of the popup: the dial that sets the brightness, the preset arcs and the UP and DOWN buttons.
4. Schedule of the day, when the object has one; see Preview in widgets popup.
5. Further commands offered by that particular device, here the color temperature.

Functions2.4.3.4

Every widget belongs to a category, called a function. Functions organize the widgets inside a room: they appear as blocks, each one gathering the widgets with a similar purpose.

Pressing an icon of that bar restricts the page to a single function, which is convenient in rooms with many widgets.

Which functions are in use is set in the Administration, in the Functions tab of the project card, and each room card can enable them one by one; a function with no widget in a room does not appear in that room.

Favourites2.4.3.5

The favourites page, reached from the navigation menu of the Visualization, is filled by the end user with the widgets, the scenes and the schedules used most often, so that they are all in one place instead of one room away.

To add an element to the favourites:

1. find it in its room;
2. press and hold it for a couple of seconds, until the edit popup opens;
3. in the popup, select ADD TO FAVOURITES.

The same long press is used to remove an element that is already among the favourites. Several widgets can be added in one go, long-pressing each of them.

The page is per user: each account has its own favourites, and what one user adds does not appear to the others.

Project3

The Project section of the bar holds everything that describes the installation as the end user will see it: the project card, with the name, position and language of the installation, the home page and the navigation menu; the building, with its floors and rooms; and the widgets placed in each room, together with the map and the links offered in the Visualization.

Each server holds a single project, created with the server itself: the Project button at the left end of the bar opens its card and switches between Project view and Guest room management view, and has no command to create a further project. A project is replaced as a whole by restoring a backup, from the Backup/Restore tab of the project card.

The settings of the server itself, which apply whatever project is configured, are described in Settings; users, groups and their permissions in Users.

Project card3.1

The settings of the project are gathered in the project card, opened from the Project button at the top left of the bar. It has seven tabs:

Project info holds the following fields:

Name and Location3.1.1

In the Project info tab of the project card, press the icon next to Location: a popup opens in which you set the place where DELÉGO SERVER is installed. From that place the server automatically sets:

• the geographic coordinates of the astronomical clock, which computes sunrise and sunset from them;
• the references of the online weather forecast;
• any other information related to the geolocation of the installation.

Project name, in the same tab, is the name of the project, shown in the Project button.

Language3.1.2

The Language field of Project → Project info sets the language of both the Administration and the Visualization of DELÉGO SERVER.

The supported languages are English, Italian, French and German.

Functions3.1.3

Functions, in the project card, enables or disables the functional categories of the home automation system, according to the customer's needs. Each category is a switch.

Project → Functions

The categories are Lighting, HVAC, Shades, Scenes, Security, Multimedia, Gates, Sockets, Technologic and Irrigation. By default all of them are enabled. If a customer's installation only includes lighting, climate control and motorization, for example, you can leave only Lighting, HVAC and Shades.

The choice is reflected in the Visualization: the row of function symbols at the bottom of the homepage contains only the categories that are still enabled.

A category can also be enabled room by room, with the FUNCTIONS group that appears on the room card when Expert mode is active.

Homepage3.1.4

Homepage, in the project card, customizes the page the end user sees first in the Visualization. The project card is opened from the Project button at the top left of the bar.

Project → Homepage

Confirm with SAVE.

This topic is shown in the Project card video tutorial.

Navigation menu3.1.5

Navigation menu, in the project card, enables or disables the entries listed in the side navigation menu of the Visualization, according to the customer's needs. Each entry is a switch.

Project → Navigation menu

The entries available are Favourites, Security, Energy, Consumption monitor, Guest room management, Graphs, Notifications, Weather, New Scenario, Schedules, Presence simulator, Edit map and Configuration.

In a hospitality building, for example, you can leave only the entries a hotel manager actually uses, so that the navigation menu of the Visualization shows just those pages.

Edit map is the entry that gives access to the customization of a room over its background image, described in the chapter on map customization: if it is disabled, that editor cannot be reached from the Visualization.

It is advisable to keep the Configuration entry always enabled.

Backup/Restore3.1.6

Backup/Restore, in the project card, exports and imports the project, and restores the factory settings. The project card is opened from the Project button at the top left.

The page is divided by the kind of content each operation acts on.

Choose the operation and wait for the message that reports the outcome.

The operations marked as acting on the cloud require the unit to be logged in to a cloud account, which is done in the Cloud section.

This topic is shown in the Project card video tutorial.

Date/Time3.1.7

The clock of the server is set in the Date/Time tab of the project card:

Project → Date/Time

CONFIGURATION OF DATE AND TIME sets the date and the time of the system by hand, with Set time and Set date. After entering them, press SAVE. A warning page appears; see the note below.

TIMEZONE CONFIGURATION sets the time zone the server works in, with Timezone - area and Timezone - city.

SYNCHRONIZE DATE/TIME TO KNX associates two KNX communication objects with the date and the time held by the server, whether set by hand or taken from an Internet service. The two objects can be sent on the bus periodically, so that every device carrying a clock stays aligned.

Setting this up takes a manual procedure, because the two objects have to exist before the tab can offer them:

1. Leave the Date/Time tab.
2. Open the KNX section in the bar, select Other in the context tree and create a Single value component.
3. Open its card and set ETS encoding to a Date (3 bytes) type, then enter the group address in Command and in Feedback.
4. In the same way create a second Single value component for the time, with ETS encoding set to a Time (3 bytes) type.
5. Press UPDATE on the card of the component, so that bus communication starts working with the objects just created.
6. Go back to the Date/Time tab: if everything was done correctly, the group addresses of the two components are now associated automatically.

Once the two objects are in place, the group offers the choice between never sending the telegram and sending it at system start, whenever the date or the time changes, and periodically, with the period expressed in minutes.

SYNCHRONIZE DATE/TIME FROM keeps the clock of the server aligned through an Internet service: Source type chooses the kind of source, Ntpdate server the time server to use, when it has to be different from the default one, and Every (Minutes) how often to synchronize.

This topic is shown in the Project card video tutorial.

Graphic library3.1.8

Project → project card, Graphic library tab

Renderings are the sets of icons and attributes that give the objects their appearance in the Visualization. The server ships with a system library covering the supported object types, and each widget takes its rendering from that library. The Graphic library tab of the project card lists them all.

The SEARCH ICONS / OBJECTS group filters the list:

The GRAPHIC LIBRARY group lists the renderings found, with their NAME, the OBJECT TYPES that can use them, the LENGTH of the value and the VALUES they represent (for example 0:Off, 1:On), and their LEVEL. Each row has three commands, Edit, Copy and Delete, whose icons appear when the mouse pointer rests on the row. The renderings of level System can be neither edited nor deleted: to customize one, copy it and edit the copy, which has level User.

A custom rendering is therefore always obtained by duplicating an existing one and editing the copy, never by building one from nothing. Keep the copy as close as possible to the original, changing only what has to differ, so that the object keeps behaving as the system expects.

Edit on a rendering of level User opens its card.

The card is divided into the following groups:

The colours set in Options are the ones the object wears in the Visualization. To give the HVAC modes a different colour, for instance: filter the list on the keyword HVAC, press Copy on HVAC Operating Mode, then Edit the copy, which appears with level User. In its card change the Name, then in Options the colour of the row Com, and press SAVE. From then on every widget that uses this rendering draws its COM mode in the new colour, as in the mode buttons of the thermostat shown in Thermostat with HVAC mode.

Where a custom library already exists, created on a previous version, it remains in the database and continues to be applied.

Floors/Rooms3.2

The building is described in the context tree of the Project section, on three levels: building, floors and rooms. By default DELÉGO SERVER already has a floor containing 12 rooms, which you can edit, and ADD BUILDING, at the bottom of the tree, adds a further building.

Every node of the tree carries its own actions, which appear on the row when it is selected:

Selecting a floor opens its card in the workspace.

Selecting a room opens the room card.

With Expert mode active, the room card also shows the ID and Description of the object, a SECURITY group with Enable PIN control and the two fields to set the PIN, and a FUNCTIONS group with one switch per functional category, Lighting, HVAC, Shades, Multimedia, Security, Technologic, Scenes, Sockets, Irrigation, Gates. These switches restrict the categories available in that room.

1. ID and Description, shown only in Expert mode.
2. The SECURITY group: Enable PIN control asks for a PIN before the objects of the room can be commanded from the Visualization; New PIN and Repeat new PIN set it.
3. The FUNCTIONS group, one switch per functional category: here only Lighting, HVAC and Shades are on, so only these categories are available in the room.

It is suggested to import images in .jpg or .png format with a maximum resolution of 1024 x 768. Starting from software version 2.7.0, rooms and floors can be automatically created when importing a .knxproj ETS project. Refer to the KNX chapter.

Widgets association3.3

Once a room has been created and configured, one or more widgets are associated with it. The source panel on the right of the Project section has two tabs, and the difference between them is what decides which of the two methods you are using:

The search field at the top of the panel filters the list, which is the quickest way to find a widget when the project contains many of them.

Expanding a room in the context tree lists the widgets it contains. Their order there is the order in which they are displayed in the Visualization.

This topic is also covered in the Adding a device video tutorial.

Map view3.4

A room whose background is a floor plan is shown in the Visualization as a plan: the widgets are not listed one under the other, but placed on the drawing at the point where the device actually is. The position and the appearance of each widget are set from the Visualization itself, with the Edit map entry of the navigation menu, which opens the Customize view page. Only users with administration rights see this entry.

In this page it is possible to:

• drag the widgets to the wanted position on the plan: a widget that has never been placed starts at the top-left corner;
• change how each widget is drawn, using the Options panel on the right.

The Options panel acts on the current selection, and its header reports how many widgets are selected:

Widgets can be selected one at a time or several together, and the alignment is helped by a grid that can be turned on and off. Leaving the page without saving asks for confirmation, because the unsaved changes are lost.

Links3.5

A link is a hyperlink that can be inserted in a room and used to connect an entity to:

• Another room.
• An external URL.
• A third-party app (only in the DELÉGO mobile app), like for example Google Maps.

A link is one of the technology-independent models of the Library, in the source panel of the Project section, together with Scene, Virtual Object, IP Camera and Dico. To create one, drag Link from the Library onto the room that has to contain it, then open its card and fill the following options:

Opening third-party apps3.5.1

When App is selected as the link type, the following information is required:

Adding links to the navigation menu3.5.2

It is possible to add a link to the Visualization navigation menu, by opening Project → Navigation menu in the Administration and dropping the link into the list of items in the menu. The position of the link in the list can be changed by dragging it.

Weather service3.6

DELÉGO SERVER can talk to a weather service on the internet and obtain the current conditions and the forecast for the days to come. That information is available in the Visualization and in the logics, so an action can be made to depend on the weather.

The service lives in the project as an object of its own, described in the next chapter.

The service is not a KNX object and needs no device on the bus: it is a service of the server, listed in the Widgets tab of the source panel of the Project section.

1. The Weather Services group.
2. The Weather service object: its Open action brings up the card described in the next chapter.

Configuration3.6.1

The weather service of DELÉGO SERVER is an object of the project, and it is reached from the source panel rather than from the navigation bar:

• open the Widgets tab of the source panel;
• go down to Other › Weather Services › Weather service;
• use the Open action of that node to bring up its card.

The card asks for the following. Only the first two are visible in ordinary use; the others appear with Expert mode active.

The lower part of the card lists the data the service makes available:

ASTRONOMICAL CLOCK

DATA TODAY, DATA TOMORROW

DATA OF THE FOLLOWING DAYS carries, for each day, the weather conditions and the minimum and maximum temperature forecast.

Every one of these values is an object of the project: it can be used in the logics and as a trigger for other objects.

Schedules3.7

Configuration3.7.1

Any WIDGET or graphical entity visible in the Visualization can be scheduled, so that DELÉGO SERVER sends commands at a given time of day. The schedulers are managed by the end user, directly in the Visualization

When the user creates a schedule for a WIDGET, the scheduler is applied to the sub-object of the widget that has the schedule flag enabled. The flag is in the SCH/TRG column of the table of sub-objects on the card of the widget, which appears when Expert mode is active. Objects that do not have sub-items (e.g. SCENES) can be directly scheduled.

Active schedules visualization3.7.2

Before illustrating how to change or create new schedules, it is important to know how to see the active schedules already present in the project. There are three different methods.

Schedules overview3.7.2.1

Open the navigation menu of the Visualization and select schedules. The page collects every schedule of the project, grouped by function, and opens on the schedules that are active today.

1. Today: the schedules active on the current day, taking into account any exception defined for today's date. This is the view the page opens on.
2. Week: the same schedules seen day by day, with the seven weekdays selectable at the top.
3. Add: opens the list of the objects that can be scheduled, to create a new schedule.

Pressing the preview of a schedule opens it for editing, as described in the following paragraphs.

The Add button leads to a SEARCH page that lists all the schedulable objects of the project (widgets, scenes and the other entities) grouped by function. The bar at the bottom holds one icon per function, and only the functions that actually contain schedulable objects appear there.

This topic is shown in the Widget scheduling video tutorial.

Preview in widgets popup3.7.2.2

The widgets that have a details popup show a preview of the schedule for the current day underneath the main controls, so that the schedule can be read without leaving the object.

1. PROGRAM: the daily profile in force today, drawn on the same 24-hour bar used in the schedules page. It appears only if the object has a schedule; objects without one show no bar.

Context edit menu3.7.2.3

Pressing and holding any item in the Visualization for at least 2 s opens an edit popup, from which you can:

• Change its name.
• Add it to or remove it from the favorites.
• Create or change its schedule(s)

Daily profiles3.7.3

A schedule is made of one or more daily profiles, each of them a list of actions to be carried out within a 24-hour day. Profiles are of two kinds:

• WEEK: associated with one or more weekdays, and therefore repeated every week;
• EXCEPTIONS: associated with one or more specific dates in the year, which override the weekly profile on those days.

A schedule that has just been created is empty: the page shows the two groups, each with a [+] button to add a profile of that kind. The same [+] buttons remain available afterwards, so a schedule can hold several weekly profiles and several exceptions at the same time.

Weekly profiles3.7.3.1

When a weekly profile is added, it has to be associated with one or more weekdays. The seven days are shown as circles under the profile bar: press a circle to include that day, and it turns white to show that the profile is active on it.

Exceptions3.7.3.2

An exception, by contrast, is associated with specific dates: adding one opens a calendar where the days it applies to are selected.

To save the selection press the back button in the top-left corner and confirm the changes.

Disabling profiles3.7.3.3

A daily profile can be disabled with the power button shown next to its weekdays. This is useful to avoid losing the configuration of a profile that is not needed at the moment, for example a seasonal one.

A disabled profile still exists in the project, but it is not executed until it is enabled again.

Profiles can also be enabled and disabled automatically, when a given event occurs, using the Schedule manager model of the Library in Automations → Connections; see Schedule managers.

Actions3.7.3.4

Entering a daily profile opens the list of the actions to be carried out during the twenty-four hours. Each action consists of a value and of the time at which it is sent; the [+] at the bottom of the list adds one.

1. Title of the schedule, which can be edited.
2. Preview of the profile: the actions drawn on a 24-hour bar, with the same colors used everywhere else in the software.
3. Time of the action.
4. Value sent at that time, adjusted with the arrows at its sides.
5. Time mode: manual, sunrise or sunset. The sun and moon icons mark the actions bound to the astronomical clock, whose time follows the position set for the project.
6. Deletes the action.
7. Adds a new action.

When the list is complete, press the back button in the top-left corner and confirm the changes. The preview of the profile is updated everywhere it appears in the software: in the schedules page, in the schedule itself and in the details popup of the object.

Scenes3.8

DELÉGO SERVER offers the possibility to create sequences of commands and actions, optionally

governed by delays or conditions, called SCENES or SCENARIOS. SCENES/SCENARIOS can be created

in the Administration, by installers and system integrators, or directly in the Visualization by the end user.

Adding a scene to the project3.8.1

To create a new scene in the Administration, proceed as follows:

• Access the Administration.
• Open the Project section and drag the Scene model from the Library of the source panel onto the room that has to contain it.
• Use the Add action of the node in the context tree to create a new scene.

In the details page, the following parameters are available:

With Expert mode on, the following options are also visible:

Adding an action to a scene3.8.2

Once a SCENARIO is created with the scene:

• Look for the objects you want to control in the scene by filtering the source panel, then select them (you can use the CTRL key of the keyboard if you need to select more than one object). If you need to search KNX objects belonging to KNX widgets:

○ Activate Expert mode from the Configuration menu. ○ Enter a keyword in the filter of the source panel (e.g., KNX address or label). ○ Select the object from the results.

• Drag the object(s) into the ACTIONS section, arranging the objects in the order in which the actions must be executed.
• For each object, specify the ACTION to perform and, if required, the VALUE to set. In case of KNX objects, select “WRITE” as the action and the value - among those proposed, based on the type of object - to send on the bus when the scene is executed.

If a WIDGET is dropped into a SCENE, the following dialog is displayed:

Since a WIDGET is a collection of objects, representing different commands that can be sent on a fieldbus (KNX, MODBUS etc…), it is required to specify which of them must be commanded as an ACTION of the SCENE.

Delays3.8.3

It is possible to add a delay between the actions of a scene. In the Administration, the procedure to add a delay to a SCENE is the following:

• Enter the keyword “wait” in the SEARCH
• Select the desired predefined delay(s)
• Drop them into the ACTIONS list, at the desired position in the sequence

The following predefined delays are available:

• 1/2/5/10/15/20/30 seconds.
• 1/2/5/10/15/20/30 minutes.
• 1/2/3/6/12/24 hours.

During a delay, the SCENE can be stopped in two different ways:

• By pressing the STOP button in the Visualization
• With an AUTOMATION which sends the STOP command to the SCENE

In both cases, when a scene is stopped, the actions that follow the WAIT in the sequence are no longer executed. Note that the scene is not reverted to its initial state.

Creating a scene in the Visualization3.8.4

Selecting New Scenario in the navigation menu of the Visualization opens the editor of a new scene:

1. Name of the scene, edited directly in the title of the popup.
2. Room the scene belongs to, so that it appears in that room of the Visualization.
3. ADD: look for an object and add it to the sequence.
4. SNAPSHOT (LEARN): take the objects already in the sequence to their current state, so that the scene commands them to that state instead of the one recorded before.
5. SORT: change the order in which the actions are executed.
6. DELETE: delete the scene for good.

Pressing ADD shows all the widgets available, grouped by function; typing one or more keywords in the title of the popup filters the list.

1. The [+] that opens the search.
2. The objects that can be added, grouped by function; the bar at the bottom filters them by function, and the dots tell how many pages the list takes.
3. Removes the action from the sequence.
4. Adds a delay before this action: raise the seconds, minutes or hours to insert a pause in the sequence.
5. Name of the object commanded.
6. Value that is sent every time the scene is executed, changed with the arrows at its sides.

Executing scenes3.8.5

To execute a scene from the Visualization, find it in the room it belongs to and press the PLAY button on its right.

1. PLAY: runs the sequence. If the scene is enabled for the stop, pressing the button again interrupts it.

Settings4

Configuration menu4.1

The Configuration menu, opened with the gear symbol at the right end of the bar, collects the commands that act on the whole server.

The first entry, Settings, opens the settings of the server, described in detail in the following chapters. They concern the server itself and apply whatever project is configured. They open in a workspace of their own, with a single panel and one tab per group of settings.

System4.2

Settings → System, reached from the Configuration menu, reports the state of the unit and holds the recovery commands.

DEVICE INFORMATION reports the Serial number and the Hardware code of the unit, the two items of information that Ekinex customer service asks for.

SYSTEM STATUS reports the time elapsed since the last start and the free and used RAM. DOWNLOAD saves the Log file and the SSL certificate, to be sent to customer service when requested.

SYSTEM ACTIONS holds four commands.

This topic is shown in the Server settings video tutorial.

Options4.3

The Options tab gathers the settings that govern the behaviour of the project, arranged in groups: E-MAIL, SIP, MAP VIEW, FUNCTIONS VIEW, CHARTS and the advanced parameters. Each group is described in the chapters that follow.

Email settings4.3.1

The E-MAIL group of Settings → Options sets how the server sends the email notifications. Two methods are available, chosen with E-mail sending method.

Cloud service. Nothing else has to be configured: the server hands the message to the EKINEX cloud, which delivers it. The unit must be logged in to the cloud account, which is done in the Cloud section.

Custom SMTP server. The server delivers the message itself, through a mail server you provide. Enter the following:

A configuration using Gmail, as an example:

Map View settings4.3.2

The MAP VIEW group of Settings → Options governs how rooms configured with a graphic map are displayed.

Confirm with SAVE at the bottom of the page.

Functions view settings4.3.3

Element Display, in the FUNCTION VIEW group of Settings → Options, sets how the rooms are arranged in the function pages, the ones the end user reaches from the bar at the bottom of the home page. Three criteria are available.

Compact. Rooms are grouped by floor, in columns, and only the state previews of the widgets are shown. Pressing a preview sends the command to the corresponding widget. A vertical scroll moves through the rooms of a floor, a horizontal one through the floors.

Opening the detail of a room expands it to show all its widgets, with the commands available for each.

Dynamic. The rooms are arranged automatically to make the best use of the space available in the window.

Floors. The rooms are presented floor by floor, following the structure of the building.

Advanced settings4.3.4

The ADVANCED group at the bottom of Settings → Options tunes how the clients talk to the server. The default values suit most installations: change them only for a specific reason, because they affect responsiveness and load.

Confirm with SAVE at the bottom of the page.

Network4.4

The network parameters of the server are set in Settings → Network, reached from the Configuration menu.

NETWORK INFORMATIONS reports read-only data.

NETWORK CONFIGURATION holds the addressing.

An indicator beside the section reports whether the device is reachable. REFRESH updates it; RESTART restarts the network services.

IP ALIAS adds a second address on which the server answers, for networks that require it. Enter the address and its subnet mask, then confirm with SAVE.

This topic is shown in the Server settings video tutorial.

Software update4.5

The software of the server is updated from Settings → System Update, reached from the Configuration menu.

The page reports Software version, the version currently installed, and Last software version, the most recent one found on the EKINEX cloud. Update type chooses between Automatic and Manual.

Automatic. The server checks the cloud by itself. If a newer version is available, Update starts the procedure.

Manual. Use this when the unit has no internet access:

1. Ask Ekinex technical support for the latest package and save it on the PC without unzipping it.
2. Select Manual.
3. Choose the package with the file selector.
4. Press Update.

In both cases the procedure runs on its own. It can take several minutes, depending on the installed version and on the size of the configuration. Wait for it to finish without reloading the page or closing the browser. At the end a summary of the new version is shown; restart the server to complete the installation.

If the update is interrupted, for example by a power failure or by the loss of the network connection with the PC:

1. Restart the server.
2. Wait about 1 minute, then open the address of the server in the browser.
3. Let the automatic recovery finish, then restart the server again.

The same recovery also starts after a hard reset from the reset button. If the unit has not recovered after at least 15 minutes, contact Ekinex technical support.

External memory management4.6

An external memory, USB or SD, extends the space available for the data the server records at runtime and for the traffic captured by the KNX telegram recorder. It is configured in Settings → External SD, reached from the Configuration menu.

Select the kind of device connected in Type, choosing between USB and SD. The page then reports whether a memory is inserted and activated, its size, the space used and free, and whether writing is enabled.

Vouchers4.7

Several functions of the server are tied to an activation code. The codes are managed in Settings → Vouchers, reached from the Configuration menu.

The page opens with the Serial number and the Hardware code of the unit, which Ekinex customer service needs in order to issue a code. Below them each module has its own field, with the state of the license beside it: a valid license is reported as such, and some modules also report their capacity, for example the number of KNX group addresses in use out of those allowed, or the number of rooms enabled.

To enter a new code, request it from Ekinex customer service, type it in the field of the module it belongs to, then confirm with SAVE. Take care to match the code to the right module: a code entered in the wrong field is not accepted.

This topic is shown in the Server settings video tutorial.

Account5

The user menu, at the right end of the bar beside the Configuration menu and marked with the name of the current user, holds the operations on the session.

Password change5.1

Any user, even with basic rights, can change their access password with Change password, in the user menu at the right end of the bar. The command opens the card of the current user, where you can change the username and enter a new password, which takes effect as soon as it has been entered correctly twice.

Product registration5.2

It is possible to register DELÉGO SERVER on Ekinex’s cloud to have access to exclusive services (e.g., VPN).

The EKINEX cloud services are gathered in the Cloud section of the bar.

The first step is to create a free cloud account, if you do not have one already. Open

Cloud → Cloud Services

and click REGISTER to be redirected to a page where you can create a new account:

Once the credentials are entered, it is possible to associate the current user (the one you entered in DELÉGO SERVER) to your cloud account. It is possible to choose between two types of profile:

At this point you can access the following pages of the Cloud section:

Cloud login5.3

Each user of DELÉGO SERVER can be associated with an EKINEX cloud account. The user logs in with the credentials of the cloud account and binds the server to it with one of two levels:

The first login and the creation of the cloud account are described in Product registration.

Once the user is logged in, the entry of the user menu becomes Cloud account.... Pressing it opens a popup from which you can:

• log out of the cloud account;
• unbind the server from the cloud account;
• change the binding level, from OWNER to INSTALLER or the other way round.

Being logged in also gives access to the cloud services and to voice control, described in Cloud services and Voice control. The cloud VPN is described in Cloud VPN.

Users6

This chapter illustrates DELÉGO SERVER’s user management and how to customize it according to your needs, to guarantee security and differentiated access to the supervision pages.

Users and user groups6.1

Authentication in DELÉGO SERVER rests on two distinct things, which the Users section keeps in two separate tabs:

• Users are the accounts used to sign in, each identified by a username and a password. A user holds no permissions of their own; what a user may do is determined by the user groups they belong to.
• User groups hold the permissions on the functions of the software. Changing a permission on a group changes it at once for every user belonging to it.

Creating a new user6.2

A new user is created in the same way as the other types of object seen so far:

• Open the Administration.
• Open the Users section of the bar, Users tab.
• Use the Add action of the node in the context tree, then open the card of the newly created object.

The card allows you to set the following properties:

QR CODE generates the code that carries the access data to the server, so that it can be shared with the user instead of being dictated.

TRIGGERS, at the bottom of the card, lists the conditions that concern this user: an object is dragged into the table from the source panel, and for each row the condition, the action and the value are set.

User groups and access rights6.3

The User groups tab of the Users section is where the kinds of user that may reach the server are defined: installers, maintenance staff, tenants and so on. A new project comes with three groups: Administrators, User and Access manager.

Once a user has been created as described in the previous section, it is assigned to a group by dragging it into the USERS table on the card of the group, either from the context tree or from the source panel.

The same card can also be given one or more objects of the supervision, which makes them private: only the users belonging to that group can see and command them. The objects are dropped into the OBJECTS table.

Restricting access6.4

Access to the objects of the project can be restricted to some users only: an object associated with one or more user groups can be viewed and controlled only by the users belonging to one of those groups. For example, in a building containing an apartment A and apartment B, each user can see only the apartment they are associated with. To obtain this configuration, open the Users section of the bar, Users tab, and

• Create an USER A for apartment A.
• Create a USER B for apartment B.

Subsequently in the User groups tab of the same section:

• Create a USER GROUP A.
• Create a USER GROUP B.

In USER GROUP A:

• Drag user A into the USERS table.
• Drag into the OBJECTS table the floor, the rooms and all the objects the user has to see.

Perform the same procedure for USER GROUP B.

The card of a group has a USERS table, listing who belongs to it, and an OBJECTS table, listing what those users may see. Both are filled by dragging from the source panel.

In the Users section, User groups tab, open Administrators and drag all the floors, rooms and objects present in the building into the OBJECTS table. In this way, the admin will be the owner of all the objects of the installation, while users A and B can see and control only the objects assigned to them.

Default passwords6.5

Changing the default password of every user that comes pre-installed in DELÉGO is of fundamental importance, and all the more so when the server is reachable remotely.

As long as at least one of the predefined users still has its default password, the Administration shows a red band at the bottom of the page: One or more users have the default password. Change password for all predefined users to increase security.

Access with QR code6.6

Reaching a DELÉGO SERVER from the iOS and Android apps can be made easier by generating a QR code, one for each user, carrying all the access information: whoever scans it does not have to configure the app by hand.

The QR code is built out of two things. The addresses of the server come from the project card:

Project → Project info

where Local IP address reports the address the server has on the local network and Remote address the one to be used from outside: the address assigned by the cloud, when the remote access service is active. Both are filled in by the server and cannot be edited.

The user is the second half. Open

Users, tab Users

select the account in the context tree and press QR CODE on its card: the code produced belongs to that user and carries their credentials.

Once the DELÉGO app is installed on a smartphone, the user creates a new project by scanning the code, or by opening the image received from the installer.

Access log6.7

The access log recorded who connected to DELÉGO and when, with a filter by date range, and was reached from the Users section of the Administration.

Notifications7

Notifications are messages that DELÉGO SERVER sends to the users when specific actions, called TRIGGERS, occur. They can be sent as push notifications, shown in the Visualization and on the smartphone, as messages on a DELÉGO PANEL, as e-mails or as Telegram messages.

They are configured in the Notifications section of the bar, whose context tree groups them by channel: Push notifications, E-mail notifications, Telegram notifications and Delégo Panel notifications, each with the notifications already defined below it. The last node is Notification log, the history of everything that has been sent. The building tree is shown above them, so that a notification can be referred to the room it belongs to.

Push notifications7.1

Push notifications are shown in the Visualization, in a specific popup accessible in the navigation menu that opens automatically when a message of type “alarm” is received, and are also sent to the smartphones that have the DELÉGO mobile app installed. They reach the phone even when the app is closed or in the background, or the device is in standby. To create a push notification:

• Access the Administration.
• Open the Notifications section and select Push notifications in the context tree.
• Use the Add action of the node in the context tree.
• Access the edit page of the new object created.

To configure a notification set the following information:

Once a notification is created, it has to be associated with an object through a trigger, so that when the state of that object changes the system generates the message. To link a notification to a trigger, drag the object or objects from the source panel into the TRIGGERS table of the notification, and select which values should be used for the trigger condition. Use the filter at the top of the source panel to find the object.

1 Refer to the Connections chapter for further details about the TRIGGERS

Email notifications7.2

Email notifications are sent to one or more recipients when a specific TRIGGER occurs. To create an email notification:

• Access the Administration
• Open the Notifications section and select E-mail notifications in the context tree
• Use the Add action of the node in the context tree.
• Access the edit page of the new object created.

To configure a notification set the following information:

The keywords available in the message body are:

In Expert mode it is also possible to enter CC and BCC addresses.

1. Name of the notification and Active, which switches the notification on or off.
2. Recipients, and the CC and BCC addresses shown in Expert mode.
3. Mail's subject and Message.
4. The Dynamic tags that can be used in the message, each with its ADD button.
5. The TRIGGERS table, where the objects that send the notification are dropped.

After creating a mail it is necessary to link the trigger to an object; the procedure is the same as for push notifications.

The sending of email notifications depends on the settings of the E-MAIL group of Settings → Options (see Email settings).

Telegram notifications7.3

DELÉGO SERVER can send its notifications to the TELEGRAM instant messaging service, so that they reach a phone without the DELÉGO app being involved.

Preliminary operations7.3.1

Creating a BOT on Telegram7.3.1.1

Once the Telegram app has been installed on your device, you need to create a new bot, which will be associated with DELÉGO SERVER.

To create a new bot, you need to search for the @BotFather (the “father” of all bots) in the Telegram app, which will allow you to create and manage new ones, whenever you want.

Then type /newbot and follow the interactive instructions. First you will need to give your bot a name, for example

Home

and then choose a username, which must be unique and must end in ; for example

DelegoBot

At this point your personal bot is ready to be used; @BotFather provides an API key, which is then used in DELÉGO SERVER..

Copy the code you just received for configuration with DELÉGO, and use it in the next steps.

Configuration7.3.2

Creating a BOT on DELÉGO SERVER7.3.2.1

Access the section in the menu administration

the Notifications section, node Telegram notifications, and use its Add action to create a new bot. Enter the API key issued by @BotFather in the API key field, and give the bot a name.

Then start the service clicking the START button; from this moment DELÉGO SERVER and your personal bot will be connected. It is necessary to open the Telegram application again and search for the newly created bot by typing @ before the username you chose.

Giving permissions to chats and users7.3.2.2

The bot can be talked to directly, or added to a Telegram group. Either way, the user and the chat have to be authorized before the bot will deal with them, and the first step is simply to start the conversation: send a “Hello” in the chat.

After pressing REFRESH, a new row appears in the Chats list and in the Users list. Both have to be authorized, with the Authorize flag, before the bot interacts with them. A chat can also be enabled to receive the notifications sent by DELÉGO SERVER, with its Notifications flag.

Delégo Panel notifications7.4

DELÉGO SERVER can send messages straight to one or more DELÉGO PANEL units. This kind of notification appears on top of whatever app is running on the panel and, depending on the settings of the panel itself, plays a sound. To receive it, the NOTIFICATION CENTER app has to be installed on the panel first.

After creating a new notification, its card asks for the following:

The text may contain three dynamic tags, replaced when the notification is sent: {{obj.name}} with the name of the object that raised it, {{obj.current_value}} with its value at that moment, and {{obj.id}} with its identifier.

The Triggers list at the bottom of the card decides what causes the notification to be sent: drop into it the objects whose change of state has to raise it.

Notification log7.5

Notification log, the last node of the Notifications context tree, keeps the history of all the notifications sent by DELÉGO.

SEARCH OPTIONS restricts the history to a period, with the two date fields. The result appears below, headed by the number of entries found, in a table with the following columns:

Cloud8

Introduction8.1

This chapter contains all the information for configuring and using the services based on the EKINEX cloud that extend the local operation of DELÉGO SERVER.

Most of the services described are based on the EKINEX CLOUD platform, which requires a free account to be registered before it can be used; once created, the same account can be used for all the products and applications provided by EKINEX, not only limited to the DELÉGO suite.

Ekinex Cloud8.2

The Cloud section of the bar associates the DELÉGO SERVER with the EKINEX cloud and manages the related services. It has two pages:

Among the services listed in CLOUD SERVICES is the VPN, which gives full access to the home network where the webserver is installed. It can be used as an interface for the remote commissioning and maintenance of the KNX bus, and to reach other devices on the same network for their configuration. The desktop version of the DELÉGO app is required to get access to the cloud VPN from a PC or Mac.

The online services based on the EKINEX cloud are described in the following chapters.

Cloud services8.3

Remote access8.3.1

The CLOUD SERVICES page activates the Remote accessibility service, which lets you reach DELÉGO SERVER without opening IP ports on the home router. By pressing the ACTIVATE button, a request is made to the cloud, which after a few seconds sends a confirmation email to the requester (the same email with which the cloud section was accessed) containing:

• The address that can be accessed remotely (to be entered directly into the browser, or into the app DELÉGO)
• The expiry date of the service

The remote control service is free. Once the service is active, it is possible to see the remote server address of DELÉGO SERVER on the following pages:

• Settings → Network, in the NETWORK INFORMATIONS group, as Domain or public IP
• the QR CODE button on the card of a user, in the Users section

Without this service both fields would have to be filled in by hand with your public IP address or dynamic DNS name. With the service active they can no longer be edited: the cloud address can only be copied, to be used in a browser or in an app, or shared with other users.

Since the cloud address is made up of random characters, and therefore not easy to memorize, it is recommended to share access to DELÉGO SERVER via QR, as illustrated previously.

The DELÉGO SERVER exchanges information with the EKINEX cloud using port 5223. This does not pose any problem for home routers which have all outgoing ports open. If DELÉGO SERVER is used in a network with a firewall also for outgoing purposes (e.g. corporate network), port 5223 must be open for outgoing traffic only, for the IP address assigned to DELÉGO SERVER.

As an alternative to the remote accessibility cloud service, you can configure a port forwarding in your internet router, redirecting port 443 of the webserver (on the local network) to port 443, or another port of your choice, on the public address. In this case, it is advisable to enter the public IP address (if static) or the dynamic domain name (dyndns) in Settings → Network.

Access via a direct port is however not recommended, compared to cloud access, as it is less secure, and is conveyed through so-called “self-signed” SSL certificates present within the webserver, which imply security warnings when accessed with the browser or the app, or (in certain cases) the inability to access remotely.

Cloud backup8.3.2

Thanks to this service, a copy of the project’s database can be exported on the cloud, and imported into the same DELÉGO SERVER or another one. Besides manual backups, a cloud backup is also saved automatically every day.

In order to use this service, you must be logged in to the EKINEX cloud service from DELÉGO SERVER, as explained in the Product registration chapter.

By opening the Backup/Restore tab of the project card

Project → Backup/Restore

the following options for cloud backup are available:

Cloud sync8.3.3

This section describes how to synchronize DELÉGO SERVER with the cloud and how to select the graphic components that can be controlled by external services, such as Alexa and Google voice assistants. It is advisable to identify your DELÉGO SERVER with a label and the geographical coordinates of the location where it is installed. This allows an easier identification of the server on the cloud. After any change, press SYNC. This can be done in the following section:

Project → Project info

Cloud synchronization is decided widget by widget, on the card of each one, in the CLOUD block.

Turn Enable cloud sync on for each widget that has to reach the cloud. The selector stays orange until the synchronization has actually run: orange means the choice is saved in the project but not yet pushed to the EKINEX cloud.

Once every widget has been chosen, press the cloud indicator in the bar to review the summary and start the procedure with SYNC.

At the end of the procedure, all objects will be marked in green, until a new change to their configuration occurs; in the latter case, it will be necessary to perform a synchronization again. The status of the CLOUD indicator – green or red – indicates whether or not there are objects to synchronize.

If an object continues to be orange after a synchronization, you need to check its configuration; in the case of composite graphic components, for example, the minimum number of sub-objects essential for its correct management via the cloud may be missing.

Voice control8.3.4

Once the graphic components have been correctly synchronized, it is possible to control them via the voice assistants Alexa and Google Assistant, through the management of the smart home of the respective systems (“Alexa” app in the case of Amazon, “Home” for Google). This chapter will describe the procedure for Alexa.

The first step is to activate the EKINEX option in Alexa or Google Home apps; during the procedure, you are asked to associate the EKINEX cloud account. Then it is necessary to execute a scan to search for new devices. Once the procedure has been completed, it is possible to associate each device to a group, to identify it easily and be able to issue group commands, or refer to it verbally using the name of the group. At this point, it is possible to control the new functions with your voice, or with the graphics of the Alexa / Google Home app. For a list of specific keywords, refer to the Alexa and Google Assistant documentation. Here are some examples of the most common requests using Alexa:

Alexa, turn on the light in the kitchen Alexa, set the living room light to 70% Alexa, increase the light in the room by 20% Alexa, tell me the temperature in the living room Alexa, set the kitchen temperature to 21 degrees Alexa, run turn everything off

Please note that not all DELÉGO SERVER features can be managed with Alexa and Google Assistant, because the device models of these systems are far simpler than the functions a KNX system offers. For this purpose, an indicator has been introduced in DELÉGO SERVER, which highlights whether a specific graphic component / object (or which sub-objects are, in the case of composite graphic components) can be controlled by voice.

That indicator is the VOICE column of the address table on the card of the widget, shown in the figure of the Cloud sync chapter: a speaker in full color marks a datapoint an assistant can reach, a grayed-out one a datapoint it cannot.

The use of DELÉGO SERVER with Amazon or Google voice assistants requires the use of port 8883 for updating states and commands. This is not a problem for home routers with all outgoing ports open. If DELÉGO SERVER is used in a network with a firewall (e.g. company network), port 8883 must be open only for the IP address assigned to the DELÉGO SERVER.

Where voice assistants are to be used, the widgets of the Other family, Single value and Generic, cannot be synchronized on the cloud: use only widgets from Lighting, HVAC and Shades.

Quick commands on the mobile app8.3.5

The DELÉGO app for mobile devices provides a set of quick commands accessible directly on the initial graphic page of the app, convenient for multi-system management. In fact, it is possible to carry out commands and view the most frequently used and/or most important states (for example garage opening and closing) to manage a system without directly accessing the complete graphic interface.

The procedure for configuring shortcuts on the app requires you to follow these steps.

1. On DELÉGO SERVER create an EKINEX cloud account, to be associated with every server whose installation the DELÉGO app has to display. The account must be unique for all servers that belong to a multi-installation configuration. The account may not necessarily be the account with which the remote access service is associated. To create an account, open the Administration on the DELÉGO SERVER and go to Cloud → Cloud Services. Once the account has been created, the same account can be used to associate other servers.
2. On DELÉGO SERVER, bind the created account with each of the servers for which DELÉGO app must display the shortcuts on the app. The binding must be done as Owner.

3. On DELÉGO SERVER activate the cloud synchronization checkbox for each of the widgets you intend to expose in the shortcuts.
4. On DELÉGO SERVER synchronize all the widgets for which the cloud check-box has been activated to the cloud. To carry out this operation, in the Administration go to Cloud → Voice control, press the SYNC button and wait for all the checkboxes to turn green, with the Last sync field updated to the current time.
5. On the DELÉGO app, open the contextual menu at the top right of the app title bar and select Connect Ekinex account: enter the credentials of the account created in point 1. Once connected, the configured quick commands will appear on the main page of the app for each system.

Cloud VPN8.4

Starting from version 2.5.2, it is possible to connect directly to the home network where DELÉGO SERVER is installed, from a PC / Mac, through a VPN connection based on the EKINEX cloud.

This connection is useful to remotely:

• Program KNX devices or do diagnostics with ETS PROFESSIONAL.
• Change the configuration of EKINEX connected devices (DICO intercom, DELÉGO Panels, etc.).
• Access any other network-based device, in the same way it would be possible being physically attached to the LAN.

Each DELÉGO SERVER has its own dedicated VPN, isolated from the others, and uses WireGuard tunnel technology, to ensure the maximum degree of robustness and security. No configuration is required on the internet router / firewall.

The cloud VPN service is available only on the 4 DIN rail modules hardware version of DELÉGO SERVER. The older version of 2 DIN rail modules does not support it.

The “old” local VPN, based on an internal server and requiring a port forwarding rule on the router, is no longer available starting from release 2.7.0.

Service activation8.4.1

In the Administration, after having done a cloud login with a valid EKINEX cloud account, open

Cloud → Cloud Services

and identify the VPN service.

Press the ACTIVATE button and wait until the list reloads and the service becomes active.

The VPN service will “belong” to the cloud account used to activate it. It is your choice to associate it to the installer account, or the property manager (owner) one.

VPN creation8.4.2

Once the VPN service has been activated, enter the section

Cloud → VPN

and enter a name, to be associated with the VPN. This name will be reported in email and push messages, therefore it is suggested to give a name reminding the building / installation.

By default, for security reasons, DELÉGO SERVER does not allow access to any other device in the home network (LAN) except itself.

It is possible to optionally expose one or more devices, or network subnets, by entering the following informations:

• To expose a single IP address, enter it in the text fields, and press ADD.
• To expose a subnet, enter only the first parts of the address, by leaving the last part(s) empty. In this case all the IP devices matching the numbers entered will be reachable remotely.

In some sections of the webserver, mobile app and client for the VPN connection, the so-called “CIDR” notation is used to represent the exposed addresses.

Please refer to the following table, containing some examples, to clarify the different notations:

192.168.1.254

Press the CREATE button and wait until the VPN information appears on the page, like in the following example:

If you want to reach the DELÉGO SERVER with its IP address in the home network (LAN), this address must be added to the exposed IP addresses list.

Otherwise, the DELÉGO SERVER will be only reachable with its VPN address, the one reported under STATUS.

The new VPN is enabled by default: this means that all the cloud accounts, entitled to have a connection, will be able to connect.

Deselect the corresponding flag and press the UPDATE button to make it disabled by default; the owner(s) will enable it with the DELÉGO mobile app, as described below.

After any change to the configuration, press the UPDATE button to apply it. To erase an existing VPN completely, press DELETE.

Connections8.4.3

In order to connect to the VPN, installers must have one connection for each PC / Mac they will use to remotely access the home network. Use the Add action of the node in the context tree and enter the following information:

• A label that identifies the PC / Mac used for the connection.
• The cloud account associated with the connection.
• The enable (grant) status of the connection.

Only the cloud accounts associated with the DELÉGO SERVER can be selected for the connections. In order to grant access to new accounts:

1. Create a new local user in DELÉGO SERVER in the Users section.
2. Log in with these credentials, then log in to the desired cloud account in Cloud → Cloud Services.
3. Bind the cloud account as OWNER or INSTALLER by pressing the corresponding button (once the cloud login has been done).

Once the SAVE button has been pressed, two further buttons become available:

• The DOWNLOAD button is used to download the configuration file, necessary to set up the VPN connection on the PC/Mac of the installer that needs to connect to the DELÉGO SERVER.
• The QR CODE button is used to download the QR code that can be used on a VPN tool to set up automatically the VPN connection to the DELÉGO SERVER.

Any time a change is done on the configuration of the VPN (e.g. changing the exposed IP addresses) it is necessary to download a new configuration file or QR code.

In that situation, a yellow warning indicator blinks close to the connections to be downloaded again.

Starting and stopping the VPN8.4.4

By default a VPN is stopped, and has to be started by hand whenever a remote connection to the home network is needed. This can be done by pressing the START button in the VPN configuration page in DELÉGO SERVER, or with the mobile app (as described in the dedicated section later). A VPN connection stays active for 2 hours, then stops on its own. To stop it manually, press the STOP button, when it is no longer needed.

If a longer connection is needed, the VPN can be simply stopped / started again, any desired number of times.

The Status section also contains the IP address of DELÉGO SERVER inside the VPN, in the IP Address row.

Use this IP address to “point” to the webserver, in order to:

• Access its web pages.
• Use it as an IP interface for ETS PROFESSIONAL.

Control with the mobile app8.4.5

Requirements8.4.5.1

The DELÉGO mobile app can drive the VPN of a DELÉGO SERVER, provided that:

• an EKINEX cloud account has been entered in the settings of the app;
• at least one DELÉGO SERVER carries a valid cloud remote address;
• the servers are associated with that cloud account, with Owner or Installer rights.

A project whose VPN is available shows a padlock on the right of its title. Pressing it opens the VPN control screen, described in the paragraphs that follow.

Owner view8.4.5.2

The following picture shows the typical VPN section content for an owner account:

If the owner is not associated with a connection, the START / STOP button is not visible; this action, in fact, is useful only to users who need to connect from their PC / Mac.

If the VPN is not enabled, all the contents are hidden, and the only possible action is to enable it:

Each account with an associated connection can be enabled or disabled with the corresponding control: in general, a VPN can be enabled (green indicator in the initial part of the screen) but the single users can be disabled. In this case, they cannot connect. When a user connects through one of these connections, the state goes to green.

The server info section contains details about the connection of the webserver to the VPN, its IP address, and all the other reachable IP addresses.

After any Enable, START / STOP or grant operation it may take up to a minute for the connection to be established again and for the status indicator in the app to line up with the webserver and the connected computers.

Installer view8.4.5.3

The VPN section as an installer sees it contains less information, as in the following example:

If the VPN is disabled, or the installer has not been granted access, the only allowed action is to send a request to connect:

Notifications8.4.5.4

When an installer asks to connect, a push notification and an e-mail go out immediately to every owner of the webserver. Pressing the notification opens the DELÉGO app straight on the VPN concerned, where the Enable control is all that has to be operated.

The same notifications are sent when:

• a VPN is enabled or disabled;
• a VPN is started or stopped;
• a connection is granted to a user, or refused.

Remote VPN Connection8.4.6

Installing the DELÉGO app8.4.6.1

To connect remotely to the home network, you need to use the desktop version of the DELÉGO app, which can be downloaded for free from DELÉGO app on the Ekinex website:

https://www.ekinex.com/en/delego-server/new-delego-server.html

Once installed, open the app and enter your computer's administrator password when prompted (this is required to have the necessary permissions to open VPN connections). The app's main screen looks like the following figure:

Cloud login8.4.6.2

Reaching an installation over the VPN requires authenticating with an EKINEX cloud account.

Press the settings button, select Connect Ekinex account and enter the e-mail address and the password of the account.

Accessing the VPNs8.4.6.3

If the connection to the cloud is successful, a menu appears in the system bar containing the list of CLOUD VPNs to which your account has access.

If one or more webservers have also been configured as systems (see next point) they appear at the beginning of the list, otherwise they are listed in the “Other VPNs” section as in the following example (which shows the macOS version):

The first time you connect to a VPN, you need to press the SETTINGS item; a screen similar to the following is displayed:

In the CONNECTIONS section, a new connection is automatically created for your PC / MAC, associated with your cloud account. This connection is initially disabled; if you have an installer profile, you must request access via the appropriate button at the top of the popup, and wait for the building owner to authorize your user to connect.

If, on the other hand, you are the owner, you can enable the connection, with the appropriate selector.

By pressing the CONNECT button, you can establish a connection to the building's local network through the CLOUD VPN; after a few seconds, the status indicators turn green, and the statistics on connection time and exchanged data traffic begin to update.

The IP address of the webserver in the VPN is shown in the section below, containing the server data; you can copy it to the clipboard with the appropriate button, so that it can be pasted into other applications (for example ETS Professional).

After the first connection, you can monitor the connection statistics and start or stop the connection directly from the system tray. It also displays the time remaining before the connection stops automatically, and it is possible (via the dedicated button, by opening the settings) to reset the countdown, if the maintenance intervention requires more than 2 hours.

Adding projects8.4.6.4

To browse the supervision pages of a DELÉGO SERVER it has to be added as an installation:

• press the [+] button;
• enter a name, the login credentials, the IP address and port for the local network, and the cloud address, in the form XXXXXXXX.ekinex.cloud;
• save.

The configured installations are listed in the menu on the left. Clicking one opens its supervision in the main working area, much as a web browser would; the app decides on its own whether to go through the local address or through the cloud.

KNX9

Introduction9.1

This chapter contains all the information for configuring and visualizing a building automation system based on the KNX standard, inside DELÉGO SERVER, the multiprotocol webserver for the connected buildings by EKINEX.

Preliminary operations9.2

Connection9.2.1

DELÉGO SERVER is a DIN-rail module intended for the installation in an electric cabinet, and directly connected to the local network (it can be powered via PoE) and to the KNX bus. The bus is wired with a certified KNX TP (twisted pair) cable to the standard red and black KNX terminal supplied with the module.

It is also possible to interact with the KNX installation through the IP network, by configuring the communication driver as described below.

The connection to the KNX bus is not strictly essential in order to configure it; however, it is not possible to verify the correctness of the project or simulate the automation functions configured on the server until this connection is established.

ETS library9.2.2

It is recommended to add the DELÉGO SERVER library into the ETS project, by searching for it in the online catalog, or downloading it from the EKINEX website.

When the library is added to a project with KNX Secure enabled, ETS asks for an (optional) project password:

The library offers only a KNXnet/IP tunnelling interface, as an IP interface, without any parameter to be set nor communication object. It is only necessary to assign a unique address, to be entered in DELÉGO SERVER.

The ETS library is compulsory in case of KNX Secure projects. Otherwise, it is not strictly necessary, even if it’s recommended.

Communication settings9.2.3

Open the KNX section of the Administration. The same page that holds the ETS import also holds the KNX - PHYSICAL ADDRESS and COMMUNICATION INTERFACE blocks, with all the settings related to the communication with a KNX installation, as better described in the following paragraphs.

This topic is also covered in the KNX widget card video tutorial.

KNX physical address9.2.3.1

Enter the physical address of DELÉGO SERVER in the Physical address field, in the KNX - PHYSICAL ADDRESS group of the KNX section.

The address must be specified in the X.Y.Z format respecting the limits imposed by the KNX protocol:

• First number between 0 and 15
• Second number between 0 and 15
• Third number between 0 and 255

When a driver with the “ETS remote” support is selected (see the next paragraph for further details) it automatically allocates the next 10 physical addresses not only for its communication with the bus, but also for ETS remote control (the reserved addresses are shown on the screen, like in the following figure).

Both the base address and the 10 reserved addresses must be free within the project and not used by any other KNX device.

Communication driver9.2.3.2

The driver is selected in the Driver field of the COMMUNICATION INTERFACE group, at the bottom of the KNX section. Starting from version 2.6.0 it is possible to choose between the following KNX communication drivers:

The drivers supporting the ETS remoting functionality allow the use of DELÉGO SERVER as an IP interface for ETS PROFESSIONAL. As described in detail in the ETS remoting chapter, this functionality can be used locally and remotely, thanks to the CLOUD VPN service.

Communication interface settings9.2.3.3

The COMMUNICATION INTERFACE group, at the bottom of the KNX section, holds the settings of the interface towards the bus. SAVE applies them.

ETS import9.3

It is possible to import the ETS project in order to facilitate the creation of the KNX WIDGETS and the structure of FLOORS and ROOMS, starting from the information already present in the project.

Even if the importing of the ETS project is not strictly necessary, it is strongly recommended as a starting point for the creation of a KNX visualization.

Supported formats9.3.1

The import from ETS accepts the following formats:

The recommended format is the full project, *.KNXPROJ, which is compatible with ETS 5 and 6. The OPC and CSV formats, described in Older formats, are still supported but no longer recommended.

Project export from ETS9.3.2

Full project (KNXPROJ)9.3.2.1

Select the project in the main screen of ETS and press EXPORT, choosing *.KNXPROJ as the format. This format is produced by ETS 5 and 6 only.

Older formats9.3.2.2

The OPC and CSV formats are no longer recommended: they carry much less information than the KNXPROJ file, although they are still supported.

OPC export

The procedure is the same (select the project in the main screen of ETS and press EXPORT) choosing the OPC format instead. An OPC export produces two files, and the server needs both:

CSV group addresses list

The tree of the group addresses, whole or in part, can be exported in CSV format straight from the Group Addresses panel of ETS, by right-clicking the main group of interest. The file carries the group addresses and nothing else.

Project upload and options setting9.3.2.3

To import a new ETS project, open the KNX section of the Administration. The ETS PROJECT block at the top of the page reports the last project imported and holds Import new, which opens the import dialog:

As soon as a project file is selected, the settings of the import are displayed, according to the file format; the following screenshots refer to the KNXPROJ format:

The following settings are available for the KNXPROJ format; other formats may offer a shorter list.

GENERAL

BUILDINGS

WIDGETS

AI

CLOUD BACKUP

The cloud backup is available only when the server is logged on the EKINEX cloud. It keeps the very project that was imported last: if the original file is lost, or simply to be sure of opening in ETS the same project that is in the server, it can be downloaded to the PC from the Backup/Restore tab of the project card.

Project import and final report9.3.2.4

After specifying the import options, pressing NEXT starts the project analysis and import; during this procedure, an animation reports the current stage and the progress. Do not exit this page until the import is finished; it normally takes no more than 5 minutes for large projects.

At the end of the import procedure, a summary of the performed operations is given, like in the following example:

The elements reported as “not updated / deleted” had already been created by a previous import and were not considered in this one, because the corresponding update flags were not set.

The buildings, floors and rooms of the ETS project become the BUILDINGS, FLOORS and ROOMS of DELÉGO SERVER. Rooms, cabinets or stairs directly associated to a building part are created as ROOMS, and the building part they belong to as FLOOR.

The BUILDINGS, FLOORS and ROOMS automatically generated by the ETS import can be manually customized, in the same way as those manually created.

This topic is shown in the The KNX section video tutorial.

Encoding and function assignment9.3.2.5

The KNX group addresses the import procedure did not recognize have to be checked by hand before going on, so that the right encoding is used for the communication.

Importing a project in the KNXPROJ format normally skips this step altogether, because everything needed is already in the project file; only the addresses whose encoding is unknown are listed here.

Each of the addresses in the list offers:

From here there are two ways of proceeding.

One address at a time. Choose its exact encoding, the function it belongs to (not mandatory) and the icon that represents it best.

Several addresses at once, when one rule can cover them: press Modify rules and write a rule for the purpose. The page that opens lists the import rules already defined, each of them made of:

A rule reads like this: when DELÉGO SERVER meets a group address whose name contains at least one of the keywords, and whose data length is the one the rule states, it adopts the encoding of the rule for reading and writing on the bus, assigns the function chosen, and uses its icon for the graphical representation of the object.

Once the rules are in place, go back to the ETS import with Return to KNX import and select Use automatic import rules. Repeat as many times as it takes to work through the whole list. Leaving some addresses unmapped is allowed, but they may not behave correctly later, when the KNX widgets are configured.

Press NEXT to finish the import. The page reloads and every address of the project appears in the ETS tab of the source panel, arranged by the address levels the project uses, ready to be associated with the KNX widgets.

KNX widgets9.4

As described in the Widgets chapter KNX WIDGETS visually represent a functionality executed by one or more KNX DEVICES; these devices exchange commands and states by communicating on the KNX bus by means of telegrams addressed to one or more GROUP ADDRESSES.

Each command / state is normally associated with a different group address (or a couple of group addresses, the one being the command, and the other the corresponding status feedback). They are also called sub-items of the WIDGET.

A typical example is a dimmer (light with brightness control) which can be commanded in different ways:

• ON/OFF switching
• Brightness control
• Tunable white control (warm/cool light temperature) if supported

The KNX widgets are configured in the KNX section of the Administration, where the context tree on the left lists them grouped by CATEGORIES where the widgets can be created; each category contains the list (initially empty) of widgets belonging to the corresponding function.

Creating a new KNX widget9.4.1

When a KNXPROJ file containing Ekinex products is imported, almost all the widgets that the project needs are created automatically. A widget has to be created by hand only when a function is not covered by the import, or when a new function has to be offered to the end user.

Create widgets one at a time and check that each works before going further: once a widget of a given type behaves correctly, duplicate it rather than building the next one from scratch. The offset-based duplication described in the next chapter saves a considerable amount of time on a project of any size.

As for any other technology, a widget can be created by hand in two alternative ways:

• In the KNX section. Open the source panel on the right, on its Library tab, find the model you need under its category and drag it onto the category of the context tree where it belongs. The tree is organized by the same categories as the library: Lighting, HVAC, Shades, Scenes, Security, Multimedia, Gates, Sockets, Technologic, Irrigation and Other.
• Directly in the Project section. Open the Library tab of the source panel, find the KNX model you need and drag it onto the room of the context tree where the widget belongs.

In both cases, selecting the new widget in the tree opens its card. Fill in its settings and, above all, associate a group address with each of its functionalities, as described below.

GENERAL INFORMATION and CLOUD hold the general attributes.

REFRESH re-reads the state of the widget from the bus; CLONE duplicates it.

KNX ADDRESSES lists the commands and states that the model supports. Each row carries the following:

Associating the group addresses. A group address can be entered in the COMMAND or FEEDBACK box of a functionality in three ways:

• Dragging it from ETS. Select the ETS tab of the source panel and drag the group address you need onto the COMMAND or FEEDBACK box of the functionality. The tab lists the group addresses of the imported ETS project (see ETS import).
• Typing it. If you know the address, type it in the box. To be faster, type a space instead of each /: once the whole address has been typed, the spaces are replaced automatically, so 1 2 3 becomes 1/2/3.
• Choosing it from the context menu. As you start typing part of the address, or part of the name the address has in ETS, a context menu opens with the matching group addresses, filtered as you type. Select the one you need.

1. The group address in the ETS tab: the name it carries in the ETS project, its address and its datapoint type.
2. The COMMAND box of the functionality it is dropped on. The FEEDBACK box takes an address the same way.

Advanced fields. Switching Expert mode on, in the Configuration menu, adds several fields to the same card.

The address table gains its technical columns: ETS ENCODING, which sets the datapoint type of the address, MIN, MAX and STEP for the values the interface may send, READ, SCH/TRG and SCEN., which enable the address for reading, for schedules and triggers and for scenes, and LIBRARY, which chooses the graphic set used to represent the address.

This topic is also covered in the Widget scheduling, The KNX section and KNX widget card video tutorials.

Cloning KNX widgets9.4.2

Once a widget is fully configured, it can be duplicated several times, to make the creation of similar widgets quicker. This approach represents the fastest way to quickly implement the supervision project, thanks to the possibility - during duplication - of automatically increasing the group addresses.

To duplicate a widget, select it in the context tree, open its card and press CLONE. A dialog opens:

The fields are:

For example, entering 1 or +1 as the offset on the address group increases the last number of every KNX address of the starting widget by one, as many times as there are copies requested.

For example, by entering “1” or “+1” as an offset on the group address, each KNX address present in the starting widget will be increased by 1 on the last number, as many times as there are copies requested:

3/0/1 · 3/0/2 · 3/0/3 …

EXECUTE starts the duplication, CLOSE leaves without cloning; after a few seconds, the new widgets appear under the same category of the context tree. After the duplication of a widget, it is required to press the REFRESH button in the category list, in order to see the new widgets

At this point:

• Change the label of the new widgets.
• Assign them to the appropriate room.

Customization9.4.3

Switching Expert mode on, in the Configuration menu, makes it possible to customize specific aspects of the addresses of a widget.

For the numeric items, it is possible to force the MIN, MAX and STEP values, in order to set a specific range of values and the “granularity” of the intermediate values between the limits. The round sliders in the Visualization will adjust the displayed values accordingly.

Furthermore, for a specific subset of the items, a different graphic library can be set, from the default one. By pressing the corresponding button, a dialog window is displayed, with the possibility to filter and select the most appropriate set.

The graphic library can even be customized, as explained in detail in the Graphic library chapter.

Functions9.4.4

As explained in the Functions chapter, every element visible in DELÉGO SERVER belongs to a function, and KNX widgets are no exception.

The chapters that follow go through the templates available for each function, and through the graphical forms each of them can take.

Lighting9.5

ON/OFF light9.5.1

Simple widget for the control of ON/OFF lights and, more in general, switching relays. Items supported by the template:

The following picture shows how the widget appears in the Visualization of DELÉGO SERVER:

Dimmer9.5.2

Template dedicated to the control of lights with brightness and, where available, tunable white control. Items supported by the template:

The “color temperature” and “color temperature %” are mutually exclusive being alternative encodings for the same meaning.

The following picture shows how the widget appears in the Visualization of DELÉGO SERVER:

RGBW9.5.3

Template dedicated to the control of colored lights. Items supported by the template:

It is important to specify only one of the following color adjustment modes, which must be considered mutually exclusive:

• RGB single components
• RGB single telegram
• HSV single components
• HSV single telegram

This template makes it possible to save the current color in a PRESET, in order to retrieve it in a second moment. It is possible to save up to 4 presets. In order to save a preset:

• Set the desired color
• Long press on one of the four elements on top of the color picker The following picture shows how the widget appears in the Visualization of DELÉGO SERVER:

HVAC9.6

Thermostat with HVAC mode9.6.1

Full-featured template for thermostats configured in ETS to be used with the HVAC operating mode(s) (also called “absolute” temperature control).

GENERIC THERMOSTATS Items supported by the template for generic thermostats:

To change the values exchanged on the KNX bus, press the button in the last column of the row and pick the most suitable set of options in the popup that opens.

If a single HVAC mode is used, the “HVAC manual mode” item must be filled in with the KNX group addresses from ETS, and not the “HVAC mode”. The “HVAC mode” is intended for the dual mode configuration, specific for EKINEX thermostats / pushbuttons, as explained below.

The “ventilation speed” and “ventilation speed (%)” are mutually exclusive; assign KNX group address(es) only to one of the two items, according to the encoding (datapoint type) configured in ETS. The following picture shows how the widget appears in the Visualization of DELÉGO SERVER:

EKINEX THERMOSTATS AND PUSHBUTTONS EKINEX’s thermostats and pushbuttons with integrated thermostat have an advanced HVAC regulation, normally not available on KNX devices from other manufacturers, based on the principle of two different operating conditions, where the thermostat can be in:

• Chrono mode
• Manual mode

In chrono mode the thermostat is under the control of a BMS - like DELÉGO SERVER - where the temperature and HVAC operating mode are managed automatically and scheduled during the day. In that condition, the “ HVAC Mode ” is considered as the operating mode of the thermostat. When the user interacts with the thermostat (e.g., by changing the HVAC mode or the manual setpoint ) the thermostat goes to the manual mode.

The advantage of this dual mode approach, is an easy way - for the end user - to “override” the automatic (chrono) functionality with a temporary manual mode; during the manual mode, anyway, the thermostat keeps in memory the changes of the automatic mode; when the user restores the chrono mode, the thermostat returns to the state it would have had if it had not gone into manual mode. The following items of the thermostat widget are involved in the dual mode:

The two pictures below show the communication objects involved with the dual mode in the ETS library, and how the widget then appears in the Visualization of DELÉGO SERVER in each of the two modes:

For the dual mode to work properly, the following steps are also necessary:

• Switch Expert mode on
• Select HVAC mode (the chrono one) in the SCH/TRG column

By doing this, the schedules will be done on the chrono HVAC mode, and not on the manual one.

Thermostat with single setpoint9.6.2

Items supported by the template:

(ON/OFF)

The “ventilation speed” and “ventilation speed (%)” are mutually exclusive; assign KNX group address(es) only to one of the two items, according to the encoding (datapoint type) configured in ETS.

The following picture shows how the widget appears in the Visualization of DELÉGO SERVER:

Thermostat with seasonal setpoint9.6.3

This template is similar to the thermostat with a single setpoint, but offers two different temperature setpoints, one for the heating, and the other for the cooling.

Items supported by the template:

This template is particularly suited for the Ekinex EK-ER2-TP easy thermostat; the following picture shows the communication objects that normally have to be configured, to obtain a suitable visualization in DELÉGO SERVER, and how the widget then appears in the Visualization:

The Ekinex easy thermostat EK-ER2-TP does not support the eco and comfort modes, even if they are present in the DELÉGO SERVER template (being it more generic). Furthermore, in order to manage the ON/OFF of the thermostat from the Visualization, it is necessary to invert the group object called “thermostat OFF” with a logic function, because the thermostat accepts the value 1 to switch OFF, instead of 0.

Air conditioning unit9.6.4

Template dedicated to AC (Air Conditioning) interfaces for VRV / Split systems and native KNX devices.

Items supported by the template:

To change the values exchanged on the KNX bus, press the button in the last column of the row and pick the most suitable set of options in the popup that opens.

The following picture shows how the widget appears in the Visualization of DELÉGO SERVER:

Humidity control9.6.5

Template dedicated to humidity sensors and controllers. Items supported by the template:

The following picture shows how the widget appears in the Visualization of DELÉGO SERVER:

CO₂ and VOC Control9.6.6

Templates dedicated to air quality sensors with CO₂ / VOC measurement and control. Supported items by the CO₂ control template:

Supported items by the VOC control template:

The following picture displays how the widget is displayed in the Visualization of DELÉGO SERVER for both CO₂ and VOC controls:

Motorizations9.7

Shutter up/down/stop9.7.1

Simple motor control for up/down and stop control of shutters and similar motorizations. Items supported by the template:

The following picture shows how the widget appears in the Visualization of DELÉGO SERVER:

Shutter up/down/percentage9.7.2

Motor control for up/down and stop control of shutters and similar motorizations with percent (absolute) position control. Items supported by the template:

Visualization preview:

Venetian blinds up/down/step9.7.3

Simple venetian blinds control with up/down/stop movement control and slats open/close (step up/down). Items supported by the template:

The following picture shows how the widget appears in the Visualization of DELÉGO SERVER:

Venetian up/down/percentage9.7.4

Venetian blind control with percent position and slats step up/down command. Items supported by the template:

The following picture shows how the widget appears in the Visualization of DELÉGO SERVER:

Venetian with slat orientation9.7.5

Full-feature venetian blinds control with up/down/percent positioning management and slats orientation percent control. Items supported by the template:

The following picture shows how the widget appears in the Visualization of DELÉGO SERVER:

Multimedia9.8

Multiroom - Zone9.8.1

Audio zone management for KNX-based multiroom systems. Items supported by the template:

The following picture shows how the widget appears in the Visualization of DELÉGO SERVER:

Other functions9.9

Alarm9.9.1

A simple widget tied to a single KNX address, to represent an alarm or an anomaly. The template supports one item:

Energy9.9.2

This category holds the widget templates dedicated to energy monitoring, which are described in the Energy chapter together with the rest of the energy management.

Single value9.9.3

This template is intended for the generic visualization of single KNX group addresses (with the corresponding status feedback address, where present) not already covered by existing templates in the categories seen before.

When creating a single value widget, the following additional option can be set:

Items supported by the template:

If the default ON/OFF switching (1 bit) encoding is not suitable for the specific need, activate Expert mode from the Configuration menu and select the most appropriate encoding with the drop-down menu in the ETS ENCODING column.

The single value widgets, in the OTHER category, can be assigned to one of the following functions:

GATES Intended for doors, gates and similar

If a different category is assigned (e.g. lighting, shading, climate etc…) after a page reload, the widgets will no longer be visible in the OTHER category, but in the assigned category.

The single value widget template is useful also when a KNX group address must be used in an automation (trigger, logic, connection etc…) without the need to be put in the Visualization.

In that case, no matter the style, the creation of the widget is still necessary, because otherwise, the group address (even if it was imported from ETS) cannot be used in the project.

The following picture shows how the widget appears in the Visualization of DELÉGO SERVER:

KNX Scenario9.9.4

This template is intended for the execution of a KNX scenario configured in ETS. This functionality is normally associated with a group address belonging to DPT 17.001 or 18.001, but an encoding of 1 byte unsigned integer (DPT 5.001) is also supported.

Items supported by the template:

When creating a KNX scenario widget, the following additional option must be set:

In case the same group address is associated with multiple scenes with different values, it is recommended to create several widgets (with the KNX scenario template) by entering the same group address, and the different values in the SCENARIO VALUE field.

In the Visualization, a KNX scenario is displayed as a simple element; pressing the play symbol executes the scenario, and the row turns green briefly.

Generic9.9.5

General purpose flexible template useful to create popup-based widgets hosting multiple KNX group addresses (up to 64).

When editing a generic template, the APPEARANCE group sets the style of the main page of the popup:

In the list of KNX addresses, in order to add new items, press ADD and select the position where the new item must be placed:

Each item in this list can be accompanied by a Label that will be presented in the popup (secondary screens). As an example, six consecutive addresses are enough: the main state, the upper buttonset and the lower slider make up the main page, while three more objects placed on the first tab carry the labels that will name them in the popup. This is the result in the Visualization of DELÉGO SERVER:

KNX Devices Watchdog9.10

KNX Devices Watchdog is new in this version. It sits at the bottom of the context tree of the KNX section and lists the physical devices of the installation, identified by their individual address, as read from the imported ETS project.

It serves two purposes: watching whether each device answers on the bus, and updating the firmware of Ekinex devices without removing them from the wall.

This topic is shown in the The KNX section video tutorial.

Device monitoring9.10.1

Selecting KNX Devices Watchdog shows the list of the devices found in the ETS project, with their individual address and their state.

A device that does not answer is reported as unreachable, which usually means it is unpowered, disconnected from the bus, or programmed with a different individual address than the one the ETS project declares. Where no bus is connected, every device is reported as not available.

Selecting a single device opens its card, which reports the Manufacturer, the Physical address and Scan periodically, the switch that includes the device in the periodic check.

Firmware update9.10.2

The firmware of an Ekinex KNX device can be updated directly from DELÉGO SERVER, over the bus, without removing the device from the wall. The update is available only for Ekinex devices: the firmware section appears in the card of a device only when the imported ETS project describes it as made by Ekinex, with its order number.

Before starting, the following are needed:

• A KNX communication driver with ETS remoting, With ETS remoting or With ETS remoting and KNX secure support (see Communication driver): the Standard driver does not support the firmware update. With the Standard driver, selecting an Ekinex device in KNX Devices Watchdog shows a Notice asking to change the driver in the KNX settings, and the update controls are not shown. Once the update has finished, the previous driver can be selected again.
• The firmware file of the device model. On www.ekinex.com, open the detail page of the product, scroll to the Technical documentation section and download the Firmware item. It is a ZIP archive: unpack it on the computer. It contains the setup of a Windows program that updates the device directly from a PC, which is not part of this procedure, and the firmware file itself, with the extension .ekboot, which is the one to use with DELÉGO SERVER.
• The ETS project of the installation, needed to program the device again after the update.

To update the device:

1. In the KNX section, select the device in KNX Devices Watchdog, at the bottom of the context tree. The FIRMWARE INFORMATION group appears at the bottom of its card, below the description of the procedure.

2. In Update file (.ekboot), choose the .ekboot file. The server checks that the file is meant for the model of the device selected in the tree, and shows that model in Device model. If the two do not match, an error message appears and the update cannot go on, so that a wrong firmware never reaches the device.

3. Press UPDATE. The update starts, the file fields are hidden and the ADVANCE PROGRESS group shows how it is going:

The update typically takes 10 to 15 minutes. When it has finished, download the application configuration to the device again with ETS: the device keeps its individual address, but not its configuration. The UPDATE STATISTICS group keeps the Last version installed and the Last update timestamp.

While the update is running, you can move to other sections of DELÉGO SERVER and go on with the configuration: going back to the card of the device shows the progress reached in the meantime. Only one update can run at a time, though: the card of any other KNX device shows a Notice in place of the firmware section until the current update has finished.

If the status ends in Failed, check the bus connection of the device and start the update again with the same file.

KNX Telegram recorder9.11

Starting from software version 2.7.0, DELÉGO SERVER offers the possibility to trace and store the KNX telegrams history, to be consulted interactively or exported to ETS PROFESSIONAL.

Due to the intense load that this functionality places on the storage, especially on high KNX traffic installations, it is recommended to switch Enable telegram recording on only when needed, and to deactivate it when the diagnostic purposes are over.

To take the most benefit from this functionality, it is suggested to install an SD card, and to activate the long-term storage of the KNX telegrams. In this way, it will be possible to retrieve the entire log for a specific day and consult it in ETS.

Activation9.11.1

To activate the KNX TELEGRAM RECORDER, open the KNX section in the bar, where the KNX TELEGRAM RECORDER block sits on the same page as the ETS import and the physical address,

and select Enable telegram recording, then press SAVE and confirm the warning message. Wait until the browser reloads, and open again this section to start using it.

Interactive use9.11.2

The recorder is opened from the KNX TELEGRAM RECORDER block of the KNX section, above the physical address: once Enable telegram recording is on, OPEN TELEGRAM RECORDER opens a window that lists the most recent telegrams detected on the bus, in descending order. In case of a high number of telegrams, it is possible to move among the pages with the dedicated buttons (SHOW PAGE X OF Y).

The log contains the following information:

The list does not update on its own: press REFRESH to show the telegrams received by the webserver in the meantime. The other buttons at the bottom of the window export the log (EXPORT CSV, EXPORT XML), open the external memory page (LOG ON SD) and close the recorder (CLOSE).

It is possible to export the log in two different formats:

• CSV: useful for opening in a spreadsheet, for example Microsoft Excel
• XML: ready to be imported in the diagnostic tools of ETS PROFESSIONAL (bus or group monitor)

The following screenshot shows the log exported in XML from DELÉGO SERVER, and imported in ETS:

Log on SD card9.11.3

If an external SD memory is installed, it can be used to store periodically the KNX log for longer amounts of time, and to retrieve it after days.

As a preliminary action, the SD memory must be activated, in the

Settings → External SD

page, as described in the External memory management chapter. This configuration page can be accessed directly from the KNX TELEGRAM RECORDER, by pressing the LOG ON SD button.

In the KNX BUS MONITOR section, select first the “enable KNX historical saving on SD” checkbox, and then select which format must be used to store the KNX telegrams, among the following options:

• CSV: suitable for further processing in a spreadsheet (e.g. Microsoft Excel)
• XML: compatible with the diagnostic tools of ETS PROFESSIONAL
• TRX: older format to be imported in ETS versions 3 and 4

After doing this, DELÉGO SERVER starts saving, every hour, the KNX telegrams (and correspondingly clearing them from the temporary memory, the one that can be consulted in the interactive view) and creating a daily archive, available for a future download. In the calendar above the settings, the highlighted days have a daily record; by pressing on a day, the corresponding log is automatically downloaded.

The KNX log is saved on the SD card in the selected format. If the format is changed, all the previously saved archives in a different format are no longer available in the calendar (unless the original format is selected back) and only the new archives, created from that moment on, will be highlighted.

From this page it is possible to return to the interactive KNX real-time monitor by pressing the OPEN button under the calendar.

KNX Secure9.12

DELÉGO SERVER supports both KNX DATA SECURE and KNX IP SECURE:

• KNX Data Secure protects the communication on the twisted pair, through the KNX interface integrated in the server: DELÉGO SERVER reads and sends encrypted telegrams directly on the bus.
• KNX IP Secure protects the communication with an external IP interface that supports the secure protocol, when the server reaches the bus through the network; it is described in KNX IP Secure.

Delégo library configuration in ETS9.12.1

In order to be able to send commands to secure devices, the ETS library of DELÉGO SERVER must be added to the project and bound with all the KNX group addresses containing secure devices:

Keyring import9.12.2

After doing the association of DELÉGO SERVER with all the secure group addresses, it is necessary to export the KEYRING from ETS; it is an archive containing all the certificates of the secure devices in the project. This file must be kept in a secure place and never shared with anyone.

Enter the project settings and press the “arrow” in the SECURITY section

then press the BACKUP KEYRING button in the list of certificates…

and enter a password to protect the keyring:

Leave the Include device certificates checkbox cleared.

At that point, in DELÉGO SERVER, browse for the key archive file, and enter the protection password, before proceeding with the import of the project.

KNX IP Secure9.12.3

In the Communication interface settings of the KNX section, activating the driver with KNX secure support (With ETS remoting and KNX secure support) allows the server to talk to an external IP interface in an encrypted way, with the KNX IP SECURE protocol.

The KNX IP Secure group then asks for the following:

The last two are not needed when the IP interface is not in secure mode.

ETS remoting9.13

DELÉGO SERVER can be used as an IP interface for the commissioning of KNX devices and the diagnostics with ETS PROFESSIONAL.

It requires a communication driver with ETS remoting support (With ETS remoting or With ETS remoting and KNX secure support) selected in the Driver field of the COMMUNICATION INTERFACE group of the KNX section, as explained in the chapter on the communication driver.

Use in local network9.13.1

When the PC with ETS PROFESSIONAL is in the same local network as DELÉGO SERVER, proceed as follows:

• Open the MANAGE CONFIGURED CONNECTIONS window.
• Press the ADD button.
• Enter the following information: ○ Server → IP address of DELÉGO SERVER. ○ Port → leave default value (3671). ○ Connect using NAT mode: select it if the communication does not start.
• Check the communication with the TEST button.
• If the TEST is OK, save with the OK button, and ensure the new connection is selected as the active one for the following download / diagnostic operations.

Remote connection9.13.2

Using DELÉGO SERVER as an IP interface for ETS Professional from outside the installation requires a VPN between the two. The chapter that follows describes how to establish it with the cloud VPN, configured as described in the Cloud VPN chapter.

Cloud VPN9.13.2.1

When using the CLOUD VPN for the ETS remoting, it is necessary to enter the webserver VPN IP address (typically 10.56.210.2 ) in the ETS connection (after having started the VPN connection), like in the following example:

MODBUS10

Introduction10.1

This chapter contains all the information for configuring and visualizing one or more MODBUS devices inside DELÉGO SERVER, the multiprotocol webserver for the connected buildings by EKINEX.

MODBUS Master10.2

DELÉGO SERVER speaks MODBUS RTU and MODBUS TCP/IP, and can therefore control the parts of an installation built on that technology. It handles several MODBUS slave devices at the same time, on RTU over RS485 cabling and over the LAN, in any combination.

The installation and the configuration differ according to the transport.

MODBUS RTU. The integrated RS485 port of DELÉGO SERVER can be used directly: connect the terminals of the slave devices to it with two wires, respecting the polarity. The alternatives are an RS232 port, available only on the 4 DIN rail modules hardware version, and a USB to RS485 converter, which is what allows more than one RS485 line to be managed.

MODBUS TCP. The devices reach DELÉGO SERVER over the data network of the installation. Each peripheral with a MODBUS TCP interface has its own IP address and communication port, both set on the device, exactly as the server does. The physical connection is an ordinary LAN one: network cables or wi-fi, switches and routers.

MODBUS lines10.2.1

DELÉGO SERVER supports more than one MODBUS interface, by creating as many MODBUS lines on different communication channels. The lines work at the same time, provided each is configured on one of the interfaces the server offers:

• the integrated RS485 port;
• a USB converter;
• the LAN.

Each line holds a number of objects, the MODBUS registers, belonging to the devices connected to it; those objects are then placed in the graphical pages of the supervision. Several slave devices cascaded on the same RS485 line are handled by a single line in DELÉGO SERVER, telling them apart by their slave address, as described further on.

Within a line it is also possible to create graphical components directly, each made of a list of registers. On a line with many slave devices this keeps the configuration shorter and far easier to read.

New MODBUS line10.2.1.1

To create a new MODBUS line, proceed as follows:

• Access the Administration of DELÉGO SERVER
• Open the Modbus section in the bar
• Select Modbus master in the context tree
• Use the Add action of that node, which appears on the node itself when the pointer is over it

A new bus line is created and added under Modbus master. Select it in the tree to open its card:

The GENERAL INFORMATION group holds the identification of the line and the communication parameters.

The debug log is useful while commissioning MODBUS devices with DELÉGO SERVER, but once the installation is working it is advisable to enable it only when actually needed, for example during maintenance or a software change.

With Serial / USB, the parameters of the serial channel appear:

With Network, the address of the device is asked instead:

The status bar at the top of the card reports the Execution state of the line as a coloured dot, green while the line is communicating and red when it is stopped, and holds RESTART. Changing any of the communication parameters above stops the line and turns the dot red, so that it never keeps running with the previous values: press RESTART to start it again with the new ones. The colours are described in Workspace.

PERMISSIONS holds Enable, which activates the line, and Execute at startup, which starts it when the system is powered up.

With Expert mode active, the following advanced settings become available:

Expert mode also shows General communication status and Communication status with slaves, which report the health of the line, and Additional options.

Advanced options10.2.1.2

By activating Expert mode, the switch in the Configuration menu, the following advanced settings are available:

It is possible to optimize the reading of contiguous registers by automatically reading them in groups instead of one at a time; this operation is performed automatically by the Modbus master process, regardless of the register configuration, according to the following parameters:

Registers10.2.2

Once the communication is configured, the registers of the slave devices on the MODBUS line are created with the widgets, as described in Creating a new widget. The table of the read and write registers of each device is in the technical manual of the product, and that manual is where the information below has to be found before starting.

The functions are the following.

Reading:

Writing:

Knowing which function reads and writes each register of each device is essential to reach the right data, and that too is in the manual of the device.

With the information gathered and the communication tested, the registers can be created in the webserver.

Multiple reads and writes10.2.2.1

It is possible to read and/or write simultaneously on more than one register; this option is necessary (by setting the value “2”) for the 4-byte encodings, and “4” for the 8-byte ones, but more generally it can be used (if the slave device supports it) to operate on contiguous registers with a single read/write operation, thus speeding up communication.

To activate multiple reading/writing, enter a value other than “1” in the R/W field; one “sub-object” is automatically created for each read/write beyond the first: with R/W set to n, the main register is followed by n − 1 sub-objects, automatically configured with the registers adjacent to the first:

The sub-objects are constrained to share some attributes with the first, such as read/write flags and encoding. Conversely, it is possible to independently set any multiplication factor, the COV and the set of icons, given that they represent independent values in the graphic supervision (which could also represent different types of quantities).

Widgets10.2.3

Widgets can be built on MODBUS exactly as they are on KNX, with the same templates available. Compared with creating the single registers one by one, a widget brings four advantages:

• the list of registers arrives already filled in from the model chosen, and only the communication mapping has to be set;
• the widget can be placed directly in a room;
• once configured, it can be duplicated, which makes repetitive configurations far quicker;
• the registers stay readable, because they are grouped by slave device instead of forming one long list.

Nothing changes on the protocol side. A widget is a graphical structure only: how the server talks to the devices, and what has to be configured for each register, is exactly what the previous chapters describe.

Creating a new widget10.2.3.1

The templates available for a MODBUS line are in the Library panel on the right of the Modbus section:

To insert a new graphic component into the line, drag its template from the Library onto the line, entering the number of components to create if it is different from one.

Once the graphic component has been created, open its card with the edit button; in the initial section of the page it is possible to specify the following (in addition to the parameters / flags common to all DELÉGO object types):

In the MODBUS REGISTERS section there are all the registers created automatically, based on the template chosen initially. Registers cannot be created directly on a MODBUS line: they always belong to a widget and come from its template.

If there are unnecessary registers in the list (because the template provides them, but they will not actually be used in the specific case) simply delete them with the appropriate trash can button.

A graphics component does not necessarily have to coincide with a MODBUS slave device; for this reason, it is possible not to specify the slave address above, and fill in the SLAVE field for each of the addresses. Typically, however, graphic components are used precisely to automate the graphic creation of an element that represents a physical device.

For each register you can set the following properties:

The encodings available in the ENCODE field are the following:

In the inverted encodings the order of the registers is reversed with respect to the corresponding straight one.

After each change to the list of registers, press REFRESH on the widget card to confirm the changes, make the registers active and restart communication on the MODBUS line.

Duplication10.2.3.2

Once a graphics component is successfully configured, you can duplicate it to speed up the configuration of repetitive elements. To do this, press the CLONE button in its detail sheet or, alternatively, the duplicate button directly from the list of graphic components in the line; in both cases, the following window is shown:

The WIDGET field is preselected with the starting element and cannot be modified; on the other hand, it is possible to establish how many copies must be made, and whether the corresponding registers must be created identical to the original, or instead by applying an offset.

The offset can be either on the slave address or on the register; indicate an incremental number (using for example “+1” to increase, “-1” to decrease) which will be applied, for each of the graphic components, compared to the original.

When finished, the new graphic components appear in the line list; by entering their tab, it is possible to verify that the creation of the registers has correctly implemented the offset, and possibly modify the configuration according to your needs.

CoolMasterNET10.3

This chapter contains all the information required for the integration of DELÉGO SERVER, the multiprotocol webserver for connected buildings by EKINEX, with a CoolMasterNET device.

CoolMasterNET connection and configuration10.3.1

Connection of CoolMasterNET and the external unit(s)10.3.1.1

Refer to the following CoolMaster document for detailed instructions for the connection of the CoolMasterNET to the external unit(s):

https://coolautomation.com/wp-content/uploads/sites/2/2021/01/CoolMasterNET-installation-manual-3.5_.pdf

DIP switches must be set appropriately for the HVAC units in use, then the outdoor unit comms line must be connected to the CoolMaster (only certain comms lines can be used for certain brands). The image below is for a Samsung outdoor unit.

This connection allows up to 64 indoor units to be controlled from a single connection to the outdoor unit. Refer to the manual of the HVAC unit for recommendations on cable used for this connection. For example a Samsung VRF unit recommends a conductor cross-section of 0.75 mm² to 1.5 mm². If there is a second outdoor unit, then simply connect it to another data line of the CoolMasterNET.

Indoor units detection and addressing10.3.1.2

A CoolMasterNET controls several indoor units, so before any of them can be reached over Modbus each one needs a virtual address. That address is then the base address of the Modbus registers of that unit.

The CoolMaster can scan a line on its own and detect every indoor unit connected to it, which is the quickest way to obtain the list to work from.

HVAC brand setting

1. Open Settings

2. Enter HVAC line

3. Select the HVAC Line you want to configure

4. Configure the HVAC line type

5. Make sure the DIP switches are set properly for the brand (see the CoolMasterNET installation manual linked in the previous section)
6. A red warning message appears if the DIP switches are set incorrectly
7. Reset is required to make the change

Scanning for indoor units

1. Open settings

2. Enter HVAC Line

3. Select the HVAC Line you want to configure

4. Press SCAN

Modbus IP enabling

1. Open settings

2. Open BMS Settings

Creating VA list

1. Run VA Auto

2. View VA List

For full instructions please refer to the CoolMasterNET documentation at the following link:

https://coolautomation.com/wp-content/uploads/sites/2/2021/03/CoolMasterNet_UM_v1.1.2-1.pdf

Delégo configuration10.3.2

Widget configuration10.3.2.1

Open the Library panel on the right, where the Modbus templates are grouped into HVAC, Energy and Other, and drag CoolMaster, in the HVAC group, onto the Modbus line in the context tree; a new widget is created under the line, for the first AC unit. Select it to open its card, enter a name and 1 in the Address field (the Modbus slave number), leaving all the other settings as default:

The CoolMasterNET gives access to each AC unit with register addresses shifted by 16 from one another:

For this reason, in order to add the next AC units, the quicker approach is to clone the first widget, by specifying “16” as address offset:

• Press the CLONE button from the details page of the first AC unit
• Enter the number of AC units to be created
• Enter “+16” as an offset for the register (no offset for the slave)
• Press EXECUTE

When done, return to the Modbus line page, and change the names of the AC units in the WIDGETS list. Finally, press REFRESH to restart the communication; if everything has been correctly set, the “dots” in the detail page of each AC unit must turn from red to green.

Visualization10.3.3

Assigning each AC unit a Room in the Widgets list of the Modbus line page makes it appear automatically in the page of that room in the Visualization.

The following pictures show an example of visualization of an AC unit in the widgets list of a room, and the corresponding detail popup (accessible by pressing the widget in the list):

MATTER11

Introduction11.1

MATTER is the standard for smart home IoT, used by many connected accessories and compatible with several ecosystems like Apple Home, Amazon Alexa, Google Home and Samsung SmartThings.

DELÉGO SERVER implements the MATTER protocol in two different ways:

• CONTROLLER: the webserver can control MATTER accessories and make them interact with KNX and the other supported cabled technologies
• MATTER BRIDGE: a subset of the configured widgets can be exposed to a MATTER ecosystem, in order to be managed by the corresponding apps and voice assistants

Matter Controller11.2

Preliminary operations11.2.1

Enrollment11.2.1.1

Before becoming available for the management in DELÉGO SERVER, a MATTER native device must be enrolled to one of the following smart home ecosystems (typically the preferred one by the end user):

• Google Home
• Apple Home
• Amazon Alexa
• Samsung SmartThings

This operation normally associates the device to the home Wi-Fi network, and adds it to the devices that can be managed by the corresponding app; the following examples refer to the Apple Home ecosystem.

It is also possible to manage devices, or groups of devices, not natively based on MATTER, but compatible with the standard by means of a gateway device, which is normally referred to as the “border router”. The PHILIPS HUE smart lighting system, based on the ZigBee radio protocol, is an example.

In this case, the enrollment stage is not necessary, and the PAIRING can be directly done, by following the specific instructions of the manufacturer of the compatible system.

DELÉGO SERVER also supports use of MATTER THREAD devices, which use a low-power mesh network for communicating and preserving energy on battery powered Matter devices. Thread is an alternative technology to Wi-Fi and a MATTER THREAD “border router” is required for communications with DELÉGO SERVER to work. Adding a new accessory typically requires scanning the QR code printed on the device:

After a while (the operation can take some minutes) the app recognizes the type of device, and asks in which room to add it. This depends on the specific app you are using; the following screenshots refer to the enrollment of a smart plug into the Apple Home application:

Finally, the new device can be controlled from the room it belongs to, like in the following example:

Pairing11.2.1.2

In order to be controlled by DELÉGO SERVER, the device must be put in PAIRING MODE. This can be done directly by the preferred smart home app, normally by opening the device settings; the following screenshots show how to do it in Apple Home:

The given pairing code can be copied and pasted (or manually entered) into DELÉGO SERVER, as described in the next chapter.

The pairing code stays valid only for a few minutes after activation: complete the procedure in the webserver before it expires.

Matter Thread11.2.1.3

In case of MATTER THREAD devices, the procedure may change depending on the manufacturer of the devices and the border router.

Usually, a pairing between the border router and your network is required. This can be done using the border router manufacturer app.

When the border router is configured, you can pair the MATTER THREAD devices you own with it using the dedicated function, so they’ll use the router as a communication gateway to the LAN.

Then, enable the Pairing mode on any device you want to control with DELÉGO SERVER to obtain the Pairing code you’ll need to use in the next steps.

All these steps have to be performed directly from the border router app or web interface made by its manufacturer.

The exact procedure can change from one manufacturer to another. Please refer to the user manuals of the MATTER THREAD border router and devices.

Configuration11.2.2

In order to manage one or more MATTER devices in DELÉGO SERVER, open the Matter section in the bar and select the Matter Controller tab. The page appears like this:

The PERMISSIONS group holds Enable, which activates the controller, and Execute at startup, which starts it automatically when the DELÉGO SERVER is powered on. The status bar at the top of the tab reports the Execution state of the controller as a coloured dot, and a change to its settings stops it and turns the dot red, until RESTART starts it again with the new settings (see Workspace). Under COMMUNICATION, PAIRING starts the association of a new device.

Each physical MATTER device, after the configuration described below, will be listed in the DEVICES table of this page, with its name, vendor and product name. This is valid not only for MATTER native products, but also for compatible systems; in this second case, the gateway (border router) will be listed here.

A MATTER device (also called NODE in the standard terminology) can offer more than one functionality, referred to as ENDPOINTS. An example can be a sensor, offering both the light brightness and the presence of persons in a room: those two functionalities can be used independently, despite the fact they’re offered by the same hardware.

This is especially true for compatible systems: in this situation, as mentioned above, the DEVICE is the gateway, and each appliance of the system is an ENDPOINT. This is because, from the MATTER perspective, all those appliances behave as if they were a single device (the border router itself).

Each detected ENDPOINT becomes in DELÉGO SERVER a widget, which can be assigned to a FUNCTION and placed into a ROOM, in exactly the same way as the other types of widget (KNX, Modbus etc…) as described in the Widgets association chapter.

Matter Thread support11.2.2.1

Depending on the version of DELÉGO SERVER and on when it was manufactured, the page may report that the Thread components are not installed.

When a MATTER THREAD device is going to be used, press INSTALL THREAD: the server downloads and installs what it needs by itself. The installation ends with a reboot of the server, so plan it outside the hours when the installation is in use.

Pairing11.2.2.2

After having set the MATTER device in pairing mode, as described in Pairing, press PAIRING in the controller page, and enter the pairing code:

After a while, the new appliance is listed in the DEVICES section, like in the following example:

If the communication is established correctly, the indicator becomes green after some seconds. The device is now ready to be used; repeat the pairing for the other devices.

Widgets11.2.2.3

By entering the device page (by pressing the corresponding EDIT button) a number of details (manufacturer, version and so on) are listed at the beginning of the page; the associated WIDGETs are displayed in the bottom section, like in the following example (of a smart plug):

In order for the WIDGET to be displayed in the Visualization, as any other graphical element in DELÉGO SERVER, it must be assigned to a FUNCTION and an existing ROOM:

In the administration area, by entering once again in details into the widget, a page similar to the following example is displayed:

The ATTRIBUTES are information made available by the MATTER device, some of which can also be written. Conversely, the COMMANDS are actions that can be performed; in the example of a smart plug, to switch it ON or OFF, or to TOGGLE its state.

The following example represents a thermostat, which normally gives a higher number of attributes:

The following screenshot shows how a MATTER thermostat appears in the DELÉGO SERVER visualization:

Matter Controller key archive11.2.2.4

Each time a device is paired with DELÉGO SERVER, a key is added inside the server. That key is what makes the communication work, and it exists only on the unit until a copy is taken.

The archive of those keys is exported and imported from the project card, in Backup/Restore, under MATTER CONTROLLER: the copy can be saved to the PC or to the cloud, and reloaded from either.

Keeping a copy of the archive is strongly recommended, because it is what allows a paired installation to be brought back on a replacement unit. Please note that this is a different set of keys than the one used by the MATTER BRIDGE.

Supported product families11.2.2.5

At present DELÉGO SERVER supports the following device families:

• Lights
• Motorizations
• Smart plugs / switches
• Thermostats
• Brightness and motion sensors
• Window/door sensors
• Smart locks

If a device is not recognized by DELÉGO SERVER, an error is given at the end of the pairing procedure. Ekinex continuously works to expand the compatibility to new families and functionalities; feel free to contact us to get specific support, and ask to add new products to our development roadmap.

Furthermore, DELÉGO SERVER may not implement all the features that the device offers in other smart home ecosystems; this is due to compatibility constraints, which can evolve over time and change among software versions of the webserver.

Automations11.2.3

Once a MATTER device has been created in DELÉGO SERVER, it can be combined with other widgets / functions, in order to exchange information and/or trigger cross-technology actions.

As an example, a KNX light in a hallway can be switched ON when a MATTER presence sensor detects a person. Conversely, a KNX wall-mounted pushbutton can command a traditional light powered by means of a MATTER smart plug.

Connections11.2.3.1

The simplest way to combine a MATTER device with the other supported technologies in DELÉGO SERVER is to create a new CONNECTION (Automations → Connections, then +) and drop into it the MATTER widget that represents the functionality.

Do the same with the other technological function (a light, a pushbutton etc…) and connect the input / output nodes, in order to build the desired automation:

Alternative ways to do bidirectional automations are the ACTIONS / TRIGGERS and the LOGIC MODULE of DELÉGO SERVER. For more information please refer to the Connections chapter.

Matter Bridge11.3

A subset of the widgets configured in DELÉGO SERVER can be exposed to a MATTER ecosystem, in order to make them manageable by the corresponding app and/or voice assistants.

One or more of the following systems can be connected in this way:

• Apple Home
• Amazon Alexa
• Google Home
• Samsung SmartThings

Bridge start11.3.1

Open the Matter section in the bar and select the Matter Bridge tab, to open the following page:

Turn on Execute at startup and start the bridge with RESTART in the status bar; after a few seconds the Status dot turns green. A red dot means the bridge is stopped, which is normal while it has never run. A change to the settings of the bridge stops it and turns the dot red: press RESTART again to start it with the new settings (see Workspace). SYNC pushes the associated widgets to the ecosystems, and PAIRING opens the pairing procedure described further on.

Widgets association11.3.2

Search for the desired widgets (in the search field on the left) and drag and drop them into the CONNECTED WIDGETS list. The following KNX and MODBUS WIDGETS are compatible with the MATTER BRIDGE:

Other templates and technologies will be added in future versions.

The associated widgets stay yellow and inactive in the bridge until it takes them on board, with SYNC or at the next REFRESH. After that the compatible ones turn green and the MODEL column names the MATTER device type each widget has been mapped to, which is the quickest check that the association went through. The widgets that are not supported stay red and are simply ignored by the bridge.

The whole list is exported as a single accessory, so the widgets have to be named in a way that stays readable inside the ecosystem app.

Pairing11.3.3

In order to manage the associated widgets in a MATTER compatible ecosystem, press PAIRING on the bridge page; a panel opens over the page with a QR code. The bridge must be running and connected, otherwise the page answers with an error message: press REFRESH first, wait for Status to read OK and retry.

Scan the QR code in the external app to start the pairing (or manually enter the pairing code, if for some reason the QR code cannot be scanned); the following examples refer to the APPLE HOME app, and may vary in the other ecosystems.

The pairing must be completed in 15 minutes, and can be stopped before that timeout with the corresponding button. If a pairing procedure is in progress on one PC, it cannot be started on a second computer, unless the first finishes.

The following picture shows an example of the pairing procedure:

The pairing process typically asks to add the bridge to the MATTER ecosystem and then requests a confirmation (or customization) of the name of each widget, and the room it has to be added to:

Because the MATTER certification of DELÉGO SERVER is still in progress, a warning could appear during the procedure; select ADD ANYWAY (or similar) to proceed. This does not compromise the functionality or security of the system. It is possible to associate further widgets to the bridge after the pairing; in such a case, after a while, the new widgets become automatically available on the MATTER ecosystem. If they do not appear, try a pairing again.

Matter Bridge key archive11.3.3.1

As with the Matter controller, the keys of the bridge are exported and imported from the project card, in Backup/Restore, under MATTER BRIDGE.

Supported widgets11.3.4

Premise11.3.4.1

Not all the WIDGET templates are compatible with the MATTER BRIDGE, due to limitations of the standard; some features offered by DELÉGO SERVER are in fact still not available in MATTER, and will be added in the future. Generic widgets cannot be exposed to MATTER either, because they do not fall into a specific category.

Furthermore, within a supported WIDGET not all the items (addresses) are exported through the MATTER BRIDGE, because the management in MATTER of some features is highly simplified as compared to DELÉGO SERVER. A thermostat, for example, can have in MATTER only one temperature setpoint, and does not support the HVAC operating mode (comfort, standby, economy etc…).

This limitation is similar to what happens with AMAZON ALEXA and GOOGLE HOME voice assistants; generally speaking the supported items in the MATTER BRIDGE are the same as those available for voice control, and are identified by the active “VOICE” symbol in the list, as in the following example:

The following paragraphs give the complete list of supported widgets, with the details of the items involved in the MATTER BRIDGE. Some of those items are necessary, others are optional: if they are missing, the corresponding functionality is not available in MATTER. An example is the color temperature in a dimmer: if not associated with a KNX address, it is simply not exposed to MATTER, and only the brightness level (and the ON/OFF) is possible.

Lighting11.3.4.2

ON/OFF LIGHT Supported items in MATTER:

Example of visualization in APPLE HOME app:

DIMMER Supported items in MATTER:

In case of absolute value for the color temperature, it is possible to specify the temperature range (in °K) by enabling Expert mode and entering the minimum and maximum values in the MIN / MAX columns respectively, as in the following example:

Example of visualization in APPLE HOME app:

RGBW Supported items in MATTER:

For compatibility reasons, do not configure the item called Intensity dimmer, because the brightness is already associated with HSV - Value.

Example of visualization in APPLE HOME app:

Motorizations11.3.4.3

SHUTTER (WITH PERCENT POSITION)

Supported items in MATTER:

Example of visualization in APPLE HOME app:

VENETIAN BLIND

Supported items in MATTER:

Example of visualization in APPLE HOME app:

HVAC11.3.4.4

THERMOSTAT Supported items in MATTER:

VENTILATION SPEED (%) Typically represented as a slider. In case of discrete speeds, the slider positioning will be rounded to the nearest option.

NOTE: only one of the two items is expected (if both are present, the percent value is used).

Example of visualization in APPLE HOME app:

AIR CONDITIONING UNIT

Supported items in MATTER:

VENTILATION SPEED (%) Typically represented as a slider. In case of discrete speeds, the slider positioning will be rounded to the nearest option.

NOTE: only one of the two items is expected (if both are present, the percent value is used).

SWING ✔ Automatic oscillation of the slats

Example of visualization in APPLE HOME app:

In some ecosystem apps, such as APPLE HOME, the fan speed control of the THERMOSTAT and of the AC UNIT is published as a separate accessory

MQTT12

Introduction12.1

DELÉGO can connect as a client to one or more MQTT brokers for publishing and receiving data in real time. This functionality is useful for interacting with devices or systems operating on cloud services other than the native EKINEX ones.

DELÉGO can also in turn function as an MQTT broker, thus acting as the hub for communication with the devices on the local network using the MQTT exchange protocol. This capability can also be used to make two or more DELÉGO servers communicate with each other.

This chapter contains all the information for the integration of DELÉGO SERVER, the multiprotocol webserver for the connected buildings by EKINEX, with other devices or services, based on the popular MQTT communication protocol.

MQTT Broker12.2

DELÉGO provides an MQTT broker, to which it is possible to connect not only the same webserver, but also third-party devices that support this protocol, or other DELÉGOs as long as they are in the same LAN network.

This chapter illustrates how to set up DELÉGO's integrated MQTT broker; after carrying out the operations described, it is typically necessary to:

• Configure third-party devices to work with the broker
• Configure DELÉGO itself to make its supervision objects interact with the broker (internal client connection)
• Configure other DELÉGOs to “point” to the broker

For the first point, you need to refer to the documentation of the devices to be integrated with the broker. The second and third points are covered in the following chapter; if you do not want to use DELÉGO's integrated broker but only configure a connection to an external broker, we recommend moving directly to the next chapter.

Broker settings12.2.1

Open the MQTT section in the bar and select the MQTT Broker tab, to set the following:

1. Execute at startup: starts the broker when the system is powered up.
2. Authentication: verifies the credentials of the connecting clients against the list of Users (see the next chapter). Strongly recommended.
3. Allowed connections: All, or SSL only to accept encrypted connections only.
4. Ports used: the ports on which the broker listens, 1883 for plain connections and 8883 for SSL connections. Not editable.
5. Execution state: whether the broker is running, reported as text, next to RESTART, which restarts it.
6. APPLY: saves the settings of the tab.

Unlike the other communication processes of this version, the broker tab has no status bar with the coloured dot: its state is reported as text in Execution state. After changing a setting, press APPLY and then RESTART, so that the broker starts again with the new values.

Users12.2.2

With authentication enabled, every client device that connects to the broker needs a user of its own. DELÉGO itself needs one too, for when it connects to its own broker as a client; that is the subject of the next chapter.

Pressing ADD inserts a new row in the Users section:

After every change to the list press REFRESH. Once the users are in place and the broker is running, carry on with the next chapter to configure the connection of the client.

MQTT Client12.3

DELÉGO allows connection to more than one MQTT broker simultaneously; it is advisable to limit the number of such connections as much as possible, so as not to overload system resources. It is possible to associate one or more supervision objects with each MQTT connection; in this way:

• when a value is received via MQTT, it is passed to the object as a command
• vice versa, when the object changes state, its value is sent to the broker via MQTT

To each of the objects associated with the connection, it is possible to assign two topics, i.e. the communication channels on which DELÉGO exchanges information with the broker; for further information on MQTT topics, please refer to the specifications of this protocol, and to the documentation widely available on the internet. The report topic is used by DELÉGO to send the state of objects every time it changes:

Conversely, when DELÉGO receives a value on the command topic, it runs that value as a command on the object.

In both cases, DELÉGO expects numeric values to be exchanged on the topics, using the dot as decimal separator (if they are not integer values). No other format is supported, JSON included. For each object it is necessary to indicate at least one command topic or one report topic. Both may of course be specified.

It is strongly discouraged to use the same topic for both the command and the report, because loops could be generated.

To connect to your integrated broker it is necessary to configure a connection in any case, however using a simplified procedure, better described below.

New connection12.3.1

To create a new connection, open the MQTT section in the bar and select the MQTT Client tab. Add a connection with the Add action of the root node of the context tree, then select it to set its parameters. Its card looks like the following figure:

Enter the following information:

Once all the data has been entered, press RESTART in the status bar to start the connection with the new parameters; if the data and credentials are correct, after a few seconds the dot turns green and Connection status becomes CONNECTED. Changing one of these parameters stops the connection and turns the dot red, so that it never keeps running with the old values: press RESTART again to start it with the new ones (see Workspace). At this point, everything is ready to associate the objects with the connection.

Object association12.3.2

Drag into the ASSOCIATED OBJECTS section the supervision objects that you want to connect to the service; for each of them it is necessary to specify at least one of the following parameters:

It is possible to directly control the object through the selector in the STATUS column, in order to verify in real time whether the MQTT communication takes place correctly:

The following screen shows an example of MQTT test client software, with which it is possible to subscribe to the same broker and read / write on the same topics, thus verifying the correct communication of DELÉGO:

Before carrying out a test with DELÉGO, it is recommended to verify the correct configuration and functionality of the broker. For this purpose, it is possible to use other known devices, or two instances of an MQTT test client software, mutually writing to and receiving from the command and report topics. If the expected behavior is verified, it is then possible to configure DELÉGO and carry out the appropriate checks in the real environment.

Internal connection12.3.3

To connect to the internal broker of DELÉGO select Internal broker in the configuration of the client connection seen previously; in this case it is not necessary to fill in all the fields normally required, and it is possible to choose the user from a drop-down menu (instead of typing it manually). For security reasons it is still necessary to specify the password.

M2M connection12.3.4

It is possible to use the MQTT protocol to establish a bidirectional machine-to-machine communication between several DELÉGO servers, provided they are all connected to the same network. First of all it must be decided which DELÉGO should act as “master”, and the built-in MQTT broker must be enabled on it. Then the MQTT client connections must be configured as follows:

• On the same DELÉGO configure an Internal broker connection, selecting one of the previously created users
• On the other DELÉGO servers create a generic connection, specifying the IP address of the master and manually typing the user to be used

For each of the DELÉGO servers, including the master, a dedicated user must be provided, and a unique client ID must be assigned....

To control an object of another server from a DELÉGO, at that point, it is necessary to proceed as follows:

• In the DELÉGO to be controlled, drag the technology object (e.g. KNX) into the connection tab, arbitrarily choosing one topic for the command and one for the status
• In the other DELÉGO servers, create a virtual object with the same graphical rendering and drag it into the corresponding MQTT client connection, using:

○ As command topic the one that on the other server is marked for the report ○ As report topic the one that is instead used for the command

In other words, the topics must be “crossed” between the object to be controlled and the “synchronized” object on the other DELÉGO.

M-Bus13

Introduction13.1

M-Bus (Meter-Bus) is the bus used by heat, water and gas meters. This chapter describes how to configure and visualize one or more M-Bus devices in DELÉGO SERVER.

For related topics, see also the Energy chapter.

M-Bus13.2

DELÉGO handles one or more metering devices speaking the M-Bus standard, over an RS-485 connection or over the LAN. The protocol is widely used for energy metering inside buildings.

The server supports both transports, and can work in two roles: as the master that interrogates the devices, and as a sniffer of the traffic another concentrator generates.

This chapter covers what there is to do:

• create an M-Bus communication line;
• scan the devices present on the line;
• choose which of them to bring into the project;
• place them in the energy flow management and in the consumption monitor of the supervision.

Lines13.2.1

A set of M-Bus devices connected together (on the same RS485 line, or conveyed through the same IP interface) is managed in DELÉGO by a line. M-Bus is not a section of its own: it lives in the Integrations section, on the MBUS tab, where the context tree lists the lines already defined. A new line is created with the Add action of the MBUS node, which appears on the node when the pointer is over it. Once a line has been created, select it in the tree to set its properties, as in this example:

The status bar at the top of the card shows the Execution state of the line as a coloured dot, and holds RESTART. A change to the communication settings below stops the line and turns the dot red, so that it never keeps running with the old values: press RESTART to start it again with the new ones (see Workspace). The available properties are the following:

With Serial, the parameters of the port used to reach the slave devices appear:

With Network, the address of the IP gateway appears instead:

Two further parameters govern the polling:

Discovery13.2.2

Once the line has been configured correctly and Enable is on, the devices present on it can be detected.

The DISCOVERY button starts the search. The operation queries the devices one address at a time and takes a few minutes; to narrow the search and reduce the waiting time, enter the lower and upper limits in the two Discovery from … to … fields before starting the procedure.

At the end of the scan, the devices detected are listed under NEW DEVICES, with their name and secondary address. If a device does not expose a name on the bus, it is shown as a device without a name with the manufacturer's abbreviation (usually three letters) in brackets; that wording and the secondary address, which is the unique serial number of the device, are what allow the detected devices to be told apart.

Configuration13.2.3

The devices discovered by DISCOVERY are not yet part of the project: you have to select the ones you intend to insert and press CREATE WIDGET.

Not all detected devices must necessarily be managed in the project; in situations of shared metering systems for example, as in the case of condominiums, meters of different ownership typically coexist on the same line, and typically only those relating to one's own housing unit are of interest to the supervisor. The configuration procedure carries out a second, more in-depth reading of the parameters that the devices involved make available, and creates the object structures within the project database. Depending on the number of enabled devices, this operation may also take a few minutes. At the end, the objects created are usable in the supervision, and the corresponding entries are removed from the NEW DEVICES list.

If the device configuration changes at a later time, it is possible to update their list of attributes (channels) with the REFRESH button.

Devices13.2.4

Selecting a device opens its card, with the general data at the top and the Channels list below.

The following information is made available in the general data section:

Each M-Bus device provides a series of information, which can represent its configuration, its version, and the measured quantities. The list of this information is not known a priori, and depends on each device; in the case of measured quantities, the unit of measurement is typically also made known. This information is represented within DELÉGO in the form of objects, listed in the Channels list; to leave some of this information out of the Visualization, clear the corresponding VISIBLE box. By also accessing the detail sheet of each of these objects, it is also possible to associate them individually with a room, through the appropriate drop-down menu in the general data.

Load control13.2.5

Some M-Bus devices are automatically enabled to be directly inserted into the load control; for this to happen, they must have at least one electrical power type quantity.

If an M-Bus device falls into this category, the sub-information necessary for use is also available: under the Channels list of the device, the Load control section adds the minimum and maximum power limits, the priority and the Over limit indication.

Consumption monitor13.2.6

M-Bus devices can be inserted directly into the consumption monitor (please refer to the Energy chapter for further details).

In order for them to be correctly managed in this section of the supervision, however, it is necessary for them to have at least one energy type quantity (for the categories relating to energy) or volume type (for the categories relating to gas and water).

By dragging a device within a category of the consumption monitor, a check is carried out on the list of quantities; if a quantity suitable for that category is not found, a warning is shown: in the Counters list, a device that exposes no volume quantity is marked in red Measured volume missing, while a compliant one is marked OK.

For further information, please refer to the Consumption monitor section of the Energy chapter.

Philips Hue14

Introduction14.1

This chapter contains all the information for configuring and visualizing a PHILIPS HUE lighting system inside DELÉGO SERVER, the multiprotocol webserver for the connected buildings by EKINEX.

Configuration14.2

DELÉGO SERVER brings one or more bridges of the PHILIPS HUE lighting system into the supervision. The lights are then handled as though they were KNX widgets: in the Visualization, and in the automations, scenes, logics and schedules alike.

Creating a bridge14.2.1

Open the Integrations section in the bar and select the Philips HUE tab, then add a new bridge. Open its card and enter the following data:

The card guides the connection in four steps, listed under CONFIGURATION STEPS: enter the IP address of the bridge, press the physical button on the Philips Hue bridge, press PAIRING on the card to complete the connection and, once the User field is filled in, press DISCOVERY to detect the lights and create the corresponding widgets. The status bar at the top of the card reports the Execution state of the connection as a coloured dot; changing the IP address stops the connection and turns the dot red: press RESTART to start it again with the new value (see Workspace).

Discovery14.2.2

Press DISCOVERY on the bridge card to detect the lights in your PHILIPS HUE system; at the end of the procedure they appear in the tree on the left, under the bridge, one node per light. Three types of light are recognised, each with its own icon:

• Dimming lights white lights with intensity adjustment only
• RGB lights lights with color control
• Temperature lights white lights with adjustment of intensity and white temperature

Each light found is a widget of the project: to show it in the Visualization, drag it into a room of the building tree in the Project section, as for any other widget; only the lights placed in a room are shown.

Visualization14.3

The different types of PHILIPS HUE lights can be managed inside the Visualization pages of DELÉGO, in much the same way as the widgets based on other technologies (e.g. KNX).

The following pictures show an example of the different light types, when their popup is opened in the app or browser:

Sonos15

Introduction15.1

This chapter contains all the information for configuring a SONOS multimedia system inside DELÉGO SERVER, the multiprotocol webserver for the connected buildings by EKINEX.

Configuration15.2

Discovery15.2.1

Open the Integrations section in the bar and select the Sonos tab. The tab holds one or more Sonos system objects, each of them a SONOS installation reachable on the network.

Press DISCOVERY on the card of a system to look for the SONOS devices on the same network as DELÉGO SERVER. While the search runs, the card reports that it is looking for devices, and at the end it says how many devices are new and how many have been updated. The zones found are then listed in the ZONES section of the card. The status bar at the top of the card reports the Execution state of the system as a coloured dot, green while it is communicating, and a change to its settings stops it and turns the dot red, until RESTART starts it again with the new settings (see Workspace).

If no device answers, the card reports that no SONOS device was found: check that the players are powered and on the same network as the server, then repeat the discovery.

Zones15.2.2

Each zone found is an object of the project, with the IP address of its player and a set of Commands:

As with the other technologies, a zone is shown in the Visualization once it has been dragged into a room of the building tree of the Project section; only the zones placed in a room are shown.

Sentio16

Introduction16.1

DELÉGO SERVER can act as a KNX gateway to control the Ekinex SENTIO system via pushbuttons or dedicated SIGNUM screen. The gateway is configured in the Integrations section of the bar, on the Sentio tab.

Discovery16.2

In the Administration, open the Integrations section in the bar and select the Sentio tab.

The status bar at the top of the gateway card reports its Execution state as a coloured dot. If the gateway is not running, turn on Enable communication and press RESTART; the dot turns green (see Workspace). Changing a setting of the gateway stops it again and turns the dot red: press RESTART to start it with the new settings. The SENTIO streamers present in the same network as DELÉGO SERVER are then recognised and listed under NEW DISCOVERED DEVICES:

Configuration16.3

To configure one or more zones inside the gateway, turn on the ENABLE switch of each of them and press CREATE WIDGET. When the operation finishes, the configured zones leave the list and appear in the tree on the left, under the gateway.

A green State indicator on the zone card confirms that the server is talking to the streamers. A red one means it is not: check that the streamer is properly connected to the local network.

KNX addresses16.4

In the details page of each streamer it is possible to set the KNX group addresses:

The card shows at the top the State of the zone, which reports whether the gateway is reaching the streamer. Below, KNX ADDRESSES has one row per feature: the COMMAND and FEEDBACK group addresses side by side, the STATE read from the streamer and, under TEST, the buttons that write a value to it. Rows that are feedback only, such as Track or Author, have no command address; rows that are command only, such as Prev/Next or Volume up/down, have no feedback address.

The group addresses can be either typed manually in the fields or dragged onto them from the ETS tree shown in the right panel.

The KNX group addresses entered in the COMMAND column can be used by any KNX device to give commands to the SENTIO streamer; vice versa, the status information of the audio zone is sent upon change to the group addresses entered as FEEDBACK.

The following features are available for each audio zone:

Once the KNX group addresses have been specified, they can be used immediately without further saving operations.

As regards specifically the increase/decrease of the source, the detail page of the Source up/down row (the Edit action of the row) makes it possible to select which sources should be taken into consideration, if not all of them are used:

Use in combination with Signum16.5

The SIGNUM virtual pushbutton panel provides a graphic screen for controlling a multimedia area of a KNX compatible audio system. In particular, this screen can be used to control a SENTIO streamer, through the DELÉGO SERVER gateway function.

For optimal use we recommend using the following versions of SIGNUM:

• Firmware: release 1.2.0 or later
• ETS library: release 0.6 or later

Furthermore, to view the SIGNUM audio screen, it is necessary to apply a specific license voucher to the keypad; for further details, please refer to the relevant documentation.

Parameters

Inside the SIGNUM ETS library it is first necessary to enable the audio screen (and the corresponding tab configuration), through the following flag:

In the AUDIO configuration tab, first enable all the features, as in the following example:

Finally, it is recommended to enable the maximum number of sources available in SIGNUM (6) and to associate them with the same number of SENTIO presets, therefore using the numbers from 1 to 6 as numbering (to be read / written on the KNX bus). In this way, via the SENTIO app you can associate your favorite streams with PRESETS, and you can subsequently recall them from SIGNUM.

Alternatively, you can reserve one or more sources of SIGNUM to activate a different input from a stream, such as Bluetooth (see following screenshot):

As regards the wording to be assigned in SIGNUM, it is recommended to adopt a generic nomenclature “PRESET 1”, “PRESET 2” etc... in order to subsequently be able to customize the streaming associated with each preset, without having to consequently adapt the wording in SIGNUM. The colors obviously can be chosen as you wish.

In any case, please remember that the wordings of the SIGNUM sources can also be modified via the EKINEX TOOL app, therefore without the need to modify and download the ETS project again.

Group addresses

The SIGNUM library provides a series of group objects, through which the pushbutton panel updates its status on the screen according to the SENTIO audio system, and on the other hand allows commands to be sent to DELÉGO SERVER, which forwards them to the corresponding streamer.

The following figure shows an example of configuration of group addresses associated with the different group objects, for a SIGNUM with audio function enabled:

As you can see, the group addresses associated in ETS with the “COMMAND” type group objects must be reported in the COMMAND column of DELÉGO, and vice versa as regards the states (“FEEDBACK” column).

The card of the same zone in the current version of the server is described in KNX addresses.

Security17

Introduction17.1

This chapter contains all the information for configuring and visualizing a compatible intrusion detection system inside the DELÉGO SERVER visualization.

General overview17.2

DELÉGO controls the intrusion systems it supports natively, connecting to them over the LAN or through a USB or serial port, depending on the panel.

Native supervision is safer than going through an external gateway, such as a panel interfaced over KNX: it speaks the protocol certified by the manufacturer of the security system, and the exchange of information is encrypted.

It is also far more flexible, because a native integration typically reaches every single aspect of the panel, rather than the handful of signals a gateway exposes.

Creation of a control panel17.2.1

Once the license code of the desired technology has been entered, DELÉGO SERVER provides a dedicated section in the area

Integrations → Security

of the configuration menu, based on the license entered.

By expanding this section, and the corresponding Control panels item, it is possible to add a new control panel with the Add action of the node in the context tree. Depending on the chosen technology, it is possible to create a single control panel, or communicate with multiple control panels at the same time; for further details, please refer to the subsequent sections of this chapter.

Once the new control panel card has been opened, it is possible to set the general communication parameters, which depend on the type of technology chosen. Furthermore, in the subsequent sections of the page, it is possible to create sub-objects that represent the different functions of the anti-intrusion system, the number of which depends on the specific configuration and the number of devices installed.

The following table summarizes the types of functions made available by the different technologies:

Adding features17.2.2

To add one or more functions, specify the number of objects to create in the appropriate field and press ADD; new objects are numbered progressively starting from the last number used. The numbering reflects what is configured within the control panel and therefore functions as a reference key for the security system.

Once the sub-objects have been created, you can:

• Assign an identifying label (e.g. location of a sensor)
• Modify any detailed parameters by accessing their tab
• Drag them into one or more rooms, to allow their management in navigation by floors, as well as in the specific dedicated section of supervision
• Use them within logic or as triggers for automatic actions (scenes, notifications etc...)

Central States17.2.3

The states of the control panel are a particular kind of sub-object: their number cannot be chosen. Pressing ADD creates, according to the model of panel, the set of elements that stand for its states and alarms.

As with the other objects, once they exist their default name can be changed and they can be assigned to a room. They can also be used inside logic blocks, to command the KNX system or run a scene depending on the state of the panel.

Visualization17.2.4

Once the anti-intrusion system has been configured and communication has started, open the Visualization with Frontend, in the Configuration menu, and select the item

SECURITY

it is possible to manage the entire anti-intrusion system through a control panel similar to the following figure:

Depending on the type of integrated control panel, the following sections are available:

When accessing from a smartphone, given the limited size of the screen, one section is displayed at a time; it is possible to switch from one section to another via the toolbar at the bottom.

Tecnoalarm17.3

Compatibility17.3.1

DELÉGO talks to every TECNOALARM control panel that offers the TECNO-OUT protocol. Enabling that protocol may require an additional license from the manufacturer.

The connection is over the LAN or directly over USB. Only one intrusion panel can be managed.

Preparation of the control panel17.3.2

NETWORK COMMUNICATION Inside the control panel configuration software, in the LAN configuration section, it is necessary to tick the Enable checkbox and enter the network parameters, making sure they are compatible with DELÉGO (same subnet).

In the SERVER section it is possible to configure up to 4 connections for “generic tasks”, such as via iOS-Android apps, remote monitor software etc... DELÉGO does not fall into this category, having to be configured in the Tecno-out section (as detailed below) however it is important to check that the configuration of the “generic” servers does not conflict with the subsequent configuration of DELÉGO.

If you need to use one of the 4 “generic” servers, it is important to make sure that the port is unique for each server, and different from the port subsequently configured in the Tecno-Out section. The port can be any number greater than 10,000 and less than 65,535.

In the TECNO-OUT tab it is possible to configure dedicated access to the Tecno-out server, therefore reserved for DELÉGO. In particular it is necessary:

• Enable the protocol using the appropriate enable box
• Select “SERVER” mode
• Insert a port with a number greater than 10,004, consistently with what was seen previously (port greater than 10,000 and unique)
• Enter a passphrase that serves as the basis for encrypting communication

It is strongly recommended to enter an alphanumeric passphrase that is not easily reproducible, possibly “pseudo random”, because the encryption algorithm for data transit on the LAN network and therefore the security of the system is based on this parameter. For the correct functioning of DELÉGO, furthermore, the passphrase must be exactly 16 or 32 characters long; based on the length, DELÉGO must be appropriately configured as detailed below.

NOTE

• For the basic operation of the integration there are no configurations of the “Whitelist” parameters, please refer to the official Tecnoalarm documentation for this type of setting.
• The programming of these 3 phases is sent to the control panel and set correctly only when a complete sending is carried out in “first programming of the control panel” mode (as reiterated several times at the bottom of the sheets themselves): to make this happen, it is necessary to set from keypad the control panel identifier to FFFF and send the complete programming. To change the control panel identifier you need to log in from the console with the installer code (factory default 54321) and go to the “Telephone” - “Callback” - “Identifier” menu: with the upward arrow you delete the 4 numbers of the pre-existing identification code, by typing “yes”+“6” four times, the FFFF identifier is entered. By pressing “Exit” until you return to the date and time on the console, the data is stored. At this point it is necessary to completely re-download the configuration to the control panel using the Tecnoalarm software and proceed with testing.
• Integration access code: even in the preliminary phase it is necessary to use a code with sufficient rights to be able to act on the various functions of the control panel. To facilitate the task, it is strongly recommended to use the master code in order to verify the correctness of the functionality integrated between DELÉGO and the control panel. Furthermore, in the case of communication via network, after each change to the control panel configuration, it is of fundamental importance to carry out the following steps:
• Set the control panel in “first programming” mode
• Enter the master code
• Reset panel ID to “FFFF”

Communication check17.3.3

Before tackling the integration into DELÉGO, it is recommended to check communication using the TECNO-OUT MONITOR program, available for WINDOWS PCs.

Configuration17.3.4

In the card of the TECNOALARM control panel inside DELÉGO, the following information is requested:

The user code is used for all non-interactive operations (periodic status request, reading of the panel log and so on), so it has to be a code that is allowed to perform them.

Depending on the communication mode chosen, it is possible to set this additional information:

Once this information has been specified, it is necessary to press the UPDATE CONF. button to activate the communication. This operation is necessary whenever the user code or communication port is changed. After pressing UPDATE CONF., check the correctness of the configuration, in particular:

• In the case of a USB connection, check that the corresponding port is connected to a device
• In the case of a LAN connection, check that the IP address corresponds to a device on the network

Once the communication parameters have been configured, the objects that represent the programs (the arming modes) and the zones (the detectors) are inserted through the ADD button of the sections of the same name, and the same button in the CENTRAL STATES section creates the objects that carry the status and error signals of the panel.

Zones and programs keep the number they have in the control panel, which is what ties the object in DELÉGO to the physical one; the central states arrive as a ready-made list of read-only signals, each with its own visibility flag and its current value.

Log17.3.5

The TECNO-OUT communication protocol allows you to read the log inside the control panel and show it in DELÉGO; in this way, it is possible to review the operating events and the actions carried out on the security system, not only through the webserver but also through keypads, key readers and so on. To consult the logs in the administration of DELÉGO, select the item

Integrations → Security, node TecnoAlarm → Log

The following screen is shown:

SEARCH OPTIONS restricts the list to a period, with the two date fields, and three buttons act on the result:

Each record carries Date, Time, Level (the severity), Type and the Message as the panel worded it.

Visualization17.3.5.1

In the Visualization, the control center of the TECNOALARM system allows you to manage the PROGRAMS, ZONES and CENTRAL STATES as already seen on a general level. Furthermore, it is possible to consult the control panel log by selecting the appropriate button in the toolbar at the bottom (if accessed from a smartphone) or by scrolling on a tablet / desktop to the corresponding panel:

By pressing a specific message in the log list, the corresponding record is expanded to allow reading in case of long messages.

To arm a program, press the corresponding status button (normally REST); you are asked to enter your PIN, as exemplified in the figure below. If the PIN entered is correct, after a few seconds the program switches to the ARMED state.

Similarly, it is possible to exclude individual zones of the system.

The PIN entered in the DELÉGO Visualization is passed to the control panel for validation; it is therefore possible to use the same user PIN that is used to interact with the anti-intrusion system, for example, from the keypad. DELÉGO does not process or validate the PIN to authorize commands.

EL.MO. / IESS17.4

Compatibility17.4.1

DELÉGO talks to EL.MO. and IESS control panels, over USB or over the LAN. Unlike the other integrations of this chapter, this one manages several panels at once.

Control panel configuration17.4.2

In the control panel tab inside DELÉGO, the following information is requested:

The following status indicators are also available:

Once the communication parameters have been configured, start the gateway with START; after any later change press UPDATE CONF. so that it is applied.

Sectors, inputs and outputs17.4.3

It is possible to define the SECTORS, INPUTS and OUTPUTS within DELÉGO using the ADD button in the corresponding sections of the page, specifying the number of objects to create:

By accessing the detail sheet of a sector, it is possible to change its number (which is also possible in the general list) and, if desired, set a PIN different from the general one.

If, after changing a PIN at a single sector level, you change the panel PIN again, the latter will be applied again to all sub-objects, therefore invalidating the specific PIN.

The lists at the bottom of the page allow you to manage the sector arming commands and all its states. To allow the correct updating of the states, it is necessary to associate the inputs with their sectors, thus replicating the configuration carried out within the control panel. To associate one or more inputs with a sector:

• Access the sector tab
• Identify the “Related inputs” section
• Look for the inputs by filtering by source panel
• Drag the inputs into the “Related inputs” section

Alternatively, it is possible to proceed in the opposite way, i.e. access the card of an input and drag the sectors, once found by filtering the source panel, into the Related sectors section. In a completely similar way, by accessing the Input and Output tabs, the list of commands available for interaction and available states is summarized.

In all the element types seen previously, the “digest” sub-object is available; it represents a state of synthesis, based on priority among the other available states, and is the graphic element that is reported in the supervision, with an associated color, depending on whether it is a state of exclusion (gray), rest (green), activation (yellow) or alarm (red).

Central States17.4.4

Pressing ADD in the Status panel section creates the objects that stand for the state of the system.

They can simply be displayed, or used like any other state object seen so far: inside a logic, or as a trigger that fires KNX commands, scenes and notifications.

Visualization17.4.5

In the Visualization, the control center of the EL.MO. / IESS system allows you to manage the SECTORS, INPUTS, OUTPUTS and CENTRAL STATES as already seen on a general level.

By pressing on a sector, the following detailed pop-up is displayed:

The upper portion highlights the Synthesis sub-object of the sector; the elements below allow you to send different types of arming or exclusion commands. Similarly, by accessing the input and output pop-ups, the list of the states they are in is shown and, in the case of the outputs, the ON/OFF control selector is made available:

Also in this case, the part at the top summarizes the status, while the selector below allows you to send the exclusion command (for the inputs) or activation (for the outputs). All the commands mentioned are executed only upon correct entry of the PIN.

The PIN entered in the DELÉGO Visualization is validated by the webserver, based on what is set in the configuration sections seen previously. This PIN does not necessarily coincide with what is set at the control panel level.

Paradox Evo17.5

Compatibility17.5.1

DELÉGO talks to the PARADOX control panels of the EVO family over a serial connection, which requires a PRT-3 printer module between the two systems. Only one panel can be managed.

Preparation of the control panel17.5.2

PRT-3 MODULE The communication module must be installed and configured as shown in the following screenshots:

CENTRAL OUTPUTS To allow DELÉGO to control the control panel outputs, the following configuration must be set up:

Configuration17.5.3

In the PARADOX EVO control panel data sheet, the following information is requested:

It is possible to define within DELÉGO the AREAS, ZONES and UTILITY KEYS that have been configured in the control panel, using ADD in the corresponding sections of the page. Furthermore, as already seen on a general level, through the ADD button in the Central alarms section, it is possible to create a set of objects that represent the different states / alarms of the system.

Visualization17.5.4

In the Visualization, the control center of the PARADOX EVO system allows you to manage AREAS, ZONES, UTILITY KEYS and CENTRAL STATES as already seen on a general level.

By pressing on an area, the pop-up shown below is displayed, which allows you to send different types of commands, both in terms of arming modes and for specific call or reset actions. Every command sent to the system is authorized only after the valid PIN has been entered, as previously configured. The PIN entered in the DELÉGO Visualization is validated by the webserver, based on what is set in the configuration sections seen previously. This PIN does not necessarily coincide with what is set at the control panel level.

Axel17.6

Configuring the control panel17.6.1

The configuration of the AXEL control panels can be done either directly from the keypad or via the Oberon software. Refer to the manufacturer's website (https://www.axelweb.com/) for further information and to download the necessary documentation and material. The procedure described below involves configuration via the Oberon software.

Enabling communication

The first thing to do is enable communication with external entities. To do this, simply modify the “Active service” item found in the Communications and connection → Network services configuration → User connection menu. Remember to send the programming to the control panel for the change to take effect.

Customizing the LAN code

The LAN code is used by the control panel to authorize the communication requested by external entities, such as DELÉGO. Its default value is “000000”, but the installer can change it as required. Simply change the “LAN Code” field found in the Communications and Connection → Network Services Configuration → User Connection menu. Remember to send the programming to the control panel for the change to take effect.

Communication port towards DELÉGO

The communication port towards external entities such as DELÉGO is not expressly mentioned or configurable in the Oberon software. It is important to note that you cannot use the same port used for the connection with the Oberon software, because the protocol adopted is not compatible.

The communication port open towards DELÉGO is always the one immediately following the one configured for the Oberon software. The port configured for the Oberon software is found under the “TCP Port” item in the Communications and connection → Network services configuration → Installer connection menu. The default value for the port reserved for the Oberon software is 8030, consequently the communication port open towards DELÉGO by default is 8031. Remember to send the programming to the control panel to make the change effective.

Delégo Configuration17.6.2

To be able to use DELÉGO’s Axel features, you need to have an additional activation license. To verify that you have the necessary license, or to enter the code received at the time of purchase, proceed as follows:

• Authenticate on DELÉGO with a user authorized to access the administration
• Open the Settings section and select Modules and licenses
• Identify the “AXEL” entry and check the presence of a valid license (identified with green writing)
• If the license is not present or valid, enter the new code in the corresponding field and press “SAVE”

CENTRAL Once the module license has been activated, it is necessary to configure communication with the intrusion detection control panel; for this purpose:

• Open the Integrations section of the bar, Security tab
• Select “AXEL” then “Axel centrals”
• Use the Add action of the node in the context tree at the bottom to create a new control panel
• Select the new item in the context tree to open its card

The following information is requested:

Once this information has been specified, it is necessary to press the UPDATE CONF. button to activate the communication.

This operation is necessary whenever a structural change is made to the control panel data or to the objects connected to it, with the exception of names.

AREAS

Once the control panel has been defined, it is possible to configure one or more areas associated with it, whose status is monitored by DELÉGO and displayed in the Visualization. To create one or more areas, proceed as follows:

• Access the control panel tab
• Type the number of areas to create in the text field next to the “ADD” button within the “AREAS” section title
• Press the ADD button

As many areas as requested are automatically created, numbered progressively starting from the last area index present in the project. The sub-objects belonging to the area are also created, which control its state and display. Once created, areas can be renamed simply by typing the new name in the appropriate text box.

It is also possible to access the detail sheet of the areas, through the corresponding edit button; the “DELETE” button, on the other hand, removes (permanently) the area from the project. By accessing the detail sheet of an area it is also possible to view the sub-objects that make up the area itself through the “AREA PROPERTIES” section.

Also in this case it is possible to rename the sub-objects and view their current value through the “STATUS” column; through the same column it is also possible to control the sub-objects that are enabled for the control.

ZONES

In a similar way to what was seen for the areas, it is possible to configure one or more zones within DELÉGO by typing the number of objects to create in the corresponding field and pressing the “ADD” button:

Also in this case, once the objects have been created they can be renamed.

RELATIONSHIP BETWEEN AREAS AND ZONES

To associate the zones that apply to each area, you need to:

1. click on the “edit” button (the one with the three dots) next to the affected area 2. click on the “edit” button next to the sub-object of the area concerned (Armed in X mode) 3. search for the desired zones by pressing the title “ZONES ASSOCIATED WITH GROUP X”, or using the search tool at the top left 4. drag the zones to be associated from the search results to the appropriate list in the area detail screen

The objects of the dragged zone are also related automatically to the zone sub-objects corresponding to the same mode. These relationships can also be created by hand, by opening the sub-object of the area.

Central warnings DELÉGO can monitor a series of status information made available by the control panel. These objects differ based on the control panel model; for this reason they are created dynamically when a model is selected in the control panel detail sheet; on the contrary, if no model is selected (option “---”) any “Central warnings” objects previously created by selecting a model are eliminated.

Automatic creation of central state objects takes a few seconds. Do not close the window or perform any other operation until the operation is complete.

The following figure shows an example of a control panel with configured alerts:

Usage17.6.3

Once an Axel control panel and the related sub-objects have been configured, they are automatically available for use in the FRONTEND, in the “SECURITY” section of the navigation menu. This page allows you to quickly access the complete list of areas, zones and central alerts (toolbar at the top right) and manage them as detailed in the following paragraphs.

AREAS

The areas are presented in the FRONTEND in the form of “widgets”. The icon at the top right highlights the arming status, as exemplified in the following figure:

Pressing on an area opens the relevant detail popup showing the states of its sub-objects...

... and provide the following direct commands:

• DISARM: disarming the area
• INT: arming the area in INT mode
• ON: arming the area in ON mode
• PAR: arming the area in PAR mode

By pressing a command button, the user is asked to specify the numeric PIN set in the control panel card: ZONE

Similarly, the zones appear as “widgets” which allow the exclusion or, vice versa, the enabling of previously excluded zones; also in this case, the icon at the top left highlights the current status of the zone, and any command in the detail popup must be authorized by the user by entering the PIN specified in the control panel card.

CENTRAL WARNINGS

The control panel alerts are presented in the FRONTEND in the form of a “widget” and show a general picture of the “health status” of the control panel:

Bentel Absoluta17.7

Compatibility17.7.1

DELÉGO talks to every BENTEL control panel of the ABSOLUTA family, over the LAN.

Preparation of the control panel17.7.2

NETWORK COMMUNICATION Before configuring DELÉGO, it is necessary to set up communication via the network, through the IP section of the BENTEL BOSS configuration software:

In particular, it is necessary to set the following parameters:

This information must then be entered consistently in DELÉGO.

Central configuration17.7.2.1

In the BENTEL ABSOLUTA control panel card inside DELÉGO, the following information is requested:

The following status indicators are also available:

Once the communication parameters have been configured, start the gateway with the START button; in the event of any subsequent changes, press UPDATE CONF. so that they are implemented.

Central States17.7.3

When the control panel is created, the following general states are made available:

Once communication is started, they are automatically aligned with the control panel. It is possible to establish which of them are visible in the Visualization by acting on the corresponding VISIBLE flag. Among these, the general command is also available INSERT COMMAND

through which it is possible to force a simultaneous arming of the entire system, in one of the possible partial arming modes (A, B, C or D). All other items in the list are read-only.

Areas, zones and outputs17.7.4

It is possible to define the AREAS, ZONES and OUTPUTS (panel outputs) within DELÉGO using ADD in the corresponding sections of the page:

By accessing the detail sheet of an area, it is possible to change its number (which is also possible in the general list) and, if desired, set a PIN different from the general one.

If, after changing a PIN at a single area level, you change the panel PIN again, the latter will be applied again to all sub-objects, therefore invalidating the specific PIN.

The list at the bottom of the page allows you to manage all the individual aspects of the area; it is also possible to force an arming command, using the appropriate element. The individual objects in this list not only allow you to control the status of an area, but can be associated with other elements of supervision, through logic or as triggers to perform actions (e.g. KNX commands, scenes, notifications and so on).

In a completely similar way, by accessing the tab of a zone, the following is shown:

Also in this case, in addition to monitoring individual aspects of the sensor, it is possible to send an exclusion command. Finally, the detail sheet of an OUTPUT of the control panel allows you to control it and view what state it is in at a given moment.

In all the element types seen previously, the “digest” sub-object is available; it represents a summary state, chosen by priority among the other available states, and is the graphic element that is reported in the supervision, with an associated color, depending on whether it is a state of exclusion (gray), rest (green), activation (yellow) or alarm (red).

Visualization17.7.5

In the Visualization, the control center of the BENTEL ABSOLUTA system allows you to manage the AREAS, ZONES, OUTPUTS and CENTRAL STATES as already seen on a general level.

By pressing on an area, the following detailed pop-up is displayed:

The upper portion highlights the state of synthesis of the area; the first element below allows you to carry out an arming command, in one of the partitions A...D, or to disarm; you are asked to enter a PIN to validate the operation. The subsequent elements are read-only, and highlight the different states in which the area is found. Similarly, by accessing the ZONE and OUTPUT pop-ups, the list of the states they are in is shown and, in the case of the outputs, the ON/OFF control selector is made available:

The PIN entered in the DELÉGO Visualization is validated by the webserver, based on what is set in the configuration sections seen previously. These PINs do not necessarily coincide with what is set at the control panel level.

VoIP Intercom18

Introduction18.1

This chapter contains all the information for the configuration of DELÉGO SERVER as a SIP server for IP phones and door intercom phones. In particular, a detailed description is given of the specific configuration of DICO, the multi-function intercom door station with face recognition by EKINEX.

Ekinex Studio18.2

Starting from release 2.8.0 it is no longer recommended, as the primary solution for intercom applications, to use DELÉGO SERVER as the SIP server for DICO and the DELÉGO PANELs.

For an easier configuration of the door phone and the panels, which no longer requires a SIP server like DELÉGO SERVER, it is recommended to use the new EKINEX STUDIO software.

The functionalities described in this chapter remain available for special applications and for third-party devices, and for compatibility with installations created previously.

General overview18.3

DELÉGO SERVER orchestrates the door entry system: DICO door stations, DELÉGO PANEL indoor units and third-party devices, whether door stations or IP phones. Audio and video calls are then handled together, and the same call can reach devices of different makes.

SIP protocol18.3.1

The communication protocol used for the door entry management is called SIP; any third-party device to be integrated must comply with this standard. All the involved devices must be in the same local network; the DICO app for smartphones works with the Ekinex Cloud in a different way, and for this reason, it is not a topic for this chapter.

The SIP protocol requires a (single) server that coordinates all the other devices, acting as clients; in the

Ekinex solution, the SIP server can be the DELÉGO SERVER or a DELÉGO PANEL belonging to the SMART series (8” or 10”). This chapter covers the case of the DELÉGO SERVER as the SIP server.

In order to operate together, the SIP clients must register themselves to the SIP server, with a unique number (the username) and a password:

Once they are registered, they can originate calls, asking the server to be put in communication with a number, or receive calls from other devices, routed by the server.

The number called by a SIP client can be either another SIP client or a call group. In this second case the server makes every SIP client belonging to that group ring, and the first one to answer handles the call (and the other called parties stop ringing).

Due to these principles, the configuration requires the following steps to be followed:

1. The SIP clients (DICO, DELÉGO PANEL or third-party devices) must be declared in DELÉGO SERVER by assigning a number and a password 2. The same number, password and the IP address of the SIP server, must be entered in the SIP account configuration of the clients, in order to instruct them how to register 3. One or more call groups must be created, if multiple calls have to be made (e.g. when a button is pressed on the display of the DICO door station)

Once these steps have been completed, all the interested devices can communicate together with audio and video calls. Normally, in order to complete the configuration, the following operations must be done on the outdoor unit(s) and the touch panel(s) - but they do not strictly affect the SIP communication coordinated by DELÉGO SERVER (and therefore are not covered by this chapter):

• The buttons on the display of DICO (or the physical buttons of third-party outdoor units, where present) must be assigned to the desired number to be called
• The DELÉGO PANELs must be instructed to send the appropriate commands for the opening of doors and gates

Indoor units18.4

Delégo configuration18.4.1

This section contains the instructions for the declaration of the DELÉGO PANELS, or any other third-party IP phone, to be used as indoor units to receive calls from the door station.

Open the following section of the bar

Integrations → SIP, node SIP phones

and use the Add action of the node in the context tree. Enter the new item details page, and fill in the following parameters:

Once done, press the UPDATE CONFIG. button to apply the changes.

Delégo Panel configuration (Smart)18.4.2

A DELÉGO PANEL SMART is configured entirely from its own web interface, both to work with DELÉGO SERVER and to work with DICO.

The instructions are in two separate documents:

• DELÉGO PANEL SMART configuration manual
• DICO integration guide

DICO18.5

Preliminary operations18.5.1

DICO IP address identification18.5.1.1

To configure a DICO unit in DELÉGO SERVER it is necessary to enter its IP address. If it is not already known, proceed as follows:

• Touch the screen of the DICO video intercom to turn it on
• Press anywhere on the screen and hold your finger down until you are asked for a password
• Enter the administration password (default: “admin”) and confirm
• Select the NETWORK item (NETWORK if the device is set in English)
• Identify the IP address on the network configuration detail screen

Delégo Server configuration18.5.2

General settings18.5.2.1

To configure a DICO door station, select the menu item

Integrations → SIP, node Dico

and use the Add action of the node in the context tree. Enter the new item details page and fill in the following parameters:

NAME Description to identify the outdoor unit

Authentication18.5.2.2

AUTOMATIC MODE. With the default manage automatically option, DELÉGO SERVER assigns a strong username and password to the door station by itself and uses them for the communication. This is the recommended approach.

After saving, the username and password that were generated can be read on the card, to be copied into the web interface of the DICO: that interface is still where the parameters DELÉGO SERVER does not govern are configured.

MANUAL MODE. With manual configuration, the communication channel towards DELÉGO (called HTTP API) has to be enabled on the DICO unit first.

Then choose the authentication mode in the web interface of the DICO, among these:

Once the DICO is set, go back to DELÉGO SERVER and enter the same authentication method, username and password.

When everything is filled in, press UPDATE CONFIG. and wait a few seconds. If the data is right the Active selector turns on and the door station is ready to be configured as described below. If it does not turn on, check the IP address and the credentials.

Additional settings18.5.2.3

Once communication has been established, the following additional settings can be configured; they are automatically saved into the DICO outdoor unit without the need to open its web interface.

RELAY

Press the TEST button to check interactively that it works.

LANGUAGE

Select the language used on the display of the DICO unit

LAN NETWORK

Select if the DICO unit must operate with an automatic address (DHCP) or in STATIC mode; in the second case, enter also the IP address, subnet mask and default gateway to be assigned to the unit.

AUDIO

LIGHT

VIDEO

After any change to these parameters, press the SAVE button to send the new settings to the DICO unit.

DICO configuration18.5.3

Set up SIP account 2 of the DICO following its own configuration manual: that is the account the door station uses to register with DELÉGO SERVER.

Third party outdoor units18.6

Third-party door stations can be configured in DELÉGO SERVER as well, provided they speak SIP.

Delégo Server configuration18.6.1

Enter the DELÉGO configuration section and select the menu

Integrations → SIP, node 3rd party intercom

Use the Add action of the node in the context tree, enter the details page and fill the following parameters:

Once setup is complete, press the button UPDATE CONFIG. to apply the changes.

Third party intercom configuration18.6.2

Configure the SIP account of the third-party intercom following its own technical documentation, so that it registers with the IP address of DELÉGO SERVER using the credentials entered in the previous step.

Call groups18.7

Multiple indoor units can be called when an incoming call is received by the DELÉGO SERVER; to do this, a call group containing those indoor units must be created, and the outdoor unit must be instructed to call the group.

To create a new call group, enter the section

Integrations → SIP, node Call groups

and use the Add action of the node in the context tree. Enter the details page and fill the following parameters:

Once the new call group has been created, the indoor units to be associated must be dragged and dropped from the menu (or from the search results) into the Members of the queue section.

When finished, press the UPDATE CONFIG. button to apply the changes. The number associated with the call group can now be associated with the outdoor units to be called when the keys are pressed.

Phone lines18.8

It is possible to connect DELÉGO SERVER to an external service / PBX based on SIP technology by configuring a phone line, called a Trunk in this version, on the SIP tab of the Integrations section.

In order to configure the items described in this chapter, a VoIP voucher must be acquired and the corresponding license entered in DELÉGO SERVER.

Delégo Server configuration18.8.1

Phone lines are called Trunks in this version. Open the Integrations section in the bar, select the SIP tab, and add a trunk with the Add action of the Trunks node in the context tree. Then enter the following parameters in its card:

If you choose a connection to a SIP PROVIDER as the TYPE, you must also specify the following additional information:

Voice messages18.9

DELÉGO SERVER can answer a call with a message recorded beforehand, instead of ringing an indoor unit. The messages are held in the Integrations section, SIP tab, under the Voice messages node of the context tree, and each of them is an object of the project with a number of its own.

Use the Add action of the node to create a message, then open its card:

The message itself is recorded by telephone, from the Recording group of the card: press Record, answer the call that arrives on the phone chosen above, and speak the message. Play calls the same phone back and plays what was recorded, so that the result can be checked before saving.

Once recorded, a message is used as the destination of a call, by choosing Recorded message from the destination types.

Video surveillance19

Introduction19.1

This chapter contains all the information for configuring and visualizing IP cameras inside the Visualization of DELÉGO SERVER.

IP Camera streaming19.2

It is possible to integrate in the Visualization of DELÉGO SERVER one or more video streams from compatible IP cameras. The supported transmission protocols are:

• (M)JPG
• RTSP

The streaming from the IP camera to the client (DELÉGO app or web browser) can be handled in two different ways:

The advantages given by the IP CAMERA PROXY are:

• The IP cameras can be seen also remotely through the EKINEX cloud
• The original RTSP video streams can be seen also in the desktop version of the DELÉGO app or in a web browser, because the proxy converts them into the MJPG format (this limitation is not present in the mobile version of the app)

The side effects are:

• a higher CPU load on the webserver, each time a video stream is retrieved
• a limitation in the resolution of the video streaming due to the conversion

The camera proxy can be enabled or disabled on each configured IP camera, as better described in the next chapter.

Configuration19.3

New IP camera19.3.1

A new IP camera is declared in the Project section: open the Library panel on the right, find IP Camera among the object models, and drag it into the room where the camera is installed.

General properties19.3.2

Once an IP camera has been created, it is first necessary to assign an identifying name and choose the type from those available: standard templates are available for the generic management of the following transmission protocols:

• JPG / Motion JPEG
• RTSP

and specific templates for some brands of cameras / NVRs / DVRs:

• Axis
• Mobotix
• Hikvision
• Elvox

It is also necessary to assign the camera to the room where it is installed, so that it can be correctly displayed in the Visualization.

Once the template has been selected, a list of parameters is proposed which depends on the type of camera; the properties typically required to configure a camera are:

Some additional properties, specific for particular video formats, are described in the following paragraphs. Here is an example of a configuration of a DICO device for video surveillance, using the RTSP string rtsp://admin:admin@192.168.1.115:554/live/ch0_00.

If the camera proxy is active (and also the first time it is enabled), it is necessary to press the UPDATE CONF. button after any change to the parameters.

Specific formats19.3.3

AXIS19.3.3.1

DELÉGO natively supports all AXIS camera and video server models; for further details on the AXIS product catalog, please refer to the website https://www.axis.com.

This video format provides the following specific parameters, in addition to those seen previously:

MOBOTIX19.3.3.2

DELÉGO natively supports all MOBOTIX camera models; for further details on the MOBOTIX product catalog, please refer to the website https://www.mobotix.com. This format does not include parameters other than the generic ones seen previously.

HIKVISION19.3.3.3

DELÉGO natively supports all HIKVISION IP camera and DVR/NVR models that use RTSP streaming; for further details on the HIKVISION product catalog, please refer to the website https://www.hikvision.com.

This video format provides the following specific parameters, in addition to those seen previously:

Visualization19.4

Once a camera has been placed in a room it appears in the Security function, reachable both by walking through the floors and straight from the home page. The VIEW button next to the camera opens a popup with the live video stream.

Delégo mobile app19.4.1

In the app for iOS and Android, selecting a camera shows its stream full screen; closing that window returns to the page the camera was opened from.

No third-party app has to be installed to watch the streams.

Web browser19.4.2

From a browser only (M)JPG streams can be watched: selecting the camera opens a popup in the middle of the screen with the stream inside it.

An RTSP stream, as explained above, is only watchable with the camera proxy enabled, because the browser cannot play RTSP on its own.

Connections20

Introduction20.1

Since release 2.6.0 the relations between widgets and objects can be established with a visual editor, by creating one or more connections.

A connection is a visual representation of the relationships between the objects of the project: a relationship makes something happen automatically on one object (the destination) when the state of another one (the source) changes.

Unlike the Logics, described in the chapter of the same name, these relationships are not running permanently in the background of the webserver: they come into play only on the event, when one of the objects involved receives a new state or an incoming telegram from its field technology.

Creating a new connection20.2

In the administration view navigate to the section

Automations → Connections

The connections of the project are listed in the lower part of the tree on the left, under the Connections folder. Hovering over that folder brings up its action icons: Add creates a new connection, which appears in the folder ready to be named. Selecting it opens an empty editor like the one in the following figure.