Remove ozone
state attribute and ozone
sensors from Accuweather
#91492
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.
Breaking change
The
ozone
sensors and theozone
state attribute of the weather entity showed incorrect values and are being removed. If you use these values in your automations, you need to update them.Proposed change
Due to my misinterpretation of the Accuweather API documentation, the ozone values of the sensors and the weather entity attribute show incorrect values - these are numeric values describing air quality (air quality index), not the concentration of ozone in the air. For this reason, I completely remove the ozone sensors and the ozone weather entity attribute. In the next step, I will add an air quality sensor.
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
.To help with the load of incoming pull requests: