Merge branch 'current' into next

balloob · balloob · commit cec178bdce47 · 2018-08-20T16:20:34.000+02:00
diff --git a/_config.yml b/_config.yml
@@ -141,14 +141,14 @@ social:
 
 # Home Assistant release details
 current_major_version: 0
-current_minor_version: 75
-current_patch_version: 3
-date_released: 2018-08-09
+current_minor_version: 76
+current_patch_version: 1
+date_released: 2018-08-19
 
 # Either # or the anchor link to latest release notes in the blog post.
 # Must be prefixed with a # and have double quotes around it.
 # Major release:
-patch_version_notes: "#release-0753---august-9"
+patch_version_notes: "#release-0761---august-19"
 # Minor release (Example #release-0431---april-25):
 
 # Date we moved to Discourse for comments
diff --git a/source/_addons/bluetooth_bcm43xx.markdown b/source/_addons/bluetooth_bcm43xx.markdown
@@ -9,13 +9,14 @@ sharing: true
 footer: true
 ---
 
-Start this add-on to activate the BCM43xx Bluetooth chipset.
+Start this add-on to activate the BCM43xx Bluetooth chipset in the old ResinOS based builds. If you first installed Hass.io after mid July 2018 then you will have a HassOS based system.
+
+You can identify the base of your system by looking in the System tab of the Hass.io menu.
 
 <p class='note warning'>
- This is not required on HassOS based Hass.io installs and should not be installed.
+ This is not required on the new HassOS based Hass.io installs and should not be installed.
 </p>
 
 Supported platforms:
 
 - Raspberry Pi 3
-
diff --git a/source/_components/climate.ecobee.markdown b/source/_components/climate.ecobee.markdown
@@ -245,7 +245,9 @@ canceled.
 | Service data attribute | Optional | Description |
 | ---------------------- | -------- | ----------- |
 | `entity_id` | yes | String or list of strings that point at `entity_id`'s of climate devices to control. Else targets all.
-| `hold_mode` | no | 'temp', 'home', 'away', 'sleep', etc., None
+| `hold_mode` | no | `temp`, `home`, `away`, `sleep`, `None`, `smart1`, `smart2`, etc.
+
+NOTE: If you create custom hold modes (also known as "Comfort Settings") on your ecobee.com dashboard, their hold_modes are `smart1`, `smart2`, `smart3`, etc. The number for each custom mode should match the mode's icon on your ecobee.com dashboard. Also note that the mode numbers/icons in the ecobee mobile app *may not match* the numbers/icons from the ecobee.com web dashboard. The ones on the website are the ones you shoud use to determine the correct `smartX` hold_mode IDs.
 
 ### {% linkable_title Service `set_temperature` %}
 
diff --git a/source/_components/dyson.markdown b/source/_components/dyson.markdown
@@ -27,9 +27,9 @@ dyson:
   language: YOUR_DYSON_ACCOUNT_LANGUGAGE
   devices:
     - device_id: DEVICE_ID_1 # eg. Serial number: XXX-XX-XXXXXXXX
-      device_ip: DEVICE_ID_1
+      device_ip: DEVICE_IP_1
     - device_id: DEVICE_ID_2
-      device_ip: DEVICE_ID_2
+      device_ip: DEVICE_IP_2
 ```
 
 Configuration variables:
diff --git a/source/_components/http.markdown b/source/_components/http.markdown
@@ -69,7 +69,7 @@ trusted_proxies:
   required: false
   type: string, list
 use_x_forwarded_for:
-  description: "Enable parsing of the `X-Forwarded-For` header, passing on the client's correct IP address in proxied setups. You **must** also whitelist trusted proxies using the `trusted_proxies` setting below for this to work. Non-whitelisted requests with this header will be considered IP spoofing attacks, and the header will, therefore, be ignored."
+  description: "Enable parsing of the `X-Forwarded-For` header, passing on the client's correct IP address in proxied setups. You **must** also whitelist trusted proxies using the `trusted_proxies` setting above for this to work. Non-whitelisted requests with this header will be considered IP spoofing attacks, and the header will, therefore, be ignored."
   required: false
   type: boolean
   default: false
@@ -87,6 +87,11 @@ login_attempts_threshold:
   required: false
   type: integer
   default: -1
+ssl_profile:
+  description: The [Mozilla SSL profile](https://wiki.mozilla.org/Security/Server_Side_TLS) to use. Only lower if you are experiencing integrations causing SSL handshake errors.
+  required: false
+  type: string
+  default: modern
 {% endconfiguration %}
 
 The sample below shows a configuration entry with possible values:
diff --git a/source/_components/lutron_caseta.markdown b/source/_components/lutron_caseta.markdown
@@ -25,9 +25,9 @@ The currently supported Caseta devices are:
 - Scenes as Home Assistant [scenes](/components/scene.lutron_caseta/)
 - Lutron shades as Home Assistant [covers](/components/cover.lutron_caseta/)
 
-When configured, the `lutron_caseta` component will automatically discover the currently supported devices as setup in the Lutron Smart Bridge. The name assigned in the Lutron mobile app will be used to form the `entity_id` used in Home Assistant. e.g., a dimmer called 'Bedroom Lamp' becomes `light.bedroom_lamp` in Home Assistant.
+When configured, the `lutron_caseta` component will automatically discover the currently supported devices as setup in the Lutron Smart Bridge. The name assigned in the Lutron mobile app will be used to form the `entity_id` used in Home Assistant. e.g., a dimmer called 'Lamp' in a room called 'Bedroom' becomes `light.bedroom_lamp` in Home Assistant.
 
-To use Lutron Caseta devices in your installation, you must first log in to your Lutron account and generate a certificate that allows Home Assistant to connect to your bridge. This can be accomplished by downloading and executing [this script](/assets/get_lutron_cert.zip), which will generate three files: caseta.key, caseta.crt, caseta-bridge.crt when you run it. See the instructions at the top of the script for more information.
+To use Lutron Caseta devices in your installation, you must first log in to your Lutron account and generate a certificate that allows Home Assistant to connect to your bridge. This can be accomplished by downloading and executing [get_lutron_cert.py](https://github.com/gurumitts/pylutron-caseta/blob/master/get_lutron_cert.py), which will generate three files: caseta.key, caseta.crt, caseta-bridge.crt when you run it. See the instructions at the top of the script for more information.
 
 Once you have the three necessary files, place them in your configuration directory and add the following to your `configuration.yaml`:
 
@@ -40,12 +40,24 @@ lutron_caseta:
     ca_certs: caseta-bridge.crt
 ```
 
-Configuration variables:
-
-- **host** (*Required*): The IP address of the Lutron Smart Bridge.
-- **keyfile** (*Required*): The private key that Home Assistant will use to authenticate to the bridge.
-- **certfile** (*Required*): The certificate chain that Home Assistant will use to authenticate to the bridge.
-- **ca_certs** (*Required*): The list of certificate authorities (usually only one) that Home Assistant will expect when connecting to the bridge.
+{% configuration %}
+  host:
+    required: true
+    description: The IP address of the Lutron Smart Bridge.
+    type: string
+  keyfile:
+    required: true
+    description: The private key that Home Assistant will use to authenticate to the bridge.
+    type: string
+  certfile:
+    required: true
+    description: The certificate chain that Home Assistant will use to authenticate to the bridge.
+    type: string
+  ca_certs:
+    required: true
+    description: The list of certificate authorities (usually only one) that Home Assistant will expect when connecting to the bridge.
+    type: string
+{% endconfiguration %}
 
 <p class='note'>
 It is recommended to assign a static IP address to your Lutron Smart Bridge. This ensures that it won't change IP address, so you won't have to change the `host` if it reboots and comes up with a different IP address.
diff --git a/source/_components/media_player.panasonic_viera.markdown b/source/_components/media_player.panasonic_viera.markdown
@@ -29,6 +29,7 @@ Currently known supported models:
 - TX-P42STW50
 - TX-P50GT30Y
 - TX-P50GT60E
+- TH-32ES500
 
 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.github.io/blob/next/source/_components/media_player.panasonic_viera.markdown).
 
diff --git a/source/_components/panel_custom.markdown b/source/_components/panel_custom.markdown
@@ -12,29 +12,34 @@ ha_category: Front end
 ha_release: 0.26
 ---
 
-
-The `panel_custom` support allows you to add additional panels to your Home Assistant frontend. The panels are listed in the sidebar if wished and can be highly customized.
+The `panel_custom` support allows you to add additional panels to your Home Assistant frontend. The panels are listed in the sidebar if wished and can be highly customized. See the developer documentation on [instructions how to build your own panels](https://developers.home-assistant.io/docs/en/frontend_creating_custom_panels.html).
 
 To enable customized panels in your installation, add the following to your `configuration.yaml` file:
 
 ```yaml
-# Example configuration.yaml entry for https://github.com/home-assistant/example-custom-config/blob/master/panels/hello_world.html
+# Example configuration.yaml entry
 panel_custom:
-  - name: todomvc
+  - name: my-panel
     sidebar_title: TodoMVC
     sidebar_icon: mdi:work
     url_path: my-todomvc
-    webcomponent_path: /home/hass/hello.html
+    js_url: /local/my-panel.js
     config:
       who: world
 ```
 
+<p class='note'>
+Store your custom panels in `<config>/www` to make them available in the frontend at the path `/local`.
+</p>
+
 Configuration variables:
 
-- **name** (*Optional*): Name of the panel.
+- **name** (*Required*): Name of the web component that renders your panel.
 - **sidebar_title** (*Optional*): Friendly title for the panel in the sidebar. Omitting it means no sidebar entry (but still accessible through the URL).
 - **sidebar_icon** (*Optional*): Icon for entry. Pick an icon that you can find on [materialdesignicons.com](https://materialdesignicons.com/) to use for your input and prefix the name with `mdi:`. For example `mdi:car`, `mdi:ambulance`, or  `mdi:motorbike`.
-- **url_path** (*Optional*): The URL your panel will be available on. If omitted will default to the panel name.
-- **webcomponent_path** (*Optional*): The  path to your component. If omitted will default to `<config dir>/panels/<component name>.html`
+- **url_path** (*Optional*): The URL your panel will be available on in the frontend. If omitted will default to the panel name.
+- **js_url** (*Required*): The URL that contains the JavaScript of your panel.
 - **config** (*Optional*): Configuration to be passed into your web component when being instantiated.
-
+- **embed_iframe** (*Optional*): Set to `true` to embed panel in iframe. This is necessary if the panel is panel is using the React framework or if it contains conflicting web components.
+- **trust_external_script** (*Optional*): By default the user has to confirm before loading a script from an external source. Setting this to `true` will omit this confirmation.
+- **webcomponent_path** (*Optional* *DEPRECATED*): The HTML path to your component. If omitted will default to `<config dir>/panels/<component name>.html`
diff --git a/source/_components/sensor.mold_indicator.markdown b/source/_components/sensor.mold_indicator.markdown
@@ -27,12 +27,28 @@ sensor:
     calibration_factor: 2.0
 ```
 
-Configuration variables:
-
-- **indoor_temp_sensor** (*Required*): The entity ID of the indoor temperature sensor.
-- **indoor_humidity_sensor** (*Required*): The entity ID of the indoor humidity sensor.
-- **outdoor_temp_sensor** (*Required*): The entity ID of the outdoor temperature sensor.
-- **calibration_factor** (*Required*): Needs to be calibrated to the critical point in the room.
+{% configuration %}
+name:
+  description: The name of the sensor.
+  required: false
+  type: string
+indoor_temp_sensor:
+  description: The entity ID of the indoor temperature sensor.
+  required: true
+  type: string
+indoor_humidity_sensor: 
+  description: The entity ID of the indoor humidity sensor.
+  required: true
+  type: string
+outdoor_temp_sensor:
+  description: The entity ID of the outdoor temperature sensor.
+  required: true
+  type: string
+calibration_factor: 
+  description: Needs to be calibrated to the critical point in the room.
+  required: true
+  type: float
+{% endconfiguration %}
 
 In this case, the weather forecast temperature sensor is used for the outside temperature.
 
diff --git a/source/_components/sensor.worldtidesinfo.markdown b/source/_components/sensor.worldtidesinfo.markdown
@@ -14,6 +14,12 @@ ha_release: 0.52
 
 The `worldtidesinfo` sensor platform uses details from [World Tides](https://www.worldtides.info/) to provide information about the prediction for the tides for any location in the world. 
 
+## {% linkable_title Setup %}
+
+Get your API key from your account at [https://www.worldtides.info/](https://www.worldtides.info/).
+
+## {% linkable_title Configuration %}
+
 To use this sensor, add the following to your `configuration.yaml` file:
 
 ```yaml
@@ -23,10 +29,25 @@ sensor:
     api_key: YOUR_API_KEY
 ```
 
-Configuration variables:
-
-- **api_key** (*Required*): Your API key for https://www.worldtides.info/.
-- **name** (*Optional*): Name to use in the frontend.
-- **latitude** (*Optional*): Latitude of the location to display the tides. Defaults to the latitude in your `configuration.yaml` file. 
-- **longitude** (*Optional*): Longitude of the location to display the tides. Defaults to the longitude in your `configuration.yaml` file.
+{% configuration %}
+api_key:
+  description: Your API key.
+  required: true
+  type: string
+name:
+  description: Name to use in the frontend.
+  required: false
+  type: string
+  default: WorldTidesInfo
+latitude:
+  description: Latitude of the location to display the tides.
+  required: false
+  type: float
+  default: "The latitude in your `configuration.yaml` file."
+longitude:
+  description: Longitude of the location to display the tides.
+  required: false
+  type: float
+  default: "The longitude in your `configuration.yaml` file."
+{% endconfiguration %}
 
diff --git a/source/_docs/configuration/basic.markdown b/source/_docs/configuration/basic.markdown
@@ -20,6 +20,9 @@ homeassistant:
   unit_system: metric
   time_zone: America/Los_Angeles
   name: Home
+  whitelist_external_dirs:
+    - /usr/var/dumping-ground
+    - /tmp
 ```
 
 Configuration variables:
diff --git a/source/_docs/ecosystem/appdaemon.markdown b/source/_docs/ecosystem/appdaemon.markdown
@@ -107,4 +107,4 @@ Of course, if I wanted to make this App or its predecessor reusable, I would hav
 
 In addition, Apps can write to `AppDaemon`'s log files, and there is a system of constraints that allows you to control when and under what circumstances Apps and callbacks are active to keep the logic clean and simple.
 
-For full installation instructions, see the [AppDaemon Project Documentation pages](http://appdaemon.readthedocs.io/en/stable/).
+For full installation instructions, see the [AppDaemon Project Documentation pages](http://appdaemon.readthedocs.io/en/stable/). If you're using Hassbian, then the [Hassbian scripts](https://github.com/home-assistant/hassbian-scripts/blob/dev/docs/appdaemon.md) make it easy to install.
diff --git a/source/_docs/ecosystem/backup/backup_github.markdown b/source/_docs/ecosystem/backup/backup_github.markdown
@@ -42,27 +42,29 @@ $ sudo apt-get update
 $ sudo apt-get install git
 ```
 
-### {% linkable_title Step 2: Creating %} `.gitignore`
+### {% linkable_title Step 2: Creating `.gitignore` %}
 
 <p class='note warning'>
 Before creating and pushing your Home Assistant configuration to GitHub, please make sure to follow the `secrets.yaml` best practice mentioned above and scrub your configuration for any passwords or sensitive information.
 </p>
 
-Creating a `.gitignore` file in your repository will tell git which files NOT to push to the GitHub server. This should be used to prevent publishing sensitive files to the public. It should contain a list of filenames and pattern matches. This list should include at least your `secrets.yaml` file, device configuration files, and the Home Assistant database/directory structure.  The `.gitignore` file should be placed in your Home Assistant directory.
+Creating a `.gitignore` file in your repository will tell git which files NOT to push to the GitHub server. This should be used to prevent publishing sensitive files to the public. It should contain a list of filenames and pattern matches. This list should include at least your `secrets.yaml` file, device configuration files, and the Home Assistant database/directory structure.  The `.gitignore` file should be placed in the root of your Home Assistant configuration directory: `<config dir/.gitignore`.
 
-Here is an example that will include your `.gitignore` file, a `scenes` directory, and all .yaml files except for `secrets.yaml` and `known_devices.yaml`. All other files will be excluded.
-
-`.gitignore`
+Here is an example that will ignore everything but your YAML configuration.
 
 ```bash
+# Example .gitignore file for your config dir
 *
 !*.yaml
-!scenes
 !.gitignore
 secrets.yaml
 known_devices.yaml
 ```
 
+<p class='note'>
+  You might read this guide too late and accidentally already have your secrets published. It is not enough to just remove them with a new commit. Git is a version control system and keeps history. You need to delete your repository and start a new one. Also change all passwords and revoke the API keys that were public.
+</p>
+
 More information on the layout of the file can be found in the [.gitignore manual](https://git-scm.com/docs/gitignore).
 
 ### {% linkable_title Step 3: Preparing your Home Assistant directory for GitHub %}
diff --git a/source/_docs/ecosystem/hadashboard.markdown b/source/_docs/ecosystem/hadashboard.markdown
@@ -37,6 +37,4 @@ HADashboard is a modular, skinnable dashboard for [Home Assistant](/) that is in
     Glassic Theme
 </p>
 
-
-
-For full installation instructions see the HADashboard section in the [AppDaemon Project Documentation](http://appdaemon.readthedocs.io/en/stable/DASHBOARD_INSTALL.html)
+For full installation instructions see the HADashboard section in the [AppDaemon Project Documentation](http://appdaemon.readthedocs.io/en/stable/DASHBOARD_INSTALL.html). If you're using Hassbian, then the [Hassbian scripts](https://github.com/home-assistant/hassbian-scripts/blob/dev/docs/appdaemon.md) make it easy to install AppDaemon.
diff --git a/source/_docs/mqtt/broker.markdown b/source/_docs/mqtt/broker.markdown
@@ -14,25 +14,27 @@ The MQTT component needs you to run an MQTT broker for Home Assistant to connect
 
 ### {% linkable_title Embedded broker %}
 
-Home Assistant contains an embedded MQTT broker. If no broker configuration is given, the [HBMQTT broker](https://pypi.python.org/pypi/hbmqtt) is started and Home Assistant connects to it. Embedded broker default configuration:
+Home Assistant contains an embedded MQTT broker called [HBMQTT](https://pypi.python.org/pypi/hbmqtt). If you don't have an MQTT broker, you can configure this one to be used. If configured, Home Assistant will automatically connect to it.
 
 | Setting        | Value |
 | -------------- | ----- |
 | Host           | localhost |
 | Port           | 1883 |
 | Protocol       | 3.1.1 |
 | User           | homeassistant |
-| Password       | no default value |
+| Password       | _password set under mqtt settings_ |
 | Websocket port | 8080 |
 
-Since release 0.76, the embedded broker does not use your [API password](/components/http/) as the default password. The MQTT component will fail to set up if you have API password configured, but don't have MQTT password configured as in the following example.
-
 ```yaml
 # Example configuration.yaml entry
 mqtt:
-  password: YOUR_MQTT_PASSWORD
+  password: hello
 ```
 
+<p class='note'>
+Before release 0.76, the embedded broker would use your API password as a password to the MQTT user. This is no longer the case.
+</p>
+
 <p class='note warning'>
 There is [an issue](https://github.com/beerfactory/hbmqtt/issues/62) with the HBMQTT broker and the WebSocket connection that is causing a memory leak. If you experience this issue, consider using another broker like Mosquitto.
 </p>
diff --git a/source/_docs/scripts/conditions.markdown b/source/_docs/scripts/conditions.markdown
@@ -163,7 +163,7 @@ The template condition will test if the [given template][template] renders a val
 ```yaml
 condition:
   condition: template
-  value_template: '{% raw %}{{ states.device_tracker.iphone.attributes.battery > 50 }}{% endraw %}'
+  value_template: "{% raw %}{{ state_attr('device_tracker.iphone', 'battery') > 50 }}{% endraw %}"
 ```
 
 Within an automation, template conditions also have access to the `trigger` variable as [described here][automation-templating].
diff --git a/source/_posts/2018-08-17-release-76.markdown b/source/_posts/2018-08-17-release-76.markdown
diff --git a/source/assets/get_lutron_cert.zip b/source/assets/get_lutron_cert.zip
diff --git a/source/images/blog/2018-08-0.76/components.png b/source/images/blog/2018-08-0.76/components.png
diff --git a/source/lovelace/index.markdown b/source/lovelace/index.markdown

Original file line number	Diff line number	Diff line change
`@@ -107,4 +107,4 @@ Of course, if I wanted to make this App or its predecessor reusable, I would hav`
`107`	`107`
`108`	`108`	In addition, Apps can write to `AppDaemon`'s log files, and there is a system of constraints that allows you to control when and under what circumstances Apps and callbacks are active to keep the logic clean and simple.
`109`	`109`
`110`		`-For full installation instructions, see the [AppDaemon Project Documentation pages](http://appdaemon.readthedocs.io/en/stable/).`
	`110`	`+For full installation instructions, see the [AppDaemon Project Documentation pages](http://appdaemon.readthedocs.io/en/stable/). If you're using Hassbian, then the [Hassbian scripts](https://github.com/home-assistant/hassbian-scripts/blob/dev/docs/appdaemon.md) make it easy to install.`