Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
sys_arch [2019/07/12 18:08] – wikiadmin | sys_arch [2023/05/18 07:34] – [System Architecture] ingrid | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | |||
====== System Architecture ====== | ====== System Architecture ====== | ||
- | < | ||
- | * [[#introduction| Introduction]] | + | * [[#introductionsystem_components|Introduction: System Components]] |
- | * [[#thinknx_solution_components| Thinknx | + | * [[#thinknx_servers| Thinknx |
- | * [[#Thinknx_servers| Thinknx Servers]] | + | * [[#pro_line| Pro Line]] |
- | * [[# | + | |
- | * [[# | + | |
- | * [[# | + | * [[# |
- | * [[#communication_between_components| Communication Between Components]] | + | * [[# |
+ | * [[#server_-_client_connection| Server - Client Connection]] | ||
+ | * [[# | ||
- | ===== Introduction ===== | + | ===== Introduction: System Components |
+ | |||
+ | ThinKnx is a supervision system for home and building automation based on client-server architecture. | ||
+ | |||
+ | The **[[# | ||
+ | The **[[# | ||
+ | The **[[# | ||
+ | The **[[# | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | <WRAP center 60%> <WRAP centeralign> | ||
+ | |||
+ | The picture above shows a standard installation of ThinKnx system in a KNX or Modbus plant. The ThinKnx server interfaces with KNX plant through its dedicated **bus connector**. It is also possible to interface with Modbus or other buses through **RS232** or **TCP**. Additional systems can be integrated with server through RS232 or TCP. For example, anti-theft systems, audio or video matrix, home theater systems, etc. The ThinKnx server controls all the devices connected to it and, working as a gateway, allows interactions between the connected devices even if they are using different technologies. The clients, on the other hand, send their commands to the server which forwards them to the remaining devices allowing the communication between both parties. | ||
+ | |||
+ | The Gateway feature inside the server allows to control and integrate different devices and systems: | ||
+ | |||
+ | * For example, Sonos Player or IR transmitter can be controlled from KNX keypads by simply configuring server logic. | ||
+ | * Anti-theft system can also send telegrams on KNX or launch scenes on particular events. | ||
+ | * When an intercom door station makes a call to a Thinknx client, the server can perform actions on other devices or KNX. | ||
- | ThinKnx is a supervision system for home and building automation based on | ||
- | client-server architecture. | ||
- | * The **[[# | ||
- | * The **[[# | ||
- | * The **[[# | ||
- | * The **[[# | ||
- | \\ | ||
- | <WRAP Group> | ||
- | <WRAP column half> | ||
- | {{ : | ||
- | <WRAP center 60%> <WRAP centeralign> | ||
- | </ | ||
- | <WRAP column half> | ||
- | \\ | ||
- | The picture to the left shows a standard installation of ThinKnx system in a KNX or | ||
- | Modbus plant. | ||
- | \\ The ThinKnx server interfaces with KNX plant through its | ||
- | dedicated **bus connector**. It is also possible to interface with Modbus or other | ||
- | buses through **RS232** or **TCP**. Additional systems can be integrated with server through RS232 or TCP. For example, anti-theft systems, | ||
- | audio or video matrix, home theater systems, etc. | ||
- | \\ The ThinKnx server | ||
- | controls all the devices connected to it and, working as a gateway, allows | ||
- | interactions between the connected devices even if they are using different | ||
- | technologies. The clients, on the other hand, send their commands to the server which forwards them to the remaining devices allowing the communication between both parties. | ||
- | \\ | ||
- | \\ The Gateway feature inside the server allows to control and integrate | ||
- | different devices and systems: | ||
- | * //For example, Sonos Player or IR transmitter can be controlled from KNX keypads by simply configuring server logic.// | ||
- | * // | ||
- | * //When an intercom door station makes a call to a Thinknx client, the server can perform actions on other devices or KNX.// | ||
With a powerful tool such as the Thinknx server, the possibilities are endless. | With a powerful tool such as the Thinknx server, the possibilities are endless. | ||
+ | |||
+ | ===== ThinKnx Servers ===== | ||
+ | |||
+ | During normal runtime, ThinKnx server is the logical unit of the supervision system and communicates directly with the ThinKnx clients. The ThinKnx servers range was born to cover all the possible installation cases of a supervision system. | ||
+ | The products are divided into two lines based on the project requirement: | ||
+ | |||
+ | ==== Pro Line ==== | ||
+ | |||
+ | The **Pro Line** includes a professional range of servers able to interact with complex systems. These servers can interface directly with the KNX plant and have several communication ports to connect to the Ethernet and to other buses (like Modbus etc.) or to other devices like anti-theft systems (through RS232 or TCP/IP). They are also accurately designed for 24/7 operation and optimized for high reliability. In addition to the basic functions that are included on every server model, more functionalities can be activated by means of licenses. | ||
+ | <WRAP tip center round 80%> When using a Pro Line server, the end-user can benefit from a highly customizable interface through the Thinknx UP application, | ||
+ | |||
+ | The models included in the Pro Line are listed below: | ||
+ | |||
+ | * [[# | ||
+ | * [[# | ||
+ | * [[# | ||
+ | * [[# | ||
+ | * [[# | ||
+ | * [[# | ||
+ | |||
+ | === ThinKnx Micro_20 / Micro_DIN === | ||
+ | |||
+ | This very small device has the ability to completely control KNX systems. Can be enhanced with VoIP function for intercom communication or with Z-wave dongle for wireless integration. | ||
+ | <WRAP group> <WRAP column half> | ||
+ | |||
+ | * Fanless processing device optimized for continuous operation | ||
+ | * Mass memory on MicroSD | ||
+ | * Power: 9-24 VDC - 1A Max | ||
+ | * 1x EIB/KNX port with direct connection through clips | ||
+ | * 1x network port | ||
+ | * 1x USB port (for Z-wave dongle) | ||
+ | * KNX telegrams led | ||
+ | * Consumption 1 Watt | ||
+ | |||
+ | </ | ||
+ | <WRAP column half> {{ : | ||
+ | For more information about the Micro_20/ | ||
+ | |||
+ | === ThinKnx Compact_20 / Compact_DIN === | ||
+ | |||
+ | A completely re-engineered version of the Compact, the Compact_20 and Compact_DIN offer an extended set of I/O's and two serial ports, in addition to a small monitor allowing the integrator to easily control the inputs and outputs. This server is the perfect fit for all types of projects, and can be upgraded with all available licenses such as Z-Wave, Lutron, Modbus, Intercom, Security and more. | ||
+ | |||
+ | <WRAP GROUP> <WRAP column half> | ||
+ | |||
+ | * Fanless processing device optimized for continuous operation | ||
+ | * Power: 9-24 VDC - 1A Max | ||
+ | * Memory on chip eMMC | ||
+ | * 1x EIB/KNX port with direct connection through clips | ||
+ | * 1x network port | ||
+ | * 1x RS-232 and 1x RS-485 serial ports | ||
+ | * 2x USB ports | ||
+ | * 4x Output relays (6A) | ||
+ | * 3x digital outputs open collector | ||
+ | * 4x Analog/ | ||
+ | * 2x Digital inputs | ||
+ | * 1x Display | ||
+ | |||
+ | </ | ||
+ | <WRAP column half> {{ : | ||
+ | |||
+ | For more information about the Compact_20/ | ||
+ | |||
+ | === ThinKnx Envision7_20 === | ||
+ | |||
+ | All-in-one Touch Server which allows control of the home or building using a high resolution touch screen. <WRAP GROUP> <WRAP column half> | ||
+ | |||
+ | * Octa-core Cortex A53 CPU | ||
+ | * Capacitive touch screen | ||
+ | * 7” screen 155×87 mm visible area, 1024×600 resolution | ||
+ | * Linux embedded operating system | ||
+ | * Power: 12-24 VDC - 1.5A Max | ||
+ | * 1x EIB/KNX port with direct connection through clips | ||
+ | * Consumption: | ||
+ | * 1x network port | ||
+ | * 1x RS-232 and 1 RS-485 serial ports | ||
+ | * Sensors: 1x temperature sensor, 1x humidity sensor, 1x ambient luminosity sensor | ||
+ | |||
+ | </ | ||
+ | <WRAP column half> {{ : | ||
+ | |||
+ | For more information about the Envision, visit [[https:// | ||
+ | === ThinKnx Envision7R_20 (Retrofit) === | ||
+ | |||
+ | All-in-one Touch Server which allows control of the home or building using a high resolution touch screen. | ||
+ | <WRAP GROUP> <WRAP column half> | ||
+ | * Octa-core Cortex A53 CPU | ||
+ | * Capacitive touch screen | ||
+ | * 7” screen 155×87 mm visible area, 1024×600 resolution | ||
+ | * Linux embedded operating system | ||
+ | * Power: 12-24 VDC - 1.5A Max | ||
+ | * 1x EIB/KNX port with direct connection through clips | ||
+ | * Consumption: | ||
+ | * 1x network port | ||
+ | * 1x RS-232 and 1 RS-485 serial ports | ||
+ | * Sensors: 1x temperature sensor, 1x humidity sensor, 1x ambient luminosity sensor | ||
+ | |||
+ | </ | ||
+ | <WRAP column half> {{ : | ||
</ | </ | ||
- | </WRAP> | + | For more information about the Envision, visit [[https:// |
+ | === ThinKnx Envision10_20 === | ||
+ | All-in-one Touch Server which allows control of the home or building using a high resolution touch screen. | ||
+ | <WRAP GROUP> <WRAP column half> | ||
+ | * Octa-core Cortex A53 CPU | ||
+ | * Capacitive touch screen | ||
+ | * 10” screen 217×136 mm visible area, 1280×800 resolution | ||
+ | * Linux embedded operating system | ||
+ | * Power: 12-24 VDC - 1.5A Max | ||
+ | * 1x EIB/KNX port with direct connection through clips | ||
+ | * Consumption: | ||
+ | * 1x network port | ||
+ | * 1x RS-232 and 1 RS-485 serial ports | ||
+ | * Sensors: 1x temperature sensor, 1x humidity sensor, 1x ambient luminosity sensor | ||
- | ===== ThinKnx Solution Components ===== | + | </ |
- | ==== ThinKnx Servers ==== | + | <WRAP column half> {{ :envision.png? |
- | During normal runtime, ThinKnx server is the logical unit of the supervision system and communicates directly with the ThinKnx clients. | + | For more information about the Envision, visit [[https:// |
- | \\ | + | |
- | The ThinKnx servers range was born to cover all the possible installation cases of a supervision system. All the devices are able to interface directly with the KNX plant and have several communication ports to connect to the Ethernet and to other buses (like Modbus etc.) or to other devices like anti-theft systems (through RS232 or TCP/IP). They are also accurately designed for 24/7 operation and optimized for high reliability. In respect to the basic functions - that are included on every server model - additional facility can be activated by means of licenses. | + | |
- | * **ThinKnx Compact** It is the most versatile device of all, and supports all kind of functions (Security, VoIP, Audio/ | + | === ThinKnx Rack === |
- | * Fanless processing device optimized for continuous operation | + | |
- | * Mass memory on industrial Compact-Flash | + | |
- | * Power: 12-18 VDC - 1A Max | + | |
- | * 1x EIB/KNX port with direct connection through clips | + | |
- | * 1x network port | + | |
- | * 1x standard RS232 serial port with DE9P connector | + | |
- | * 2x USB port | + | |
- | * KNX telegrams led | + | |
- | //For more info about ThinKnx Compact server please check out the related [[http:// | + | |
- | \\ | + | |
- | * **ThinKnx Micro** It is a very small device with the ability to completely control KNX systems. Can be enhanced with VoIP function for intercom communication. | + | |
- | * Fanless processing device optimized for continuous operation | + | |
- | * Mass memory on MicroSD | + | |
- | * Power: 12-24 VDC - 1A Max | + | |
- | * 1x EIB/KNX port with direct connection through clips | + | |
- | * 1x network port | + | |
- | * KNX telegrams led | + | |
- | * Consumption 1 Watt | + | |
- | //For more info about ThinKnx Micro server please check the related [[http:// | + | |
- | \\ | + | |
- | * **ThinKnx Micro ZWave** It is a very small device with the ability to completely control KNX and Zwave systems. Can be enhanced with VoIP function for intercom communication. | + | |
- | * Fanless processing device optimized for continuous operation | + | |
- | * Mass memory on MicroSD | + | |
- | * Power: 12-24 VDC - 1A Max | + | |
- | * Z-Wave transceiver | + | |
- | * 1x EIB/KNX port with direct connection through clips | + | |
- | * 1x network port | + | |
- | * KNX telegrams led | + | |
- | * Consumption 1 Watt | + | |
- | //For more info about ThinKnx Micro ZWave server please check the related [[http:// | + | |
- | \\ | + | |
- | * **ThinKnx Envision** All-in-one Touch Server which allows control of the home or building using a high resolution touch screen. | + | |
- | * Quad-core ARM Cortex A9 CPU | + | |
- | * 1 GB DDR3 SDRAM | + | |
- | * Capacitive touch screen | + | |
- | * 7” screen 158x93mm visible area, 1024x600 resolution or 10” screen 217x136mm visible area, 1280x800 resolution | + | |
- | * Linux embedded operating system | + | |
- | * Power: 12-24 VDC - 1.5A Max | + | |
- | * 1x EIB/KNX port with direct connection through clips | + | |
- | * 1x network port | + | |
- | * Consumption: | + | |
- | //For more info about ThinKnx Envision server please check the related [[http:// | + | |
- | \\ | + | |
- | * **ThinKnx Rack** It is the most powerful and expandable device, designed for large buildings or demanding applications. | + | |
- | * Fanless processing device optimized for continuous operation | + | |
- | * Mass memory on industrial Compact-Flash | + | |
- | * External power supply 220V AC | + | |
- | * 1x EIB/KNX port with direct connection through clips | + | |
- | * 2x serial ports configurable for RS232 or RS485 | + | |
- | * 1x serial port RS232 9 pins | + | |
- | * 4x USB ports | + | |
- | * 2x Ethernet ports | + | |
- | //For more info about ThinKnx Rack server please check the related [[http:// | + | |
- | ==== ThinKnx Clients ==== | + | It is the most powerful |
- | Thinknx clients are all the devices connected to the network | + | <WRAP GROUP> <WRAP column half> |
- | ThinKnx offers a wide range of native applications to allow tablets, smartphones, | + | |
- | * **ThinKnx Player for Windows** This application allows to control the building from any Windows | + | * Fanless processing |
- | * **ThinKnx Player | + | * Mass memory |
- | <WRAP round important center 80%> ThinKnx Player for Mac is an Air application, | + | * External power supply 220V AC |
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | * 2x Ethernet ports | ||
- | | + | </ |
- | | + | For more information about the Rack, visit [[https:// |
- | * **ThinKnx for Android** This is the app for Android tablet and smartphone that coordinates the intelligent building through a Wi-Fi or 3G connection to ThinKnx servers. The interface is designed with attention to the smallest detail to adapt the graphics to the display size of the employed device. | + | |
+ | ==== Trend Line ==== | ||
+ | |||
+ | The Trend Line was designed to integrate with the KNX system and its most needed functionalities quickly and easily. It is the perfect entry level solution for residential buildings, apartments or hospitality. Certain devices in the Trend Line such as K and K2 embed stand-alone servers, allowing control of the KNX system through mobile application without the need to install a Pro Line server. Other devices such as the Piccolo operates just as smart clients and require the installation of a server (can be either Pro or Trend Line server). | ||
+ | |||
+ | <WRAP tip center round 80%>All Trend Line devices can be integrated in a plant where a Pro Line server is installed, allowing the user to to operate them as client devices.</ | ||
+ | |||
+ | The following devices are available in the Trend Line: | ||
+ | |||
+ | | ||
+ | | ||
+ | | ||
+ | |||
+ | === ThinKnx | ||
+ | |||
+ | This capacitive screen can operate as a Trend Line server or as a client in an installation where a Pro Line server is the main hub. <WRAP GROUP> <WRAP column half> | ||
+ | |||
+ | * Capacitive 4.3" touch screen | ||
+ | * Resolution 480×720 | ||
+ | * Temperature sensor | ||
+ | * Humidity sensor | ||
+ | * 1x KNX port | ||
+ | * 1x Network port | ||
+ | * 1x USB port | ||
+ | * 12-24VDC - 1A Max | ||
+ | * Standard automation control | ||
+ | * Widgets list view | ||
+ | * Unlimited KNX group addresses | ||
+ | * Unlimited clients | ||
+ | * Dedicated Trend Line application | ||
+ | * Camera monitoring | ||
+ | |||
+ | </ | ||
+ | |||
+ | === ThinKnx K2 === | ||
+ | |||
+ | This capacitive screen can operate as a Trend Line server or as a client in an installation where a Pro Line server is the main hub. <WRAP GROUP> <WRAP column half> | ||
+ | |||
+ | * Capacitive 5.5" touch screen | ||
+ | * Resolution 720×1280 | ||
+ | * Temperature sensor | ||
+ | * Humidity sensor | ||
+ | * 1x KNX port | ||
+ | * 1x Network port | ||
+ | * 12VDC - 1A Max or PoE | ||
+ | * Standard automation control | ||
+ | * Widgets list view | ||
+ | * Unlimited KNX group addresses | ||
+ | * Unlimited clients | ||
+ | * Dedicated Trend Line application | ||
+ | * Camera monitoring | ||
+ | * Doorcom functionality | ||
+ | |||
+ | </ | ||
+ | |||
+ | === ThinKnx Piccolo === | ||
+ | |||
+ | This capacitive screen operates only as a client device and requires a ThinKnx server (either Pro or Trend Line server) to control the system through a ThinKnx application. <WRAP GROUP> <WRAP column half> | ||
+ | |||
+ | * Capacitive 4" touch screen | ||
+ | * Resolution 480×480 | ||
+ | * Temperature sensor | ||
+ | * Humidity sensor | ||
+ | * 1x Network port | ||
+ | * Power 230VAC | ||
+ | * Standard automation control | ||
+ | * Widgets list view | ||
+ | * Camera monitoring | ||
+ | |||
+ | </ | ||
+ | |||
+ | ==== ThinKnx Brickbox ==== | ||
+ | |||
+ | Using the same hardware as the Pro Line, but with completely different functionalities, | ||
+ | |||
+ | ===== ThinKnx Clients ===== | ||
+ | |||
+ | Thinknx clients are all the devices connected to the network and using the Thinknx application to connect to a Thinknx server. ThinKnx offers a wide range of native applications to allow tablets, smartphones, | ||
+ | |||
+ | **Thinknx UP Player | ||
+ | |||
+ | **ThinKnx Player for Windows (Classic)** This application allows to control the building from any Windows device. Suitable even for the Windows 10 operating system, it includes settings that allows to disable the full-screen mode, resize the application window and visualize the mouse cursor, adapting the application to the device which the application is installed on and improving the user’s experience. The Classic Player only works with servers using firmware 1.1.9 or below, and can only view projects created with the Classic Configurator (with extension .erg). | ||
+ | |||
+ | **Thinknx UP Player for Mac** This application allows to control the building from any computer running Mac operating system. It offers the same functions of the Player for Windows application. | ||
+ | |||
+ | **ThinKnx Player for Mac (Classic)** This application allows to control the building from any computer running Mac operating system. It offers the same functions of the Player for Windows application. This player only works with servers using firmware 1.1.9 or below, and can only view projects created with the Classic Configurator (with extension .erg). | ||
+ | |||
+ | <WRAP round important center 80%> ThinKnx Player for Mac (Classic) is an Air application, | ||
+ | |||
+ | **Thinknx UP for iOS** This application allows to control the building from any iOS device (iPad / iPhone). It is an upgraded version of the Thinknx Pocket with a totally redesigned interface and many additional features. Thinknx UP for iOS only works with servers using firmware 1.1.10 or above, and can only view projects created with the UP Configurator (with extension .tup). | ||
+ | |||
+ | **ThinKnx for iPad (Classic)** This is the app for iPad that connects | ||
+ | **ThinKnx Pocket for iPhone | ||
+ | |||
+ | **Thinknx UP for Android** This application is used on Android tablets and smartphones to control the building automation. It is an upgraded version of the classic Thinknx for Android app with a totally redesigned interface and many additional features. It only works with servers using firmware 1.1.10 or above, and can only view projects created with the UP Configurator (with extension .tup). | ||
+ | |||
+ | **ThinKnx for Android | ||
+ | |||
+ | ===== ThinKnx Cloud ===== | ||
- | ==== ThinKnx Cloud ==== | ||
Thinknx Cloud is used for several services in the Thinknx system: | Thinknx Cloud is used for several services in the Thinknx system: | ||
- | - **Modifying and updating the project remotely on server and clients**. Using the Thinknx Configurator, | ||
- | - **Automatic client connection**. In the absence of a fixed external IP address at the automated location, it is possible to use Thinknx Cloud to allow remote access to the project for all clients. They will be able to monitor their entire house from anywhere using only the Internet at no additional cost. However, some services might not be available for this option, such as answering a SIP call remotely or viewing a local IP camera from outside the house. For more information regarding Thinknx Cloud, check out [[thinknx_cloud| this section]]. | ||
- | - **Database for live data storage**. Every project will require to save some data for continuous monitoring, chart visualization, | ||
- | - **Dynamic DNS**. This option is used in the absence of a //fixed// external IP address at the automated location. Instead, the public IP address is accessible but changes after each connection renewal or on router reboot. Thinknx offers a free dynamic DNS service configurable from the server’s web page. With this service, a host name (such as // | ||
+ | **Modifying and updating the project remotely on server and clients**. Using the Thinknx Configurator, | ||
- | {{ : | + | **Automatic client connection**. In the absence of a fixed external IP address at the automated location, it is possible to use Thinknx Cloud to allow remote access to the project for all clients. They will be able to monitor their entire house from anywhere using only the Internet at no additional cost. However, some services might not be available for this option, such as answering a SIP call remotely or viewing a local IP camera from outside the house. For more information regarding |
- | <WRAP center 60%> <WRAP centeralign> | + | |
- | ==== ThinKnx Configurator ==== | + | **Database for live data storage**. Every project will require to save some data for continuous monitoring, chart visualization, |
+ | |||
+ | **Dynamic DNS**. This option is used in the absence of a //fixed// external IP address at the automated location. Instead, the public IP address is accessible but changes after each connection renewal or on router reboot. Thinknx offers a free dynamic DNS service configurable from the server’s web page. With this service, a host name (such as // | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | ===== ThinKnx Configurator | ||
The ThinKnx Configurator software is the indispensable tool for the creation and development of a supervision project. It makes possible to create all the connections between the graphical user interface and all the devices integrated into the plant. | The ThinKnx Configurator software is the indispensable tool for the creation and development of a supervision project. It makes possible to create all the connections between the graphical user interface and all the devices integrated into the plant. | ||
Line 142: | Line 290: | ||
Finally, the same tool allows to upload the project on client devices and ThinKnx servers with differentiated exports based on the specific user. | Finally, the same tool allows to upload the project on client devices and ThinKnx servers with differentiated exports based on the specific user. | ||
- | For a detailed explanation of the Configurator, | + | For a detailed explanation of the Configurator, |
- | ===== Communication Between Components | + | ===== Server - Client Connection |
- | All the clients can connect to the server using two IP addresses, one local address to use inside the LAN and one host name or external address to use outside the LAN for remote access. | + | All the clients can connect to the server using two IP addresses, one local address to use inside the LAN and one host name or external address to use outside the LAN for remote access. It is highly recommended to configure the local IP address of the server to be fixed and not use DHCP service. Otherwise, it is possible to run into client-server connection problems when the DHCP lease expires. The fixed local address can be configured by accessing the server’s web interface using port 5051 TCP. This can be done by inputting < |
- | \\ It is highly recommended to configure the local IP address of the server to be fixed and not use DHCP service. Otherwise, it is possible to run into client-server connection problems when the DHCP lease expires. | + | |
- | \\ The fixed local address can be configured by accessing the server’s web interface using port 5051 TCP. This can be done by inputting < | + | To allow clients a remote access to the server, multiple scenarios can be considered depending on the actual situation: |
- | \\ In addition to **port 5051** TCP used for the web interface, the client-server connection is possible through **port 7550** TCP. | + | * **The existence of a static external IP address** which is directly accessible from the Internet. This option is usually sold at an additional cost by the Internet provider. In that case, the external IP address can be set inside the Configurator, |
- | \\ **Port 5050** is used to deploy a Thinknx project from Configurator to a client’s device when using the local network instead of Thinknx Cloud. | + | |
- | \\ | + | {{ : |
- | \\ To allow clients a remote access to the server, multiple scenarios can be considered depending on the actual situation: | + | <WRAP center 60%> <WRAP centeralign> |
- | * __The existence of a **static external IP address**__ which is directly accessible from the Internet. This option is usually sold at an additional cost by the Internet provider. In that case, the external IP address can be set inside the Configurator, | + | |
- | \\ {{ : | + | * **The existence of a dynamic external IP address** which is directly accessible from the Internet but changes at router reboot or after a connection renewal. In that case, and to overcome the problems tied to not having a static IP, Thinknx offers a free Dynamic DNS service configurable from the server’s web interface. With this service, a hostname will be associated to the public IP address of the router and will always be translated to the actual IP address. |
- | <WRAP center 60%> <WRAP centeralign> | + | {{ : |
- | * __The existence of a **dynamic external IP address**__ which is directly accessible from the Internet but changes at router reboot or after a connection renewal. In that case, and to overcome the problems tied to not having a static IP, Thinknx offers a free Dynamic DNS service configurable from the server’s web interface. With this service, a hostname will be associated to the public IP address of the router and will always be translated to the actual IP address. | + | |
- | \\ {{ : | + | * **The absence of a public IP address**. In that case, the IP given from the Internet provider is not directly reachable from the Internet because it is part of a sub-network or behind a NAT. By enabling and using Thinknx Cloud, remote clients can establish a connection to the server using a tunnel created by means of the Cloud. {{ : |
- | <WRAP center 60%> <WRAP centeralign> | + | |
- | * __The **absence of a public IP address**.__ In that case, the IP given from the Internet provider is not directly reachable from the Internet because it is part of a sub-network or behind a NAT. By enabling and using Thinknx Cloud, remote clients can establish a connection to the server using a tunnel created by means of the Cloud. | + | |
- | \\ {{ : | + | |
- | <WRAP center 60%> <WRAP centeralign> | + | |
===== Network requirements for Thinknx services ===== | ===== Network requirements for Thinknx services ===== | ||
Line 168: | Line 312: | ||
<WRAP center 80%>< | <WRAP center 80%>< | ||
- | ^ Service | ||
- | | NTP | 123 (TCP and UDP) \\ outbound/ | ||
- | | Thinknx cloud | cloud.thinknx.eu \\ 80, 443, 24532 (TCP) outbound | ||
- | | Thinknx projects sync | data.thinknx.eu \\ 80, 443 (TCP) outbound | ||
- | | Thinknx clients | ||
- | | Thinknx clients (cloud) | ||
- | | Internal webpage | ||
- | | Remote assistance | ||
- | </ | ||
- | Notes: | ||
- | |||
- | - This service is mandatory to sync clock with internet services. Server can act as NTP server as well (inbound connection) and it is advised to use just for local network (not exposed to the internet) | ||
- | - These services are required when cloud connection is used. | ||
- | - Port 7550 inbound is only required when direct client connection is adopted. It usually requires to create port forwarding rules on router/ | ||
- | - Access to webpages is not required and it is advised not to expose to the internet. | ||
- | - Remote assistance service used on request to obtain factory support | ||
+ | ^Service | ||
+ | |NTP |123 (TCP and UDP) \\ outbound/ | ||
+ | |Thinknx cloud |*.thinknx.eu \\ 80, 443, 24532 (TCP) outbound | ||
+ | |Thinknx projects sync | data.thinknx.eu \\ projects.thinknx.cloud \\ 80, 443 (TCP) outbound | ||
+ | |Thinknx clients | ||
+ | |Thinknx clients (cloud) | ||
+ | |Internal webpage | ||
+ | |Remote assistance | ||
+ | </ |