Merge branch 'current' into next
This commit is contained in:
Paulus Schoutsen
commit
4c1c60df29
55 changed files with 421 additions and 159 deletions
|
|
@ -9,17 +9,18 @@ sharing: true
|
|||
footer: true
|
||||
logo: apiai.png
|
||||
ha_category: Voice
|
||||
featured: true
|
||||
ha_release: 0.37
|
||||
featured: false
|
||||
ha_release: 0.38
|
||||
---
|
||||
|
||||
This component is designed to be used with the "webhook" integration in api.ai. When a conversation ends with an user, api.ai sends an action and parameters to the webhook.
|
||||
This component is designed to be used with the "webhook" integration in [api.ai][apiai-web]. When a conversation ends with an user, api.ai sends an action and parameters to the webhook.
|
||||
|
||||
Api.ai requires a public endpoint (HTTPS recommended), so your Home Assistant should be exposed to Internet. Api.ai will return fall back answers if your server do not answer, or takes too long (more than 5 seconds).
|
||||
api.ai requires a public endpoint (HTTPS recommended), so your Home Assistant should be exposed to Internet. api.ai will return fallback answers if your server do not answer, or takes too long (more than 5 seconds).
|
||||
|
||||
Api.ai could be integrated with many popular messaging, virtual assistant and IoT platforms, eg.: Google Assistant (Google Actions), Skype, Messenger. [See here](https://docs.api.ai/docs/integrations) the complete list.
|
||||
api.ai could be integrated with many popular messaging, virtual assistant and IoT platforms, eg.: Google Assistant (Google Actions), Skype, Messenger. [See here](https://docs.api.ai/docs/integrations) the complete list.
|
||||
|
||||
Using Api.ai will be easy to create conversations like:
|
||||
|
||||
> User: Which is the temperature at home?
|
||||
>
|
||||
> Bot: The temperature is 34 degrees
|
||||
|
|
@ -35,6 +36,7 @@ Using Api.ai will be easy to create conversations like:
|
|||
To use this integration you should define a conversation (intent) in Api.ai, configure Home Assistant with the speech to return and, optionally, the action to execute.
|
||||
|
||||
### {% linkable_title Configuring your api.ai account %}
|
||||
|
||||
- [Login][apiai-web] with your Google account.
|
||||
- Click on "Create Agent"
|
||||
- Select name, language (if you are planning to use it with Google Actions check [here](https://support.google.com/assistant/answer/7108196?hl=en) supported languages) and time zone
|
||||
|
|
@ -55,6 +57,7 @@ Take a look to "Integrations", in the left menu, to configure third parties.
|
|||
|
||||
|
||||
### {% linkable_title Configuring Home Assistant %}
|
||||
|
||||
Out of the box, the component will do nothing. You have to teach it about all intents you want it to answer to. The way it works is that the answer for each intent is based on [templates] that you define. Each template will have access to the existing states via the `states` variable but will also have access to all variables defined in the intent.
|
||||
|
||||
You can use [templates] for setting `speech`.
|
||||
|
|
@ -129,6 +132,7 @@ apiai:
|
|||
{%- endif -%}
|
||||
data_template:
|
||||
entity_id: "switch.light_{{ Room | replace(' ', '_') }}"
|
||||
{% endraw %}
|
||||
```
|
||||
|
||||
[apiai-web]: https://api.ai/
|
||||
|
|
|
|||
|
|
@ -28,6 +28,11 @@ Configuration variables:
|
|||
|
||||
- **show_on_map** (*Optional*): Option to show the position of the ISS on the map. Defaults to `False`.
|
||||
|
||||
<p class='note warning'>
|
||||
If you set `show_on_map` `True` then the location attributes are named `latitude` and `longitude`. The default name of the location attributes is `lat` and `long` to avoid showing them on the map.
|
||||
</p>
|
||||
|
||||
|
||||
### {% linkable_title Show position on map with camera platform %}
|
||||
|
||||
The [generic camera platform](/components/camera.mjpeg/) offers the possibility to show the location of the ISS on Google Maps.
|
||||
|
|
|
|||
|
|
@ -31,6 +31,7 @@ The requirement is that you have setup [Wink](/components/wink/).
|
|||
- Wink Relay buttons and presense detection
|
||||
- Wink spotter loudness and vibration (No Wink hub required)
|
||||
- Wink hub devices connection status. This includes any paired hubs like Hue, Wink v1, Wink v2, Wink Relay...
|
||||
- Dropcam sensors
|
||||
|
||||
<p class='note'>
|
||||
The above devices are confimed to work, but others may work as well.
|
||||
|
|
|
|||
|
|
@ -27,6 +27,7 @@ The requirement is that you have setup [Wink](/components/wink/).
|
|||
- Carrier (Unconfirmed)
|
||||
- Honeywell (No wink hub required)
|
||||
- Generic Z-Wave
|
||||
- Quirky Aros window AC unit
|
||||
|
||||
<p class='note'>
|
||||
The above devices are confimed to work, but others may work as well.
|
||||
|
|
|
|||
|
|
@ -31,6 +31,7 @@ Configuration variables:
|
|||
- **max_gps_accuracy** (*Optional*): Sometimes Owntracks can report GPS location with a very low accuracy (few kilometers). That can trigger false zoning in your Home Assistant installation. With the parameter, you can filter these GPS reports. The number has to be in meter. For example, if you put 200 only GPS report with an accuracy under 200 will be take in account.
|
||||
- **waypoints** (*Optional*): Owntracks users can define [waypoints](http://owntracks.org/booklet/features/waypoints/) (a.k.a regions) which are similar in spirit to Home Assistant zones. If this configuration variable is `True`, the Owntracks users who are in `waypoint_whitelist` can export waypoints from the device and Home Assistant will import them as zone definitions. Defaults to `True`.
|
||||
- **waypoint_whitelist** (*Optional*): A list of user names (as defined for [Owntracks](/components/device_tracker.owntracks/)) who can export their waypoints from Owntracks to Home Assistant. Defaults to all users who are connected to Home Assistant via Owntracks.
|
||||
- **secret** (*Optional*): [Payload encryption key](http://owntracks.org/booklet/features/encrypt/). This is usable when communicating with a third-party untrusted server or a public server (where anybody can subscribe to any topic). By default the payload is assumed to be unecrypted (although the comunication between Home Assistant and the server might still be encrypted). This feature requires the `libsodium` library to be present.
|
||||
|
||||
A full sample configuration for the `owntracks` platform is shown below:
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ ha_release: 0.38
|
|||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `nuki` platform allows you to control [Nuki Smart Locks](https://nuki.io/en/smart-lock/) via either a [sofware bridge](https://play.google.com/store/apps/details?id=io.nuki.bridge) or a [physical bridge](https://nuki.io/en/bridge/).
|
||||
The `nuki` platform allows you to control [Nuki Smart Locks](https://nuki.io/en/smart-lock/) via either a [software bridge](https://play.google.com/store/apps/details?id=io.nuki.bridge) or a [physical bridge](https://nuki.io/en/bridge/).
|
||||
|
||||
To add a Nuki bridge to your installation, you need to enable developper mode on your bridge and define a port and an access token. This can be achieved using the [Android app](https://play.google.com/store/apps/details?id=io.nuki). Please note that the API token should be 6-20 characters long, even though the app allows you to set a longer one.
|
||||
Then add the following to your `configuration.yaml` file:
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ logo: logbook.png
|
|||
ha_category: "History"
|
||||
---
|
||||
|
||||
<img src='/images/screenshots/logbook.png' style='margin-left:10px; float: right;' height="100" /> The logbook component provides a different perspective on the history of your house by showing all the changes that happened to your house in reverse chronological order. [See the demo for a live example](/demo/).
|
||||
<img src='/images/screenshots/logbook.png' style='margin-left:10px; float: right;' height="100" /> The logbook component provides a different perspective on the history of your house by showing all the changes that happened to your house in reverse chronological order. [See the demo for a live example](/demo/). It depends on the `recorder` component for storing the data. This means that if the [`recorder`](/components/recorder/) component is set up to use e.g. MySQL or PostgreSQL as data store, the `logbook` component does not use the default SQLite database to store data.
|
||||
|
||||
To enable the logbook in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
|
|
@ -55,7 +55,7 @@ logbook:
|
|||
- media_player
|
||||
```
|
||||
|
||||
You can also use the `include` list and filter out some entities or domains with an `exclude` list. Usually this makes sense if you define domains on the include side and filter out some specific entities.
|
||||
You can also use the `include` list and filter out some entities or domains with an `exclude` list. Usually this makes sense if you define domains on the include side and filter out some specific entities.
|
||||
|
||||
```yaml
|
||||
# Example of combining include and exclude configurations
|
||||
|
|
|
|||
|
|
@ -36,7 +36,7 @@ Configuration variables:
|
|||
- **login_id** (*Required*): An identifier used to login to the device, see below
|
||||
- **name** (*Optional*): The name of the device used in the frontend
|
||||
|
||||
In order to connect to the device you need a *login id*. The easiest way to obtain this identifier is to use the application ``atvremote``. It should be available in the same environment as you installed Home-Assistant. Just run it like this to scan for all devices (try again if a device is missing):
|
||||
In order to connect to the device you need a *login id*. The easiest way to obtain this identifier is to use the application ``atvremote``. It should be available in the same environment as you installed Home-Assistant. To install this utility, run ``pip3 install --upgrade pyatv``. The run atvremote scan for all devices (try again if a device is missing):
|
||||
|
||||
```bash
|
||||
$ atvremote scan
|
||||
|
|
|
|||
|
|
@ -20,7 +20,9 @@ The requirements are:
|
|||
- You need a [Telegram bot](https://core.telegram.org/bots). Please follow those [instructions](https://core.telegram.org/bots#6-botfather) to create one and get the token for your bot. Keep in mind that bots are not allowed to contact users. You need to make the first contact with your user. Meaning that you need to send a message to the bot from your user.
|
||||
- The `chat_id` of an user.
|
||||
|
||||
The quickest way to retrieve your `chat_id` is visiting [https://api.telegram.org/botYOUR_API_TOKEN/getUpdates](https://api.telegram.org/botYOUR_API_TOKEN/getUpdates) or to use `$ curl -X GET https://api.telegram.org/botYOUR_API_TOKEN/getUpdates`. Replace `YOUR_API_TOKEN` with your actual token.
|
||||
To retrieve your `chat_id`, contact any of the Telegram bots created for this purpose (@myidbot, @get_id_bot)
|
||||
|
||||
The quickest way to retrieve your `chat_id` is visiting [https://api.telegram.org/botYOUR_API_TOKEN/getUpdates](https://api.telegram.org/botYOUR_API_TOKEN/getUpdates) or to use `$ curl -X GET https:/api.telegram.org/botYOUR_API_TOKEN/getUpdates`. Replace `YOUR_API_TOKEN` with your actual token.
|
||||
|
||||
The result set will include your chat ID as `id` in the `from` section:
|
||||
|
||||
|
|
|
|||
|
|
@ -90,8 +90,10 @@ If you only want to hide events from e.g. your history, take a look at the [`his
|
|||
| Database engine | `db_url` |
|
||||
| :---------------|:---------------------------------------------------------|
|
||||
| SQLite | `sqlite:///PATH/TO/DB_NAME` |
|
||||
| MySQL | `mysql+pymysql://SERVER_IP/DB_NAME` |
|
||||
| MySQL | `mysql+pymysql://user:password@SERVER_IP/DB_NAME` |
|
||||
| MySQL | `mysql://SERVER_IP/DB_NAME` |
|
||||
| MySQL | `mysql://user:password@SERVER_IP/DB_NAME` |
|
||||
| MySQL (pymysql) | `mysql+pymysql://SERVER_IP/DB_NAME` |
|
||||
| MySQL (pymysql) | `mysql+pymysql://user:password@SERVER_IP/DB_NAME` |
|
||||
| PostgreSQL | `postgresql://SERVER_IP/DB_NAME` |
|
||||
| PostgreSQL | `postgresql://scott:tiger@SERVER_IP/DB_NAME` |
|
||||
|
||||
|
|
@ -99,22 +101,22 @@ If you only want to hide events from e.g. your history, take a look at the [`his
|
|||
|
||||
Not all Python bindings for the chosen database engine can be installed directly. This section contains additional details which should help you to get it working.
|
||||
|
||||
### {% linkable_title MYSQL %}
|
||||
### {% linkable_title MySQL %}
|
||||
|
||||
For MySQL you may have to install a few dependencies:
|
||||
For MySQL you may have to install a few dependencies. You can choose between `pymysql` and `mysqlclient`:
|
||||
|
||||
```bash
|
||||
$ sudo apt-get install libmysqlclient-dev
|
||||
$ pip3 install pymysql
|
||||
$ pip3 install mysqlclient
|
||||
```
|
||||
If you are in a virtual environment, don't forget to activate it before installing the pymysql package.
|
||||
|
||||
```bash
|
||||
pi@homeassistant:~ $ sudo -i
|
||||
root@homeassistant:~# su homeassistant
|
||||
root@homeassistant:~# su homeassistant
|
||||
homeassistant@homeassistant:/root$ cd /srv/homeassistant/homeassistant_venv/
|
||||
homeassistant@homeassistant:/srv/homeassistant/homeassistant_venv$ source bin/activate
|
||||
(homeassistant_venv) homeassistant@homeassistant:/srv/homeassistant/homeassistant_venv$ pip3 install pymysql
|
||||
(homeassistant_venv) homeassistant@homeassistant:/srv/homeassistant/homeassistant_venv$ pip3 install mysqlclient
|
||||
```
|
||||
|
||||
### {% linkable_title PostgreSQL %}
|
||||
|
|
|
|||
|
|
@ -25,11 +25,9 @@ sensor:
|
|||
monitored_conditions:
|
||||
- Temperature
|
||||
- Humidity
|
||||
- Rain
|
||||
- Pressure
|
||||
- UVIndex
|
||||
- Luminance
|
||||
- Night
|
||||
- Voltage
|
||||
```
|
||||
|
||||
|
|
@ -38,9 +36,10 @@ Configuration variables:
|
|||
- **monitored_conditions** array (*Required*): The sensors that you wish to monitor on all of your devices. Select from these options:
|
||||
- Humidity
|
||||
- Luminance
|
||||
- Night
|
||||
- Pressure
|
||||
- Rain
|
||||
- Temperature
|
||||
- UVIndex
|
||||
- Voltage
|
||||
|
||||
|
||||
More conditions are available using the [BloomSky binary sensor](/components/binary_sensor.bloomsky) component.
|
||||
|
|
|
|||
|
|
@ -32,34 +32,13 @@ sensor:
|
|||
- summary
|
||||
- icon
|
||||
- nearest_storm_distance
|
||||
- nearest_storm_bearing
|
||||
- precip_type
|
||||
- precip_intensity
|
||||
- precip_probability
|
||||
- temperature
|
||||
- apparent_temperature
|
||||
- dew_point
|
||||
- wind_speed
|
||||
- wind_bearing
|
||||
- cloud_cover
|
||||
- humidity
|
||||
- pressure
|
||||
- visibility
|
||||
- ozone
|
||||
- minutely_summary
|
||||
- hourly_summary
|
||||
- daily_summary
|
||||
- temperature_max
|
||||
- temperature_min
|
||||
- apparent_temperature_max
|
||||
- apparent_temperature_min
|
||||
- precip_intensity_max
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **api_key** (*Required*): Your API key.
|
||||
- **name** (*Optional*): Additional name for the sensors. Default to platform name.
|
||||
- **forecast** array (*Optional*): List of days in the 7 day forecast you would like to receive data on, starting with tomorrow as day 1. Any `monitored_condition` with a daily forecast by DarkSky will generate a sensor tagged with `_<day>`.
|
||||
- **monitored_conditions** array (*Required*): Conditions to display in the frontend.
|
||||
- **summary**: A human-readable text summary of the current conditions.
|
||||
- **precip_type**: The type of precipitation occurring.
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ sensor:
|
|||
|
||||
Configuration variables:
|
||||
|
||||
- **stopid** (*Required*): The ID of the bust stop to get the information for.
|
||||
- **stopid** (*Required*): The ID of the bus stop to get the information for.
|
||||
- **route** (*Optional*): Only show a single bus route at the stop. This is the same as the bus number, e.g. `83`.
|
||||
- **name** (*Optional*): A friendly name for this sensor.
|
||||
|
||||
|
|
|
|||
|
|
@ -33,8 +33,9 @@ Configuration variables:
|
|||
- **api_key** (*Required*): Your application's API key (get one by following the instructions above). This key identifies your application for purposes of quota management.
|
||||
- **origin** (*Required*): The starting point for calculating travel distance and time. You can supply one or more locations separated by the pipe character, in the form of an address, latitude/longitude coordinates, or a [Google place ID](https://developers.google.com/places/place-id). When specifying the location using a Google place ID, the ID must be prefixed with `place_id:`.
|
||||
- **destination** (*Required*): One or more locations to use as the finishing point for calculating travel distance and time. The options for the destinations parameter are the same as for the origins parameter, described above.
|
||||
- **name** (*Optional*): A name to display on the sensor. The default is "Google Travel Time - <Transit Mode>" where transit mode is the mode set in options for the sensor (if no mode is set, the default is driving).
|
||||
- **name** (*Optional*): A name to display on the sensor. The default is "Google Travel Time - [Travel Mode]" where [Travel Mode] is the mode set in options for the sensor (see option "mode" below).
|
||||
- **options** (*Optional*): A dictionary containing parameters to add to all requests to the Distance Matrix API. A full listing of available options can be found [here](https://developers.google.com/maps/documentation/distance-matrix/intro#RequestParameters).
|
||||
- **mode** (*Optional*): The travel mode used to calculate the directions / time. Can be `driving` (*Default*), `bicycling`, `transit` or `walking`.
|
||||
- **departure_time** (*Optional*): Can be `now`, a Unix timestamp, or a 24 hour time string like `08:00:00`. If you provide a time string, it will be combined with the current date to get travel time for that moment.
|
||||
- **arrival_time** (*Optional*): See notes above for `departure_time`. `arrival_time` can not be `now`, only a Unix timestamp or time string. You can not provide both `departure_time` and `arrival_time`. If you do provide both, `arrival_time` will be removed from the request.
|
||||
- **units** (*Optional*): Set the unit for the sensor in metric or imperial, otherwise the default unit the same as the unit set in `unit_system:`.
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ footer: true
|
|||
logo: loop.png
|
||||
ha_category: Energy
|
||||
ha_release: 0.17
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: "Cloud Push"
|
||||
---
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -23,4 +23,5 @@ To enable the moon sensor, add the following lines to your `configuration.yaml`:
|
|||
sensor:
|
||||
- platform: moon
|
||||
```
|
||||
|
||||
This sensor will return one of the following values:
|
||||
`Full moon`, `Last quarter`, `First quarter` or `New moon`.
|
||||
|
|
|
|||
|
|
@ -53,7 +53,7 @@ Configuration variables:
|
|||
Device configuration variables:
|
||||
|
||||
- **name** (*Optional*): Name for the device, defaults to Rflink ID.
|
||||
- **sensor_type_** (*Optional*): Override automatically detected type of sensor.
|
||||
- **sensor_type** (*Required*): Override automatically detected type of sensor.
|
||||
- **unit_of_measurement** (*Optional*): Override automatically detected unit of sensor.
|
||||
- **aliasses** (*Optional*): Alternative Rflink ID's this device is known by.
|
||||
|
||||
|
|
|
|||
|
|
@ -35,4 +35,113 @@ Configuration variables:
|
|||
- 'humidity'
|
||||
- 'pressure'
|
||||
|
||||
### {% linkable_title Installation instruction for the All-In-One installer and HASSbian %}
|
||||
|
||||
Here are the steps to make the Sense HAT sensor work with a virtual environment.
|
||||
|
||||
Install SenseHAT package. Switch to the `homeassistant_venv` directory and activate the virtual environment.
|
||||
|
||||
```bash
|
||||
$ sudo su -s /bin/bash homeassistant
|
||||
$ source /srv/homeassistant/homeassistant_venv/bin/activate
|
||||
```
|
||||
|
||||
Install the `sense-hat` module.
|
||||
|
||||
```bash
|
||||
$ pip3 install sense-hat
|
||||
```
|
||||
|
||||
Please be patient, this will take a long while...
|
||||
|
||||
Type `exit` to quit out of the _homeassistant_venv_ back to your `pi` environment. As all of the following steps should be under the `pi` user environment.
|
||||
|
||||
Install the [RTIMU](https://github.com/RPi-Distro/RTIMULib) Python module:
|
||||
|
||||
```bash
|
||||
$ pip3 install rtimulib
|
||||
```
|
||||
|
||||
Add symlink to RTIMU in `homeassistant_venv` directory. Create a symlink using the following command:
|
||||
|
||||
```bash
|
||||
$ ln -s /usr/lib/python3/dist-packages/RTIMU.cpython-34m-arm-linux-gnueabihf.so /srv/homeassistant/homeassistant_venv/lib/python3.4/
|
||||
```
|
||||
|
||||
Add `homeassistant` user to the `input` and the `i2c` groups.
|
||||
|
||||
```bash
|
||||
$ sudo addgroup homeassistant input
|
||||
$ sudo addgroup homeassistant i2c
|
||||
```
|
||||
|
||||
Reboot Raspberry Pi to apply changes.
|
||||
|
||||
```bash
|
||||
$ sudo reboot
|
||||
```
|
||||
|
||||
### {% linkable_title Customizing the Sense HAT data %}
|
||||
|
||||
To format the sensor values, add the following to your `sensor` entry in your `configuration.yaml` file.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: sensehat
|
||||
display_options:
|
||||
- temperature
|
||||
- humidity
|
||||
- pressure
|
||||
|
||||
- platform: template
|
||||
sensors:
|
||||
sensehat_temperature:
|
||||
value_template: '{% raw %}{{ states.sensor.temperature.state | round(1) }}{% endraw %}'
|
||||
unit_of_measurement: '°C'
|
||||
sensehat_pressure:
|
||||
value_template: '{% raw %}{{ states.sensor.pressure.state | round(1) }}{% endraw %}'
|
||||
unit_of_measurement: 'mb'
|
||||
sensehat_humidity:
|
||||
value_template: '{% raw %}{{ states.sensor.humidity.state | round(1) }}{% endraw %}'
|
||||
unit_of_measurement: '%'
|
||||
```
|
||||
|
||||
Add the following to your `customize` section to set friendly names & icons for the values.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
customize:
|
||||
sensor.sensehat_temperature:
|
||||
icon: mdi:thermometer
|
||||
friendly_name: "Temperature"
|
||||
sensor.sensehat_humidity:
|
||||
icon: mdi:weather-rainy
|
||||
friendly_name: "Humidity"
|
||||
sensor.sensehat_pressure:
|
||||
icon: mdi:gauge
|
||||
friendly_name: "Pressure"
|
||||
```
|
||||
|
||||
Create a group for your Sense HAT details by adding the following to your `groups` section.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
group:
|
||||
sense_hat:
|
||||
name: Sense HAT
|
||||
entities:
|
||||
- sensor.sensehat_temperature
|
||||
- sensor.sensehat_humidity
|
||||
- sensor.sensehat_pressure
|
||||
```
|
||||
|
||||
Add the _sense_hat group_ a group (_Kitchen for example_)
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
group:
|
||||
kitchen:
|
||||
- group.sense_hat
|
||||
```
|
||||
|
||||
|
|
|
|||
|
|
@ -25,6 +25,7 @@ The requirement is that you have setup [Wink](/components/wink/).
|
|||
- Wink eggminder (No Wink hub required)
|
||||
- Nest protect Smoke and CO severity (No confirmation that this is actually reported) (No Wink hub required)
|
||||
- Motion sensor temperature
|
||||
- Quirky refuel propane tank monitor
|
||||
|
||||
<p class='note'>
|
||||
The above devices are confimed to work, but others may work as well.
|
||||
|
|
|
|||
|
|
@ -114,5 +114,8 @@ Configuration variables:
|
|||
|
||||
All the conditions listed above will be updated each 5 minutes with exception of `alerts` that will be updated each 15 minutes by default.
|
||||
|
||||
Additional details about the API are available [here](https://www.wunderground.com/weather/api/d/docs).
|
||||
<p class='note warning'>
|
||||
Note: While the platform is called “wunderground” the sensors will show up in Home Assistant as “PWS” (eg: sensor.pws_weather).
|
||||
</p>
|
||||
|
||||
Additional details about the API are available [here](https://www.wunderground.com/weather/api/d/docs).
|
||||
|
|
|
|||
|
|
@ -33,7 +33,16 @@ The commands can be dynamic, using templates to insert values of other entities.
|
|||
Any service data passed into the service call to activate the shell command will be available as a variable within the template.
|
||||
|
||||
```yaml
|
||||
|
||||
# Apply value of a GUI slider to the shell_command
|
||||
automation:
|
||||
- alias: run_set_ac
|
||||
trigger:
|
||||
platform: state
|
||||
entity_id: input_slider.ac_temperature
|
||||
action:
|
||||
service: shell_command.set_ac_to_slider
|
||||
|
||||
input_slider:
|
||||
ac_temperature:
|
||||
name: A/C Setting
|
||||
|
|
@ -41,8 +50,9 @@ input_slider:
|
|||
min: 18
|
||||
max: 32
|
||||
step: 1
|
||||
|
||||
{% raw %}
|
||||
shell_command:
|
||||
set_ac_to_slider: 'irsend SEND_ONCE DELONGHI AC_{{ states.input_slider.ac_temperature.state}}_AUTO'
|
||||
set_ac_to_slider: 'irsend SEND_ONCE DELONGHI AC_{{ states.input_slider.ac_temperature.state }}_AUTO'
|
||||
{% endraw %}
|
||||
```
|
||||
|
|
|
|||
|
|
@ -59,7 +59,7 @@ switch:
|
|||
command_on: "/usr/bin/curl -X GET http://192.168.1.10/digital/4/1"
|
||||
command_off: "/usr/bin/curl -X GET http://192.168.1.10/digital/4/0"
|
||||
command_state: "/usr/bin/curl -X GET http://192.168.1.10/digital/4"
|
||||
value_template: '{% raw %}{{ return_value == "1" }}{% endraw %}'
|
||||
value_template: '{% raw %}{{ value == "1" }}{% endraw %}'
|
||||
friendly_name: Kitchen Lightswitch
|
||||
```
|
||||
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@ switch:
|
|||
|
||||
Configuration variables:
|
||||
|
||||
- **host** (*Required*): The IP address of your TP-Link switch, eg. `http://192.168.1.32`.
|
||||
- **host** (*Required*): The IP address of your TP-Link switch, eg. `192.168.1.32`.
|
||||
- **name** (*Optional*): The name to use when displaying this switch.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -13,6 +13,7 @@ ha_release: 0.37
|
|||
---
|
||||
|
||||
The `amazon_polly` text-to-speech platform that works with [Amazon Polly](https://aws.amazon.com/polly/) to create the spoken output.
|
||||
Polly is a paid service via Amazon Web Services. There is a [free tier](https://aws.amazon.com/polly/pricing/) for the first 12 months and then a charge per million characters afterwards.
|
||||
|
||||
To enable text-to-speech with Amazon Polly, add the following lines to your `configuration.yaml`:
|
||||
|
||||
|
|
|
|||
|
|
@ -23,13 +23,12 @@ To add OpenWeatherMap to your installation, add the following to your `configura
|
|||
weather:
|
||||
- platform: openweathermap
|
||||
api_key: YOUR_API_KEY
|
||||
latitude: 46.1234
|
||||
longitude: 7.1234
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **api_key** (*Required*): Your API key for http://openweathermap.org/.
|
||||
- **name** (*Optional*): Name to use in the frontend.
|
||||
- **latitude** (*Optional*): Latitude of the location to display the weather. Defaults to the latitude in your your `configuration.yaml` file.
|
||||
- **longitude** (*Optional*): Longitude of the location to display the weather. Defaults to the longitude in your `configuration.yaml` file.
|
||||
|
||||
|
|
|
|||
|
|
@ -34,3 +34,5 @@ wemo:
|
|||
Any WeMo devices that are not statically configured but reachable via discovery will still be added automatically.
|
||||
|
||||
Note that if you use this, you may want to configure your router (or whatever runs your DHCP server) to force your WeMo devices to use a static IP address. Check the DHCP section of your router configuration for this ability.
|
||||
|
||||
If the device doesn't seem to work and all you see is the state "unavailable" on your dashboard, check that your firewall doesn't block incoming request on port 8989 since this is the address to which the WeMo devices sends their update.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue