Merge branch 'current' into next

fabaff · fabaff · commit 00e221b4d1f3 · 2017-10-22T00:57:29.000+02:00
diff --git a/_config.yml b/_config.yml
@@ -139,12 +139,12 @@ social:
 
 # Home Assistant release details
 current_major_version: 0
-current_minor_version: 55
-current_patch_version: 1
-date_released: 2017-10-15
+current_minor_version: 56
+current_patch_version: 0
+date_released: 2017-10-21
 
 # 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-0551---october-15"
+#patch_version_notes: "#release-0551---october-15"
 # Minor release (Example #release-0431---april-25):
diff --git a/source/_components/switch.telnet.markdown b/source/_components/switch.telnet.markdown
@@ -40,5 +40,5 @@ Configuration variables:
     - **command_on** (*Required*): Command to turn device on.
     - **command_off** (*Required*): Command to turn device off.
     - **command_state** (*Required*): Command to determine the state of the switch. If not defined the switch will assume successful state changes.
-    - **value_template** (*Required*): The template evaluating to `true` will indicate the switch is on.
+    - **value_template** (*Required*): The template evaluating to `true` will indicate that the switch is on.
     - **name** (*Optional*): The name used to display the switch in the frontend.
diff --git a/source/_docs/autostart/init.d.markdown b/source/_docs/autostart/init.d.markdown
@@ -26,19 +26,23 @@ $ sudo chmod +x /etc/init.d/hass-daemon
 
 Create or pick a user that the Home Assistant daemon will run under. Update script to set `RUN_AS` to the username that should be used to execute hass.
 
-### {% linkable_title 3. Register the daemon with Linux %}
+### {% linkable_title 3. Change hass executable if required. %}
+
+Some installation environments may require a change in the Home Assistant executable `hass`. Update script to set `HASS_BIN` to the appropriate `hass` executable path.
+
+### {% linkable_title 4. Register the daemon with Linux %}
 
 ```bash
 $ sudo update-rc.d hass-daemon defaults
 ```
 
-### {% linkable_title 4. Install this service %}
+### {% linkable_title 5. Install this service %}
 
 ```bash
 $ sudo service hass-daemon install
 ```
 
-### {% linkable_title 5. Restart Machine %}
+### {% linkable_title 6. Restart Machine %}
 
 That's it. Restart your machine and Home Assistant should start automatically.
 
@@ -64,6 +68,8 @@ If any commands need to run before executing hass (like loading a virtual enviro
 # /etc/init.d Service Script for Home Assistant
 # Created with: https://gist.github.com/naholyr/4275302#file-new-service-sh
 PRE_EXEC=""
+# Typically /usr/bin/hass
+HASS_BIN="hass"
 RUN_AS="USER"
 PID_FILE="/var/run/hass.pid"
 CONFIG_DIR="/var/opt/homeassistant"
@@ -76,7 +82,7 @@ start() {
     return 1
   fi
   echo 'Starting service…' >&2
-  local CMD="$PRE_EXEC hass $FLAGS $REDIRECT;"
+  local CMD="$PRE_EXEC $HASS_BIN $FLAGS $REDIRECT;"
   su -c "$CMD" $RUN_AS
   echo 'Service started' >&2
 }
diff --git a/source/_docs/configuration/secrets.markdown b/source/_docs/configuration/secrets.markdown
@@ -23,7 +23,7 @@ http:
   api_password: YOUR_PASSWORD
 ```
 
-Those entries need to be replaced with `!secret` and a identifier.
+Those entries need to be replaced with `!secret` and an identifier.
 
 ```yaml
 http:
diff --git a/source/_docs/z-wave/installation.markdown b/source/_docs/z-wave/installation.markdown
@@ -18,6 +18,12 @@ There is one dependency you will need to have installed ahead of time (included
 $ sudo apt-get install libudev-dev
 ```
 
+When installing on macOS you may have to also run the command below ahead of time, replace "x.x" with the version of Python (`$ python3 --version`) you have installed. 
+
+```bash
+$ sudo /Applications/Python\ x.x/Install\ Certificates.command
+```
+
 <p class='note'>
 The installation of python-openzwave can take half an hour or more on a Raspbery Pi.
 </p>
diff --git a/source/_posts/2017-10-21-release-56.markdown b/source/_posts/2017-10-21-release-56.markdown
diff --git a/source/developers/credits.markdown b/source/developers/credits.markdown
diff --git a/source/developers/development_submitting.markdown b/source/developers/development_submitting.markdown
@@ -24,7 +24,10 @@ Submit your improvements, fixes, and new features to Home Assistant one at a tim
     `git add .`
     
     `git commit -m "Added some-feature"`
-    
+
+     * Write a meaningful commit message and not only `Update` or `Fix`.
+     * Use a capital letter to start with your commit message.
+     * Don't prefix your commit message with `[bla.bla]` or `platform:`.
      * Consider adding tests to ensure that your code works.
    
  5. Push your committed changes back to your fork on GitHub:
diff --git a/source/developers/frontend_creating_custom_panels.markdown b/source/developers/frontend_creating_custom_panels.markdown
@@ -28,38 +28,38 @@ The `hello.html` contains the needed building blocks to create the elements insi
 </dom-module>
 
 <script>
-Polymer({
-  is: 'ha-panel-hello',
-  properties: {
-    // Home Assistant object
-    hass: {
-      type: Object,
-    },
-    // If should render in narrow mode
-    narrow: {
-      type: Boolean,
-      value: false,
-    },
-    // If sidebar is currently shown
-    showMenu: {
-      type: Boolean,
-      value: false,
-    },
-    // Home Assistant panel info
-    // panel.config contains config passed to register_panel serverside
-    panel: {
-      type: Object,
-    },
-    who: {
-      type: String,
-      computed: 'computeWho(panel)',
-    }
-  },
+class HaPanelHello extends Polymer.Element {
+  static get is() { return 'ha-panel-hello'; }
+  
+  static get properties() {
+    return {
+      // Home Assistant object
+      hass: Object,
+      // If should render in narrow mode
+      narrow: {
+        type: Boolean,
+        value: false,
+      },
+      // If sidebar is currently shown
+      showMenu: {
+        type: Boolean,
+        value: false,
+      },
+      // Home Assistant panel info
+      // panel.config contains config passed to register_panel serverside
+      panel: Object,
+      who: {
+        type: String,
+        computed: 'computeWho(panel)',
+      },
+    };
+  }
 
-  computeWho: function (panel) {
+  computeWho(panel) {
     return panel && panel.config && panel.config.who ? panel.config.who : 'World';
-  },
-});
+  }
+}
+customElements.define(HaPanelHello.is, HaPanelHello);
 </script>
 ```
 
diff --git a/source/developers/frontend_creating_custom_ui.markdown b/source/developers/frontend_creating_custom_ui.markdown
@@ -9,6 +9,7 @@ sharing: true
 footer: true
 ha_release: 0.38
 ---
+
 If you would like to use your own [State card](/developers/frontend_add_card/) without merging your code into [home-assistant-polymer](https://github.com/home-assistant/home-assistant-polymer/) you can create your own implementation.
 
 Put the element source file and its dependencies in `www/custom_ui/` directory under your Home Assistant [configuration](/docs/configuration/) directory.
@@ -21,10 +22,13 @@ In `state-card-my-custom-light.html` you should use `<link rel="import">` to imp
 Do not import any dependencies used by the Home Assistant UI.
 Importing those will work in `development: 1` mode, but will fail in production mode.
 
-1) In the `customize:` section of the `configuration.yaml` file put `custom_ui_state_card: state-card-my-custom-light`.
-2) In the `frontend` section use `extra_html_url` to specify the URL to load.
+1. In the `customize:` section of the `configuration.yaml` file put `custom_ui_state_card: state-card-my-custom-light`.
+2. In the `frontend` section use `extra_html_url` to specify the URL to load.
+
+Example:
+
+`configuration.yaml`:
 
-For example:
 ```yaml
 homeassistant:
   customize:
@@ -36,4 +40,42 @@ frontend:
     - /local/custom_ui/state-card-my-custom-light.html
 ```
 
+`www\custom_ui\state-card-my-custom-light.html`:
+
+```javascript
+<dom-module id='state-card-my-custom-light'>
+  <template>
+    <style>
+
+    </style>
+    <textarea>[[_toStr(StateObj)]]</textarea>
+  </template>
+</dom-module>
+
+<script>
+class StateCardMyCustomLight extends Polymer.Element {
+  static get is() { return 'state-card-my-custom-light'; }
+  
+  static get properties() {
+    return {
+      // Home Assistant object
+      hass: Object,
+      // inDialog is true if shown as more-info-card
+      inDialog: {
+        type: Boolean,
+        value: false,
+      },
+      // includes state, config and more information of the entity
+      stateObj: Object,
+    };
+  }
+
+  _toStr(obj) {
+    return JSON.stringify(obj);
+  }
+}
+customElements.define(StateCardMyCustomLight.is, StateCardMyCustomLight);
+</script>
+```
+
 For more possibilities, see the [Custom UI section](/cookbook/#user-interface) on our Examples page.
diff --git a/source/hassio/run_local.markdown b/source/hassio/run_local.markdown
@@ -11,11 +11,13 @@ footer: true
 
 Hass.io is a managed environment, which means that you can't install applications that can be embedded into Home Assistant using the `command_line` sensor/switch.
 
-There are two options if you need to run a script to read data from a sensor or send commands to other devices on Hass.io.
+There are three options if you need to run a script to read data from a sensor or send commands to other devices on Hass.io.
 
 The first option is to write a custom component for Home Assistant. Using Python, you can communicate with your device. For more information about developing a custom component, take a  look at the [developer documentation][custom-component].
 
-The second option is to make a local add-on for Hass.io that sends the data to Home Assistant via MQTT. Before we dive into this, read up on [Hass.io add-on development][addons-tutorial] first.
+The second option is to use STDIN inside add-on and use the service `hassio.addon_stdin` to send data. More about this options look into [developer documentation][communication] for internal add-on communication. There is also describe how do you can easy access to Home-Assistant Rest API.
+
+The third option is to make a local add-on for Hass.io that sends the data to Home Assistant via MQTT. Before we dive into this, read up on [Hass.io add-on development][addons-tutorial] first.
 
 For security and speed, Hass.io does not provide a way for containers to communicate directly. So the first step is to set up a communication channel. We're going to use MQTT for this using the [MQTT broker add-on][mqtt-addon].
 
@@ -98,3 +100,4 @@ done < <(mosquitto_sub -h "$MQTT_SERVER" -p "$MQTT_PORT" -u "$USER" -P "$PASSWOR
 [MQTT-addon]: /addons/mosquitto/
 [custom-component]: /developers/component_loading/
 [addons-tutorial]: /developers/hassio/addon_tutorial/
+[communication]: /developers/hassio/addon_communication/
diff --git a/source/images/blog/2017-10-0.56/components.png b/source/images/blog/2017-10-0.56/components.png
