Merge branch 'current' into next

source/_components/deconz.markdown

@@ -17,24 +17,19 @@ ha_iot_class: "Local Push"
 
 [deCONZ REST API](http://dresden-elektronik.github.io/deconz-rest-doc/).
 
-### {% linkable_title Supported device types %}
+### {% linkable_title Recommended way of running deCONZ %}
 
-- [Zigbee Lights](/components/light.deconz/)
-- [Consumption Sensors](/components/sensor.deconz/)
-- [Humidity Sensors](/components/sensor.deconz/)
-- [Light Level Sensors](/components/sensor.deconz/)
-- [OpenClose Detectors](/components/binary_sensor.deconz/)
-- [Power Sensors](/components/sensor.deconz/)
-- [Presence Detectors](/components/binary_sensor.deconz/)
-- [Pressure Sensors](/components/sensor.deconz/)
-- [Switches (Remote Controls)](/components/sensor.deconz/)
-- [Temperature Sensors](/components/sensor.deconz/)
+Use [community container](https://hub.docker.com/r/marthoc/deconz/) by Marthoc for your deCONZ needs. It works both as a standalone container as well as with HASS.io.
+
+### {% linkable_title Supported devices %}
+
+See [deCONZ wiki](https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Supported-Devices) for a list of supported devices.
 
 ## {% linkable_title Configuration %}
 
 Home Assistant will automatically discover deCONZ presence on your network, if `discovery:` is present in your `configuration.yaml` file.
 
-If you don't have the API key, you can generate an API key for deCONZ by using the one-click functionality similar to Philips Hue. Go to **Menu** -> **Settings** -> **Unlock Gateway** in deCONZ and then use the deCONZ configurator in Home Assistant frontend to create an API key. When you've generated the API key from Home Assistant, the API key will be stored in `.config_entries.json` inside the `.homeassistant` folder.
+If you don't have the API key, you can generate an API key for deCONZ by using the one-click functionality similar to Philips Hue. Go to **Menu** -> **Settings** -> **Unlock Gateway** in deCONZ and then use the deCONZ configurator in Home Assistant frontend to create an API key. When you're done setting up deCONZ it will be stored as a config entry.
 
 You can add the following to your configuration.yaml file if you are not using the `discovery:` component:
 
@@ -125,6 +120,8 @@ For the IKEA Tradfri remote, 1 is the middle button, 2 is up, 3 is down, 4 is le
 
 ### {% linkable_title Step up and step down input number with wireless dimmer %}
 
+#### YAML
+
 {% raw %}
 ```yaml
 automation:
@@ -173,3 +170,37 @@ automation:
             {{ [bri-30, 0] | max }}
 ```
 {% endraw %}
+
+#### Appdaemon
+
+{% raw %}
+```yaml
+remote_control_living_room:
+  module: remote_control
+  class: RemoteControl
+  event: deconz_event
+  id: dimmer_switch_3
+```
+
+```python
+import appdaemon.plugins.hass.hassapi as hass
+
+class RemoteControl(hass.Hass):
+
+    def initialize(self):
+        if 'event' in self.args:
+            self.listen_event(self.handle_event, self.args['event'])
+
+    def handle_event(self, event_name, data, kwargs):
+        if data['id'] == self.args['id']:
+            self.log(data['event'])
+            if data['event'] == 1002:
+                self.log('Button on')
+            elif data['event'] == 2002:
+                self.log('Button dim up')
+            elif data['event'] == 3002:
+                self.log('Button dim down')
+            elif data['event'] == 4002:
+                self.log('Button off')
+```
+{% endraw %}

source/_components/hue.markdown

@@ -20,7 +20,7 @@ Once discovered, if you have a custom default view, locate `configurator.philips
 
 When you configure the Hue bridge from Home Assistant, it writes a token to a file in your Home Assistant [configuration directory](/docs/configuration/). That token authenticates the communication with the Hue bridge. This token uses the Address of the Hue Bridge. If the IP address for the Hue Bridge changes, you will need to register the Hue Bridge with Home Assistant again. To avoid this you may set up DHCP registration for your Hue Bridge, so that it always has the same IP address.
 
-Once registration is complete you should see the Hue lights listed as "light" entities; if you don't you may have to restart Home Assistant once more. Add these light entities to configuration.yaml and restart Home Assistant once more to complete the installation.
+Once registration is complete you should see the Hue lights listed as `light` entities. If you don't you may have to restart Home Assistant once more. Add these light entities to `configuration.yaml` file and restart Home Assistant once more to complete the installation.
 
 If you want to enable the component without relying on the [discovery component](/components/discovery/), add the following lines to your `configuration.yaml` file:
 
@@ -33,11 +33,13 @@ hue:
 
 Configuration variables:
 
-- **host**: IP address of the device, eg. 192.168.1.10. Required if not using the `discovery` component to discover Hue bridges.
+- **host** (*Required*): The IP address of the device, eg. 192.168.1.10. Required if not using the `discovery` component to discover Hue bridges.
 - **allow_unreachable** (*Optional*): (true/false)  This will allow unreachable bulbs to report their state correctly.
 - **filename** (*Optional*): Make this unique if specifying multiple Hue hubs.
 - **allow_hue_groups** (*Optional*): (true/false) Enable this to stop Home Assistant from importing the groups defined on the Hue bridge.
 
+## {% linkable_title Examples %}
+
 ```yaml
 # Example configuration.yaml entry specifying optional parameters
 hue:
@@ -49,7 +51,7 @@ hue:
 
 ### {% linkable_title Migrating from older configuration %}
 
-In previous versions of the Hue component the configuration looked different:
+In previous versions of the `hue` component the configuration looked different:
 
 ```yaml
 # Example configuration.yaml entry

source/_components/light.yeelight.markdown

@@ -59,6 +59,7 @@ This component is tested to work with the following models. If you have a differ
 - **YLDP01YL**: LED Bulb (White)
 - **YLDP02YL**: LED Bulb (Color)
 - **YLDP03YL**: LED Bulb (Color) - E26
+- **YLDP06YL**: LED Bulb (Color) II
 - **YLDD01YL**: Lightstrip (Color)
 - **YLDD02YL**: Lightstrip (Color)
 - **MJCTD01YL**: Xiaomi Mijia Bedside Lamp - WIFI Version!

source/_components/media_player.markdown

@@ -32,7 +32,7 @@ Available services: `turn_on`, `turn_off`, `toggle`, `volume_up`, `volume_down`,
 | Service data attribute | Optional | Description                                      |
 |------------------------|----------|--------------------------------------------------|
 | `entity_id`            |      yes | Target a specific media player. Defaults to all. |
-| `volume_level`         |       no | Float for volume level                           |
+| `volume_level`         |       no | Float for volume level. Range 0..1               |
 
 #### {% linkable_title Service `media_player.media_seek` %}
 

source/_components/recorder.markdown

@@ -26,51 +26,51 @@ recorder:
 ```
 
 {% configuration %}
-  recorder:
-    description: Enables the recorder component. Only allowed once.
-    required: true
-    type: map
-    keys:
-      db_url:
-        description: The URL which points to your database.
-        required: false
-        type: URL
-      purge_keep_days:
-        description: Specify the number of history days to keep in recorder database after a purge.
-        required: false
-        default: 10
-        type: int
-      purge_interval:
-        description: How often (in days) the purge task runs. If a scheduled purge is missed (e.g., if Home Assistant was not running), the schedule will resume soon after Home Assistant restarts. You can use the [service](#service-purge) call `purge` when required without impacting the purge schedule. If this is set to `0` (zero), automatic purging is disabled.
-        required: false
-        default: 1
-        type: int
-      exclude:
-        description: Configure which components should be excluded
-        required: false
-        type: map
-        keys:
-          domains:
-            description: The list of domains to be excluded from recordings.
-            required: false
-            type: List
-          entities:
-            description: The list of entity ids to be excluded from recordings.
-            required: false
-            type: List
-      include:
-        description: Configure which components should be included in recordings. If set, all other entities will not be recorded.
-        required: false
-        type: map
-        keys:
-          domains:
-            description: The list of domains to be included in the recordings.
-            required: false
-            type: List
-          entities:
-            description: The list of entity ids to be included in the recordings.
-            required: false
-            type: List
+recorder:
+  description: Enables the recorder component. Only allowed once.
+  required: true
+  type: map
+  keys:
+    db_url:
+      description: The URL which points to your database.
+      required: false
+      type: URL
+    purge_keep_days:
+      description: Specify the number of history days to keep in recorder database after a purge.
+      required: false
+      default: 10
+      type: int
+    purge_interval:
+      description: How often (in days) the purge task runs. If a scheduled purge is missed (e.g., if Home Assistant was not running), the schedule will resume soon after Home Assistant restarts. You can use the [service](#service-purge) call `purge` when required without impacting the purge schedule. If this is set to `0` (zero), automatic purging is disabled.
+      required: false
+      default: 1
+      type: int
+    exclude:
+      description: Configure which components should be excluded
+      required: false
+      type: map
+      keys:
+        domains:
+          description: The list of domains to be excluded from recordings.
+          required: false
+          type: List
+        entities:
+          description: The list of entity ids to be excluded from recordings.
+          required: false
+          type: List
+    include:
+      description: Configure which components should be included in recordings. If set, all other entities will not be recorded.
+      required: false
+      type: map
+      keys:
+        domains:
+          description: The list of domains to be included in the recordings.
+          required: false
+          type: List
+        entities:
+          description: The list of entity ids to be included in the recordings.
+          required: false
+          type: List
 {% endconfiguration %}
 
 Define domains and entities to `exclude` (aka. blacklist). This is convenient when you are basically happy with the information recorded, but just want to remove some entities or domains. Usually these are entities/domains which do not change (like `weblink`) or rarely change (`updater` or `automation`).
@@ -79,7 +79,7 @@ Define domains and entities to `exclude` (aka. blacklist). This is convenient wh
 # Example configuration.yaml entry with exclude
 recorder:
   purge_keep_days: 5
-  db_url: sqlite:///home/user/.homeassistant/test
+  db_url: sqlite:////home/user/.homeassistant/test
   exclude:
     domains:
       - automation
@@ -145,7 +145,7 @@ If the `recorder` component is activated then some components support `restore_s
 
 | Database engine | `db_url`                                                 | 
 | :---------------|:---------------------------------------------------------|
-| SQLite          | `sqlite:///PATH/TO/DB_NAME`                              |
+| SQLite          | `sqlite:////PATH/TO/DB_NAME`                             |
 | MariaDB         | `mysql://SERVER_IP/DB_NAME?charset=utf8`                 |
 | MariaDB         | `mysql://user:password@SERVER_IP/DB_NAME?charset=utf8`   |
 | MySQL           | `mysql://SERVER_IP/DB_NAME?charset=utf8`                 |

source/_components/sensor.dsmr.markdown

@@ -15,8 +15,9 @@ ha_iot_class: "Local Push"
 
 A sensor platform for Dutch Smart Meters which comply to DSMR (Dutch Smart Meter Requirements), also known as 'Slimme meter' or 'P1 poort'.
 
-- Currently support DSMR V2.2 and V4 through the [dsmr_parser](https://github.com/ndokter/dsmr_parser) module by Nigel Dokter.
-- For official information about DSMR refer to: [DSMR Document](http://www.netbeheernederland.nl/themas/hotspot/hotspot-documenten/?dossierid=11010056&title=Slimme%20meter&onderdeel=Documenten)
+- Currently support DSMR V2.2, V3, V4 and V5 through the [dsmr_parser](https://github.com/ndokter/dsmr_parser) module by Nigel Dokter.
+- For official information about DSMR refer to: [DSMR Document](https://www.netbeheernederland.nl/dossiers/slimme-meter-15)
+- For official information about the P1 port refer to: https://www.wijhebbenzon.nl/media/kunena/attachments/3055/DSMRv5.0FinalP1.pdf
 - For unofficial hardware connection examples refer to: [Domoticx](http://domoticx.com/p1-poort-slimme-meter-hardware/)
 
 <p class='img'>
@@ -26,6 +27,7 @@ A sensor platform for Dutch Smart Meters which comply to DSMR (Dutch Smart Meter
 This component is known to work for:
 
 - Iskra ME382 / MT382 (DSMR 2.2)
+- ISKRA AM550 (DSMR 5.0)
 - Landis+Gyr E350 (DMSR 4)
 - Landis+Gyr ZCF110 / ZM F110 (DSMR 4.2)
 - Kaifa E0026
@@ -36,6 +38,7 @@ USB serial converters:
 - Cheap (Banggood/ebay) Generic PL2303
 - https://sites.google.com/site/nta8130p1smartmeter/webshop
 - https://www.sossolutions.nl/slimme-meter-kabel
+- https://tweakers.net/gallery/269738/aanbod/
 
 Serial to network proxies:
 
@@ -57,7 +60,7 @@ sensor:
     required: false
     type: string
   name:
-    description: "Version of DSMR used by meter. Choices: 2.2, 4, 5. Defaults to 2.2."
+    description: "Version of DSMR used by meter. Choices: 2.2, 3, 4, 5. Defaults to 2.2."
     required: false
     type: string
 {% endconfiguration %}
@@ -69,7 +72,7 @@ Full configuration examples can be found below:
 sensor:
   - platform: dsmr
     port: /dev/ttyUSB1
-    dsmr_version: 4
+    dsmr_version: 5
 
 group:
   meter_readings:
@@ -88,7 +91,7 @@ sensor:
   - platform: dsmr
     host: 192.168.1.13
     port: 2001
-    dsmr_version: 4
+    dsmr_version: 5
 
 group:
   meter_readings:
@@ -127,7 +130,7 @@ $ sudo reboot
 
 ### {% linkable_title Technical overview %}
 
-DSMR is a standard to which Dutch smartmeters must comply. It specifies that the smartmeter must send out a 'telegram' every 10 seconds over a serial port.
+DSMR is a standard to which Dutch smartmeters must comply. It specifies that the smartmeter must send out a 'telegram' every 10 seconds (every second for DSMR 5.0 devices) over a serial port.
 
 The contents of this telegram differ between version but they generally consist of lines with 'obis' (Object Identification System, a numerical ID for a value) followed with the value and unit.
 

source/_components/sensor.postnl.markdown

@@ -20,7 +20,7 @@ The `postnl` platform allows one to track deliveries by [PostNL](https://www.pos
 To enable this sensor, add the following lines to your `configuration.yaml`:
 
 ```yaml
-sensors:
+sensor:
   - platform: postnl
     username: POSTNL_USERNAME
     password: POSTNL_PASSWORD

source/_components/sensor.whois.markdown

@@ -14,14 +14,17 @@ ha_iot_class: "Cloud Polling"
 ---
 
 
-`whois` sensor allows you to perform daily WHOIS lookups against your owned domains. This provides you with information such as `expiration_date`, `name_servers`, and `registrar` details.
+The `whois` sensor platform allows you to perform daily WHOIS lookups against your owned domains. This provides you with information such as `expiration_date`, `name_servers` and `registrar` details.
+
+## {% linkable_title Configuration %}
+
+To use this sensor in your installation, add the following to your `configuration.yaml` file:
 
 ```yaml
 # Example configuration.yaml entry
 sensor:
   - platform: whois
     domain: example.net
-    name: primary
 ```
 
 {% configuration %}

source/_components/snips.markdown

@@ -105,6 +105,22 @@ By default, Snips runs its own MQTT broker. But we can also tell Snips to use an
 
 ## {% linkable_title Home Assistant configuration %}
 
+{% configuration %}
+feedback_sounds:
+  description: Turn on feedbacks sounds for Snips
+  required: false
+  type: str
+  default: false
+site_ids:
+  description: A list of siteIds if using multiple Snips instances. Used to make sure feedback is toggled on or off for all sites
+  required: false
+  type: str
+probability_threshhold:
+  description: Threshhold for intent probability. Intents under this level are discarded
+  require: false
+  type: int
+{% endconfiguration %}
+
 ### {% linkable_title Specifying the MQTT broker %}
 
 Messages between Snips and Home Assistant are passed via MQTT. We can either point Snips to the MQTT broker used by Home Assistant, as explained above, or tell Home Assistant which [MQTT broker](/docs/mqtt/) to use by adding the following entry to the `configuration.yaml` file:
@@ -147,7 +163,9 @@ In the `data_template` block, we have access to special variables, corresponding
 
 ### {% linkable_title Special slots %}
 
-In the above example, the slots are plain strings. However, when more complex types are used, such as dates or time ranges, they will be transformed to rich Python objects, for example:
+Two special values for slots are populated with the siteId the intent originated from and the probability value for the intent.
+
+In the above example, the slots are plain strings. However, snips has a duration builtin value used for setting timers and this will be parsed to a seconds value.
 
 {% raw %}
 ```yaml
@@ -160,12 +178,13 @@ SetTimer:
     data_template:
       name: "{{ timer_name }}"
       duration: "{{ timer_duration }}"
-      seconds: "{{ slots.timer_duration.value.seconds }}"
-      minutes: "{{ slots.timer_duration.value.minutes }}"
-      hours: "{{ slots.timer_duration.value.hours }}"
+      siteId: "{{ site_id }}"
+      probability: "{{ probability }}"
 ```
 {% endraw %}
 
+
+
 ### {% linkable_title Sending TTS Notifications %}
 
 You can send TTS notifications to Snips using the snips.say and snips.say_action services. Say_action starts a session and waits for user response, "Would you like me to close the garage door?", "Yes, close the garage door".
@@ -202,7 +221,7 @@ intent_script:
   turn_on_light:
     speech:
       type: plain
-      text: 'OK, closing the garage door'
+      text: 'OK, turning on the light'
     action:
       service: light.turn_on
 ```
@@ -256,7 +275,7 @@ intent_script:
 
 ##### {% linkable_title Weather %}
 
-So now you can open and close your garage door, let's check the weather. Add the Weather by Snips Skill to your assistant. Create a weather sensor, in this example (Dark Sky)[/components/sensor.darksky/] and the `api_key` in the `secrets.yaml` file.
+So now you can open and close your garage door, let's check the weather. Add the Weather by Snips Skill to your assistant. Create a weather sensor, in this example [Dark Sk](/components/sensor.darksky/) and the `api_key` in the `secrets.yaml` file.
 
 ```yaml
 - platform: darksky
@@ -272,7 +291,7 @@ So now you can open and close your garage door, let's check the weather. Add the
     - temperature_min
 ```
 
-Then create this `intent_script.yaml` file in your configuration directory.
+Then add this to your configuration file.
 
 {% raw %}
 ```yaml

source/_docs/configuration/platform_options.markdown

@@ -19,17 +19,17 @@ By setting an entity namespace, all entities will be prefixed with that namespac
 ```yaml
 # Example configuration.yaml entry
 light:
-  platform: hue
-  entity_namespace: holiday_house
+  - platform: your_lights
+    entity_namespace: holiday_house
 ```
 
 ### {% linkable_title Scan Interval %}
 
-Platforms that require polling will be polled in an interval specified by the main component. For example a light will check every 30 seconds for a changed state. It is possible to overwrite this scan interval for any platform that is being polled by specifying a `scan_interval` configuration key. In the example below we setup the Philips Hue lights but tell Home Assistant to poll the devices every 10 seconds instead of the default 30 seconds.
+Platforms that require polling will be polled in an interval specified by the main component. For example a light will check every 30 seconds for a changed state. It is possible to overwrite this scan interval for any platform that is being polled by specifying a `scan_interval` configuration key. In the example below we set up the `your_lights` platform but tell Home Assistant to poll the devices every 10 seconds instead of the default 30 seconds.
 
 ```yaml
-# Example configuration.yaml entry to poll Hue lights every 10 seconds.
+# Example configuration.yaml entry to poll your_lights every 10 seconds.
 light:
-  platform: hue
-  scan_interval: 10
+  - platform: your_lights
+    scan_interval: 10
 ```

source/_docs/z-wave/controllers.markdown

@@ -17,7 +17,7 @@ You need to have a [supported Z-Wave USB stick or module](https://github.com/Ope
 |-------------------------|----------------|------------------|--------------|
 | Aeotec Z-Stick          |   ✓     |                  |              |
 | Aeotec Z-Stick Series 2 |   ✓     |                  |              |
-| Aeotec Z-Stick Series 5 |   ✓     |                  |   ✓   |
+| Aeotec Z-Stick Series 5 |   ✓     |    ✓      |   ✓   |
 | Pine64 Z-Wave Module    |   ✓     |                  |              |
 | Razberry GPIO Module    |   ✓     |                  |              |
 | Seluxit ViaSens 100     |                |                  |              |

source/_posts/2018-05-11-release-69.markdown

@@ -1,8 +1,8 @@
 ---
 layout: post
-title: "0.69: TBD - Update date"
-description: "TBD."
-date: 2018-05-05 00:01:00
+title: "0.69: Matrix Chatbot, PostNL, Social Blade, Xiaomi Mijia sensors"
+description: "Great release mainly focused on bug fixes."
+date: 2018-05-11 00:01:00
 date_formatted: "May 11, 2018"
 author: Paulus Schoutsen
 author_twitter: balloob
@@ -13,12 +13,12 @@ og_image: /images/blog/2018-05-0.69/components.png
 
 <a href='/components/#version/0.69'><img src='/images/blog/2018-05-0.69/components.png' style='border: 0;box-shadow: none;'></a>
 
+Not much time to write a great into this time as we're hanging out at PyCon! Some fixes for the Hue and Wink colors thanks to [@amelchio]. Initial foundation for users has landed, it's not anywhere near usable. We'll keep hacking on it. Google Assistant for Home Assistant Cloud now supports room hints. This will cause Google Assistant put the devices in the right groups when you link your account.
+
 ## {% linkable_title New Platforms %}
 
-- New sensor domain expiry ([@masarliev] - [#14067]) ([sensor.domain_expiry docs]) (new-platform)
 - Support Xiaomi Mijia Bluetooth Wireless Temperature and Humidity Sensor ([@ratcashdev] - [#13955]) ([sensor.mitemp_bt docs]) (new-platform)
 - Move RainMachine to component/hub model ([@bachya] - [#14085]) ([rainmachine docs]) ([switch.rainmachine docs]) (breaking change) (new-platform)
-- Foundation for users ([@balloob] - [#13968]) ([auth docs]) ([http docs]) (new-platform)
 - Add Social Blade Sensor ([@meauxt] - [#14060]) ([sensor.socialblade docs]) ([sensor.uscis docs]) (new-platform)
 - Add PostNL sensor (Dutch Postal Services) ([@iMicknl] - [#12366]) ([sensor.postnl docs]) (new-platform)
 - Issue/add template fans ([@giangvo] - [#12027]) ([fan.template docs]) (new-platform)
@@ -35,17 +35,24 @@ Experiencing issues introduced by this release? Please report them in our [issue
 <!--more-->
 ## {% linkable_title Breaking Changes %}
 
-- Pollen.com: Added attributes on top 3 allergens ([@bachya] - [#14018]) ([sensor.pollen docs]) (breaking change)
-- Add Sonos device attribute with grouping information ([@amelchio] - [#13553]) ([media_player.sonos docs]) (breaking change)
-- Re-implement HomematicIP cloud to async ([@mxworm] - [#13468]) ([homematicip_cloud docs]) ([sensor.homematicip_cloud docs]) (breaking change)
-- Move RainMachine to component/hub model ([@bachya] - [#14085]) ([rainmachine docs]) ([switch.rainmachine docs]) (breaking change) (new-platform)
+- Pollen.com: Added attributes on top 3 allergens. This caused attribute names `primary_allergen_genus`, `primary_allergen_name` and `primary_allergen_type` to be suffixed with `_1` ([@bachya] - [#14018]) ([sensor.pollen docs]) (breaking change)
+- Add Sonos device attribute with grouping information. The `media_player.sonos` attribute `is_coordinator` has been removed; the new attribute `sonos_group` (listing all group members, coordinator first) can be used instead. ([@amelchio] - [#13553]) ([media_player.sonos docs]) (breaking change)
+- Re-implement HomematicIP cloud to async. Change of configuration schema: `name` is optional and cannot be empty. Remove of state attributes for sensors. Remove of additional sensor to show state of all found components ([@mxworm] - [#13468]) ([homematicip_cloud docs]) ([sensor.homematicip_cloud docs]) (breaking change)
 - System log: make firing event optional ([@balloob] - [#14102]) ([system_log docs]) (breaking change)
-- Disable eliqonline requirement ([@balloob] - [#14156]) ([sensor.eliqonline docs]) (breaking change)
-- Custom component loading cleanup ([@balloob] - [#14211]) (breaking change)
 - Converts RainMachine to hub model (part 2) ([@bachya] - [#14225]) ([rainmachine docs]) ([switch.rainmachine docs]) (breaking change)
 - Homekit: Changed device_class requirement Humidity Sensor ([@cdce8p] - [#14277]) ([homekit docs]) (breaking change)
-- Sensor device classes ([@cdce8p] - [#14282]) ([sensor docs]) (breaking change)
-- Matrix Chatbot ([@tinloaf] - [#13355]) ([matrix docs]) ([notify docs]) (breaking change) (new-platform)
+- The sensor unit `lux` has been replaced with `lx` for consistency. That covers the following sensor platforms: homematic, isy994, miflora, mysensors, tahoma, vera and template sensors. To add light sensors for the HomeKit component the device_class changed to illuminance. ([@cdce8p] - [#14282]) ([sensor docs]) (breaking change)
+- The Matrix notification platform now depends on the the new Matrix component. Please see the documentation for how to configure the Matrix component. ([@tinloaf] - [#13355]) ([matrix docs]) ([notify docs]) (breaking change) (new-platform)
+- Move RainMachine to component/hub model and remove Remote API. ([@bachya] - [#14085] - [#14225]) ([rainmachine docs]) ([switch.rainmachine docs]) (breaking change) (new-platform)
+
+```yaml
+# New rainmachine config
+rainmachine:
+  ip_address: 192.168.1.100
+  password: abc123
+  switches:
+    zone_run_time: 240
+```
 
 ## {% linkable_title Beta Fixes %}
 
@@ -54,7 +61,8 @@ Experiencing issues introduced by this release? Please report them in our [issue
 - Fix module names for custom components ([@balloob] - [#14317]) (beta fix)
 - Revert custom component loading logic ([@balloob] - [#14327]) (beta fix)
 - fix(hbmqtt): partial packets breaking hbmqtt ([@graffic] - [#14329]) ([mqtt docs]) (beta fix)
-- Fix Yeelight naming ([@syssi])
+- Ignore more loading errors ([@balloob] - [#14331]) (beta fix)
+- Ignore NaN values for influxdb ([@amelchio] - [#14347]) ([influxdb docs]) (beta fix)
 
 ## {% linkable_title All changes %}
 
@@ -71,7 +79,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
 - Remove excessive debugging in webostv module ([@stephanerosi] - [#14056]) ([media_player.webostv docs])
 - Support new Xiaomi Aqara device model names and LAN protocol 2.0 ([@ileler] - [#13540]) ([xiaomi_aqara docs]) ([binary_sensor.xiaomi_aqara docs]) ([light.xiaomi_aqara docs]) ([sensor.xiaomi_aqara docs]) ([switch.xiaomi_aqara docs])
 - Add devices to Tahoma ([@bakedraccoon] - [#14075]) ([tahoma docs]) ([cover.tahoma docs]) ([sensor.tahoma docs])
-- New sensor domain expiry ([@masarliev] - [#14067]) ([sensor.domain_expiry docs]) (new-platform)
 - Modify weather components for "new" frontend card ([@c727] - [#14076]) ([weather.buienradar docs]) ([weather.darksky docs]) ([weather.openweathermap docs])
 - Add Sonos device attribute with grouping information ([@amelchio] - [#13553]) ([media_player.sonos docs]) (breaking change)
 - Re-implement HomematicIP cloud to async ([@mxworm] - [#13468]) ([homematicip_cloud docs]) ([sensor.homematicip_cloud docs]) (breaking change)
@@ -115,7 +122,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
 - Fixes #14169 (Upgrade pyupnp-async to 0.1.0.2) ([@dgomes] - [#14210]) ([upnp docs])
 - zha: Clean up binary_sensor listener registration/state updates ([@rcloran] - [#14197])
 - HomematicIP cloud: Add logic to check accesspoint connection state ([@sander76] - [#14203]) ([homematicip_cloud docs])
-- Foundation for users ([@balloob] - [#13968]) ([auth docs]) ([http docs]) (new-platform)
+- Foundation for users ([@balloob] - [#13968]) ([http docs]) (new-platform)
 - Allow easy extension of websocket API ([@balloob] - [#14186]) ([frontend docs]) ([websocket_api docs])
 - Change the divisor for total consumption output ([@CM000n] - [#14215]) ([switch.fritzbox docs])
 - Upgrade mypy to 0.590 ([@fabaff] - [#14207])
@@ -133,6 +140,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
 - Add Social Blade Sensor ([@meauxt] - [#14060]) ([sensor.socialblade docs]) ([sensor.uscis docs]) (new-platform)
 - UPnP code cleanup ([@dgomes] - [#14235]) ([upnp docs]) ([sensor.upnp docs])
 - Improve config schema of the blackbird component ([@syssi] - [#14007]) ([media_player.blackbird docs])
+- Fix Hue color state for missing xy ([@amelchio] - [#14230]) ([light.hue docs])
 - Add support for tracking devices on Netgear access points ([@MatMaul] - [#13331]) ([device_tracker docs])
 - WUnderground unique ids ([@OttoWinter] - [#13311]) ([sensor.wunderground docs])
 - Add PostNL sensor (Dutch Postal Services) ([@iMicknl] - [#12366]) ([sensor.postnl docs]) (new-platform)
@@ -142,11 +150,12 @@ Experiencing issues introduced by this release? Please report them in our [issue
 - Restores switch state, case the switch is optimistic ([@dgomes] - [#14151]) ([switch.mqtt docs])
 - Issue/add template fans ([@giangvo] - [#12027]) ([fan.template docs]) (new-platform)
 - HomeKit - Climate: power state on/off support ([@roiff] - [#14082]) ([homekit docs])
-- Demo Sensor - Added device_class support ([@cdce8p] - [#14269]) ([sensor.demo docs])
+- Demo Sensor - Added device_class support ([@cdce8p] - [#14269])
 - Re-enable eliqonline requirement ([@molobrakos] - [#14265]) ([sensor.eliqonline docs])
 - Add fetching camera thumbnails over websocket ([@balloob] - [#14231]) ([camera docs]) ([frontend docs]) ([image_processing docs]) ([microsoft_face docs]) ([websocket_api docs])
 - Allow fetching media player covers via websocket connection ([@balloob] - [#14233]) ([media_player docs])
 - Fix ZWave light brightness ([@cdce8p] - [#14261]) ([light.zwave docs])
+- Color fixes for Wink lights ([@amelchio] - [#14263]) ([light.wink docs])
 - fix check config not working after #14211 ([@fanthos] - [#14259])
 - Issue Template Fix CRLF ([@OttoWinter] - [#14283])
 - Upgrade attrs to 18.1.0 ([@fabaff] - [#14281])
@@ -154,6 +163,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
 - Upgrade holidays to 0.9.5 ([@fabaff] - [#14274]) ([binary_sensor.workday docs])
 - Homekit: Changed device_class requirement Humidity Sensor ([@cdce8p] - [#14277]) ([homekit docs]) (breaking change)
 - HomeKit: Support triggered state for alarm_control_panel ([@schmittx] - [#14285]) ([homekit docs])
+- Fix filter sensor missing window_size argument ([@dgomes] - [#14252]) ([sensor.filter docs])
 - Upgrade astral to 1.6.1 ([@fabaff] - [#14297])
 - BOM Weather throttle fix ([@nickw444] - [#14234]) ([sensor.bom docs])
 - Publish attributes unconditionally ([@blackwind] - [#14179]) ([mqtt_statestream docs])
@@ -163,7 +173,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
 - Add alarmdotcom sensor status ([@jnewland] - [#14254]) ([alarm_control_panel.alarmdotcom docs])
 - Add domain to labels and count state changes to Prometheus ([@jnewland] - [#14253]) ([prometheus docs])
 - Add support for max_volume ([@relvacode] - [#13822]) ([media_player.onkyo docs])
-- Refactor ImageProcessingFaceEntity ([@robmarkcole] - [#14296]) ([image_processing docs]) ([image_processing.demo docs]) ([image_processing.dlib_face_detect docs]) ([image_processing.dlib_face_identify docs]) ([image_processing.microsoft_face_detect docs]) ([image_processing.microsoft_face_identify docs])
+- Refactor ImageProcessingFaceEntity ([@robmarkcole] - [#14296]) ([image_processing docs]) ([image_processing.dlib_face_detect docs]) ([image_processing.dlib_face_identify docs]) ([image_processing.microsoft_face_detect docs]) ([image_processing.microsoft_face_identify docs])
 - Onkyo: SUPPORT_VOLUME_STEP ([@rsmeral] - [#14299]) ([media_player.onkyo docs])
 - Add All-Linking capabilities ([@teharris1] - [#14065]) ([insteon_plm docs]) ([binary_sensor.insteon_plm docs]) ([fan.insteon_plm docs]) ([light.insteon_plm docs]) ([sensor.insteon_plm docs]) ([switch.insteon_plm docs])
 - Add missing 'sensor' to ABODE_PLATFORMS ([@jloutsenhizer] - [#14313]) ([abode docs]) (beta fix)
@@ -171,6 +181,8 @@ Experiencing issues introduced by this release? Please report them in our [issue
 - Fix module names for custom components ([@balloob] - [#14317]) (beta fix)
 - Revert custom component loading logic ([@balloob] - [#14327]) (beta fix)
 - fix(hbmqtt): partial packets breaking hbmqtt ([@graffic] - [#14329]) ([mqtt docs]) (beta fix)
+- Ignore more loading errors ([@balloob] - [#14331]) (beta fix)
+- Ignore NaN values for influxdb ([@amelchio] - [#14347]) ([influxdb docs]) (beta fix)
 
 [#12027]: https://github.com/home-assistant/home-assistant/pull/12027
 [#12060]: https://github.com/home-assistant/home-assistant/pull/12060
@@ -260,14 +272,17 @@ Experiencing issues introduced by this release? Please report them in our [issue
 [#14220]: https://github.com/home-assistant/home-assistant/pull/14220
 [#14221]: https://github.com/home-assistant/home-assistant/pull/14221
 [#14225]: https://github.com/home-assistant/home-assistant/pull/14225
+[#14230]: https://github.com/home-assistant/home-assistant/pull/14230
 [#14231]: https://github.com/home-assistant/home-assistant/pull/14231
 [#14233]: https://github.com/home-assistant/home-assistant/pull/14233
 [#14234]: https://github.com/home-assistant/home-assistant/pull/14234
 [#14235]: https://github.com/home-assistant/home-assistant/pull/14235
+[#14252]: https://github.com/home-assistant/home-assistant/pull/14252
 [#14253]: https://github.com/home-assistant/home-assistant/pull/14253
 [#14254]: https://github.com/home-assistant/home-assistant/pull/14254
 [#14259]: https://github.com/home-assistant/home-assistant/pull/14259
 [#14261]: https://github.com/home-assistant/home-assistant/pull/14261
+[#14263]: https://github.com/home-assistant/home-assistant/pull/14263
 [#14265]: https://github.com/home-assistant/home-assistant/pull/14265
 [#14269]: https://github.com/home-assistant/home-assistant/pull/14269
 [#14274]: https://github.com/home-assistant/home-assistant/pull/14274
@@ -285,6 +300,9 @@ Experiencing issues introduced by this release? Please report them in our [issue
 [#14317]: https://github.com/home-assistant/home-assistant/pull/14317
 [#14327]: https://github.com/home-assistant/home-assistant/pull/14327
 [#14329]: https://github.com/home-assistant/home-assistant/pull/14329
+[#14331]: https://github.com/home-assistant/home-assistant/pull/14331
+[#14347]: https://github.com/home-assistant/home-assistant/pull/14347
+[#14381]: https://github.com/home-assistant/home-assistant/pull/14381
 [@CM000n]: https://github.com/CM000n
 [@Danielhiversen]: https://github.com/Danielhiversen
 [@Hate-Usernames]: https://github.com/Hate-Usernames
@@ -383,11 +401,14 @@ Experiencing issues introduced by this release? Please report them in our [issue
 [image_processing.microsoft_face_detect docs]: /components/image_processing.microsoft_face_detect/
 [image_processing.microsoft_face_identify docs]: /components/image_processing.microsoft_face_identify/
 [image_processing.opencv docs]: /components/image_processing.opencv/
+[influxdb docs]: /components/influxdb/
 [insteon_plm docs]: /components/insteon_plm/
 [light.deconz docs]: /components/light.deconz/
 [light.flux_led docs]: /components/light.flux_led/
+[light.hue docs]: /components/light.hue/
 [light.insteon_plm docs]: /components/light.insteon_plm/
 [light.mqtt_json docs]: /components/light.mqtt_json/
+[light.wink docs]: /components/light.wink/
 [light.xiaomi_aqara docs]: /components/light.xiaomi_aqara/
 [light.yeelight docs]: /components/light.yeelight/
 [light.zwave docs]: /components/light.zwave/
@@ -422,6 +443,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
 [sensor.domain_expiry docs]: /components/sensor.domain_expiry/
 [sensor.dsmr docs]: /components/sensor.dsmr/
 [sensor.eliqonline docs]: /components/sensor.eliqonline/
+[sensor.filter docs]: /components/sensor.filter/
 [sensor.homematicip_cloud docs]: /components/sensor.homematicip_cloud/
 [sensor.insteon_plm docs]: /components/sensor.insteon_plm/
 [sensor.lastfm docs]: /components/sensor.lastfm/

source/cloud/google_assistant.markdown

@@ -20,7 +20,7 @@ To use this integration, you need to have:
 
  - The cloud component set up. [Learn more](/components/cloud/)
  - A Google Assistant enabled device like the Google Home
- - Activated the [Home Assistant Smart Home skill for Google Assistant](https://assistant.google.com/services/a/uid/00000091fd5fb875)
+ - Activated the Home Assistant Smart Home skill for Google Assistant by using the Google Home app, select *Home control*, and then add *hass.io* using the *Add devices* option.
 
 You can use `configuration.yaml` to configure the entities that are being shown to Google Assistant and how they are exposed.
 

source/hassio/installation.markdown

@@ -22,6 +22,16 @@ Hass.io images are available for all available Raspberry Pi and Intel NUC platfo
   - [Intel NUC][nuc]
 
 - Flash the downloaded image to an SD card using [Etcher].
+
+<p class='note warning'>
+  There is an [issue in the Etcher flashing process on Mac OS High Sierra](https://github.com/resin-io/etcher/issues/1908).
+  There is an easy workaround, just uncompress the image first.
+  
+  ```bash
+  bunzip2 -c resinos-hassio-1.1-raspberrypi3.img.bz2 > image.img
+  ```
+</p>
+
 - Optional - Setup the WiFi or static IP: On the SD-card, edit the `system-connections/resin-sample` file and follow the [ResinOS howto][resinos-network].
 - Insert SD card to Raspberry Pi and turn it on. On first boot, it downloads the latest version of Home Assistant which takes ~20 minutes (slower/faster depending on the platform).
 

source/help/index.markdown

@@ -51,6 +51,7 @@ Looking for [talking points](/help/talking-points/) or [trivia](/help/trivia)?
 
 Don't miss the regular [Home Assistant podcasts](https://hasspodcast.io/).
 
+- [​Home Assistant lets you automate your smart home without giving up privacy](https://www.the-ambient.com/features/home-assistant-automation-privacy-582) - May 2018
 - [HackSpace magazine #6](https://s3-eu-west-1.amazonaws.com/rpi-magazines/issues/full_pdfs/000/000/013/original/HS_6_Digital_Optimised.pdf?1524495009) - May 2018
 - [The winners of the Thomas-Krenn-Awards 2018](https://www.thomas-krenn.com/de/tkmag/allgemein/die-gewinner-des-thomas-krenn-awards-2018-stehen-fest/) - March 2018
 - [Hausautomations-Schaltzentrale Home Assistant auf Python-Basis](https://www.heise.de/ct/ausgabe/2017-26-Hausautomations-Schaltzentrale-Home-Assistant-3909532.html) - December 2017