Multi-site

The Multi-site function allows multiple Thinknx servers installed in different locations to be managed through a single centralized project.

This function is designed for distributed installations, such as retail chains, shopping centers, corporate offices, separate buildings, or configurations consisting of multiple local servers. Each site retains its own Thinknx server, while a main server supervises and controls the various secondary servers.

The main project can be used to create a centralized supervision interface, import graphical objects from secondary projects, copy pages, and configure shared commands, controls, and schedules.

The Multi-site function is recommended when multiple separate Thinknx sites need to be supervised from a single control point.

Typical applications include:

• retail chains with multiple stores;
• shopping centers with separate areas or buildings;
• distributed corporate offices;
• installations consisting of multiple independent Thinknx servers;
• centralized supervision of remote facilities.

Each site retains its own secondary project and secondary server, while the main project collects the most important information and allows the required elements to be controlled from a single interface.

The Multi-site system is based on a structure consisting of:

• one main server, used for centralized supervision;
• one or more secondary servers, installed at the different sites;
• secondary projects exported in Multi-site format with the .site extension;
• graphical objects linked to the subprojects and used within the centralized supervision interface.

The main project contains references to the imported sites. From this project, it is possible to display, organize, and control objects belonging to the secondary servers.

Before configuring a Multi-site system, make sure that:

• each site has a correctly configured Thinknx secondary server;
• the secondary projects are complete and operational;
• the main project is intended for the main server that will manage centralized supervision;
• the secondary servers can be reached through the local network, a public IP address, or a cloud connection, depending on the required configuration;
• the secondary projects have been exported in the dedicated .site format.

The .site file must be generated from the secondary project and then imported into the main project.

To use the Multi-site function, the dedicated object must be added in the Configurator.

In the Configurator, click Add and select:

System > Report & gateway > Multi-site

Once added, the object is displayed in the project tree under System > Report & gateway.

The secondary projects must be exported in a dedicated format before they can be used in the main project.

To export a secondary project in Multi-site format:

• open the secondary project;
• click Export in the toolbar;
• select Export multi-site;
• save the generated file.

The exported file uses the following extension:

.site

This .site file contains the information required to import the secondary project into the main project.

After exporting the secondary projects in .site format, they can be imported into the main project.

In the Multi-site object, open the Thinknx site management window and add the required sites.

The configuration window can be used to add, clone, remove, and reorder the imported sites.

Once a site has been imported, its main properties are displayed, including:

Once the sites have been imported into the main project, the graphical elements of the secondary projects can be used.

An arrow next to the Paste command opens the site import menu.

From this menu, select:

Import from site

This function opens a window containing the objects available in the imported site.

This window can be used to copy pages, functions, and graphical objects from the subprojects into the main project.

The imported objects can then be used to create a centralized supervision interface while retaining their references to the secondary servers.

In addition to using the Import from site command, a graphical object can be manually linked to a subproject.

To do this, select the required graphical object and set the following property:

Bus type > Subproject

Then, in the Site field, select the secondary project from which the object must receive information or to which it must send commands.

The graphical object in the main project is now linked to an element belonging to one of the imported sites.

This method is useful when creating a customized centralized supervision interface and manually selecting which objects must be linked to the various subprojects.

The main project can contain pages dedicated to the overall supervision of the entire Multi-site system.

These pages can be used to:

• display the status of objects belonging to the different secondary servers;
• send commands to devices in the subprojects;
• create shared summary pages;
• manage centralized schedules;
• organize centralized controls for multiple sites;
• create a map or general overview of the entire installation.

This configuration keeps the individual secondary projects separate while allowing them to be controlled from a single supervision point.

The recommended workflow for configuring a Multi-site system is:

• configure the secondary project for each site;
• export each secondary project using Export > Export multi-site;
• create or open the main project;
• add the Multi-site object;
• import the .site files of the secondary projects;
• copy pages or objects using Import from site;
• alternatively, link objects manually using Bus type > Subproject;
• create the centralized supervision pages;
• send the main project to the main server.

When a secondary project is modified, it must be exported again in .site format, and the corresponding site must be updated in the main project.

This allows the main project to use the latest version of the objects, pages, and references belonging to the subproject.

It is recommended to use clear and consistent names for exported .site files, so that the site and project version can be easily identified.

The secondary projects must be exported in .site format before they can be used with the Multi-site function.

The main server does not replace the secondary servers. It communicates with them to provide centralized management. Each secondary server continues to manage its own site, while the main project allows multiple sites to be supervised and controlled from a single interface.

The Multi-site function is particularly useful for distributed installations where local control of individual sites must be maintained together with centralized supervision.