System Configuration

Page: Manage -> System Management

The System Management pages are reached from the top-right Manage menu by selecting "System Management". It is the area where you can set up a variety of system-wide settings.

General Settings~

Page: Manage -> System Management -> General Settings

AI Service~

There is no site-name field on this page. The name shown in the navigation bar and the browser tab is set under Manage -> System Management -> Custom UI (Brand Text); see Custom UI below for branding and colors.

Custom UI~

Page: Manage -> System Management -> Custom UI

This page customizes the branding and color palette of the web interface — useful for putting your own name and logo on AoT, or simply changing its color scheme. A live preview at the top of the page shows every color as you change it; nothing is applied elsewhere until you click Save.

Below Branding, colors are organized into groups: Brand Colors is always visible, and the rest appear as tabs. Every color has its own hex input and color picker, and clicking an element in the live preview jumps to the color that controls it.

Theme Preset switches between built-in palettes (AoT Default, Ocean Blue, Warm Sunset, Minimal Gray, Night Mode) or a palette you saved yourself with Save Preset. Reset to Defaults restores AoT's built-in colors.

Time Series Database Settings~

Page: Manage -> System Management -> General Settings

Measurements are stored in a time series database. The options currently available in AoT are InfluxDB 1.x and InfluxDB 2.x. InfluxDB 1.x works on both 32-bit and 64-bit operating systems, but 2.x only works on 64-bit operating systems. Therefore, if you are using a 32-bit operating system, you must use InfluxDB 1.x. During AoT installation, you can choose InfluxDB 1.x, 2.x, or no installation. If InfluxDB is not installed, you must specify a separate installation address and credentials so that AoT can store and retrieve measurements.

If installing with Docker, after installation you must change the host name to "aot_influxdb" in order to connect to the InfluxDB Docker container.

Dashboard Settings~

Page: Manage -> System Management -> General Settings

Upgrade Settings~

Page: Manage -> System Management -> General Settings

Energy Usage Settings~

Page: Manage -> System Management -> General Settings

To calculate accurate energy usage statistics, you need to know a few characteristics of your electrical system. These variables should describe the characteristics of the electrical system that operates electrical devices through relays.

Controller Sampling Period Settings~

Page: Manage -> System Management -> General Settings

Each controller for Inputs, Outputs, and Functions operates periodically. The fastest speed at which each controller can respond is determined by that controller's sampling period. The controller pauses its loop for the duration of the period. For example, if the Output controller's sampling period is set to 1 second, an output on/off command will react within at most 1 second.

Input Settings~

Page: Manage -> System Management -> Custom Inputs

Input modules can be imported into AoT for use. These modules must follow a specific format. For details, see Custom Inputs.

Output Settings~

Page: Manage -> System Management -> Custom Outputs

Output modules can be imported into AoT for use. These modules must follow a specific format. For details, see Custom Outputs.

Function Settings~

Page: Manage -> System Management -> Custom Functions

Function modules can be imported into AoT for use. These modules must follow a specific format. For details, see Custom Functions.

Action Settings~

Page: Manage -> System Management -> Custom Actions

Action modules can be imported into AoT for use. These modules must follow a specific format. For details, see Custom Actions.

Widget Settings~

Page: Manage -> System Management -> Custom Widgets

Widget modules can be imported into AoT for use. These modules must follow a specific format. For details, see Custom Widgets.

Measurement Settings~

Page: Manage -> System Management -> Measurements

You can create new measurements, units, and conversions to extend functionality beyond AoT's built-in types and formulas. Before creating a measurement, you must first create the unit, because you need to select a unit when creating a measurement. You can also assign additional units to a measurement that already exists. For example: altitude already exists, but if you want to add the fathom unit, first create the fathom unit, then create the altitude measurement with fathom selected.

User Settings~

Page: Manage -> System Management -> Users

At least one Admin user is required for AoT's login system to be enabled. If no Admin user exists, the web server redirects to the Admin creation form. This is the first page shown when AoT is started for the first time. After the Admin user has been created, additional users can be created on the User Settings page.

Roles~

Roles define the permissions of each user. Five default roles are provided (Admin, Editor, Monitor, Guest, and Kiosk, a display-only role that can view the camera and statistics) that determine whether a user can view or edit specific areas of AoT. In addition to the default roles, you can create custom roles.

The Edit Controllers permission protects editing of Conditionals, Graphs, LCDs, Methods, PIDs, Outputs, and Inputs. It also protects work tasks for people (weeding, inspection and the like): creating, editing or cancelling one needs this permission wherever it happens — the Scheduler, a note passage, the AI assistant or MCP, or a Google Calendar import. Roles without it can see work tasks but not change them, even if they can edit settings.

The View Stats permission protects viewing of the Usage Statistics, System Information, and Energy Usage pages.

Groups~

Page: Manage -> System Management -> Users -> Groups

Roles and Groups answer two different questions. A Role decides what a user is allowed to do (edit settings, edit controllers, view stats, and so on — see Roles above). A Group decides which dashboards, maps, facilities, and tabs (and the inputs, outputs, functions, and controllers placed on those tabs) a user is allowed to operate. The two combine: to perform an action on something, a user needs both the Role permission for that action, and membership in a Group the target has been granted to.

By default, no resource belongs to any group, so behavior is unchanged from before Groups existed: anyone whose Role allows an action can perform it on anything. This only changes once you grant a Group to a specific resource. From that point on, only members of the granted Group(s) — plus any user whose Role has "Access all groups" enabled — can operate that one resource. Everyone else immediately loses the ability to operate it, so check who currently uses a resource before granting a Group to it.

Groups restrict operating a resource only: turning a device on or off, changing its settings, deleting it, or opening its dashboard/map/facility/tab page. They do not restrict viewing. Sensor readings, history, and exported data remain visible to every logged-in user whether or not they belong to the relevant group.

The same limit applies when you ask the AI assistant or an external MCP client to change something: a change that touches another group's resource is refused, whether that resource is named, given by id, reached through a schedule or sequence step, or only mentioned in the text of a note or request. A scheduled job is checked again each time it runs, against the person responsible for it.

This page (the Groups tab under Users) is only for creating groups and choosing their members. Resources are not granted to a group here.

A Group is granted to a resource from that resource's own settings, not from this page. Each of the following carries a "Groups that can operate this ___" section in its own settings dialog:

Notes and scheduled tasks can also be attached to a zone, a site outline, a facility's own boundary, or a section inside a facility drawn on a map — not only to a tab, dashboard, map, or facility. Those shapes are not granted to a group directly; there is no "Groups that can operate this ___" section for them. Instead, a note or task attached to one follows the Facility that contains it, if it is inside one; otherwise it follows the Map it is drawn on. So restricting a Facility also restricts writing notes and tasks anywhere inside its outline, and restricting a Map restricts everything drawn on it that is not inside a Facility. This applies the same way on the notes and schedule screens as it does through the AI assistant or an MCP client.

A Facility does not inherit its Map's groups. If you restrict only the Map, notes and tasks inside its Facilities are not restricted — restrict each Facility as well.

A user can belong to more than one group. When a user's groups disagree about a resource, the widest access applies — belonging to any one group the resource is granted to is enough.

On the Roles screen, a Role can be marked "Access all groups". Users with such a Role bypass every group restriction and can operate every resource regardless of what has been granted — intended for the small number of people who manage the whole system rather than one area of it. The built-in Admin role has this enabled by default.

Raspberry Pi Settings~

Page: Manage -> System Management -> Raspberry Pi

The Raspberry Pi settings configure part of the Linux system on which AoT runs.

This page works only on a Raspberry Pi installation with raspi-config. In Docker (or on any system without raspi-config) it shows a notice instead of the settings.

pigpiod is required to use PWM outputs and PWM, RPM, DHT22, DHT11, and HTU21D inputs.

Alert Settings~

Page: Manage -> System Management -> Alerts

The Alert settings hold the SMTP account AoT uses to send email. Nothing is emailed until a Conditional function with a Send Email action (or one of the other email paths described in Alerts) runs, so configuring this page alone sends no alerts.

Click Save to store the settings.

Send a test email~

The Send Test Email section sends one message to the address you type in Test recipient. The test uses the settings that are already saved, not the values currently typed in the form, so click Save first and then send the test. A success or failure message appears at the top of the page.

Using Gmail~

Google does not accept a normal account password for SMTP. Turn on 2-step verification for the Google account, create an app password (Google Account -> Security -> App passwords), and enter that 16-character password as the SMTP password. Use smtp.gmail.com with SSL (port 465) or TLS (port 587), enter the full Gmail address as the SMTP user, and set From Email to the same address, because Gmail rewrites or rejects other sender addresses.

The hourly limit~

The limit applies to the Send Email and Send Email with Photo actions. The counter starts a one-hour window; once the number of emails in that window reaches the limit, further emails are dropped until the window ends. Dropped emails are not sent later. Each one leaves an error line in the daemon log (Wait N seconds to email again; see Log Viewer). The counter also counts attempts made while the limit was already reached.

To clear the counter and start a fresh window immediately, use Reset Email Counter on the Diagnostic page.

Camera Settings~

Page: Manage -> System Management -> Camera

AoT can use multiple cameras simultaneously. Each camera can be used throughout the software after being configured in the Camera settings.

Diagnostic Settings~

Page: Manage -> System Management -> Diagnostics

Problems can occur in the system due to incompatible configurations. These can result from a part of the system (Input, Output, etc.) being misconfigured, an update in which the database upgrade was not handled properly, or other unexpected issues. There are times when you need to perform diagnostics to identify the cause of a problem or to resolve the problem itself. The options below are intended to mitigate problems. For example, if the Data -> Dashboard page cannot be accessed because of a misconfigured dashboard element that causes an error, deleting all dashboard elements may be the most economical way to regain access. Note, however, that in this case you will have to re-add all existing dashboard elements.