mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-24 01:37:23 +00:00
Franck Nijhof
GitHub
parent
3d1d8b8d8e
commit
783ac162f8
@ -64,7 +64,7 @@ template:
|
||||
|
||||
## Trigger-based template sensors
|
||||
|
||||
If you want more control over when an entity updates, you can define a trigger. Triggers follow the same format and work exactly the same as [triggers in automations][trigger-doc]. This feature is a great way to create entities based on webhook data, or update entities based on a schedule.
|
||||
If you want more control over when an entity updates, you can define a trigger. Triggers follow the same format and work exactly the same as [triggers in automations][trigger-doc]. This feature is a great way to create entities based on webhook data ([example](#storing-webhook-information)), or update entities based on a schedule.
|
||||
|
||||
Whenever the trigger fires, all related entities will re-render and it will have access to [the trigger data](/docs/automation/templating/) in the templates.
|
||||
|
||||
|
||||
@ -1,8 +1,8 @@
|
||||
---
|
||||
layout: post
|
||||
title: "2021.5: Beta release notes"
|
||||
description: "Beta release notes for Home Assistant 2021.5"
|
||||
date: 2021-04-28 00:00:00
|
||||
title: "2021.5: Stability, performance, triggers, color modes!"
|
||||
description: "Improved database and start up handling, an updated look and feel for the integrations dashboard and color modes for lights!"
|
||||
date: 2021-05-05 00:00:00
|
||||
date_formatted: "May 5, 2021"
|
||||
author: Franck Nijhof
|
||||
author_twitter: frenck
|
||||
@ -14,38 +14,42 @@ og_image: /images/blog/2021-05/social.png
|
||||
feedback: true
|
||||
---
|
||||
|
||||
<!--<a href='/integrations/#version/2021.5'><img src='/images/blog/2021-05/social.png' style='border: 0;box-shadow: none;'></a>-->
|
||||
<a href='/integrations/#version/2021.5'><img src='/images/blog/2021-05/social.png' style='border: 0;box-shadow: none;'></a>
|
||||
|
||||
These are the beta release notes for Home Assistant Core 2021.5 (and is thus a
|
||||
work in progress).
|
||||
Here I am again, a month later. Are you used to these monthly release cycles
|
||||
yet? Hello, 2021.5! Nice to see you this May!
|
||||
|
||||
If you encounter any issues with the beta release, please report them on GitHub:
|
||||
I would say this release is a bit less feature rich compared to the previous
|
||||
release (which was epic, in my opinion!). But it is not a bad thing!
|
||||
|
||||
- Issues with integrations, automations and such (Core related):<br>
|
||||
<https://github.com/home-assistant/core/issues>
|
||||
- Issues with the frontend/Lovelace:<br>
|
||||
<https://github.com/home-assistant/frontend/issues>
|
||||
- Issues with the Supervisor:<br>
|
||||
<https://github.com/home-assistant/supervisor/issues>
|
||||
- Issues with the documentation:<br>
|
||||
<https://github.com/home-assistant/home-assistant.io/issues>
|
||||
Some really good stability improvements have been introduced this release! Not
|
||||
the hot new items you want to explore immediately, but these fundamental things
|
||||
will really help our systems now and in the future. Making this release an
|
||||
upgrade that would be a smooth sail for most of us (check the breaking changes).
|
||||
|
||||
Please be sure to include the beta version you are running in the issue
|
||||
description (not title), so we can classify your issue correctly.
|
||||
The most visual part changed this release can be found in the facelift that the
|
||||
integrations dashboard got. Oh, and the new color modes for lights is an amazing
|
||||
improvement as well!
|
||||
|
||||
Issues introduced in the beta are processed with priority.
|
||||
May... For me, that feels like the summer is slowly trying to make its
|
||||
appearance and I'm looking forward to it 🕶. Do you have a summer
|
||||
Home Automation project figured out yet?
|
||||
|
||||
This release we did an exhaustive review of the startup, shutdown, and upgrade
|
||||
processes.
|
||||
Oh, and don't forget to tune into the release party live stream later today!
|
||||
(Spoiler alert: I've heard we might have a special guest, only Paulus didn't
|
||||
want to tell me who it is...)
|
||||
|
||||
2021.5 Stream Party on YouTube: <https://www.youtube.com/watch?v=bvAKUz-bmqU>
|
||||
|
||||
../Frenck
|
||||
|
||||
- [Code Editor bug & Safari](#code-editor-bug--safari)
|
||||
- [Database upgrades & performance](#database-upgrades--performance)
|
||||
- [Startup visibility - What is taking so long?](#startup-visibility---what-is-taking-so-long)
|
||||
- [Ever wonder why Home Assistant didn’t restart when you pressed the restart button?](#ever-wonder-why-home-assistant-didnt-restart-when-you-pressed-the-restart-button)
|
||||
- [Memory Leaks](#memory-leaks)
|
||||
- [Why Home Assistant didn’t restart when I pressed the restart button?](#why-home-assistant-didnt-restart-when-i-pressed-the-restart-button)
|
||||
- [Updated look and feel for the integration dashboard](#updated-look-and-feel-for-the-integration-dashboard)
|
||||
- [Color modes!](#color-modes)
|
||||
- [Docker](#docker)
|
||||
- [Tigger-based binary template sensor](#tigger-based-binary-template-sensor)
|
||||
- [Docker images now signed and available on the GitHub Container Registry](#docker-images-now-signed-and-available-on-the-github-container-registry)
|
||||
- [Other noteworthy changes](#other-noteworthy-changes)
|
||||
- [New Integrations](#new-integrations)
|
||||
- [New Platforms](#new-platforms)
|
||||
@ -55,33 +59,23 @@ processes.
|
||||
- [Farewell to the following](#farewell-to-the-following)
|
||||
- [All changes](#all-changes)
|
||||
|
||||
## Code Editor bug & Safari
|
||||
|
||||
We are aware of bug with CodeMirror, the code editor in Home Assistant
|
||||
used for things like YAML, when using the Safari browser.
|
||||
|
||||
We currently advise not to use Safari when using the code editor in
|
||||
Home Assistant.
|
||||
|
||||
We are working with the upstream project to have this fixed during the beta.
|
||||
|
||||
## Database upgrades & performance
|
||||
|
||||
There is a database upgrade this release, but worry not as database upgrades
|
||||
There is a database upgrade in this release, but worry not as database upgrades
|
||||
now happen in the background and no longer prevent Home Assistant from starting.
|
||||
During migration, Home Assistant will prevent being restarted or stopped until
|
||||
During migration, Home Assistant will prevent being restarted or stopped until
|
||||
the migration has been completed.
|
||||
|
||||
Thanks to [@lmagyar] and [@raman325] we now can store events up to
|
||||
64 characters and the recorder won’t get stuck if there is one exceeding that
|
||||
length.
|
||||
|
||||
And if you have ever had to wait for the recorder to shutdown, worry no more
|
||||
And if you have ever had to wait for the recorder to shut down, worry no more
|
||||
as Home Assistant can now shut down successfully, even when the database is
|
||||
broken.
|
||||
|
||||
Talking about broken databases: if you have ever had database corruption of
|
||||
your sqlite database, you probably know how much of a pain it is to get things
|
||||
your SQLite database, you probably know how much of a pain it is to get things
|
||||
back up and running again. We recently added live recovery to allow
|
||||
Home Assistant to recover and start a new database when the recorder encountered
|
||||
corruption when saving events or states to the database. This release extends
|
||||
@ -93,136 +87,194 @@ frequency.
|
||||
|
||||
## Startup visibility - What is taking so long?
|
||||
|
||||
TODO:
|
||||
- Some rewording / flow fixes
|
||||
- Screenshot
|
||||
|
||||
Ever wondered why starting up Home Assistant took so long?
|
||||
|
||||
Stop wondering, as you can now see which integration is delaying startup as
|
||||
the integration taking the longest time to setup is now displayed when
|
||||
the integration taking the longest time to set up is now displayed when
|
||||
Home Assistant is starting.
|
||||
|
||||
## Ever wonder why Home Assistant didn’t restart when you pressed the restart button?
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2021-05/still-starting.png' alt='Screenshot of Home Assistant starting'>
|
||||
Screenshot of Home Assistant reporting integrations that are being set up.
|
||||
</p>
|
||||
|
||||
TODO:
|
||||
- Title...
|
||||
- Wording/flow adjustments
|
||||
And in case you missed those notifications, you can always check the
|
||||
information panel afterward.
|
||||
|
||||
The restart button now provides feedback so you know right away if a restart
|
||||
can’t happen because of invalid config, broken integration or database upgrade
|
||||
in progress.
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2021-05/setup-time.png' alt='Screenshot of information panel showing integration set up times'>
|
||||
Screenshot of information panel showing integration set up times.
|
||||
</p>
|
||||
|
||||
We adjusted timeouts and fixed a few places were shutdown would block
|
||||
This My button brings you right to it:
|
||||
|
||||
{% my info badge %}
|
||||
|
||||
## Why Home Assistant didn’t restart when I pressed the restart button?
|
||||
|
||||
So, why didn't Home Assistant restart when you press the restart button?
|
||||
This question we have seen quite a few times and was a rather annoying
|
||||
occurrence that has been improved.
|
||||
|
||||
The restart button now provides feedback! So you know right away if a restart
|
||||
can’t happen because of invalid configuration, broken integration or database
|
||||
upgrade in progress.
|
||||
|
||||
We adjusted timeouts and fixed a few places where shutdown would block
|
||||
forever, for example, when restarting Home Assistant the configuration gets
|
||||
checked and there was a case that could hang in this check forever.
|
||||
|
||||
Restarts are faster now... (WTH https://community.home-assistant.io/t/wth-stopping-service-is-too-slow/220507),
|
||||
as more parts of Home Assistant now cancel/react to the shutdown procedure
|
||||
better.
|
||||
This means restarts are faster now! As more parts of Home Assistant now
|
||||
cancel/react to the shutdown procedure better than before
|
||||
(from the Month of [What the Heck][wth]).
|
||||
|
||||
We also audited the top 35 integrations to make sure they stop polling on stop.
|
||||
Thanks for {% my general title="turning on analytics" %}!
|
||||
|
||||
## Memory Leaks
|
||||
|
||||
TODO:
|
||||
- Extend or move to other noteworthy changes
|
||||
|
||||
We did an audit of memory leaks and fixed a couple of generic cases in our core
|
||||
codebase. But also fixed over 15 cases during unload/reload in popular
|
||||
integrations.
|
||||
[wth]: https://community.home-assistant.io/t/wth-stopping-service-is-too-slow/220507
|
||||
|
||||
## Updated look and feel for the integration dashboard
|
||||
|
||||
TODO:
|
||||
|
||||
- Screenshot
|
||||
- Improve flow/writing
|
||||
|
||||
The {% my integrations title="Integrations dashboard" %} has been updated to
|
||||
have a more compacted look and provide more useful information.
|
||||
have a more compact look and provide more useful information.
|
||||
|
||||
For example, it now shows the state of the integration and in case of a
|
||||
failure, it will now tell you why that is.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2021-05/integrations-dashboard.png' alt='Screenshot of the updated integrations dashboard'>
|
||||
Screenshot of the updated integrations dashboard.
|
||||
</p>
|
||||
|
||||
Additionally, you can now recognize integrations that rely on the cloud
|
||||
(they show a little cloud label) and integration that are installed as
|
||||
(they show a little cloud label) and integrations that are installed as
|
||||
custom integration (they show a little package label).
|
||||
|
||||
## Color modes!
|
||||
|
||||
TODO:
|
||||
- Make story out of it
|
||||
- Add screenshot
|
||||
We now have support for RGBWW, RGBW and many more color modes!
|
||||
|
||||
We now have support RGBWW, RGBW and many more color modes! Previously, we
|
||||
relied mainly on HS & Brightness (HSB/HSV) and colors in Home Assistant was
|
||||
based on that. But now, an integration can provide the actual color mode an
|
||||
light supports. This allow Home Assistant (and integration to adjust the
|
||||
behavior for the light better.
|
||||
Previously, we relied mainly on HS (Hue Saturation) & Brightness (HSB/HSV)
|
||||
and colors in Home Assistant was based on that. But now, an integration can
|
||||
provide the actual color mode an light supports. This allows Home Assistant
|
||||
(and integrations) to adjust the behavior for the light better.
|
||||
|
||||
For example, the frontend will adjust the color picker based on the color mode
|
||||
of the light.
|
||||
of the light. The more info dialog for lights have been modernized to support
|
||||
this change:
|
||||
|
||||
<insert screenshot>
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2021-05/rgbww-light.png' alt='Screenshot of the updated more info dialog for lights'>
|
||||
Screenshot of the updated more info dialog for lights.
|
||||
</p>
|
||||
|
||||
At this moment not all integrations are able to support color modes yet.
|
||||
Please notes, that at this moment not all integrations are able to support color
|
||||
modes yet. However, all lights do have an nice updated UI as in the screenshot.
|
||||
|
||||
<!--<p class='img'>
|
||||
<img src='/images/blog/2021-05/automation-tracing.png' alt='Screenshot of lorem ipsum'>
|
||||
Screenshot of lorem ipsum.
|
||||
</p>-->
|
||||
## Trigger-based binary template sensor
|
||||
|
||||
## Docker
|
||||
In the [previous release][previous], we introduced a trigger-based template
|
||||
sensor. This release extends on that features by adding support for
|
||||
trigger-based binary sensors using templates.
|
||||
|
||||
We are now using both Docker and GitHub container registries. If you want use the new GHCR,
|
||||
just use `ghcr.io/home-assistant/home-assistant` instead of `homeassistant/home-assistant`.
|
||||
Trigger-based binary sensors can also be configured with an `auto_off` duration.
|
||||
This will automatically turn a binary sensor state to `off` after the specified
|
||||
duration.
|
||||
|
||||
Our core images are now also signed with [CodeNotary](https://codenotary.io) and allow to check integrity of our images.
|
||||
CodeNotary is a distributed Ledger solution using the [immudb](https://github.com/codenotary/immudb) as a database for built-in cryptographic proof and verification.
|
||||
{% raw %}
|
||||
|
||||
If you running the Supervisord or Operating-System, we check allready the integrity of our distributed content. If you running the container installation,
|
||||
you can install the [VCN](https://github.com/codenotary/vcn) or simple `bash <(curl https://getvcn.codenotary.io -L)`. Now you can use it like:
|
||||
```yaml
|
||||
template:
|
||||
- trigger:
|
||||
- platform: event
|
||||
event_type: netatmo_event
|
||||
event_data:
|
||||
type: movement
|
||||
binary_sensor:
|
||||
- name: "Motion"
|
||||
# We use auto_off, so just set it to true on each trigger
|
||||
state: "true"
|
||||
device_class: motion
|
||||
# Automatically turn off 60 seconds after the last event
|
||||
auto_off: 60
|
||||
```
|
||||
|
||||
{% endraw %}
|
||||
|
||||
Some other ideas:
|
||||
|
||||
- [Store webhook information in Home Assistant](/integrations/template/#storing-webhook-information)
|
||||
- One that updates based on a time trigger once a day
|
||||
(e.g., "Is is my birthday?" binary sensor).
|
||||
|
||||
[previous]: /blog/2021/04/07/release-20214/#trigger-based-template-sensors
|
||||
|
||||
## Docker images now signed and available on the GitHub Container Registry
|
||||
|
||||
We are now using both DockerHub and the new GitHub Container Registry.
|
||||
|
||||
If you want to use the new GitHub Container Registry, just use:
|
||||
|
||||
`ghcr.io/home-assistant/home-assistant`
|
||||
|
||||
(Instead of `homeassistant/home-assistant`)
|
||||
|
||||
Our core images are now also signed with [CodeNotary](https://codenotary.io)
|
||||
and allowing you to check the integrity of our images.
|
||||
|
||||
CodeNotary is a distributed Ledger solution using the
|
||||
[immudb](https://github.com/codenotary/immudb) as a database for built-in
|
||||
cryptographic proof and verification.
|
||||
|
||||
If you are running the Home Assistant Operating System or a Supervised
|
||||
installation type, we already check the integrity of our distributed content.
|
||||
If you running the Container installation, you can install the
|
||||
[VCN](https://github.com/codenotary/vcn) tool.
|
||||
|
||||
Now you can use it like so:
|
||||
|
||||
```sh
|
||||
docker pull ghcr.io/home-assistant/home-assistant:2021.5.0
|
||||
vcn authenticate --org home-assistant.io docker://ghcr.io/home-assistant/home-assistant:2021.5.0
|
||||
```
|
||||
|
||||
This will tell/confirm that the image you have, is actually created
|
||||
and shipped by the Home Assistant project.
|
||||
|
||||
## Other noteworthy changes
|
||||
|
||||
There is much more juice in this release; here are some of the other
|
||||
noteworthy changes this release:
|
||||
|
||||
Backend things/candidates:
|
||||
- Are you in meetings a lot? The new [mutesync][mutesync docs] integration
|
||||
shows if you're in a meeting and if you're muted in Home Assistant. This will
|
||||
unlock some cool do-not-disturb automations.
|
||||
- We did an audit of memory leaks and fixed a couple of generic cases in our
|
||||
core codebase. But also fixed over 15 cases during unload/reload in popular
|
||||
integrations.
|
||||
- The TTS service by Home Assistant Cloud now uses an improved bitrate,
|
||||
making it sound even more impressive.
|
||||
- ClimaCell now supports the v4 API. So, I've you've wanted to test it out you
|
||||
can now actually use it with the new API keys. Thanks [@raman325]!
|
||||
- If you are into templating, we now have `min()` and `max()` available
|
||||
as functions in Jinja templates.
|
||||
- The AdGuard integration now supports multiple instances thanks to [@eifinger].
|
||||
- When viewing your logs in the frontend, the log entry will tell you if
|
||||
the log was created by a custom integration.
|
||||
- If you have a Sonos Move or Sonos Roam, you can now see their battery level
|
||||
and charging state. Thanks for that [@hufman] and [@jjlawren].
|
||||
- Template covers now can have an opening and closing state, which was added by
|
||||
[@bdr99], thanks for that!
|
||||
- The ZHA integration now has configuration options in the UI, allowing you
|
||||
to set things like default transition times for your lights.
|
||||
Thanks [@dmulcahey]!
|
||||
- The Z-Wave JS integration now allows you to re-interview a device from the
|
||||
UI thanks to [@cgarwood].
|
||||
- [@cgarwood] didn't stop there, you can now opt-in for sending Z-Wave JS
|
||||
telemetry to the Z-Wave JS project to help them out. This can be turned
|
||||
on in the Z-Wave JS configuration panel.
|
||||
|
||||
- Add ClimaCell v4 API support ([@raman325] - [#47575]) ([climacell docs])
|
||||
- Add hive boost off functionality ([@KJonline] - [#48701]) ([hive docs]) (breaking-change)
|
||||
- Allow template covers to have opening and closing states ([@bdr99] - [#47925]) ([template docs])
|
||||
- Bump hass-nabucasa 0.43 ([@balloob] - [#48964]) ([cloud docs])
|
||||
- Add new attributes to Climacell ([@raman325] - [#48707]) ([climacell docs])
|
||||
- Reintroduce iAlarm integration ([@RyuzakiKK] - [#43525]) ([ialarm docs]) (new-integration)
|
||||
- Add Rituals Perfume Genie sensor platform ([@milanmeu] - [#48270]) ([rituals_perfume_genie docs]) (new-platform)
|
||||
- Live db migrations and recovery ([@bdraco] - [#49036]) ([recorder docs]) (breaking-change)
|
||||
- Support min()/max() as template function ([@frenck] - [#48996])
|
||||
- Add support for custom configurations in ZHA ([@dmulcahey] - [#48423]) ([zha docs])
|
||||
- Allow top level non-trigger template entities ([@balloob] - [#48976]) ([template docs])
|
||||
- Added Spanish US voice to Google Cloud TTS ([@soundch3z] - [#49200]) ([google_cloud docs])
|
||||
- Support all available Google Cloud TTS languages ([@hmmbob] - [#49208]) ([google_cloud docs])
|
||||
- Add binary sensor platform to Rituals Perfume Genie Integration ([@milanmeu] - [#49207]) ([rituals_perfume_genie docs]) (new-platform)
|
||||
- Add support for multiple AdGuard instances ([@eifinger] - [#49116]) ([adguard docs])
|
||||
- Add alarm control panel support to deCONZ integration ([@Kane610] - [#48736]) ([deconz docs]) (new-platform)
|
||||
- Skip recorder commit if there is nothing to do ([@bdraco] - [#49614]) ([recorder docs])
|
||||
- Add battery support for Sonos speakers ([@jjlawren] - [#49441]) ([sonos docs]) (new-platform)
|
||||
- Add Blueprint foundation to Scripts ([@frenck] - [#48621]) ([config docs]) ([script docs])
|
||||
|
||||
Frontend things/candidates:
|
||||
|
||||
- Align layout of all cards (#8931) @balloob
|
||||
- Highlight if log comes from custom component (#8912) @balloob
|
||||
- Add UI for Z-Wave JS Device Reinterview (#8957) @cgarwood
|
||||
- Add opt-in toggle for zwave-js telemetry to config panel (#8958) @cgarwood
|
||||
[@hufman]: https://github.com/hufman
|
||||
|
||||
## New Integrations
|
||||
|
||||
@ -274,7 +326,25 @@ Below is a listing of the breaking change for this release, per subject or
|
||||
integration. Click on one of those to read more about the breaking change
|
||||
for that specific item.
|
||||
|
||||
{% details "Custom integration" %}
|
||||
{% details "Container udev" %}
|
||||
|
||||
We no longer run an udev instance inside our containers. This was used by the
|
||||
Supervisor which now is using the host udev in all containers.
|
||||
|
||||
For now, we have a fallback environment variable `USING_UDEV=1` which you can
|
||||
set on your container to get the old behavior. This gives you time for using
|
||||
the Docker way to map/use devices.
|
||||
|
||||
If you run a system that uses the Supervisor, this is automatically taken
|
||||
care of.
|
||||
|
||||
([@pvizeli]- [#180])
|
||||
|
||||
[#180]: https://github.com/home-assistant/docker/pull/180
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Custom integrations" %}
|
||||
|
||||
Custom integrations now require a version key in their manifest file, this also
|
||||
means that all custom integrations now require a manifest file.
|
||||
@ -296,35 +366,75 @@ custom integration.
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Google Travel Time" %}
|
||||
{% details "Events" %}
|
||||
|
||||
The Google Travel Time integration is now configured via the UI. Configuring
|
||||
An event fired with an `event_type` of more than 64 characters would previously
|
||||
result in recorder errors but the event would otherwise work. Now, firing an
|
||||
event with more than 64 characters in the event type will raise immediately.
|
||||
|
||||
If you are using long events in your automations or scripts, you should adjust
|
||||
to this change. Custom integration authors should review their event types.
|
||||
|
||||
([@raman325] - [#48115])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "ASUSWRT" %}
|
||||
|
||||
The `device_tracker` entity state attribute `ip_address` has been changed and is
|
||||
now be named `ip`. You need to update automations and scripts that use this
|
||||
attribute.
|
||||
|
||||
([@bieniu] - [#48764])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "AVM FRITZ!Box Tools" %}
|
||||
|
||||
The AVM FRITZ!Box Tools integration is now configured via the UI. Configuring
|
||||
the integration via YAML is now deprecated. Existing YAML configuration is
|
||||
automatically imported on upgrade and can be safely removed after upgrade.
|
||||
|
||||
([@raman325] - [#43509])
|
||||
([@chemelli74] - [#48287])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Garmin Connect" %}
|
||||
{% details "AVM FRITZ!SmartHome" %}
|
||||
|
||||
The unit of measurement from Garmin Connect timestamp sensors has been removed.
|
||||
It used to be set to empty string. If you have automations, scripts or external
|
||||
data recvorder that rely on unit of measurement for these sensors, you might
|
||||
need to adjust to this change.
|
||||
YAML configuration for AVM FRITZ!SmartHome has been removed, after it has been
|
||||
deprecated for 12 months. Configuration via UI is fully integrated. Existing
|
||||
YAML configuration has already been imported automatically in the previous
|
||||
releases and can now safely be removed from your configuration files.
|
||||
|
||||
([@MartinHjelmare] - [#48431])
|
||||
([@mib1185] - [#49663])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "System Monitor" %}
|
||||
{% details "DHT Sensor" %}
|
||||
|
||||
The unit of measurement from System Monitor timestamp sensors has been removed.
|
||||
It used to be set to empty string. If you have automations, scripts or external
|
||||
data recorder that rely on unit of measurement for these sensors, you might
|
||||
need to adjust to this change.
|
||||
The `pin` configuration option is currently an integer but will need to be
|
||||
prefixed with D for Raspberry Pi platforms.
|
||||
|
||||
([@MartinHjelmare] - [#48431])
|
||||
Please adjust your YAML configuration for this change.
|
||||
|
||||
([@TheGardenMonkey] - [#41525])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "ecobee" %}
|
||||
|
||||
ecobee climate devices will change the reported temperature precision for their
|
||||
`current_temperature` attribute from whole degrees to 0.1 degree increments.
|
||||
Automations which rely on whole-number precision may need adjustments.
|
||||
|
||||
([@jjlawren] - [#48697])
|
||||
|
||||
Setting a fan hold in the ecobee integration will no longer also set a
|
||||
temperature hold. If any automations assumed that the temperature would be set
|
||||
when calling the set_fan_mode service on an ecobee device, those automations
|
||||
will need to add the appropriate `set_temperature` service call.
|
||||
|
||||
([@bjpetit] - [#48086])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
@ -342,70 +452,6 @@ can now be disabled in the UI.
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Waze Travel Time" %}
|
||||
|
||||
The Waze Travel Time integration is now configured via the UI. Configuring
|
||||
the integration via YAML is now deprecated. Existing YAML configuration is
|
||||
automatically imported on upgrade and can be safely removed after upgrade.
|
||||
|
||||
([@raman325] - [#43419])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "ASUSWRT" %}
|
||||
|
||||
The `device_tracker` entity state attribute `ip_address` has been changed and is
|
||||
now be named `ip`. You need to update automations and scripts that use this
|
||||
attribute.
|
||||
|
||||
([@bieniu] - [#48764])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details " Recollect Waste" %}
|
||||
|
||||
Recollect Waste pickup dates are now stored as UTC timestamps.
|
||||
|
||||
([@bachya] - [#48690])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "KNX" %}
|
||||
|
||||
The `config_file` YAML option for KNX was deprecated before and has now been
|
||||
removed.
|
||||
|
||||
([@marvin-w] - [#48799])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Events" %}
|
||||
|
||||
An event fired with an `event_type` of more than 64 characters would previously
|
||||
result in recorder errors but the event would otherwise work. Now, firing an
|
||||
event with more than 64 characters in the event type will raise immediately.
|
||||
|
||||
If you are using long events in your automations or scripts, you should adjust
|
||||
to this change. Custom integration authors should review their event types.
|
||||
|
||||
([@raman325] - [#48115])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Hive" %}
|
||||
|
||||
The existing Hive service `heating_boost` will be deprecated in Home Assistant
|
||||
release 2021.6 and a new service to replace it has been created called
|
||||
`heating_boost_on`.
|
||||
|
||||
If you use the `heating_boost` Hive service please update your configuration
|
||||
to the new service. A deprecation warning will be printed to the logs when the
|
||||
deprecated service is used.
|
||||
|
||||
([@KJonline] - [#48701])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Ezviz" %}
|
||||
|
||||
The Ezviz integration is now configured via the UI. Configuring
|
||||
@ -435,84 +481,13 @@ will need to adjust to this change.
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Litter-Robot" %}
|
||||
{% details "Garmin Connect" %}
|
||||
The unit of measurement from Garmin Connect timestamp sensors has been removed.
|
||||
It used to be set to empty string. If you have automations, scripts or external
|
||||
data recvorder that rely on unit of measurement for these sensors, you might
|
||||
need to adjust to this change.
|
||||
|
||||
`reset_waste_drawer`, `set_sleep_mode`, and `set_wait_time` now have their own
|
||||
services. Previously, they were triggered by using `send_command`.
|
||||
If you used any of those commands in your automations or scripts, you'll need
|
||||
to replace them with their service counter-part.
|
||||
|
||||
([@natekspencer] - [#48300])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Recorder" %}
|
||||
|
||||
Database migrations are now done in the background and no longer prevent
|
||||
Home Assistant from starting.
|
||||
|
||||
The migration is started shortly after the started event since they are CPU
|
||||
intensive (mostly just sqlite since its in the same process) and we do not want
|
||||
to compete with startup.
|
||||
|
||||
Events created by your system are queued and processed when the migration is
|
||||
completed. There is a safety to start discarding events if more than ~30000
|
||||
events happen before migration is completed to avoid memory exhaustion.
|
||||
|
||||
During migration, Home Assistant will prevent being started or stopped and
|
||||
this will also disable the `homeassistant.stop` and `homeassistant.start`
|
||||
services until the migration has been completed.
|
||||
|
||||
The sqlite database recovery logic can now recover at point after setup
|
||||
including purge, migration, and event insert. In short we can _always_
|
||||
(hopefully) recover and start a new db without a restart.
|
||||
|
||||
The quick check is no longer performed on unclean shutdown since we can always
|
||||
recover live. The `db_integrity_check` option has been deprecated.
|
||||
|
||||
([@bdraco] - [#49036] [#49098])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "SMA Solar" %}
|
||||
|
||||
The SMA integration is now configured via the UI. Configuring the integration
|
||||
via YAML is now deprecated. Existing YAML configuration is automatically
|
||||
imported on upgrade and can be safely removed after upgrade.
|
||||
|
||||
Using custom sensors is deprecated and not possible using the UI. Feel free to
|
||||
submit additional sensors to be added as standard sensors to the
|
||||
[pysma library](https://github.com/kellerza/pysma/blob/master/pysma/__init__.py#L100).
|
||||
|
||||
The `pv_power` sensor is now reporting DC power of solar panels side A and named `pv_power_a` for new installations. `grid_power` is the total power supplied to the grid.
|
||||
|
||||
([@rklomp] - [#48003])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Swiss Hydrological Data" %}
|
||||
|
||||
FEON/BAFU changed their data which required removing some of the attributes.
|
||||
|
||||
The following attributes are no longer available:
|
||||
|
||||
- delta-24h
|
||||
- max-1h
|
||||
- min-1h
|
||||
- mean-1h
|
||||
- previous-24h
|
||||
|
||||
([@Bouni] - [#49119])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Shelly" %}
|
||||
|
||||
The Shelly Wi-Fi RSSI sensor unit was wrong, it is **dBm** and not **dB**.
|
||||
If you rely on the unit of measurement from this sensor, you might need to
|
||||
adjust to this change.
|
||||
|
||||
([@thecode] - [#49265])
|
||||
([@MartinHjelmare] - [#48431])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
@ -527,57 +502,60 @@ The Growl project has now fully retired, see: <https://growl.github.io/growl/>
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "ecobee" %}
|
||||
{% details "Google Travel Time" %}
|
||||
|
||||
ecobee climate devices will change the reported temperature precision for their
|
||||
`current_temperature` attribute from whole degrees to 0.1 degree increments.
|
||||
Automations which rely on whole-number precision may need adjustments.
|
||||
|
||||
([@bjpetit] - [#48086])
|
||||
|
||||
Setting a fan hold in the ecobee integration will no longer also set a
|
||||
temperature hold. If any automations assumed that the temperature would be set
|
||||
when calling the set_fan_mode service on an ecobee device, those automations
|
||||
will need to add the appropriate `set_temperature` service call.
|
||||
|
||||
([@jjlawren] - [#48697])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "ZeroConf" %}
|
||||
|
||||
If the `default_interface` is not set, the value is auto-detected based on the
|
||||
system routing next hop for the mDNS broadcast address (`224.0.0.251`).
|
||||
|
||||
If the next-hop cannot be detected or is a loopback address, `zeroconf` will
|
||||
broadcast on all interfaces. If the next hop is a non-loopback address,
|
||||
`zeroconf` will only broadcast on the default interface.
|
||||
|
||||
Setting the `default_interface` to `true` or `false` will override the auto
|
||||
detection.
|
||||
|
||||
([@bdraco] - [#49529])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "AVM FRITZ!Box Tools" %}
|
||||
|
||||
The AVM FRITZ!Box Tools integration is now configured via the UI. Configuring
|
||||
The Google Travel Time integration is now configured via the UI. Configuring
|
||||
the integration via YAML is now deprecated. Existing YAML configuration is
|
||||
automatically imported on upgrade and can be safely removed after upgrade.
|
||||
|
||||
([@chemelli74] - [#48287])
|
||||
([@raman325] - [#43509])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "AVM FRITZ!SmartHome" %}
|
||||
{% details "Hive" %}
|
||||
|
||||
YAML configuration for AVM FRITZ!SmartHome has been removed, after it has been
|
||||
deprecated for 12 months. Configuration via UI is fully integrated. Existing
|
||||
YAML configuration has already been imported automatically in the previous
|
||||
releases and can now safely be removed from your configuration files.
|
||||
The existing Hive service `heating_boost` will be deprecated in Home Assistant
|
||||
release 2021.6 and a new service to replace it has been created called
|
||||
`heating_boost_on`.
|
||||
|
||||
([@mib1185] - [#49663])
|
||||
If you use the `heating_boost` Hive service please update your configuration
|
||||
to the new service. A deprecation warning will be printed to the logs when the
|
||||
deprecated service is used.
|
||||
|
||||
([@KJonline] - [#48701])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "KNX" %}
|
||||
|
||||
The `config_file` YAML option for KNX was deprecated before and has now been
|
||||
removed.
|
||||
|
||||
([@marvin-w] - [#48799])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Light profiles" %}
|
||||
|
||||
When a light entity has a default profile associated, the default profile will
|
||||
only be applied for the `light.turn_on` service call when the light state is
|
||||
off or no data is sent with the service call.
|
||||
|
||||
The transition attribute from the default profile in `light_profiles.csv` will
|
||||
also be applied when `light.turn_off` is called.
|
||||
|
||||
([@karliemeads] - [#49376]) ([light docs])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Litter-Robot" %}
|
||||
|
||||
`reset_waste_drawer`, `set_sleep_mode`, and `set_wait_time` now have their own
|
||||
services. Previously, they were triggered by using `send_command`.
|
||||
If you used any of those commands in your automations or scripts, you'll need
|
||||
to replace them with their service counter-part.
|
||||
|
||||
([@natekspencer] - [#48300])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
@ -624,6 +602,92 @@ Swap allows `none`/`byte`/`word`/`word_byte` options.
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Recollect Waste" %}
|
||||
|
||||
Recollect Waste pickup dates are now stored as UTC timestamps.
|
||||
|
||||
([@bachya] - [#48690])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Recorder" %}
|
||||
|
||||
Database migrations are now done in the background and no longer prevent
|
||||
Home Assistant from starting.
|
||||
|
||||
The migration is started shortly after the started event since they are CPU
|
||||
intensive (mostly just sqlite since its in the same process) and we do not want
|
||||
to compete with startup.
|
||||
|
||||
Events created by your system are queued and processed when the migration is
|
||||
completed. There is a safety to start discarding events if more than ~30000
|
||||
events happen before migration is completed to avoid memory exhaustion.
|
||||
|
||||
During migration, Home Assistant will prevent being started or stopped and
|
||||
this will also disable the `homeassistant.stop` and `homeassistant.start`
|
||||
services until the migration has been completed.
|
||||
|
||||
The sqlite database recovery logic can now recover at point after setup
|
||||
including purge, migration, and event insert. In short we can _always_
|
||||
(hopefully) recover and start a new db without a restart.
|
||||
|
||||
The quick check is no longer performed on unclean shutdown since we can always
|
||||
recover live. The `db_integrity_check` option has been deprecated.
|
||||
|
||||
([@bdraco] - [#49036] [#49098])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "RoonLabs music player" %}
|
||||
|
||||
The RoonLabs music player `media_player` previously had integration specific
|
||||
services for `roon.join` and `roon.un_join`. These have been removed removes
|
||||
and replaced with the `media_player.join` and `media_player.unjoin` services.
|
||||
|
||||
If you use these services in your automations or script, you need to adjust those.
|
||||
|
||||
([@pavoni] - [#49667])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Shelly" %}
|
||||
|
||||
The Shelly Wi-Fi RSSI sensor unit was wrong, it is **dBm** and not **dB**.
|
||||
If you rely on the unit of measurement from this sensor, you might need to
|
||||
adjust to this change.
|
||||
|
||||
([@thecode] - [#49265])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "SimpliSafe" %}
|
||||
|
||||
The unpublished SimpliSafe cloud API no longer provides a functioning websocket.
|
||||
Therefore, the integration will no longer be able to receive `SIMPLISAFE_EVENT`
|
||||
or `SIMPLISAFE_NOTIFICATION` events, nor will it be possible for stage changes
|
||||
performed outside of Home Assistant (e.g., via the keypad) to be reflected in
|
||||
Home Assistant in near-realtime.
|
||||
|
||||
([@bachya] - [#49876]) ([simplisafe docs])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "SMA Solar" %}
|
||||
|
||||
The SMA integration is now configured via the UI. Configuring the integration
|
||||
via YAML is now deprecated. Existing YAML configuration is automatically
|
||||
imported on upgrade and can be safely removed after upgrade.
|
||||
|
||||
Using custom sensors is deprecated and not possible using the UI. Feel free to
|
||||
submit additional sensors to be added as standard sensors to the
|
||||
[pysma library](https://github.com/kellerza/pysma/blob/master/pysma/__init__.py#L100).
|
||||
|
||||
The `pv_power` sensor is now reporting DC power of solar panels side A and named `pv_power_a` for new installations. `grid_power` is the total power supplied to the grid.
|
||||
|
||||
([@rklomp] - [#48003])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Sure Petcare" %}
|
||||
|
||||
The following YAML configuration options have been deprecated:
|
||||
@ -640,43 +704,73 @@ remove those.
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "RoonLabs music player" %}
|
||||
{% details "Swiss Hydrological Data" %}
|
||||
|
||||
The RoonLabs music player `media_player` previously had integration specific
|
||||
services for `roon.join` and `roon.un_join`. These have been removed removes
|
||||
and replaced with the `media_player.join` and `media_player.unjoin` services.
|
||||
FEON/BAFU changed their data which required removing some of the attributes.
|
||||
|
||||
If you use these services in your automations or script, you need to adjust those.
|
||||
The following attributes are no longer available:
|
||||
|
||||
([@pavoni] - [#49667])
|
||||
- delta-24h
|
||||
- max-1h
|
||||
- min-1h
|
||||
- mean-1h
|
||||
- previous-24h
|
||||
|
||||
([@Bouni] - [#49119])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "DHT Sensor" %}
|
||||
{% details "System Monitor" %}
|
||||
|
||||
The `pin` configuration option is currently an integer but will need to be
|
||||
prefixed with D for Raspberry Pi platforms.
|
||||
The unit of measurement from System Monitor timestamp sensors has been removed.
|
||||
It used to be set to empty string. If you have automations, scripts or external
|
||||
data recorder that rely on unit of measurement for these sensors, you might
|
||||
need to adjust to this change.
|
||||
|
||||
Please adjust your YAML configuration for this change.
|
||||
|
||||
([@TheGardenMonkey] - [#41525])
|
||||
([@MartinHjelmare] - [#48431])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Container udev" %}
|
||||
{% details "Tasmota" %}
|
||||
|
||||
We don't run a udev instance anymore inside the container. This was used by the Supervisor
|
||||
which now using the host udev over all containers.
|
||||
Tasmota lights no longer supports deprecated `white_value`, use `rgbw_color`
|
||||
instead.
|
||||
|
||||
For now, we have a fallback ENV variable `USING_UDEV=1` which you can set on your container
|
||||
to get the old behavier and give you time for using the docker way to map/use devices.
|
||||
([@emontnemery] - [#49599]) ([tasmota docs])
|
||||
|
||||
([@pvizeli]- [#180])
|
||||
The Tasmota Wi-Fi RSSI sensor unit was wrong, it is **dBm** and not **dB**.
|
||||
If you rely on the unit of measurement from this sensor, you might need to
|
||||
adjust to this change.
|
||||
|
||||
[#180]: https://github.com/home-assistant/docker/pull/180
|
||||
([@thecode] - [#49263]) ([tasmota docs])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Waze Travel Time" %}
|
||||
|
||||
The Waze Travel Time integration is now configured via the UI. Configuring
|
||||
the integration via YAML is now deprecated. Existing YAML configuration is
|
||||
automatically imported on upgrade and can be safely removed after upgrade.
|
||||
|
||||
([@raman325] - [#43419])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "ZeroConf" %}
|
||||
|
||||
If the `default_interface` is not set, the value is auto-detected based on the
|
||||
system routing next hop for the mDNS broadcast address (`224.0.0.251`).
|
||||
|
||||
If the next-hop cannot be detected or is a loopback address, `zeroconf` will
|
||||
broadcast on all interfaces. If the next hop is a non-loopback address,
|
||||
`zeroconf` will only broadcast on the default interface.
|
||||
|
||||
Setting the `default_interface` to `true` or `false` will override the auto
|
||||
detection.
|
||||
|
||||
([@bdraco] - [#49529])
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
## Farewell to the following
|
||||
|
||||
@ -1248,6 +1342,8 @@ their data, which is not allowed for core integrations.
|
||||
- Add color_mode support to tasmota light ([@emontnemery] - [#49599]) ([tasmota docs]) (breaking-change) (beta fix)
|
||||
- Fix fitbit RuntimeError: I/O must be done in the executor ([@vlebourl] - [#50058]) ([fitbit docs]) (beta fix)
|
||||
- Bump motioneye-client to v0.3.6 . ([@dermotduffy] - [#50096]) ([motioneye docs]) (beta fix)
|
||||
- Remove surepetcare usage of deprecated config options ([@benleb] - [#50113]) ([surepetcare docs]) (beta fix)
|
||||
- Fix Tasmota color scaling and RGBW lights ([@emontnemery] - [#50120]) ([tasmota docs]) (beta fix)
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
@ -1807,6 +1903,8 @@ their data, which is not allowed for core integrations.
|
||||
[#50064]: https://github.com/home-assistant/core/pull/50064
|
||||
[#50093]: https://github.com/home-assistant/core/pull/50093
|
||||
[#50096]: https://github.com/home-assistant/core/pull/50096
|
||||
[#50113]: https://github.com/home-assistant/core/pull/50113
|
||||
[#50120]: https://github.com/home-assistant/core/pull/50120
|
||||
[@AaronDavidSchneider]: https://github.com/AaronDavidSchneider
|
||||
[@Adminiuga]: https://github.com/Adminiuga
|
||||
[@Bouni]: https://github.com/Bouni
|
||||
|
||||
BIN
source/images/blog/2021-05/integrations-dashboard.png
Normal file
BIN
source/images/blog/2021-05/integrations-dashboard.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 122 KiB |
BIN
source/images/blog/2021-05/rgbww-light.png
Normal file
BIN
source/images/blog/2021-05/rgbww-light.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 60 KiB |
BIN
source/images/blog/2021-05/setup-time.png
Normal file
BIN
source/images/blog/2021-05/setup-time.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 64 KiB |
BIN
source/images/blog/2021-05/social.png
Normal file
BIN
source/images/blog/2021-05/social.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 146 KiB |
BIN
source/images/blog/2021-05/still-starting.png
Normal file
BIN
source/images/blog/2021-05/still-starting.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 5.0 KiB |
Loading…
x
Reference in New Issue
Block a user