Add support for multiple NUT servers #5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
any update here? Would be cool to add multiple servers. |
|
any update on that ? |
Author
|
You can use this branch, and I would welcome feedback on it but there is nothing I can do about merging it into main unless @rshipp accepts the changes. |
|
I know it is about 1 year :( |
|
@AdeMiller i found a small bug when you have multiple UPS monitored and one go offline the web interface do not display anything |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New Feature
The PR adds support for multiple NUT servers. It uses a new configuration which is backwards compatible with the original single server configuration format. UPSs are now indexed by an ID, "[ups]@[server]". The UI has been updated to support a new server column in the "UPS Devices" view.
Some additional minor fixes:
_get_ups_status()battery.charge, are not set. This can happen for a dummy/heartbeat UPS, which does not pupulate all values. Use.get()with a default value "--" in these cases.