Skip to content
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

Add UPS Power (in Watts) to the UPS Status page #339

Closed
wants to merge 1 commit into from

Conversation

oobayly
Copy link

@oobayly oobayly commented Apr 10, 2017

As the title suggests - this adds a new row that shows how many Watts are being drawn from the UPS.
This will differ from the current UPS Load percentage, as that is calculated in VA, not Watts. I'm open to discussion whether real power (W) or apparent power should be used.

This will differ from the current UPS Load percentage, as that is
calculated in VA, not Watts
@netgate-git-updates
Copy link

Before this pull request can be accepted you must first sign a CLA as described at https://www.pfsense.org/about-pfsense/#cla. Please read for more details.

@dennypage
Copy link
Contributor

UPS power is already displayed on this page in the UPS Detail section (assuming the UPS provides it). Scroll down and you should see it.

FWIW, the reason UPS power is not in the top section is because a) it's rare compared to UPS load which is almost universal, and b) it's not used as part of the runtime calculation. The top section and the widget contain only those items pertaining to failure (quality and runtime).

@oobayly
Copy link
Author

oobayly commented Apr 10, 2017

Fair enough

@oobayly oobayly closed this Apr 10, 2017
netgate-git-updates pushed a commit that referenced this pull request Sep 19, 2020
   * Provide --version option (#372)
   * Version information now within generated certificates like on *nix
   * Fixed issue where gen-dh overwrote existing files without warning (#373)
   * Fixed issue with ED/EC certificates were still signed by RSA (#374)
   * Added support for export-p8 (#339)
   * Clarified error message (#384)
   * 2->3 upgrade now errors and prints message when vars isn't found (#377)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants