mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-08 18:06:54 +00:00
2025.5: Process review comment, iterate, add missing backward incompat changes
This commit is contained in:
Franck Nijhof
parent
a6458f6992
commit
57662d3b88
@ -82,7 +82,7 @@ Enjoy the (beta) release!
|
||||
- [Waiting for the backup to finish on restarts](#waiting-for-the-backup-to-finish-on-restarts)
|
||||
- [Thousands of new text-to-speech voice variants for Home Assistant Cloud subscribers](#thousands-of-new-text-to-speech-voice-variants-for-home-assistant-cloud-subscribers)
|
||||
- [Picking entities](#picking-entities)
|
||||
- [Z-Wave Smart Start and long range support](#z-wave-smart-start-and-long-range-support)
|
||||
- [Z-Wave Smart Start and Long Range support](#z-wave-smart-start-and-long-range-support)
|
||||
- [Integrations](#integrations)
|
||||
- [New integrations](#new-integrations)
|
||||
- [Noteworthy improvements to existing integrations](#noteworthy-improvements-to-existing-integrations)
|
||||
@ -114,7 +114,7 @@ multiple locations configured in Home Assistant.
|
||||
|
||||
<img class="no-shadow" alt="TODO: Replace." src="/images/blog/2025-05/temp-backups-retention-per-location.png" />
|
||||
|
||||
It might be that one of your backups locations has more storage space than
|
||||
It might be that one of your backup locations has more storage space than
|
||||
another, or that you want to keep more backups in one location than another.
|
||||
For example, maybe you have space to store the last 3 backups in your Google
|
||||
Drive, but you want to keep 25 backups on your local NAS server.
|
||||
@ -149,13 +149,13 @@ to set the default behavior for the backup before upgrade toggle.
|
||||
<img class="no-shadow" alt="TODO: Replace." src="/images/blog/2025-05/temp-backups-select-preference-backup-before-update.png" />
|
||||
|
||||
When you set the option to "Backup before upgrade", the toggle will be enabled
|
||||
by default, otherwise it will be default to disabled. There is an additional
|
||||
by default, otherwise it will default to disabled. There is an additional
|
||||
option to set this behavior for add-ons as well, so you can tweak it to your
|
||||
liking.
|
||||
|
||||
### Waiting for the backup to finish on restarts
|
||||
|
||||
Another small improvement, but one an unimportant one, is that if you restart
|
||||
Another small improvement, but not an unimportant one, is that if you restart
|
||||
Home Assistant while a backup is in progress, the restart will wait for the
|
||||
backup to finish before proceeding.
|
||||
|
||||
@ -166,15 +166,15 @@ abort the process by restarting Home Assistant.
|
||||
|
||||
## Thousands of new text-to-speech voice variants for Home Assistant Cloud subscribers
|
||||
|
||||
You are are subscribed to [Home Assistant Cloud](https://www.nabucasa.com), you
|
||||
If you are subscribed to [Home Assistant Cloud](https://www.nabucasa.com), you
|
||||
not just get [backup storage included](https://www.nabucasa.com/config/backups/),
|
||||
but you also get access to the absolute [best in class text-to-speech](https://www.nabucasa.com/config/tts/)
|
||||
available. If you haven't tried it yet, you should!
|
||||
|
||||
This release, extends the already staggering amount of text-to-speech voices
|
||||
This release extends the already staggering amount of text-to-speech voices
|
||||
and above all now include voice variants and styles. This means that you can
|
||||
now choose between different voice styles and tones, such as "friendly",
|
||||
"angry", "sad", "wispher", etc; allowing you to customize your announcements to
|
||||
"angry", "sad", "whisper", etc., allowing you to customize your announcements to
|
||||
fit the mood and context of the situation.
|
||||
|
||||
<img class="no-shadow" alt="TODO: Replace." src="/images/blog/2025-05/temp-new-voice-variants-for-home-assistant-cloud.png" />
|
||||
@ -211,7 +211,7 @@ Thanks a ton! 🙏 ❤️
|
||||
|
||||
{% endimportant %}
|
||||
|
||||
We are working on improving the context of things shown in the UI. This to
|
||||
We are working on improving the context of things shown in the UI. This is to
|
||||
ensure you always know which device or entity you are looking at, no matter
|
||||
where you are in the Home Assistant interface.
|
||||
|
||||
@ -219,13 +219,13 @@ In the last release, we already had a small noteworthy change regarding this.
|
||||
We added the device and area to the entity information dialogs, so you always
|
||||
exactly know which entity you are viewing.
|
||||
|
||||
This release, we improve context on the entity pickers in our UI. This is the
|
||||
dropdown you see when you select an entity in, for example, an card, automation,
|
||||
In this release, we improve context on the entity pickers in our UI. This is the
|
||||
dropdown you see when you select an entity in, for example, a card, automation,
|
||||
or script. This picker will now show the device and area name as well!
|
||||
|
||||
<img class="no-shadow" alt="TODO: Replace." src="/images/blog/2025-05/temp-improved-entity-picker.png" />
|
||||
|
||||
This slowly will remove the need for you to rename every single entity or
|
||||
This will slowly remove the need for you to rename every single entity or
|
||||
device to include this information in the name of the entity.
|
||||
|
||||
You might notice that the entity ID isn't shown in the picker anymore. We think
|
||||
@ -233,20 +233,20 @@ we are at a point where many uses solely rely on the UI and the entity ID is
|
||||
not needed anymore. However, if you do prefer to see the entity ID, you can
|
||||
enable it in your profile settings.
|
||||
|
||||
## Z-Wave Smart Start and long range support
|
||||
## Z-Wave Smart Start and Long Range support
|
||||
|
||||
We are providing quite a few enhancements to the Z-Wave integration and
|
||||
experience this release. Our commercial partner [Nabu Casa](https://nabucasa.com)
|
||||
is working on a–not so secret–Z-Wave antenna, and we want to ensure that
|
||||
Home Assistant is ready for it; providing the best possible user experience
|
||||
experience in this release. Our commercial partner [Nabu Casa](https://nabucasa.com)
|
||||
is working on a not-so-secret Z-Wave antenna, and we want to ensure that
|
||||
Home Assistant is ready for it, providing the best user experience
|
||||
possible.
|
||||
|
||||
This release, we improved the whole experience in setting up new Z-Wave devices,
|
||||
adding support for Z-Wave smart start to scan a QR code from your new device
|
||||
improved support for Z-Wave Smart Start to scan a QR code from your new device
|
||||
to magically add it to Home Assistant; and most noteworthy, we added support
|
||||
for Z-Wave long range devices directly in Home Assistant!
|
||||
for Z-Wave Long Range devices directly in Home Assistant!
|
||||
|
||||
**TODO**: Add screenshots or little video of this this process.
|
||||
**TODO**: Add screenshots or little video of this process.
|
||||
|
||||
<img class="no-shadow" alt="TODO: Replace." src="/images/blog/2025-05/temp-zwave-long-range.png" />
|
||||
|
||||
@ -434,10 +434,10 @@ noteworthy changes this release:
|
||||
in Home Assistant. Cool!
|
||||
- The `floor_id` and `area_id` template methods have been enhanced by [@formatBCE]
|
||||
to also look for floors or area aliases. Awesome!
|
||||
- We new have support for trigger-based template entities for switches and
|
||||
- We now have support for trigger-based template entities for switches and
|
||||
lights. Amazing work [@Petro31]!
|
||||
- [@Petro31] wasn't done yet though, he also added support for modern YAML-syntax
|
||||
to the cover template entities. Nice!
|
||||
- Support for modern YAML-syntax was also added to the cover template entities
|
||||
by [@Petro31]. Nice!
|
||||
- [@frenck] added support for detecting Home Assistant Container installation
|
||||
types not running in host networking mode. This is important for
|
||||
Home Assistant to function properly. It raises a repair issue if it detects
|
||||
@ -496,20 +496,20 @@ condition, or action.
|
||||
|
||||
**TODO:** Add small movie clip on how this works.
|
||||
|
||||
An amazing quality of live improvement, contributed by [@jpbede]! Thank you! 🙌
|
||||
An amazing quality of life improvement, contributed by [@jpbede]! Thank you! 🙌
|
||||
|
||||
[@jpbede]: https://github.com/jpbede
|
||||
|
||||
## Discover what Home Assistant is discovering
|
||||
|
||||
Home Assistant is constantly scanning your network for new devices and
|
||||
integrations. using all sorts of discovery protocols. This greatly improves the
|
||||
integrations using all sorts of discovery protocols. This greatly improves the
|
||||
user experience, as it allows you to easily add new devices to your Home
|
||||
Assistant installation.
|
||||
|
||||
However, sometimes, you might want to know what Home Assistant is seeing
|
||||
or wondering why a certain device is not being discovered. To help with that
|
||||
[@bdraco] added browsing tools for the DHCP, mDNS/ZeroConf and UPnP/SSDP, that
|
||||
[@bdraco] added browsing tools for the DHCP, mDNS/ZeroConf, and UPnP/SSDP that
|
||||
allow you to see what Home Assistant is seeing. It is quite technical, but
|
||||
it is a great way to see what is going on in your network.
|
||||
|
||||
@ -528,7 +528,7 @@ Our very active [Discord chat server](/join-chat) is an excellent place to be
|
||||
at, and don't forget to join our amazing [forums](https://community.home-assistant.io/).
|
||||
|
||||
Found a bug or issue? Please report it in our [issue tracker](https://github.com/home-assistant/core/issues),
|
||||
to get it fixed! Or, check [our help page](/help) for guidance for more
|
||||
to get it fixed! Or, check [our help page](/help) for guidance on more
|
||||
places you can go.
|
||||
|
||||
Are you more into email? [Sign-up for our Building the Open Home Newsletter](/newsletter)
|
||||
@ -667,8 +667,8 @@ following variables** accordingly.
|
||||
The previously deprecated state attributes for the 17TRACK entities
|
||||
have been removed.
|
||||
|
||||
If you relied on these attributes your automations or scripts, you will need to
|
||||
update them to use the dedicated sensors instead.
|
||||
If you relied on these attributes in your automations or scripts, you will need
|
||||
to update them to use the dedicated sensors instead.
|
||||
|
||||
([@joostlek] - [#142622]) ([documentation](/integrations/seventeentrack))
|
||||
|
||||
@ -684,7 +684,7 @@ multiple units with different features. We now merge all units of a device into
|
||||
one entry representing the physical device.
|
||||
|
||||
As this might remove existing devices and create new ones, you should check your
|
||||
automations and scripts, if they need to be adjusted to the new device registry
|
||||
automations and scripts to see if they need to be adjusted to the new device registry
|
||||
entries.
|
||||
|
||||
([@mib1185] - [#142845]) ([documentation](/integrations/fritzbox))
|
||||
@ -731,6 +731,44 @@ has to be changed in Home Assistant (where applicable).
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Google Maps Travel Time" %}
|
||||
|
||||
Google has deprecated the Distance Matrix API. The new Routes API does not
|
||||
provide the state attributes `Destination addresses` and `Origin addresses`
|
||||
anymore.
|
||||
|
||||
The amount of free requests got halved, resulting in the sensor now refreshing
|
||||
every 10 minutes instead of every 5 minutes.
|
||||
|
||||
([@eifinger] - [#140691]) ([documentation](/integrations/google_travel_time))
|
||||
|
||||
[@eifinger]: https://github.com/eifinger
|
||||
[#140691]: https://github.com/home-assistant/core/pull/140691
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "La Marzocco" %}
|
||||
|
||||
La Marzocco released the gateway firmware v5 last month, which stopped
|
||||
supporting local communication. We now fully support this firmware; support for
|
||||
older firmware has been dropped.
|
||||
|
||||
The following entities and controls are missing, either because they are no
|
||||
longer supported by the app or not part of the new library version yet:
|
||||
|
||||
- Steam & coffee boiler temperatures
|
||||
- Shot timer sensor
|
||||
- Scale support
|
||||
- Steam temperature number
|
||||
- Prebrew & Preinfusion numbers
|
||||
|
||||
([@zweckj] - [#142098]) ([documentation](/integrations/lamarzocco))
|
||||
|
||||
[@zweckj]: https://github.com/zweckj
|
||||
[#142098]: https://github.com/home-assistant/core/pull/142098
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Network UPS Tools (NUT)" %}
|
||||
|
||||
The status sensor has changed, providing the state from the UPS Display.
|
||||
@ -758,6 +796,26 @@ can be used to set a custom polling interval.
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Opower" %}
|
||||
|
||||
If you return energy to the grid, you will have to reconfigure your energy
|
||||
dashboard.
|
||||
|
||||
For improved experience in the energy dashboard, negative energy
|
||||
consumption/cost values have been separated into two dedicated
|
||||
return/compensation statistics.
|
||||
|
||||
Add `Opower {utility name} elec {account number} return` under
|
||||
**Return to grid** to see return energy statistics. Track return compensation
|
||||
using `Opower {utility name} elec {account number} compensation`.
|
||||
|
||||
([@parkerbxyz] - [#135258]) ([documentation](/integrations/opower))
|
||||
|
||||
[@parkerbxyz]: https://github.com/parkerbxyz
|
||||
[#135258]: https://github.com/home-assistant/core/pull/135258
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
{% details "Overkiz" %}
|
||||
|
||||
Previously, for Atlantic Electrical Towel Dryer devices, the ‘auto’ HVAC mode
|
||||
@ -777,7 +835,7 @@ Now, the ‘auto’ mode in Home Assistant will correspond directly to the
|
||||
|
||||
Persistent notifications are no longer created when devices are discovered.
|
||||
|
||||
Automations which trigger on the persistent notification
|
||||
Automations that trigger on the persistent notification
|
||||
`config_entry_discovery` should be updated to instead trigger on the
|
||||
event `config_entry_discovered`.
|
||||
|
||||
@ -793,8 +851,8 @@ event `config_entry_discovered`.
|
||||
The previously deprecated state attributes for the Total Connect alarm control
|
||||
panel have been removed.
|
||||
|
||||
If you relied on these attributes your automations or scripts, you will need to
|
||||
update them to use the dedicated sensors instead.
|
||||
If you relied on these attributes in your automations or scripts, you will need
|
||||
to update them to use the dedicated sensors instead.
|
||||
|
||||
([@joostlek] - [#142625]) ([documentation](/integrations/totalconnect))
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user