Merge branch 'current' into release-0-59

source/_components/binary_sensor.template.markdown

@@ -158,7 +158,7 @@ binary_sensor:
 This example creates a washing machine "load running" sensor by monitoring an
 energy meter connected to the washer. During the washer's operation, the energy
 meter will fluctuate wildly, hitting zero frequently even before the load is
-finished. By utilizing `off_delay`, we can have this sensor only turn off if
+finished. By utilizing `delay_off`, we can have this sensor only turn off if
 there has been no washer activity for 5 minutes.
 
 {% raw %}

source/_components/ecobee.markdown

@@ -61,3 +61,5 @@ Configuration variables:
   <img src='{{site_root}}/images/screenshots/ecobee-sensor-badges.png' />
   <img src='{{site_root}}/images/screenshots/ecobee-thermostat-card.png' />
 </p>
+
+If for whatever reason you delete and re-create your ecobee app at ecobee.com such that your developer API key changes, you will need to delete your `/conf/ecobee.conf file`. You will also need to update the `api_key:` in the `configuration.yaml` or `secrets.yaml` file.  

source/_components/satel_integra.markdown

@@ -13,7 +13,7 @@ ha_release: 0.54
 ha_iot_class: "Local Push"
 ---
 
-The `satel_integra` component will allow Home Assistant users who own a Satel Integra alarm panel to leverage their alarm system and its sensors to provide Home Assistant with information about their homes. Connectivity between Home Assistant and the alarm  is accomplished through a ETHM extension module that must be installed in the alarm.
+The `satel_integra` component will allow Home Assistant users who own a Satel Integra alarm panel to leverage their alarm system and its sensors to provide Home Assistant with information about their homes. Connectivity between Home Assistant and the alarm  is accomplished through a ETHM extension module that must be installed in the alarm. Compatible with ETHM-1 Plus module with firmware version > 2.00 (version 2.04 confirmed).
 
 There is currently support for the following device types within Home Assistant:
 

source/_cookbook/custom_panel_using_react.markdown

@@ -18,7 +18,7 @@ This is a [React](https://facebook.github.io/react/) implementation of [TodoMVC]
 - It uses the user configuration for the component in the `configuration.yaml` file for rendering.
 - It allows toggling the sidebar.
 
-All you need is available as a [custom panel](https://github.com/home-assistant/example-custom-config/blob/master/panels/react.html). Download the file and save it in `<config dir>/panels/` (you might have to create the directory if it doesn't exist).
+Download the source [here](https://github.com/home-assistant/example-custom-config/blob/master/panels/react.html). Copy the file to `<config dir>/panels/` (you might have to create the directory if it doesn't exist).
 
 Create a entry for the panel in your `configuration.yaml` file to enable it.
 

source/developers/frontend_creating_custom_panels.markdown

@@ -9,13 +9,28 @@ sharing: true
 footer: true
 ---
 
-Any component has the possibility to add a panel to the frontend. Panels will be rendered full screen and have real-time access to the Home Assistant object via JavaScript. Examples of this in the app are map, logbook and history.
+Panels are pages within Home Assistant that show information within Home Assistant and can allow controlling it. Panels are linked from the sidebar and rendered full screen. The have have real-time access to the Home Assistant object via JavaScript. Examples of panels in the app are map, logbook and history.
+
+Besides components registering panels, users can also register panels using the `panel_custom` component. This allows users to quickly build their own custom interfaces for Home Assistant.
+
+### {% linkable_title Before you get started %}
+
+The Home Assistant user interface is currently served to browsers in modern JavaScript and older JavaScript (ES5). The older version has a wider browser support but that comes at a cost of size, performance and more difficult to get started building panels for authors.
+
+We therefore advice to set up the frontend to serve the modern version of the frontend so that you won't need any build tools while developing. If you realize that your audience requires both, you can add a transpilation step in the future. To set up your frontend to always serve the latest version, add this to your config:
+
+```
+frontend:
+  javascript_version: latest
+```
+
+### {% linkable_title Building your first panel %}
 
 Create a file called `hello.html` in your <config dir>/panels/.
 
 The `hello.html` contains the needed building blocks to create the elements inside the view.
 
-```javascript
+```html
 <dom-module id='ha-panel-hello'>
   <template>
     <style>