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-17 06:16:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix ha_release and other minor issues

Browse Source
This commit is contained in:
Fabian Affolter 2016-05-21 11:39:02 +02:00
parent 2b3c56017d
commit 03ca0b369e
10 changed files with 27 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
source/_components/media_player.gpmdp.markdown
View File

@ -10,7 +10,7 @@ footer: true
logo: gpmdp.png logo: gpmdp.png
ha_category: Media Player ha_category: Media Player
ha_iot_class: "Local Polling" ha_iot_class: "Local Polling"
ha_release: 0.20 ha_release: "0.20"
--- ---

2
source/_components/media_player.lg_netcast.markdown
View File

@ -10,7 +10,7 @@ footer: true
logo: lg.png logo: lg.png
ha_category: Media Player ha_category: Media Player
ha_iot_class: "Local Poll" ha_iot_class: "Local Poll"
ha_release: 0.20 ha_release: "0.20"
--- ---
The `lg_netcast` platform allows you to control a LG Smart TV running NetCast 3.0 (LG Smart TV models released in 2012) and NetCast 4.0 (LG Smart TV models released in 2013). For the new LG WebOS TV's use the [webostv](/components/mediaplayer.webostv) platform. The `lg_netcast` platform allows you to control a LG Smart TV running NetCast 3.0 (LG Smart TV models released in 2012) and NetCast 4.0 (LG Smart TV models released in 2013). For the new LG WebOS TV's use the [webostv](/components/mediaplayer.webostv) platform.

2
source/_components/media_player.roku.markdown
View File

@ -9,7 +9,7 @@ sharing: true
footer: true footer: true
logo: roku.png logo: roku.png
ha_category: Media Player ha_category: Media Player
ha_release: 0.20 ha_release: "0.20"
--- ---
The [Roku](http://www.roku.com/) media players will be automatically discovered if you enable the [discovery component](/components/discovery/). The [Roku](http://www.roku.com/) media players will be automatically discovered if you enable the [discovery component](/components/discovery/).

9
source/_components/notify.aws_lambda.markdown
View File

@ -9,10 +9,12 @@ sharing: true
footer: true footer: true
logo: aws_lambda.png logo: aws_lambda.png
ha_category: Notifications ha_category: Notifications
ha_release: 0.20 ha_release: "0.20"
--- ---
The AWS Lambda notify platform enables invoking [AWS Lambda](https://aws.amazon.com/lambda/) functions. The `aws_lambda` notification platform enables invoking [AWS Lambda](https://aws.amazon.com/lambda/) functions.
To use this notification platform in your installation, add the following to your `configuration.yaml` file:
### Configuration ### Configuration
@ -25,7 +27,6 @@ notify:
aws_secret_access_key: AWS_SECRET_ACCESS_KEY aws_secret_access_key: AWS_SECRET_ACCESS_KEY
profile_name: AWS_PROFILE profile_name: AWS_PROFILE
region_name: 'us-east-1' region_name: 'us-east-1'
# Optional
context: context:
... ...
``` ```
@ -39,7 +40,7 @@ Configuration variables:
- **name** (*Optional*): Setting the optional parameter `name` allows multiple notifiers to be created. The default value is `notify`. The notifier will bind to the service `notify.NOTIFIER_NAME`. - **name** (*Optional*): Setting the optional parameter `name` allows multiple notifiers to be created. The default value is `notify`. The notifier will bind to the service `notify.NOTIFIER_NAME`.
- **context** (*Optional*): An optional dictionary you can provide to pass custom context through to the Lambda function. The `context` dictionary (if any) is combined with the same data available at the `/api/config` HTTP API route. - **context** (*Optional*): An optional dictionary you can provide to pass custom context through to the Lambda function. The `context` dictionary (if any) is combined with the same data available at the `/api/config` HTTP API route.
### Usage ### {% linkable_title Usage %}
AWS Lambda is a notify platform and thus can be controlled by calling the notify service [as described here](/components/notify/). It will invoke a Lambda for all targets given in the notification payload. A target can be formatted as a function name, an entire ARN ([Amazon Resource Name](http://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html)) or a partial ARN. For more information, please see the [boto3 docs](http://boto3.readthedocs.io/en/latest/reference/services/lambda.html#Lambda.Client.invoke). AWS Lambda is a notify platform and thus can be controlled by calling the notify service [as described here](/components/notify/). It will invoke a Lambda for all targets given in the notification payload. A target can be formatted as a function name, an entire ARN ([Amazon Resource Name](http://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html)) or a partial ARN. For more information, please see the [boto3 docs](http://boto3.readthedocs.io/en/latest/reference/services/lambda.html#Lambda.Client.invoke).

8
source/_components/notify.aws_sns.markdown
View File

@ -9,12 +9,12 @@ sharing: true
footer: true footer: true
logo: aws_sns.png logo: aws_sns.png
ha_category: Notifications ha_category: Notifications
ha_release: 0.20 ha_release: "0.20"
--- ---
The AWS SNS notify platform enables publishing to an [AWS SNS](https://aws.amazon.com/sns/) topic or application. The `aws_sns` notification platform enables publishing to an [AWS SNS](https://aws.amazon.com/sns/) topic or application.
### Configuration To use this notification platform in your installation, add the following to your `configuration.yaml` file:
```yaml ```yaml
# Example configuration.yaml entry # Example configuration.yaml entry
@ -35,7 +35,7 @@ Configuration variables:
- **region_name** (*Required*): The region identifier to connect to. The default is `us-east-1`. - **region_name** (*Required*): The region identifier to connect to. The default is `us-east-1`.
- **name** (*Optional*): Setting the optional parameter `name` allows multiple notifiers to be created. The default value is `notify`. The notifier will bind to the service `notify.NOTIFIER_NAME`. - **name** (*Optional*): Setting the optional parameter `name` allows multiple notifiers to be created. The default value is `notify`. The notifier will bind to the service `notify.NOTIFIER_NAME`.
### Usage ### {% linkable_title Usage %}
AWS SNS is a notify platform and thus can be controlled by calling the notify service [as described here](/components/notify/). It will publish a message to all targets given in the notification payload. A target must be a SNS topic or endpoint ARN ([Amazon Resource Name](http://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html)). For more information, please see the [boto3 docs](http://boto3.readthedocs.io/en/latest/reference/services/sns.html#SNS.Client.publish). AWS SNS is a notify platform and thus can be controlled by calling the notify service [as described here](/components/notify/). It will publish a message to all targets given in the notification payload. A target must be a SNS topic or endpoint ARN ([Amazon Resource Name](http://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html)). For more information, please see the [boto3 docs](http://boto3.readthedocs.io/en/latest/reference/services/sns.html#SNS.Client.publish).

8
source/_components/notify.aws_sqs.markdown
View File

@ -9,12 +9,12 @@ sharing: true
footer: true footer: true
logo: aws_sqs.png logo: aws_sqs.png
ha_category: Notifications ha_category: Notifications
ha_release: 0.20 ha_release: "0.20"
--- ---
The AWS SQS notify platform enables publishing to an [AWS SQS](https://aws.amazon.com/sqs/) message queue. The `aws_sqs` notification platform enables publishing to an [AWS SQS](https://aws.amazon.com/sqs/) message queue.
### Configuration To use this notification platform in your installation, add the following to your `configuration.yaml` file:
```yaml ```yaml
# Example configuration.yaml entry # Example configuration.yaml entry
@ -35,7 +35,7 @@ Configuration variables:
- **region_name** (*Required*): The region identifier to connect to. The default is `us-east-1`. - **region_name** (*Required*): The region identifier to connect to. The default is `us-east-1`.
- **name** (*Optional*): Setting the optional parameter `name` allows multiple notifiers to be created. The default value is `notify`. The notifier will bind to the service `notify.NOTIFIER_NAME`. - **name** (*Optional*): Setting the optional parameter `name` allows multiple notifiers to be created. The default value is `notify`. The notifier will bind to the service `notify.NOTIFIER_NAME`.
### Usage ### {% linkable_title Usage %}
AWS SQS is a notify platform and thus can be controlled by calling the notify service [as described here](/components/notify/). It will publish a message to the queue for all targets given in the notification payload. A target must be a SQS topic URL. For more information, please see the [SQS docs](http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/ImportantIdentifiers.html). AWS SQS is a notify platform and thus can be controlled by calling the notify service [as described here](/components/notify/). It will publish a message to the queue for all targets given in the notification payload. A target must be a SQS topic URL. For more information, please see the [SQS docs](http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/ImportantIdentifiers.html).

9
source/_components/notify.ecobee.markdown
View File

@ -1,7 +1,7 @@
--- ---
layout: page layout: page
title: "Ecobee Notify" title: "Ecobee Notify"
description: "Instructions how to setup the Ecobee notify component within Home Assistant." description: "Instructions how to setup the Ecobee notification component within Home Assistant."
date: 2016-05-12 09:00 date: 2016-05-12 09:00
sidebar: true sidebar: true
comments: false comments: false
@ -9,12 +9,12 @@ sharing: true
footer: true footer: true
logo: ecobee.png logo: ecobee.png
ha_category: Notify ha_category: Notify
ha_release: 0.20 ha_release: "0.20"
--- ---
To get your Ecobee sensors working with Home Assistant, you must first have the main [Ecobee component](/components/ecobee/) loaded and running. Once you have that configured, you can setup this component to send messages to your thermostat. To get your Ecobee notifications working with Home Assistant, you must first have the main [Ecobee component](/components/ecobee/) loaded and running. Once you have that configured, you can setup this component to send messages to your Ecobee device.
Add the following to your `configuration.yaml` file: To use this notification platform in your installation, add the following to your `configuration.yaml` file:
```yaml ```yaml
# Example configuration.yaml entry # Example configuration.yaml entry
@ -26,7 +26,6 @@ notify:
Configuration variables: Configuration variables:
- **name** (*Optional*): Setting the optional parameter `name` allows multiple notifiers to be created. The default value is `notify`. The notifier will bind to the service `notify.NOTIFIER_NAME`. - **name** (*Optional*): Setting the optional parameter `name` allows multiple notifiers to be created. The default value is `notify`. The notifier will bind to the service `notify.NOTIFIER_NAME`.
- **index** (*Optional*): If you have more than one thermostat, you can create a notifier for each one by providing the zero based index for each thermostat. (Default: 0)
To use notifications, please see the [getting started with automation page](/getting-started/automation/). To use notifications, please see the [getting started with automation page](/getting-started/automation/).

6
source/_components/notify.twilio_sms.markdown
View File

@ -9,12 +9,12 @@ sharing: true
footer: true footer: true
logo: twilio.png logo: twilio.png
ha_category: Notifications ha_category: Notifications
ha_release: 0.20 ha_release: "0.20"
--- ---
The `twilio` notify platform enables sending notifications via SMS, powered by [Twilio](https://twilio.com). The `twilio` notification platform enables sending notifications via SMS, powered by [Twilio](https://twilio.com).
To use this nofification in your installation, add the following to your `configuration.yaml` file: To use this notification platform in your installation, add the following to your `configuration.yaml` file:
```yaml ```yaml
# Example configuration.yaml entry # Example configuration.yaml entry

2
source/_components/sensor.lastfm.markdown
View File

@ -10,7 +10,7 @@ footer: true
logo: lastfm.png logo: lastfm.png
ha_category: Sensor ha_category: Sensor
ha_iot_class: "Cloud Polling" ha_iot_class: "Cloud Polling"
ha_release: 0.20 ha_release: "0.20"
--- ---

4
source/_components/sensor.supervisord.markdown
View File

@ -8,11 +8,13 @@ comments: false
sharing: true sharing: true
footer: true footer: true
ha_category: Sensor ha_category: Sensor
ha_release: 0.20 ha_release: "0.20"
--- ---
The `supervisord` platform allows you to track the states of [Supervisor](http://supervisord.org/). The `supervisord` platform allows you to track the states of [Supervisor](http://supervisord.org/).
To use this sensor in your installation, add the following to your `configuration.yaml` file:
```yaml ```yaml
# Example configuration.yaml entry # Example configuration.yaml entry
sensor: sensor: