Adquio controllers work internally with an architecture of devices and variables. For Adquio, any other element it connects to (other controllers, expansions, gateways, etc.) is a device, and this device has variables. This standardizes any external device that provides data to Adquio into this simple architecture.
Additionally, Adquio also has the figure of modules, which are nothing more than drivers to connect with different types of protocols or physical media. All devices that Adquio manages always have a module associated with them. Examples of modules are: BACnet IP, Modbus RTU, etc. Additionally, in these modules, you can select the associated Adquio port on which it will work.
Adquio saves all configuration data for these devices in JSON format. Therefore, every device you configure manually will eventually be saved in this format. This represents an advantage for you, since it allows you to automate the creation of new and complex devices. Additionally, it allows you to copy one device from another very easily.
Well, we are going to base ourselves on this quality to send to Adquio all the values exported in the previous chapter.
But first, let’s see how we connect to the Adquio controller and how we get to its web interface. To make the connection with the Adquio controller you have two main options, by cable or by Wi-Fi (valid for Adquio Pro, Lite, and Mini).