diff --git a/source/_integrations/ifttt.markdown b/source/_integrations/ifttt.markdown index 7e9e44f9f08..41cceed9735 100644 --- a/source/_integrations/ifttt.markdown +++ b/source/_integrations/ifttt.markdown @@ -12,7 +12,7 @@ ha_platforms: ha_integration_type: integration --- -[IFTTT](https://ifttt.com) is a web service that allows users to create chains of simple conditional statements, so-called "Applets". With the IFTTT component, you can trigger applets through the **"Webhooks"** service (which was previously the **"Maker"** channel). +[IFTTT](https://ifttt.com) is a web service that allows users to create chains of simple conditional statements, so-called "Applets". With the IFTTT integration, you can trigger applets through the **"Webhooks"** service (which was previously the **"Maker"** channel). ## Prerequisites diff --git a/source/_integrations/ihc.markdown b/source/_integrations/ihc.markdown index 537b30ad234..87ecd0b16f2 100644 --- a/source/_integrations/ihc.markdown +++ b/source/_integrations/ihc.markdown @@ -59,7 +59,7 @@ auto_setup: type: boolean default: true info: - description: Shows the IHC "name", "note" and "position" attributes of each component. This will make it easier to identify the IHC products within Home Assistant. + description: Shows the IHC "name", "note" and "position" attributes of each integration. This will make it easier to identify the IHC products within Home Assistant. required: false type: boolean default: true @@ -85,7 +85,7 @@ See the manual of each device type for configuration options. ## Binary Sensor -Before you can use the IHC Binary Sensor platform, you must setup the IHC Component. +Before you can use the IHC Binary Sensor platform, you must setup the IHC integration. When auto setup is enabled the following products will be found in the IHC project and setup as binary sensors: @@ -154,7 +154,7 @@ The resource id should be an id of a boolean IHC resource. For more information ## Sensor -Before you can use the IHC Sensor platform, you must setup the IHC Component. +Before you can use the IHC Sensor platform, you must setup the IHC integration. When auto setup is enabled the following products will be found in the IHC project and setup as sensors: @@ -212,7 +212,7 @@ The resource id should be a IHC float resource. For more information about IHC r ## Light -Before you can use the IHC Light platform, you must setup the IHC Component. +Before you can use the IHC Light platform, you must setup the IHC integration. When auto setup is enabled the following products will be found in the IHC project and setup as light devices: @@ -265,7 +265,7 @@ light: required: false type: integer name: - description: The name of the component + description: The name of the integration required: false type: string note: @@ -282,7 +282,7 @@ In the example above 12345 is ihc resource id and "tablelight" is the name. The ## Switch -Before you can use the IHC Switch platform, you must setup the IHC Component. +Before you can use the IHC Switch platform, you must setup the IHC integration. When auto setup is enabled the following products will be found in the ihc project and setup as switch devices: @@ -323,7 +323,7 @@ switch: required: false type: integer name: - description: The name of the component + description: The name of the integration required: false type: string note: diff --git a/source/_integrations/influxdb.markdown b/source/_integrations/influxdb.markdown index f9201749b40..9c20f787987 100644 --- a/source/_integrations/influxdb.markdown +++ b/source/_integrations/influxdb.markdown @@ -173,7 +173,7 @@ ignore_attributes: 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_measurement: type: string @@ -199,7 +199,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_measurement: type: string @@ -294,11 +294,11 @@ influxdb: ## Sensor -The `influxdb` sensor allows you to use values from an [InfluxDB](https://influxdb.com/) database to populate a sensor state. This can be used to present statistics as Home Assistant sensors, if used with the `influxdb` history component. It can also be used with an external data source. +The `influxdb` sensor allows you to use values from an [InfluxDB](https://influxdb.com/) database to populate a sensor state. This can be used to present statistics as Home Assistant sensors, if used with the `influxdb` history integration. It can also be used with an external data source.
- You must configure the `influxdb` history component in order to create `influxdb` sensors. If you just want to create sensors for an external InfluxDB database and you don't want Home Assistant to write any data to it you can exclude all entities like this: + You must configure the `influxdb` history integration in order to create `influxdb` sensors. If you just want to create sensors for an external InfluxDB database and you don't want Home Assistant to write any data to it you can exclude all entities like this: ```yaml influxdb: @@ -567,7 +567,7 @@ sensor: {% endraw %} -Note that when working with Flux queries, the resultset is broken into tables, you can see how this works in the Data Explorer of the UI. If you are operating on data created by the InfluxDB history component, this means by default, you will have a table for each entity and each attribute of each entity (other then `unit_of_measurement` and any others you promoted to tags). +Note that when working with Flux queries, the resultset is broken into tables, you can see how this works in the Data Explorer of the UI. If you are operating on data created by the InfluxDB history integration, this means by default, you will have a table for each entity and each attribute of each entity (other then `unit_of_measurement` and any others you promoted to tags). This is a lot more tables compared to 1.xx queries, where you essentially had one table per `unit_of_measurement` across all entities. You can still create aggregate metrics across multiple sensors though. As you can see in the example above, a good way to do this is with the [keep](https://v2.docs.influxdata.com/v2.0/reference/flux/stdlib/built-in/transformations/keep/) or [drop](https://v2.docs.influxdata.com/v2.0/reference/flux/stdlib/built-in/transformations/drop/) filters. When you remove key columns Influx merges tables, allowing you to make many tables that share a schema for `_value` into one. diff --git a/source/_integrations/intesishome.markdown b/source/_integrations/intesishome.markdown index 6c064d614f5..14cec3519bb 100644 --- a/source/_integrations/intesishome.markdown +++ b/source/_integrations/intesishome.markdown @@ -44,8 +44,8 @@ device: type: string {% endconfiguration %} -This component opens a TCP connection with the IntesisHome API to receive temperature and status updates, and to issue commands. -By default, the component will be named using the friendly device name from the IntesisHome website or application. +This integration opens a TCP connection with the IntesisHome API to receive temperature and status updates, and to issue commands. +By default, the integration will be named using the friendly device name from the IntesisHome website or application. If internet connectivity is lost, the device will be marked as unavailable after 5 minutes. ### Supported services diff --git a/source/_integrations/isy994.markdown b/source/_integrations/isy994.markdown index abccaa4d568..8a7b5a1c9cb 100644 --- a/source/_integrations/isy994.markdown +++ b/source/_integrations/isy994.markdown @@ -122,7 +122,7 @@ All `isy994_control` events will have an `entity_id` and `control` parameter in ### Insteon Scenes & Keypad/Remote Buttons -All Insteon scenes configured in the ISY Admin Console will show up as a `switch` in Home Assistant, as they do not support dimming or setting specific brightness settings as Home Assistant's `light` component. +All Insteon scenes configured in the ISY Admin Console will show up as a `switch` in Home Assistant, as they do not support dimming or setting specific brightness settings as Home Assistant's `light` integration. Insteon Secondary Keypad buttons and Remote buttons are added to Home Assistant to allow support for using Control Events in Automations. These devices are added as `sensors` since they cannot be directly controlled (turned on/off); their state is the last ON level command they sent, in a range from `0` (Off) to `255` (On 100%). Note: these devices may report incorrect states before being used after a reboot of the ISY. Secondary Keypad buttons may be turned on or off using ISY Scenes (refer to ISY Documentation for more details). diff --git a/source/_integrations/izone.markdown b/source/_integrations/izone.markdown index 40ee910e3d3..02209993c04 100644 --- a/source/_integrations/izone.markdown +++ b/source/_integrations/izone.markdown @@ -107,7 +107,7 @@ type: history-graph ## Debugging -If you're trying to track down issues with the component, set up logging for it: +If you're trying to track down issues with the integration, set up logging for it: ```yaml # Example configuration.yaml with logging for iZone diff --git a/source/_integrations/joaoapps_join.markdown b/source/_integrations/joaoapps_join.markdown index b0d498782af..035aa874b8e 100644 --- a/source/_integrations/joaoapps_join.markdown +++ b/source/_integrations/joaoapps_join.markdown @@ -13,10 +13,10 @@ ha_integration_type: integration --- The `joaoapps_join` integration exposes services from -[Join](https://joaoapps.com/join). In Home Assistant, the Join features are -divided up in two locations, the Join component, and the Join notify platform. -The notify platform allows us to send messages to Join devices, the component -allows us to access the other special features that Join offers. When in doubt, you can reference the [API documentation](https://joaoapps.com/join/api/) this is based on. +[Join](https://joaoapps.com/join). In Home Assistant, the Joaoapps Join features are +divided up in two locations, the Join integration, and the Joaoapps Join notify platform. +The notify platform allows us to send messages to Joaoapps Join devices, the integration +allows us to access the other special features that Joaoapps Join offers. When in doubt, you can reference the [API documentation](https://joaoapps.com/join/api/) this is based on. In the `configuration.yaml` file you need to provide the API key and device id or name of the target device. You can find your device id and API key @@ -57,7 +57,7 @@ device_names: required: false type: string name: - description: The name parameter is optional but needed if you want to use multiple notification platforms. The platform will be exposed as service `notify.`. The name will default to `notify` if not supplied. See the [Notifications integration](/integrations/notify) for more details. + description: The name parameter is optional but needed if you want to use multiple notification platforms. The platform will be exposed as service `notify.`. The name will default to `notify` if not supplied. See the [Notifications integration](/integrations/notify) for more details. required: false type: string {% endconfiguration %}