-
Notifications
You must be signed in to change notification settings - Fork 28
Sidebar Data Pages Guide
DartSteven edited this page Mar 28, 2026
·
1 revision
This guide explains the daily operational pages available from the left sidebar:
- Energy
- Power
- Battery
- Voltage
- UPS Info
- Command
- Settings
- Events
The sidebar is your operational navigation.

Correct sequence:
- choose active target in TopBar
- open page from sidebar
- interpret values in current target context
If target context is wrong, page interpretation is wrong.
Read-oriented pages:
- Energy, Power, Battery, Voltage, UPS Info, Events
Write/control pages:
- Command, Settings (
upsrw)
Operational discipline:
- monitor first, control second
- use control pages intentionally and only when required

What this page answers:
- how much energy was consumed
- cost estimate for selected period
- load behavior over time
- estimated CO2 impact
Main components:
- KPI cards (energy, cost, load, CO2)
- trend chart (time series)
- distribution bars by period slices
Documentation date reference:
2026-03-07
Clicking a trend bar opens interval details.

Use case:
- identify which hours produced the highest consumption/cost
Clicking a bar in modal 1 opens finer detail.

Use case:
- isolate short spikes and micro-patterns inside one hour

What this page answers:
- real-time power behavior and trend
- min/max vs current comparison
- possible overload or unstable draw patterns
How to read quickly:
- compare current value to recent min/max
- look for repeated spikes or long high-load plateaus
- cross-check with nominal power assumptions

What this page answers:
- current battery charge and trend
- runtime evolution
- battery voltage and related fields (if provided by UPS)
How to use operationally:
- verify runtime headroom under current load
- detect unusual oscillations in charge/runtime
- review battery indicators before maintenance windows

What this page answers:
- line/input voltage behavior
- threshold behavior
- nominal vs observed stability
Use case:
- detect line instability and transfer-risk patterns
- validate high/low transfer settings with real behavior

Purpose:
- technical inventory and identity for active UPS
Typical fields:
- manufacturer, model, serial
- firmware and driver context
- battery technical properties
- transfer and nominal settings
Use this page for:
- asset inventory
- ticket creation and diagnostics
- driver/firmware context checks

Purpose:
- execute NUT commands exposed by active UPS
Safety rule:
- commands can alter UPS behavior and may affect workload continuity
Documentation note:
- in this wiki capture, no execution button was pressed

Purpose:
- read/edit writable UPS variables
- inspect variable history in UI context
Safety rule:
- writable variables can alter behavior and thresholds
Documentation note:
- in this wiki capture, no action button was pressed

Purpose:
- event timeline and event operations
What you can do:
- inspect recent/critical event history
- filter by type/time/search
- mark events as seen
- remove selected entries when cleanup is intentional
Use this page as:
- operational audit trail
- first stop after anomalies
- confirm active target in TopBar
- check Power, Battery, Voltage for immediate health
- check Energy for cost/consumption patterns
- check Events for alarms and transitions
- open UPS Info for hardware/identity context when needed
- use Command/Settings only for explicit operations
- reading data from wrong target because topbar was not switched
- expecting control changes to apply to all targets
- treating control pages like monitoring pages
- forgetting that charts reflect selected date/time range
When something looks wrong:
- open Events to identify timeline trigger
- open Power and Voltage for source behavior
- open Battery to assess autonomy impact
- open UPS Info for hardware context
- only then decide whether Command/Settings actions are needed