Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Azeti Site Controller is azetiĀ“s response to the need of monitoring and communicating directly with devices and sensors at the edge of infrastructures. We bring the capability of interacting with sensors and devices, executing actions and programming complex rules that will be executed even if the cloud connectivity is lost. It allows a seamless integration of sensors and devices with cloud services. The current document gives an overview of the internals of the Site Controller. It will give you a general description of the architecture of the system, its modules, and how every part of the system interacts with the other. It concentrates in describing the architecture and flow of information inside the Site Controller.

In this section we will go over the installation of the Site Controller on different operating systems and the Quick Start guide, which covers the basic setup to enable the Site Controller to communicate with the Engine. Additionally there is an overview of the architecture and the terminology used.


Link to Installation guides.

Link to Quick Start guide.

titleOn this page:

Table of Contents

Related pages:

  • Content by Label
    cqllabel in ("sitecontroller","installation")

Basic architecture

The following diagram shows a basic description of the architecture inside the Site Controller.The complete architecture is built around a MQTT broker that is used as messaging system among the modules. All modules are connected to the broker, where they get configuration and data and deliver their information. Data acquisition modules are connecting to external devices (see picture below) and publishing the information they gather to the broker in order to be processed by the rest of the modules. There is also a module responsible for the communication with the cloud.