-
-
Notifications
You must be signed in to change notification settings - Fork 33.7k
Add entity categories to most NUT entities #58798
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
Conversation
Hey there @bdraco, @ollo69, mind taking a look at this pull request as it has been labeled with an integration ( |
Ok made changes. I also left an Alarm sensor and a battery status sensor that could be useful if exposed by someone's UPS. And if we are leaving output/input voltages in, a watts sensor should be left too (probably won't be available for most UPS anyway but if it is it's something they can use for energy) |
LGTM |
Breaking change
Proposed change
Adding entity categories to most NUT entities as only very few were updated initially.
I'd argue battery charge should not be diagnostic but I'm sure no one will agree 😆
Type of change
Additional information
Checklist
black --fast homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
..coveragerc
.The integration reached or maintains the following Integration Quality Scale:
To help with the load of incoming pull requests: