home-assistant · ToRvaLDz · Feb 13, 2019 · Feb 13, 2019 · Feb 13, 2019 · Feb 13, 2019
diff --git a/.themes/classic/sass/partials/_sidebar.scss b/.themes/classic/sass/partials/_sidebar.scss
@@ -1,4 +1,3 @@
 @import "sidebar/base";
-@import "sidebar/googleplus";
 @import "sidebar/pinboard";
 @import "sidebar/delicious";
diff --git a/.themes/classic/sass/partials/sidebar/_googleplus.scss b/.themes/classic/sass/partials/sidebar/_googleplus.scss
diff --git a/.themes/classic/source/_includes/asides/googleplus.html b/.themes/classic/source/_includes/asides/googleplus.html
diff --git a/Gemfile.lock b/Gemfile.lock
@@ -53,9 +53,9 @@ GEM
       ruby_dep (~> 1.2)
     mercenary (0.3.6)
     method_source (0.8.2)
-    mini_portile2 (2.3.0)
-    nokogiri (1.8.2)
-      mini_portile2 (~> 2.3.0)
+    mini_portile2 (2.4.0)
+    nokogiri (1.10.1)
+      mini_portile2 (~> 2.4.0)
     octopress (3.0.11)
       jekyll (>= 2.0)
       mercenary (~> 0.3.2)

diff --git a/_config.yml b/_config.yml
@@ -32,8 +32,12 @@ destination: public/
 plugins_dir: plugins
 code_dir: downloads/code
 category_dir: blog/categories
+
 markdown: kramdown
+highlighter: rouge
 timezone: UTC
+liquid:
+  error_mode: strict
 
 kramdown:
   input: GFM
@@ -44,8 +48,6 @@ kramdown:
   smart_quotes:   lsquo,rsquo,ldquo,rdquo
   parse_block_html: true
 
-highlighter: rouge
-
 plugins:
   - jekyll-redirect-from
   - jekyll-time-to-read
@@ -97,11 +99,6 @@ twitter_tweet_button: true
 google_plus_one: true
 google_plus_one_size: standard
 
-# Google Plus Profile
-# Hidden: No visible button, just add author information to search results
-googleplus_user: +PaulusSchoutsen
-googleplus_hidden: true
-
 # Pinboard
 pinboard_user:
 pinboard_count: 3
@@ -141,9 +138,9 @@ social:
 
 # Home Assistant release details
 current_major_version: 0
-current_minor_version: 84
-current_patch_version: 3
-date_released: 2018-12-17
+current_minor_version: 88
+current_patch_version: 2
+date_released: 2019-02-27
 
 # 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/plugins/configuration.rb b/plugins/configuration.rb
@@ -2,7 +2,7 @@ module Jekyll
   class ConfigurationBlock < Liquid::Block
     TYPE_LINKS = {
       'action'       => '/docs/scripts/',
-      'device_class' => '/components/%{component}/#device-class',
+      'device_class' => '/docs/configuration/customizing-devices/#device-class',
       'template'     => '/docs/configuration/templating/',
       'icon'         => '/docs/configuration/customizing-devices/#icon',
     }

diff --git a/sass/custom/_paulus.scss b/sass/custom/_paulus.scss
@@ -411,6 +411,8 @@ p.note {
   .brand-logo-container {
     text-align: center;
     height: 87px;
+    margin-top: 50px;
+    margin-bottom: 25px;
 
     img {
       max-height: 67px;
@@ -458,7 +460,7 @@ a code {
   color: $primary-color;
 }
 
-twitterwidget {
+twitter-widget {
   margin-left: auto;
   margin-right: auto;
 }

diff --git a/sass/partials/_sidebar.scss b/sass/partials/_sidebar.scss
@@ -1,4 +1,3 @@
 @import "sidebar/base";
-@import "sidebar/googleplus";
 @import "sidebar/pinboard";
 @import "sidebar/delicious";
diff --git a/sass/partials/sidebar/_googleplus.scss b/sass/partials/sidebar/_googleplus.scss
diff --git a/source/_addons/check_config.markdown b/source/_addons/check_config.markdown
@@ -11,6 +11,16 @@ footer: true
 
 You can use this add-on to check whether your configuration files are valid against the new version of Home Assistant before you actually update your Home Assistant installation. This add-on will help you avoid errors due to breaking changes, resulting in a smooth update.
 
+### {% linkable_title How to use this add-on %} 
+
+1. Just start the add-on.
+2. Wait (On a Raspberry Pi it can take several minutes).
+3. If you see the following output then you are good to go to update Home Assistant: `[Info] Configuration check finished - no error found! :)`.
+
+If you get errors, then you should look for **Breaking Changes** against the version you specified for this add-on and change your configuration accordingly.
+
+### {% linkable_title Add-on configuration %}
+
 ```json
 {
   "version": "latest"

diff --git a/source/_addons/duckdns.markdown b/source/_addons/duckdns.markdown
@@ -55,7 +55,7 @@ Use the following configuration in Home Assistant to use the generated certifica
 
 ```yaml
 http:
-  base_url: my-domain.duckdns.org:8123
+  base_url: https://my-domain.duckdns.org:8123
   ssl_certificate: /ssl/fullchain.pem
   ssl_key: /ssl/privkey.pem
 ```

diff --git a/source/_addons/git_pull.markdown b/source/_addons/git_pull.markdown
@@ -13,12 +13,17 @@ Load and update configuration files for Home Assistant from a [Git](https://git-
 
 ```json
 {
-  "repository": "https://example.com/my_configs.git",
-  "auto_restart": false,
   "git_branch": "master",
   "git_command": "pull",
   "git_remote": "origin",
   "git_prune": "false",
+  "repository": "https://example.com/my_configs.git",
+  "auto_restart": false,
+  "restart_ignore": [
+    "ui-lovelace.yaml",
+    ".gitignore",
+    "exampledirectory/"
+  ],
   "repeat": {
     "active": false,
     "interval": 300
@@ -38,22 +43,22 @@ Load and update configuration files for Home Assistant from a [Git](https://git-
 }
 ```
 
-- **repository** (*Required*): Git URL to your repository (make sure to use double quotes). You have to add `.git` to your GitHub repository URL (see example configuration). The contents of the repository is assumed to be the root of Home Assistant `config/` folder. The configuration cannot be in a subdirectory, i.e., `configuration.yaml`, `groups.yaml`, etc. must be in the root of the repository.
 - **git_branch** (*Required*): Branch name of the Git repo. If left empty, the currently checked out branch will be updated. Leave this as 'master' if you are unsure.
-- **git_remote** (*Required*): Name of the tracked repository. Leave this as `origin` if you are unsure.
-- **git_prune** (*Required*): If set to true, the add-on will cleanup branches that are deleted on the remote repository, but still have cached entries on the local machine. Leave this as `false` if you are unsure.
-- **git_command** (*Required*): Must be either `pull` or `reset`. Leave this as `pull` if you are unsure.
-
-  * **pull**: Incorporates changes from a remote repository into the current branch. Will preserve any local changes to tracked files.
-  * **reset**: Will execute `git reset --hard` and overwrite any local changes to tracked files and update from the remote repository.
-
+- **git_command** (*Required*): `pull`/`reset`: Command to run. Leave this as `pull` if you are unsure.
+* **pull**: Incorporates changes from a remote repository into the current branch. Will preserve any local changes to tracked files.
+* **reset**: Will execute `git reset --hard` and overwrite any local changes to tracked files and update from the remote repository. Use with caution.
 <p class='note warning'>
-  Using the `reset` option will overwrite changes to tracked files. Tracked files are those visible in the Github repository or those given by the output on this command: `git ls-tree -r master --name-only`.
+  Using the `reset` option will overwrite changes to tracked files. Tracked files are those visible in the git repository or those given by the output on this command: `git ls-tree -r master --name-only`.
 </p>
-
-- **auto_restart** (*Optional*): Restart Home Assistant when the configuration has changed (and is valid).
-- **repeat/active** (*Optional*): Pull periodic for Git updates.
-- **repeat/interval** (*Optional*): Pull all x seconds and look for changes.
+- **git_remote** (*Required*): Name of the tracked repository. Leave this as `origin` if you are unsure.
+- **git_prune** (*Required*): `true`/`false`: If set to true, the add-on will clean-up branches that are deleted on the remote repository, but still have cached entries on the local machine. Leave this as `false` if you are unsure.
+
+- **repository** (*Required*): Git URL to your repository (make sure to use double quotes). You have to add `.git` to your repository URL (see example configuration).
+- **auto_restart** (*Required*): `true`/`false`: Restart Home Assistant when the configuration has changed (and is valid).
+- **restart_ignore** (*Optional*): When `auto_restart` is enabled, changes to these files will not make HA restart. Full directories to ignore can be specified.
+- **repeat**: Poll the repository for updates periodically automatically.
+* **active** (*Required*): `true`/`false`: Enable/disable automatic polling.
+* **interval** (*Required*): The interval in seconds to poll the repo for if automatic polling is enabled.
 - **deployment_user** (*Optional*): Username to use when authenticating to a repository with a username and password.
 - **deployment_password** (*Optional*): Password to use when authenticating to a repository.  Ignored if `deployment_user` is not set.
 - **deployment_key** (*Optional*): A private SSH key that will be used for communication during Git operations. This key is mandatory for ssh-accessed repositories, which are the ones with the following pattern: `<user>@<host>:<repository path>`.
@@ -63,7 +68,7 @@ Load and update configuration files for Home Assistant from a [Git](https://git-
   * **ecdsa**
   * **ed25519**
   * **rsa**
-  
+
 The protocol is typically known by the suffix of the private key --e.g., a key file named `id_rsa` will be a private key using `rsa` protocol.
 
 <p class='note warning'>

diff --git a/source/_addons/homematic.markdown b/source/_addons/homematic.markdown
@@ -118,7 +118,7 @@ homematic:
       port: 2000
     hmip:
       host: core-homematic
-      port: 2001
+      port: 2010
 ```
 
 ## {% linkable_title Raspberry Pi3 %}

diff --git a/source/_addons/lets_encrypt.markdown b/source/_addons/lets_encrypt.markdown
@@ -79,4 +79,26 @@ Use this in your `automations.yaml` to attempt certificate renewal each day at m
       addon: core_letsencrypt
 ```
 
+If you are using the [Nginx Proxy add-on] you will need need to stop this during the renewal process. This can be achieved by stopping the add-on whilst restarting the Let's Encrypt add-on. This can be achieved the following configuration: 
+
+```yaml
+- id: letsencrypt-renewal
+  alias: 'LetsEncrypt renewal'
+  trigger:
+  - platform: time
+    at: '00:00:00'
+  action:
+  - service: hassio.addon_stop
+    data:
+      addon: core_nginx_proxy
+  - service: hassio.addon_restart
+    data:
+      addon: core_letsencrypt
+  - delay: '00:01:30'
+  - service: hassio.addon_start
+    data:
+      addon: core_nginx_proxy
+```
+
 [DuckDNS add-on]: /addons/duckdns/
+[Nginx Proxy add-on]: /addons/nginx_proxy/
diff --git a/source/_addons/mosquitto.markdown b/source/_addons/mosquitto.markdown
@@ -55,6 +55,24 @@ This add-on is attached to the Home Assistant user system, so mqtt clients can m
 
 To use the Mosquitto as [broker](/docs/mqtt/broker/#run-your-own), go to the integration page and install the configuration with one click. If you have old MQTT settings available, remove this old integration and restart Home Assistant to see the new one.
 
+#### {% linkable_title Using Mosquitto with Hass.io %}
+
+1. Install the [Mosquitto add-on](/addons/mosquitto/) with the default configuration via 'Hass.io > ADD-ON STORE'. (Don't forget to start the add-on & verify that 'Start on boot' is enabled.)
+
+2. Create a new user for MQTT via the `Configuration > Users (manage users)`. (Note: This name cannot be "homeassistant" or "addon")
+
+3. Once back on-line, return to `Configuration > Integrations` and select configure next to `MQTT`.
+
+```
+  Broker: YOUR_HASSIO_IP_ADDRESS
+  Port: 1883
+  Username: MQTT_USERNAME
+  Password: MQTT_PASSWORD
+```
+
+Note: .yaml modifications are not required. 
+See [testing your setup](/docs/mqtt/testing/) to verify the steps above.
+
 ### {% linkable_title Disable listening on insecure (1883) ports %}
 
 Remove the ports from the add-on page network card (set them as blank) to disable them.

diff --git a/source/_addons/nginx_proxy.markdown b/source/_addons/nginx_proxy.markdown
@@ -11,7 +11,7 @@ footer: true
 
 Sets up an SSL proxy with NGINX and redirect port 80 to 443. Make sure you have generated a certificate before you start this add-on.
 
-In the `http` section of the `configuration.yaml` file remove `ssl_certificate` and `ssl_key` and don't enter the port in the `base_url` to avoid an HTTP 502 error.
+In the `http` section of the `configuration.yaml` file remove `ssl_certificate`, `ssl_key` and `server_port` and don't enter the port in the `base_url` to avoid an HTTP 502 error.
 
 ```json
 {

diff --git a/source/_addons/samba.markdown b/source/_addons/samba.markdown
@@ -13,7 +13,7 @@ featured: true
 This add-on allows you to set up a [Samba](https://samba.org/) server to access Hass.io folders using Windows network shares.
 
 <p class='note warning'>
-Be careful when setting up port forwarding for remote access. If you don't restrict access by setting a username and strong password, your configuration could be exposed to the entire internet!
+Be careful when setting up port forwarding for remote access. If you don't restrict access by setting a username and strong password, your configuration could be exposed to the entire Internet!
 </p>
 
 ```json
@@ -37,7 +37,7 @@ workgroup:
   default: "`WORKGROUP`"
   type: string
 username:
-  description: Username for logging in if guest login is not used.
+  description: Username for logging in.
   required: true
   type: string
 password:

diff --git a/source/_addons/tellstick.markdown b/source/_addons/tellstick.markdown
@@ -92,6 +92,8 @@ code:
   type: string
 {% endconfiguration %}
 
+For more information about the configuration including protocols, see the [telldus documentation](https://developer.telldus.com/wiki/TellStick_conf).
+
 ## {% linkable_title Service calls %}
 
 If you wish to teach a self-learning device in your TellStick configuration:
-Original file line number
+Diff line change
@@ Expand Up / @@ -11,7 +11,7 @@ footer: true @@
     Sets up an SSL proxy with NGINX and redirect port 80 to 443. Make sure you have generated a certificate before you start this add-on.
-    In the `http` section of the `configuration.yaml` file remove `ssl_certificate` and `ssl_key` and don't enter the port in the `base_url` to avoid an HTTP 502 error.
+    In the `http` section of the `configuration.yaml` file remove `ssl_certificate`, `ssl_key` and `server_port` and don't enter the port in the `base_url` to avoid an HTTP 502 error.
     ```json
     {
@@ Expand Down @@