From 98c1851b4b03db5e8c22e0d3c0637956c1604e62 Mon Sep 17 00:00:00 2001 From: Erik Montnemery Date: Wed, 6 Mar 2024 11:35:36 +0100 Subject: [PATCH] Document changes in integration_entities (#31697) Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> --- source/_docs/configuration/templating.markdown | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/source/_docs/configuration/templating.markdown b/source/_docs/configuration/templating.markdown index 21e11ffcdee..ebd6bf6065b 100644 --- a/source/_docs/configuration/templating.markdown +++ b/source/_docs/configuration/templating.markdown @@ -508,10 +508,12 @@ The same thing can also be expressed as a test: {% endraw %} -### Integrations +### Entities for an integration - `integration_entities(integration)` returns a list of entities that are associated with a given integration, such as `hue` or `zwave_js`. -- `integration_entities(title)` if you have multiple instances set-up for an integration, you can also use the title you've set for the integration in case you only want to target a specific device bridge. +- `integration_entities(config_entry_title)` if you have multiple entries set-up for an integration, you can also use the title you've set for the integration in case you only want to target a specific entry. + +If there is more than one entry with the same title, the entities for all the matching entries will be returned, even if the entries are for different integrations. It's not possible to search for entities of an untitled integration. #### Integrations examples