⚡ Reduxi Configurator · User manual
Audit log
See who changed what on the controller and when — logins, settings, devices, strategies and system events.
📋 In this article
→ Overview
The Audit log lists every action that changed the controller's configuration or state: logins and logouts, changes to devices, strategies, prices, users and settings, software updates, reboots and every start of the controller software. For each entry you see who did it, from where, and the values before and after the change.
Entries cannot be edited or deleted from the Configurator or by the controller itself. Use the log to answer questions such as "who switched this strategy off?" or "when was the export limit changed?".
1 Find an entry
1
Open the log
In the left menu, click Settings, System, Diagnostics, then Audit log.
2
Set the period
Click the date range at the top right and pick the start and end. By default the log shows the last 7 days up to the end of today. Your choice is remembered in this browser.
3
Narrow the list
Type in the Filter field below Username, Action type or Subject, or use Search (see below).
4
Open the details
Click the eye icon in the Details column. A dialog shows the full entry, including what changed.
Settings → System → Diagnostics → Audit log with the search field, date range and a list of logins, device creations and controller start-ups
2 Parameters
Search and period
| Parameter | What it does | Unit / default |
|---|---|---|
| Search | Free-text search. Without Search all fields it searches only the recorded change data (the Payload shown in Details), for example a device name or a value. | text |
| Search all fields | Extends Search to username, IP address, user type, time zone, action type, subject and time. | off |
| Date range | Period shown. The controller loads at most 500 entries for the period; if there are more, a red bar Showing … of … rows. Select a shorter time range to see all results. appears. | default last 7 days |
Table
| Parameter | What it does | Unit / default |
|---|---|---|
| Time | When the action happened, in the controller's time zone. Click the header to sort; newest first by default. | date and time |
| Username | Who did it: a local Configurator user (for example admin); system for actions of the controller itself; or a cloud user (name and e-mail) or cloud for actions made through the Reduxi Cloud. Filter field below the header. |
— |
| Action type | What was done, see the table below. Filter field below the header. | — |
| Subject | What the action was done to, as KIND: name, for example DEVICE: Etrel Inch or USER: admin. Filter field below the header. |
— |
| Details | Eye icon: opens the Details dialog. | — |
| Rows per page, page, Prev, Next | Paging of the list. | 20 rows |
Details dialog
Audit log Details dialog for a USER_LOGIN entry with time, username, IP, user type LOCAL, time zone, action type, subject and payload
| Parameter | What it does | Unit / default |
|---|---|---|
| Time, Username | As in the table. | — |
| IP | Address the action came from: the browser's address for local users, the cloud user's address for cloud actions, empty for system actions. | — |
| User type | LOCAL = local Configurator user, CLOUD = through the Reduxi Cloud, SYSTEM = the controller itself. | — |
| Timezone | Controller time zone when the entry was written. | — |
| Action type | As in the table. | — |
| Subject | Kind, internal ID and name, for example DEVICE #4 (Etrel Inch). |
— |
| Payload | The recorded data. For changes it holds before and after with only the values that changed. Passwords, keys, tokens, certificates, license data and device configuration blocks are replaced by [REDACTED]. |
JSON |
3 Action types
| Area | Action type | Recorded when |
|---|---|---|
| Users |
USER_LOGIN, USER_LOGOUT
|
A user logs in or out. |
USER_CREATE, USER_EDIT, USER_DELETE
|
A user is added, changed (including password) or deleted. | |
USER_TOTP_ENABLE, USER_TOTP_DISABLE
|
Two-factor login is switched on or off for a user. | |
LOCAL_AUTH_TOKEN_CREATE |
The Reduxi Cloud creates a login for remote access to the Configurator. | |
| Devices |
DEVICE_CREATE, DEVICE_EDIT, DEVICE_DELETE
|
A device is added, its settings are saved, or it is deleted. |
DEVICE_SETPOINT_SET |
A manual setpoint is sent to a device. | |
DEVICE_PARAMETER_SET |
A device parameter is changed, for example the control type. | |
DEVICE_EMULATION_SET, DEVICE_EMULATION_DELETE
|
Meter emulation for a device is set or removed. | |
| Strategies |
STRATEGY_CREATE, STRATEGY_EDIT, STRATEGY_DELETE
|
A strategy is added, saved (details, optimization modes) or deleted. |
STRATEGY_SET_ACTIVE |
A strategy is switched on or off. | |
STRATEGY_PARAMETER_SET |
A strategy parameter is changed. | |
STRATEGY_ITEM_CREATE, STRATEGY_ITEM_SET_ALL
|
Included items of a strategy are added or saved. | |
STRATEGY_AI_SCHEDULE_CREATE, STRATEGY_AI_SCHEDULE_EDIT, STRATEGY_AI_SCHEDULE_DELETE
|
An AI energy manager schedule entry is added, changed or deleted. | |
| Settings | SETTINGS_EDIT |
Settings → Grid is saved. |
NETWORK_EDIT |
Network settings are saved. | |
CONNECTOR_EDIT |
The Cloud, MQTT v3 or Flex connector or Open VPN is saved or cleared. | |
DSO_EDIT |
Grid operator (DSO) settings are changed. | |
GATEWAY_CREATE, GATEWAY_EDIT, GATEWAY_DELETE
|
A Reduxi gateway is added, changed or deleted. | |
PRICE_CREATE, PRICE_EDIT, PRICE_DELETE
|
A utility rate plan entry is added, changed or deleted. | |
TIME_SET, TIMEZONE_SET, TIME_DATETIME_SET
|
Time settings, the time zone or the date and time are set. | |
LOCATION_GPS_SET |
The GPS location is set from the cloud. | |
SUPPORT_EDIT |
Remote support access is switched on or off. | |
LICENSE_CREATE, LICENSE_DELETE
|
A license is added or removed. | |
CONFIG_BACKUP, CONFIG_RESTORE
|
A configuration backup is downloaded or restored. | |
| Controller | CONTROLLER_STARTUP |
The controller software starts (after a reboot, an update or a restart). |
CONTROLLER_REBOOT |
A reboot is started from the Configurator. | |
CONTROLLER_FACTORY_RESET |
A factory reset is started. | |
CONTROLLER_UPDATE_INITIATED |
A software update is started, from the cloud or from a file. | |
CONTROLLER_UPDATE_SETTINGS_EDIT |
Auto update settings are changed. |
What is not in the audit log
Regulation by strategies, values written by the Modbus slave connector, and commands received over MQTT are not recorded here. The Modbus and EEBUS connector pages also write no entry when saved. Use the strategy and device Archive tabs to see what the controller did.
4 Keeping the log
- The controller never deletes audit log entries.
- While the cloud connection is up, new entries are copied to the Reduxi Cloud every 15 minutes, so they survive the loss of the controller.
- A factory reset erases the controller's data, including the local audit log.
Before a factory reset
If you need the audit log for an investigation, read or export the relevant entries, or make sure the cloud connection was up long enough for them to be copied, before you start a factory reset.
5 Checklist
- The date range covers the period you are looking for, and no red "Showing … of …" bar hides entries.
- Column filters and Search are cleared when you expect to see everything.
- Details was opened to see the exact before and after values.
- The cloud connection is on if the log must be kept outside the controller.