home-assistant · engrbm87 · Aug 7, 2019 · Aug 21, 2019 · Aug 21, 2019 · Aug 22, 2019
diff --git a/.gitignore b/.gitignore
@@ -6,6 +6,7 @@
 public
 source/_stash
 source/stylesheets/screen.css
+source/.jekyll-cache/
 vendor
 node_modules
 source/.jekyll-metadata

diff --git a/.gitpod.yml b/.gitpod.yml
@@ -11,5 +11,5 @@ github:
     pullRequestsFromForks: true
     addCheck: true
     addComment: false
-    addBadge: true
+    addBadge: false
     addLabel: false
diff --git a/Gemfile b/Gemfile
@@ -3,8 +3,8 @@ source "https://rubygems.org"
 ruby "> 2.5.0"
 
 group :development do
-  gem 'rake', '12.3.2'
-  gem 'jekyll', '3.8.6'
+  gem 'rake', '12.3.3'
+  gem 'jekyll', '4.0.0'
   gem 'compass', '1.0.3'
   gem 'sass-globbing', '1.1.5'
   gem 'stringex', '2.8.5'
@@ -18,5 +18,5 @@ group :jekyll_plugins do
   gem 'jekyll-commonmark-ghpages', '0.1.6'
 end
 
-gem 'sinatra', '2.0.5'
+gem 'sinatra', '2.0.6'
 gem 'nokogiri', '1.10.4'
diff --git a/Gemfile.lock b/Gemfile.lock
@@ -27,21 +27,23 @@ GEM
     ffi (1.11.1)
     forwardable-extended (2.6.0)
     http_parser.rb (0.6.0)
-    i18n (0.9.5)
+    i18n (1.6.0)
       concurrent-ruby (~> 1.0)
-    jekyll (3.8.6)
+    jekyll (4.0.0)
       addressable (~> 2.4)
       colorator (~> 1.0)
       em-websocket (~> 0.5)
-      i18n (~> 0.7)
-      jekyll-sass-converter (~> 1.0)
+      i18n (>= 0.9.5, < 2)
+      jekyll-sass-converter (~> 2.0)
       jekyll-watch (~> 2.0)
-      kramdown (~> 1.14)
+      kramdown (~> 2.1)
+      kramdown-parser-gfm (~> 1.0)
       liquid (~> 4.0)
       mercenary (~> 0.3.3)
       pathutil (~> 0.9)
-      rouge (>= 1.7, < 4)
+      rouge (~> 3.0)
       safe_yaml (~> 1.0)
+      terminal-table (~> 1.8)
     jekyll-commonmark (1.3.1)
       commonmarker (~> 0.14)
       jekyll (>= 3.7, < 5.0)
@@ -52,15 +54,17 @@ GEM
     jekyll-paginate (1.1.0)
     jekyll-redirect-from (0.15.0)
       jekyll (>= 3.3, < 5.0)
-    jekyll-sass-converter (1.5.2)
-      sass (~> 3.4)
+    jekyll-sass-converter (2.0.0)
+      sassc (> 2.0.1, < 3.0)
     jekyll-sitemap (1.3.1)
       jekyll (>= 3.7, < 5.0)
     jekyll-time-to-read (0.1.2)
       jekyll
     jekyll-watch (2.2.1)
       listen (~> 3.0)
-    kramdown (1.17.0)
+    kramdown (2.1.0)
+    kramdown-parser-gfm (1.1.0)
+      kramdown (~> 2.0)
     liquid (4.0.3)
     listen (3.1.5)
       rb-fsevent (~> 0.9, >= 0.9.4)
@@ -76,43 +80,48 @@ GEM
       forwardable-extended (~> 2.6)
     public_suffix (3.1.1)
     rack (2.0.7)
-    rack-protection (2.0.5)
+    rack-protection (2.0.6)
       rack
-    rake (12.3.2)
+    rake (12.3.3)
     rb-fsevent (0.10.3)
     rb-inotify (0.10.0)
       ffi (~> 1.0)
-    rouge (3.6.0)
+    rouge (3.9.0)
     ruby-enum (0.7.2)
       i18n
     ruby_dep (1.5.0)
     safe_yaml (1.0.5)
     sass (3.4.25)
     sass-globbing (1.1.5)
       sass (>= 3.1)
-    sinatra (2.0.5)
+    sassc (2.1.0)
+      ffi (~> 1.9)
+    sinatra (2.0.6)
       mustermann (~> 1.0)
       rack (~> 2.0)
-      rack-protection (= 2.0.5)
+      rack-protection (= 2.0.6)
       tilt (~> 2.0)
     stringex (2.8.5)
+    terminal-table (1.8.0)
+      unicode-display_width (~> 1.1, >= 1.1.1)
     tilt (2.0.9)
+    unicode-display_width (1.6.0)
 
 PLATFORMS
   ruby
 
 DEPENDENCIES
   compass (= 1.0.3)
-  jekyll (= 3.8.6)
+  jekyll (= 4.0.0)
   jekyll-commonmark-ghpages (= 0.1.6)
   jekyll-paginate (= 1.1.0)
   jekyll-redirect-from (= 0.15.0)
   jekyll-sitemap (= 1.3.1)
   jekyll-time-to-read (= 0.1.2)
   nokogiri (= 1.10.4)
-  rake (= 12.3.2)
+  rake (= 12.3.3)
   sass-globbing (= 1.1.5)
-  sinatra (= 2.0.5)
+  sinatra (= 2.0.6)
   stringex (= 2.8.5)
 
 RUBY VERSION

diff --git a/_config.yml b/_config.yml
@@ -98,9 +98,9 @@ social:
 
 # Home Assistant release details
 current_major_version: 0
-current_minor_version: 97
-current_patch_version: 2
-date_released: 2019-08-12
+current_minor_version: 98
+current_patch_version: 0
+date_released: 2019-08-28
 
 # 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/source/_components/androidtv.markdown b/source/_components/androidtv.markdown
@@ -20,11 +20,11 @@ For Fire TV devices, the instructions are as follows:
 
 - Turn on ADB Debugging on your Amazon Fire TV:
   - From the main (Launcher) screen, select Settings.
-  - Select System > Developer Options.
+  - Select My Fire TV > Developer Options.
   - Select ADB Debugging.
 - Find Amazon Fire TV device IP address:
   - From the main (Launcher) screen, select Settings.
-  - Select System > About > Network.
+  - Select My Fire TV > About > Network.
 
 ## Configuration
 

diff --git a/source/_components/coolmaster.markdown b/source/_components/coolmaster.markdown
@@ -44,8 +44,8 @@ supported_modes:
       description: Heat mode.
     cool:
       description: Cool mode.
-    auto:
-      description: Auto mode.
+    heat_cool:
+      description: Heat/Cool mode (CoolMasterNet refers to it as Auto).
     dry:
       description: Dry mode.
     fan_only:

diff --git a/source/_components/fritz.markdown b/source/_components/fritz.markdown
@@ -15,7 +15,7 @@ The `fritz` platform offers presence detection by looking at connected devices t
 ## Setup
 
 <div class='note warning'>
-It might be necessary to install additional packages: <code>sudo apt-get install python3-lxml libxslt-dev libxml2-dev zlib1g-dev</code>
+If not running Hass.io it might be necessary to install additional packages: <code>sudo apt-get install python3-lxml libxslt-dev libxml2-dev zlib1g-dev</code>
 If you installed Home Assistant in a virtualenv, run the following commands inside it: <code>pip3 install lxml</code>; be patient this will take a while.</div>
 
 ## Configuration

diff --git a/source/_components/google_assistant.markdown b/source/_components/google_assistant.markdown
@@ -200,17 +200,20 @@ Currently, the following domains are available to be used with Google Assistant,
 - climate (temperature setting, hvac_mode)
 - vacuum (dock/start/stop/pause)
 - sensor (temperature setting, only for temperature sensor)
+- Alarm Control Panel (Arm and Disarm alarm control panel entities)
 
 <div class='note warning'>
   The domain groups contains groups containing all items, by example group.all_automations. When telling Google Assistant to shut down everything, this will lead in this example to disabling all automations
 </div>
 
 ### Secure Devices
 
-Certain devices are considered secure, including anything in the `lock` domain, and `covers` with device types `garage` and `door`.
+Certain devices are considered secure, including anything in the `lock` domain, `alarm_control_panel` domain and `covers` with device types `garage` and `door`.
 
 By default these cannot be opened by Google Assistant unless a `secure_devices_pin` is set up. To allow opening, set the `secure_devices_pin` to something and you will be prompted to speak the pin when opening the device. Closing and locking these devices does not require a pin.
 
+For the Alarm Control Panel if a code is configured it must be the same as the `secure_device_pin` set as it will use it when arming or disarming the system. if `code_armed_required` is set to false then the system will arm without prompting for the pin.
+
 ### Media Player Sources
 
 Media Player sources are sent via the Modes trait in Google Assistant.

diff --git a/source/_components/heos.markdown b/source/_components/heos.markdown
@@ -76,7 +76,7 @@ You can play a HEOS favorite by number or name with the `media_player.play_media
 | Attribute              | Description
 | ---------------------- | ---------------------------------------------------------|
 | `entity_id`            | `entity_id` of the player
-| `media_content_type`   | Set to the value `playlist`
+| `media_content_type`   | Set to the value `favorite`
 | `media_content_id`     | The nubmer (i.e. `1`) or name (i.e. `Thumbprint Radio`) of the HEOS favorite
 
 #### Play Playlist
@@ -157,4 +157,4 @@ logger:
 If the HEOS controller is not signed in to a HEOS account, HEOS favorites will not be populated in the media player source selection and the service `media_player.play_media` for `favorite` and `playlist` will fail. Additionally, the following warning will be logged at startup:
 > IP_ADDRESS is not logged in to a HEOS account and will be unable to retrieve HEOS favorites: Use the 'heos.sign_in' service to sign-in to a HEOS account
 
-To resolve this issue, use the `heos.sign_out` service to sign the controller into an account as documented above. This only needs to be performed once, as the controller will remain signed in while the account credentials are valid.
+To resolve this issue, use the `heos.sign_in` service to sign the controller into an account as documented above. This only needs to be performed once, as the controller will remain signed in while the account credentials are valid.
diff --git a/source/_components/nissan_leaf.markdown b/source/_components/nissan_leaf.markdown
@@ -16,7 +16,6 @@ The `nissan_leaf` integration offers integration with the [NissanConnect EV](htt
 
 * sensors for the battery status, range and charging status
 * a switch to start and stop the climate control
-* a device tracker to locate the car (only on later Leaf models)
 * services to request updates from the car and to request the car starts charging.
 
 ## Configuration
@@ -43,11 +42,6 @@ region:
   description: The region where the NissanConnect EV account is registered. Should be one of the following, NE (for Europe), NNA (USA), NCI (Canada), NMA (Australia), NML (Japan).
   required: true
   type: string
-nissan_connect:
-  description: If your car has the updated head unit (NissanConnect rather than Carwings) then the location can be acquired and exposed via a device tracker. If you have Carwings then this should be set to false. The easiest way to identify NissanConnect is if the T&C buttons are orange and blue, for CarWings they're both blue, or just look for anything saying "CarWings" in Settings area of the infotainment system.
-  required: false
-  type: boolean
-  default: true
 update_interval:
   description: The interval between updates if the climate control is off and the car is not charging. Set in any time unit (e.g. minutes, hours, days!).
   required: false
@@ -75,7 +69,6 @@ nissan_leaf:
   username: "YOUR_USERNAME"
   password: "YOUR_PASSWORD"
   region: "YOUR_REGION"
-  nissan_connect: true
   update_interval:
     hours: 1
   update_interval_charging:
@@ -87,7 +80,7 @@ nissan_leaf:
 
 ## Starting a Charge
 
-You can use the `nissan_leaf.start_charge` service to send a request to the Nissan servers to start a charge. The car must be plugged in!  The service requires you to provide the vehicle identification number (VIN) as a parameter. You can see the VIN on the attributes of all the entities created by this component, except the device_tracker.
+You can use the `nissan_leaf.start_charge` service to send a request to the Nissan servers to start a charge. The car must be plugged in!  The service requires you to provide the vehicle identification number (VIN) as a parameter. You can see the VIN on the attributes of all the entities created by this component.
 
 ```yaml
 - service: nissan_leaf.start_charge
@@ -125,6 +118,7 @@ You can also use the `nissan_leaf.update` service to request an on-demand update
 * The Nissan APIs do not allow charging to be stopped remotely.
 * The Nissan servers have a history of being unstable, therefore please confirm that the official Nissan Leaf app/website is working correctly before reporting bugs.
 * In the UK the cut-off for Carwings was the 16 plate 24 kWh and the 65 plate 30 kWh. Cars after this have NissanConnect.
+* As of 25 July 2019 the MyCarFinder API is not longer available, hence the device_tracker support has been removed.
 
 Please report bugs using the following logger configuration.
 
@@ -133,7 +127,6 @@ logger:
   default: critical
   logs:
     homeassistant.components.nissan_leaf: debug
-    homeassistant.components.device_tracker.nissan_leaf: debug
     homeassistant.components.sensor.nissan_leaf: debug
     homeassistant.components.switch.nissan_leaf: debug
 ```
diff --git a/source/_components/notify.markdown b/source/_components/notify.markdown
@@ -50,7 +50,7 @@ The automation equivalent would be:
 ```yaml
 action:
   service: notify.notify
-  data:
+  data_template:
     message: "The sun is {% raw %}{% if is_state('sun.sun', 'above_horizon') %}up{% else %}down{% endif %}{% endraw %}!"
 ```
 

diff --git a/source/_components/python_script.markdown b/source/_components/python_script.markdown
@@ -45,6 +45,7 @@ hass.bus.fire(name, { "wow": "from a Python script!" })
 The following example shows how to call a service from `python_script`. This script takes two parameters: `entity_id` (required), `rgb_color` (optional) and calls `light.turn_on` service by setting the brightness value to `255`.
 
 ```python
+# turn_on_light.py
 entity_id = data.get('entity_id')
 rgb_color = data.get('rgb_color', [255, 255, 255])
 if entity_id is not None:
@@ -57,4 +58,21 @@ The above `python_script` can be called using the following JSON as an input.
 {"entity_id": "light.bedroom", "rgb_color": [255, 0, 0] }
 ```
 
+## Documenting your Python scripts
+
+You can add descriptions for your Python scripts that will be shown in the Call Services tab of the Developer Options page. To do so, simply create a `services.yaml` file in your `<config>/python_scripts` folder. Using the above Python script as an example, the `services.yaml` file would look like:
+
+```yaml
+# services.yaml
+turn_on_light:
+  description: Turn on a light and set its color. 
+  fields:
+    entity_id:
+      description: The light that will be turned on.
+      example: light.bedroom
+    rgb_color:
+      description: The color to which the light will be set.
+      example: [255, 0, 0]
+```
+
 For more examples, visit the [Scripts section](https://community.home-assistant.io/c/projects/scripts) in our forum.
diff --git a/source/_components/rejseplanen.markdown b/source/_components/rejseplanen.markdown
@@ -53,6 +53,11 @@ stop_id:
   description: The ID of the public transport stop.
   required: true
   type: string
+name:
+  description: "The name of the sensor. Entity ID for the sensor will be created based on this name. E.g., Glostrup St becomes `sensor.glostrup_st`. It's optional but recommended if you define more than one sensor."
+  required: false
+  type: string
+  default: "Next departure"
 route:
   description: List of route names.
   required: false
@@ -105,6 +110,7 @@ A more extensive example on how to use this sensor:
 # Example configuration.yaml entry
 sensor:
   - platform: rejseplanen
+    name: 'Elmegade 350S'
     stop_id: '000045740'
     route: 'Bus 350S'
     direction:

diff --git a/source/_components/stream.markdown b/source/_components/stream.markdown
@@ -59,14 +59,14 @@ To do this add either [picture-entity](/lovelace/picture-entity/), [picture-glan
 
 Some users on manual installs may see the following error in their logs after restarting:
 
-```
+```text
 2019-03-12 08:49:59 ERROR (SyncWorker_5) [homeassistant.util.package] Unable to install package av==6.1.2: Command "/home/pi/home-assistant/bin/python3 -u -c "import setuptools, tokenize;__file__='/tmp/pip-install-udfl2b3t/av/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-record-ftn5zmh2/install-record.txt --single-version-externally-managed --compile --install-headers /home/pi/home-assistant/include/site/python3.6/av" failed with error code 1 in /tmp/pip-install-udfl2b3t/av/
 2019-03-12 08:49:59 ERROR (MainThread) [homeassistant.requirements] Not initializing stream because could not install requirement av==6.1.2
 2019-03-12 08:49:59 ERROR (MainThread) [homeassistant.setup] Setup failed for stream: Could not install all requirements.
 ```
 
 If you see this error you can solve it by running the following commands and restarting Home Assistant (commands do not need to be ran as the `homeassistant` user):
 
-```
+```text
 sudo apt-get install -y python-dev pkg-config libavformat-dev libavcodec-dev libavdevice-dev libavutil-dev libswscale-dev libavresample-dev libavfilter-dev
 ```
diff --git a/source/_components/trafikverket_train.markdown b/source/_components/trafikverket_train.markdown
@@ -92,7 +92,7 @@ Click [here](https://www.trafikverket.se/trafikinformation/tag/?ArrDep=departure
 
 ```yaml
 sensor:
-- platform: trafikverket
+- platform: trafikverket_train
   api_key: !secret trafikverket_api_key
   trains:
   - name: "Train to work"

diff --git a/source/_components/unifi.markdown b/source/_components/unifi.markdown
@@ -44,17 +44,17 @@ unifi:
 
 {% configuration %}
 host:
-  description: Same address as relevant config entry, needed to identify config entry
+  description: Same address as relevant config entry, needed to identify config entry.
   type: string
   required: true
   default: None
 site:
-  description: Same site as relevant config entry, needed to identify config entry
+  description: Same site as relevant config entry, needed to identify config entry.
   type: string
   required: true
   default: None
 block_client:
-  description: Clients that can be blocked from the network
+  description: A list of Clients MAC Addresses that can be blocked from the network.
   type: list
   required: false
   default: None
@@ -111,7 +111,7 @@ If Home Assistant and the UniFi controller are running on separate machines or V
 
 ### Block network access for clients
 
-Allow control of network access to clients configured in `configuration.yaml`
+Allow control of network access to clients configured in the `configuration.yaml` file by adding a list of the MAC addresses. Items in this list will have a Home Assistant switch created, using the Unifi Device name, allowing for blocking and unblocking.
 
 ### Control clients powered by POE
-Original file line number
+Diff line change
@@ Expand Up / @@ -50,7 +50,7 @@ The automation equivalent would be: @@
     ```yaml
     action:
       service: notify.notify
-      data:
+      data_template:
         message: "The sun is {% raw %}{% if is_state('sun.sun', 'above_horizon') %}up{% else %}down{% endif %}{% endraw %}!"
     ```
@@ Expand Down @@