From 0a28f41189dddda3ec9fd3174d808dbb03e30dea Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20Huryn?= Date: Thu, 31 Aug 2023 22:27:42 +0200 Subject: [PATCH 1/7] blebox: sensor types extended (#26801) * chore: update functionality status * chore: added humitidySensor, moved airSensor --- source/_integrations/blebox.markdown | 11 +++-------- 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/source/_integrations/blebox.markdown b/source/_integrations/blebox.markdown index 2c2299e57df..2bf5e29769b 100644 --- a/source/_integrations/blebox.markdown +++ b/source/_integrations/blebox.markdown @@ -48,7 +48,7 @@ This integration adds BleBox device as a binary_sensor in Home Assistant. Currently, this includes support for the following product classes: - BleBox rainSensor -- BleBox wind&rainSensor (rain only) +- BleBox wind&rainSensor ## Sensors @@ -57,6 +57,8 @@ This integration adds the BleBox device as a sensor in Home Assistant. Currently, this includes support for the following product classes and their features: - BleBox tempSensor (temperature only) +- Blebox humiditySensor +- BleBox airSensor ## Switches @@ -76,13 +78,6 @@ Currently, this includes support for the following product classes: - BleBox saunaBox - BleBox thermoBox -## Air Quality - -This integration adds the BleBox device as an air quality entity in Home Assistant. - -Currently, this includes support for the following product classes: - -- BleBox airSensor ## Lights From 71fa7d512bbedf929884816ec8e8225a8b1eec04 Mon Sep 17 00:00:00 2001 From: jimmyd-be <34766203+jimmyd-be@users.noreply.github.com> Date: Thu, 31 Aug 2023 22:25:25 +0200 Subject: [PATCH 2/7] Renson binary sensor (#27802) * add Renson endura delta integration documentation * Fixed text lint error in renson endura delta * Changed metadata header * Changed integration domain to renson * Removed manual configuration Changed intro a bit * Add binary sensor to renson --- source/_integrations/renson.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_integrations/renson.markdown b/source/_integrations/renson.markdown index 36c9ba8d828..442da8e8388 100644 --- a/source/_integrations/renson.markdown +++ b/source/_integrations/renson.markdown @@ -2,6 +2,7 @@ title: Renson description: Instructions on how to integrate Renson Endura Delta sensors into Home Assistant. ha_category: + - Binary Sensor - Sensor ha_release: 2023.7 ha_iot_class: Local Polling @@ -10,6 +11,7 @@ ha_codeowners: - '@jimmyd-be' ha_domain: renson ha_platforms: + - binary_sensor - sensor ha_integration_type: integration --- From 724878a111b88de2a5233cf691edfe0c9d972cfe Mon Sep 17 00:00:00 2001 From: G Johansson Date: Thu, 31 Aug 2023 22:01:39 +0200 Subject: [PATCH 3/7] Timer start service remove duration parameter (#28754) --- source/_integrations/timer.markdown | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/source/_integrations/timer.markdown b/source/_integrations/timer.markdown index 97beeeed51c..994e54dd1bb 100644 --- a/source/_integrations/timer.markdown +++ b/source/_integrations/timer.markdown @@ -91,13 +91,12 @@ Pick an icon from [Material Design Icons](https://pictogrammers.com/library/mdi/ ### Service `timer.start` -Starts or restarts a timer with the provided duration. If no duration is given, it will either restart with its initial value, or continue a paused timer with the remaining duration. If a new duration is provided, this will be the new default for the timer until Home Assistant is restarted (which loads your default values). The duration can be specified as a number of seconds or the easier to read `01:23:45` format. +Starts or restarts a timer. It will either restart with its initial value, or continue a paused timer with the remaining duration. You can also use `entity_id: all` and all active timers will be started. | Service data attribute | Optional | Description | | ---------------------- | -------- | ----------- | | `entity_id` | no | Name of the entity to take action, e.g., `timer.timer0`. | -| `duration` | yes | Duration in seconds or `01:23:45` format until the timer finishes. | ### Service `timer.change` From 72062aa3dec48e2f0c9c83fbb49bbb29c84c9942 Mon Sep 17 00:00:00 2001 From: Allen Porter Date: Mon, 4 Sep 2023 09:35:57 -0700 Subject: [PATCH 4/7] Add template entity script action documentation (#28768) * Add template entity script action documentation * Update source/_integrations/template.markdown Co-authored-by: Erik Montnemery * Focus action explanation on variables avaiable in templates * Remove whitespace * tiny tweak --------- Co-authored-by: Erik Montnemery Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> --- source/_integrations/template.markdown | 34 ++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) diff --git a/source/_integrations/template.markdown b/source/_integrations/template.markdown index caab7a606b2..153eee1a261 100644 --- a/source/_integrations/template.markdown +++ b/source/_integrations/template.markdown @@ -112,6 +112,10 @@ unique_id: description: The unique ID for this config block. This will be prefixed to all unique IDs of all entities in this block. required: false type: string +action: + description: Define actions to be executed when the trigger fires. Optional. Variables set by the action script are available when evaluating entity templates. This can be used to interact with anything via services, in particular services with [response data](/docs/scripts/service-calls#use-templates-to-handle-response-data). [See action documentation](/docs/automation/action). + required: false + type: list sensor: description: List of sensors required: true @@ -660,6 +664,36 @@ template: {% endraw %} +### Trigger based handling of service response data + +This example demonstrates how to use an `action` to call a [service with response data](/docs/scripts/service-calls/#use-templates-to-handle-response-data) +and use the response in a template. + +{% raw %} + +```yaml +template: + - trigger: + - platform: time_pattern + hours: /1 + action: + - service: weather.get_forecast + data: + type: hourly + target: + entity_id: weather.home + response_variable: hourly + sensor: + - name: Weather Forecast Hourly + unique_id: weather_forecast_hourly + state: "{{ now().isoformat() }}" + attributes: + forecast: "{{ hourly.forecast }}" +``` + +{% endraw %} + + ## Legacy binary sensor configuration format _This format still works but is no longer recommended. [Use modern configuration](#configuration-variables)._ From 19399cce865f924d7de07f71ec72590068d01537 Mon Sep 17 00:00:00 2001 From: Erik Montnemery Date: Mon, 4 Sep 2023 20:17:46 +0200 Subject: [PATCH 5/7] Revert "Timer start service remove duration parameter (#28754)" (#28783) This reverts commit 48f8de4237d238dcff69f37819755c826a3a6cb9. --- source/_integrations/timer.markdown | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/source/_integrations/timer.markdown b/source/_integrations/timer.markdown index 994e54dd1bb..97beeeed51c 100644 --- a/source/_integrations/timer.markdown +++ b/source/_integrations/timer.markdown @@ -91,12 +91,13 @@ Pick an icon from [Material Design Icons](https://pictogrammers.com/library/mdi/ ### Service `timer.start` -Starts or restarts a timer. It will either restart with its initial value, or continue a paused timer with the remaining duration. +Starts or restarts a timer with the provided duration. If no duration is given, it will either restart with its initial value, or continue a paused timer with the remaining duration. If a new duration is provided, this will be the new default for the timer until Home Assistant is restarted (which loads your default values). The duration can be specified as a number of seconds or the easier to read `01:23:45` format. You can also use `entity_id: all` and all active timers will be started. | Service data attribute | Optional | Description | | ---------------------- | -------- | ----------- | | `entity_id` | no | Name of the entity to take action, e.g., `timer.timer0`. | +| `duration` | yes | Duration in seconds or `01:23:45` format until the timer finishes. | ### Service `timer.change` From 5ab36ff1b20f63d23dbc32a61d17979788ec95c6 Mon Sep 17 00:00:00 2001 From: Bram Kragten Date: Tue, 5 Sep 2023 13:46:54 +0200 Subject: [PATCH 6/7] Update 2023-09-06-release-20239.markdown --- source/_posts/2023-09-06-release-20239.markdown | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/source/_posts/2023-09-06-release-20239.markdown b/source/_posts/2023-09-06-release-20239.markdown index 1a5df072209..ddeff688fca 100644 --- a/source/_posts/2023-09-06-release-20239.markdown +++ b/source/_posts/2023-09-06-release-20239.markdown @@ -139,6 +139,10 @@ Temporary screenshot that needs to be replaced.

+## 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. +

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 From ebaa73b493f06537690486ce385171d981bb7231 Mon Sep 17 00:00:00 2001 From: Bram Kragten Date: Tue, 5 Sep 2023 13:58:42 +0200 Subject: [PATCH 7/7] Update 2023-09-06-release-20239.markdown --- source/_posts/2023-09-06-release-20239.markdown | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/source/_posts/2023-09-06-release-20239.markdown b/source/_posts/2023-09-06-release-20239.markdown index ddeff688fca..a7e041bca38 100644 --- a/source/_posts/2023-09-06-release-20239.markdown +++ b/source/_posts/2023-09-06-release-20239.markdown @@ -471,12 +471,20 @@ 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)) +With this release, you will need to update your zwave-js-server instance. You must use zwave-js-server 1.31.0 or greater (schema 31). + +If you use the Z-Wave JS add-on, you need at least version 0.1.88. +If you use the Z-Wave JS UI add-on, you need at least version ??. +If you use the Z-Wave JS UI Docker container, you need at least version 8.23.2. +If you run your own Docker container or some other installation method, you will need to update your zwave-js-server instance to at least 1.31.0. + +([@raman325] - [#99250]) ([documentation](/integrations/zwave_js)) + [@raman325]: https://github.com/raman325 [#98140]: https://github.com/home-assistant/core/pull/98140 +[#99250]: https://github.com/home-assistant/core/pull/99250 {% enddetails %}