mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-06-18 08:06:52 +00:00
Integrations starting with a-c: Replace component by integration (#27784)
This commit is contained in:
c0ffeeca7
GitHub
parent
b9a6488c3d
commit
a22ddc4cf0
@ -35,7 +35,7 @@ light:
|
||||
- platform: avion
|
||||
```
|
||||
|
||||
There are two ways to configure this component: username & password, or list of devices. You must choose one.
|
||||
There are two ways to configure this integration: username & password, or list of devices. You must choose one.
|
||||
|
||||
{% configuration %}
|
||||
username:
|
||||
|
||||
@ -17,7 +17,7 @@ The `aws` integration provides a single place to interact with [Amazon Web Servi
|
||||
|
||||
You have to have an AWS account to use Amazon Web Services, create one [here](https://aws.amazon.com/free/) with a 12 months free tier benefit. Please note, even in the first 12-months, you may still be billed if you use more resources than offered in the free tier. We advise you to monitor your costs in the [AWS Billing Console](https://console.aws.amazon.com/billing/) closely. You can read the [Control your AWS costs](https://aws.amazon.com/getting-started/hands-on/control-your-costs-free-tier-budgets/) guide for more information.
|
||||
|
||||
The `lambda`, `sns`, `sqs`, and `events` services, used in the `aws` component, all provide an **Always Free** tier for all users even after the 12-month period. The general usage in Home Automation will most likely not reach the free tier limit. Please read [Lambda Pricing](https://aws.amazon.com/lambda/pricing/), [SNS Pricing](https://aws.amazon.com/sns/pricing/), [SQS Pricing](https://aws.amazon.com/sqs/pricing/), and [EventBridge Pricing](https://aws.amazon.com/eventbridge/pricing/) for more details.
|
||||
The `lambda`, `sns`, `sqs`, and `events` services, used in the `aws` integration, all provide an **Always Free** tier for all users even after the 12-month period. The general usage in Home Automation will most likely not reach the free tier limit. Please read [Lambda Pricing](https://aws.amazon.com/lambda/pricing/), [SNS Pricing](https://aws.amazon.com/sns/pricing/), [SQS Pricing](https://aws.amazon.com/sqs/pricing/), and [EventBridge Pricing](https://aws.amazon.com/eventbridge/pricing/) for more details.
|
||||
|
||||
The `aws` integration is using [botocore](https://botocore.amazonaws.com/v1/documentation/api/latest/index.html) to communicate with Amazon Web Services, which is also used by the [AWS Command Client Interface](https://aws.amazon.com/cli/) tool. Therefore, `aws` shares the same credential and profiles with `awscli` tool. Please read [Configuring the AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html) to learn how to get access keys and how to manage them on your local system securely.
|
||||
|
||||
|
||||
@ -131,4 +131,4 @@ monitored_conditions:
|
||||
description: Voltage
|
||||
{% endconfiguration %}
|
||||
|
||||
More conditions are available using the [BloomSky binary sensor](#binary-sensor) component.
|
||||
More conditions are available using the [BloomSky binary sensor](#binary-sensor) integration.
|
||||
|
||||
@ -14,7 +14,7 @@ The `browser` integration provides a service to open URLs in the default browser
|
||||
|
||||
## Configuration
|
||||
|
||||
To load this component, add the following lines to your `configuration.yaml`:
|
||||
To load this integration, add the following lines to your `configuration.yaml`:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
||||
@ -21,7 +21,7 @@ ha_integration_type: integration
|
||||
|
||||
The Buienradar integration uses [buienradar.nl](https://buienradar.nl/) as a source for current meteorological data for your location. The weather forecast is delivered by Buienradar, who provides a web service that provides detailed weather information for users in The Netherlands.
|
||||
|
||||
The relevant weather station used will be automatically selected based on the location specified in the Home Assistant configuration (or in the Buienradar weather/sensor component). A map of all available weather stations can be found [here](https://www.google.com/maps/d/embed?mid=1NivHkTGQUOs0dwQTnTMZi8Uatj0).
|
||||
The relevant weather station used will be automatically selected based on the location specified in the Home Assistant configuration (or in the Buienradar weather/sensor integration). A map of all available weather stations can be found [here](https://www.google.com/maps/d/embed?mid=1NivHkTGQUOs0dwQTnTMZi8Uatj0).
|
||||
|
||||
Besides the weather platform, there is currently support for the following additional device types:
|
||||
|
||||
@ -34,7 +34,7 @@ Besides the weather platform, there is currently support for the following addit
|
||||
|
||||
The `buienradar` camera platform uses [buienradar.nl](https://buienradar.nl/) as a source for the last rain radar map. The overview image of the whole of the Netherlands is loaded and shown as a camera in Home Assistant. The Netherlands is the default country and can be changed to Belgium (see [Options](#options)).
|
||||
|
||||
Internally this component uses the radar map image as [documented](https://www.buienradar.nl/overbuienradar/gratis-weerdata) on buienradar.nl.
|
||||
Internally, this integration uses the radar map image as [documented](https://www.buienradar.nl/overbuienradar/gratis-weerdata) on buienradar.nl.
|
||||
The downloaded image is cached to prevent Home Assistant from making a new request to buienradar.nl multiple times a minute when Home Assistant checks for new stills from the camera.
|
||||
|
||||
The camera entity is added disabled by default and should first be enabled before it starts reading the camera images.
|
||||
|
||||
@ -36,7 +36,7 @@ Passing the key `color_extract_url` to the service call will download the linked
|
||||
|
||||
<div class="note">
|
||||
|
||||
Please ensure any [external URLs](/docs/configuration/basic/#allowlist_external_urls) or [external files](/docs/configuration/basic/#allowlist_external_dirs) are authorized for use, you will receive error messages if this component is not allowed access to these external resources.
|
||||
Please ensure any [external URLs](/docs/configuration/basic/#allowlist_external_urls) or [external files](/docs/configuration/basic/#allowlist_external_dirs) are authorized for use. You will receive error messages if this integration is not allowed access to these external resources.
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
@ -44,7 +44,7 @@ This section enables you to control Home Assistant from within Home Assistant. C
|
||||
|
||||
### Persons
|
||||
|
||||
This section enables you to associate users with their device tracker entities using the person component.
|
||||
This section enables you to associate users with their device tracker entities using the person integration.
|
||||
|
||||
### Entities
|
||||
|
||||
|
||||
@ -21,6 +21,6 @@ The configurator integration allows integrations to request information from the
|
||||
- Input fields can be defined with a description, and optional type
|
||||
- It will trigger a callback when the button is pressed
|
||||
|
||||
The Hue integration in [the demo](/demo) and Plex are implemented using the configurator. See [the source of the demo integration](https://github.com/home-assistant/home-assistant/tree/dev/homeassistant/components/demo) for a simple example.
|
||||
The Hue integration in [the demo](https://demo.home-assistant.io/) and Plex are implemented using the configurator. See [the source of the demo integration](https://github.com/home-assistant/home-assistant/tree/dev/homeassistant/components/demo) for a simple example.
|
||||
|
||||
See [the source](https://github.com/home-assistant/home-assistant/tree/dev/homeassistant/components/configurator) for more details on how to use the configurator integration.
|
||||
|
||||
@ -166,7 +166,7 @@ cover:
|
||||
name: non_kaku_not_inverted_by_default
|
||||
```
|
||||
|
||||
The configuration above shows that the `type` property may be omitted. When the ID starts with `newkaku`, the component will make sure that the on and off commands are inverted. When the ID does not start with `newkaku`, the on and off commands are not inverted.
|
||||
The configuration above shows that the `type` property may be omitted. When the ID starts with `newkaku`, the integration will make sure that the on and off commands are inverted. When the ID does not start with `newkaku`, the on and off commands are not inverted.
|
||||
|
||||
## Setting up a non-RTS cover
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user