What MayaUPS tracks
MayaUPS records battery install date, nominal life, next preventive-maintenance date, and a temperature-adjusted service-life estimate. It also displays runtime remaining, load, charge, temperature, and historical trends where the monitored network-management card exposes those values through SNMP or the standard UPS MIB.
How alerts work
battery_due and pm_due alarms fire roughly 30 days ahead, giving the operator time to swap batteries before failure. Alerts are routed through the SMTP engine with grouping, return-to-normal notices, escalation, and an optional daily digest so one aging battery does not create a stream of repeated messages.
Why forecasting is different from a fault alarm
A fault alarm tells the operator that a condition is already active. Battery forecasting is earlier: it turns install date, nominal life, temperature-adjusted estimates, and maintenance timing into a planning signal. That distinction matters for sites that need to schedule replacement work, avoid surprise runtime loss, and document preventive maintenance.
How the site key fits
After a verified download, the live backend emails a site key. The user enters that key in MayaUPS to receive battery-replacement alerts. The final production flow still needs the real download URLs, checksum values, and legal identity details, so those items remain labelled as [[TODO]] elsewhere in the site.
Mixed-vendor battery visibility
The battery page belongs with multi-vendor monitoring because battery state is often reviewed across APC, Eaton, Vertiv/Liebert, CyberPower, and other standards-exposing UPS hardware. MayaUPS uses RFC-1628 data plus vendor profiles where available, which keeps replacement planning in one console instead of splitting it across brand-specific tools.