-
-
Notifications
You must be signed in to change notification settings - Fork 351
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added more variables from the CyberPower MIB #1982
Conversation
Thanks! Can you please check against docs/nut-names.txt for standard naming to common concepts (and bring up on nut-upsdev mailing list if more need to be introduced)? The |
Hi, somehow the question in mailing list did not gain traction, however your idea there about putting these status values (overheat, HW fault) into alarms/alerts instead sounds interesting. While https://github.com/networkupstools/nut/blob/master/docs/new-drivers.txt#L223-L239 defines quite a lot of The next chapter there about UPS Alarms having a less pre-defined vocabulary, and particularly the example in Line 128 in 3a11558
OVERHEAT as a sample ups.alarm value), suggest that this is a better route to follow.
|
I've moved the |
Signed-off-by: Jim Klimov <[email protected]>
Signed-off-by: Jim Klimov <[email protected]>
Thanks, looks reasonable. I refreshed some maintenance cosmetics, waiting for CI give its verdict just in case... :) |
…#1982] Signed-off-by: Jim Klimov <[email protected]> Signed-off-by: Alex W Baulé <[email protected]>
Added some more fields from the CyberPower MIB (v2.11) including:
ups.id
ups.status
(adding hardware status fromCPS-MIB::upsStatus.0
)ups.temperature
battery.date
input.transfer.reason
ups.test.date
ups.test.result
MAINTAINER NOTE: See also #686 with previous large data point changes