Merge pull request #9568 from home-assistant/rc

Release 0.94
2025-07-26 10:46:51 +00:00 · 2019-06-05 18:46:06 +02:00 · 2019-06-05 18:46:06 +02:00 · f8e7d04fa2
commit f8e7d04fa2
parent 456add7392 c1c1141f95
35 changed files with 1890 additions and 145 deletions
--- a/_config.yml
+++ b/_config.yml
@ -138,9 +138,9 @@ social:

 # Home Assistant release details
 current_major_version: 0
-current_minor_version: 93
-current_patch_version: 2
-date_released: 2019-05-22
+current_minor_version: 94
+current_patch_version: 0
+date_released: 2019-06-05

 # Either # or the anchor link to latest release notes in the blog post.
 # Must be prefixed with a # and have double quotes around it.
--- a/source/_components/alert.markdown
+++ b/source/_components/alert.markdown
@ -23,11 +23,6 @@ water leak sensors, or any condition that may need your attention.
 Alerts will add an entity to the front end only when they are firing.
 This entity allows you to silence an alert until it is resolved.

-<p class='note warning'>
-When using the `alert` component, it is important that the time zone used for Home Assistant and the underlying operating system match.
-Failing to do so may result in multiple alerts being sent at the same time (such as when Home Assistant is set to the `America/Detroit` time zone but the operating system uses `UTC`).
-</P>
-
 ### {% linkable_title Basic Example %}

 The `alert` component makes use of any of the `notifications` components. To
--- a/source/_components/androidtv.markdown
+++ b/source/_components/androidtv.markdown
@ -208,7 +208,7 @@ stop_netflix:

 ### {% linkable_title `androidtv.adb_command` %}

-The service `androidtv.adb_command` allows you to send either keys or ADB shell commands to your Android TV / Fire TV device.
+The service `androidtv.adb_command` allows you to send either keys or ADB shell commands to your Android TV / Fire TV device. If there is any output, it will be stored in the `'adb_response'` attribute (i.e., `state_attr('media_player.android_tv_living_room', 'adb_response')` in a template) and logged at the INFO level.

 | Service data attribute | Optional | Description |
 | ---------------------- | -------- | ----------- |
@ -240,4 +240,4 @@ Available key commands include:

 The full list of key commands can be found [here](https://github.com/JeffLIrion/python-androidtv/blob/e1c07176efc9216cdcff8245c920224c0234ea56/androidtv/constants.py#L115-L155).

-You can also use the command `GET_PROPERTIES` to retrieve the properties used by Home Assistant to update the device's state.  These will be logged at the INFO level and can be used to help improve state detection in the backend [androidtv](https://github.com/JeffLIrion/python-androidtv) package.
+You can also use the command `GET_PROPERTIES` to retrieve the properties used by Home Assistant to update the device's state.  These will be stored in the media player's `'adb_response'` attribute and logged at the INFO level, this information can be used to help improve state detection in the backend [androidtv](https://github.com/JeffLIrion/python-androidtv) package.
--- a/source/_components/axis.markdown
+++ b/source/_components/axis.markdown
@ -11,6 +11,7 @@ logo: axis.png
 ha_category:
  - Camera
  - Binary Sensor
+  - Switch
 ha_config_flow: true
 ha_release: 0.45
 ha_iot_class: Local Push
@ -43,3 +44,11 @@ The following sensor types are supported:
 - Passive IR motion detection
 - Sound detection
 - Day/night mode
+- Inputs and Supervised Inputs
+
+## {% linkable_title Switch %}
+
+The following controllable port types are supported:
+
+- Output
+- Relay
--- a/source/_components/azure_event_hub.markdown
+++ b/source/_components/azure_event_hub.markdown
@ -0,0 +1,103 @@
+---
+layout: page
+title: "Azure Event Hub"
+description: "Setup for Azure Event Hub integration"
+date: 2019-05-15 08:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: azure_event_hub.svg
+ha_category:
+  - History
+ha_release: 0.94
+---
+
+The `Azure Event Hub` component allows you to hook into the Home Assistant event bus and send events to [Azure Event Hub](https://azure.microsoft.com/en-us/services/event-hubs/) or to a [Azure IoT Hub](https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-messages-read-builtin). 
+
+## {% linkable_title First time setup %}
+
+This assumes you already have a Azure account. Otherwise create a Free account [here](https://azure.microsoft.com/en-us/free/).
+
+You need to create a Event Hub namespace and a Event Hub in that namespace, you can follow [this guide](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-create). Alternatively you can directly deploy an ARM template with the namespace and the Event Hub [from here](https://github.com/Azure/azure-quickstart-templates/tree/master/201-event-hubs-create-event-hub-and-consumer-group/).
+
+You must then create a Shared Access Policy for the Event Hub with 'Send' claims or use the RootManageAccessKey from your namespace (this key has additional claims, including managing the event hub and listening, which are not needed for this purpose), for more details on the security of Event Hubs [go here](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-authentication-and-security-model-overview).
+
+Once you have the name of your namespace, instance, Shared Access Policy and the key for that policy, you can setup the component itself.
+
+## {% linkable_title Configuration %}
+
+Add the following lines to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+azure_event_hub:
+  event_hub_namespace: NAMESPACE_NAME
+  event_hub_instance_name: EVENT_HUB_INSTANCE_NAME
+  event_hub_sas_policy: SAS_POLICY_NAME
+  event_hub_sas_key: SAS_KEY
+  filter:
+    include_domains:
+    - homeassistant
+    - light
+    - media_player
+```
+
+{% configuration %}
+event_hub_namespace:
+  description: The name of your Event Hub namespace.
+  required: true
+  type: string
+event_hub_instance_name:
+  description: The name of your Event Hub instance.
+  required: true
+  type: string
+event_hub_sas_policy:
+  description: The name of your Shared Access Policy.
+  required: true
+  type: string
+event_hub_sas_key:
+  description: The key for the Shared Access Policy.
+  required: true
+  type: string
+filter:
+  description: Filter domains and entities for Event Hub.
+  required: false
+  type: map
+  default: Includes all entities from all domains
+  keys:
+    include_domains:
+      description: List of domains to include (e.g., `light`).
+      required: false
+      type: list
+    exclude_domains:
+      description: List of domains to exclude (e.g., `light`).
+      required: false
+      type: list
+    include_entities:
+      description: List of entities to include (e.g., `light.attic`).
+      required: false
+      type: list
+    exclude_entities:
+      description: List of entities to include (e.g., `light.attic`).
+      required: false
+      type: list
+{% endconfiguration %}
+
+<p class='note warning'>
+  Not filtering domains or entities will send every event to Azure Event Hub, thus taking up a lot of space. 
+</p>
+
+<p class='note warning'>
+Event Hubs have a retention time of at most 7 days, if you do not capture or use the events they are deleted automatically from the Event Hub, the default retention is 1 day.
+</p>
+
+### {% linkable_title Using the data in Azure %}
+
+There are a number of ways to stream the data that comes into the Event Hub into storages in Azure, the easiest way is to use the built-in Capture function and this allows you to capture the data in Azure Blob Storage or Azure Data Lake store, [details here](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-capture-overview).
+
+Other storages in Azure (and outside) are possible with a [Azure Stream Analytics job](https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-define-inputs#stream-data-from-event-hubs), for instance for [Cosmos DB](https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-documentdb-output), [Azure SQL DB](https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-sql-output-perf), [Azure Table Storage](https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-define-outputs#table-storage), custom writing to [Azure Blob Storage](https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-custom-path-patterns-blob-storage-output) and [Topic and Queues](https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-quick-create-portal#configure-job-output).
+
+On the analytical side, Event Hub can be directly fed into [Azure Databricks Spark](https://docs.microsoft.com/en-us/azure/azure-databricks/databricks-stream-from-eventhubs?toc=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fevent-hubs%2FTOC.json&bc=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fbread%2Ftoc.json), [Azure Time Series Insights](https://docs.microsoft.com/en-us/azure/time-series-insights/time-series-insights-how-to-add-an-event-source-eventhub) and [Microsoft Power BI](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-tutorial-visualize-anomalies).
+
+The final way to use the data in Azure is to connect a Azure Function to the Event Hub using the [Event Hub trigger binding](https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-event-hubs).
--- a/source/_components/blink.markdown
+++ b/source/_components/blink.markdown
@ -73,6 +73,16 @@ sensors:
      required: false
      type: list
      default: all (`battery`, `temperature`, `wifi_strength`)
+offset:
+  description: How far back in time (minutes) to look for motion. Motion is determined if a new video has been recorded between now and the last time you refreshed plus this offset.
+  required: false
+  type: integer
+  default: 1
+mode:
+  description: Set to 'legacy' to enable use of old API endpoint subdomains (APIs can differ based on region, so use this if you are having issues with the integration).
+  required: false
+  type: string
+  default: not set
 {% endconfiguration %}

 Once Home Assistant starts, the `blink` component will create the following platforms:
--- a/source/_components/doorbird.markdown
+++ b/source/_components/doorbird.markdown
@ -37,18 +37,15 @@ To connect your device, add the following to your `configuration.yaml` file:
 ```yaml
 # Example configuration.yaml entry
 doorbird:
-  token: YOUR_DOORBIRD_TOKEN
  devices:
    - host: DOORBIRD_IP_OR_HOSTNAME
      username: YOUR_USERNAME
      password: YOUR_PASSWORD
+      token: YOUR_DOORBIRD_TOKEN
 ```

 {% configuration %}
-token:
-  description: Token to be used to authenticate Doorbird calls to Home Assistant. This can be obtained from your "Digital Passport" document provided with your Doorbird.
-  required: true
-  type: string
+
 devices:
  description: List of Doorbird devices.
  required: true
@ -66,6 +63,10 @@ devices:
      description: The password for the user specified.
      required: true
      type: string
+    token:
+      description: Token to be used to authenticate Doorbird calls to Home Assistant. This is a user defined value and should be unique across all Doorbird devices.
+      required: true
+      type: string
    name:
      description: Custom name for this device.
      required: false
@ -74,56 +75,62 @@ devices:
      description: If your DoorBird cannot connect to the machine running Home Assistant because you are using dynamic DNS or some other HTTP configuration (such as HTTPS), specify the LAN IP of the machine here to force a LAN connection.
      required: false
      type: string
-    monitored_conditions:
-      description: Monitor motion and/or doorbell events for this device.
+    events:
+      description: Custom event names to be registered on the device. User defined values. Special characters should be avoided.
      required: false
-      type: string
-      keys:
-        doorbell:
-          description: Monitor doorbell events.
-        motion:
-          description: Monitor motion events (Motion monitoring must be enabled on the doorstation via DoorBird app).
-        relay:
-          description: Monitor relay events. This event is fired even if a relay is not physically connected to the door station.  Can be used to lock/unlock any smart lock present in Home Assistant via the Doorbird app.
-
+      type: list
+      
 {% endconfiguration %}

 ## {% linkable_title Full example %}

 ```yaml
 doorbird:
-  token: YOUR_DOORBIRD_TOKEN
  devices:
    - host: DOORBIRD_IP_OR_HOSTNAME
      username: YOUR_USERNAME
      password: YOUR_PASSWORD
+      token: CUSTOM_TOKEN_1
      hass_url_override: HASS_URL
      name: Front Door
    - host: DOORBIRD_IP_OR_HOSTNAME
      username: YOUR_USERNAME
      password: YOUR_PASSWORD
+      token: CUSTOM_TOKEN_2
      name: Driveway Gate
-      monitored_conditions:
-        - doorbell
-        - motion
-        - relay
+      events:
+        - doorbell_1
+        - somebody_pressed_the_button
+        - relay_unlocked
+        - unit_2_bell
+        - rfid_card_scanned
 ```

 ## {% linkable_title Events %}

-Home Assistant will fire an event any time a `monitored_condition` happens on a doorstation.  Event names are created using the format `doorbird_{station}_{event}` (Examples: `doorbird_side_entry_button`, `doorbird_side_entry_motion`).  You can verify the assigned event names in the Available Events list on the Events developer view.
+Events can be defined for each configured DoorBird device independently. These events will be registered on the device and can be attached to a schedule via the DoorBird app. 
+
+See [Schedules](#schedules) section below for details on how to configure schedules.
+
+Event names will be prefixed by `doorbird_`. For example, the example event `somebody_pressed_the_button` will be seen in Home Assistant as `doorbird_somebody_pressed_the_button`. This is to prevent conflicts with other events.
+
+See [Automation Example](#automation_example) section below for details on how to use the event names in an automation.

 <p class="note info">
-Home Assistant will register the monitored conditions with the device as schedule entries that correspond to favorites on startup. If you remove monitored conditions from your configuration, Home Assistant will attempt to remove these items from the device. However, in some cases, such as if the IP address of the machine running Home Assistant changes or if the device is renamed in your configuration, this will not work correctly and some data will be left in device storage.
-<br><br>
-This should not cause any problems, but if you would like to remove it, open a new browser window and navigate to `{Home Assistant URL}/api/doorbird/clear/{DoorBird name}`. Replace `{Home Assistant URL}` with the full path to your running instance, such as `http://localhost:8123`. Replace `{DoorBird name}` with the name specified in your configuration for the device you would like to clear, or how it appears in the Home Assistant UI if you have not specified one, such as `DoorBird 1`. Then use the mobile app to reschedule push notifications.
-<br><br>
-Please note that clearing device registrations will prevent the device from sending pushes to Home Assistant until you restart your instance with the component enabled. It could also affect other third-party applications you may use with your DoorBird device. It will not break the official mobile app in any way, so mobile push notifications will still work.
+Events will not be received in Home Assistant until a schedule is defined via the DoorBird app.
 </p>

+#### {% linkable_title Clearing Registered Events %}
+Events can be cleared from DoorBird devices by visiting a special URL.
+
+Simply open a new browser window and navigate to `{Home Assistant URL}/api/doorbird/clear?token={DEVICE_TOKEN}`. Replace `{Home Assistant URL}` with the full path to your running instance, such as `http://localhost:8123`. Replace `{DEVICE_TOKEN}` with the token specified in your configuration for the device you would like to clear.
+<br><br>
+Please note that clearing device events will require configuration steps above to be taken again. It could also affect other third-party applications you may use with your DoorBird device. It will not break the official mobile app in any way, so mobile push notifications will still work.
+
+
 #### {% linkable_title Event Data %}

-Each event includes live image and video URLs for the Doorbird device that triggered the event. These URLs can be found on the event data and can be useful in automation actions.  For example, you could use `html5_viewer_url` on a notification to be linked directly to the live view of the device that triggered the automation.
+Each event will include live image and video URLs for the Doorbird device that triggered the event. These URLs can be found on the event data and can be useful in automation actions. For example, you could use `html5_viewer_url` on a notification to be linked directly to the live view of the device that triggered the automation.

 The following keys are available on `event_data`:

@ -134,16 +141,33 @@ The following keys are available on `event_data`:
 - `html5_viewer_url`

 <p class="note">
-The URLs on the event will be based on the configuration used to connect to your Doorbird device.  Ability to connect from outside your network will depend on your configuration.
+The URLs on the event will be based on the configuration used to connect to your Doorbird device. Ability to connect from outside your network will depend on your configuration.
 </p>

+#### {% linkable_title Schedules %}
+
+Once events have been registered on the DoorBird device, they must be attached to a schedule using the official DoorBird app on Android or iOS. Currently there are schedules available for doorbell, motion, relay, and RFID events (on supported devices).
+
+For iOS, the schedules can be found by navigating to the following areas of the app:
+
+- Doorbell  | Settings > Administration > Specific Device > Schedule for Doorbell
+- Motion    | Settings > Administration > Specific Device > 3D Motion Sensor (Settings) > Schedule for Actions
+- Relay     | Settings > Administration > Specific Device > Relays > Schedule
+- RFID      | Settings > Administration > Specific Device > RFID Transponder > Settings > Select Transponder > Schedule
+
+Once you are on the desired schedule, click the dropdown button in the upper left to switch to the HTTP Calls view. Now if you click on the heading just above the schedule, you can select the event you would like to be called for the particular schedule that is being viewed.
+
+On the desired event, you should be able to specify blocks of time for when you would like the event to be sent to Home Assistant. If you want the event to always send, the square in the upper right can be used to populate the entire schedule. Events will be fired to Home Assistant for blocks of time that are blue.
+
+Remember to complete the schedule assignment steps above for each event type that you registered.
+
 ### {% linkable_title Automation Example %}

 ```yaml
 - alias: Doorbird Ring
  trigger:
    platform: event
-    event_type: doorbird_side_entry_button
+    event_type: doorbird_somebody_pressed_the_button
  action:
    service: light.turn_on
      entity_id: light.side_entry_porch
--- a/source/_components/fibaro.markdown
+++ b/source/_components/fibaro.markdown
@ -11,6 +11,7 @@ logo: fibaro.png
 ha_category:
  - Hub
  - Binary Sensor
+  - Climate
  - Cover
  - Light
  - Sensor
@ -33,6 +34,7 @@ There is currently support for the following device types within Home Assistant:

 - Binary Sensor
 - Cover
+- Climate
 - Light
 - Sensor
 - Scene
--- a/source/_components/geniushub.markdown
+++ b/source/_components/geniushub.markdown
@ -11,17 +11,47 @@ logo: geniushub.png
 ha_category:
  - Climate
  - Water heater
+  - Sensor
+  - Binary sensor
 ha_release: 0.92
 ha_iot_class: Local Polling
 ---

-The `geniushub` integration links Home Assistant with your Genius Hub (the hub does not have to be in the same network as HA).
+The `geniushub` integration links Home Assistant with your Genius Hub for controlling its Zones and Devices. Currently, there is no support for Zone schedules.

-Currently only **Radiator** and **Hot Water Temperature** zones are supported. Within HA, each **Radiator** zone will appear as a `Climate` device, and each **Hot Water Temperature** zone will appear as a `WaterHeater` device.
+It uses the [geniushub-client](https://pypi.org/project/geniushub-client/) library.

-The device's `operating_mode` can be set to one of `off`, `timer`, `on` (i.e. **Override** mode) or `eco`. The `eco` mode is a proxy for the **Footprint** mode and so is only available to **Radiator** zones that have room sensors.
+### {% linkable_title Zones %}

-Other properties are available via the device's state attributes, which includes a JSON data structure called `status`. For example, in the case of **Radiator** zones/`Climate` devices:
+Each Zone controlled by your Genius hub will be exposed as either a:
+
+ - `Climate` entity, for **Radiator** Zones, and
+ - `Water Heater`, for **Hot Water Temperature** Zones
+
+Other Zone types, such as **On / Off** Zones, are not currently supported.
+
+Each such entity will report back its mode, state, setpoint and current temperature; other properties are available via its attributes (see below).
+
+In addition, the entity's mode and setpoint can be changed. The entity's `operating_mode` can be set to one of `off`, `timer`, `on` (i.e. **Override** mode) or `eco`. The `eco` mode is a proxy for the **Footprint** mode and so is only available to **Radiator** Zones that have room sensors.
+
+### {% linkable_title Devices %}
+
+If the Hub is directly polled using the v3 API (see below), then each Device controlled by your Genius hub will be exposed as either a:
+
+ - `Sensor` entity with a % battery, for any Device with a battery (e.g. a Genius Valve), or
+ - `Binary Sensor` entity with on/off state for any Device that is a switch (e.g. a Smart Plug)
+
+Each such entity will report back its primary state; in addition, `assigned_zone` and `last_comms` (last communications time) are available via the entity's attributes.
+
+### {% linkable_title Issues %}
+
+There are three `Sensor` entities that will indicate the number of **Errors**, **Warnings** and **Information** issues.
+
+Each such entity has a state attribute that will contain a list of any such issues. For example, `error_list`.
+
+### {% linkable_title State Attributes %}
+
+Other properties are available via each entity's state attributes. For example, in the case of **Radiator** Zones/`Climate` devices:

 ```json
 {
@ -35,7 +65,6 @@ Other properties are available via the device's state attributes, which includes
    }
  }
 }
-
 ```

 This data can be accessed in automations, etc. via a value template. For example:
@ -54,8 +83,6 @@ value_template: "{{ state_attr('climate.main_room', 'status').occupied }}"
 ```
 {% endraw %}

-Currently, there is no support for modifying schedules and neither do they appear in the state attributes.
-
 ## {% linkable_title Configuration %}

 To add your Genius Hub into your Home Assistant installation, add one of the following to your `configuration.yaml` file.
--- a/source/_components/geofency.markdown
+++ b/source/_components/geofency.markdown
@ -16,15 +16,13 @@ redirect_from:
  - /components/device_tracker.geofency/
 ---

-This component sets up integration with [Geofency](http://www.geofency.com/). Geofency is a [paid app](https://itunes.apple.com/app/id615538630) for iOS that lets users to configure a request that will be sent when a geofence or iBeacon region is entered or exited. This can be configured with Home Assistant to update your location.
-
-Enabling this component will automatically enable the Geofency Device Tracker.
+This component sets up integration with [Geofency](http://www.geofency.com/). Geofency is a paid app for iOS that lets users to configure a request that will be sent when a geofence or iBeacon region is entered or exited. This can be configured with Home Assistant to update your location.

 ## {% linkable_title Configuration %}

 To configure Geofency, you must set it up via the integrations panel in the configuration screen. You must then configure the iOS app (via the Webhook feature) to send a POST request to your Home Assistant server at the webhook URL provided by the integration during setup. Use the default POST format. Make sure to enable the 'Update Geo-Position' functionality for mobile beacons.

-Geofency will automatically generate the device tracker name used for geofences, and you will find it in `known_devices.yaml` after the first request. For beacons, the device name will be `beacon_<name from Geofency>`, e.g., `device_tracker.beacon_car`.
+Geofency will automatically generate the device tracker name used for geofences, and you will find it in the integrations section after the first request. For beacons, the device name will be `beacon_<name from Geofency>`, e.g., `device_tracker.beacon_car`.

 When using mobile beacons (optional) an entry in `configuration.yaml` is still needed as this can't be added via the integrations panel.

@ -49,4 +47,4 @@ geofency:

 When you enter a geofence or stationary beacon, your location name in Home Assistant will be set to the name of the geofence or beacon location in Geofency. When you exit a geofence or stationary beacon, your location name in Home Assistant will be set to `not home`. For mobile beacons, the location name will be `not_home` whenever the beacon is entered or exited outside of a [zone](/components/zone/), otherwise, it will be set to the name of the zone.

-To make Geofency work better with the [proximity](/components/proximity/) component, you should enable the 'Send Current Location' feature in the Webhook configuration screen. This ensures that the _current_ GPS coordinates are included in exit events instead of the coordinates of the (center of) the zone that was exited.
+To make Geofency work better with the [proximity](/components/proximity/) component, you should enable the 'Send Current Location' feature in the Webhook configuration screen. This ensures that the _current_ GPS coordinates are included in exit events instead of the coordinates of the (center of) the zone that was exited.
--- a/source/_components/gpslogger.markdown
+++ b/source/_components/gpslogger.markdown
@ -16,9 +16,7 @@ redirect_from:
 - /components/device_tracker.gpslogger/
 ---

-This component sets up integration with [GPSLogger](http://code.mendhak.com/gpslogger/). GPSLogger is an open source app for [Android](https://play.google.com/store/apps/details?id=com.mendhak.gpslogger) that allows users to set up a `POST` request to update GPS coordinates. This can be configured with Home Assistant to update your location.
-
-Enabling this component will automatically enable the GPSLogger Device Tracker.
+This component sets up integration with [GPSLogger](https://gpslogger.app/). GPSLogger is an open source app for Android that allows users to update your location in Home Assistant.

 ## {% linkable_title Configuration %}

--- a/source/_components/homematicip_cloud.markdown
+++ b/source/_components/homematicip_cloud.markdown
@ -96,7 +96,15 @@ authtoken:
  * Smoke sensor and alarm (*HmIP-SWSD*)
  * Motion Detector with Brightness Sensor - indoor (*HmIP-SMI*)
  * Motion Detector with Brightness Sensor - outdoor (*HmIP-SMO*)
+  * Presence Sensor – indoor (*HmIP-SPI*)
  * Water Sensor (*HmIP-SWD*)
+  * Remote Control - 8 buttons (*HmIP-RC8*) (battery only)
+  * Wall-mount Remote Control - 2-button (*HmIP-WRC2*) (battery only)
+  * Wall-mount Remote Control - 6-button (*HmIP-WRC6*) (battery only)
+  * Key Ring Remote Control - 4 buttons (*HmIP-KRC4*) (battery only)
+  * Key Ring Remote Control - alarm  (*HmIP-KRCA*) (battery only)
+  * Alarm Siren (*HmIP-ASIR, -B1*) (battery only)
+  * Remote Control for brand switches – 2-button (*HmIP-BRC2*) (battery only)

 * homematicip_cloud.climate
  * Climate group (*HmIP-HeatingGroup*)
@ -116,7 +124,7 @@ authtoken:
  * Switch actuator and meter for brand switches (*HmIP-BSM*)
  * Dimming actuator for brand switches (*HmIP-BDT*)
  * Dimming actuator flush-mount (*HmIP-FDT*)
-  * Switch Actuator and Meter – flush-mount (*HmIP-FSM*)
+  * Pluggable Dimmer – trailing edge (*HmIP-PDT*)
  * Switch Actuator for brand switches – with signal lamp (*HmIP-BSL*)

 * homematicip_cloud.sensor
@ -128,12 +136,13 @@ authtoken:
  * Temperature and Humidity sensor - outdoor (*HmIP-STHO, -A*)
  * Motion Detector with Brightness Sensor - indoor (*HmIP-SMI*)
  * Motion Detector with Brightness Sensor - outdoor (*HmIP-SMO*)
+  * Presence Sensor – indoor (*HmIP-SPI*)
  * Light Sensor - outdoor (*HmIP-SLO*)

 * homematicip_cloud.switch
  * Pluggable Switch (*HmIP-PS*)
  * Pluggable Switch and Meter (*HmIP-PSM*) - should also work with (*HmIP-PSM-CH, -IT, -UK, -PE*)
-  * Switch Actuator for brand switches – with signal lamp (*HmIP-BSL*)
+  * Switch Actuator and Meter – flush-mount (*HmIP-FSM, -FSM16*)
  * Open Collector Module Receiver - 8x (*HmIP-MOD-OC8*)
  * Multi IO Box - 2x (*HmIP-MIOB*)

@ -141,4 +150,14 @@ authtoken:
  * Weather Sensor – basic (*HmIP-SWO-B*)
  * Weather Sensor – plus (*HmIP-SWO-PL*)
  * Weather Sensor – pro (*HmIP-SWO-PR*)
+  
+Additional info:

+Push button devices are only available with a battery sensor. This is due to a limitation of the vendor API (eq3).
+It's not possible to detect a key press event on these devices at the moment.
+
+  * Remote Control - 8 buttons (*HmIP-RC8*)
+  * Wall-mount Remote Control - 2-button (*HmIP-WRC2*)
+  * Wall-mount Remote Control - 6-button (*HmIP-WRC6*)
+  * Key Ring Remote Control - 4 buttons (*HmIP-KRC4*)
+  * Key Ring Remote Control - alarm  (*HmIP-KRCA*)
--- a/source/_components/lcn.markdown
+++ b/source/_components/lcn.markdown
@ -11,6 +11,7 @@ logo: lcn.png
 ha_category:
  - Hub
  - Binary Sensor
+  - Climate
  - Cover
  - Light
  - Sensor
@ -31,11 +32,18 @@ With this setup sending and receiving commands to and from LCN modules is possib
 There is currently support for the following device types within Home Assistant:

 - [Binary Sensor](#binary-sensor)
+- [Climate](#climate)
 - [Cover](#cover)
 - [Light](#light)
 - [Sensor](#sensor)
 - [Switch](#switch)

+<p class='note'>
+  Please note: Besides the implemented platforms the `lcn` component offers a variety of [service calls](#services).
+  These service calls cover functionalities of the LCN system which cannot be represented by the platform implementations.
+  They are ideal to be used in automation scripts or for the `template` platforms.
+</p>
+
 ## {% linkable_title Configuration %}

 To use your LCN system in your installation, add the following lines to your `configuration.yaml` file.
@ -56,6 +64,16 @@ lcn:
      address: myhome.s0.m7
      source: binsensor1

+  climates:
+    - name: Temperature bedroom
+      address: myhome.s0.m7
+      source: var1
+      setpoint: r1varsetpoint
+      min_temp: 17.
+      max_temp: 30.
+      lockable: true
+      unit_of_measurement: °C
+
  covers:
    - name: Living room cover
      address: myhome.s0.m7
@ -72,7 +90,7 @@ lcn:
    - name: Temperature
      address: myhome.s0.m7
      source: var3
-      unit_of_measuremnt: °C
+      unit_of_measurement: °C
  
  switches:
    - name: Sprinkler switch
@ -128,14 +146,56 @@ binary_sensors:
      required: true
      type: string
    address:
-      description: "[Address](/components/lcn#lcn-addresses) of the module/group."
+      description: "[Address](#lcn-addresses) of the module/group."
      required: true
      type: string
    source:
-      description: "Sensor source ([BINSENSOR](/components/lcn#ports), [SETPOINT](/components/lcn#variables-and-units), [KEYS](/components/lcn#keys))."
+      description: "Sensor source ([BINSENSOR](#ports), [SETPOINT](#variables-and-units), [KEYS](#keys))."
      required: true
      type: string

+climates:
+  description: List of your climate devices.
+  required: false
+  type: map
+  keys:
+    name:
+      description: "Name of the climate controller."
+      required: true
+      type: string
+    address:
+      description: "[Address](#lcn-addresses) of the module/group."
+      required: true
+      type: string
+    source:
+      description: "Current temperature source ([VARIABLE](#variables-and-units))."
+      required: true
+      type: string
+    setpoint:
+      description: "Setpoint for target temperature ([VARIABLE](#variables-and-units), [SETPOINT](#variables-and-units))."
+      required: true
+      type: string
+    unit_of_measurement:
+      description: "Measurement unit ([VAR_UNIT](#variables-and-units))."
+      required: false
+      type: string
+      default: 'celsius'
+    min_temp:
+      description: "Minimum target temperature."
+      required: false
+      type: float
+      default: 7.
+    max_temp:
+      description: "Maximum target temperature."
+      required: false
+      type: float
+      default: 35.
+    lockable:
+      description: "Climate control can be locked."
+      required: false
+      type: bool
+      default: false
+
 covers:
  description: List of your covers.
  required: false
@ -146,11 +206,11 @@ covers:
      required: true
      type: string
    address:
-      description: "[Address](/components/lcn#lcn-addresses) of the module/group."
+      description: "[Address](#lcn-addresses) of the module/group."
      required: true
      type: string
    motor:
-      description: "Motor port ([MOTOR_PORT](/components/lcn#ports))."
+      description: "Motor port ([MOTOR_PORT](#ports))."
      required: true
      type: string

@ -164,11 +224,11 @@ lights:
      required: true
      type: string
    address:
-      description: "[Address](/components/lcn#lcn-addresses) of the module/group."
+      description: "[Address](#lcn-addresses) of the module/group."
      required: true
      type: string
    output:
-      description: "Light source ([OUTPUT_PORT](/components/lcn#ports), [RELAY_PORT](/components/lcn#ports))."
+      description: "Light source ([OUTPUT_PORT](#ports), [RELAY_PORT](#ports))."
      required: true
      type: string
    dimmable:
@ -192,15 +252,15 @@ sensors:
      required: true
      type: string
    address:
-      description: "[Address](/components/lcn#lcn-addresses) of the module/group."
+      description: "[Address](#lcn-addresses) of the module/group."
      required: true
      type: string
    source:
-      description: "Sensor source ([VARIABLE](/components/lcn#variables-and-units), [SETPOINT](/components/lcn#variables-and-units), [THRESHOLD](/components/lcn#variables-and-units), [S0_INPUT](/components/lcn#variables-and-units), [LED_PORT](/components/lcn#ports), [LOGICOP_PORT](/components/lcn#ports))."
+      description: "Sensor source ([VARIABLE](#variables-and-units), [SETPOINT](#variables-and-units), [THRESHOLD](#variables-and-units), [S0_INPUT](#variables-and-units), [LED_PORT](#ports), [LOGICOP_PORT](#ports))."
      required: true
      type: string
    unit_of_measurement:
-      description: "Measurement unit ([VAR_UNIT](/components/lcn#variables-and-units))."
+      description: "Measurement unit ([VAR_UNIT](#variables-and-units))."
      required: false
      type: string
      default: 'native'
@ -215,11 +275,11 @@ switches:
      required: true
      type: string
    address:
-      description: "[Address](/components/lcn#lcn-addresses) of the module/group."
+      description: "[Address](#lcn-addresses) of the module/group."
      required: true
      type: string
    output:
-      description: "Switch source ([OUTPUT_PORT](/components/lcn#ports), [RELAY_PORT](/components/lcn#ports))."
+      description: "Switch source ([OUTPUT_PORT](#ports), [RELAY_PORT](#ports))."
      required: true
      type: string
 {% endconfiguration %}
@ -232,7 +292,7 @@ Modules can be arranged in _segments_. Segments can be addressed by their numeri

 LCN Modules within the _same_ segment can be grouped by their group id (5..254) or 3 (= target all groups.)

-The LCN component allow the connection to more than one hardware coupler. In this case it has to be specified which hardware coupler should be used for addressing the specified module.
+The LCN component allows the connection to more than one hardware coupler. In this case it has to be specified which hardware coupler should be used for addressing the specified module.

 Whenever the address of a module or a group has to be specified, it can be addressed using one of the following syntaxes:

@ -271,7 +331,7 @@ The platforms and service calls use several predefined constants as parameters.
 | LOGICOP_PORT | `logicop1`, `logicop2`, `logicop3`, `logicop4` |
 | BINSENSOR_PORT | `binsensor1`, `binsensor2`, `binsensor3`, `binsensor4`, `binsensor5`, `binsensor6`, `binsensor7`, `binsensor8` |

-The [MOTOR_PORT](/components/lcn#ports) values specify which hardware relay configuration will be used:
+The [MOTOR_PORT](#ports) values specify which hardware relay configuration will be used:

 | Motor    | Relay on/off | Relay up/down |
 | :------: | :----------: | :-----------: |
@ -289,6 +349,8 @@ The [MOTOR_PORT](/components/lcn#ports) values specify which hardware relay conf
 | THRESHOLD | `thrs1`, `thrs2`, `thrs3`, `thrs4`, `thrs5`, `thrs2_1`, `thrs2_2`, `thrs2_3`, `thrs2_4`, `thrs3_1`, `thrs3_2`, `thrs3_3`, `thrs3_4`, `thrs4_1`, `thrs4_2`, `thrs4_3`, `thrs4_4` |
 | S0_INPUT | `s0input1`, `s0input2`, `s0input3`, `s0input4` |
 | VAR_UNIT | `native`, `°C`, `°K`, `°F`, `lux_t`, `lux_i`, `m/s`, `%`, `ppm`, `volt`, `ampere`, `degree` |
+| TIME_UNIT | `seconds`, `minutes`, `hours`, `days` |
+| RELVARREF | `current`, `prog` |

 ### {% linkable_title States %}:

@ -314,6 +376,17 @@ The `lcn` binary sensor platform allows the monitoring of the following [LCN](ht

 The binary sensor can be used in automation scripts or in conjunction with `template` platforms.

+### {% linkable_title Climate %}
+
+The `lcn` climate platform allows the control of the [LCN](http://www.lcn.eu) climate regulators.
+This platform depends on the correct configuration of the module's regulators which has to be done in the LCN-PRO programming software.
+You need to specify at least the variable for the current temperature and a setpoint variable for the target temperature. 
+If the control is set lockable, the regulator can be turned on/off. 
+
+<p class='note'>
+If you intend to leave the regulation to home assistant, you should consider using the [Generic Thermostat](climate.generic_thermostat) in conjuction with [LCN Sensor](#sensor) and [LCN Switch](#switch).
+</p>
+
 ### {% linkable_title Cover %}

 The `lcn` cover platform allows the control of [LCN](http://www.lcn.eu) relays which have been configured as motor controllers.
@ -349,3 +422,256 @@ The `lcn` switch platform allows the control of the following [LCN](http://www.l

 - Output ports
 - Relays
+
+## {% linkable_title Services %}
+
+In order to directly interact with the LCN system, and invoke commands which are not covered by the implemented platforms, the following service calls can be used.
+Refer to the (Services Calls)[/docs/scripts/service-calls] page for examples on how to use them. 
+
+### {% linkable_title Service `output_abs` %}
+
+Set absolute brightness of output port in percent.
+
+| Service data attribute | Optional | Description  | Values |
+| ---------------------- | -------- | -----------  | ------ |
+| `address` | No | [LCN address](#lcn-addresses) |
+| `output` | No | Output port of module | [OUTPUT_PORT](#ports) | 
+| `brightness` | Yes | Absolute brightness in percent | 0..100 | 
+| `transition` | Yes | Transition (ramp) time in seconds | 0..486 | 
+
+Example:
+
+```
+{"address": "myhome.0.7", "output": "output1", "brightness": 100, "transition": 0}
+```
+
+### {% linkable_title Service `output_rel` %}
+
+Set relative brightness of output port in percent.
+
+| Service data attribute | Optional | Description  | Values |
+| ---------------------- | -------- | -----------  | ------ |
+| `address` | No | [LCN address](#lcn-addresses) |
+| `output` | No | Output port of module | [OUTPUT_PORT](#ports) | 
+| `brightness` | Yes | Relative brightness in percent | -100..100 | 
+| `transition` | Yes | Transition (ramp) time in seconds | 0..486 | 
+
+Example:
+
+```
+{"address": "myhome.0.7", "output": "output1", "brightness": 30}
+```
+
+### {% linkable_title Service `output_toggle` %}
+
+Toggle output port.
+
+| Service data attribute | Optional | Description  | Values |
+| ---------------------- | -------- | -----------  | ------ |
+| `address` | No | [LCN address](#lcn-addresses) |
+| `output` | No | Output port of module | [OUTPUT_PORT](#ports) | 
+| `transition` | Yes | Transition (ramp) time in seconds | 0..486 | 
+
+Example:
+
+```
+{"address": "myhome.0.7", "output": "output1", "transition": 0}
+```
+
+### {% linkable_title Service `relays` %}
+
+Set the relays status. The relays states are defined as a string with eight characters.
+Each character represents the state change of a relay (1=on, 0=off, t=toggle, -=nochange).
+
+Example states:  `t---001-`
+
+| Service data attribute | Optional | Description  | Values |
+| ---------------------- | -------- | -----------  | ------ |
+| `address` | No | [LCN address](#lcn-addresses) |
+| `state` | No | Relay states as string |
+
+Example:
+
+```
+{"address": "myhome.0.7", "state": "t---001-"}
+```
+
+### {% linkable_title Service `led` %}
+
+Set the led status.
+
+| Service data attribute | Optional | Description  | Values |
+| ---------------------- | -------- | -----------  | ------ |
+| `address` | No | [LCN address](#lcn-addresses) |
+| `state` | No | Led state as string | [LED_STATE](#states) |
+
+Example:
+
+```
+{"address": "myhome.0.7", "led": "led6", "state": "blink"}
+```
+
+### {% linkable_title Service `var_abs` %}
+
+Set the absolute value of a variable or setpoint.
+If `value` is not defined, it is assumed to be 0.
+If `unit_of_measurement` is not defined, it is assumed to be `native`.
+
+| Service data attribute | Optional | Description  | Values |
+| ---------------------- | -------- | -----------  | ------ |
+| `address` | No | [LCN address](#lcn-addresses) |
+| `variable` | No | Variable name | [VARIABLE](#variables-and-units), [SETPOINT](#variables-and-units) |
+| `value` | Yes | Variable value | _any positive number_ |
+| `unit_of_measurement` | Yes | Variable unit | [VAR_UNIT](#variables-and-units) |
+
+Example:
+
+```
+{"address": "myhome.0.7", "variable": "var1", "value": 75, "unit_of_measurement": "%"}
+```
+
+<p class='note'>
+  Ensure that the LCN module is configured properly to provide acces to the defined variable.
+  Otherwise the module might show unexpected behaviors or return error messages.
+</p>
+
+### {% linkable_title Service `var_rel` %}
+
+Set the relative value of a variable or setpoint.
+If `value` is not defined, it is assumed to be 0.
+If `unit_of_measurement` is not defined, it is assumed to be `native`.
+
+| Service data attribute | Optional | Description  | Values |
+| ---------------------- | -------- | -----------  | ------ |
+| `address` | No | [LCN address](#lcn-addresses) |
+| `variable` | No | Variable name | [VARIABLE](#variables-and-units), [SETPOINT](#variables-and-units), [THRESHOLD](#variables-and-units) |
+| `value` | Yes | Variable value | _any positive or negative number_ |
+| `unit_of_measurement` | Yes | Variable unit | [VAR_UNIT](#variables-and-units) |
+
+Example:
+
+```
+{"address": "myhome.0.7", "variable": "var1", "value": 10, "unit_of_measurement": "%"}
+```
+
+<p class='note'>
+  Ensure that the LCN module is configured properly to provide acces to the defined variable.
+  Otherwise the module might show unexpected behavior or return error messages.
+</p>
+
+### {% linkable_title Service `var_reset` %}
+
+Reset value of variable or setpoint.
+
+| Service data attribute | Optional | Description  | Values |
+| ---------------------- | -------- | -----------  | ------ |
+| `address` | No | [LCN address](#lcn-addresses) |
+| `variable` | No | Variable name | [VARIABLE](#variables-and-units), [SETPOINT](#variables-and-units) |
+
+Example:
+
+```
+{"address": "myhome.0.7", "variable": "var1"}
+```
+
+<p class='note'>
+  Ensure that the LCN module is configured properly to provide acces to the defined variable.
+  Otherwise the module might show unexpected behavior or return error messages.
+</p>
+
+### {% linkable_title Service `lock_regulator` %}
+
+Locks a regulator setpoint.
+If `state` is not defined, it is assumed to be `False`.
+
+| Service data attribute | Optional | Description  | Values |
+| ---------------------- | -------- | -----------  | ------ |
+| `address` | No | [LCN address](#lcn-addresses) |
+| `setpoint` | No | Setpoint name | [SETPOINT](#variables-and-units) |
+| `state` | Yes | Lock state | true, false |
+
+Example:
+
+```
+{"address": "myhome.0.7", "setpoint": "r1varsetpoint", "state": true}
+```
+
+### {% linkable_title Service `send_keys` %}
+
+Send keys (which executes bound commands).
+The keys attribute is a string with one or more key identifiers. Example: `a1a5d8`
+If `state` is not defined, it is assumed to be `hit`.
+The command allow the sending of keys immediately or deferred. For a deferred sendig the attributes `time` and `time_unit` have to be specified. For deferred sending the only key state allowed is `hit`.
+If `time_unit` is not defined, it is assumed to be `seconds`.
+
+| Service data attribute | Optional | Description  | Values |
+| ---------------------- | -------- | -----------  | ------ |
+| `address` | No | [LCN address](#lcn-addresses) |
+| `keys` | No | Keys string |
+| `state` | Yes | Keys state | [SENDKEYCOMMANDS](#states) |
+| `time` | Yes | Deferred time | 0.. |
+| `time_unit` | Yes | Time unit | [TIME_UNIT](#variables-and-units)
+
+Examples:
+
+```
+{"address": "myhome.0.7", "keys": "a1a5d8", "state": "hit"}
+{"address": "myhome.0.7", "keys": "a1a5d8", "time": 5, "time_unit": "s"}
+```
+
+### {% linkable_title Service `lock_keys` %}
+
+Locks keys.
+If table is not defined, it is assumend to be table `a`.
+The key lock states are defined as a string with eight characters. Each character represents the state change of a key lock (1=on, 0=off, t=toggle, -=nochange).
+The command allows the locking of keys for a specified time period. For a time period the attributes `time` and `time_unit` have to be specified. For a time period only tabley `a` is allowed.
+If `time_unit` is not defined, it is assumed to be `seconds`.
+
+| Service data attribute | Optional | Description  | Values |
+| ---------------------- | -------- | -----------  | ------ |
+| `address` | No | [LCN address](#lcn-addresses) |
+| `table` | Yes | Table with keys to lock |
+| `state` | No | Key lock states as string | [SENDKEYCOMMANDS](#states) |
+| `time` | Yes | Time period to lock | 0.. |
+| `time_unit` | Yes | Time unit | [TIME_UNIT](#variables-and-units)
+
+Examples:
+
+```
+{"address": "myhome.0.7", "table": "a", "state": "1---t0--"}
+{"address": "myhome.0.7", "state": "1---t0--", "time": 10, "time_unit": "s"}
+```
+
+### {% linkable_title Service `dyn_text` %}
+
+Send dynamic text to LCN-GTxD displays.
+The displays support four rows for text messages.
+Each row can be set independently and can store up to 60 characters (encoded in UTF-8).
+
+
+| Service data attribute | Optional | Description  | Values |
+| ---------------------- | -------- | -----------  | ------ |
+| `address` | No | [LCN address](#lcn-addresses) |
+| `row` | No | Text row 1..4 |
+| `text` | No | Text to send for the specified row |
+
+Example:
+
+```
+{"address": "myhome.0.7", "row": 1, "text": "text in row 1"}
+```
+
+### {% linkable_title Service `pck` %}
+
+Send arbitrary PCK command. Only the command part of the PCK command has to be specified in the `pck` string.
+
+| Service data attribute | Optional | Description  | Values |
+| ---------------------- | -------- | -----------  | ------ |
+| `address` | No | [LCN address](#lcn-addresses) |
+| `pck` | No | PCK command |
+
+Example:
+
+```
+{"address": "myhome.0.7", "pck": "PIN4"}
+```
--- a/source/_components/locative.md
+++ b/source/_components/locative.md
@ -17,7 +17,7 @@ redirect_from:
 ---

 <p class='note'>
-Locative is no longer under active development. <a href="https://blog.locative.io/bye-everyone-df01871fe949">Read more here</a>
+Locative is no longer under active development.
 </p>

 This platform allows you to detect presence using [Locative](https://my.locative.io/). Locative is an open source app for [iOS](https://github.com/LocativeHQ/ios-app) and [Android](https://github.com/LocativeHQ/Locative-Android) that allows users to set up a `GET` or `POST` request when a geofence is entered or exited. This can be configured with Home Assistant to update your location.
@ -34,5 +34,3 @@ To configure Locative, you must set it up via the integrations panel in the conf
 </p>

 When you enter a geofence, your location name in Home Assistant will be set to the name of the geofence in Locative. When you exit a geofence, your location name in Home Assistant will be set to "not home".
-
-To use Locative in combination with another device tracker, such as [Nmap](/components/device_tracker.nmap_tracker/) or [Netgear](/components/device_tracker.netgear/), fill in the `mac` field to the Locative entry in `known_devices.yaml` with the MAC address of the device you want to track. The state of the device will be determined by the source that reported last.
--- a/source/_components/mcp23017.markdown
+++ b/source/_components/mcp23017.markdown
@ -0,0 +1,121 @@
+---
+layout: page
+title: "MCP23017 I2C GPIO expander"
+description: "Instructions on how to integrate the MCP23017 GPIO pin expander with I2C interface into Home Assistant."
+date: 2019-04-14 07:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: raspberry-pi.png
+ha_category:
+  - DIY
+  - Binary Sensor
+  - Switch
+ha_release: 0.94
+ha_iot_class: Local Polling
+---
+
+The `mcp23017` component is the base for all related mcp23017 platforms in Home Assistant. There is no setup needed for the component itself, for the platforms please check their corresponding sections.
+
+For more details about the MCP23017 I2C I/O port expander you can find its datasheet here: [MCP23017](https://www.microchip.com/wwwproducts/en/MCP23017).
+
+## {% linkable_title Binary Sensor %}
+
+The `mcp23017` binary sensor platform allows you to read sensor values from the I/O pins of your [MCP23017 I2C I/O expander](https://www.adafruit.com/product/732).
+
+The pin numbers are from 0 to 15 where: 0-7 correspond to port A (A1-A8) and 8-15 to port B (B1-B8).
+
+### {% linkable_title Configuration %}
+
+To use the I/O pins of an mcp23017 connected to an I2C bus of your Raspberry Pi as binary sensors, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+binary_sensor:
+  - platform: mcp23017
+    i2c_address: 0x20
+    pins:
+      0: PIR Office
+      1: PIR Bedroom
+```
+
+{% configuration %}
+i2c_address:
+  description: i2c address of MCP23017 chip.
+  required: false
+  type: integer
+  default: "`0x20`"
+pins:
+  description: List of used pins.
+  required: true
+  type: map
+  keys:
+    "pin: name":
+      description: The pin numbers (from 0 to 15) and corresponding names.
+      required: true
+      type: [integer, string]
+scan_interval:
+  description: Interval to scan for sensor state changes in seconds.
+  required: false
+  type: integer
+  default: 15
+invert_logic:
+  description: If `true`, inverts the output logic to ACTIVE LOW.
+  required: false
+  type: boolean
+  default: "`false` (ACTIVE HIGH)"
+pull_mode:
+  description: >
+    Type of internal pull resistor to use.
+    Options are `UP` - pull-up resistor and `DOWN` - pull-down resistor.
+  required: false
+  type: string
+  default: "`UP`"
+{% endconfiguration %}
+
+<p class='note warning'>
+  MCP23017 only has internal pull-up resistors, if you want to use pull-down you will have to wire your own pull-down resistors.
+</p>
+
+## {% linkable_title Switch %}
+
+The `mcp23017` switch platform allows you to write to the I/O pins of your [MCP23017 I2C I/O expander](https://www.adafruit.com/product/732).
+
+The pin numbers are from 0 to 15 where: 0-7 correspond to port A (A1-A8) and 8-15 to port B (B1-B8).
+
+### {% linkable_title Configuration %}
+
+To use the I/O pins of an mcp23017 connected to an I2C bus of your Raspberry Pi as switches, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+switch:
+  - platform: mcp23017
+    i2c_address: 0x20
+    pins:
+      11: Fan Office
+      12: Light Desk
+```
+
+{% configuration %}
+i2c_address:
+  description: i2c address of MCP23017 chip.
+  required: false
+  type: integer
+  default: "`0x20`"
+ports:
+  description: Array of used pins.
+  required: true
+  type: list
+  keys:
+    port:
+      description: The pin numbers (from 0 to 15) and corresponding names.
+      required: true
+      type: [integer, string]
+invert_logic:
+  description: If true, inverts the output logic to ACTIVE LOW.
+  required: false
+  default: false
+  type: boolean
+{% endconfiguration %}
--- a/source/_components/owntracks.markdown
+++ b/source/_components/owntracks.markdown
@ -24,17 +24,9 @@ By default the integration will listen for incoming messages from OwnTracks via
 <iframe width="560" height="315" src="https://www.youtube.com/embed/UieAQ8sC6GY" frameborder="0" allowfullscreen></iframe>
 </div>

-### {% linkable_title Configuring the component %}
+## {% linkable_title Configuration %}

-1. Open the Home Assistant frontend
-1. Open Settings -> integrations
-1. If you see an Owntracks component under 'Configured', delete it.
-   - Click on it.
-   - Click on the trashcan icon in the upper right corner.
-1. Now, look for Owntracks in 'Setup new integration' and click on CONFIGURE.
-1. The login credentials and configuration for owntracks will be presented to you.
-   in a popup window. You will need these in the configuration for the app as mentioned below.
-1. Save these credentials somewhere, as there is no way to get it back at a later point in time if it is lost, besides         repeating step 1-5
+To configure OwnTracks, you must set it up via the integrations panel in the configuration screen. This will give you the webhook URL to use during mobile device configuration (below).

 ### {% linkable_title Configuring the app - Android %}

@ -43,7 +35,7 @@ By default the integration will listen for incoming messages from OwnTracks via
 In the OwnTracks app, open sidebar and click on preferences, then on connection. Change the following settings:

 - Mode: Private HTTP
- - Host: `<URL given to you when setting up the integration above>`
+ - Host: `<URL given to you when setting up the integration>`
 - Identification:
   - Username: `<Username>`
   - Password: Can be left blank.
@ -167,19 +159,3 @@ By default, any Owntracks user connected to Home Assistant can export their wayp

 1. The configuration variable `waypoints` can be set to `false` which will disable importing waypoints for all users.
 2. The configuration variable `waypoint_whitelist` can contain a list of users who are allowed to import waypoints.
-
-## {% linkable_title Using Owntracks with other device trackers %}
-
-Owntracks can also be used with other device trackers, such as [Nmap](/components/device_tracker.nmap_tracker/) or [Netgear](/components/device_tracker.netgear/). To do this, fill in the `mac` field to the Owntracks entry in `known_devices.yaml` with the MAC address of the device you want to track. This way the state of the device will be determined by the source that reported last. The naming convention for known device list is `<username>_<device-id>` and could be set in app configuration. More details about this config can found in [device tracker](/components/device_tracker/).
-
-An example showing the inclusion of the `mac` field for multiple component tracking. The `mac` field will need to be added to the `owntracks` device and will enable tracking by all components that track via the `mac` address.
-
-```yaml
-USERNAME_DEVICE_ID:
-  name: Friendly Name
-  mac: EA:AA:55:E7:C6:94
-  picture: https://www.home-assistant.io/images/favicon-192x192.png
-  gravatar: test@example.com
-  track: true
-  hide_if_away: false
-```
--- a/source/_components/plex.markdown
+++ b/source/_components/plex.markdown
@ -93,41 +93,18 @@ You can customize the Plex component by adding any of the variables below to you
 # Example configuration.yaml entry
 media_player:
  - platform: plex
-    entity_namespace: 'plex'
-    include_non_clients: true
-    scan_interval: 5
    show_all_controls: false
-    use_custom_entity_ids: true
    use_episode_art: true
    remove_unavailable_clients: true
    client_remove_interval: 600
 ```

 {% configuration %}
-entity_namespace:
-  description: "Prefix for entity ID's. Useful when using overlapping components (ex. Apple TV and Plex components when you have Apple TV's you use as Plex clients). Go from _media_player.playroom2_ to _media_player.plex_playroom_"
-  required: false
-  type: string
-include_non_clients:
-  description: "Display non-recontrollable clients (ex. remote clients, PlexConnect Apple TV's)."
-  required: false
-  default: false
-  type: boolean
-scan_interval:
-  description: "Amount in seconds in between polling for device’s current activity."
-  required: false
-  default: 10
-  type: int
 show_all_controls:
  description: "Forces all controls to display. Ignores dynamic controls (ex. show volume controls for client A but not for client B) based on detected client capabilities. This option allows you to override this detection if you suspect it to be incorrect."
  required: false
  default: false
  type: boolean
-use_custom_entity_ids:
-  description: "Name Entity ID's by client ID's instead of friendly names. HA assigns entity ID's on a first come first serve basis.  When you have identically named devices connecting (ex. media_player.plex_web_safari, media_player.plex_web_safari2), you can't reliably distinguish and or predict which device is which.  This option avoids this issue by using unique client ID's (ex. media_player.dy4hdna2drhn)."
-  required: false
-  default: false
-  type: boolean
 use_episode_art:
  description: Display TV episode art instead of TV show art.
  required: false
--- a/source/_components/remote_rpi_gpio.markdown
+++ b/source/_components/remote_rpi_gpio.markdown
@ -0,0 +1,127 @@
+---
+layout: page
+title: "Remote Raspberry Pi GPIO"
+description: "Instructions on how to integrate the GPIO capability of a Remote Raspberry Pi into Home Assistant."
+date: 2019-02-20 19:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: raspberry-pi.png
+ha_category:
+  - DIY
+  - Binary Sensor
+  - Switch
+ha_release: 0.94 
+ha_iot_class: Local Push
+---
+
+The `rpi_gpio` component is the base for all related GPIO platforms in Home Assistant. There is no setup needed for the component itself, for the platforms please check their corresponding pages.
+
+## {% linkable_title Binary Sensor %}
+
+The `remote_rpi_gpio` binary sensor platform allows you to read sensor values of the GPIOs of a [Remote Raspberry Pi](https://www.raspberrypi.org/).
+
+To use your Remote Raspberry Pi's GPIO in your installation, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+binary_sensor:
+  - platform: remote_rpi_gpio
+    address: <address of remote pi>
+    ports:
+      11: PIR Office
+      12: PIR Bedroom
+      
+switch:
+  - platform: remote_rpi_gpio
+    address: <address of remote pi>
+    ports:
+      4: Garage Relay
+```
+
+{% configuration %}
+address:
+  description: IP Address of remote Raspberry Pi
+  required: true
+  type: string
+ports:
+  description: List of used ports.
+  required: true
+  type: map
+  keys:
+    "port: name":
+      description: The port numbers (BCM mode pin numbers) and corresponding names.
+      required: true
+      type: string
+invert_logic:
+  description: If `true`, inverts the output logic
+  required: false
+  type: boolean
+  default: "`false` (ACTIVE HIGH)"
+pull_mode:
+  description: >
+    Type of internal pull resistor to use.
+    Options are `UP` - pull-up resistor and `DOWN` - pull-down resistor.
+    Pull-Up defaults to active LOW and Pull-down defaults to active HIGH.  This can be adjusted with invert_logic
+  required: false
+  type: string
+  default: "`UP`"
+{% endconfiguration %}
+
+For more details about the GPIO layout, visit the Wikipedia [article](https://en.wikipedia.org/wiki/Raspberry_Pi#GPIO_connector) about the Raspberry Pi.
+
+## {% linkable_title Switch %}
+
+The `remote_rpi_gpio` switch platform allows you to control the GPIOs of a [Remote Raspberry Pi](https://www.raspberrypi.org/).
+
+To use your Remote Raspberry Pi's GPIO in your installation, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+switch:
+  - platform: remote_rpi_gpio
+    address: 192.168.0.123
+    ports:
+      11: Fan Office
+      12: Light Desk
+```
+
+{% configuration %}
+address:
+  description: IP Address of remote Raspberry Pi
+  required: true
+  type: string
+ports:
+  description: Array of used ports.
+  required: true
+  type: list
+  keys:
+    port:
+      description:  Port numbers and corresponding names (GPIO #).
+      required: true
+      type: [integer, string]
+invert_logic:
+  description: If true, inverts the output logic to ACTIVE LOW.
+  required: false
+  default: false
+  type: boolean
+{% endconfiguration %}
+
+For more details about the GPIO layout, visit the Wikipedia [article](https://en.wikipedia.org/wiki/Raspberry_Pi#GPIO_connector) about the Raspberry Pi.
+
+<p class='note warning'>
+Note that a pin managed by HASS is expected to be exclusive to HASS.
+</p>
+
+A common question is what does Port refer to, this number is the actual GPIO #, not the pin #.
+For example, if you have a relay connected to pin 11 its GPIO # is 17.
+
+```yaml
+# Example configuration.yaml entry
+switch:
+  - platform: remote_rpi_gpio
+    address: 192.168.0.123
+    ports:
+      17: Speaker Relay
+```
--- a/source/_components/repetier.markdown
+++ b/source/_components/repetier.markdown
@ -0,0 +1,111 @@
+---
+layout: page
+title: Repetier-Server Component
+description: "Instructions how to add Repetier-Server sensors to Home Assistant."
+date: 2019-05-01
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: repetier.png
+ha_category:
+  - Hub
+  - Sensor
+featured: false
+ha_release: 0.94
+ha_iot_class: Local Polling
+---
+
+[Repetier-Server](https://www.repetier-server.com/) is a 3D printer/CNC server, able to control multiple devices on the same server.
+This component handles the main integration to the server.
+
+There is currently support for the following device types within Home Assistant:
+
+- Sensor
+
+## {% linkable_title Configuration %}
+
+```yaml
+repetier:
+  - host: REPETIER_HOST
+    api_key: YOUR_API_KEY
+```
+
+{% configuration %}
+repetier:
+  type: list
+  required: true
+  keys:
+    host:
+      description: The host IP or hostname of your Repetier-Server.
+      required: true
+      type: string
+    api_key:
+      description: API-key for the user used to connect to Repetier-Server
+      required: true
+      type: string
+    port:
+      description: The port used to connect to the host
+      required: false
+      type: integer
+      default: 3344
+    sensors:
+      description: Configuration for the sensors.
+      required: false
+      type: map
+      keys:
+        monitored_conditions:
+          description: The sensors to activate.
+          type: list
+          default: all
+          keys:
+            "current_state":
+              description: Text of current state.
+            "extruder_temperature":
+              description: Temperatures of all available extruders. These will be displayed as `printer_name_extruder_N`.
+            "bed_temperature":
+              description: Temperatures of all available heated beds. These will be displayed as `printer_name_bed_N`.
+            "chamber_temperature":
+              description: Temperatures of all available heated chambers. These will be displayed as `printer_name_chamber_N`.
+            "current_job":
+              description: Returns percentage done of current job in state, and current job information as attributes.
+            "job_start":
+              description: Start timestamp of job start.
+            "job_end":
+              description: Estimated job end timestamp.
+{% endconfiguration %}
+
+Example with multiple Repetier Servers:
+
+```yaml
+repetier:
+  - host: REPETIER_HOST
+    api_key: YOUR_API_KEY
+    sensors:
+      monitored_conditions:
+        - 'current_state'
+        - 'current_job'
+  - host: REPETIER_HOST
+    api_key: YOUR_API_KEY
+    port: 3344
+```
+
+If the Repetier-Server host is equipped with a web camera it is possible to add this as well.
+
+```yaml
+camera:
+  - platform: mjpeg
+    name: Repetier
+    still_image_url: http://YOUR_REPETIER_HOST_IP:8080/?action=snapshot
+    mjpeg_url: http://YOUR_REPETIER_HOST_IP:8080/?action=stream
+```
+
+### {% linkable_title Retrieve API-key %}
+
+To generate the needed API-key do the following:
+
+* Go to your Repetier Server web-console
+* Push the settings icon (the gear icon)
+* Select User Profiles.
+* Create a new user, deselect all options and click Create User.
+* Edit the newly created user and take note of the API-key for this user, that's the one to use in the Home Assistant Settings
--- a/source/_components/smarthab.markdown
+++ b/source/_components/smarthab.markdown
@ -0,0 +1,50 @@
+---
+layout: page
+title: "SmartHab"
+description: "Instructions on how to integrate SmartHab devices into Home Assistant"
+date: 2019-02-13 08:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: smarthab.png
+ha_release: 0.94
+ha_category:
+  - Hub
+  - Cover
+  - Light
+ha_iot_class: Cloud Polling
+---
+
+If your home is fitted with [SmartHab](http://www.smarthab.fr/en/home/)'s 
+devices and you have access to their app-based services, you will be able 
+to control your lights and shutters with the SmartHab component for Home 
+Assistant.
+
+Once you have added a `smarthab` entry to your configuration, your supported 
+devices will automatically be discovered and made available on your dashboard.
+
+<p class='note warning'>
+  To prevent being automatically logged out of your SmartHab mobile app, you
+  might want to create a secondary user in the app's settings and grant it
+  access to your home. You can then configure the component using this account's
+  credentials. This is also more secure, as this user should be less priviledged.
+</p>
+
+```yaml
+# Example configuration.yaml entry
+smarthab:
+  email: EMAIL_ADDRESS
+  password: PASSWORD
+```
+
+{% configuration %}
+email:
+  description: The email address of your SmartHab account.
+  required: true
+  type: string
+password:
+  description: The SmartHab account's password.
+  required: true
+  type: string
+{% endconfiguration %}
--- a/source/_components/solax.markdown
+++ b/source/_components/solax.markdown
@ -0,0 +1,57 @@
+---
+layout: page
+title: "Solax Sensor"
+description: "Instructions on how to integrate Solax sensor within Home Assistant."
+date: 2019-03-31 04:20
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: solax-logo.png
+ha_category:
+  - Energy
+  - Sensor
+ha_release: 0.94
+ha_iot_class: Local Polling
+---
+
+The `solax` component connects home-assistant to Solax solar power inverters. Solax inverters may be connected to a home Wi-Fi network and expose a REST API. This component retrieves information such as photovoltaic power production, battery levels and power, and how much power is being fed back into the grid.
+
+## {% linkable_title Configuration %}
+
+To use the Solax sensors in your installation, add the following to your configuration.yaml file:
+
+```yaml
+# Example configuration.yaml entry
+sensor:
+  - platform: solax
+    ip_address: IP_ADDRESS
+```
+
+{% configuration %}
+ip_address:
+  description: The IP address of your Solax system.
+  required: true
+  type: string
+{% endconfiguration %}
+
+### {% linkable_title Optional template sensor %}
+
+If you would like to convert the values from multiple panels or view the total power the house is using, you can use the [template platform](/components/sensor.template/).
+
+{% raw %}
+```yaml
+# Example configuration.yaml entry for template platform
+sensors:
+- platform: template
+  sensors:
+    total_pv_power:
+      friendly_name: "Total PV Power"
+      unit_of_measurement: 'W'
+      value_template: "{{ (states('sensor.pv1_power') | float) + (states('sensor.pv2_power') | float) }}"
+    load_power:
+      friendly_name: "Load Power"
+      unit_of_measurement: 'W'
+      value_template: "{{ (states('sensor.power_now') | float) - (states('sensor.exported_power') | float) }}"
+```
+{% endraw %}
--- a/source/_components/spaceapi.markdown
+++ b/source/_components/spaceapi.markdown
@ -114,6 +114,20 @@ sensors:
      type: entity_id
 {% endconfiguration %}

+The list of sensors can be any sensor, not just temperature or humidity.
+
+## {% linkable_title Sensor specific location %}
+
+The [SpaceAPI specification](https://spaceapi.io/pages/docs.html) requires every sensor to provide a location. 
+In order to set a sensor specific location do the following steps: 
+
+1. Go to Configuration -> Customization
+2. Select the sensor entity
+3. Pick "Other" from the attribute override pulldown
+4. Set the attribute name to location and the attribute value to your desired location
+
+If no location is set, the location defined in the HA config is used.
+
 ## {% linkable_title Examples %}

 In this section you find some real-life examples of how to use this component.
--- a/source/_components/ssdp.markdown
+++ b/source/_components/ssdp.markdown
@ -0,0 +1,33 @@
+---
+layout: page
+title: "SSDP"
+description: "Discover integrations on the network using the SSDP protocol."
+date: 2019-06-02 18:50
+sidebar: true
+comments: false
+sharing: true
+footer: true
+ha_category:
+  - Network
+ha_release: 0.94
+---
+
+The `ssdp` integration will scan the network for supported devices and services. Discovered integrations will show up in the discovered section on the integrations page in the config panel.
+
+Integrations can opt-in to be found by adding [an SSDP section](https://developers.home-assistant.io/docs/en/next/creating_integration_manifest.html#ssdp) to their manifest.json.
+
+## {% linkable_title Configuration %}
+
+To integrate this into Home Assistant, add the following section to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+ssdp:
+```
+
+## {% linkable_title Discovered Integrations %}
+
+The following integrations are automatically discovered by the SSDP integration:
+
+ - Deconz
+ - Philips Hue
--- a/source/_components/sun.markdown
+++ b/source/_components/sun.markdown
@ -73,3 +73,4 @@ which event (sunset or sunrise) and the offset.
 | `next_midnight` | Date and time of the next solar midnight (in UTC).
 | `elevation` |  Solar elevation. This is the angle between the sun and the horizon. Negative values mean the sun is below the horizon.
 | `azimuth` | Solar azimuth. The angle is shown clockwise from north.
+| `rising` | True if the Sun is currently rising, after solar midnight and before solar noon.
--- a/source/_components/watson_tts.markdown
+++ b/source/_components/watson_tts.markdown
@ -0,0 +1,108 @@
+---
+layout: page
+title: "Watson TTS"
+description: "Instructions on how to setup IBM Watson TTS with Home Assistant."
+date: 2019-04-22 12:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: watson_tts.png
+ha_category:
+  - Text-to-speech
+ha_release: 0.94
+---
+
+The `watson_tts` text-to-speech platform that works with [IBM Watson Cloud](https://www.ibm.com/watson/services/text-to-speech/) to create the spoken output.
+Polly is a paid service via IBM Cloud but there is a decent [free tier](https://www.ibm.com/cloud/watson-text-to-speech/pricing) which offers 10000 free characters every month.
+
+## {% linkable_title Setup %}
+
+For supported formats and voices please go to [IBM Cloud About section](https://cloud.ibm.com/docs/services/text-to-speech?topic=text-to-speech-about#about).
+
+To get started please read the [Getting started tutorial](https://cloud.ibm.com/docs/services/text-to-speech?topic=text-to-speech-gettingStarted#gettingStarted).
+
+## {% linkable_title Configuration %}
+
+To configure Watson TTS, add the following lines to your `configuration.yaml`:
+
+```yaml
+# Example configuration.yaml entry
+tts:
+  - platform: watson_tts
+    watson_apikey: YOUR_GENERATED_APIKEY
+```
+
+You can get these tokens after you generated the credentials on the IBM Cloud console:
+
+<p class='img'>
+  <img src='{{site_root}}/images/screenshots/watson_tts_screen.png' />
+</p>
+
+{% configuration %}
+watson_url:
+  description: "The endpoint to which the service will connect."
+  required: false
+  type: string
+  default: https://stream.watsonplatform.net/text-to-speech/api
+watson_apikey:
+  description: "Your secret apikey generated on the IBM Cloud admin console."
+  required: true
+  type: string
+voice:
+  description: Voice name to be used.
+  required: false
+  type: string
+  default: en-US_AllisonVoice
+output_format:
+  description: "Override the default output format. Supported formats: `audio/flac`, `audio/mp3`, `audio/mpeg`, `audio/ogg`, `audio/ogg;codecs=opus`, `audio/ogg;codecs=vorbis`, `audio/wav`"
+  required: false
+  type: string
+  default: audio/mp3
+{% endconfiguration %}
+
+## {% linkable_title Usage %}
+
+Say to all `media_player` device entities:
+
+```yaml
+- service: tts.watson_tts_say
+  data_template:
+    message: 'Hello from Watson'
+```
+
+or
+
+```yaml
+- service: tts.watson_tts_say
+  data_template:
+    message: >
+      <speak>
+          Hello from Watson
+      </speak>
+```
+
+Say to the `media_player.living_room` device entity:
+
+```yaml
+- service: tts.watson_tts_say
+  data_template:
+    entity_id: media_player.living_room
+    message: >
+      <speak>
+          Hello from Watson
+      </speak>
+```
+
+Say with break:
+
+```yaml
+- service: tts.watson_tts_say
+  data_template:
+    message: >
+      <speak>
+          Hello from
+          <break time=".9s" />
+          Watson
+      </speak>
+```
--- a/source/_components/zeroconf.markdown
+++ b/source/_components/zeroconf.markdown
@ -7,13 +7,14 @@ sidebar: true
 comments: false
 sharing: true
 footer: true
-logo: avahi.png
 ha_category:
  - Network
 ha_release: 0.18
 ---

-The `zeroconf` component exposes your Home Assistant to the local network using [Zeroconf](https://en.wikipedia.org/wiki/Zero-configuration_networking). Zeroconf is also sometimes known as Bonjour, Rendezvous, and Avahi.
+The `zeroconf` integration will scan the network for supported devices and services. Discovered integrations will show up in the discovered section on the integrations page in the config panel. It will also make Home Assistant discoverable for other services in the network. Zeroconf is also sometimes known as Bonjour, Rendezvous, and Avahi.
+
+Integrations can opt-in to be found by adding either [a Zeroconf section](https://developers.home-assistant.io/docs/en/next/creating_integration_manifest.html#zeroconf) or [a HomeKit section](https://developers.home-assistant.io/docs/en/next/creating_integration_manifest.html#homekit) to their manifest.json.

 ## {% linkable_title Configuration %}

@ -24,24 +25,12 @@ To integrate this into Home Assistant, add the following section to your `config
 zeroconf:
 ```

-The registration will include meta-data about the Home Assistant instance, including a base URL that can be used to access Home Assistant, the currently running Home Assistant version, and whether an API password is needed to access the instance. The examples below show two ways to retrieve the details for testing.
+## {% linkable_title Discovered Integrations %}

-```bash
-$ avahi-browse -alr
-+ eth0 IPv4 Home                              _home-assistant._tcp local
-= eth0 IPv4 Home                              _home-assistant._tcp local
-   hostname = [Home._home-assistant._tcp.local]
-   address = [192.168.0.70]
-   port = [8123]
-   txt = ["base_url=http://192.168.0.70:8123" "requires_api_password=true" "version=0.41.0"]
-```
+The following integrations are automatically discovered by the SSDP integration:

-```bash
-$ avahi-discover
-Browsing domain 'local' on -1.-1 ...
-Browsing for services of type '_home-assistant._tcp' in domain 'local' on 4.0 ...
-Found service 'Home' of type '_home-assistant._tcp' in domain 'local' on 4.0.
-Service data for service 'Home' of type '_home-assistant._tcp' in domain 'local' on 4.0:
-   Host Home._home-assistant._tcp.local (192.168.0.70), port 8123, TXT data:
-['requires_api_password=true', 'base_url=http://192.168.0.70:8123', 'version=0.41.0']
-```
+ - Axis
+ - ESPHome
+ - HomeKit Controller
+ - LIFX
+ - Trådfri
--- a/source/_posts/2019-06-05-release-94.markdown
+++ b/source/_posts/2019-06-05-release-94.markdown
@ -0,0 +1,650 @@
+---
+layout: post
+title: "0.94: TBD - update date"
+description: "TO DO."
+date: 2019-05-29 04:11:03
+date_formatted: "June 5, 2019"
+author: Paulus Schoutsen
+author_twitter: balloob
+comments: true
+categories: Release-Notes
+og_image: /images/blog/2019-06-release-94/google-ui.png
+---
+
+<a href='/components/#version/0.94'><img src='/images/blog/2019-06-release-94/components.png' style='border: 0;box-shadow: none;'></a>
+
+It is time for the 0.94 release and there is some seriously good stuff in this release. We're working hard on polishing everything and getting ready for the big Home Assistant 1.0 release. And we're getting closer. So close actually, that this is the first release that can be installed and configured without touching a text editor! Onboard, configure integrations, manage automations and scripts all from the UI.
+
+<div class="videoWrapper">
+  <iframe width="853" height="480" src="https://www.youtube-nocookie.com/embed/mTFX-_jB2xw" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
+</div>
+
+This milestone has been achieved thanks to the hard work by [@emontnemery] who contributed the ability to store the core config in storage: name, location, unit system, time zone. We still allow users to store their core configuration in `configuration.yaml`, which will take precedent when defined. This means that it is a non-breaking change. Core config is now set during onboarding and can be edited in the general page of the config panel.
+
+Another cool new feature is the total revamp of how you manage which entities are exposed to Google Assistant via Home Assistant Cloud. From the cloud UI you can now click "Manage Entities" and you are brought to the Google Assistant entity manager. From here you can enable which entities are exposed and, if you deem appropriate, choose to disable the two factor authentication on your garage door (the asking for a pin).
+
+<p class='img'>
+<img src='/images/blog/2019-06-release-94/google-ui.png' alt='Screenshot of the new user interface to manage which entities are exposed to Google Assistant.'>
+Screenshot of the new user interface to manage which entities are exposed to Google Assistant.
+</p>
+
+<!--more-->
+
+## {% linkable_title Discovery %}
+
+Discovery has been mordernized thanks to [@Kane610] and with the input from [@Jc2k]. Each integration is now able to specify how they can be discovered in their manifest, and the new `zeroconf` and `ssdp` integrations will do the rest. The new discovery is non-obtrusive: no devices are set up without approval by the user. Instead, you will need to approve each discovered integration. You can find them in the discovered section of the integrations page in the config. Only a handful of integrations have been migrated to the new approach in this release: Hue, LIFX, Deconz, Trådfri, Axis, ESPHome, HomeKit Controller.
+
+The new discovery is now part of the default config. If you are not using the default config, add `ssdp:` and `zeroconf:` to your configuration.yaml.
+
+## {% linkable_title Deprecating Python 3.5 support %}
+
+This release has deprecated support for the almost 4 year old version 3.5 of Python. The first Home Assistant release after August 1 will drop support. This is part of our newly adopted [Python support approach](https://github.com/home-assistant/architecture/blob/master/adr/0002-minimum-supported-python-version.md).
+
+This will only impact you if you are running a custom installation of Home Assistant. This will not impact anyone using Hass.io or Docker. If you are using hassbian, you can upgrade Python by following [these instructions](https://github.com/home-assistant/hassbian-scripts/blob/dev/docs/suites/python.md).
+
+## {% linkable_title Modernizing the device tracker %}
+
+This release also introduces a long overdue overhaul of how the device tracker works. We are introducing this overhaul piece by piece, focusing first on device tracker platforms that push their updates to Home Assistant: mobile app, OwnTracks, GeoFency, GPSLogger and Locative.
+
+These integrations will no longer use `known_devices.yaml` but instead use entities, like all other integrations in Home Assistant. You can change the name and entity ID via the UI. It is no longer posible to merge the devices with other device tracker entities. This was flaky at best. You should now use the new person integration for this.
+
+## {% linkable_title Improved hass.io builds %}
+
+We have been working hard on improving Hass.io builds. It's our goal to make the update process faster and more predictable. A build can now be online in as little as 30 minutes after a new release has been tagged. This is thanks to a new wheel-based infrastructure build by [@pvizeli] with input from [@frenck]. With Python wheels, we will build all the requirements of integrations ahead of time, and so a new version of Home Assistant is now just putting pieces together.
+
+Because of this, we changed how packages are installed when running Home Assistant inside a Docker container. It will now install the packages into the Python environment inside the container, instead of storing them in the `config/deps` folder, which lived outside the container.
+
+**Note:** Because of the new way packages are installed, Home Assistant on Hass.io will take longer to start the first time it is launched after an upgrade. Don't worry and let it finish! We are working on making this process faster in the future.
+
+**Note 2:** If you are using Hass.io or a dockerized version of Home Assistant, this release will one time clear the `deps` folder in your config folder.
+
+[@frenck]: https://github.com/frenck
+
+## {% linkable_title New Integrations %}
+
+- Adding Watson TTS (IBM Cloud) ([@rutkai] - [#23299]) ([watson_tts docs]) (new-integration)
+- MCP23017 ([@jardiamj] - [#23127]) ([mcp23017 docs]) (new-integration)
+- Solax Inverter Sensor Component ([@squishykid] - [#22579]) ([solax docs]) (new-integration)
+- Add Remote RPi Component ([@jgriff2] - [#23518]) ([remote_rpi_gpio docs]) (new-integration)
+- Azure Event Hub history component ([@eavanvalkenburg] - [#23878]) ([azure_event_hub docs]) (new-integration)
+- Add SSDP integration ([@balloob] - [#24090]) ([default_config docs]) ([discovery docs]) ([hue docs]) ([ssdp docs]) ([zeroconf docs]) (new-integration)
+- Add Repetier-Server Component ([@MTrab] - [#21658]) ([repetier docs]) (new-integration)
+
+## {% linkable_title New Platforms %}
+
+- Add LCN climate platform ([@alengwenus] - [#22542]) ([lcn docs]) (new-platform)
+- Add incomfort climate and bump client ([@zxdavb] - [#23830]) ([incomfort docs]) (new-platform)
+- Add new SmartHab light and cover platform ([@outadoc] - [#21225]) ([smarthab docs]) (new-platform)
+- Add geniushub sensor and binary_sensor ([@zxdavb] - [#23811]) ([geniushub docs]) (new-platform)
+- Mobile app to use device tracker config entry ([@balloob] - [#24238]) ([mobile_app docs]) (beta fix) (new-platform)
+
+## {% linkable_title If you need help... %}
+
+...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
+
+## {% linkable_title Reporting Issues %}
+
+Experiencing issues introduced by this release? Please report them in our [issue tracker](https://github.com/home-assistant/home-assistant/issues). Make sure to fill in all fields of the issue template.
+
+## {% linkable_title Breaking Changes %}
+
+- __Sun__ - Inspired by a [reddit](https://www.reddit.com/r/homeassistant/comments/bm62hl/sunsun_chatty_sensor_psa/) report, the sun.sun sensor has been tuned so that it doesn't update nearly as frequently. Previously the sun.sun sensor was updating every 30 seconds, day and night. Now it updates dependent on the solar elevation. This could possibly be a breaking change for some users as it updates less frequently. ([@Swamp-Ig] - [#23832]) ([sun docs])
+- __Doorbird__ -_Refactored_- This change cleans up the code for the component quite a bit. Schedule manipulation has been removed and HTTP views have been consolidated. The configuration changes should result in an overall easier experience for setting up a Doorbird in HA and allow for new Doorbird events to be utilized without having to update the component as often. No changes for switches or camera integrations of this component. ([@oblogic7] - [#23892]) ([doorbird docs])
+
+   Example configuration:
+   ```
+   doorbird:
+     devices:
+       - host: 10.10.10.10
+         token: 12345678abcd
+         name: Side Entry
+         username: abcd1234
+         password: abcd4321
+         events:
+           - button_1
+           - unit_1_button
+           - movement
+           - relay_1
+           - lock_relay
+    ```
+ 
+ - __Plex__
+   * Configuration option `include_non_clients` has been removed. The component was unnecessarily complicated with separate update methods for Plex devices and Plex sessions. This change always updates all known Plex clients regardless of type. The previous design also had issues where the Plex sessions are never polled if there are no Plex clients connected at startup and only 'session' client types connect after that point. This leads to a failure to discover new devices. This is a breaking change if the config option `include_non_clients` is being used since it has been removed. ([@jjlawren] - [#24038]) ([plex docs])
+   
+   * Configuration options use_custom_entity_ids and entity_namespace have been removed. This change will prepend the display name (and therefore the default entity_id) of each newly created entity with 'Plex' for easy identification. Users may customize each display name and entity_id as desired via the Entity Registry. Entities created before this PR will not be affected as the unique_id remains the same. ([@jjlawren] - [#24072]) ([plex docs])
+
+- __Verisure__ - Base entity_id of alarm_control_panel on alias of installation set by giid rather than first installation. This is a breaking change as it will change entity_id of alarm_control_panel in cases where a user is configuring an installation using giid that is not the first installation. ([@tkjacobsen] - [#23606]) ([verisure docs])
+- __Zestimate__ - Changed name property to return Zestimate and the property address. This will make it easier to distinguish multiple Zestimate sensor entities in the UI and is a breaking change as it will change entity_id of Zestimate sensors. If you have automations relying on your Zestimate sensor(s) you may need to revisit them to fix the ID's to the new ones. Also, you may need to update your Zestimate sensor(s) in your Lovelace UI. ([@dreed47] - [#23770]) ([zestimate docs])
+
+- __Python__ - _Deprecation_ - Python 3.5.3 support will be removed in the first release after August 1, 2019. This release will print a warning if a soon to be unsupported Python version is used. A notification will be present if Home Assistant is run under 3.6.0. ([@balloob] - [#24177])
+- __Async__ - _Developers only_ - `hass.components.frontend.async_register_built_in_panel` is no longer an async function. This allows removing panels form the frontend on the fly, and fires and event when panels are added/removed so the frontend knows when to reload. ([@balloob] - [#24184])
+- __TP-Link__ - _Distress Signal_ - Add a deprecation warning for tplink device_tracker ([@rytilahti] - [#24236]) ([tplink docs])
+
+## {% linkable_title Beta Fixes %}
+
+- Dynamic panels ([@balloob] - [#24184]) (breaking change) (beta fix)
+- Fix ESPHome discovered when already exists ([@OttoWinter] - [#24187]) ([esphome docs]) (beta fix)
+- homekit_controller no longer logs with transient network errors causing crypto failures as it will auto recover ([@Jc2k] - [#24193]) ([homekit_controller docs]) (beta fix)
+- Update hass-nabucasa ([@balloob] - [#24197]) ([cloud docs]) (beta fix)
+- Bump oauthlib version ([@therve] - [#24111]) ([fitbit docs]) (beta fix)
+- Allow discovery flows to be discovered via zeroconf/ssdp ([@balloob] - [#24199]) (beta fix)
+- Instantiate lock inside event loop ([@balloob] - [#24203]) (beta fix)
+- Improve error handling ([@balloob] - [#24204]) ([ssdp docs]) (beta fix)
+- Axis - Handle Vapix error messages ([@Kane610] - [#24215]) ([axis docs]) (beta fix)
+- Don't follow redirect on ingress itself ([@pvizeli] - [#24218]) ([hassio docs]) (beta fix)
+- Use resource for index routing. ([@balloob] - [#24223]) ([frontend docs]) (beta fix)
+- Add manifest support for homekit discovery ([@balloob] - [#24225]) ([lifx docs]) ([zeroconf docs]) (beta fix)
+- Log HomeKit model ([@balloob] - [#24229]) ([homekit_controller docs]) (beta fix)
+- Don't allow more than one config flow per discovered Axis device ([@Kane610] - [#24230]) ([axis docs]) (beta fix)
+- Add GPSLogger device_info and unique_id ([@balloob] - [#24231]) ([gpslogger docs]) (beta fix)
+- GeoFency unique ID and device info ([@balloob] - [#24232]) ([geofency docs]) (beta fix)
+- add a deprecation warning for tplink device_tracker ([@rytilahti] - [#24236]) ([tplink docs]) (breaking change) (beta fix)
+- Mobile app to use device tracker config entry ([@balloob] - [#24238]) ([mobile_app docs]) (beta fix) (new-platform)
+- Do not use the cache dir for PIP installs ([@balloob] - [#24233]) (beta fix)
+- Add restore state to OwnTracks device tracker ([@balloob] - [#24256]) ([owntracks docs]) (beta fix)
+- Mobile app device tracker to restore state ([@balloob] - [#24266]) ([mobile_app docs]) (beta fix)
+- Add restore state to Geofency ([@balloob] - [#24268]) ([geofency docs]) (beta fix)
+- deCONZ migrate to SSDP discovery ([@Kane610] - [#24252]) ([deconz docs]) ([hue docs]) ([ssdp docs]) (beta fix)
+- Add temperature sensor support to google smarthome thermostat device ([@piitaya] - [#24264]) ([google_assistant docs]) (beta fix)
+- Bump aioesphomeapi to 2.1.0 ([@OttoWinter] - [#24278]) ([esphome docs]) (beta fix)
+- Fix cors on the index view ([@balloob] - [#24283]) ([http docs]) (beta fix)
+- Remove deps folder in config when on Docker ([@balloob] - [#24284]) (beta fix)
+- Guard against bad states in Mobile App/OwnTracks ([@balloob] - [#24292]) ([mobile_app docs]) ([owntracks docs]) (beta fix)
+- Create progress file for pip installs ([@pvizeli] - [#24297]) (beta fix)
+- Run SSDP discovery in parallel ([@balloob] - [#24299]) ([ssdp docs]) (beta fix)
+- Upgrade Zeroconf to 0.23 ([@balloob] - [#24300]) ([zeroconf docs]) (beta fix)
+- address is deprecated in favor of addresses ([@Kane610] - [#24302]) ([zeroconf docs]) (beta fix)
+- Fix OwnTracks race condition ([@balloob] - [#24303]) ([owntracks docs]) (beta fix)
+
+## {% linkable_title All changes %}
+
+- Add Presence Detector Indoor to Homematic IP ([@SukramJ] - [#23755]) ([homematicip_cloud docs])
+- Split up yaml loaders into multiple files ([@ties] - [#23774])
+- Add config entry for IQVIA ([@bachya] - [#23765]) ([iqvia docs])
+- Add stepped volume to demo ([@elupus] - [#23759]) ([demo docs])
+- Add battery binary sensor to homematic ([@sander76] - [#23067]) ([homematic docs])
+- fix two times creating JWT headers. ([@pszafer] - [#23777]) ([html5 docs])
+- Bumped keenetic NDMS2 client version ([@foxel] - [#23786]) ([keenetic_ndms2 docs])
+- Add support for an external step in config flow ([@balloob] - [#23782])
+- Centralize geniushub updates ([@zxdavb] - [#23764]) ([geniushub docs])
+- Move tests to right folder ([@balloob] - [#23790])
+- Add LCN climate platform ([@alengwenus] - [#22542]) ([lcn docs]) (new-platform)
+- Bump venstarcolortouch to v0.7 ([@stbenjam] - [#23806]) ([venstar docs])
+- Upgrade youtube_dl to 2019.05.11 ([@fabaff] - [#23808]) ([media_extractor docs])
+- Bump pyotgw to 0.4b4, fix Opentherm Gateway name in manifest.json ([@mvn23] - [#23810]) ([opentherm_gw docs])
+- Fix patching right import ([@balloob] - [#23816])
+- Add incomfort climate and bump client ([@zxdavb] - [#23830]) ([incomfort docs]) (new-platform)
+- Make broadlink switch restore its state ([@akloeckner] - [#23829]) ([broadlink docs])
+- Catch import error when processing config ([@balloob] - [#23833])
+- Remove badges from README [skipci] ([@balloob] - [#23815])
+- HomeKit Controller: Adopt config entries for pairing with homekit accessories ([@Jc2k] - [#23825]) ([discovery docs]) ([homekit_controller docs])
+- Automatically generate config flow list ([@balloob] - [#23802])
+- Add new SmartHab light and cover platform ([@outadoc] - [#21225]) ([smarthab docs]) (new-platform)
+- Daikin adaptions for AirBase units ([@fredrike] - [#23734]) ([daikin docs])
+- Fix for battery device: new_device referenced before assignment. ([@sander76] - [#23793]) ([homematic docs])
+- Better handle large amounts of data being sent over WS ([@balloob] - [#23842]) ([camera docs]) ([lovelace docs]) ([media_player docs]) ([websocket_api docs])
+- Zeroconf - replace library ([@Kane610] - [#23835]) ([zeroconf docs])
+- WS: Improve service calling errors ([@balloob] - [#23840]) ([script docs]) ([websocket_api docs])
+- Allow deletion of automations and scripts ([@balloob] - [#23845]) ([config docs])
+- Use Cloudhooks for OwnTracks ([@balloob] - [#23847]) ([owntracks docs])
+- Fix aiohttp response serialize ([@balloob] - [#23858]) ([cloud docs])
+- Add geniushub sensor and binary_sensor ([@zxdavb] - [#23811]) ([geniushub docs]) (new-platform)
+- Quiet the chatty sun.sun ([@Swamp-Ig] - [#23832]) ([sun docs]) (breaking change)
+- Take code owner for sun.sun ([@Swamp-Ig] - [#23877]) ([sun docs])
+- Fix homekit test assert no messages ([@scop] - [#23856])
+- Restructure device tracker ([@balloob] - [#23862]) ([device_tracker docs])
+- Update Pynetgear to v0.6.1 ([@starkillerOG] - [#23886]) ([netgear docs])
+- Fix ecobee 3 homekit pairing ([@Jc2k] - [#23882]) ([homekit_controller docs])
+- Enable Homematic IP cloud climate device with HeatingThermostat only ([@SukramJ] - [#23776]) ([homematicip_cloud docs])
+- Load HA core config from storage ([@emontnemery] - [#23872])
+- Netatmo, handle offline device ([@Danielhiversen] - [#23907]) ([netatmo docs])
+- [WIP] Simplify zeroconf ([@robbiet480] - [#23890]) ([zeroconf docs])
+- Version bump insteonplm to 0.15.4 ([@nugget] - [#23918])
+- Fix bug when IQVIA API fails to return data ([@bachya] - [#23916]) ([iqvia docs])
+- Fix icons for homekit_controller sensors ([@Jc2k] - [#23921]) ([homekit_controller docs])
+- Fix additional IQVIA data bug ([@bachya] - [#23931]) ([iqvia docs])
+- Have homekit_controller use device registry ([@Jc2k] - [#23874]) ([homekit_controller docs])
+- Fix for non existing Daikin zones ([@fredrike] - [#23792]) ([daikin docs])
+- Fix fan rates for Daikin ([@fredrike] - [#23860]) ([daikin docs])
+- Added support for sensor other than temperature and humidity ([@Bouni] - [#23863]) ([spaceapi docs])
+- Add unit of measurement to Tautulli sensor ([@SiliconAvatar] - [#23873]) ([tautulli docs])
+- Update requests to 2.22.0 ([@BKPepe] - [#23958])
+- show battery level also when vacuum has no map support ([@adrianschroeter] - [#23947]) ([neato docs])
+- Upate xiaomi voltage parser, fix #23898 ([@Danielhiversen] - [#23962]) ([xiaomi_aqara docs])
+- Doorbird Refactor ([@oblogic7] - [#23892]) ([doorbird docs]) (breaking change)
+- Update russound_rio dependency to version 0.1.7 ([@wickerwaka] - [#23973]) ([russound_rio docs])
+- Adding Watson TTS (IBM Cloud) ([@rutkai] - [#23299]) ([watson_tts docs]) (new-integration)
+- Entity Cleanup on Z-Wave node removal ([@cgarwood] - [#23633]) ([zwave docs])
+- Use the timezone defined in Home Assistant when making the API call ([@ludeeus] - [#23284]) ([vasttrafik docs])
+- Updated non-blocking timout to 10 seconds for fixing timeout issues. ([@TomerFi] - [#23930]) ([switcher_kis docs])
+- Delete devices / entities when we remove a config entry. ([@Swamp-Ig] - [#23983])
+- Better handle file not found when loading YAML ([@balloob] - [#23908]) ([apns docs]) ([http docs])
+- daikin version bump ([@fredrike] - [#23991]) ([daikin docs])
+- Bump loopenergy library version - catches runtime exception. ([@pavoni] - [#23989]) ([loopenergy docs])
+- Update owner frontend integrations [skip ci] ([@balloob] - [#24001]) ([frontend docs]) ([lovelace docs]) ([panel_custom docs]) ([panel_iframe docs])
+- Axis IO-port support ([@Kane610] - [#23312]) ([axis docs])
+- Fire event when core config is updated ([@emontnemery] - [#23922])
+- Update CODEOWNERS ([@emontnemery] - [#24015])
+- Add websocket API for updating core config ([@emontnemery] - [#24009]) ([config docs])
+- Add geniushub sensors for issues ([@zxdavb] - [#23976]) ([geniushub docs])
+- Fix iterating over NoneType exception ([@iamtpage] - [#23648]) ([darksky docs])
+- bump geniushub-client to 0.4.9 ([@zxdavb] - [#24022]) ([geniushub docs])
+- Zeroconf discovery for config entries ([@Kane610] - [#23919]) ([axis docs]) ([zeroconf docs])
+- Improve yeelight imports ([@zewelor] - [#24020]) ([yeelight docs])
+- Downgrade Hue warning ([@balloob] - [#24033]) ([hue docs])
+- Ambiclimate test, mock ([@Danielhiversen] - [#24034])
+- Upgrade Mastodon.py to 1.4.2 ([@fabaff] - [#24004]) ([mastodon docs])
+- Require core config detection to be triggerd manually ([@balloob] - [#24019]) ([config docs]) ([onboarding docs])
+- Don't pass in loop ([@balloob] - [#23984])
+- Update ambiclimate library ([@Danielhiversen] - [#24049]) ([ambiclimate docs])
+- ESPHome component to use zeroconf discovery ([@Kane610] - [#24043]) ([esphome docs])
+- Add support for available property for broadlink ([@Danielhiversen] - [#23981]) ([broadlink docs])
+- Always update all Plex client types ([@jjlawren] - [#24038]) ([plex docs]) (breaking change)
+- Convert stream source to method ([@balloob] - [#23905])
+- Fix entity id naming when not using first install ([@tkjacobsen] - [#23606]) ([verisure docs]) (breaking change)
+- Daikin airbase beta fixes ([@fredrike] - [#24050]) ([daikin docs])
+- Better logging of method used for ADB connection ([@JeffLIrion] - [#24037]) ([androidtv docs])
+- Fix zeroconf sorting ([@balloob] - [#24068])
+- Rfxtrx, add data types ([@Danielhiversen] - [#24066]) ([rfxtrx docs])
+- Update the name of Zestimate sensors ([@dreed47] - [#23770]) ([zestimate docs]) (breaking change)
+- Added possibility to define the data type of Homematic ([@p0l0] - [#24078]) ([homematic docs])
+- Add 'adb_response' attribute to Android TV / Fire TV ([@JeffLIrion] - [#23960]) ([androidtv docs])
+- Adjust logging ([@elupus] - [#24082])
+- Fix Hue bridge timeout ([@terual] - [#24084]) ([hue docs])
+- MCP23017 ([@jardiamj] - [#23127]) ([mcp23017 docs]) (new-integration)
+- Remove device tracker unnecessary separate except clause ([@elupus] - [#24081]) ([device_tracker docs])
+- Refactoring of LCN component ([@alengwenus] - [#23824]) ([lcn docs])
+- Update code owner for Xiaomi TV ([@simse] - [#24102]) ([xiaomi_tv docs])
+- Issue #23514 - fix invalid hue response ([@techfreek] - [#23909]) ([emulated_hue docs])
+- Config entry device tracker ([@balloob] - [#24040]) ([device_tracker docs]) ([geofency docs]) ([gpslogger docs]) ([icloud docs]) ([locative docs]) ([owntracks docs]) ([zone docs])
+- Solax Inverter Sensor Component ([@squishykid] - [#22579]) ([solax docs]) (new-integration)
+- Set assumed_state property to True. ([@jardiamj] - [#24118]) ([mcp23017 docs])
+- Remove custom entity_id naming ([@jjlawren] - [#24072]) ([plex docs]) (breaking change)
+- Move imports to top ([@andrewsayre] - [#24108]) ([heos docs])
+- Use name in ESPHome discovery title ([@OttoWinter] - [#24100])
+- Add Remote RPi Component ([@jgriff2] - [#23518]) ([remote_rpi_gpio docs]) (new-integration)
+- Azure Event Hub history component ([@eavanvalkenburg] - [#23878]) ([azure_event_hub docs]) (new-integration)
+- geniushub: fix sensor battery level, and bump client ([@zxdavb] - [#24123]) ([geniushub docs])
+- Use importlib metadata to check installed packages ([@balloob] - [#24114])
+- Avoid useless Sonos state updates ([@amelchio] - [#24135]) ([sonos docs])
+- Add SSDP integration ([@balloob] - [#24090]) ([default_config docs]) ([discovery docs]) ([hue docs]) ([ssdp docs]) ([zeroconf docs]) (new-integration)
+- Lovelace: Fire event on save ([@bramkragten] - [#24104]) ([lovelace docs])
+- Use central polling to update entities ([@jjlawren] - [#24059]) ([plex docs])
+- Library refactorization of deCONZ ([@Kane610] - [#23725]) ([deconz docs])
+- Retrieve wire and wireless devices with the SRM device tracker ([@aerialls] - [#24117]) ([synology_srm docs])
+- bump dependency envoy_reader to 0.4 ([@jesserizzo] - [#24145]) ([enphase_envoy docs])
+- Debug log when polling ZHA light. ([@Adminiuga] - [#24167]) ([zha docs])
+- Upgrade huawei-lte-api to 1.2.0 ([@chmielowiec] - [#24165]) ([huawei_lte docs])
+- Use device name for device_tracker entry ([@robbiet480] - [#24155]) ([mobile_app docs])
+- Use global imports for ESPHome ([@OttoWinter] - [#24158]) ([esphome docs])
+- Add Repetier-Server Component ([@MTrab] - [#21658]) ([repetier docs]) (new-integration)
+- Cloud: Websocket API to manage Google assistant entity config ([@balloob] - [#24153]) ([cloud docs]) ([google_assistant docs])
+- Fix calling notify.notify with mobile_app targets in play. Fixes #24064 ([@robbiet480] - [#24156]) ([mobile_app docs])
+- Remove unused Sonos turn on/off methods ([@amelchio] - [#24174]) ([sonos docs])
+- Reinstate passing loop to DSMR ([@balloob] - [#24127]) ([dsmr docs])
+- Trådfri component to use new zeroconf discovery ([@Kane610] - [#24041]) ([discovery docs]) ([tradfri docs])
+- Move Homekit controller component to user zeroconf discovery ([@Kane610] - [#24042]) ([discovery docs]) ([homekit_controller docs])
+- Revert Zeroconf back to previously used library ([@Kane610] - [#24139]) ([zeroconf docs])
+- Deprecate Python 3.5.3 ([@balloob] - [#24177]) (breaking change)
+- Keep integrations in discovery ([@Kane610] - [#24179]) ([discovery docs])
+- Avoid slow updates with unavailable Sonos devices ([@amelchio] - [#24180]) ([sonos docs])
+- Support Hass.io wheels / docker env ([@pvizeli] - [#24175])
+- Remove discovery from initial config ([@balloob] - [#24183])
+- Fix duplicated discovered homekit devices ([@Jc2k] - [#24178]) ([homekit_controller docs])
+- Add service calls for LCN component ([@alengwenus] - [#24105]) ([lcn docs])
+- Update azure-pipelines.yml for check version ([@pvizeli] - [#24194])
+- Dynamic panels ([@balloob] - [#24184]) (breaking change) (beta fix)
+- Fix ESPHome discovered when already exists ([@OttoWinter] - [#24187]) ([esphome docs]) (beta fix)
+- homekit_controller no longer logs with transient network errors causing crypto failures as it will auto recover ([@Jc2k] - [#24193]) ([homekit_controller docs]) (beta fix)
+- Update hass-nabucasa ([@balloob] - [#24197]) ([cloud docs]) (beta fix)
+- Fix ESPHome config flow with invalid config entry ([@OttoWinter] - [#24213]) ([esphome docs])
+- Bump oauthlib version ([@therve] - [#24111]) ([fitbit docs]) (beta fix)
+- Allow discovery flows to be discovered via zeroconf/ssdp ([@balloob] - [#24199]) (beta fix)
+- Instantiate lock inside event loop ([@balloob] - [#24203]) (beta fix)
+- Improve error handling ([@balloob] - [#24204]) ([ssdp docs]) (beta fix)
+- Axis - Handle Vapix error messages ([@Kane610] - [#24215]) ([axis docs]) (beta fix)
+- Don't follow redirect on ingress itself ([@pvizeli] - [#24218]) ([hassio docs]) (beta fix)
+- Use resource for index routing. ([@balloob] - [#24223]) ([frontend docs]) (beta fix)
+- Add manifest support for homekit discovery ([@balloob] - [#24225]) ([lifx docs]) ([zeroconf docs]) (beta fix)
+- Log HomeKit model ([@balloob] - [#24229]) ([homekit_controller docs]) (beta fix)
+- Don't allow more than one config flow per discovered Axis device ([@Kane610] - [#24230]) ([axis docs]) (beta fix)
+- Add GPSLogger device_info and unique_id ([@balloob] - [#24231]) ([gpslogger docs]) (beta fix)
+- GeoFency unique ID and device info ([@balloob] - [#24232]) ([geofency docs]) (beta fix)
+- add a deprecation warning for tplink device_tracker ([@rytilahti] - [#24236]) ([tplink docs]) (breaking change) (beta fix)
+- Mobile app to use device tracker config entry ([@balloob] - [#24238]) ([mobile_app docs]) (beta fix) (new-platform)
+- Do not use the cache dir for PIP installs ([@balloob] - [#24233]) (beta fix)
+- Add restore state to OwnTracks device tracker ([@balloob] - [#24256]) ([owntracks docs]) (beta fix)
+- Mobile app device tracker to restore state ([@balloob] - [#24266]) ([mobile_app docs]) (beta fix)
+- Add restore state to Geofency ([@balloob] - [#24268]) ([geofency docs]) (beta fix)
+- deCONZ migrate to SSDP discovery ([@Kane610] - [#24252]) ([deconz docs]) ([hue docs]) ([ssdp docs]) (beta fix)
+- Add temperature sensor support to google smarthome thermostat device ([@piitaya] - [#24264]) ([google_assistant docs]) (beta fix)
+- Bump aioesphomeapi to 2.1.0 ([@OttoWinter] - [#24278]) ([esphome docs]) (beta fix)
+- Fix cors on the index view ([@balloob] - [#24283]) ([http docs]) (beta fix)
+- Remove deps folder in config when on Docker ([@balloob] - [#24284]) (beta fix)
+- Guard against bad states in Mobile App/OwnTracks ([@balloob] - [#24292]) ([mobile_app docs]) ([owntracks docs]) (beta fix)
+- Create progress file for pip installs ([@pvizeli] - [#24297]) (beta fix)
+- Run SSDP discovery in parallel ([@balloob] - [#24299]) ([ssdp docs]) (beta fix)
+- Upgrade Zeroconf to 0.23 ([@balloob] - [#24300]) ([zeroconf docs]) (beta fix)
+- address is deprecated in favor of addresses ([@Kane610] - [#24302]) ([zeroconf docs]) (beta fix)
+- Fix OwnTracks race condition ([@balloob] - [#24303]) ([owntracks docs]) (beta fix)
+
+[#21225]: https://github.com/home-assistant/home-assistant/pull/21225
+[#21658]: https://github.com/home-assistant/home-assistant/pull/21658
+[#22542]: https://github.com/home-assistant/home-assistant/pull/22542
+[#22579]: https://github.com/home-assistant/home-assistant/pull/22579
+[#23067]: https://github.com/home-assistant/home-assistant/pull/23067
+[#23127]: https://github.com/home-assistant/home-assistant/pull/23127
+[#23284]: https://github.com/home-assistant/home-assistant/pull/23284
+[#23299]: https://github.com/home-assistant/home-assistant/pull/23299
+[#23312]: https://github.com/home-assistant/home-assistant/pull/23312
+[#23518]: https://github.com/home-assistant/home-assistant/pull/23518
+[#23606]: https://github.com/home-assistant/home-assistant/pull/23606
+[#23633]: https://github.com/home-assistant/home-assistant/pull/23633
+[#23648]: https://github.com/home-assistant/home-assistant/pull/23648
+[#23725]: https://github.com/home-assistant/home-assistant/pull/23725
+[#23734]: https://github.com/home-assistant/home-assistant/pull/23734
+[#23755]: https://github.com/home-assistant/home-assistant/pull/23755
+[#23759]: https://github.com/home-assistant/home-assistant/pull/23759
+[#23764]: https://github.com/home-assistant/home-assistant/pull/23764
+[#23765]: https://github.com/home-assistant/home-assistant/pull/23765
+[#23770]: https://github.com/home-assistant/home-assistant/pull/23770
+[#23774]: https://github.com/home-assistant/home-assistant/pull/23774
+[#23776]: https://github.com/home-assistant/home-assistant/pull/23776
+[#23777]: https://github.com/home-assistant/home-assistant/pull/23777
+[#23782]: https://github.com/home-assistant/home-assistant/pull/23782
+[#23786]: https://github.com/home-assistant/home-assistant/pull/23786
+[#23790]: https://github.com/home-assistant/home-assistant/pull/23790
+[#23792]: https://github.com/home-assistant/home-assistant/pull/23792
+[#23793]: https://github.com/home-assistant/home-assistant/pull/23793
+[#23802]: https://github.com/home-assistant/home-assistant/pull/23802
+[#23806]: https://github.com/home-assistant/home-assistant/pull/23806
+[#23808]: https://github.com/home-assistant/home-assistant/pull/23808
+[#23810]: https://github.com/home-assistant/home-assistant/pull/23810
+[#23811]: https://github.com/home-assistant/home-assistant/pull/23811
+[#23815]: https://github.com/home-assistant/home-assistant/pull/23815
+[#23816]: https://github.com/home-assistant/home-assistant/pull/23816
+[#23824]: https://github.com/home-assistant/home-assistant/pull/23824
+[#23825]: https://github.com/home-assistant/home-assistant/pull/23825
+[#23829]: https://github.com/home-assistant/home-assistant/pull/23829
+[#23830]: https://github.com/home-assistant/home-assistant/pull/23830
+[#23832]: https://github.com/home-assistant/home-assistant/pull/23832
+[#23833]: https://github.com/home-assistant/home-assistant/pull/23833
+[#23835]: https://github.com/home-assistant/home-assistant/pull/23835
+[#23840]: https://github.com/home-assistant/home-assistant/pull/23840
+[#23842]: https://github.com/home-assistant/home-assistant/pull/23842
+[#23845]: https://github.com/home-assistant/home-assistant/pull/23845
+[#23847]: https://github.com/home-assistant/home-assistant/pull/23847
+[#23856]: https://github.com/home-assistant/home-assistant/pull/23856
+[#23858]: https://github.com/home-assistant/home-assistant/pull/23858
+[#23860]: https://github.com/home-assistant/home-assistant/pull/23860
+[#23862]: https://github.com/home-assistant/home-assistant/pull/23862
+[#23863]: https://github.com/home-assistant/home-assistant/pull/23863
+[#23872]: https://github.com/home-assistant/home-assistant/pull/23872
+[#23873]: https://github.com/home-assistant/home-assistant/pull/23873
+[#23874]: https://github.com/home-assistant/home-assistant/pull/23874
+[#23877]: https://github.com/home-assistant/home-assistant/pull/23877
+[#23878]: https://github.com/home-assistant/home-assistant/pull/23878
+[#23882]: https://github.com/home-assistant/home-assistant/pull/23882
+[#23886]: https://github.com/home-assistant/home-assistant/pull/23886
+[#23890]: https://github.com/home-assistant/home-assistant/pull/23890
+[#23892]: https://github.com/home-assistant/home-assistant/pull/23892
+[#23905]: https://github.com/home-assistant/home-assistant/pull/23905
+[#23907]: https://github.com/home-assistant/home-assistant/pull/23907
+[#23908]: https://github.com/home-assistant/home-assistant/pull/23908
+[#23909]: https://github.com/home-assistant/home-assistant/pull/23909
+[#23916]: https://github.com/home-assistant/home-assistant/pull/23916
+[#23918]: https://github.com/home-assistant/home-assistant/pull/23918
+[#23919]: https://github.com/home-assistant/home-assistant/pull/23919
+[#23921]: https://github.com/home-assistant/home-assistant/pull/23921
+[#23922]: https://github.com/home-assistant/home-assistant/pull/23922
+[#23930]: https://github.com/home-assistant/home-assistant/pull/23930
+[#23931]: https://github.com/home-assistant/home-assistant/pull/23931
+[#23947]: https://github.com/home-assistant/home-assistant/pull/23947
+[#23958]: https://github.com/home-assistant/home-assistant/pull/23958
+[#23960]: https://github.com/home-assistant/home-assistant/pull/23960
+[#23962]: https://github.com/home-assistant/home-assistant/pull/23962
+[#23973]: https://github.com/home-assistant/home-assistant/pull/23973
+[#23976]: https://github.com/home-assistant/home-assistant/pull/23976
+[#23981]: https://github.com/home-assistant/home-assistant/pull/23981
+[#23983]: https://github.com/home-assistant/home-assistant/pull/23983
+[#23984]: https://github.com/home-assistant/home-assistant/pull/23984
+[#23989]: https://github.com/home-assistant/home-assistant/pull/23989
+[#23991]: https://github.com/home-assistant/home-assistant/pull/23991
+[#24001]: https://github.com/home-assistant/home-assistant/pull/24001
+[#24004]: https://github.com/home-assistant/home-assistant/pull/24004
+[#24009]: https://github.com/home-assistant/home-assistant/pull/24009
+[#24015]: https://github.com/home-assistant/home-assistant/pull/24015
+[#24019]: https://github.com/home-assistant/home-assistant/pull/24019
+[#24020]: https://github.com/home-assistant/home-assistant/pull/24020
+[#24022]: https://github.com/home-assistant/home-assistant/pull/24022
+[#24033]: https://github.com/home-assistant/home-assistant/pull/24033
+[#24034]: https://github.com/home-assistant/home-assistant/pull/24034
+[#24037]: https://github.com/home-assistant/home-assistant/pull/24037
+[#24038]: https://github.com/home-assistant/home-assistant/pull/24038
+[#24040]: https://github.com/home-assistant/home-assistant/pull/24040
+[#24041]: https://github.com/home-assistant/home-assistant/pull/24041
+[#24042]: https://github.com/home-assistant/home-assistant/pull/24042
+[#24043]: https://github.com/home-assistant/home-assistant/pull/24043
+[#24049]: https://github.com/home-assistant/home-assistant/pull/24049
+[#24050]: https://github.com/home-assistant/home-assistant/pull/24050
+[#24059]: https://github.com/home-assistant/home-assistant/pull/24059
+[#24066]: https://github.com/home-assistant/home-assistant/pull/24066
+[#24068]: https://github.com/home-assistant/home-assistant/pull/24068
+[#24072]: https://github.com/home-assistant/home-assistant/pull/24072
+[#24078]: https://github.com/home-assistant/home-assistant/pull/24078
+[#24081]: https://github.com/home-assistant/home-assistant/pull/24081
+[#24082]: https://github.com/home-assistant/home-assistant/pull/24082
+[#24084]: https://github.com/home-assistant/home-assistant/pull/24084
+[#24090]: https://github.com/home-assistant/home-assistant/pull/24090
+[#24100]: https://github.com/home-assistant/home-assistant/pull/24100
+[#24102]: https://github.com/home-assistant/home-assistant/pull/24102
+[#24104]: https://github.com/home-assistant/home-assistant/pull/24104
+[#24105]: https://github.com/home-assistant/home-assistant/pull/24105
+[#24108]: https://github.com/home-assistant/home-assistant/pull/24108
+[#24111]: https://github.com/home-assistant/home-assistant/pull/24111
+[#24114]: https://github.com/home-assistant/home-assistant/pull/24114
+[#24117]: https://github.com/home-assistant/home-assistant/pull/24117
+[#24118]: https://github.com/home-assistant/home-assistant/pull/24118
+[#24123]: https://github.com/home-assistant/home-assistant/pull/24123
+[#24127]: https://github.com/home-assistant/home-assistant/pull/24127
+[#24135]: https://github.com/home-assistant/home-assistant/pull/24135
+[#24139]: https://github.com/home-assistant/home-assistant/pull/24139
+[#24145]: https://github.com/home-assistant/home-assistant/pull/24145
+[#24153]: https://github.com/home-assistant/home-assistant/pull/24153
+[#24155]: https://github.com/home-assistant/home-assistant/pull/24155
+[#24156]: https://github.com/home-assistant/home-assistant/pull/24156
+[#24158]: https://github.com/home-assistant/home-assistant/pull/24158
+[#24165]: https://github.com/home-assistant/home-assistant/pull/24165
+[#24167]: https://github.com/home-assistant/home-assistant/pull/24167
+[#24174]: https://github.com/home-assistant/home-assistant/pull/24174
+[#24175]: https://github.com/home-assistant/home-assistant/pull/24175
+[#24177]: https://github.com/home-assistant/home-assistant/pull/24177
+[#24178]: https://github.com/home-assistant/home-assistant/pull/24178
+[#24179]: https://github.com/home-assistant/home-assistant/pull/24179
+[#24180]: https://github.com/home-assistant/home-assistant/pull/24180
+[#24183]: https://github.com/home-assistant/home-assistant/pull/24183
+[#24184]: https://github.com/home-assistant/home-assistant/pull/24184
+[#24187]: https://github.com/home-assistant/home-assistant/pull/24187
+[#24193]: https://github.com/home-assistant/home-assistant/pull/24193
+[#24194]: https://github.com/home-assistant/home-assistant/pull/24194
+[#24197]: https://github.com/home-assistant/home-assistant/pull/24197
+[#24199]: https://github.com/home-assistant/home-assistant/pull/24199
+[#24203]: https://github.com/home-assistant/home-assistant/pull/24203
+[#24204]: https://github.com/home-assistant/home-assistant/pull/24204
+[#24213]: https://github.com/home-assistant/home-assistant/pull/24213
+[#24215]: https://github.com/home-assistant/home-assistant/pull/24215
+[#24218]: https://github.com/home-assistant/home-assistant/pull/24218
+[#24223]: https://github.com/home-assistant/home-assistant/pull/24223
+[#24225]: https://github.com/home-assistant/home-assistant/pull/24225
+[#24229]: https://github.com/home-assistant/home-assistant/pull/24229
+[#24230]: https://github.com/home-assistant/home-assistant/pull/24230
+[#24231]: https://github.com/home-assistant/home-assistant/pull/24231
+[#24232]: https://github.com/home-assistant/home-assistant/pull/24232
+[#24233]: https://github.com/home-assistant/home-assistant/pull/24233
+[#24236]: https://github.com/home-assistant/home-assistant/pull/24236
+[#24238]: https://github.com/home-assistant/home-assistant/pull/24238
+[#24252]: https://github.com/home-assistant/home-assistant/pull/24252
+[#24256]: https://github.com/home-assistant/home-assistant/pull/24256
+[#24264]: https://github.com/home-assistant/home-assistant/pull/24264
+[#24266]: https://github.com/home-assistant/home-assistant/pull/24266
+[#24268]: https://github.com/home-assistant/home-assistant/pull/24268
+[#24278]: https://github.com/home-assistant/home-assistant/pull/24278
+[#24283]: https://github.com/home-assistant/home-assistant/pull/24283
+[#24284]: https://github.com/home-assistant/home-assistant/pull/24284
+[#24292]: https://github.com/home-assistant/home-assistant/pull/24292
+[#24297]: https://github.com/home-assistant/home-assistant/pull/24297
+[#24299]: https://github.com/home-assistant/home-assistant/pull/24299
+[#24300]: https://github.com/home-assistant/home-assistant/pull/24300
+[#24302]: https://github.com/home-assistant/home-assistant/pull/24302
+[#24303]: https://github.com/home-assistant/home-assistant/pull/24303
+[@Adminiuga]: https://github.com/Adminiuga
+[@BKPepe]: https://github.com/BKPepe
+[@Bouni]: https://github.com/Bouni
+[@Danielhiversen]: https://github.com/Danielhiversen
+[@Jc2k]: https://github.com/Jc2k
+[@JeffLIrion]: https://github.com/JeffLIrion
+[@Kane610]: https://github.com/Kane610
+[@MTrab]: https://github.com/MTrab
+[@OttoWinter]: https://github.com/OttoWinter
+[@SiliconAvatar]: https://github.com/SiliconAvatar
+[@SukramJ]: https://github.com/SukramJ
+[@Swamp-Ig]: https://github.com/Swamp-Ig
+[@TomerFi]: https://github.com/TomerFi
+[@adrianschroeter]: https://github.com/adrianschroeter
+[@aerialls]: https://github.com/aerialls
+[@akloeckner]: https://github.com/akloeckner
+[@alengwenus]: https://github.com/alengwenus
+[@amelchio]: https://github.com/amelchio
+[@andrewsayre]: https://github.com/andrewsayre
+[@bachya]: https://github.com/bachya
+[@balloob]: https://github.com/balloob
+[@bramkragten]: https://github.com/bramkragten
+[@cgarwood]: https://github.com/cgarwood
+[@chmielowiec]: https://github.com/chmielowiec
+[@dreed47]: https://github.com/dreed47
+[@eavanvalkenburg]: https://github.com/eavanvalkenburg
+[@elupus]: https://github.com/elupus
+[@emontnemery]: https://github.com/emontnemery
+[@fabaff]: https://github.com/fabaff
+[@foxel]: https://github.com/foxel
+[@fredrike]: https://github.com/fredrike
+[@iamtpage]: https://github.com/iamtpage
+[@jardiamj]: https://github.com/jardiamj
+[@jesserizzo]: https://github.com/jesserizzo
+[@jgriff2]: https://github.com/jgriff2
+[@jjlawren]: https://github.com/jjlawren
+[@ludeeus]: https://github.com/ludeeus
+[@mvn23]: https://github.com/mvn23
+[@nugget]: https://github.com/nugget
+[@oblogic7]: https://github.com/oblogic7
+[@outadoc]: https://github.com/outadoc
+[@p0l0]: https://github.com/p0l0
+[@pavoni]: https://github.com/pavoni
+[@piitaya]: https://github.com/piitaya
+[@pszafer]: https://github.com/pszafer
+[@pvizeli]: https://github.com/pvizeli
+[@robbiet480]: https://github.com/robbiet480
+[@rutkai]: https://github.com/rutkai
+[@rytilahti]: https://github.com/rytilahti
+[@sander76]: https://github.com/sander76
+[@scop]: https://github.com/scop
+[@simse]: https://github.com/simse
+[@squishykid]: https://github.com/squishykid
+[@starkillerOG]: https://github.com/starkillerOG
+[@stbenjam]: https://github.com/stbenjam
+[@techfreek]: https://github.com/techfreek
+[@terual]: https://github.com/terual
+[@therve]: https://github.com/therve
+[@ties]: https://github.com/ties
+[@tkjacobsen]: https://github.com/tkjacobsen
+[@wickerwaka]: https://github.com/wickerwaka
+[@zewelor]: https://github.com/zewelor
+[@zxdavb]: https://github.com/zxdavb
+[ambiclimate docs]: /components/ambiclimate/
+[androidtv docs]: /components/androidtv/
+[apns docs]: /components/apns/
+[axis docs]: /components/axis/
+[azure_event_hub docs]: /components/azure_event_hub/
+[broadlink docs]: /components/broadlink/
+[camera docs]: /components/camera/
+[cloud docs]: /components/cloud/
+[config docs]: /components/config/
+[daikin docs]: /components/daikin/
+[darksky docs]: /components/darksky/
+[deconz docs]: /components/deconz/
+[default_config docs]: /components/default_config/
+[demo docs]: /components/demo/
+[device_tracker docs]: /components/device_tracker/
+[discovery docs]: /components/discovery/
+[doorbird docs]: /components/doorbird/
+[dsmr docs]: /components/dsmr/
+[emulated_hue docs]: /components/emulated_hue/
+[enphase_envoy docs]: /components/enphase_envoy/
+[esphome docs]: /components/esphome/
+[fitbit docs]: /components/fitbit/
+[frontend docs]: /components/frontend/
+[geniushub docs]: /components/geniushub/
+[geofency docs]: /components/geofency/
+[google_assistant docs]: /components/google_assistant/
+[gpslogger docs]: /components/gpslogger/
+[hassio docs]: /components/hassio/
+[heos docs]: /components/heos/
+[homekit_controller docs]: /components/homekit_controller/
+[homematic docs]: /components/homematic/
+[homematicip_cloud docs]: /components/homematicip_cloud/
+[html5 docs]: /components/html5/
+[http docs]: /components/http/
+[huawei_lte docs]: /components/huawei_lte/
+[hue docs]: /components/hue/
+[icloud docs]: /components/icloud/
+[incomfort docs]: /components/incomfort/
+[iqvia docs]: /components/iqvia/
+[keenetic_ndms2 docs]: /components/keenetic_ndms2/
+[lcn docs]: /components/lcn/
+[lifx docs]: /components/lifx/
+[locative docs]: /components/locative/
+[loopenergy docs]: /components/loopenergy/
+[lovelace docs]: /components/lovelace/
+[mastodon docs]: /components/mastodon/
+[mcp23017 docs]: /components/mcp23017/
+[media_extractor docs]: /components/media_extractor/
+[media_player docs]: /components/media_player/
+[mobile_app docs]: /components/mobile_app/
+[neato docs]: /components/neato/
+[netatmo docs]: /components/netatmo/
+[netgear docs]: /components/netgear/
+[onboarding docs]: /components/onboarding/
+[opentherm_gw docs]: /components/opentherm_gw/
+[owntracks docs]: /components/owntracks/
+[panel_custom docs]: /components/panel_custom/
+[panel_iframe docs]: /components/panel_iframe/
+[plex docs]: /components/plex/
+[remote_rpi_gpio docs]: /components/remote_rpi_gpio/
+[repetier docs]: /components/repetier/
+[rfxtrx docs]: /components/rfxtrx/
+[russound_rio docs]: /components/russound_rio/
+[script docs]: /components/script/
+[smarthab docs]: /components/smarthab/
+[solax docs]: /components/solax/
+[sonos docs]: /components/sonos/
+[spaceapi docs]: /components/spaceapi/
+[ssdp docs]: /components/ssdp/
+[sun docs]: /components/sun/
+[switcher_kis docs]: /components/switcher_kis/
+[synology_srm docs]: /components/synology_srm/
+[tautulli docs]: /components/tautulli/
+[tplink docs]: /components/tplink/
+[tradfri docs]: /components/tradfri/
+[vasttrafik docs]: /components/vasttrafik/
+[venstar docs]: /components/venstar/
+[verisure docs]: /components/verisure/
+[watson_tts docs]: /components/watson_tts/
+[websocket_api docs]: /components/websocket_api/
+[xiaomi_aqara docs]: /components/xiaomi_aqara/
+[xiaomi_tv docs]: /components/xiaomi_tv/
+[yeelight docs]: /components/yeelight/
+[zeroconf docs]: /components/zeroconf/
+[zestimate docs]: /components/zestimate/
+[zha docs]: /components/zha/
+[zone docs]: /components/zone/
+[zwave docs]: /components/zwave/
--- a/source/images/blog/2019-06-release-94/components.png
+++ b/source/images/blog/2019-06-release-94/components.png
--- a/source/images/blog/2019-06-release-94/google-ui.png
+++ b/source/images/blog/2019-06-release-94/google-ui.png
--- a/source/images/screenshots/watson_tts_screen.png
+++ b/source/images/screenshots/watson_tts_screen.png
--- a/source/images/supported_brands/azure_event_hub.svg
+++ b/source/images/supported_brands/azure_event_hub.svg
@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- Generator: Adobe Illustrator 18.1.1, SVG Export Plug-In . SVG Version: 6.00 Build 0)  -->
+<svg version="1.1" id="Layer_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
+	 viewBox="-163 237 32 32" enable-background="new -163 237 32 32" xml:space="preserve">
+<path fill="#B8D432" d="M-144,251.5c0,0.3-0.2,0.5-0.5,0.5h-3.9c-0.3,0-0.5-0.2-0.5-0.5v-2.9c0-0.3,0.2-0.5,0.5-0.5h3.9
+	c0.3,0,0.5,0.2,0.5,0.5V251.5z"/>
+<path fill="#B8D432" d="M-137,254.5c0,0.3-0.2,0.5-0.5,0.5h-3.9c-0.3,0-0.5-0.2-0.5-0.5v-2.9c0-0.3,0.2-0.5,0.5-0.5h3.9
+	c0.3,0,0.5,0.2,0.5,0.5V254.5z"/>
+<path fill="#B8D432" d="M-144,257.5c0,0.3-0.2,0.5-0.5,0.5h-3.9c-0.3,0-0.5-0.2-0.5-0.5v-2.9c0-0.3,0.2-0.5,0.5-0.5h3.9
+	c0.3,0,0.5,0.2,0.5,0.5V257.5z"/>
+<path fill="#B8D432" d="M-151,248.5c0,0.3-0.2,0.5-0.5,0.5h-4c-0.3,0-0.5-0.2-0.5-0.5v-3c0-0.3,0.2-0.5,0.5-0.5h3.9
+	c0.4,0,0.6,0.2,0.6,0.5V248.5z"/>
+<path fill="#0072C6" d="M-133.5,238L-133.5,238h-3h-22.1h-1.9h-1c-0.3,0-0.5,0.2-0.5,0.5v6c0,0.3,0.2,0.5,0.5,0.5h3
+	c0.3,0,0.5-0.2,0.5-0.5V242h21v2.5c0,0.3,0.2,0.5,0.6,0.5h2.9c0.3,0,0.5-0.2,0.5-0.5v-3v-3C-133,238.2-133.2,238-133.5,238z"/>
+<path fill="#0072C6" d="M-133.5,261.1h-2.9c-0.3,0-0.5,0.2-0.5,0.5v2.4H-158v-2.5c0-0.3-0.2-0.5-0.6-0.5h-2.9
+	c-0.3,0-0.5,0.2-0.5,0.6v5.9c0,0.3,0.2,0.5,0.5,0.5h1h2h22.1h2.8h0.1c0.3,0,0.5-0.2,0.5-0.5v-5.9
+	C-133,261.3-133.2,261.1-133.5,261.1z"/>
+<path fill="#B8D432" d="M-151,254.5c0,0.3-0.2,0.5-0.5,0.5h-4c-0.3,0-0.5-0.2-0.5-0.5v-3c0-0.3,0.2-0.5,0.5-0.5h3.9
+	c0.4,0,0.6,0.2,0.6,0.5V254.5z"/>
+<path fill="#B8D432" d="M-151,260.5c0,0.3-0.2,0.5-0.5,0.5h-4c-0.3,0-0.5-0.2-0.5-0.5v-3c0-0.3,0.2-0.5,0.5-0.5h3.9
+	c0.4,0,0.6,0.2,0.6,0.5V260.5z"/>
+</svg>
--- a/source/images/supported_brands/repetier.png
+++ b/source/images/supported_brands/repetier.png
--- a/source/images/supported_brands/smarthab.png
+++ b/source/images/supported_brands/smarthab.png
--- a/source/images/supported_brands/solax-logo.png
+++ b/source/images/supported_brands/solax-logo.png
--- a/source/images/supported_brands/watson_tts.png
+++ b/source/images/supported_brands/watson_tts.png