@frenck FYI there is a breaking change for the statistics integration which seems to be missing from the list of breaking changes in the release notes created by this PR:
home-assistant:dev ā ThomDietrich:statistics_additional_characteristics
opened 12:21AM - 18 Nov 21 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO Nā¦ OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Breaking change
Statistic characteristics are no longer available as state attributes, hence users will need to adapt their configuration by adding sensors exposing the wanted characteristics. Additional template sensors to expose attributes are not necessary anymore.
The following state attributes have been removed and are now available through the configuration parameter `state_characteristic`:
`sampling_size`, `count`, `mean`, `median`, `quantiles`, `standard_deviation`, `variance`, `total`, `min_value`, `max_value`, `min_age`, `max_age`, `change`, `average_change`, `change_rate`.
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
Adds a few new values/attributes to the statistics sensor.
Statistic characteristics are no longer available as attributes, hence users will need to adapt their configuration.
**Attributes:**
* All characteristic attributes are removed, see the breaking change section for details
* Added `age_coverage_ratio`
* Added `buffer_usage_ratio`
* Added `source_value_valid`
**Characteristics:**
* Added `average_linear`
* Added `average_step`
* Added `average_timeless`
* Added `distance_absolute`
* Added `distance_95_percent_of_values`
* Added `distance_99_percent_of_values`
* Added `noisiness`
* Renamed `average_change` to `change_sample`
* Renamed `change_rate` to `change_second`
* Renamed `max_age` to `datetime_newest`
* Renamed `min_age` to `datetime_oldest`
* Renamed `max_value` to `value_max`
* Renamed `min_value` to `value_min`
* the mathematical results of old and renamed characteristics are unchanged.
All attributes and characteristics are documented in the [docu PR](https://github.com/home-assistant/home-assistant.io/pull/20347).
**Rationale for renaming:** Some old names (like `max_age`) were ambiguous. Also, as this is a breaking change, users will need to reconfigure their `statistics` sensors, look at documentation and build a new valid setup. A better opportunity to deal with this won't come up.
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [x] New feature (which adds functionality to an existing integration)
- [x] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request: https://github.com/home-assistant/home-assistant.io/pull/20347
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [x] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] The code has been formatted using Black (`black --fast homeassistant tests`)
- [x] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [x] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [ ] Untested files have been added to `.coveragerc`.
The integration reached or maintains the following [Integration Quality Scale][quality-scale]:
<!--
The Integration Quality Scale scores an integration on the code quality
and user experience. Each level of the quality scale consists of a list
of requirements. We highly recommend getting your integration scored!
-->
- [ ] No score or internal
- [ ] š„ Silver
- [ ] š„ Gold
- [ ] š Platinum
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
[quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html
[docs-repository]: https://github.com/home-assistant/home-assistant.io
Can you add that to the list? I was really confused why my templates failing because the max_age and max_value attributes were always coming back as None after update.
3 Likes
uvjim
December 13, 2021, 6:57pm
308
I would say this item in the Release Notes is likely to point you in the right directionā¦
A revamped config menu, Z-Wave SmartStart, lovely Area cards, the button entity, local only users, and blueprint scripts.
You can always submit a PR to correct the release notes. Sometimes things get missed like when the breaking change checkbox wasnāt checked when the PR gets created.
Migaddo
December 13, 2021, 7:11pm
310
Same issue for me, in the former release we did have the flash option, currently not available anymore.
Where did āCustomize Entitiesā move to? I canāt seem to find it anywhere.
Anyone else having issues with Hue zones and rooms? After upgrading to 2021.12, I have re-enabled the zone entities. But I experience the following behaviour:
When turning on the lights that are grouped as a room or zone in the Hue app (i.e. showing as one entity in HA), sometimes there is a small delay between them turning on: one turns on slightly later than the other, instead of simultaniously.
Sometimes, not all lights in the zone are turned on, only some of them
Sometimes, the brightness of the light is not properly set
I did not experience these issues before upgrading to 2021.12. Issue seems to be still present in 2021.12.1.
123
December 13, 2021, 7:30pm
313
Signify (Philips) eliminated effects from its new API. Thatās why they no longer exist in the new Philips Hue integration (which employs the new API).
opened 12:36PM - 12 Dec 21 UTC
integration: hue
### The problem
Since the new release Hue lights won't flash with the `flash` cā¦ ommand. They will just turn on, and stay on.
The previous behaviour when using `flash` is that the light would flash a given number of times ā depending on whether `short` or `long` was passed as a parameter ā and go back to its previous state (either on or off based on the state of the light when the `flash` command was issued).
### What version of Home Assistant Core has the issue?
2021.12
### What was the last working version of Home Assistant Core?
2021.11.5
### What type of installation are you running?
Home Assistant OS
### Integration causing the issue
Philips Hue
### Link to integration documentation on our website
_No response_
### Example YAML snippet
_No response_
### Anything in the logs that might be useful for us?
_No response_
### Additional information
_No response_
FWIW, thereās an effect that makes a light ābreatheā (what you see when the Hue app identifies a light for configuration) and the developer intends to use that for a long flash (thereās nothing natively available to support a short flash).
1 Like
marcelod
December 13, 2021, 7:41pm
314
I guess if he implements it as an effect you could apply it and then switch it back to no effect quickly so it flashes fewer times. Better than trying to script the flash effect and return original state!
arganto
December 13, 2021, 7:55pm
315
Please read the release notes. Or this Thread. Or both.
2 Likes
cg089
December 13, 2021, 7:56pm
316
I have different symptoms (still no values after 20 reboots) and also opened an issue tracker meanwhile:
opened 06:17PM - 13 Dec 21 UTC
integration: vallox
### The problem
After updating to 2021.12.x (tried both 2021.12.0 and 2021.12ā¦ .1) the vallox integration isn't working anymore.
### What version of Home Assistant Core has the issue?
core-2021.12.1
### What was the last working version of Home Assistant Core?
core-2021.11
### What type of installation are you running?
Home Assistant OS
### Integration causing the issue
Vallox
### Link to integration documentation on our website
https://www.home-assistant.io/integrations/vallox/
### Example YAML snippet
```yaml
vallox:
host: 192.168.12.15
```
### Anything in the logs that might be useful for us?
```txt
Logger: homeassistant.components.fan
Source: components/vallox/fan.py:102
Integration: Ventilator (documentation, issues)
First occurred: 12:22:10 (1 occurrences)
Last logged: 12:22:10
Error while setting up vallox platform for fan
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 249, in _async_setup_platform
await asyncio.shield(task)
File "/usr/src/homeassistant/homeassistant/components/vallox/fan.py", line 77, in async_setup_platform
device = ValloxFan(
File "/usr/src/homeassistant/homeassistant/components/vallox/fan.py", line 102, in __init__
self._attr_unique_id = str(self.coordinator.data.get_uuid())
AttributeError: 'NoneType' object has no attribute 'get_uuid'
Logger: homeassistant.components.sensor
Source: components/vallox/sensor.py:55
Integration: Sensor (documentation, issues)
First occurred: 12:22:09 (1 occurrences)
Last logged: 12:22:09
Error while setting up vallox platform for sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 249, in _async_setup_platform
await asyncio.shield(task)
File "/usr/src/homeassistant/homeassistant/components/vallox/sensor.py", line 238, in async_setup_platform
[
File "/usr/src/homeassistant/homeassistant/components/vallox/sensor.py", line 239, in <listcomp>
description.sensor_type(name, coordinator, description)
File "/usr/src/homeassistant/homeassistant/components/vallox/sensor.py", line 55, in __init__
uuid = self.coordinator.data.get_uuid()
AttributeError: 'NoneType' object has no attribute 'get_uuid'
```
### Additional information
_No response_
claudegel
December 13, 2021, 7:59pm
317
Can someone tell me where to find release note concerning the following:Entity light.neviweb_light_bureau (<class 'custom_components.neviweb.light.NeviwebLight'>) implements device_state_attributes. Please report it to the custom component author.
skynet01
December 13, 2021, 8:03pm
318
I have the same issue when you toggle a group switch instead of toggling the group the info box shows up with group detail
Doh! Mist it the first time. Thanks for taking the time to redirect.
1 Like
uvjim
December 13, 2021, 8:26pm
320
petro
December 13, 2021, 8:31pm
321
can you show me what you mean āin the integrationā?
nmsousa76
December 13, 2021, 8:32pm
322
input booleans no longer work as switches in Alexa. They are now showing up as other.
claudegel
December 13, 2021, 8:41pm
323
@uvjim ,thank you very much. Now I can update my custom components
123dev
December 13, 2021, 8:43pm
324
@uvjim
petro
December 13, 2021, 8:47pm
326
Thatās a result of the failure. Did you write up an issue on github with the error from your logs?
