Merge branch 'current' into next

Thrilleratplay · Mar 7, 2020 · bdb8e5b · bdb8e5b
2 parents 57edc2a + 47f27e3
commit bdb8e5b
Show file tree

Hide file tree

Showing 1,359 changed files with 1,302 additions and 1,242 deletions.
diff --git a/_config.yml b/_config.yml
@@ -101,8 +101,8 @@ social:
 # Home Assistant release details
 current_major_version: 0
 current_minor_version: 106
-current_patch_version: 4
-date_released: 2020-03-02
+current_patch_version: 5
+date_released: 2020-03-03
 
 # 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/sass/custom/_component_page.scss b/sass/custom/_component_page.scss
@@ -1,8 +1,8 @@
-#components-page{
-  .component-search{
+#components-page {
+  .component-search {
     margin-bottom: 24px;
 
-    input{
+    input {
       width: 100%;
       padding: 10px;
 
@@ -35,8 +35,8 @@
         margin-bottom: 8px;
 
         &.current {
-          background-color: #3A5561;
-          background-image: linear-gradient(to bottom, #3A5561,#3F6B7D);
+          background-color: #3a5561;
+          background-image: linear-gradient(to bottom, #3a5561, #3f6b7d);
         }
       }
     }
@@ -88,7 +88,7 @@
   align-items: flex-start;
   margin: -4px; // grid trick, has to match option-card's margin
 
-  p.note{
+  p.note {
     width: 100%;
   }
 
@@ -100,20 +100,22 @@
     background-color: #fefefe;
     margin: 4px;
     border-radius: 2px;
-    box-shadow: 0 2px 2px 0 rgba(0, 0, 0, 0.14), 0 1px 5px 0 rgba(0, 0, 0, 0.12), 0 3px 1px -2px rgba(0, 0, 0, 0.2);
+    box-shadow: 0 2px 2px 0 rgba(0, 0, 0, 0.14), 0 1px 5px 0 rgba(0, 0, 0, 0.12),
+      0 3px 1px -2px rgba(0, 0, 0, 0.2);
     padding: 8px;
     text-align: center;
     text-decoration: none;
 
     .img-container {
       height: 50px;
-      margin: 8px 0;
+      margin: 12px 0;
       font: 0/0 a;
 
-      &:before {    /* create a full-height inline block pseudo=element */
-        content: ' ';
+      &:before {
+        /* create a full-height inline block pseudo=element */
+        content: " ";
         display: inline-block;
-        vertical-align: middle;  /* vertical alignment of the inline element */
+        vertical-align: middle; /* vertical alignment of the inline element */
         height: 100%;
       }
 
@@ -127,133 +129,137 @@
     }
 
     .title {
+      display: -webkit-box;
+      -webkit-line-clamp: 2;
+      -webkit-box-orient: vertical;
+      overflow: hidden;
+
       text-decoration: none;
       font-size: 18px;
       color: #000;
       line-height: 1.3em;
       height: 2.6em;
-    }
-
-    .category {
-      font-size: 14px;
-      color: #AAA;
+      margin-top: 20px;
     }
   }
 
   // fade-in animation
-  &.show-items .option-card{
-    opacity:0;
-    -webkit-animation:new-item-animation .2s linear forwards;
-    -o-animation:new-item-animation .2s linear forwards;
-    animation:new-item-animation .2s linear forwards;
+  &.show-items .option-card {
+    opacity: 0;
+    -webkit-animation: new-item-animation 0.2s linear forwards;
+    -o-animation: new-item-animation 0.2s linear forwards;
+    animation: new-item-animation 0.2s linear forwards;
   }
 
   // fade-out animation
-  &.remove-items .option-card{
-    -webkit-animation:removed-item-animation .2s cubic-bezier(.55,-0.04,.91,.94) forwards;
-    -o-animation:removed-item-animation .2s cubic-bezier(.55,-0.04,.91,.94) forwards;
-    animation:removed-item-animation .2s cubic-bezier(.55,-0.04,.91,.94) forwards
+  &.remove-items .option-card {
+    -webkit-animation: removed-item-animation 0.2s
+      cubic-bezier(0.55, -0.04, 0.91, 0.94) forwards;
+    -o-animation: removed-item-animation 0.2s
+      cubic-bezier(0.55, -0.04, 0.91, 0.94) forwards;
+    animation: removed-item-animation 0.2s cubic-bezier(0.55, -0.04, 0.91, 0.94)
+      forwards;
   }
 }
 
 // animations for fade-in and fade-out effects of option-cards
 @keyframes new-item-animation {
   from {
-    opacity:0;
-    -webkit-transform:scale(0);
-    -ms-transform:scale(0);
-    -o-transform:scale(0);
-    transform:scale(0)
+    opacity: 0;
+    -webkit-transform: scale(0);
+    -ms-transform: scale(0);
+    -o-transform: scale(0);
+    transform: scale(0);
   }
   to {
-    opacity:1;
-    -webkit-transform:scale(1);
-    -ms-transform:scale(1);
-    -o-transform:scale(1);
-    transform:scale(1)
+    opacity: 1;
+    -webkit-transform: scale(1);
+    -ms-transform: scale(1);
+    -o-transform: scale(1);
+    transform: scale(1);
   }
 }
 @-webkit-keyframes new-item-animation {
   from {
-    opacity:0;
-    -webkit-transform:scale(0);
-    transform:scale(0)
+    opacity: 0;
+    -webkit-transform: scale(0);
+    transform: scale(0);
   }
   to {
-    opacity:1;
-    -webkit-transform:scale(1);
-    transform:scale(1)
+    opacity: 1;
+    -webkit-transform: scale(1);
+    transform: scale(1);
   }
 }
 @-o-keyframes new-item-animation {
   from {
-    opacity:0;
-    -o-transform:scale(0);
-    transform:scale(0)
+    opacity: 0;
+    -o-transform: scale(0);
+    transform: scale(0);
   }
   to {
-    opacity:1;
-    -o-transform:scale(1);
-    transform:scale(1)
+    opacity: 1;
+    -o-transform: scale(1);
+    transform: scale(1);
   }
 }
 
 // space blocker animation
 @keyframes openspace {
   to {
-    height:auto
+    height: auto;
   }
 }
 
 @-webkit-keyframes openspace {
   to {
-    height:auto
+    height: auto;
   }
 }
 @-o-keyframes openspace {
   to {
-    height:auto
+    height: auto;
   }
 }
 
 // removal animation
 @keyframes removed-item-animation {
   from {
-    opacity:1;
-    -webkit-transform:scale(1);
-    -ms-transform:scale(1);
-    -o-transform:scale(1);
-    transform:scale(1)
+    opacity: 1;
+    -webkit-transform: scale(1);
+    -ms-transform: scale(1);
+    -o-transform: scale(1);
+    transform: scale(1);
   }
   to {
-    -webkit-transform:scale(0);
-    -ms-transform:scale(0);
-    -o-transform:scale(0);
-    transform:scale(0);
-    opacity:0
+    -webkit-transform: scale(0);
+    -ms-transform: scale(0);
+    -o-transform: scale(0);
+    transform: scale(0);
+    opacity: 0;
   }
 }
 @-webkit-keyframes removed-item-animation {
   from {
-    opacity:1;
-    -webkit-transform:scale(1);
-    transform:scale(1)
+    opacity: 1;
+    -webkit-transform: scale(1);
+    transform: scale(1);
   }
   to {
-    -webkit-transform:scale(0);
-    transform:scale(0);
-    opacity:0
+    -webkit-transform: scale(0);
+    transform: scale(0);
+    opacity: 0;
   }
 }
 @-o-keyframes removed-item-animation {
   from {
-    opacity:1;
-    -o-transform:scale(1);
-    transform:scale(1)
+    opacity: 1;
+    -o-transform: scale(1);
+    transform: scale(1);
   }
   to {
-    -o-transform:scale(0);
-    transform:scale(0);
-    opacity:0
+    -o-transform: scale(0);
+    transform: scale(0);
+    opacity: 0;
   }
 }
diff --git a/source/_docs/ecosystem/certificates/lets_encrypt.markdown b/source/_docs/ecosystem/certificates/lets_encrypt.markdown
@@ -362,7 +362,7 @@ https://YOUR-HA-IP:8123
 
 Some cases such as this are where your router does not allow 'loopback' or where there is a problem with incoming connections due to technical failure. In these cases you can still use your internal connection and safely ignore the warnings.
 
-If you were previously using a webapp on your phone/tablet to access your Home Assistant you should delete the old one and create a new one with the new address. The old one will no longer work as it is not keyed to your new, secure URL.  Instructions for creating your new webapp can be found [here](/docs/frontend/mobile/).
+If you were previously using a webapp on your phone/tablet to access your Home Assistant you should delete the old one and create a new one with the new address. The old one will no longer work as it is not keyed to your new, secure URL.
 
 All done? Accessing your Home Assistant from across the world with your DuckDNS URL and a lovely secure logo on your browser? Ace! Now let's clean up our port forwards so that we are only exposing the parts of our network that are absolutely necessary to the outside world.
 

diff --git a/source/_docs/ecosystem/certificates/tls_self_signed_certificate.markdown b/source/_docs/ecosystem/certificates/tls_self_signed_certificate.markdown
@@ -23,9 +23,11 @@ Change to your Home Assistant [configuration directory](/getting-started/configu
 The certificate **must** be `.pem` extension.
 
 ```bash
-openssl req -sha256 -newkey rsa:4096 -nodes -keyout privkey.pem -x509 -days 730 -out fullchain.pem
+openssl req -sha256 -addext "subjectAltName = IP:X.X.X.X" -newkey rsa:4096 -nodes -keyout privkey.pem -x509 -days 730 -out fullchain.pem
 ```
 
+Where the `X.X.X.X` must be replaced with the IP address of your local machine running Home Assistant (e.g., `192.168.1.20`).
+
 For details about the parameters, please check the OpenSSL documentation. Provide the requested information during the generation process.
 
 At the end you will have two files called `privkey.pem` and `fullchain.pem`. The key and the certificate.

diff --git a/source/_docs/frontend/mobile.markdown b/source/_docs/frontend/mobile.markdown
diff --git a/source/_docs/installation.markdown b/source/_docs/installation.markdown
@@ -96,13 +96,13 @@ These guides are provided as-is. Some of these install methods are more limited
   </a>
   <a class='option-card' href='/docs/installation/macos/'>
     <div class='img-container'>
-      <img src='/images/supported_brands/apple.png' />
+      <img src='https://brands.home-assistant.io/ios/icon.png' />
     </div>
     <div class='title'>macOS</div>
   </a>
   <a class='option-card' href='/docs/installation/synology/'>
     <div class='img-container'>
-      <img src='/images/supported_brands/synology.png' />
+      <img src='https://brands.home-assistant.io/synology/logo.png' />
     </div>
     <div class='title'>Synology</div>
   </a>
@@ -114,7 +114,7 @@ These guides are provided as-is. Some of these install methods are more limited
   </a>
   <a class='option-card' href='/hassio/installation/#alternative-install-on-a-generic-linux-host'>
     <div class='img-container'>
-      <img src='/images/supported_brands/home-assistant.png' />
+      <img src='https://brands.home-assistant.io/homeassistant/icon.png' />
     </div>
     <div class='title'>Home Assistant Supervised <br> on generic Linux server</div>
   </a>

diff --git a/source/_docs/installation/docker.markdown b/source/_docs/installation/docker.markdown
@@ -4,6 +4,14 @@ description: "Instructions to install Home Assistant on a Docker."
 redirect_from: /getting-started/installation-docker/
 ---
 
+<div class='note warning'>
+
+These below instructions are for an installation of Home Assistant Core running in your own Docker environment, which you manage yourself.
+
+For an installation of Home Assistant Supervised, which includes Home Assistant's add-on ecosystem, see the instructions for installing [Home Assistant Supervised on a generic Linux host](/hassio/installation/#alternative-install-home-assistant-supervised-on-a-generic-linux-host/).
+
+</div>
+
 ## Platform Installation
 
 Installation with Docker is straightforward. Adjust the following command so that `/PATH_TO_YOUR_CONFIG` points at the folder where you want to store your configuration and run it:

diff --git a/source/_docs/installation/updating.markdown b/source/_docs/installation/updating.markdown
@@ -6,15 +6,15 @@ redirect_from: /getting-started/updating/
 
 <div class='note warning'>
 
-The upgrade process differs depending on the installation you have, so please review the documentation that is specific to your install [Home Assistant](/hassio/) or [Home Assistant Core](/docs/installation/virtualenv/#upgrading-home-assistant).
+The upgrade process differs depending on the installation you have, so please review the documentation that is specific to your install: [Home Assistant](/hassio/) or [Home Assistant Core](/docs/installation/virtualenv/#upgrading-home-assistant).
 
 </div>
 
-Check what's new in the latest version and potentially impacts your system in [Home Assistant release notes](https://github.com/home-assistant/home-assistant/releases). It is good practice to review these release notes and pay close attention to the **Breaking Changes** that are listed there. If you haven't done an update for a while, you should also check previous release notes as they can also contain relevant **Breaking Changes**. **Breaking Changes** may require configuration updates for your components. If you missed this and Home Assistant refuses to start, check the log file in the [configuration](/docs/configuration/) directory, e.g., `.homeassistant/home-assistant.log`, for details about broken components.
+Check what's new in the latest version and potentially impacts your system in the [Home Assistant release notes](https://github.com/home-assistant/home-assistant/releases). It is good practice to review these release notes and pay close attention to the **Breaking Changes** that are listed there. If you haven't done an update for a while, you should also check previous release notes as they can also contain relevant **Breaking Changes**. These **Breaking Changes** may require configuration updates for your components. If you missed this and Home Assistant refuses to start, check the log file in the [configuration](/docs/configuration/) directory, e.g., `.homeassistant/home-assistant.log`, for details about broken components.
 
 <div class='note'>
 
-To avoid permission errors, the upgrade must be run as the same user as the installation was completed, again review the documentation specific to your install [Home Assistant](/hassio/) or [Home Assistant Core](/docs/installation/virtualenv).
+To avoid permission errors, the upgrade must be run as the same user as was used during the initial installation, again review the documentation specific to your install [Home Assistant](/hassio/) or [Home Assistant Core](/docs/installation/virtualenv).
 
 </div>
 
@@ -36,7 +36,7 @@ For a Raspberry Pi Docker container, simply pull the latest one:
 sudo docker pull homeassistant/raspberrypi3-homeassistant:latest
 ```
 
-After updating, you must start/restart Home Assistant for the changes to take effect. This means that you will have to restart `hass` itself or the [autostarting](/docs/autostart/) daemon (if applicable). Startup can take considerable amount of time (i.e., minutes) depending on your device. This is because all requirements are updated as well.
+After updating, you must start/restart Home Assistant for the changes to take effect. This means that you will have to restart `hass` itself or the [autostarting](/docs/autostart/) daemon (if applicable). Startup can take a considerable amount of time (i.e., minutes) depending on your device. This is because all requirements are updated as well.
 
 [BRUH automation](https://www.bruhautomation.io/) has created [a tutorial video](https://www.youtube.com/watch?v=tuG2rs1Cl2Y) explaining how to upgrade Home Assistant.
 
@@ -50,7 +50,7 @@ pip3 install homeassistant==0.XX.X
 
 #### Run the beta version
 
-If you would like to test next release before anyone else, you can install the beta version released every two weeks:
+If you would like to test the next release before anyone else, you can install the beta version released every two weeks:
 
 ```bash
 pip3 install --pre --upgrade homeassistant