bvandeusenandClaude Opus 5.5 f035a3b14a fix(snmp): a UPS on mains reads "On battery: No, on mains", not "0s" (#5214) ...

UPS-MIB upsSecondsOnBattery is zero whenever the UPS is on mains power, so
"On battery for 0s" read as a timer that had just started. The reading gets
its own unit, battery_seconds: zero says "No, on mains", anything else
"for <span>". The metric key stays on_battery_for, so stored history keeps.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-08 13:16:24 -04:00

..

migrations

feat(snmp): devices you add, test and read on the SNMP page (milestone 491)

2026-10-08 10:54:11 -04:00

templates/snmp

feat(snmp): devices you add, test and read on the SNMP page (milestone 491)

2026-10-08 10:54:11 -04:00

__init__.py

feat(snmp): devices you add, test and read on the SNMP page (milestone 491)

2026-10-08 10:54:11 -04:00

models.py

feat(snmp): devices you add, test and read on the SNMP page (milestone 491)

2026-10-08 10:54:11 -04:00

plugin.yaml

feat(snmp): devices you add, test and read on the SNMP page (milestone 491)

2026-10-08 10:54:11 -04:00

poller.py

feat(snmp): devices you add, test and read on the SNMP page (milestone 491)

2026-10-08 10:54:11 -04:00

readings.py

fix(snmp): a UPS on mains reads "On battery: No, on mains", not "0s" (#5214)

2026-10-08 13:16:24 -04:00

routes.py

feat(snmp): devices you add, test and read on the SNMP page (milestone 491)

2026-10-08 10:54:11 -04:00

scheduler.py

feat(snmp): devices you add, test and read on the SNMP page (milestone 491)

2026-10-08 10:54:11 -04:00

service.py

feat(snmp): devices you add, test and read on the SNMP page (milestone 491)

2026-10-08 10:54:11 -04:00