Add suggested precision for Airthings BLE integration #134985
+7
−0
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
Proposed change
Sometimes, certain sensors on Airthings devices return values with many decimal places. This PR introduces a
suggested_display_precision
attribute for most entities, either 1 or 2 decimal. Some entities have text-based (e.g. radon short/long term averages).This update is necessary to prepare for the inclusion of newer devices, which may provide values with even more decimal places. Support for these devices will be added in a separate PR.
From a Wave Mini:
From a Wave Enhance (not supported yet). As shown, the pressure entity can display a significant number of decimal places:
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: