mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-21 16:27:19 +00:00
Merge branch 'current' into next
This commit is contained in:
commit
65b711bf9e
@ -80,7 +80,7 @@ GEM
|
|||||||
pathutil (0.16.2)
|
pathutil (0.16.2)
|
||||||
forwardable-extended (~> 2.6)
|
forwardable-extended (~> 2.6)
|
||||||
public_suffix (4.0.5)
|
public_suffix (4.0.5)
|
||||||
rack (2.2.2)
|
rack (2.2.3)
|
||||||
rack-protection (2.0.8.1)
|
rack-protection (2.0.8.1)
|
||||||
rack
|
rack
|
||||||
rake (13.0.1)
|
rake (13.0.1)
|
||||||
|
@ -67,7 +67,7 @@ Steps to Integrate an Amazon Alexa Smart Home Skill with Home Assistant:
|
|||||||
|
|
||||||
## Create an AWS Lambda Function
|
## Create an AWS Lambda Function
|
||||||
|
|
||||||
Alexa Smart Home skill will trigger a AWS Lambda function to process the request, we will write a small piece of code hosted as an Lambda function basically redirect the request to your Home Assistant instance, then Alexa integration integration in Home Assistant will process the request and send back the response. Your Lambda function will deliver the response back to Alexa.
|
Alexa Smart Home skill will trigger a AWS Lambda function to process the request, we will write a small piece of code hosted as an Lambda function basically redirect the request to your Home Assistant instance, then the Alexa integration in Home Assistant will process the request and send back the response. Your Lambda function will deliver the response back to Alexa.
|
||||||
|
|
||||||
<div class='info'>
|
<div class='info'>
|
||||||
|
|
||||||
|
@ -23,6 +23,7 @@ Known supported devices:
|
|||||||
- Denon AVR-X2100W
|
- Denon AVR-X2100W
|
||||||
- Denon AVR-X2200W
|
- Denon AVR-X2200W
|
||||||
- Denon AVR-X2300W
|
- Denon AVR-X2300W
|
||||||
|
- Denon AVR-X3300W
|
||||||
- Denon AVR-X3400H
|
- Denon AVR-X3400H
|
||||||
- Denon AVR-X4100W
|
- Denon AVR-X4100W
|
||||||
- Denon AVR-X4300H
|
- Denon AVR-X4300H
|
||||||
|
@ -97,9 +97,10 @@ sensor:
|
|||||||
|
|
||||||
- A sensor will be created for each of the following conditions, with a default name like `sensor.temperature`:
|
- A sensor will be created for each of the following conditions, with a default name like `sensor.temperature`:
|
||||||
- `temperature` - The current temperature, in ºC.
|
- `temperature` - The current temperature, in ºC.
|
||||||
- `dewpoint` - The current dewpoint, in ºC.
|
- `dew_point` - The current dewpoint, in ºC.
|
||||||
- `wind_chill` - The current wind chill, in ºC.
|
- `wind_chill` - The current wind chill, in ºC.
|
||||||
- `humidex` - The current humidex, in ºC.
|
- `humidex` - The current humidex, in ºC.
|
||||||
|
- `air_quality_health_index` - The current Air Quality Health Index score
|
||||||
- `pressure` - The current air pressure, in kPa.
|
- `pressure` - The current air pressure, in kPa.
|
||||||
- `tendency` - The current air pressure tendency, e.g., "Rising".
|
- `tendency` - The current air pressure tendency, e.g., "Rising".
|
||||||
- `humidity` - The current humidity, in %.
|
- `humidity` - The current humidity, in %.
|
||||||
@ -108,14 +109,14 @@ sensor:
|
|||||||
- `icon_code` - A two-digit number corresponding to a condition icon, as specified in these [image to description](https://dd.weather.gc.ca/citypage_weather/docs/Current_Conditions_Icons-Icones_conditions_actuelles.pdf) and [code to description](https://dd.weather.gc.ca/citypage_weather/docs/current_conditions_icon_code_descriptions_e.csv) mappings.
|
- `icon_code` - A two-digit number corresponding to a condition icon, as specified in these [image to description](https://dd.weather.gc.ca/citypage_weather/docs/Current_Conditions_Icons-Icones_conditions_actuelles.pdf) and [code to description](https://dd.weather.gc.ca/citypage_weather/docs/current_conditions_icon_code_descriptions_e.csv) mappings.
|
||||||
- `wind_speed` - The current sustained wind speed, in km/h.
|
- `wind_speed` - The current sustained wind speed, in km/h.
|
||||||
- `wind_gust` - The current wind gust, in km/h.
|
- `wind_gust` - The current wind gust, in km/h.
|
||||||
- `wind_dir` - The current cardinal wind direction, e.g., "SSW".
|
- `wind_direction` - The current cardinal wind direction, e.g., "SSW".
|
||||||
- `wind_bearing` - The current wind direction in degrees.
|
- `wind_bearing` - The current wind direction in degrees.
|
||||||
- `high_temp` - The next forecast high temperature, in ºC.
|
- `high_temperature` - The next forecast high temperature, in ºC.
|
||||||
- `low_temp` - The next forecast low temperature, in ºC.
|
- `low_temperature` - The next forecast low temperature, in ºC.
|
||||||
- `uv_index` - The next forecast UV index.
|
- `uv_index` - The next forecast UV index.
|
||||||
- `pop` - The next forecast probability of precipitation, in %.
|
- `chance_of_precip` - The next forecast probability of precipitation, in %.
|
||||||
- `text_summary` - A textual description of the next forecast period, e.g., "Tonight. Mainly cloudy. Low -12."
|
- `forecast` - A textual description of the next forecast period, e.g., "Tonight. Mainly cloudy. Low -12."
|
||||||
- `precip_yesterday` - The total amount of precipitation that fell the previous day.
|
- `precipitation_yesterday` - The total amount of precipitation that fell the previous day.
|
||||||
- `warnings` - Current warning alerts.
|
- `warnings` - Current warning alerts.
|
||||||
- `watches` - Current watch alerts.
|
- `watches` - Current watch alerts.
|
||||||
- `advisories` - Current advisory alerts.
|
- `advisories` - Current advisory alerts.
|
||||||
@ -124,7 +125,7 @@ sensor:
|
|||||||
- The platform automatically determines which weather station to use based on the system's latitude/longitude settings. For greater precision, it is also possible to specify either:
|
- The platform automatically determines which weather station to use based on the system's latitude/longitude settings. For greater precision, it is also possible to specify either:
|
||||||
- A specific station code of the form `AB/s0000123` based on those listed in [this CSV file](http://dd.weatheroffice.ec.gc.ca/citypage_weather/docs/site_list_towns_en.csv), or
|
- A specific station code of the form `AB/s0000123` based on those listed in [this CSV file](http://dd.weatheroffice.ec.gc.ca/citypage_weather/docs/site_list_towns_en.csv), or
|
||||||
- A specific latitude/longitude
|
- A specific latitude/longitude
|
||||||
- In the case of multiple alerts in the same category, the titles and details of each are concatenated together with a pipe (`|`) separator.
|
- In the case of multiple alerts in the same category, the titles of each are concatenated together with a pipe (`|`) separator.
|
||||||
|
|
||||||
{% configuration %}
|
{% configuration %}
|
||||||
latitude:
|
latitude:
|
||||||
|
@ -11,8 +11,8 @@ ha_domain: history
|
|||||||
---
|
---
|
||||||
|
|
||||||
The `history` integration will track everything that is going on within Home
|
The `history` integration will track everything that is going on within Home
|
||||||
Assistant and allows the user to browse through it. It depends on the `recorder`
|
Assistant and allows the user to browse through it. It depends on the [`recorder`](integrations/recorder/)
|
||||||
component for storing the data and uses the same database setting.
|
integration for storing the data and uses the same database setting.
|
||||||
If any entities are excluded from being recorded,
|
If any entities are excluded from being recorded,
|
||||||
no history will be available for these entities.
|
no history will be available for these entities.
|
||||||
|
|
||||||
|
@ -9,7 +9,7 @@ ha_quality_scale: internal
|
|||||||
ha_domain: history_stats
|
ha_domain: history_stats
|
||||||
---
|
---
|
||||||
|
|
||||||
The `history_stats` sensor platform provides quick statistics about another integration or platforms, using data from the [history](/integrations/history/).
|
The `history_stats` sensor platform provides quick statistics about another integration or platforms, using data from the [`history`](/integrations/history/) integration.
|
||||||
|
|
||||||
It can track how long the integration has been in a specific state, in a custom time period.
|
It can track how long the integration has been in a specific state, in a custom time period.
|
||||||
|
|
||||||
|
@ -21,17 +21,18 @@ Please note, the `knx` platform does not support KNX Secure.
|
|||||||
There is currently support for the following device types within Home Assistant:
|
There is currently support for the following device types within Home Assistant:
|
||||||
|
|
||||||
- [Binary Sensor](/integrations/binary_sensor.knx)
|
- [Binary Sensor](/integrations/binary_sensor.knx)
|
||||||
|
- [Climate](/integrations/climate.knx)
|
||||||
- [Cover](/integrations/cover.knx)
|
- [Cover](/integrations/cover.knx)
|
||||||
- [Sensor](/integrations/sensor.knx)
|
|
||||||
- [Switch](/integrations/switch.knx)
|
|
||||||
- [Light](/integrations/light.knx)
|
- [Light](/integrations/light.knx)
|
||||||
- [Thermostat](/integrations/climate.knx)
|
|
||||||
- [Notify](/integrations/notify.knx)
|
- [Notify](/integrations/notify.knx)
|
||||||
- [Scene](/integrations/scene.knx)
|
- [Scene](/integrations/scene.knx)
|
||||||
|
- [Sensor](/integrations/sensor.knx)
|
||||||
|
- [Switch](/integrations/switch.knx)
|
||||||
|
|
||||||
|
|
||||||
## Configuration
|
## Configuration
|
||||||
|
|
||||||
To use your KNX in your installation, add the following lines to your `configuration.yaml` file:
|
To use your KNX bus in your installation, add the following lines to your `configuration.yaml` file:
|
||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
knx:
|
knx:
|
||||||
@ -56,7 +57,7 @@ rate_limit:
|
|||||||
type: integer
|
type: integer
|
||||||
{% endconfiguration %}
|
{% endconfiguration %}
|
||||||
|
|
||||||
If the auto detection of the KNX/IP device does not work you can specify ip/port of the tunneling device:
|
If the auto detection of the KNX/IP device does not work you can specify IP and port of the tunneling device:
|
||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
knx:
|
knx:
|
||||||
|
@ -8,7 +8,7 @@ ha_quality_scale: internal
|
|||||||
ha_domain: recorder
|
ha_domain: recorder
|
||||||
---
|
---
|
||||||
|
|
||||||
The `recorder` integration is responsible for storing details in a database, which then are handled by the [`history` integration](/integrations/history/).
|
The `recorder` integration is responsible for storing details in a database, which then are handled by the [`history` ](/integrations/history/) integration.
|
||||||
|
|
||||||
<div class='note'>
|
<div class='note'>
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user