From d5505028271ed3d0a34a6fa026a568996d21ad04 Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Wed, 14 Jun 2023 15:53:05 +0200 Subject: [PATCH] P-integrations: replace term component by integration (#27815) --- source/_integrations/panel_iframe.markdown | 2 +- source/_integrations/plant.markdown | 4 ++-- source/_integrations/plugwise.markdown | 2 +- source/_integrations/prometheus.markdown | 6 +++--- source/_integrations/proxmoxve.markdown | 4 ++-- source/_integrations/pulseaudio_loopback.markdown | 4 ++-- source/_integrations/pushover.markdown | 6 +++--- 7 files changed, 14 insertions(+), 14 deletions(-) diff --git a/source/_integrations/panel_iframe.markdown b/source/_integrations/panel_iframe.markdown index 17c523ba8a8..e286e6324c3 100644 --- a/source/_integrations/panel_iframe.markdown +++ b/source/_integrations/panel_iframe.markdown @@ -37,7 +37,7 @@ panel_iframe: {% configuration %} panel_iframe: - description: Enables the panel_iframe component. Only allowed once. + description: Enables the panel_iframe integration. Only allowed once. required: true type: map keys: diff --git a/source/_integrations/plant.markdown b/source/_integrations/plant.markdown index b8903af5336..2d3951f11fe 100644 --- a/source/_integrations/plant.markdown +++ b/source/_integrations/plant.markdown @@ -9,7 +9,7 @@ ha_domain: plant ha_integration_type: integration --- -This`plant`component lets you merge moisture, conductivity, light intensity, temperature and battery level for a plant into a single UI element. It also supports setting minimum and maximum values for each measurement and will change its state to "problem" if it is not within those limits. +This`plant`integration lets you merge moisture, conductivity, light intensity, temperature and battery level for a plant into a single UI element. It also supports setting minimum and maximum values for each measurement and will change its state to "problem" if it is not within those limits. ## Configuration @@ -110,7 +110,7 @@ entity_id: ## Examples ### Using plain MQTT sensor to get the data This is a practical example that uses a multiple of `MQTT sensors` to supply the readings used by the `plant` sensor. -Another good source of this data would be the [Mi Flora](/integrations/miflora) component. +Another good source of this data would be the [Mi Flora](/integrations/miflora) integration. If the sensor data is within the min/max values the status will be `ok`, if not the status will be `problem`. You can use this to trigger a notification, if there is a problem with your plant. Of course you can only monitor attributes of your plant, where the sensor is configured and is providing the data. diff --git a/source/_integrations/plugwise.markdown b/source/_integrations/plugwise.markdown index 87fa8870d7d..07c67d8fe99 100644 --- a/source/_integrations/plugwise.markdown +++ b/source/_integrations/plugwise.markdown @@ -28,7 +28,7 @@ ha_platforms: ha_integration_type: hub --- -This enables [Plugwise](https://www.plugwise.com) components with a central Smile gateway to be integrated. This integration talks locally to your **Smile** interface, and you will need its password and IP address. +This enables [Plugwise](https://www.plugwise.com) integrations with a central Smile gateway to be integrated. This integration talks locally to your **Smile** interface, and you will need its password and IP address. The platform supports [Anna](https://www.plugwise.com/en_US/products/anna), [Adam (zonecontrol)](https://www.plugwise.com/en_US/zonecontrol), [P1](https://www.plugwise.com/en_US/products/smile-p1) Smile products and the [Stretch](https://www.plugwise.com/nl_NL/het-systeem) products. See below list for more details. Platforms available - depending on your Smile and setup include: diff --git a/source/_integrations/prometheus.markdown b/source/_integrations/prometheus.markdown index 3e9a279a66e..d3468fef069 100644 --- a/source/_integrations/prometheus.markdown +++ b/source/_integrations/prometheus.markdown @@ -68,7 +68,7 @@ override_metric: component_config: type: string required: false - description: This attribute contains component-specific override values. See [Customizing devices and services](/getting-started/customizing-devices/) for format. + description: This attribute contains integration-specific override values. See [Customizing devices and services](/getting-started/customizing-devices/) for format. keys: override_metric: type: string @@ -77,7 +77,7 @@ component_config: component_config_domain: type: string required: false - description: This attribute contains domain-specific component override values. See [Customizing devices and services](/getting-started/customizing-devices/) for format. + description: This attribute contains domain-specific integration override values. See [Customizing devices and services](/getting-started/customizing-devices/) for format. keys: override_metric: type: string @@ -86,7 +86,7 @@ component_config_domain: component_config_glob: type: string required: false - description: This attribute contains component-specific override values. See [Customizing devices and services](/getting-started/customizing-devices/) for format. + description: This attribute contains integration-specific override values. See [Customizing devices and services](/getting-started/customizing-devices/) for format. keys: override_metric: type: string diff --git a/source/_integrations/proxmoxve.markdown b/source/_integrations/proxmoxve.markdown index 6abc3d30658..a662ac5b4ab 100644 --- a/source/_integrations/proxmoxve.markdown +++ b/source/_integrations/proxmoxve.markdown @@ -16,7 +16,7 @@ ha_integration_type: integration [Proxmox VE](https://www.proxmox.com/en/) is an open-source server virtualization environment. This integration allows you to poll various data from your instance. -After configuring this component, the binary sensors automatically appear. +After configuring this integration, the binary sensors automatically appear. ## Configuration @@ -24,7 +24,7 @@ After configuring this component, the binary sensors automatically appear. You should have at least one VM or container entry configured, else this integration won't do anything. -To use the `proxmoxve` component, add the following configuration to your `configuration.yaml` file: +To use the `proxmoxve` integration, add the following configuration to your `configuration.yaml` file: ```yaml # Example configuration.yaml entry diff --git a/source/_integrations/pulseaudio_loopback.markdown b/source/_integrations/pulseaudio_loopback.markdown index a3b5a276015..1741913c470 100644 --- a/source/_integrations/pulseaudio_loopback.markdown +++ b/source/_integrations/pulseaudio_loopback.markdown @@ -13,7 +13,7 @@ ha_integration_type: integration The goal behind this switch is to allow a very flexible whole home audio system based upon [PulseAudio](https://www.freedesktop.org/wiki/Software/PulseAudio/). -For example, for a system with a 7.1 surround sound card, and 3 instances of [MPD](https://www.musicpd.org/) running, it is possible to quickly route the output of any MPD instance to any of the 8 possible (4 stereo) channels on the sound card, by loading/unloading a loopback module. This loading/unloading functionality is provided by this component. When the switch is `on`, the loopback module is loaded. When the switch is `off`, the module is not loaded. +For example, for a system with a 7.1 surround sound card, and 3 instances of [MPD](https://www.musicpd.org/) running, it is possible to quickly route the output of any MPD instance to any of the 8 possible (4 stereo) channels on the sound card, by loading/unloading a loopback module. This loading/unloading functionality is provided by this integration. When the switch is `on`, the loopback module is loaded. When the switch is `off`, the module is not loaded. The benefit of this approach is that this audio routing can occur without modifying the design-time configuration of MPD or PulseAudio. @@ -55,6 +55,6 @@ port:
-This integration relies on raw TCP commands to PulseAudio. In order for PulseAudio to accept commands with this component, `module-native-protocol-tcp auth-ip-acl=` must be loaded on the PulseAudio server. +This integration relies on raw TCP commands to PulseAudio. In order for PulseAudio to accept commands with this integration, `module-native-protocol-tcp auth-ip-acl=` must be loaded on the PulseAudio server.
diff --git a/source/_integrations/pushover.markdown b/source/_integrations/pushover.markdown index 906bf186f5d..a9a357eb55c 100644 --- a/source/_integrations/pushover.markdown +++ b/source/_integrations/pushover.markdown @@ -14,11 +14,11 @@ ha_codeowners: - '@engrbm87' --- -The [Pushover service](https://pushover.net/) is a platform for the notify component. This allows integrations to send messages to the user using Pushover. +The [Pushover service](https://pushover.net/) is a platform for the notify integration. This allows integrations to send messages to the user using Pushover. ## Configuration -In order to get an API key you need to [register an application](https://pushover.net/apps/clone/home_assistant) on the Pushover website. Your Pushover user key can be found on the [Pushover dashboard](https://pushover.net/dashboard). +In order to get an API key, you need to [register an application](https://pushover.net/apps/clone/home_assistant) on the Pushover website. Your Pushover user key can be found on the [Pushover dashboard](https://pushover.net/dashboard). {% include integrations/config_flow.md %} @@ -36,7 +36,7 @@ Example Automation: attachment: "local/image.png" ``` -Component specific values in the nested `data` section are optional. +Integration-specific values in the nested `data` section are optional. Image attachments can be added using the `attachment` parameter, which can either be a local file reference (ex: `/tmp/image.png`).