Merge branch 'rc' into current

_config.yml

@@ -141,14 +141,14 @@ social:
 
 # Home Assistant release details
 current_major_version: 0
-current_minor_version: 75
+current_minor_version: 76
-current_patch_version: 3
+current_patch_version: 0
-date_released: 2018-08-09
+date_released: 2018-08-17
 
 # Either # or the anchor link to latest release notes in the blog post.
 # Must be prefixed with a # and have double quotes around it.
 # Major release:
-patch_version_notes: "#release-0753---august-9"
+patch_version_notes: "#"
 # Minor release (Example #release-0431---april-25):
 
 # Date we moved to Discourse for comments

source/_components/amcrest.markdown

@@ -46,7 +46,7 @@ Configuration variables:
 - **host** (*Required*): The IP address or hostname of your camera. If using a hostname, make sure the DNS works as expected.
 - **username** (*Required*): The username for accessing your camera.
 - **password** (*Required*): The password for accessing your camera.
-- **name** (*Optional*): This parameter allows you to override the name of your camera. The default is "Amcrest Camera".
+- **name** (*Optional*): This parameter allows you to override the name of your camera. The default is "Amcrest Camera". In the case of multi-camera setups, this is highly recommended as camera id number will be randomly changed at each reboot if a name is not allocated.
 - **port** (*Optional*): The port that the camera is running on. The default is 80.
 - **resolution** (*Optional*): This parameter allows you to specify the camera resolution. For a high resolution (1080/720p), specify the option `high`. For VGA resolution (640x480p), specify the option `low`. If omitted, it defaults to *high*.
 - **stream_source** (*Optional*): The data source for the live stream. `mjpeg` will use the camera's native MJPEG stream, whereas `snapshot` will use the camera's snapshot API to create a stream from still images. You can also set the `rtsp` option to generate the streaming via RTSP protocol. If omitted, it defaults to *snapshot*.

source/_components/binary_sensor.openuv.markdown

@@ -0,0 +1,23 @@
+---
+layout: page
+title: "OpenUV Binary Sensor"
+description: "Instructions on how to integrate OpenUV binary sensors within Home Assistant."
+date: 2018-07-31 22:01
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: openuv.jpg
+ha_category: Binary Sensor
+ha_release: 0.76
+ha_iot_class: "Cloud Polling"
+---
+
+The `openuv` binary sensor platform allows you to view binary sensor data from
+[OpenUV](http://openuv.io).
+
+<p class='note'>
+You must have the [OpenUV component](/components/openuv/) configured to use
+this platform. After configuring that component, binary sensors will
+automatically appear.
+</p>

source/_components/binary_sensor.velbus.markdown

@@ -13,49 +13,6 @@ ha_iot_class: "Local Push"
 ha_release: "0.50"
 ---
 
-The `velbus` binary_sensor allows you to control [Velbus](http://www.velbus.eu) connected wall switches.
+The `velbus` binary_sensor allows you to control [Velbus](http://www.velbus.eu) connected input devices.
-
-## {% linkable_title Configuration %}
-
-To use your Velbus wall switches in your installation, add the following to your `configuration.yaml` file:
-
-```yaml
-# Example configuration.yaml entry
-binary_sensor:
-  - platform: velbus
-    devices:
-      - name: Wall Switch 1
-        module: 0xda
-        channel: 4
-      - name: Wall Switch 2
-        module: 0xbc
-        channel: 1
-        is_pushbutton: true
-```
-
-{% configuration %}
-devices:
-  description: The list contains the binary sensors to configure.
-  required: true
-  type: map
-  keys:
-    name:
-      description: Name to use in the frontend.
-      required: true
-      type: string
-    module:
-      description: The hexadecimal module address.
-      required: true
-      type: string
-    channel:
-      description: The channel number in the module.
-      required: true
-      type: string
-    is_pushbutton:
-      description: Set to indicate if a wall switch is a push button or not.
-      required: false
-      type: boolean
-      default: false
-{% endconfiguration %}
 
 For hub configuration, see [the Velbus component](/components/velbus/).

source/_components/device_tracker.bt_home_hub_5.markdown

@@ -25,6 +25,6 @@ device_tracker:
 
 Configuration variables:
 
-- **host** (*Required*): The IP address of your router, e.g., 192.168.1.254.
+- **host** (*Optional*): The IP address of your router, Default: 192.168.1.254.
 
 See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.

source/_components/device_tracker.google_maps.markdown

@@ -45,4 +45,8 @@ password:
   description: The password for your given username.
   required: true
   type: string
+max_gps_accuracy:
+   description: Sometimes Google Maps can report GPS locations with a very low accuracy (few kilometers). That can trigger false zoning. Using this parameter, you can filter these false GPS reports. The number has to be in meters. For example, if you put 200 only GPS reports with an accuracy under 200 will be taken into account - Defaults to 100km if not specified.
+   required: false
+   type: float
 {% endconfiguration %}

source/_components/device_tracker.keenetic_ndms2.markdown

@@ -29,7 +29,8 @@ device_tracker:
 Configuration variables:
 
 - **host** (*Required*): The IP address of your router, e.g., 192.168.1.1.
-- **username** (*Required*): The username to login into the router (user should have read access to web interface of the router).
+- **port** (*Optional*): The Telnet port of your router. Default is 23.
+- **username** (*Required*): The username to login into the router (user should have read access to telnet interface of the router).
 - **password** (*Required*): The password for the specified username.
 - **interface** (*Optional*): Ihe internal name of the interface to get devices connected to. Default is 'Home'. For expert users only. 
 

source/_components/device_tracker.ritassist.markdown

@@ -0,0 +1,82 @@
+---
+layout: page
+title: "RitAssist"
+description: "Instructions on how to use a RitAssist as a device tracker."
+date: 2018-06-15 22:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: ritassist.png
+ha_category: Presence Detection
+ha_iot_class: Cloud Polling
+ha_release: 0.76
+---
+
+This platform allows you to integrate your vehicles equipped with [RitAssist](https://ritassist.nl/) or [FleetGO](https://fleetgo.com) hardware into Home Assistant. It allows you to see certain details about your vehicle, but also shows your vehicle on the map.
+
+## API key
+To use this component, you need an **API key** and **API secret**, which can be requested by contacting [info@fleetgo.com](mailto:info@fleetgo.com?subject=API%20Key).
+
+## Configuration
+To use this device tracker in your installation, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+device_tracker:
+  - platform: ritassist
+    client_id: YOUR_CLIENT_ID
+    client_secret: YOUR_CLIENT_SECRET
+    username: YOUR_RITASSIST_USERNAME
+    password: YOUR_RITASSIST_PASSWORD
+    include:
+        - LICENSE_PLATE
+```
+
+{% configuration %}
+client_id:
+  description: The client ID used to connect to the RitAssist API.
+  required: true
+  type: string
+client_secret:
+  description: The client secret used to connect to the RitAssist API.
+  required: true
+  type: string
+username:
+  description: Your RitAssist username.
+  required: true
+  type: string
+password:
+  description: Your RitAssist password.
+  required: true
+  type: string
+include:
+  description: A list of license plates to include, if this is not specified, all vehicles will be added.
+  required: false
+  type: strings
+{% endconfiguration %}
+
+See the [device tracker component page](/components/device_tracker/) for instructions on how to configure the people to be tracked.
+
+## Available Attributes
+
+| Attribute | Description |
+|---|---|
+| latitude | The latitude of your vehicle |
+| longitude | The longitude of your vehicle |
+| altitude | Altitude of your vehicle |
+| id | Identifier used to identify your vehicle |
+| make | The make of the vehicle |
+| model | Model of your vehicle |
+| license_plate | License plate number |
+| active | If the engine is currently active or not |
+| odo | The odometer in kilometers |
+| speed | The current speed of your vehicle, in KM/h |
+| last_seen | The date and time when your vehicle last communicated with the API |
+| fuel_level | Fuel level of the vehicle [1] |
+| malfunction_light | Are any malfunction lights burning [1] |
+| coolant_temperature | Temperature of the coolant [1] |
+| power_voltage | Power voltage measured by the hardware [1] |
+| distance_from_home |  How far is your vehicle located from your Home Assistant Home location |
+
+[1] Only available on certain cars and hardware revisions.

source/_components/discovery.markdown

@@ -21,6 +21,7 @@ Home Assistant can discover and automatically configure [zeroconf](https://en.wi
  * [Bose Soundtouch speakers](/components/media_player.soundtouch/)
  * [Denon network receivers](/components/media_player.denonavr/)
  * [DirecTV receivers](/components/media_player.directv/)
+ * [DLNA DMR enabled devices](/components/media_player.dlna_dmr/)
  * [Frontier Silicon internet radios](/components/media_player.frontier_silicon/)
  * [Google Cast](/components/media_player.cast/)
  * [HomeKit](/components/homekit_controller/)
@@ -79,6 +80,7 @@ Valid values for ignore are:
  * `bose_soundtouch`: Bose Soundtouch speakers
  * `denonavr`: Denon network receivers
  * `directv`: DirecTV receivers
+ * `dlna`: DLNA DMR enabled devices
  * `frontier_silicon`: Frontier Silicon internet radios
  * `google_cast`: Google Cast
  * `harmony`: Logitech Harmony Hub

source/_components/fan.dyson.markdown

@@ -22,3 +22,12 @@ You have first to setup the [Dyson component](/components/dyson/)
 
 - Pure Cool link (desk and tower)
 - Pure Hot+cool link (but heating is not yet supported)
+
+### {% linkable_title Attributes %}
+
+The are several attributes that can be useful for automations and templates.
+
+| Attribute | Description |
+| --------- | ----------- |
+| `is_night_mode` | A boolean that indicates if the night mode of the fan device is on.
+| `is_auto_mode` | A boolean that indicates if the auto mode of the fan device is on.

source/_components/fan.velbus.markdown

@@ -1,62 +0,0 @@
----
-layout: page
-title: "Velbus Fans"
-description: "Access and control your Velbus fans."
-date: 2017-06-17 16.58
-sidebar: true
-comments: false
-sharing: true
-footer: true
-logo: velbus.png
-ha_category: Fan
-ha_iot_class: "Local Push"
-ha_release: "0.50"
----
-
-The `velbus` fan allows you to control [Velbus](http://www.velbus.eu) connected fans.
-
-## {% linkable_title Configuration %}
-
-To use your Velbus fans in your installation, add the following to your `configuration.yaml` file:
-
-```yaml
-# Example configuration.yaml entry
-fan:
-  - platform: velbus
-    devices:
-      - name: Fan 1
-        module: 0xda
-        channel_low: 4
-        channel_medium: 3
-        channel_high: 2
-```
-
-{% configuration %}
-devices:
-  description: The list contains the fans to configure.
-  required: true
-  type: map
-  keys:
-    name:
-      description: Name to use in the frontend.
-      required: true
-      type: string
-    module:
-      description: The hexadecimal module address.
-      required: true
-      type: string
-    channel_low:
-      description: The channel number in the module for low-speed.
-      required: true
-      type: string
-    channel_medium:
-      description: The channel number in the module for medium-speed.
-      required: true
-      type: string
-    channel_high:
-      description: The channel number in the module for high-speed.
-      required: true
-      type: string
-{% endconfiguration %}
-
-For hub configuration, see [the Velbus component](/components/velbus/).

source/_components/homematicip_cloud.markdown

@@ -14,17 +14,26 @@ ha_release: 0.66
 featured: false
 ---
 
-The [HomematicIP](http://www.homematic-ip.com) component platform is used as an interface to the cloud server.
+The [HomematicIP](http://www.homematic-ip.com) component platform is used as an interface to the cloud server. Since there is no official documentation about this API, everything was done via reverse engineering. The [homematicip-rest-api](https://github.com/coreGreenberet/homematicip-rest-api) is used for communicating. Use at your own risk.
-For for communication [homematicip-rest-api](https://github.com/coreGreenberet/homematicip-rest-api) is used.
 
-To set up the component:
+## {% linkable_title Setup the component via the frontend %}
 
-- generate the authentication token:
+Menu: *Configuration* -> *Integrations*
-```yaml
+  
-generate_auth_token.py
+Fill the form:
-```
+* Your **access point ID** (SGTIN)
+* Optional a **name** to identify your access point, this will be used to prefix your device names.
+  
+The authentification token will be generated and stored internally.
+
+## {% linkable_title Setup the component using the configuration files %}
+  
+Generate the authentication token:
+  
+`generate_auth_token.py`
+  
+Add the information to your `configuration.yaml` file:
 
-- add the information to your `configuration.yaml` file:
 ```yaml
 homematicip_cloud:
   - accesspoint: IDENTIFIER
@@ -34,11 +43,46 @@ homematicip_cloud:
     authtoken: AUTHTOKEN2
 ```
 
-Configuration variables (global):
+{% configuration %}
+name:
+  required: false
+  description: Name to identify your access point, this will be used to prefix your device names.
+  type: string
+accesspoint:
+  required: true
+  description: This is the access point ID (SGTIN).
+  type: string
+authtoken:
+  required: true
+  description: "Authentication token generated with `generate_auth_token.py`."
+  type: string
+{% endconfiguration %}
 
-- **name** (*Optional*): Name to identify your access point, this will be
+## {% linkable_title Implemented and tested devices %}
-  used to prefix your device names.
-- **accesspoint** (*Required*): This is the access point id (SGTIN)
-- **authtoken** (*Required*): Authentification token generated with
-`generate_auth_token.py`.
 
+- homematicip_cloud.alarm_control_panel
+    - Security zones (*HmIP-SecurityZone*)
+
+- homematicip_cloud.binary_sensor  
+    - Window and door contact (*HmIP-SWDO*)
+    - Smoke sensor and alarm (*HmIP-SWSD*) 
+    - Motion detectors (*HmIP-SMI*)
+    - Motion detectors and push button (*HmIP-SMI55*)
+  
+- homematicip_cloud.climate
+    - Radiator thermostat (*HmIP-eTRV,-2*)
+    - Climate group (*HmIP-HeatingGroup*)
+  
+- homematicip_cloud.light
+    - Switch actuator and meter for brand switches (*HmIP-BSM*)
+    - Dimming actuator for brand switches (*HmIP-BDT*)
+  
+- homematicip_cloud.sensor
+    - Accesspoint duty-cycle (*HmIP-HAP*)
+    - Wall-mounted thermostat (*HmIP-WTH*)
+    - Temperature and humidity sensor (*HmIP-STH*)
+    - Temperature and humidity Sensor with display (*HmIP-STHD*)
+    - Illuminance sensor (*HmIP-SMI, 55*)
+  
+- homematicip_cloud.switch
+    - Pluggable Switch and Meter (*HmIP-PSM*)

source/_components/http.markdown

@@ -87,6 +87,11 @@ login_attempts_threshold:
   required: false
   type: integer
   default: -1
+ssl_profile:
+  description: The [Mozilla SSL profile](https://wiki.mozilla.org/Security/Server_Side_TLS) to use. Only lower if you are experiencing integrations causing SSL handshake errors.
+  required: false
+  type: string
+  default: modern
 {% endconfiguration %}
 
 The sample below shows a configuration entry with possible values:

source/_components/image_processing.facebox.markdown

@@ -24,6 +24,7 @@ MB_KEY="INSERT-YOUR-KEY-HERE"
 
 sudo docker run --name=facebox --restart=always -p 8080:8080 -e "MB_KEY=$MB_KEY"  machinebox/facebox
 ```
+You can run Facebox with a username and password by adding `-e "MB_BASICAUTH_USER=my_username" -e "MB_BASICAUTH_PASS=my_password"` but bare in mind that the component does not encrypt these credentials and this approach does not guarantee security on an unsecured network. 
 
 If you only require face detection (number of faces) you can disable face recognition by adding `-e "MB_FACEBOX_DISABLE_RECOGNITION=true"` to the `docker run` command.
 
@@ -51,6 +52,14 @@ port:
   description: The port which Facebox is exposed on.
   required: true
   type: string
+username:
+  description: The Facebox username if you have set one.
+  required: false
+  type: string
+password:
+  description: The Facebox password if you have set one.
+  required: false
+  type: string
 source:
   description: The list of image sources.
   required: true
@@ -109,24 +118,53 @@ A valid service data example:
 ```
 {% endraw %}
 
-An `image_processing.teach_classifier` event is fired for each service call, providing feedback on whether teaching has been successful or unsuccessful. In the unsuccessful case, the `message` field of the `event_data` will contain information on the cause of failure, and a warning is also published in the logs. An automation can be used to receive alerts on teaching, for example, the following automation will send a notification with the teaching image and a message describing the status of the teaching:
+You can use an automation to receive a notification when you train a face:
+
+{% raw %}
+```yaml
+- id: '1533703568569'
+  alias: Face taught
+  trigger:
+  - event_data:
+      service: facebox_teach_face
+    event_type: call_service
+    platform: event
+  condition: []
+  action:
+  - service: notify.pushbullet
+    data_template:
+      message: '{{ trigger.event.data.service_data.name }} taught 
+      with file {{ trigger.event.data.service_data.file_path }}'
+      title: Face taught notification
+```
+{% endraw %}
+
+Any errors on teaching will be reported in the logs. If you enable [system_log](https://www.home-assistant.io/components/system_log/) events:
 
 ```yaml
-- id: '11200961111'
+system_log:
-  alias: Send facebox teaching result
+  fire_event: true
+```
+
+you can create an automation to receive notifications on Facebox errors:
+
+{% raw %}
+```yaml
+- id: '1533703568577'
+  alias: Facebox error
   trigger:
     platform: event
-    event_type: image_processing.teach_classifier
+    event_type: system_log_event
-    event_data:
+  condition:
-      classifier: facebox
+    condition: template
+    value_template: '{{ "facebox" in trigger.event.data.message }}'
   action:
-    service: notify.platform
+  - service: notify.pushbullet
     data_template:
-      title: Facebox teaching
+      message: '{{ trigger.event.data.message }}'
-      message: Name {{ trigger.event.data.name }} teaching was successful? {{ trigger.event.data.success }}
+      title: Facebox error
-      data:
-        file: ' {{trigger.event.data.file_path}} '
 ```
+{% endraw %}
 
 ## {% linkable_title Optimising resources %}
 

source/_components/light.velbus.markdown

@@ -1,55 +0,0 @@
----
-layout: page
-title: "Velbus lights"
-description: "Access and control your Velbus lights."
-date: 2017-06-17 16.58
-sidebar: true
-comments: false
-sharing: true
-footer: true
-logo: velbus.png
-ha_category: Light
-ha_iot_class: "Local Push"
-ha_release: "0.50"
----
-
-The `velbus` light allows you to control [Velbus](http://www.velbus.eu) lights.
-
-## {% linkable_title Configuration %}
-
-To use your Velbus lights in your installation, add the following to your `configuration.yaml` file:
-
-```yaml
-# Example configuration.yaml entry
-light:
-  - platform: velbus
-    devices:
-      - name: Light 1
-        module: 0xda
-        channel: 4
-      - name: Light 2
-        module: 0xbc
-        channel: 1
-```
-
-{% configuration %}
-devices:
-  description: The list contains the lights to configure.
-  required: true
-  type: map
-  keys:
-    name:
-      description: Name to use in the frontend.
-      required: true
-      type: string
-    module:
-      description: The hexadecimal module address.
-      required: true
-      type: string
-    channel:
-      description: The channel number in the module.
-      required: true
-      type: string
-{% endconfiguration %}
-
-For hub configuration, see [the Velbus component](/components/velbus/).

source/_components/media_player.dlna_dmr.markdown

@@ -0,0 +1,50 @@
+---
+layout: page
+title: "DLNA DMR"
+description: "Instructions on how to integrate a DLNA DMR device into Home Assistant."
+date: 2018-06-01 14:27
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: dlna.png
+ha_category: Media Player
+featured: false
+ha_release: 0.76
+ha_iot_class: "Local Push"
+---
+
+The `dlna_dmr` platform allows you to control a [DLNA Digital Media Renderer](https://www.dlna.org/), such as DLNA enabled TVs or radios.
+
+Please note that some devices, such as Samsung TVs, are rather picky about the source used to play from. The TTS service might not work in combination with these devices. If the play_media service does not work, please try playing from a DLNA/DMS (such as [MiniDLNA](https://sourceforge.net/projects/minidlna/)).
+
+## {% linkable_title Configuration %}
+
+To add a DLNA DMR device to your installation, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+media_player:
+  - platform: dlna_dmr
+    url: http://192.168.0.10:9197/dmr
+```
+
+{% configuration %}
+url:
+  description: The URL to the device description, e.g., `http://192.168.0.10:9197/dmr`.
+  required: true
+  type: string
+listen_ip:
+  description: IP to listen on for events from the device. Only set this when the IP is not detected properly.
+  required: false
+  type: string
+listen_port:
+  description: Port to listen on for events from the device.
+  required: false
+  default: 8301
+  type: int
+name:
+  description: The name you would like to give to the device, e.g., `TV living room`.
+  required: false
+  type: string
+{% endconfiguration %}

source/_components/media_player.pjlink.markdown

@@ -0,0 +1,53 @@
+---
+layout: page
+title: "PJLink"
+description: "Instructions on how to integrate PJLink enabled projectors into Home Assistant."
+date: 2018-06-21 08:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: pjlink.png
+ha_category: Media Player
+ha_release: 0.76
+ha_iot_class: "Local Polling"
+---
+
+The `pjlink` platform allows you to control from Home Assistant, projectors with support for the [PJLink protocol](http://pjlink.jbmia.or.jp/english/index.html).
+
+## {% linkable_title Configuration %}
+
+To add a PJLink projector  to your installation, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+media_player:
+  - platform: pjlink
+    host: 192.168.1.2
+```
+
+{% configuration %}
+host:
+  description: IP address or hostname of the device. Example:`192.168.1.2`.
+  required: true
+  type: string
+port:
+  description: port on which the PJLink service runs on the device.
+  required: false
+  type: int
+  default: 4352
+name:
+  description: Name of the device.
+  required: false
+  type: string
+  default: name of the device as returned by PJLink.
+encoding:
+  description: Character encoding to use to communicate with the device.
+  required: false
+  type: string
+  default: utf-8
+password:
+  description: Password to authenticate with the projector.
+  required: false
+  type: string
+{% endconfiguration %}

source/_components/notify.telstra.markdown

@@ -1,39 +0,0 @@
----
-layout: page
-title: "Telstra"
-description: "Instructions on how to add Telstra API notifications to Home Assistant."
-date: 2016-10-19 10:00
-sidebar: true
-comments: false
-sharing: true
-footer: true
-logo: telstra.png
-ha_category: Notifications
-ha_release: 0.31
----
-
-
-The `telstra` notification platform allows you to deliver Home Assistant notifications to Australian phone numbers over the [Telstra SMS API](https://dev.telstra.com/content/sms-api-0).
-
-To enable the Telstra notifications in your installation, you must first create an account and API app over at [dev.telstra.com](https://dev.telstra.com/). The free tier allows for a maximum of 1000 free messages.
-
-After your API app is approved, add the following to your `configuration.yaml` file:
-
-```yaml
-# Example configuration.yaml entry
-notify:
-  name: NOTIFIER_NAME
-  platform: telstra
-  consumer_key: TELSTRA_API_CONSUMER_KEY_HERE
-  consumer_secret: TELSTRA_API_CONSUMER_SECRET_HERE
-  phone_number: SMS_RECIPIENT_PHONE_NUMBER_HERE
-```
-
-Configuration variables:
-
-- **name** (*Optional*): Setting the optional parameter `name` allows multiple notifiers to be created. The default value is `notify`. The notifier will bind to the service `notify.NOTIFIER_NAME`.
-- **consumer_key** (*Required*): The consumer key of your Telstra API app.
-- **consumer_secret** (*Required*): The consumer secret of your Telstra API app.
-- **phone_number** (*Required*): The phone number of where the notifications will be sent.
-
-To use notifications, please see the [getting started with automation page](/getting-started/automation/).

source/_components/openuv.markdown

@@ -0,0 +1,126 @@
+---
+layout: page
+title: "OpenUV"
+description: "Instructions on how to integrate OpenUV within Home Assistant."
+date: 2018-07-31 22:01
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: openuv.jpg
+ha_category: Hub
+ha_release: 0.76
+ha_iot_class: "Cloud Polling"
+---
+
+The `openuv` component displays UV and Ozone data from
+[openuv.io](http://openuv.io).
+
+## {% linkable_title Generating an API Key %}
+
+To generate an API key, [simply log in to the OpenUV website](https://www.openuv.io/auth/google).
+
+<p class='note warning'>
+The "Limited" plan (which is what new users are given by default) is limited to
+500 API requests per day. In order to leave a buffer, the `openuv` component
+queries the API every 30 minutes by default. This value can be modifed (via the
+`scan_interval` key), but please note that over-running the API will require
+you to upgrade to a paid plan (and may disable your access in the meantime).
+</p>
+
+## {% linkable_title Base Configuration %}
+
+To retrieve data from OpenUV, add the following to your `configuration.yaml`
+file:
+
+```yaml
+openuv:
+  api_key: YOUR_OPENUV_API_KEY
+```
+
+To configure additional functionality, add configuration options beneath
+a `binary_sensor` and/or `sensor` key within the `openuv` section of
+`configuration.yaml` as below:
+
+```yaml
+openuv:
+  api_key: YOUR_OPENUV_API_KEY
+  binary_sensors:
+    # binary sensor configuration options...
+  sensors:
+    # sensor configuration options...
+```
+
+{% configuration %}
+api_key:
+  description: your OpenUV API key
+  required: true
+  type: string
+scan_interval:
+  description: the frequency (in seconds) between data updates
+  required: false
+  type: int
+  default: 1800
+binary_sensors:
+  description: binary sensor-related configuration options
+  required: false
+  type: map
+  keys:
+    monitored_conditions:
+      description: the conditions to create sensors from
+      required: false
+      type: list
+      default: all (`uv_protection_window`)
+sensors:
+  description: sensor-related configuration options
+  required: false
+  type: map
+  keys:
+    monitored_conditions:
+      description: the conditions to create sensors from
+      required: false
+      type: list
+      default: all ( `current_ozone_index`, `current_uv_index`, `max_uv_index`, `safe_exposure_time_type_1`, `safe_exposure_time_type_2`, `safe_exposure_time_type_3`, `safe_exposure_time_type_4`, `safe_exposure_time_type_5`, `safe_exposure_time_type_6` )
+{% endconfiguration %}
+
+## {% linkable_title Binary Sensor Types %}
+
+### {% linkable_title `uv_protection_window` %}
+
+This sensor displays `true` if UV protection (sunscreen, etc.) is recommended
+at the current date and time; displays `false` otherwise.
+
+## {% linkable_title Sensor Types %}
+
+### {% linkable_title `current_ozone_level` %}
+
+This sensor displays the current ozone level in du (Dobson Units).
+
+### {% linkable_title `current_uv_index` %}
+
+This sensor displays the current UV index.
+
+### {% linkable_title `max_uv_index` %}
+
+This sensor displays the maximum UV index that will be encountered that day (at
+solar noon).
+
+### {% linkable_title `safe_exposure_time_type_X` %}
+
+These sensors display the approximate number of minutes a particular skin type
+can be exposed to the sun before burning/tanning starts. Each sensor depicts
+a skin type based on the
+[Fitzpatrick scale](https://en.wikipedia.org/wiki/Fitzpatrick_scale):
+
+* Skin Type I
+* Skin Type II
+* Skin Type III
+* Skin Type IV
+* Skin Type V
+* Skin Type VI
+
+<p class='note warning'>
+The above guidelines constitude estimates and are intended to help informed
+decision making. They should not replace analysis, advice, or diagnosis from a
+trained medical professional.
+</p>

source/_components/sensor.enphase_envoy.markdown

@@ -0,0 +1,55 @@
+---
+layout: page
+title: "Enphase Envoy"
+description: "Instructions on how to setup Enphase Envoy with Home Assistant."
+date: 2018-06-30 12:30
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: enphase-logo.svg
+ha_category: Energy
+ha_release: 0.76
+ha_iot_class: "Local Polling"
+---
+
+A sensor platform for the [Enphase Envoy](https://enphase.com/en-us/products-and-services/envoy) solar energy monitor.
+
+### {% linkable_title Configuration %}
+
+To enable this sensor, add the following lines to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+sensor:
+  - platform: enphase_envoy
+    ip_address: ENVOY_LOCAL_IP_ADDRESS
+```
+
+{% configuration %}
+ip_address:
+  description: The local IP Address of your Envoy
+  required: true
+  type: string
+monitored_conditions:
+  description: The list of conditions to monitor
+  required: false
+  type: list
+  keys:
+    production:
+      description: The power in W being produced by the solar panels
+    daily_production:
+      description: The energy in Wh produced that day
+    7_days_production:
+      description: The energy in Wh produced the last 7 days
+    lifetime_production:
+      description: The energy in Wh produced in the lifetime of the Envoy
+    consumption:
+      description: The power in W being consumed in the whole house
+    daily_consumption:
+      description: The energy in Wh consumed that day
+    7_days_consumption:
+      description: The energy in Wh consumed the last 7 days
+    lifetime_consumption:
+      description: The energy in Wh consumed in the lifetime of the Envoy
+{% endconfiguration %}

source/_components/sensor.opensky.markdown

@@ -31,6 +31,7 @@ Configuration options for the OpenSky Network sensor:
 - **radius** (*Required*): Radius of region to monitor, in kilometers
 - **latitude** (*Optional*): Region latitude (defaults to home zone latitude)
 - **longitude** (*Optional*): Region longitude (defaults to home zone longitude)
+- **altitude** (*Optional*): The maximum altitude(in meters) for planes to be detected in, 0 sets it to unlimited (defaults to 0)
 - **name** (*Optional*): Sensor name (defaults to `opensky`)
 
 ## Events
@@ -42,6 +43,7 @@ Both events have two attributes:
 
 - **sensor**: Name of `opensky` sensor that fired the event
 - **callsign**: Callsign of the flight
+- **altitude**: Altitude of the flight in meters
 
 To receive notifications of the entering flights, add the following lines to your `configuration.yaml`.
 

source/_components/sensor.openuv.markdown

@@ -0,0 +1,23 @@
+---
+layout: page
+title: "OpenUV Sensor"
+description: "Instructions on how to integrate OpenUV sensors within Home Assistant."
+date: 2018-07-31 22:01
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: openuv.jpg
+ha_category: Sensor
+ha_release: 0.76
+ha_iot_class: "Cloud Polling"
+---
+
+The `openuv` sensor platform allows you to view sensor data from
+[OpenUV](http://openuv.io).
+
+<p class='note'>
+You must have the [OpenUV component](/components/openuv/) configured to use
+this platform. After configuring that component, sensors will automatically
+appear.
+</p>

source/_components/sensor.rmvtransport.markdown

@@ -0,0 +1,101 @@
+---
+layout: page
+title: "RMV"
+description: "Instructions on how to integrate Rhein-Main public transport departure times into Home Assistant."
+date: 2018-08-02 22:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: RMV.png
+ha_category: Transport
+ha_release: 0.76
+ha_iot_class: "Cloud Polling"
+---
+
+The `rvmtransport` sensor will give you the departure time of the next bus, tram, subway, or train at the next station or stop in the Rhein-Main area public transport network. Additional details such as the line number and destination are present in the attributes.
+
+## {% linkable_title Configuration %}
+
+To enable this sensor, add the following lines to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+sensor:
+  - platform: rmvtransport
+    next_departure:
+     - station: STATION_OR_STOP_ID
+```
+
+{% configuration %}
+name:
+  description: Name to use in the frontend.
+  required: false
+  default: The default is the station name.
+  type: string
+stationId:
+  description: ID of the stop or station, e.g. 3000010. Visit [the RMV OpenData web site](https://opendata.rmv.de) to find a list of valid IDs.
+  required: true
+  type: string
+destinations:
+  description: "One or multiple final stop names, e.g., 'Frankfurt (Main) Hauptbahnhof' or ['Frankfurt (Main) Hauptbahnhof','Frankfurt (Main) Stadion']. This can be used to only consider a particular direction of travel."
+  required: false
+  type: [string]
+lines:
+  description: "One or more line numbers, e.g., `'S8'` or `['S8', 'RB33', '41']`"
+  required: false
+  default: The default is the station name.
+  type: [string, int]
+products:
+  description: "One or more modes of transport `['U-Bahn', 'Tram', 'Bus', 'S-Bahn', 'RB', 'RE', 'EC', 'IC', 'ICE']`."
+  required: false
+  default: Defaults to all.
+  type: [string]
+time_offset:
+  description: Do not display departures leaving sooner than this number of minutes. Useful if you are a couple of minutes away from the stop.
+  required: false
+  default: The defaults is 0.
+  type: int
+max_journeys:
+  description: Specify the maximal number of journeys.
+  required: false
+  default: The default is 5.
+  type: string
+{% endconfiguration %}
+
+## {% linkable_title Examples %}
+
+### {% linkable_title Full configuration %}
+
+The example below shows a full configuration with three sensors that showcase the various configuration options.
+
+```yaml
+# Example configuration.yaml entry
+sensor:
+  - platform: rmvtransport
+    next_departure:
+      - station: 3000010
+        time_offset: 5
+        destinations:
+          - 'Frankfurt (Main) Flughafen Regionalbahnhof'
+          - 'Frankfurt (Main) Stadion'
+        products:
+          - 'RB'
+          - 'RE'
+          - 'Bus'
+          - 'S'
+      - station: 3006907
+        products: 'Bus'
+        destinations: ['Wiesbaden Dernsches Gelände', 'Mainz Hauptbahnhof']
+        name: Destination
+      - station: 3006904
+        lines: 'S8'
+        max_journeys: 5
+        products: 'S'
+```
+
+The first sensor will return S-Bahn, bus, RB and RE trains departures from Frankfurt Hauptbahnhof to Frankfurt Airport or Stadium that are at least 5 minutes away.
+
+The second sensor returns bus departures from Wiesbaden Hauptbahnhof going to Dernsches Gelände and Mainz Hauptbahnhof. To retrieve the time of the second departure, you would use states.sensor.ENTITY_NAME.attributes.departures[1].time.
+
+The third sensor returns all S-Bahn trains from Mainz Hauptbahnhof for line S8.

source/_components/sensor.waze_travel_time.markdown

@@ -56,4 +56,8 @@ excl_filter:
   description: A substring that has to be NOT present in the description of the selected route (a simple case-insensitive matching).
   required: false
   type: string
+realtime:
+  description: If this is set to false, Waze returns the time estimate, not including current conditions, but rather the average travel time for the current time of day. The parameter defaults to true, meaning Waze will return real-time travel time.
+  required: false
+  type: boolean
 {% endconfiguration %}

source/_components/switch.amcrest.markdown

@@ -16,3 +16,7 @@ ha_iot_class: "Local Polling"
 The `amcrest` switch platform lets you control settings of [Amcrest IP Camera](https://home-assistant.io/components/camera.amcrest/) through Home Assistant.
 
 Switches will be configured automatically. Please refer to the [component](/components/amcrest/) configuration on how to setup.
+
+<p class='note warning'>
+In previous versions, switch devices in setups with multiple cameras, would not have specific entity ID causing them to change randomly after each Home Assistant restart. The current version adds the name of the camera at the end of the switch entity ID, making it more specific and consistent and causes the name option to be required in a multi-camera system. This behavior matches the sensor behavior of the Amcrest component. Because of this, older automations may require updates to the entity ID.
+</p>

source/_components/switch.deconz.markdown

@@ -0,0 +1,27 @@
+---
+layout: page
+title: "deCONZ Switches"
+description: "Instructions on how to integrate Zigbee switches from deCONZ into Home Assistant."
+date: 2018-07-31 23:32
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: deconz.jpeg
+ha_category: Switch
+ha_release: "0.76"
+ha_iot_class: "Local Push"
+---
+
+See the [deCONZ main component](/components/deconz/) for configuration instructions.
+
+Switches are devices like power plugs and sirens.
+
+Note that devices in the switch platform identify as lights, so there is a manually curated list that defines which "lights" are switches.
+
+The `Entity Id` names will be `switch.device_name`, where `device_name` is defined in deCONZ.
+
+#### {% linkable_title Verified supported switches %}
+
+- Innr SP120
+- Osram Outdoor plug

source/_components/switch.velbus.markdown

@@ -15,49 +15,4 @@ ha_release: "0.50"
 
 The `velbus` switch allows you to control [Velbus](http://www.velbus.eu) connected switches.
 
-## {% linkable_title Configuration %}
-
-To use your Velbus switches in your installation, add the following to your `configuration.yaml` file:
-
-```yaml
-# Example configuration.yaml entry
-
-light:
-  - platform: velbus
-    devices:
-      - name: Switch 1
-        type: single
-        module: 0xda
-        channel: 4
-      - name: Switch 2
-        type: double
-        module: 0xbc
-        open_channel: 1
-        close_channel: 2
-```
-
-{% configuration %}
-devices:
-  description: The list contains the switches to configure.
-  required: true
-  type: map
-  keys:
-    name:
-      description: Name to use in the frontend.
-      required: true
-      type: string
-    module:
-      description: The hexadecimal module address.
-      required: true
-      type: string
-    channel:
-      description: The channel number in the module.
-      required: true
-      type: string
-    type:
-      description: "Either `single` or `double`. If single, only `channel` attribute is required. If `double`, both `open_channel:` and `close_channel:` keys are required."
-      required: true
-      type: string
-{% endconfiguration %}
-
 For hub configuration, see [the Velbus component](/components/velbus/).

source/_components/vacuum.markdown

@@ -23,7 +23,7 @@ vacuum:
 
 ### {% linkable_title Component services %}
 
-Available services: `turn_on`, `turn_off`, `start_pause`, `stop`, `return_to_home`, `locate`, `clean_spot`, `set_fanspeed` and `send_command`.
+Available services: `turn_on`, `turn_off`, `start_pause`, `start`, `pause`, `stop`, `return_to_home`, `locate`, `clean_spot`, `set_fanspeed` and `send_command`.
 
 Before calling one of these services, make sure your vacuum platform supports it.
 
@@ -51,6 +51,22 @@ Start, pause or resume a cleaning task.
 |---------------------------|----------|-------------------------------------------------------|
 | `entity_id`               |      yes | Only act on specific vacuum. Else targets all.        |
 
+#### {% linkable_title Service `vacuum.start` %}
+
+Start or resume a cleaning task.
+
+| Service data attribute    | Optional | Description                                           |
+|---------------------------|----------|-------------------------------------------------------|
+| `entity_id`               |      yes | Only act on specific vacuum. Else targets all.        |
+
+#### {% linkable_title Service `vacuum.pause` %}
+
+Pause a cleaning task.
+
+| Service data attribute    | Optional | Description                                           |
+|---------------------------|----------|-------------------------------------------------------|
+| `entity_id`               |      yes | Only act on specific vacuum. Else targets all.        |
+
 #### {% linkable_title Service `vacuum.stop` %}
 
 Stop the current activity of the vacuum.

source/_docs/z-wave/control-panel.markdown

@@ -41,8 +41,6 @@ Since 0.63 and the new experimental [entity registry](/docs/configuration/entity
 * **Replace Failed Node** will replace a failed device with another. If the node is not in the controller's Failed Node List, or the node responds, this command will fail.
 * **Print Node** prints all state of Z-Wave node to the console log
 
-* **Rename Node** sets the name of the `zwave` entity - this won't happen immediately, and requires you to restart Home Assistant (not reboot) to set the new name. Other entities of a device are renamed using the [entity registry](/docs/configuration/entity-registry/).
-
 * **Heal Node** starts healing of the node.(Update neighbor list and update return routes)
 
 * **Test Node** sends no_op test messages to the node. This could in theory bring back a dead node.
@@ -116,7 +114,7 @@ This will display the Z-Wave related information about the node:
 
 ### {% linkable_title Node Values %}
 
-Allows you to rename the entities of the node. For example, maybe for the sensor `front_door`, you want to rename the value `seismic_intensity` to `shake`. The `entity_id` for that sensor will then change from `sensor.front_door_seismic_intensity` to `sensor.front_door_shake`.
+Contains a list of available values of the selected node, and it's instances.
 
 ### {% linkable_title Node group associations %}
 
@@ -142,6 +140,12 @@ You can set the *wakeup* interval (in seconds) of the device, this is shown for
 
 Underneath that you can select any supported configuration parameter to see the current setting. You can then change this and select **Set Config Parameter** to updated it. Battery powered devices will be updated the next time they wake.
 
+### {% linkable_title Node protection %}
+
+If your node has the protection commandclass, you can change the protection level of the node.
+Check your device manual on how to use this setting, as it is different between manufacturers.
+Set the new selection by pressing the **Set Protection** button.
+
 ## {% linkable_title Node user codes %}
 
 If your node has user codes, you can set and delete them. The format is raw hex Ascii code. Below the input you will see your actual code. For normal nodes this is as follows:

source/_posts/2018-08-17-release-76.markdown

@@ -0,0 +1,368 @@
+---
+layout: post
+title: "0.76: Auth almost done, FleetGo, PJLink, RMV public transport"
+description: "The boys and girls in our virtual HQ have been working hard on creating yet another great release."
+date: 2018-08-17 00:01:00
+date_formatted: "August 17, 2018"
+author: Paulus Schoutsen
+author_twitter: balloob
+comments: true
+categories: Release-Notes
+og_image: /images/blog/2018-08-0.76/components.png
+---
+
+<p class='note'>
+This release has a migration, initial startup can take ~20 minutes (depends on size DB)
+</p>
+
+This release includes a database migration to allow us to store context in the database. This will make it possible in the future to introduce attribution. For example, we'll be able to say which user opened the garage door or which automation triggered the party mode at 3am.
+
+<a href='/components/#version/0.76'><img src='/images/blog/2018-08-0.76/components.png' style='border: 0;box-shadow: none;'></a>
+
+The auth system is entering release candidate status 🎉. If nothing major is found, it will be enabled by default starting the next release (0.77) with backwards compatability modus turned on. If you want to get ahead of the pack, you can already easily enable it now:
+
+```yaml
+homeassistant:
+  # add this part
+  auth_providers:
+   - type: homeassistant
+   # uncomment this to enable backwards compatible API password support
+   # - type: legacy_api_password
+```
+
+For iOS users, your frontend should be a lot faster. We had an issue that forced us to serve the frontend in compatability mode, which is slower. We haven't been able to solve [the issue](https://bugs.webkit.org/show_bug.cgi?id=174629), but found a workaround. Race on 🏎.
+
+## {% linkable_title New Platforms %}
+
+- deCONZ - support for power plugs ([@Kane610] - [#15752]) ([deconz docs]) ([light.deconz docs]) ([switch.deconz docs]) (breaking change) (new-platform)
+- RitAssist / FleetGO support ([@depl0y] - [#15780]) ([device_tracker docs]) (new-platform)
+- Add support for OpenUV binary sensors and sensors ([@bachya] - [#15769]) ([openuv docs]) ([binary_sensor.openuv docs]) ([sensor.openuv docs]) (new-platform)
+- Add Enphase Envoy component ([@jesserizzo] - [#15081]) ([sensor.enphase_envoy docs]) (new-platform)
+- Add media_player.dlna_dmr component ([@StevenLooman] - [#14749]) ([media_player.dlna_dmr docs]) (new-platform)
+- Add PJLink media player platform ([@benoitlouy] - [#15083]) ([media_player.pjlink docs]) (new-platform)
+- Add RMV public transport sensor ([@cgtobi] - [#15814]) ([sensor.rmvtransport docs]) (new-platform)
+
+## {% linkable_title New Features %}
+
+- Add and restore context in recorder ([@balloob] - [#15859]) (new-feature)
+
+## {% 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.
+
+<!--more-->
+
+## {% linkable_title Breaking Changes %}
+
+- Keenetic NDMS: user needs to have access to the TelNet interface ([@foxel] - [#15511]) ([device_tracker docs]) (breaking change)
+- openweathermap: wind speed is now correctly in km/h (fixes #15710) ([@fabaff] - [#15740]) ([weather.openweathermap docs]) (breaking change)
+- Remove Telstra notifiy component: This API has been decomissioned on the 31st of May 2018 by Telstra ([@dgomes] - [#15757]) ([notify docs]) (breaking change)
+- deCONZ - support for power plugs. Power plugs that are of type "On/Off plug-in unit" and "Smart plug" (Osram and Innr among others) will now be switches instead of lights. Entities will be found as switch.entity_id instead of light.entity_id. ([@Kane610] - [#15752]) ([deconz docs]) ([light.deconz docs]) ([switch.deconz docs]) (breaking change) (new-platform)
+- HTTP: Make sure use_x_forward_for and trusted_proxies must be configured together ([@awarecan] - [#15804]) ([http docs]) (breaking change)
+- Velbus: Breaking changes include auto-discovery support so that you don't need to specify modules manually anymore in the configuration file, but just load the velbus component which will automatically load the switch and binary_sensor platforms. In addition, the fan and light platforms are removed since these should be modeled with template platform based on velbus switches. ([@thomasdelaet] - [#13742]) ([velbus docs]) ([binary_sensor.velbus docs]) ([switch.velbus docs]) (breaking change)
+- Facebox: Events are no longer fired when a face is taught, as these are unnecessary and the info they convey is already in the logs. ([@robmarkcole] - [#15439]) ([image_processing.facebox docs]) (breaking change)
+- AMCrest switch: Fix for multiple camera switches naming of entity. May change switch entity_id. Please check your automation and update the identity-id if you have previously assigned a name to your camera as it appends the name of the camera to the switch id. ([@rafale77] - [#14028]) ([switch.amcrest docs]) (breaking change)
+- MQTT embedded broker will no longer rely on HTTP API password to automatically configure itself. You need to set own password. ([@awarecan] - [#15929]) ([mqtt docs]) (breaking change) (beta fix)
+- Remove remote.API from core.Config. Might break custom components if they rely on hass.config.api ([@awarecan] - [#15951]) ([http docs]) (breaking change) (beta fix)
+
+## {% linkable_title Beta Fixes %}
+
+- Upgrade pymysensors to 0.17.0 ([@MartinHjelmare] - [#15942]) ([mysensors docs]) (beta fix)
+- Deprecate remote.api ([@balloob] - [#15955]) (beta fix)
+- Added error handling for sense API timeouts ([@kbickar] - [#15789]) ([sensor.sense docs]) (beta fix)
+- Add context to login flow ([@awarecan] - [#15914]) ([auth docs]) (beta fix)
+- MQTT embedded broker has to set its own password. ([@awarecan] - [#15929]) ([mqtt docs]) (breaking change) (beta fix)
+- Fix issue when reading worxlandroid pin code ([@GotoCode] - [#15930]) ([sensor.worxlandroid docs]) (beta fix)
+- remove-phantomjs-from-docker ([@vrih] - [#15936]) (beta fix)
+- Remove remote.API from core.Config ([@awarecan] - [#15951]) ([http docs]) (breaking change) (beta fix)
+- Allow picking intermediate Mozilla cert profile ([@balloob] - [#15957]) ([http docs]) (beta fix)
+- Use JWT for access tokens ([@balloob] - [#15972]) ([auth docs]) ([http docs]) ([websocket_api docs]) (beta fix)
+- Pin crypto ([@balloob] - [#15978]) (beta fix)
+- Teak mqtt error message for 0.76 release ([@awarecan] - [#15983]) ([mqtt docs]) (beta fix)
+- Fix 0.76 beta2 hassio token issue ([@awarecan] - [#15987]) ([hassio docs]) (beta fix)
+- Fix mysensors connection task blocking setup ([@MartinHjelmare] - [#15938]) ([mysensors docs]) (beta fix)
+- Fix Nest async from sync ([@balloob] - [#15997]) ([nest docs]) (beta fix)
+
+## {% linkable_title All changes %}
+
+- Add kodi unique id based on discovery ([@rytilahti] - [#15093]) ([media_player.kodi docs])
+- Better handling of Yi camera being disconnected ([@bachya] - [#15754]) ([camera.yi docs])
+- Decouple login flow view and data entry flow view ([@awarecan] - [#15715]) ([auth docs])
+- Fixed NDMS for latest firmware ([@foxel] - [#15511]) ([device_tracker docs]) (breaking change)
+- Add disallow_untyped_calls to mypy check. ([@andrey-git] - [#15661]) ([persistent_notification docs])
+- Update pyozw to 0.4.9 ([@turbokongen] - [#15758]) ([zwave docs])
+- Convert wind speed to km/h (fixes #15710) ([@fabaff] - [#15740]) ([weather.openweathermap docs]) (breaking change)
+- Round precipitation forecast to 1 decimal place ([@priiduonu] - [#15759]) ([weather.openweathermap docs])
+- Add a "Reviewed by Hound" badge ([@salbertson] - [#15767])
+- Upgrade Mastodon.py to 1.3.1 ([@fabaff] - [#15766]) ([notify docs])
+- This component API has been decomissioned on the 31st of May 2018 by Telstra ([@dgomes] - [#15757]) ([notify docs]) (breaking change)
+- Fix docstrings ([@fabaff] - [#15770])
+- Update pynetgear to 0.4.1 (bugfixes) ([@MatMaul] - [#15768]) ([device_tracker docs])
+- Opensky altitude ([@ioangogo] - [#15273]) ([sensor.opensky docs])
+- Expose internal states and fixed on/off state of Dyson Fans ([@soraxas] - [#15716]) ([fan.dyson docs])
+- deCONZ - support for power plugs ([@Kane610] - [#15752]) ([deconz docs]) ([light.deconz docs]) ([switch.deconz docs]) (breaking change) (new-platform)
+- Add support for STATES of vacuums ([@cnrd] - [#15573]) ([vacuum docs]) ([vacuum.xiaomi_miio docs])
+- Add support for STATE_AUTO of generic_thermostat ([@niklaswa] - [#15678]) ([climate.generic_thermostat docs])
+- Revert "Add support for STATE_AUTO of generic_thermostat (#15678)" ([@awarecan] - [#15783]) ([climate.generic_thermostat docs])
+- RitAssist / FleetGO support ([@depl0y] - [#15780]) ([device_tracker docs]) (new-platform)
+- Add support for OpenUV binary sensors and sensors ([@bachya] - [#15769]) ([openuv docs]) ([binary_sensor.openuv docs]) ([sensor.openuv docs]) (new-platform)
+- Update pymediaroom to 0.6.4 ([@dgomes] - [#15786]) ([media_player.mediaroom docs])
+- Add Enphase Envoy component ([@jesserizzo] - [#15081]) ([sensor.enphase_envoy docs]) (new-platform)
+- Vacuum component: start_pause to individual start and pause commands. ([@cnrd] - [#15751]) ([vacuum docs])
+- Make sure use_x_forward_for and trusted_proxies must config together ([@awarecan] - [#15804]) ([http docs]) (breaking change)
+- Upgrade voluptuous-serialize to 2.0.0 ([@awarecan] - [#15763]) ([config docs])
+- Upgrade pylint to 2.1.0 ([@scop] - [#15811]) ([binary_sensor.bayesian docs]) ([binary_sensor.threshold docs]) ([calendar.todoist docs]) ([light.group docs]) ([sensor.min_max docs]) ([sensor.statistics docs])
+- Upgrade pytest to 3.7.1 and pytest-timeout to 1.3.1 ([@scop] - [#15809])
+- Add support for 2 Tahoma IO awning covers ([@fucm] - [#15660]) ([tahoma docs]) ([cover.tahoma docs])
+- Velbus auto-discovery ([@thomasdelaet] - [#13742]) ([velbus docs]) ([binary_sensor.velbus docs]) ([switch.velbus docs]) (breaking change)
+- Upgrade youtube_dl to 2018.08.04 ([@fabaff] - [#15837]) ([media_extractor docs])
+- Add media_player.dlna_dmr component ([@StevenLooman] - [#14749]) ([media_player.dlna_dmr docs]) (new-platform)
+- Remove 'volume' from return dict ([@mattwing] - [#15842]) ([sensor.alpha_vantage docs])
+- Upgrade shodan to 1.9.0 ([@fabaff] - [#15839]) ([sensor.shodan docs])
+- Add max_gps_accuracy option to Google Maps ([@PrimusNZ] - [#15833]) ([device_tracker docs])
+- Fix bt_home_hub_5 device tracker ([@ahobsonsayers] - [#15096]) ([device_tracker docs])
+- Change to call_service async_stop non-blocking to allow service call finish ([@awarecan] - [#15803])
+- Try to fix coveralls unstable result ([@awarecan] - [#15800])
+- Add different pop 012501 ID ([@turbokongen] - [#15838]) ([zwave docs])
+- Fix error when Series missing 'episodeFileCount' or 'episodeCount' ([@psike] - [#15824]) ([sensor.sonarr docs])
+- Add facebox auth ([@robmarkcole] - [#15439]) ([image_processing.facebox docs]) (breaking change)
+- Upgrade holidays to 0.9.6 ([@fabaff] - [#15831]) ([binary_sensor.workday docs])
+- Upgrade pysnmp to 4.4.5 ([@fabaff] - [#15854]) ([device_tracker docs]) ([sensor.snmp docs]) ([switch.snmp docs])
+- Fix HomeKit test ([@cdce8p] - [#15860])
+- Do not make internet connection during tests ([@balloob] - [#15858])
+- Upgrade pylint to 2.1.1 ([@scop] - [#15872])
+- Upgrade asynctest to 0.12.2 ([@fabaff] - [#15869])
+- Upgrade Sphinx to 1.7.6 ([@fabaff] - [#15868])
+- Upgrade requests_mock to 1.5.2 ([@fabaff] - [#15867])
+- Update based upon forum post ([@DubhAd] - [#15876]) ([device_tracker docs])
+- Upgrade netdisco to 2.0.0 ([@fabaff] - [#15885])
+- Follow changes to netdisco, separating DLNA into DLNA_DMS and DLNA_DMR ([@StevenLooman] - [#15877]) ([media_player.dlna_dmr docs])
+- Upgrade pylast to 2.4.0 ([@fabaff] - [#15886]) ([sensor.lastfm docs])
+- Add auth/authorize endpoint ([@balloob] - [#15887])
+- Upgrade locationsharinglib to 2.0.11 ([@fabaff] - [#15902]) ([device_tracker docs])
+- Refactor data entry flow ([@awarecan] - [#15883])
+- Add HomematicIP Cloud smoke detector device ([@mxworm] - [#15621]) ([binary_sensor.homematicip_cloud docs])
+- Fix for multiple camera switches naming of entity ([@rafale77] - [#14028]) ([switch.amcrest docs]) (breaking change)
+- Add realtime true/false switch for Waze ([@mountainsandcode] - [#15228]) ([sensor.waze_travel_time docs])
+- Add PJLink media player platform ([@benoitlouy] - [#15083]) ([media_player.pjlink docs]) (new-platform)
+- Some typing related fixes ([@scop] - [#15899])
+- Update August component to use py-august:0.6.0 ([@snjoetw] - [#15916]) ([august docs])
+- Misc cleanups ([@scop] - [#15907]) ([device_tracker docs]) ([sensor.irish_rail_transport docs])
+- Update radiotherm to 1.4.1 ([@craftyguy] - [#15910]) ([climate.radiotherm docs])
+- Fix bug in translations upload script ([@armills] - [#15922])
+- Add and restore context in recorder ([@balloob] - [#15859]) (new-feature)
+- Add IndieAuth 4.2.2 redirect uri at client id ([@balloob] - [#15911]) ([auth docs])
+- deCONZ - Add support for sirens ([@Kane610] - [#15896]) ([deconz docs]) ([switch.deconz docs])
+- Add RMV public transport sensor ([@cgtobi] - [#15814]) ([sensor.rmvtransport docs]) (new-platform)
+- :pencil2: Corrects typo in code comments ([@frenck] - [#15923]) ([binary_sensor.homematicip_cloud docs])
+- Upgrade pymysensors to 0.17.0 ([@MartinHjelmare] - [#15942]) ([mysensors docs]) (beta fix)
+- Deprecate remote.api ([@balloob] - [#15955]) (beta fix)
+- Added error handling for sense API timeouts ([@kbickar] - [#15789]) ([sensor.sense docs]) (beta fix)
+- Add context to login flow ([@awarecan] - [#15914]) ([auth docs]) (beta fix)
+- MQTT embedded broker has to set its own password. ([@awarecan] - [#15929]) ([mqtt docs]) (breaking change) (beta fix)
+- Fix issue when reading worxlandroid pin code ([@GotoCode] - [#15930]) ([sensor.worxlandroid docs]) (beta fix)
+- remove-phantomjs-from-docker ([@vrih] - [#15936]) (beta fix)
+- Remove remote.API from core.Config ([@awarecan] - [#15951]) ([http docs]) (breaking change) (beta fix)
+- Allow picking intermediate Mozilla cert profile ([@balloob] - [#15957]) ([http docs]) (beta fix)
+- Use JWT for access tokens ([@balloob] - [#15972]) ([auth docs]) ([http docs]) ([websocket_api docs]) (beta fix)
+- Pin crypto ([@balloob] - [#15978]) (beta fix)
+- Teak mqtt error message for 0.76 release ([@awarecan] - [#15983]) ([mqtt docs]) (beta fix)
+- Fix 0.76 beta2 hassio token issue ([@awarecan] - [#15987]) ([hassio docs]) (beta fix)
+- Fix mysensors connection task blocking setup ([@MartinHjelmare] - [#15938]) ([mysensors docs]) (beta fix)
+- Fix Nest async from sync ([@balloob] - [#15997]) ([nest docs]) (beta fix)
+
+[#13742]: https://github.com/home-assistant/home-assistant/pull/13742
+[#14028]: https://github.com/home-assistant/home-assistant/pull/14028
+[#14749]: https://github.com/home-assistant/home-assistant/pull/14749
+[#15081]: https://github.com/home-assistant/home-assistant/pull/15081
+[#15083]: https://github.com/home-assistant/home-assistant/pull/15083
+[#15093]: https://github.com/home-assistant/home-assistant/pull/15093
+[#15096]: https://github.com/home-assistant/home-assistant/pull/15096
+[#15228]: https://github.com/home-assistant/home-assistant/pull/15228
+[#15273]: https://github.com/home-assistant/home-assistant/pull/15273
+[#15439]: https://github.com/home-assistant/home-assistant/pull/15439
+[#15511]: https://github.com/home-assistant/home-assistant/pull/15511
+[#15573]: https://github.com/home-assistant/home-assistant/pull/15573
+[#15621]: https://github.com/home-assistant/home-assistant/pull/15621
+[#15660]: https://github.com/home-assistant/home-assistant/pull/15660
+[#15661]: https://github.com/home-assistant/home-assistant/pull/15661
+[#15678]: https://github.com/home-assistant/home-assistant/pull/15678
+[#15715]: https://github.com/home-assistant/home-assistant/pull/15715
+[#15716]: https://github.com/home-assistant/home-assistant/pull/15716
+[#15740]: https://github.com/home-assistant/home-assistant/pull/15740
+[#15751]: https://github.com/home-assistant/home-assistant/pull/15751
+[#15752]: https://github.com/home-assistant/home-assistant/pull/15752
+[#15754]: https://github.com/home-assistant/home-assistant/pull/15754
+[#15757]: https://github.com/home-assistant/home-assistant/pull/15757
+[#15758]: https://github.com/home-assistant/home-assistant/pull/15758
+[#15759]: https://github.com/home-assistant/home-assistant/pull/15759
+[#15763]: https://github.com/home-assistant/home-assistant/pull/15763
+[#15766]: https://github.com/home-assistant/home-assistant/pull/15766
+[#15767]: https://github.com/home-assistant/home-assistant/pull/15767
+[#15768]: https://github.com/home-assistant/home-assistant/pull/15768
+[#15769]: https://github.com/home-assistant/home-assistant/pull/15769
+[#15770]: https://github.com/home-assistant/home-assistant/pull/15770
+[#15780]: https://github.com/home-assistant/home-assistant/pull/15780
+[#15783]: https://github.com/home-assistant/home-assistant/pull/15783
+[#15786]: https://github.com/home-assistant/home-assistant/pull/15786
+[#15789]: https://github.com/home-assistant/home-assistant/pull/15789
+[#15800]: https://github.com/home-assistant/home-assistant/pull/15800
+[#15803]: https://github.com/home-assistant/home-assistant/pull/15803
+[#15804]: https://github.com/home-assistant/home-assistant/pull/15804
+[#15809]: https://github.com/home-assistant/home-assistant/pull/15809
+[#15811]: https://github.com/home-assistant/home-assistant/pull/15811
+[#15814]: https://github.com/home-assistant/home-assistant/pull/15814
+[#15824]: https://github.com/home-assistant/home-assistant/pull/15824
+[#15831]: https://github.com/home-assistant/home-assistant/pull/15831
+[#15833]: https://github.com/home-assistant/home-assistant/pull/15833
+[#15837]: https://github.com/home-assistant/home-assistant/pull/15837
+[#15838]: https://github.com/home-assistant/home-assistant/pull/15838
+[#15839]: https://github.com/home-assistant/home-assistant/pull/15839
+[#15842]: https://github.com/home-assistant/home-assistant/pull/15842
+[#15854]: https://github.com/home-assistant/home-assistant/pull/15854
+[#15858]: https://github.com/home-assistant/home-assistant/pull/15858
+[#15859]: https://github.com/home-assistant/home-assistant/pull/15859
+[#15860]: https://github.com/home-assistant/home-assistant/pull/15860
+[#15867]: https://github.com/home-assistant/home-assistant/pull/15867
+[#15868]: https://github.com/home-assistant/home-assistant/pull/15868
+[#15869]: https://github.com/home-assistant/home-assistant/pull/15869
+[#15872]: https://github.com/home-assistant/home-assistant/pull/15872
+[#15876]: https://github.com/home-assistant/home-assistant/pull/15876
+[#15877]: https://github.com/home-assistant/home-assistant/pull/15877
+[#15883]: https://github.com/home-assistant/home-assistant/pull/15883
+[#15885]: https://github.com/home-assistant/home-assistant/pull/15885
+[#15886]: https://github.com/home-assistant/home-assistant/pull/15886
+[#15887]: https://github.com/home-assistant/home-assistant/pull/15887
+[#15896]: https://github.com/home-assistant/home-assistant/pull/15896
+[#15899]: https://github.com/home-assistant/home-assistant/pull/15899
+[#15902]: https://github.com/home-assistant/home-assistant/pull/15902
+[#15907]: https://github.com/home-assistant/home-assistant/pull/15907
+[#15910]: https://github.com/home-assistant/home-assistant/pull/15910
+[#15911]: https://github.com/home-assistant/home-assistant/pull/15911
+[#15914]: https://github.com/home-assistant/home-assistant/pull/15914
+[#15916]: https://github.com/home-assistant/home-assistant/pull/15916
+[#15922]: https://github.com/home-assistant/home-assistant/pull/15922
+[#15923]: https://github.com/home-assistant/home-assistant/pull/15923
+[#15929]: https://github.com/home-assistant/home-assistant/pull/15929
+[#15930]: https://github.com/home-assistant/home-assistant/pull/15930
+[#15936]: https://github.com/home-assistant/home-assistant/pull/15936
+[#15938]: https://github.com/home-assistant/home-assistant/pull/15938
+[#15942]: https://github.com/home-assistant/home-assistant/pull/15942
+[#15951]: https://github.com/home-assistant/home-assistant/pull/15951
+[#15955]: https://github.com/home-assistant/home-assistant/pull/15955
+[#15957]: https://github.com/home-assistant/home-assistant/pull/15957
+[#15972]: https://github.com/home-assistant/home-assistant/pull/15972
+[#15978]: https://github.com/home-assistant/home-assistant/pull/15978
+[#15983]: https://github.com/home-assistant/home-assistant/pull/15983
+[#15987]: https://github.com/home-assistant/home-assistant/pull/15987
+[#15997]: https://github.com/home-assistant/home-assistant/pull/15997
+[@DubhAd]: https://github.com/DubhAd
+[@GotoCode]: https://github.com/GotoCode
+[@Kane610]: https://github.com/Kane610
+[@MartinHjelmare]: https://github.com/MartinHjelmare
+[@MatMaul]: https://github.com/MatMaul
+[@PrimusNZ]: https://github.com/PrimusNZ
+[@StevenLooman]: https://github.com/StevenLooman
+[@ahobsonsayers]: https://github.com/ahobsonsayers
+[@andrey-git]: https://github.com/andrey-git
+[@armills]: https://github.com/armills
+[@awarecan]: https://github.com/awarecan
+[@bachya]: https://github.com/bachya
+[@balloob]: https://github.com/balloob
+[@benoitlouy]: https://github.com/benoitlouy
+[@cdce8p]: https://github.com/cdce8p
+[@cgtobi]: https://github.com/cgtobi
+[@cnrd]: https://github.com/cnrd
+[@craftyguy]: https://github.com/craftyguy
+[@depl0y]: https://github.com/depl0y
+[@dgomes]: https://github.com/dgomes
+[@fabaff]: https://github.com/fabaff
+[@foxel]: https://github.com/foxel
+[@frenck]: https://github.com/frenck
+[@fucm]: https://github.com/fucm
+[@ioangogo]: https://github.com/ioangogo
+[@jesserizzo]: https://github.com/jesserizzo
+[@kbickar]: https://github.com/kbickar
+[@mattwing]: https://github.com/mattwing
+[@mountainsandcode]: https://github.com/mountainsandcode
+[@mxworm]: https://github.com/mxworm
+[@niklaswa]: https://github.com/niklaswa
+[@priiduonu]: https://github.com/priiduonu
+[@psike]: https://github.com/psike
+[@rafale77]: https://github.com/rafale77
+[@robmarkcole]: https://github.com/robmarkcole
+[@rytilahti]: https://github.com/rytilahti
+[@salbertson]: https://github.com/salbertson
+[@scop]: https://github.com/scop
+[@snjoetw]: https://github.com/snjoetw
+[@soraxas]: https://github.com/soraxas
+[@thomasdelaet]: https://github.com/thomasdelaet
+[@turbokongen]: https://github.com/turbokongen
+[@vrih]: https://github.com/vrih
+[august docs]: /components/august/
+[auth docs]: /components/auth/
+[binary_sensor.bayesian docs]: /components/binary_sensor.bayesian/
+[binary_sensor.homematicip_cloud docs]: /components/binary_sensor.homematicip_cloud/
+[binary_sensor.openuv docs]: /components/binary_sensor.openuv/
+[binary_sensor.threshold docs]: /components/binary_sensor.threshold/
+[binary_sensor.velbus docs]: /components/binary_sensor.velbus/
+[binary_sensor.workday docs]: /components/binary_sensor.workday/
+[calendar.todoist docs]: /components/calendar.todoist/
+[camera.yi docs]: /components/camera.yi/
+[climate.generic_thermostat docs]: /components/climate.generic_thermostat/
+[climate.radiotherm docs]: /components/climate.radiotherm/
+[config docs]: /components/config/
+[cover.tahoma docs]: /components/cover.tahoma/
+[deconz docs]: /components/deconz/
+[device_tracker docs]: /components/device_tracker/
+[fan.dyson docs]: /components/fan.dyson/
+[fan.velbus docs]: /components/fan.velbus/
+[hassio docs]: /components/hassio/
+[http docs]: /components/http/
+[image_processing.facebox docs]: /components/image_processing.facebox/
+[light.deconz docs]: /components/light.deconz/
+[light.group docs]: /components/light.group/
+[light.velbus docs]: /components/light.velbus/
+[media_extractor docs]: /components/media_extractor/
+[media_player.dlna_dmr docs]: /components/media_player.dlna_dmr/
+[media_player.kodi docs]: /components/media_player.kodi/
+[media_player.mediaroom docs]: /components/media_player.mediaroom/
+[media_player.pjlink docs]: /components/media_player.pjlink/
+[mqtt docs]: /components/mqtt/
+[mysensors docs]: /components/mysensors/
+[nest docs]: /components/nest/
+[notify docs]: /components/notify/
+[onboarding docs]: /components/onboarding/
+[openuv docs]: /components/openuv/
+[persistent_notification docs]: /components/persistent_notification/
+[sensor.alpha_vantage docs]: /components/sensor.alpha_vantage/
+[sensor.enphase_envoy docs]: /components/sensor.enphase_envoy/
+[sensor.irish_rail_transport docs]: /components/sensor.irish_rail_transport/
+[sensor.lastfm docs]: /components/sensor.lastfm/
+[sensor.min_max docs]: /components/sensor.min_max/
+[sensor.opensky docs]: /components/sensor.opensky/
+[sensor.openuv docs]: /components/sensor.openuv/
+[sensor.rmvtransport docs]: /components/sensor.rmvtransport/
+[sensor.sense docs]: /components/sensor.sense/
+[sensor.shodan docs]: /components/sensor.shodan/
+[sensor.snmp docs]: /components/sensor.snmp/
+[sensor.sonarr docs]: /components/sensor.sonarr/
+[sensor.statistics docs]: /components/sensor.statistics/
+[sensor.waze_travel_time docs]: /components/sensor.waze_travel_time/
+[sensor.worxlandroid docs]: /components/sensor.worxlandroid/
+[switch.amcrest docs]: /components/switch.amcrest/
+[switch.deconz docs]: /components/switch.deconz/
+[switch.snmp docs]: /components/switch.snmp/
+[switch.velbus docs]: /components/switch.velbus/
+[tahoma docs]: /components/tahoma/
+[vacuum docs]: /components/vacuum/
+[vacuum.demo docs]: /components/vacuum.demo/
+[vacuum.xiaomi_miio docs]: /components/vacuum.xiaomi_miio/
+[velbus docs]: /components/velbus/
+[weather.openweathermap docs]: /components/weather.openweathermap/
+[websocket_api docs]: /components/websocket_api/
+[zwave docs]: /components/zwave/

source/images/supported_brands/enphase-logo.svg

@@ -0,0 +1 @@
+<svg id="Layer_1" data-name="Layer 1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 280 54.2"><defs><style>.cls-1{fill:#f37321;}.cls-2{fill:#4c4c4c;}</style></defs><title>Artboard 1</title><path class="cls-1" d="M24.27,52A24.64,24.64,0,0,1,2,37.89a3,3,0,1,1,5.43-2.58,18.66,18.66,0,0,0,33.74,0,3,3,0,1,1,5.44,2.57A24.61,24.61,0,0,1,25.3,52Z"/><path class="cls-1" d="M45.53,29.84H3a3,3,0,0,1,0-6H42.28a18.66,18.66,0,0,0-34.93-5.6A3,3,0,0,1,2,15.43a24.67,24.67,0,0,1,46.52,11.4,3,3,0,0,1-3,3Z"/><path class="cls-2" d="M84.81,37.85H69V29.13H80.23a2.72,2.72,0,1,0,0-5.44H69V16.15H83.66a2.72,2.72,0,1,0,0-5.44H66.31a2.72,2.72,0,0,0-2.72,2.72h0V40.57a2.72,2.72,0,0,0,2.72,2.72h18.5a2.72,2.72,0,0,0,0-5.44Z"/><path class="cls-2" d="M276.28,37.85H260.51V29.13H271.7a2.72,2.72,0,1,0,0-5.44H260.51V16.15h14.63a2.72,2.72,0,1,0,0-5.44H257.79a2.72,2.72,0,0,0-2.72,2.72h0V40.57a2.72,2.72,0,0,0,2.72,2.72h18.49a2.72,2.72,0,1,0,0-5.44Z"/><path class="cls-2" d="M220,39.52l-3.15-7.46h0L208.56,12.4v-.08l-.07-.14-.06-.11-.07-.12-.08-.11-.08-.1-.09-.1-.09-.1-.1-.09-.1-.09-.1-.08-.11-.08-.12-.07-.11-.07-.14-.07h-.09l-.15-.05h-.23a2.7,2.7,0,0,0-.57-.08h-.15a2.7,2.7,0,0,0-.62.09H205l-.13.06-.12.07-.11.07-.12.09-.1.07-.11.09-.09.08-.09.1-.09.1-.08.11-.08.11-.07.12-.06.11-.07.14v.08L195.2,32h0L192,39.52a2.72,2.72,0,1,0,5,2.11l2.45-5.81h13l2.45,5.81a2.72,2.72,0,0,0,5-2.11Zm-18.2-9.13,4.2-10,4.2,10Z"/><path class="cls-2" d="M118.33,43.29h-.69a2.72,2.72,0,0,1-2.14-1L98.6,20.6v20a2.72,2.72,0,0,1-5.44,0V13.43a2.72,2.72,0,0,1,2.72-2.72h.57a2.72,2.72,0,0,1,2.14,1l17,21.8V13.43a2.72,2.72,0,0,1,5.44,0V40.57A2.72,2.72,0,0,1,118.33,43.29Z"/><path class="cls-2" d="M183.49,10.71a2.72,2.72,0,0,0-2.72,2.72h0V23.69H165.26V13.43a2.72,2.72,0,1,0-5.44,0v13h0V40.57a2.72,2.72,0,1,0,5.44,0V29.13h15.51V40.57a2.72,2.72,0,0,0,5.44,0V13.43A2.72,2.72,0,0,0,183.49,10.71Z"/><path class="cls-2" d="M236.25,43.89A16.14,16.14,0,0,1,225,39.37a2.72,2.72,0,0,1,3.84-3.85A10.47,10.47,0,0,0,239,38a4.06,4.06,0,0,0,3.05-3.09c.23-1.53-.6-3-5.4-5l-1.17-.52c-.34-.16-.66-.29-1.13-.48-3-1.22-9.38-3.76-9.26-9.63a8.76,8.76,0,0,1,5.8-8,14.55,14.55,0,0,1,15.27,3.37,2.72,2.72,0,1,1-3.73,4l-.11-.11a9.09,9.09,0,0,0-9.39-2.18,3.32,3.32,0,0,0-2.4,3.09c0,2.11,3.79,3.65,5.85,4.47.6.24,1.12.45,1.54.66l.88.39c2.89,1.24,9.65,4.15,8.63,10.86a9.32,9.32,0,0,1-6.73,7.44A14.27,14.27,0,0,1,236.25,43.89Z"/><path class="cls-2" d="M132.33,43.29a2.72,2.72,0,0,1-2.72-2.72h0V13.43a2.72,2.72,0,0,1,2.72-2.72H143.5c6.09,0,10.5,4.29,10.5,10.16S149.59,31,143.5,31H135v9.54A2.72,2.72,0,0,1,132.33,43.29ZM135,25.6h8.45c3.09,0,5.09-1.86,5.09-4.73s-2-4.73-5.09-4.73H135Z"/></svg>

source/lovelace/changelog.markdown

@@ -9,6 +9,30 @@ sharing: true
 footer: true
 ---
 
+## {% linkable_title Changes in 0.75.0 %}
+
+### Breaking changes 
+- 📣 [glance card]: `turn-on` replaced with `call-service`
+
+### All changes
+- 📣 Add support for CSS imports ❤️
+- 📣 New card type: `conditional-card` ❤️ - Drop your [entity filter card] hacks
+- 📣 [picture glance card]: Add support for custom icons
+- 📣 [picture entity card]: Supports hiding name and/or state
+- 📣 [glance card]: `turn-on` replaced with `call-service`
+- 📣 [glance card]: Allow selectively empty names
+- 📣 [picture elements card]: `state-label` now supports prefix and suffix
+- 📣 [entities card]: Row dividers
+- 📣 [entities card] and [glance card]: Custom icons support
+- 📣 [entities card]: Add call service support to the rows
+- 🔧 [entities card]: Climate entities row available again
+- 🔧 [entities card]: Automation and vacuum are again toggleable
+- 🔧 [entities card]: Weblinks now work
+- 🔧 [entities card]: Groups as toggleable entities fix
+- 🔧 [entities card]: Fixed toggleable state when entity unavailable
+- 🔧 [entities card]: Fix header toggle for entity objects
+- 🔧 [history graph card]: Fix cache of image between views
+
 ## {% linkable_title Changes in 0.74.0 %}
 - ❤️ [Lovelace card gallery](https://home-assistant-lovelace-gallery.netlify.com/)
 - 🔧 Async communication improvements
@@ -48,7 +72,7 @@ footer: true
 ### Cards
 
 - 📣 New card: `map` that allows showing `device_tracker` entities on a map card
-- 📣 `entities` card now support `type: custom:state-card-custom` for the entities list
+- 📣 [entities card] card now support `type: custom:state-card-custom` for the entities list
 
 ## {% linkable_title Changes in 0.73.0 %}
 
@@ -64,12 +88,12 @@ footer: true
 
 ### Cards
 
-- 📣 `picture-entity` allow hiding of infobar using `show_info: false`
+- 📣 [picture entity card] allow hiding of infobar using `show_info: false`
-- 📣 `picture-entity` now supports `tap_action` parameter allowing you to switch from `on`/`off` to `more-info-dialog`
+- 📣 [picture entity card] now supports `tap_action` parameter allowing you to switch from `on`/`off` to `more-info-dialog`
-- 📣 `picture-glance` now supports `navigation_path`
+- 📣 [picture glance card] now supports `navigation_path`
-- `picture-entity` renamed `title` to `name`
+- [picture entity card] renamed `title` to `name`
-- `picture-elements` renamed `path` to `navigation_path`
+- [picture elements card] renamed `path` to `navigation_path`
-- ‼️ `camera-preview` card removed, features added to `picture-entity` and `picture-glance`
+- ‼️ `camera-preview` card removed, features added to [picture entity card] and [picture glance card]
 
 ## {% linkable_title Changes in 0.73.0b3 %}
 
@@ -80,16 +104,16 @@ footer: true
 ### Cards
 
 - 📣 New card: `picture` for triggering navigation and services
-- 📣 `picture-elements` now supports `navigation` type
+- 📣 [picture elements card] now supports `navigation` type
-- 📣 `picture-entity` now supports `camera_image`
+- 📣 [picture entity card] now supports `camera_image`
-- 📣 `picture-glance` now supports `camera_image`
+- 📣 [picture glance card] now supports `camera_image`
-- 📣 `picture-glance` now supports `state_image` and `entity` like `picture-entity`
+- 📣 [picture glance card] now supports `state_image` and `entity` like [picture entity card]
-- 📣 `entity-filter` now supports custom name for entities like `glance` and `entities`
+- 📣 [entity filter card] now supports custom name for entities like `glance` and [entities card]
-- `entities` and `glance` custom titles now use `name` not `title`
+- [entities card] and `glance` custom titles now use `name` not `title`
-- `entity-filter` now uses `entities` as a static list to filter state against
+- [entity filter card] now uses [entities card] as a static list to filter state against
-- `entity-filter` uses `state_filter` array instead of `filter` object
+- [entity filter card] uses `state_filter` array instead of `filter` object
-- 🔧 Fix wrapping and padding for `service-button` in `picture-elements`
+- 🔧 Fix wrapping and padding for `service-button` in [picture elements card]
-- ‼️ `entity-filter` no longer allows to show all entities or a full domain
+- ‼️ [entity filter card] no longer allows to show all entities or a full domain
 
 ## {% linkable_title Changes in 0.73.0b2 %}
 
@@ -101,13 +125,13 @@ footer: true
 
 - `column` renamed to `vertical-stack`
 - `row` renamed to `horizontal-stack`
-- `picture-elements` new `state-badge` using `ha-state-label-badge`
+- [picture elements card] new `state-badge` using `ha-state-label-badge`
-- `picture-elements` renamed `state-badge` to `state-icon`
+- [picture elements card] renamed `state-badge` to `state-icon`
-- `picture-elements` renamed `state-text` to `state-label`
+- [picture elements card] renamed `state-text` to `state-label`
-- `picture-elements` moved/renamed `service.data` to `service_data`
+- [picture elements card] moved/renamed `service.data` to `service_data`
-- `picture-elements` combined `service.domain` and `service.server` into `service`
+- [picture elements card] combined `service.domain` and `service.server` into `service`
-- 📣 `entities` allow custom title just like `glance`
+- 📣 [entities card] allow custom title just like `glance`
-- 📣 `entity-filter` allow auto-hide if empty using `show_empty: false`
+- 📣 [entity filter card] allow auto-hide if empty using `show_empty: false`
 - 🔧 Fix card size calculation `horizontal-stack`/`vertical-stack` 
 
 ## {% linkable_title Changes in 0.73.0b0 %}
@@ -122,14 +146,14 @@ footer: true
 
 ### Cards
 
-- 📣 New card: `picture-elements`
+- 📣 New card: [picture elements card]
 - 📣 New card: `column`
 - 📣 New card: `row`
 - 📣 `glance` allow custom title for entities - rename your entity only in this card
-- 📣 `entities` toggle button in a header can now be hidden using `show_header_toggle: false`
+- 📣 [entities card] toggle button in a header can now be hidden using `show_header_toggle: false`
-- `entity-picture` renamed `picture-entity` to be consistent with `picture-glance`
+- `entity-picture` renamed [picture entity card] to be consistent with [picture glance card]
-- `entity-filter` removed `card_config` and made `card` property an object
+- [entity filter card] removed `card_config` and made `card` property an object
-- 🔧 Fix use of groups in `picture-entity`
+- 🔧 Fix use of groups in [picture entity card]
 - 🔧 Fix the title in `glance` to avoid overlapping
 
 ## {% linkable_title Changes in 0.72.1 %}
@@ -147,4 +171,6 @@ footer: true
 [history graph card]: /lovelace/history-graph/
 [picture glance card]: /lovelace/picture-glance/
 [picture elements card]: /lovelace/picture-elements/
+[picture entity card]: /lovelace/picture-entity/
 [entity filter card]: /lovelace/entity-filter/
+[entities card]: /lovelace/entities/

source/lovelace/tips.markdown

@@ -31,6 +31,10 @@ this tool is to help give you something to start playing with right away.
 The [Lovelace Config Generator][config-generator] by [@thomasloven] provides
 you with the ability to split your Lovelace configuration into multiple files.
 
+### {% linkable_title Lovelace Config Generator (Jinja2 Script) %}
+
+The [Lovelace Jinja2 Script][lovelace-jinja] by [@skalavala] is a simple Jinja2 script that you run in the template editor to generate lovelace configuration based on the entities that are already setup. 
+
 <p class='note'>
   Split configuration is currently possible directly in Lovelace, but it
   is expected to be removed in the near future due to fact that Home Assistant
@@ -54,10 +58,11 @@ mobile browser. (@Toast)
 
 [@dale3h]: https://github.com/dale3h
 [@thomasloven]: https://github.com/thomasloven
-
+[@skalavala]: https://github.com/skalavala
 [config-generator]: https://github.com/thomasloven/homeassistant-lovelace-gen
 [header-stacks]: https://gist.github.com/dale3h/37b34aebb0c336ffd5fb877c2651097a
 [horizontal-stack]: /lovelace/horizontal-stack/
 [migration-script]: https://github.com/dale3h/python-lovelace
 [picture-elements]: /lovelace/picture-elements/
 [vertical-stack]: /lovelace/vertical-stack/
+[lovelace-jinja]: https://sharethelove.io/tools/jinja-magic-scripts