Remove invalid watts sensor from NUT #141401
Merged
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.
Proposed change
Remove the "watts" sensor since it is invalid. This appears like a breaking change, but is not actually a breaking change. NUT variables are based on RFC 9271 available at https://www.rfc-editor.org/info/rfc9271 with a complete list of num names at https://github.com/networkupstools/nut/blob/master/docs/nut-names.txt. These variables generally take the form of x.y. The variable name "watts" is not a valid variable name. The sensor is therefore invalid and cannot be used. This PR removes the sensor from sensor.py and the translation from strings.json. It is not listed in icons.json. There are no test cases that reference this invalid sensor.
This is a replacement for PR#140334 which was inadvertently closed.
Type of change
Additional information
Checklist
ruff format 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
.To help with the load of incoming pull requests: