To fit the requirements of all platforms it is necessary to split the firmware/software in two parts:

• The IoT-device-part to aquire data from the sensors and deliver them to MQTT broker or DB servers in the web
• The web-server-part to provide configuration web pages (HTML). The user can configure IoT-device-part with a browser (FireFox, Chrome, Edge, …) by clicking web GUI

If the IoT-device is already configured no Web-server-part is necessary to run the device. The IoT-device-part can aquire data from the connected sensors and deliver them to MQTT broker or DB servers in the web via WiFi.

The IoT-device can also be used as data logger without any web access. Log files can be collected later via USB or Telnet commands.

The IoT-device-part can be configured completely with textual commands via Telnet. To send commands start a terminal program in Telnet or Raw mode and connect to the IoT-device IP address with port 10123.

For more information about commands see [Command-Wiki](../commands/Commands)

Note: Advanced Admin required!

On platforms with more resources (Raspberry Pi, PC) the web-server-part can be included. The user can connect to the IoT-device IP address with a browser (FireFox, Chrome, Edge, …) and can configure the IoT-device-part by clicking web pages.

The Web-server-part can also started on the user PC. The user can connect to the web-server at local IP address (localhost) with a browser (FireFox, Chrome, Edge, …). At first the user has to enter the IoT-device IP address in the browser and than can configure the IoT-device-part by clicking web pages.

Same as variant above but with the Web-server-part on an external server in the intranet. Technically it can be a server in the internet but is not recommented.