home-assistant · spacegaier · Jan 7, 2021 · Jan 8, 2021 · Jan 8, 2021 · Jan 8, 2021
diff --git a/Gemfile.lock b/Gemfile.lock
@@ -19,7 +19,7 @@ GEM
       sass (>= 3.3.0, < 3.5)
     compass-import-once (1.0.5)
       sass (>= 3.2, < 3.5)
-    concurrent-ruby (1.1.7)
+    concurrent-ruby (1.1.8)
     em-websocket (0.5.2)
       eventmachine (>= 0.12.9)
       http_parser.rb (~> 0.6.0)
@@ -66,7 +66,7 @@ GEM
     kramdown-parser-gfm (1.1.0)
       kramdown (~> 2.0)
     liquid (4.0.3)
-    listen (3.4.0)
+    listen (3.4.1)
       rb-fsevent (~> 0.10, >= 0.10.3)
       rb-inotify (~> 0.9, >= 0.9.10)
     mercenary (0.4.0)
@@ -94,7 +94,7 @@ GEM
     rouge (3.26.0)
     ruby-enum (0.8.0)
       i18n
-    ruby2_keywords (0.0.2)
+    ruby2_keywords (0.0.4)
     safe_yaml (1.0.5)
     sass (3.4.25)
     sass-globbing (1.1.5)

diff --git a/_config.yml b/_config.yml
@@ -101,8 +101,8 @@ social:
 # Home Assistant release details
 current_major_version: 2021
 current_minor_version: 1
-current_patch_version: 0
-date_released: 2021-01-06
+current_patch_version: 4
+date_released: 2021-01-16
 
 # Either # or the anchor link to latest release notes in the blog post.
 # Must be prefixed with a # and have double quotes around it.

diff --git a/package-lock.json b/package-lock.json
diff --git a/package.json b/package.json
@@ -12,7 +12,7 @@
     "remark-stringify": "^9.0.1",
     "textlint": "^11.7.7",
     "textlint-rule-common-misspellings": "^1.0.1",
-    "textlint-rule-terminology": "^2.1.4"
+    "textlint-rule-terminology": "^2.1.5"
   },
   "resolutions": {
     "minimist": ">=1.2.5"

diff --git a/sass/custom/_layout.scss b/sass/custom/_layout.scss
@@ -29,7 +29,7 @@ html {
     height: calc(100% - 68px);;
     margin-top: 68px;
     overflow-y: scroll;
-    padding-top: 32px;
+    padding-top: 82px;
     width: 100%;
 }
 
@@ -43,6 +43,10 @@ html {
     }
 }
 
+.alert-banner {
+    height: 50px;
+  }
+
 .site-header {
     position: fixed;
     width: 100%;

diff --git a/sass/oscailte/base/_navigation.scss b/sass/oscailte/base/_navigation.scss
@@ -69,7 +69,7 @@ header .grid {
 
 .menu {
   margin: 0;
-  top: 68px;
+  top: 138px;
 }
 
 .menu li a{
@@ -116,9 +116,17 @@ header .grid {
     padding: 15px 15px 15px 25px;
   }
 
+  .alert-banner {
+    height: 70px !important;
+  }
+
+  .page-content {
+    padding-top: 102px;
+  }
+
   .toggle {
     position: absolute;
-    top: 15px;
+    top: 85px;
     right: 10px;
   }
 

diff --git a/source/_docs/authentication/providers.markdown b/source/_docs/authentication/providers.markdown
@@ -3,25 +3,19 @@ title: "Authentication Providers"
 description: "Guide on configuring different auth providers."
 ---
 
-When you log in, an _auth provider_ checks your credentials to make sure you are an authorized user.
-
-<div class='note'>
-
-The authentication system has been changed recently. Previously there was a single "_API password_" to log in, but you can now choose from several auth providers.<br/> <br/>
-
-To make the transition from API passwords easier, we've added a _Legacy API Password_ auth provider. This is enabled by default if you have an API password configured so you will still be able to log in.
-
-However, this feature is deprecated and will be removed in a future release so you should set up one of the newer authentication techniques.
-
+<div class='note warning'>
+  This is an advanced feature.
 </div>
 
+When you log in, an _auth provider_ checks your credentials to make sure you are an authorized user.
+
 ## Configuring auth providers
 
 <div class='note warning'>
 
 Home Assistant automatically configures the standard auth providers so you don't need to specify `auth_providers` in your `configuration.yaml` file unless you are configuring more than one. Specifying `auth_providers` will disable all auth providers that are not listed, so you could reduce your security or create difficulties logging in if it is not configured correctly.
 
-This means that if you decide to use `trusted_networks` as your `auth_provider` there won't be a way to authenticate for a device outside of your listed trusted network. To overcome this ensure you add the default `auth_provider``type: homeassistant` back in manually. This will then present you with the default auth login screen when trusted network authentication fails as expected from outside your LAN.
+If you decide to use `trusted_networks` as your `auth_provider` there won't be a way to authenticate for a device outside of your listed trusted network. To overcome this ensure you add the default `auth_provider``type: homeassistant` back in manually. This will then present you with the default auth login screen when trusted network authentication fails as expected from outside your LAN.
 
 </div>
 

diff --git a/source/_docs/automation/trigger.markdown b/source/_docs/automation/trigger.markdown
@@ -151,7 +151,8 @@ The `for` template(s) will be evaluated when an entity changes as specified.
 
 ### State trigger
 
-Fires when the state of any of given entities changes. If only `entity_id` is given trigger will fire for all state changes, even if only state attributes change.
+Fires when the state of any of given entities changes. If only `entity_id` is given, the trigger will fire for all state changes, even if only state attributes change.
+If only one of `from_state` or `to_state` are given, the trigger will fire on any matching state change, but not if only attributes change.
 
 <div class='note'>
 
@@ -163,13 +164,28 @@ The values you see in your overview will often not be the same as the actual sta
 automation:
   trigger:
     platform: state
-    entity_id: device_tracker.paulus, device_tracker.anne_therese
+    entity_id:
+      - device_tracker.paulus
+      - device_tracker.anne_therese
     # Optional
     from: "not_home"
     # Optional
     to: "home"
 ```
 
+It's possible to give a list of from_states or to_states:
+
+```yaml
+automation:
+  trigger:
+    platform: state
+    entity_id: vacuum.test
+    from:
+    - "cleaning"
+    - "returning"
+    to: "error"
+```
+
 #### Holding a state
 
 You can use `for` to have the state trigger only fire if the state holds for some time.

diff --git a/source/_docs/blueprint/selectors.markdown b/source/_docs/blueprint/selectors.markdown
@@ -338,7 +338,7 @@ mode:
   description: This can be either `box` or `slider` mode.
   type: string
   required: false
-  default: box
+  default: slider
 {% endconfiguration %}
 
 ### Example number selectors

diff --git a/source/_docs/configuration/templating.markdown b/source/_docs/configuration/templating.markdown
@@ -164,7 +164,7 @@ The same thing can also be expressed as a filter:
 
 {% raw %}
 ```text
-{{ ['device_tracker.paulus', 'group.child_trackers'] | expand 
+{{ expand(['device_tracker.paulus', 'group.child_trackers']) 
   | selectattr("attributes.battery", 'defined')
   | join(', ', attribute="attributes.battery") }}
 ```

diff --git a/source/_docs/mqtt/discovery.markdown b/source/_docs/mqtt/discovery.markdown
@@ -18,6 +18,7 @@ Supported by MQTT discovery:
 - [HVACs](/integrations/climate.mqtt/)
 - [Lights](/integrations/light.mqtt/)
 - [Locks](/integrations/lock.mqtt/)
+- [Scenes](/integrations/scene.mqtt/)
 - [Sensors](/integrations/sensor.mqtt/)
 - [Switches](/integrations/switch.mqtt/)
 - [Tag Scanners](/integrations/tag.mqtt/)

diff --git a/source/_docs/scripts.markdown b/source/_docs/scripts.markdown
@@ -62,7 +62,7 @@ Scripts may also use a shortcut syntax for activating scenes instead of calling
 
 ## Variables
 
-The variable command allows you to set/override variables that will be accessible by templates in actions after it.
+The variables command allows you to set/override variables that will be accessible by templates in actions after it (see also [script variables] for how to define locally available variables).
 
 {% raw %}
 
@@ -571,3 +571,4 @@ automation:
 [service calls page]: /getting-started/scripts-service-calls/
 [conditions page]: /getting-started/scripts-conditions/
 [shorthand-template]: /docs/scripts/conditions/#template-condition-shorthand-notation
+[script variables]: /integrations/script/#-configuration-variables
diff --git a/source/_faq/unique_id.markdown b/source/_faq/unique_id.markdown
@@ -4,10 +4,14 @@ description: "This entity does not have a unique ID?"
 ha_category: Configuration
 ---
 
-When you see
+If you try to access the configuration dialog for an entity in your Home Assistant, you might end up seeing this message:
 
-```text
-This entity does not have a unique ID, therefore its settings cannot be managed from the UI
-```
+<p class='img'>
+<img src='/images/faq/faq_no_unique_id.jpg' alt='Screenshot of popup for no unique ID'>
+</p>
 
-this simply means that you can't change the `entity_id` or the friendly name from the UI. You can still use the _Customizations_ menu to customize that entity. Typically you'll see this when you create entities using YAML.
+This simply means that this entity does not provide a unique identification (e.g., a serial number)\*. As a result, the normal editing process that allows you to change various settings such as the entity ID, icon, friendly name, etc. is not possible here. Typically, you'll see this when you create entities using YAML, but it can also appear if the integration that provides this entity simply cannot determine a unique ID.
+
+If your user profile has the "Advanced Mode" activated, you will also see the second paragraph in the popup with a link to the [customization user interface](https://www.home-assistant.io/docs/configuration/customizing-devices/#customization-using-the-ui) for this specific entity, which offers some customization options.
+
+\* In case you want to read about more about that, head over to this [developer documentation page](https://developers.home-assistant.io/docs/entity_registry_index/).
diff --git a/source/_includes/site/footer.html b/source/_includes/site/footer.html
@@ -18,6 +18,7 @@
             <li><a href='https://alerts.home-assistant.io'>Home Assistant Alerts</a></li>
             <li><a href='https://developers.home-assistant.io'>Developers</a></li>
             <li><a href='https://data.home-assistant.io'>Data Science</a></li>
+            <li><a href='https://community.home-assistant.io'>Community Forum</a></li>
             <li><a href='mailto:hello@home-assistant.io'>Contact</a> (no support!)</li>
             <li><a href='/security/'>Security Vulnerabilities</a></li>
             <li><a href='/privacy/'>Privacy</a></li>

diff --git a/source/_integrations/ads.markdown b/source/_integrations/ads.markdown
@@ -1,7 +1,6 @@
 ---
 title: ADS
 description: Connect Home Assistant to TwinCAT devices via the ADS interface
-logo: beckhoff.png
 ha_category:
   - Hub
   - Binary Sensor

@@ -119,7 +119,7 @@ Next you need create a Lambda function.
 - Scroll down a little bit, you will find `Environment variables`, you need add 1 environment variable and, if required, 3 optional variables. This is done by selecting `Manage environment variables` then adding the following:
   - *(required)* Key = BASE_URL, Value = your Home Assistant instance's Internet accessible URL with port if needed. *Do not include the trailing `/`*.
   - *(optional)* Key = NOT_VERIFY_SSL, Value = *True*. You can set this to *True* to ignore SSL issues, for example if you don't have a valid SSL certificate or you are using a self-signed certificate.
-  - *(optional)* Key = DEBUG, Value = *True*. Set this variable to log the debug message.
+  - *(optional)* Key = DEBUG, Value = *True*. Set this variable to log the debug message and to allow the LONG_LIVED_ACCESS_TOKEN
   - *(optional, not recommend)* Key = LONG_LIVED_ACCESS_TOKEN, Value = your Home Assistant Long-Lived Access Token. To avoid the use of a long-lived access token you will connect your Alexa Smart Home skill with your Home Assistant user account in the later steps, meaning you don't need to add it here. However, the access token you got from login flow is only valid for 30 minutes. It will be hard for you to test lambda function with the access token in test data. So for your convenience, you can remove the access token from the test data, [generate a long-lived access token][generate-long-lived-access-token] put here, then the function will fall back to read token from environment variables. (tips: You did not enable the security storage for your environment variables, so your token saved here is not that safe. You should only use it for debugging and testing purpose. You should remove and delete the long-lived access token after you finish the debugging.)
 
 <p class='img'>
@@ -167,9 +167,9 @@ After your Home Assistant has restarted, go back to `AWS Lambda Console`, you ar
 
 This test event is a `Discovery` directive, your Home Assistant instance will respond with a list of devices Alexa can interact with. This test data is lack of `token` in `payload.scope`, your Lambda function will read the `LONG_LIVED_ACCESS_TOKEN` from environment variable.
 
-Click the `Test` button. If you don't have `LONG_LIVED_ACCESS_TOKEN`, you will get a `INVALID_AUTHORIZATION_CREDENTIAL` response as the execution result.
+Click the `Test` button. If you don't have `LONG_LIVED_ACCESS_TOKEN`, or you haven't enabled `DEBUG` you will get a `INVALID_AUTHORIZATION_CREDENTIAL` response as the execution result.
 
-Now, you can login to your Home Assistant and [generate a long-lived access token][generate-long-lived-access-token]. After you put your long-lived access token to the `Environment variable`, do not forget click `Save` button before you `Test` again.
+Now, you can login to your Home Assistant and [generate a long-lived access token][generate-long-lived-access-token]. After you put your long-lived access token to the `Environment variable` and set the `DEBUG` environment variable to `True`, do not forget to click the `Save` button before you `Test` again.
 
 This time, you will get a list of your devices in the response. 🎉
 

diff --git a/source/_integrations/androidtv.markdown b/source/_integrations/androidtv.markdown
@@ -12,6 +12,12 @@ ha_domain: androidtv
 
 The `androidtv` platform allows you to control an Android TV device or [Amazon Fire TV](https://www.amazon.com/b/?node=8521791011) device.
 
+<div class='note'>
+
+When setting up this integration, it is recommended that you do NOT use an ADB server and instead use the built-in Python ADB implementation. This simplifies the setup and makes it easier to troubleshoot issues. If there are stability issues with this approach, then you may wish to try using an ADB server. See the [ADB Setup](#adb-setup) section for more information.
+
+</div>
+
 ## Device preparation
 
 To set up your device, you will need to find its IP address and enable ADB debugging. For Android TV devices, please consult the documentation for your device.
@@ -35,12 +41,6 @@ media_player:
   - platform: androidtv
     name: Android TV 1
     host: 192.168.0.111
-
-  # Use an ADB server for sending ADB commands
-  - platform: androidtv
-    name: Android TV 2
-    host: 192.168.0.222
-    adb_server_ip: 127.0.0.1
 ```
 
 {% configuration %}

diff --git a/source/_integrations/aquostv.markdown b/source/_integrations/aquostv.markdown
@@ -74,5 +74,6 @@ Currently known supported models:
 - LC-60SQ15U
 - LC-50US40 (no volume control, not fully tested)
 - LC-70LE650U
+- LC-70LE747E (no volume control)
 
 If your model is not on the list then give it a test, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.io/blob/current/source/_integrations/aquostv.markdown).
diff --git a/source/_integrations/calendar.google.markdown b/source/_integrations/calendar.google.markdown
@@ -221,8 +221,10 @@ For example, the actions following this condition will only be executed for even
 
 ```yaml
     condition:
-        condition: template
-        value_template: "{{is_state_attr('calendar.calendar_name', 'message', 'vacation') }}"
+      - condition: state
+        entity_id: calendar.calendar_name
+        state: vacation
+        attribute: message
 ```
 
 {% endraw %}
@@ -124,7 +124,7 @@ media_player:
   type: list
   keys:
     uuid:
-      description: UUID of a Cast device to add to Home Assistant. Use only if you don't want to add all available devices. The device won't be added until discovered through mDNS. In order to find the UUID for your device use a mDNS browser or advanced users can use the following Python command (adjust friendly names as required) - python3 -c "import pychromecast; print(pychromecast.get_listed_chromecasts(friendly_names=["Living Room TV", "Bedroom TV", "Office Chromecast"]))"
+      description: UUID of a Cast device to add to Home Assistant. Use only if you don't want to add all available devices. The device won't be added until discovered through mDNS. In order to find the UUID for your device use a mDNS browser or advanced users can use the following Python command (adjust friendly names as required) - `python3 -c "import pychromecast; print(pychromecast.get_listed_chromecasts(friendly_names=['Living Room TV', 'Bedroom TV', 'Office Chromecast']))"`
       required: false
       type: string
     ignore_cec: