Merge branch 'current' into next

.github/move.yml

@@ -0,0 +1,13 @@
+# Configuration for move-issues - https://github.com/dessant/move-issues
+
+# Delete the command comment. Ignored when the comment also contains other content
+deleteCommand: true
+# Close the source issue after moving
+closeSourceIssue: true
+# Lock the source issue after moving
+lockSourceIssue: false
+# Set custom aliases for targets
+# aliases:
+#   r: repo
+#   or: owner/repo
+

source/_components/google_assistant.markdown

@@ -30,7 +30,7 @@ google_assistant:
   client_id: [long URL safe random string]
   access_token: [a different long URL safe random string]
   agent_user_id: [a string to identify user]
-  api_key: [an API Key generated for the Google Actions project]
+  api_key: [a Homegraph API Key generated for the Google Actions project]
   exposed_domains:
     - switch
     - light
@@ -41,7 +41,7 @@ google_assistant:
       aliases:
         - bright lights
         - entry lights
-      type: 'action.devices.types.LIGHT'
+      type: light
     light.living_room:
       expose: false
 ```
@@ -102,7 +102,7 @@ entity_config:
           required: false
           type: list
         type:
-          description: Override the type of the entity in Google Assistant. [List of available types](https://developers.google.com/actions/smarthome/guides/)
+          description: Override the domain how Google Assistant has to interpretet the entity. For example, set to `light` for a switch entity to have it be handeld as a light.
           required: false
           type: string
 {% endconfiguration %}
@@ -163,7 +163,7 @@ If you're not using Linux, you can use sites such as [this one](https://www.brow
 	2. Under the gear icon, click `Permissions`
 	3. Click `Add`, type the new user's e-mail address and choose `Project -> Editor` role
 	4. Have the new user go to [developer console](https://console.actions.google.com/) and repeat steps starting from point 7.
-11. If you want to use the `google_assistant.request_sync` service in Home Assistant, then enable Homegraph API for your project:
+11. If you want to use the `google_assistant.request_sync` service, to update devices without unlinking and relinking, in Home Assistant, then enable Homegraph API for your project:
 	1. Go to the [cloud console](https://console.cloud.google.com/apis/api/homegraph.googleapis.com/overview)
 	2. Select your project and click Enable Homegraph API
 	3. Go to Credentials and select API Key from Create Credentials

source/_components/sensor.template.markdown

@@ -27,7 +27,6 @@ sensor:
     sensors:
       solar_angle:
         friendly_name: "Sun angle"
-        entity_id: sun.sun
         unit_of_measurement: 'degrees'
         value_template: "{{ states.sun.sun.attributes.elevation }}"
 

source/_docs/ecosystem/hass-configurator.markdown

@@ -39,14 +39,14 @@ Consider running the configurator as a user with limited privileges to limit pos
 
 ### {% linkable_title Installation (Linux, OS X) %}
 There are no dependencies on Python modules that are not part of the standard library. And all the fancy JavaScript libraries are loaded from CDN (which means this doesn't work when you're offline).  
-- Copy [configurator.py](https://github.com/danielperna84/hass-configurator/blob/master/configurator.py) to your Home Assistant configuration directory (e.g /home/homeassistant/.homeassistant)
+- Copy [configurator.py](https://github.com/danielperna84/hass-configurator/blob/master/configurator.py) to your Home Assistant configuration directory (e.g `/home/homeassistant/.homeassistant`): `wget https://raw.githubusercontent.com/danielperna84/hass-configurator/master/configurator.py`
 - Make it executable: `sudo chmod 755 configurator.py`
 - (Optional) Set the `GIT` variable in configurator.py to `True` if [GitPython](https://gitpython.readthedocs.io/) is installed on your system. This is required if you want to make use of the Git integration.
 - Execute it: `sudo ./configurator.py`
 - To terminate the process do the usual `CTRL+C`, maybe once or twice
 
 ### {% linkable_title Configuration %}
-Near the top of the configurator.py-file you will find some global variables you can change to customize the configurator. If you are unfamiliar with Python: when setting variables of the type _string_, you have to write that within quotation marks. The default settings are fine for just checking out the configurator quickly. With more customized setups you should change some settings though.  
+Near the top of the `configurator.py`-file you will find some global variables you can change to customize the configurator. If you are unfamiliar with Python: when setting variables of the type _string_, you have to write that within quotation marks. The default settings are fine for just checking out the configurator quickly. With more customized setups you should change some settings though.  
 To keep your settings across updates it is also possible to save settings in an external file. In that case copy [settings.conf](https://github.com/danielperna84/hass-configurator/blob/master/settings.conf) wherever you like and append the full path to the file to the command when starting the configurator. E.g. `sudo .configurator.py /home/homeassistant/.homeassistant/mysettings.conf`. This file is in JSON format. So make sure it has a valid syntax (you can set the editor to JSON to get syntax highlighting for the settings). The major difference to the settings in the py-file is, that `None` becomes `null`.
 
 #### LISTENIP (string)

source/_posts/2018-01-14-release-61.markdown

@@ -17,8 +17,13 @@ Almost a 100 contributors to this release 🎉  That's what you get when you ski
 
 This release contain some breaking changes. Please make sure that you check the section below if you are running into trouble.
 
-There is not much more to tell and I don't want to make something up.
+## {% linkable_title Assistant configs %}
 
+We made a mistake in the foundation of both the Google Assistant and Alexa integrations: they were storing their config inside customize. This is not the right place and we moved them to be under the components itself. See the breaking changes section on how to migrate.
+
+## {% linkable_title Hass.io updates %}
+
+Pascal has made it easier to create and restore snapshots for Hass.io by calling the new services. This way it will be easy to automate the creation of a snapshot at night. The updater has also been fixed and will now report on new versions of Hass.io that are available.
 
 ## {% linkable_title New Platforms %}
 

source/developers/maintenance.markdown

@@ -28,6 +28,10 @@ To fix the line separator, use `dos2unix` or `sed`.
 $ dos2unix homeassistant/components/notify/kodi.py
 ```
 
+### {% linkable_title File permissions %}
+
+Most files don't need to the be executable. `0644` is fine.
+
 ### {% linkable_title Dependencies %}
 
 A lot of components and platforms depends on third-party Python modules. The dependencies which are stored in the `requirements_*.txt` files are tracked by [gemnasium](https://gemnasium.com/github.com/home-assistant/home-assistant) and [Requires.io](https://requires.io/github/home-assistant/home-assistant/requirements/?branch=dev).