From 964f9f873dce03f41acf6c538924d69fd231680c Mon Sep 17 00:00:00 2001 From: Kanga-Who Date: Thu, 14 May 2020 07:24:37 +1000 Subject: [PATCH 01/13] Update glossary.yml (#13422) --- source/_data/glossary.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/source/_data/glossary.yml b/source/_data/glossary.yml index 9bb3f81f014..cb3d0cc0a1a 100644 --- a/source/_data/glossary.yml +++ b/source/_data/glossary.yml @@ -32,12 +32,12 @@ description: "[Groups](/integrations/group/) are a way to organize your entities into a single unit." - topic: hass description: "HASS or [hass](/docs/tools/hass/) is often used as an abbreviation for Home Assistant. It is also the command-line tool." -- topic: Hass.io - description: "[Hass.io](/hassio/) is a full UI managed home automation ecosystem that runs Home Assistant, the Hass.io Supervisor and add-ons. It comes pre-installed on HassOS, but can be installed on any Linux system. It leverages Docker, which is managed by the Hass.io Supervisor." -- topic: Hass.io Supervisor - description: "The Hass.io Supervisor is a program that manages a Hass.io installation, taking care of installing and updating Home Assistant, add-ons, itself and, if used, updating the HassOS operating system." -- topic: HassOS - description: "HassOS, the Home Assistant Operating System, is an embedded, minimalistic, operating system designed to run the Hass.io ecosystem on single board computers (like the Raspberry Pi) or Virtual Machines. The Hass.io Supervisor can keep it up to date, removing the need for you to manage an operating system." +- topic: Home Assistant Supervised (Previously Hass.io) + description: "[Home Assistant](/hassio/) is a full UI managed home automation ecosystem that runs Home Assistant, the Home Assistant Supervisor and add-ons. It comes pre-installed on Home Assistant OS, but can be installed on any Linux system. It leverages Docker, which is managed by the Home Assistant Supervisor." +- topic: Home Assistant Supervisor + description: "The Home Assistant Supervisor is a program that manages a Home Assistant installation, taking care of installing and updating Home Assistant, add-ons, itself and, if used, updating the HassOS operating system." +- topic: Home Assistant Operating System + description: "Home Assistant OS, the Home Assistant Operating System, is an embedded, minimalistic, operating system designed to run the Home Assistant ecosystem on single board computers (like the Raspberry Pi) or Virtual Machines. The Home Assistant Supervisor can keep it up to date, removing the need for you to manage an operating system." - topic: Integration description: "[Integrations](/integrations/) provide the core logic for the functionality in Home Assistant. Like `notify` provides sending notifications." - topic: Lovelace From 900ce51a57033447eee9dd2e31c7f0f4711a9eca Mon Sep 17 00:00:00 2001 From: Abe Wiersma Date: Wed, 13 May 2020 23:27:04 +0200 Subject: [PATCH 02/13] WakeOnLan webostv documentation change (#13430) --- source/_integrations/webostv.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_integrations/webostv.markdown b/source/_integrations/webostv.markdown index a2cd1500561..6bad2ea019d 100644 --- a/source/_integrations/webostv.markdown +++ b/source/_integrations/webostv.markdown @@ -119,6 +119,7 @@ webostv: service: wake_on_lan.send_magic_packet data: mac: AA-BB-CC-DD-EE-FF + broadcast_address: 11.22.33.44 media_player: From dcfcaceef02066ed96a5090f4e5ccb8a106dd17e Mon Sep 17 00:00:00 2001 From: Mike Nabhan <13139061+mikenabhan@users.noreply.github.com> Date: Thu, 14 May 2020 01:06:08 -0600 Subject: [PATCH 03/13] Add example of network in trusted_proxy (#13435) --- source/_integrations/http.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_integrations/http.markdown b/source/_integrations/http.markdown index bc04a3b0cea..f983e75c21a 100644 --- a/source/_integrations/http.markdown +++ b/source/_integrations/http.markdown @@ -113,6 +113,7 @@ http: use_x_forwarded_for: true trusted_proxies: - 10.0.0.200 + - 172.30.33.0/24 ip_ban_enabled: true login_attempts_threshold: 5 ``` From 5a4b46d6e5e079b5a5dcb05d1debb6ff87fd8581 Mon Sep 17 00:00:00 2001 From: Kanga-Who Date: Thu, 14 May 2020 17:06:52 +1000 Subject: [PATCH 04/13] Update glossary.yml (#13434) --- source/_data/glossary.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_data/glossary.yml b/source/_data/glossary.yml index cb3d0cc0a1a..63997496c97 100644 --- a/source/_data/glossary.yml +++ b/source/_data/glossary.yml @@ -32,6 +32,8 @@ description: "[Groups](/integrations/group/) are a way to organize your entities into a single unit." - topic: hass description: "HASS or [hass](/docs/tools/hass/) is often used as an abbreviation for Home Assistant. It is also the command-line tool." +- topic: Home Assistant Core + description: Home Assistant Core is a Python program. It can be run on various operating systems and is the basis for Home Assistant. When people are talking about Home Assistant Core they usually refer to a standalone installation method that can be installed using a Virtual Environment or Docker. Home Assistant Core does not use the Home Assistant Supervisor. - topic: Home Assistant Supervised (Previously Hass.io) description: "[Home Assistant](/hassio/) is a full UI managed home automation ecosystem that runs Home Assistant, the Home Assistant Supervisor and add-ons. It comes pre-installed on Home Assistant OS, but can be installed on any Linux system. It leverages Docker, which is managed by the Home Assistant Supervisor." - topic: Home Assistant Supervisor From 2e9501f62fb53acf5f34bdbb36d274d909e0e0f8 Mon Sep 17 00:00:00 2001 From: Marouane Felja Date: Thu, 14 May 2020 09:07:22 +0200 Subject: [PATCH 05/13] Updating Alexa documentation. Adding France to Alexa web-based app list (#13433) --- source/_integrations/alexa.smart_home.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_integrations/alexa.smart_home.markdown b/source/_integrations/alexa.smart_home.markdown index 2dd0ed9c5ff..c2f04a236f5 100644 --- a/source/_integrations/alexa.smart_home.markdown +++ b/source/_integrations/alexa.smart_home.markdown @@ -957,6 +957,7 @@ The following is a list of regions and the corresponding URL for the web-based A - Australia: `https://alexa.amazon.com.au` - India: `https://alexa.amazon.in` - Spain: `https://alexa.amazon.es` +- France: `https://alexa.amazon.fr` ## Troubleshooting From ebb4bfb13d2867e491869299e6dba74fb4a0e58b Mon Sep 17 00:00:00 2001 From: Hedda Date: Thu, 14 May 2020 10:00:53 +0200 Subject: [PATCH 06/13] Update zha.markdown with Radio Type description for all supported radios (#13437) --- source/_integrations/zha.markdown | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/source/_integrations/zha.markdown b/source/_integrations/zha.markdown index 010f96e35b1..eec5c32e3dd 100644 --- a/source/_integrations/zha.markdown +++ b/source/_integrations/zha.markdown @@ -92,9 +92,11 @@ In the popup: | Radio Type | Zigbee Radio Hardware | | ------------- | ------------- | -| `ezsp` | EmberZNet based radios, Telegesis ETRX357USB*** (using EmberZNet firmware) | -| `deconz` | ConBee, ConBee II | -| `xbee` | Digi XBee Series 2, 2C, 3 | +| `ezsp` | Silicon Labs Ember based radios with EmberZNet Zigbee firmware | +| `deconz` | dresden elektronik ConBee and RaspBee based radios with deCONZ Zigbee firmware | +| `xbee` | Digi XBee Series 2 and 3 based radios with XBee Zigbee firmware | +| `ti_cc` | Texas Instruments CC253x/CC26x2/CC13x2 based radios with Z-Stack firmware | +| `zigate` | ZiGate USB-TTL, PiZiGate, and WiFi based Zigbee radios with ZiGate firmware | - Press `Submit` to save changes. From 6a5e4be11b777d5e877cdd947ea3c499317f687e Mon Sep 17 00:00:00 2001 From: Amir hossein Hossein Zadeh Karimi Date: Thu, 14 May 2020 14:17:15 +0430 Subject: [PATCH 07/13] Update web socket API link (#13439) --- source/_integrations/websocket_api.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/websocket_api.markdown b/source/_integrations/websocket_api.markdown index 9f69ec191ba..da251d29c8c 100644 --- a/source/_integrations/websocket_api.markdown +++ b/source/_integrations/websocket_api.markdown @@ -25,7 +25,7 @@ It is HIGHLY recommended that you set the `api_password`, especially if you are websocket_api: ``` -For details to use the WebSocket API, please refer to the [WebSocket API documentation](/developers/websocket_api/) . +For details to use the WebSocket API, please refer to the [WebSocket API documentation](https://developers.home-assistant.io/docs/api/websocket) . ## Track current connections From cdceba4061ed549a95e34889d66ccc0aeac0d420 Mon Sep 17 00:00:00 2001 From: Mike Nabhan <13139061+mikenabhan@users.noreply.github.com> Date: Thu, 14 May 2020 17:08:16 -0600 Subject: [PATCH 08/13] Fix broken links Documentation, standards, create new page (#13448) --- source/_includes/asides/help_navigation.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/_includes/asides/help_navigation.html b/source/_includes/asides/help_navigation.html index 458a6a93850..491f508735f 100644 --- a/source/_includes/asides/help_navigation.html +++ b/source/_includes/asides/help_navigation.html @@ -11,10 +11,10 @@ Developer documentation
  • - {% active_link /developers/documentation/ Website/Documentation %} + {% active_link /developers/documenting Website/Documentation %}
      -
    • {% active_link /developers/documentation/standards/ Standards %}
      • -
    • {% active_link /developers/documentation/create_page/ Create a new page %}
      • +
    • {% active_link /developers/documenting/standards/ Standards %}
      • +
    • {% active_link /developers/documenting/create-page Create a new page %}
  • From 68c1d94dd09f7edfae243f07e72338a63bb3cc17 Mon Sep 17 00:00:00 2001 From: Hedda Date: Fri, 15 May 2020 01:27:10 +0200 Subject: [PATCH 09/13] Update zha.markdown with RaspBee II (a.k.a. RaspBee 2) (#13440) --- source/_integrations/zha.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_integrations/zha.markdown b/source/_integrations/zha.markdown index eec5c32e3dd..a3b8bf50483 100644 --- a/source/_integrations/zha.markdown +++ b/source/_integrations/zha.markdown @@ -50,6 +50,7 @@ ZHA integration uses a hardware independent Zigbee stack implementation with mod - dresden elektronik deCONZ based Zigbee radios (via the [zigpy-deconz](https://github.com/zigpy/zigpy-deconz) library for zigpy) - [ConBee II (a.k.a. ConBee 2) USB adapter from dresden elektronik](https://phoscon.de/conbee2) - [ConBee USB adapter from dresden elektronik](https://phoscon.de/conbee) + - [RaspBee II (a.k.a. RaspBee 2) Raspberry Pi Shield from dresden elektronik](https://www.dresden-elektronik.com/product/raspbee-II.html) - [RaspBee Raspberry Pi Shield from dresden elektronik](https://phoscon.de/raspbee) - EmberZNet based radios using the EZSP protocol (via the [bellows](https://github.com/zigpy/bellows) library for zigpy) - [Nortek GoControl QuickStick Combo Model HUSBZB-1 (Z-Wave & Zigbee USB Adapter)](https://www.nortekcontrol.com/products/2gig/husbzb-1-gocontrol-quickstick-combo/) From b8f6d29289086029fee862a668837ca864c70f02 Mon Sep 17 00:00:00 2001 From: Sean Mooney Date: Thu, 14 May 2020 19:27:43 -0400 Subject: [PATCH 10/13] Remove reference to old icon on Templating page (#13444) --- source/_docs/configuration/templating.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/configuration/templating.markdown b/source/_docs/configuration/templating.markdown index de04e1a88be..cf889f05507 100644 --- a/source/_docs/configuration/templating.markdown +++ b/source/_docs/configuration/templating.markdown @@ -25,7 +25,7 @@ Templating in Home Assistant is powered by the [Jinja2](https://palletsprojects. We will not go over the basics of the syntax, as Jinja2 does a great job of this in their [templates documentation](https://jinja.palletsprojects.com/en/master/templates/). -The frontend has a template editor tool to help develop and debug templates. Click on the template developer tool icon icon, create your template in the _Template editor_ and check the results on the right. +The frontend has a template editor tool to help develop and debug templates. Navigate to Developer Tools > Template, create your template in the _Template editor_ and check the results on the right. Templates can get big pretty fast. To keep a clear overview, consider using YAML multiline strings to define your templates: From e9acec29c092f28d0dce157252d8376a8242ff37 Mon Sep 17 00:00:00 2001 From: Sean Mooney Date: Thu, 14 May 2020 19:28:33 -0400 Subject: [PATCH 11/13] Tweaks to reloading customize instructions (#13443) --- source/_docs/configuration/customizing-devices.markdown | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/source/_docs/configuration/customizing-devices.markdown b/source/_docs/configuration/customizing-devices.markdown index 274664e0a0d..60ffd57306d 100644 --- a/source/_docs/configuration/customizing-devices.markdown +++ b/source/_docs/configuration/customizing-devices.markdown @@ -8,7 +8,7 @@ redirect_from: /getting-started/customizing-devices/ You can use the UI to change the `entity_id` and friendly name of supported entities. To do this: -1. Select the entity, either from the frontend or by clicking next to the entity in the Developer Tools "States" tab. +1. Select the entity, either from the frontend or by clicking the info button next to the entity in the Developer Tools "States" tab. 2. Click on the cog in the right corner of the entity's dialog 3. Enter the new name or the new entity ID (remember not to change the domain of the entity - the part before the `.`) 4. Select *Save* @@ -123,7 +123,11 @@ homeassistant: ### Reloading customize -Home Assistant offers a service to reload the core configuration while Home Assistant is running called `homeassistant.reload_core_config`. This allows you to change your customize section and see it being applied without having to restart Home Assistant. To call this service, go to the "Service" tab under Developer Tools, select the `homeassistant.reload_core_config` service and click the "CALL SERVICE" button. Alternatively, you can press the "Reload Location & Customizations" button under Configuration > Server Control. +Home Assistant offers a service to reload the core configuration while Home Assistant is running. This allows you to change your customize section and see your changes being applied without having to restart Home Assistant. + +To reload customizations, navigate to Configuration > Server Controls and then press the "Reload Location & Customizations" button. If you don't see this, enable Advanced Mode on your user profile page first. + +Alternatively, you can reload via service call. Navigate to Developer Tools > Services tab, select `homeassistant.reload_core_config` from the dropdown and press the "Call Service" button.
    New customize information will be applied the next time the state of the entity gets updated. From 9c2e57e72116041eb72ee2949f8eade45e6c8320 Mon Sep 17 00:00:00 2001 From: Erik Montnemery Date: Fri, 15 May 2020 19:31:18 +0200 Subject: [PATCH 12/13] Improve JSON attributes template example (#13382) --- source/_integrations/sensor.mqtt.markdown | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/source/_integrations/sensor.mqtt.markdown b/source/_integrations/sensor.mqtt.markdown index a8c67ec2689..cfe318e7b1d 100644 --- a/source/_integrations/sensor.mqtt.markdown +++ b/source/_integrations/sensor.mqtt.markdown @@ -130,7 +130,9 @@ In this section you find some real-life examples of how to use this sensor. ### JSON attributes topic configuration -The example sensor below shows a configuration example which uses a JSON dict: `{"ClientName": , "IP": , "MAC": , "RSSI": , "HostName": , "ConnectedSSID": }` in a separate topic `home/sensor1/attributes` to add extra attributes. It also makes use of the `availability` topic. Extra attributes will be displayed in the frontend and can also be extracted in [Templates](/docs/configuration/templating/#attributes). For example, to extract the `ClientName` attribute from the sensor below, use a template similar to: {% raw %}`{{ state_attr('sensor.bs_rssi', 'ClientName') }}`{% endraw %}. +The example sensor below shows a configuration example which uses a JSON dict: `{"ClientName": , "IP": , "MAC": , "RSSI": , "HostName": , "ConnectedSSID": }` in a separate topic `home/sensor1/attributes` to add extra attributes. It also makes use of the `availability` topic. + +Extra attributes will be displayed in the frontend and can also be extracted in [Templates](/docs/configuration/templating/#attributes). For example, to extract the `ClientName` attribute from the sensor below, use a template similar to: {% raw %}`{{ state_attr('sensor.bs_rssi', 'ClientName') }}`{% endraw %}. {% raw %} ```yaml @@ -150,7 +152,9 @@ sensor: ### JSON attributes template configuration -The example sensor below shows a configuration example which uses a JSON dict: `{"Timer1":{"Arm": , "Time":