Home
Shop
Docs
Connect
Contact
User interface
The IOZER basic user interface is opened in a web browser and is used for commissioning, configuration, diagnostics, and programming. It is designed for local operation: after opening the device's IP address, the dashboard, programming, settings, updates, and diagnostic functions are available directly in the browser.
Interface layout
The interface is divided into three areas:
- Left sidebar: main navigation for Dashboard, Program, Settings, Update, Log, and Functions.
- Header: device and program status, language, help, and the signed-in user.
- Workspace: content of the selected menu item, such as the dashboard, settings, or programming view.
The current device or program state is shown in the upper-left status area. An active program is shown in green. States such as setup mode, stopped programs, or faults are also indicated by the RGB status LED on the device.
Menu items
| Menu item | Purpose |
|---|---|
| Dashboard | Overview of the device, program, network, interfaces, and datapoints. This is the central starting point for commissioning and diagnostics. |
| Program | Creation and editing of local automation. Events, Blockly logic, and JavaScript programs are managed here. |
| Settings | Configuration of the network, interfaces, protocols, time base, and system parameters. |
| Update | Management of firmware updates. |
| Log | Display of system and event messages for troubleshooting, commissioning, and service. |
| Functions | Device functions for service and maintenance, such as restarting the device or creating a backup. |
Additional menu items may be visible depending on the firmware version, license, or development status.
Dashboard
The dashboard summarizes the most important operating data. Typical information includes the serial number, device model, hardware and firmware version, system time, uptime, memory status, and CPU load.
It also shows the state of the active program, datapoint status, and key network and interface information. For integrators, this page is especially useful for quickly checking whether the device is reachable, the program is running, and connected interfaces such as 1-Wire, Modbus, or MQTT are operating correctly.
Program
The Program section is used to create and manage local IOZER basic logic. Programming is event-based: an event triggers an action that can be defined using Blockly or JavaScript.
Typical tasks in this section include:
- Creating events for inputs, datapoints, schedules, or system states
- Creating and testing Blockly logic
- Editing JavaScript code
- Saving, applying, and running programs
- Checking program status
The underlying concepts are described under Programming.
Settings
The device's operating parameters are configured under Settings. Depending on the firmware version, these include the network, interfaces, communication protocols, time base, user access, and device-specific system options.
The following items are especially relevant during commissioning:
- IP configuration and connection method
- MQTT and Modbus communication
- 1-Wire and RS485 interfaces
- Time, time zone, and NTP
- Device security and credentials
Update
The Update menu item is used to update the firmware. Before starting an update, ensure that the power supply is stable and that the current settings have been documented or backed up.
Do not disconnect power during the update. Once the update is complete, the device normally restarts and the new firmware version is shown on the dashboard.
Log
The log displays system messages, events, and runtime notices. It helps with troubleshooting when a program does not start as expected, an interface is not connected, or an external service cannot be reached.
For service and commissioning, the log is the first place to check when the dashboard or status LED indicates a fault.
Functions
The Functions section contains device-specific tools and actions for commissioning, diagnostics, or maintenance.
Available functions may vary depending on the firmware version, for example restart or backup actions. Only perform critical actions when their effect on the system is understood.
