jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-24 09:46:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update 2023-09-06-release-20239.markdown

Browse Source
This commit is contained in:
Bram Kragten 2023-09-05 13:46:54 +02:00
parent 19399cce86
commit 5ab36ff1b2
1 changed files with 11 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
source/_posts/2023-09-06-release-20239.markdown
View File

@ -139,6 +139,10 @@ Temporary screenshot that needs to be replaced.
</p>
## Actions for template entities
Trigger template entities can now have an action block that is executed after the trigger but before the entities are rendered. All variables from the action block will be available during the entity rendering. This will allow users to fetch things like weather forecast or calendar events and use them in their template entities. Long term goal is to align the trigger template entities with automation syntax so we can support things like tracing too.
## Weather forecast service
We added a weather forecast service, that returns the weather forecast.
@ -146,12 +150,15 @@ We added a weather forecast service, that returns the weather forecast.
Previously you would have to look at the `forecast` attribute of a weather entity to get the forecast, now this can be done by calling a new service, `weather.get_forecast`, that will respond with the forecast.
You can also specify what type of forecast you want, daily or do you want to know it for every hour? This means you no longer need separate entities for every forecast type, but it can all be done in 1 entity.
If an entity supports multiple forecasts, you can choose which one you want to see in the more info dialog.
In the weather card in your dashboard, you can also now pick what kind of weather forecast you want to show in that card.
All weather integrations are updated to support this new service.
With this change, the `forecast` attribute of the weather entity is deprecated, and will be removed in Home Assistant Core 2024.3.
You can use the newly added `action` part of a template entity to fetch the forecast and use it in your template.
<p class='img'>
<img src='https://media.discordapp.net/attachments/427516175237382144/1146445861421846608/SPOILER_CleanShot_2023-08-30_at_16.03.542x.png?width=1466&height=794'></a>
Temporary screenshot that needs to be replaced.
@ -186,9 +193,10 @@ To consider:
There are many more improvements in this release; here are some of the other
noteworthy changes this release:
- [Enphase Envoy] has gotten a lot of love this release, thanks [@bdraco]!
- [Enphase Envoy] has gotten a lot of love this release, thanks [@bdraco] and [@cgarwood]!
[@bdraco]: https://github.com/bdraco
[@cgarwood]: https://github.com/cgarwood
[Enphase Envoy]: /integrations/enphase_envoy
## New integrations
@ -463,6 +471,8 @@ some `zwave_js` entities that you haven't given a custom name to may be renamed.
Since they are registered in the entity registry, the entity IDs will not change
and your automations should therefore not be impacted by the change.
You will also need to update Z-Wave JS to version 11.14.0 (addon version 0.1.89) or higher.
([@raman325] - [#98140]) ([documentation](/integrations/zwave_js))
[@raman325]: https://github.com/raman325