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-10 02:46:53 +00:00
Code Issues Packages Projects Releases Wiki Activity

E-integrations: Rename component to integration (#27786)

Browse Source
This commit is contained in:
c0ffeeca7 2023-06-13 15:21:37 +02:00 committed by GitHub
parent 08c130ab7a
commit d51347eafd
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
7 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
source/_integrations/ebusd.markdown
View File

@ -11,7 +11,7 @@ ha_platforms:
ha_integration_type: integration
---
Integration between [ebusd](https://github.com/john30/ebusd/) daemon for communication with eBUS heating systems, and Home Assistant using sensor component.
Integration between the [ebusd](https://github.com/john30/ebusd/) daemon (used for communication with the eBUS heating systems), and Home Assistant. The ebusd integrations uses the sensor integration.
## Configuration

4
source/_integrations/ecovacs.markdown
View File

@ -62,7 +62,7 @@ The library that talks to the Ecovacs servers is in a very early state and still
Please see the [py-sucks library documentation](https://github.com/mib1185/py-sucks) for some more information about what has been tested, and check out the GitHub issues to see if the issue you're having is known or being worked on.
If you have an issue with the Ecovacs component, please file a [GitHub Issue](https://github.com/home-assistant/home-assistant/issues) and include your Home Assistant logs in the report. To get full debug output from both the Ecovacs integration and the underlying `sucks` library, place this in your `configuration.yaml` file:
If you have an issue with the Ecovacs integration, please file a [GitHub Issue](https://github.com/home-assistant/home-assistant/issues) and include your Home Assistant logs in the report. To get full debug output from both the Ecovacs integration and the underlying `sucks` library, place this in your `configuration.yaml` file:
```yaml
logger:
@ -79,7 +79,7 @@ logger:
The `ecovacs` vacuum platform allows you to monitor and control your Ecovacs Deebot vacuums.
### Component Lifespans
### Integration lifespan
The remaining lifespan of components on your Deebot vacuum will be reported as attributes on the vacuum entity. The value will be a whole number representing the percentage of life remaining.

2
source/_integrations/eight_sleep.markdown
View File

@ -104,4 +104,4 @@ script:
## Notice
Please note this component relies on an undocumented API utilized by the Eight Sleep mobile app to communicate with the Eight Sleep servers. It is not supported by Eight Sleep and may malfunction if changes are made to either the mobile app operation or the API format.
This integration relies on an undocumented API utilized by the Eight Sleep mobile app to communicate with the Eight Sleep servers. It is not supported by Eight Sleep and may malfunction if changes are made to either the mobile app operation or the API format.

2
source/_integrations/emoncms_history.markdown
View File

@ -34,7 +34,7 @@ url:
required: true
type: string
inputnode:
description: Input node that will be used inside Emoncms. Please make sure you use a dedicated, not used before, node for this component!
description: Input node that will be used inside Emoncms. Please make sure you use a dedicated, not used before, node for this integration!
required: true
type: integer
whitelist:

4
source/_integrations/envisalink.markdown
View File

@ -28,7 +28,7 @@ There is currently support for the following device types within Home Assistant:
- Sensor: Emulates an alphanumeric keypad attached to the alarm panel
- Alarm Control Panel: Reports on partition status, and can be used to arm/disarm the system
This is a fully event-based component. Any event sent by the Envisalink device will be immediately reflected within Home Assistant.
This is a fully event-based integration. Any event sent by the Envisalink device will be immediately reflected within Home Assistant.
As of 0.29, the alarm_trigger service is supported. It is possible to fire off an envisalink-based alarm directly from Home Assistant. For example, a newer Z-Wave/Zigbee sensor can now be integrated into a legacy alarm system using a Home Assistant automation.
@ -112,7 +112,7 @@ panic_type:
default: Police
type: string
zones:
description: "Envisalink boards have no way to tell us which zones are actually in use, so each zone must be configured in Home Assistant. Zone numbers correspond to the zone numbers configured on your alarm system and must be in the range of 1 to 64. For each zone, at least a name must be given. For more information about the visual representation of a zone, take a look at the [Binary Sensor](/integrations/binary_sensor/#device-class) documentation. *Note: If no zones are specified, Home Assistant will not load any binary_sensor components.*"
description: "Envisalink boards have no way to tell us which zones are actually in use, so each zone must be configured in Home Assistant. Zone numbers correspond to the zone numbers configured on your alarm system and must be in the range of 1 to 64. For each zone, at least a name must be given. For more information about the visual representation of a zone, take a look at the [Binary Sensor](/integrations/binary_sensor/#device-class) documentation. *Note: If no zones are specified, Home Assistant will not load any binary_sensor integrations.*"
required: false
type: integer
keys:

2
source/_integrations/escea.markdown
View File

@ -34,7 +34,7 @@ Fireplace on / off, fan settings, and desired temperature settings are supported
## 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 this integration, set up logging for it:
```yaml
# Example configuration.yaml with logging for Escea

2
source/_integrations/ezviz.markdown
View File

@ -24,7 +24,7 @@ ha_integration_type: integration
The `ezviz` sensor platform uses the ezvizlife.com API to interact with the devices.
It also exposes an RTSP stream, by using the local camera IPs (so the device hosting Home Assistant has to be able to access the local IP of the cameras).
As there is no official documentation for the API, the component retrieves data from the API used in the EZVIZ mobile app, [hosted here](https://apiieu.ezvizlife.com).
As there is no official documentation for the API, the integration retrieves data from the API used in the EZVIZ mobile app, [hosted here](https://apiieu.ezvizlife.com).
The password for each camera is usually written near the QR code. This could be underneath the device or in the user manual. It is usually referred to as the camera "verification code".