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-09 18:36:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

S-integrations, 02: replace term component by integration (#27819)

Browse Source
This commit is contained in:
c0ffeeca7 2023-06-14 15:50:53 +02:00 committed by GitHub
parent 6459825107
commit 0006d11324
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
7 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
source/_integrations/simulated.markdown
View File

@ -1,6 +1,6 @@
---
title: Simulated
description: Component for simulating a numerical sensor.
description: Integration for simulating a numerical sensor.
ha_category:
- Sensor
- Utility

2
source/_integrations/sisyphus.markdown
View File

@ -25,7 +25,7 @@ There is currently support for the following device types within Home Assistant:
The Light and Media players will be automatically added for each of your Sisyphus tables, if the Sisyphus integration is configured.
There are two ways to configure this component. For the automatic discovery of your table(s), simply add the following to your `configuration.yaml`:
There are two ways to configure this integration. For the automatic discovery of your table(s), add the following to your `configuration.yaml`:
```yaml
# This will auto-detect all Sisyphus tables on your local network.

2
source/_integrations/snapcast.markdown
View File

@ -20,7 +20,7 @@ The Snapcast integration allows you to control [Snapcast](https://github.com/bad
## Services
The snapcast components provides a few services registered under the media_player component.
The snapcast integration provides a few services registered under the media_player integration.
### Service `snapcast.snapshot`

2
source/_integrations/snips.markdown
View File

@ -141,7 +141,7 @@ Alternatively, MQTT can be configured to bridge messages between servers if usin
### Triggering actions
In Home Assistant, we trigger actions based on intents produced by Snips using the [`intent_script`](/integrations/intent_script) component. For instance, the following block handles a `ActivateLightColor` intent to change light colors:
In Home Assistant, we trigger actions based on intents produced by Snips using the [`intent_script`](/integrations/intent_script) integration. For instance, the following block handles a `ActivateLightColor` intent to change light colors:
Note: If your Snips action is prefixed with a username (e.g., `john:playmusic` or `john__playmusic`), the Snips integration in Home Assistant will try and strip off the username. Bear this in mind if you get the error `Received unknown intent` even when what you see on the MQTT bus looks correct. Internally the Snips integration is trying to match the non-username version of the intent (i.e., just `playmusic`).

4
source/_integrations/solaredge_local.markdown
View File

@ -15,7 +15,7 @@ ha_platforms:
ha_integration_type: integration
---
The `solaredge_local` platform uses the local API available on some SolarEdge Inverters to allow you to get details from your SolarEdge solar power setup and integrate these into your Home Assistant installation.
The `solaredge_local` integration uses the local API available on some SolarEdge Inverters to allow you to get details from your SolarEdge solar power setup and integrate these into your Home Assistant installation.
Only specific models support the local API. The local API is available on inverters that do not have an LCD character screen. You can also check the datasheets if in the section "Additional Features", sub-section "Inverter Commissioning" is present the following line "With the SetApp mobile application using built-in Wi-Fi access point for local connection". These inverters also have a part number that ends with a 4. For example: SEXXK-XXXXXBXX4 or SEXXXXH-XXXXXBXX4
@ -23,7 +23,7 @@ You can check if the local API works by finding the IP address of your inverter
<div class='note'>
Recent firmware updates have disabled the local API on many inverters. Please enter the IP address of your inverter in a browser before attempting to use this component. If the local API is enabled, you'll see a web page with the SolarEdge logo and a "Commissioning" menu. See [this issue](https://github.com/jbuehl/solaredge/issues/124) and [this issue](https://github.com/drobtravels/solaredge-local/issues/24) for additional details.
Recent firmware updates have disabled the local API on many inverters. Please enter the IP address of your inverter in a browser before attempting to use this integration. If the local API is enabled, you'll see a web page with the SolarEdge logo and a "Commissioning" menu. See [this issue](https://github.com/jbuehl/solaredge/issues/124) and [this issue](https://github.com/drobtravels/solaredge-local/issues/24) for additional details.
If your inverter does not support the local API, you can use the [cloud based version](/integrations/solaredge/)

2
source/_integrations/spaceapi.markdown
View File

@ -264,7 +264,7 @@ The list of sensors can be any sensor, not just temperature or humidity.
## Examples
In this section you find some real-life examples of how to use this component.
In this section you find some real-life examples of how to use this integration.
### Eastermundigen

2
source/_integrations/speedtestdotnet.markdown
View File

@ -39,7 +39,7 @@ Please be aware of the potential [inconsistencies](https://github.com/sivel/spee
## Examples
In this section you will find some real-life examples of how to use this component.
In this section you will find some real-life examples of how to use this integration.
### Using as a trigger in an automation
{% raw %}