diff --git a/Gemfile.lock b/Gemfile.lock index 1e371e05c75..192a66e674b 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -80,7 +80,7 @@ GEM pathutil (0.16.2) forwardable-extended (~> 2.6) public_suffix (4.0.5) - rack (2.2.2) + rack (2.2.3) rack-protection (2.0.8.1) rack rake (13.0.1) diff --git a/source/_integrations/alexa.smart_home.markdown b/source/_integrations/alexa.smart_home.markdown index 92c8cfda99b..05953dd2669 100644 --- a/source/_integrations/alexa.smart_home.markdown +++ b/source/_integrations/alexa.smart_home.markdown @@ -67,7 +67,7 @@ Steps to Integrate an Amazon Alexa Smart Home Skill with Home Assistant: ## 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.
diff --git a/source/_integrations/denonavr.markdown b/source/_integrations/denonavr.markdown index e16dd4b03a0..69ec47a0e1e 100644 --- a/source/_integrations/denonavr.markdown +++ b/source/_integrations/denonavr.markdown @@ -23,6 +23,7 @@ Known supported devices: - Denon AVR-X2100W - Denon AVR-X2200W - Denon AVR-X2300W +- Denon AVR-X3300W - Denon AVR-X3400H - Denon AVR-X4100W - Denon AVR-X4300H diff --git a/source/_integrations/environment_canada.markdown b/source/_integrations/environment_canada.markdown index 6166a61c9a7..91c16bbde97 100644 --- a/source/_integrations/environment_canada.markdown +++ b/source/_integrations/environment_canada.markdown @@ -95,11 +95,12 @@ sensor: - platform: environment_canada ``` -- 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. - - `dewpoint` - The current dewpoint, in ºC. + - `dew_point` - The current dewpoint, in ºC. - `wind_chill` - The current wind chill, 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. - `tendency` - The current air pressure tendency, e.g., "Rising". - `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. - `wind_speed` - The current sustained wind speed, 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. - - `high_temp` - The next forecast high temperature, in ºC. - - `low_temp` - The next forecast low temperature, in ºC. + - `high_temperature` - The next forecast high temperature, in ºC. + - `low_temperature` - The next forecast low temperature, in ºC. - `uv_index` - The next forecast UV index. - - `pop` - The next forecast probability of precipitation, in %. - - `text_summary` - 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. + - `chance_of_precip` - The next forecast probability of precipitation, in %. + - `forecast` - A textual description of the next forecast period, e.g., "Tonight. Mainly cloudy. Low -12." + - `precipitation_yesterday` - The total amount of precipitation that fell the previous day. - `warnings` - Current warning alerts. - `watches` - Current watch 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: - 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 -- 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 %} latitude: diff --git a/source/_integrations/history.markdown b/source/_integrations/history.markdown index 21f1914161b..caf48cc0949 100644 --- a/source/_integrations/history.markdown +++ b/source/_integrations/history.markdown @@ -11,8 +11,8 @@ ha_domain: history --- 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` -component for storing the data and uses the same database setting. +Assistant and allows the user to browse through it. It depends on the [`recorder`](integrations/recorder/) +integration for storing the data and uses the same database setting. If any entities are excluded from being recorded, no history will be available for these entities. diff --git a/source/_integrations/history_stats.markdown b/source/_integrations/history_stats.markdown index 303efde7fa3..33ad89637e9 100644 --- a/source/_integrations/history_stats.markdown +++ b/source/_integrations/history_stats.markdown @@ -9,7 +9,7 @@ ha_quality_scale: internal 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. diff --git a/source/_integrations/knx.markdown b/source/_integrations/knx.markdown index 11ff5024703..85bf1ac0aab 100644 --- a/source/_integrations/knx.markdown +++ b/source/_integrations/knx.markdown @@ -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: - [Binary Sensor](/integrations/binary_sensor.knx) +- [Climate](/integrations/climate.knx) - [Cover](/integrations/cover.knx) -- [Sensor](/integrations/sensor.knx) -- [Switch](/integrations/switch.knx) - [Light](/integrations/light.knx) -- [Thermostat](/integrations/climate.knx) - [Notify](/integrations/notify.knx) - [Scene](/integrations/scene.knx) +- [Sensor](/integrations/sensor.knx) +- [Switch](/integrations/switch.knx) + ## 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 knx: @@ -56,7 +57,7 @@ rate_limit: type: integer {% 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 knx: diff --git a/source/_integrations/recorder.markdown b/source/_integrations/recorder.markdown index fc7330a2211..433a4945a3d 100644 --- a/source/_integrations/recorder.markdown +++ b/source/_integrations/recorder.markdown @@ -8,7 +8,7 @@ ha_quality_scale: internal 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.