Merge branch 'rc' into current

_config.yml

@@ -141,9 +141,9 @@ social:
 
 # Home Assistant release details
 current_major_version: 0
-current_minor_version: 73
-current_patch_version: 2
-date_released: 2018-07-16
+current_minor_version: 74
+current_patch_version: 0
+date_released: 2018-07-20
 
 # Either # or the anchor link to latest release notes in the blog post.
 # Must be prefixed with a # and have double quotes around it.

source/_components/alarm_control_panel.homematicip_cloud.markdown

@@ -0,0 +1,21 @@
+---
+layout: page
+title: "HomematicIP Cloud Alarm Control Panel"
+description: "Instructions on how to integrate HomematicIP alarm control panel into Home Assistant."
+date: 2018-05-18 22:40
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: homematicip_cloud.png
+ha_category: Sensor
+ha_release: 0.73
+ha_iot_class: "Cloud Push"
+---
+
+The `homematicip_cloud` alarm_control_panel platform allows you to control your [HomematicIP](https://www.homematic-ip.com) `Security Zones` through Home Assistant.
+
+This component will automatically add `Security Zones` configured in your HomematicIP cloud.
+
+Please refer to the
+[component](/components/homematicip_cloud/) configuration on how to setup HomematicIP Cloud.

source/_components/auth.markdown

@@ -0,0 +1,15 @@
+---
+layout: page
+title: "Auth"
+description: "This component is responsible for providing the authentication endpoints."
+date: 2018-03-19 21:04
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: home-assistant.png
+ha_category: Other
+ha_release: 0.73
+---
+
+This component creates the endpoints for the authentication system that is built into Home Assistant. There are no configuration options for this component directly as it relies on the auth system in the core.

source/_components/binary_sensor.hikvision.markdown

@@ -18,7 +18,7 @@ The Hikvision Binary Sensor is a platform that parses the event stream of a [Hik
 The platform will automatically add all sensors to Home Assistant that are configured within the camera/nvr interface to "Notify the surveillance center" as a trigger. If you would like to hide a sensor type you can do so by either unchecking "Notify the surveillance center" in the camera configuration or by using the "ignored" customize option detailed below.
 
 <p class='note'>
-In order for the sensors to work the hikvision user must have the 'Remote: Notify Surveillance Center/Trigger Alarm Output' permission which can be enabled from the user management section of the web interface. Also the 'WEB Authentication' needs to be set to 'digest/basic' in the security/authentication section. 
+In order for the sensors to work the hikvision user must have the 'Remote: Notify Surveillance Center/Trigger Alarm Output' permission which can be enabled from the user management section of the web interface. Also the 'WEB Authentication' needs to be set to 'digest/basic' in the security/authentication section.
 </p>
 
 For example, if you configure a camera with the name "Front Porch" that has motion detection and line crossing events enabled to notify the surveillance center the following binary sensors will be added to Home Assistant:
@@ -44,6 +44,7 @@ This platform should work with all Hikvision cameras and nvrs, and has been conf
 - DS-2CD2032-I
 - DS-2CD2042WD-I
 - DS-2CD2142FWD-I
+- DS-2CD2155FWD-IS
 
 To enable this sensor, the following lines are required in your `configuration.yaml` file:
 

source/_components/camera.push.markdown

@@ -0,0 +1,77 @@
+---
+layout: page
+title: "Push"
+description: "Instructions how to use Push Camera within Home Assistant."
+date: 2018-06-26 23:50
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: camcorder.png
+ha_category: Camera
+ha_iot_class: "Local Push"
+ha_release: 0.74  
+---
+
+The `push` camera platform allows you to integrate images sent over HTTP POST to Home Assistant as a camera. External applications/daemons/scripts are therefore able to "stream" images through Home Assistant.
+
+Optionally the Push Camera can **buffer** a given number of images, creating an animation of the detected motion after the event has been recorded.
+
+Images are cleared on new events, and events are separated by a soft (configurable) **timeout**.
+
+## Integration with motionEye
+
+The `push` camera can as an example be used with [motionEye](https://github.com/ccrisan/motioneye/wiki) a web frontend for the motion daemon. motionEye is usually configured to save/record files ***only*** when motion is detected. It provides a hook to run a command whenever an image is saved, which can be used together with cURL to send the motion detected images to the `push` camera, as shown in this example:
+
+In motionEye, under **File Storage -> Run A Command** type in:
+```bash
+curl -X POST -F "image=@%f" http://my.hass.server.com:8123/api/camera_push/camera.push_camera
+```
+
+Please take note that you might need to add `-H "x-ha-access: YOUR_PASSWORD"` if you have API authentication enabled.
+
+Optionally configure motionEye to save only motion triggered images by going into **Still Images -> Capture Mode** and setting **Motion Triggered**. Tune your preferences under **Motion Detection**.
+
+In this setup, you can configure the push camera to continuously replay the last motion triggered event using a configuration such as:
+
+```yaml
+camera:
+  - platform: push
+    name: MotionEye Outdoor
+    buffer: 3
+    timeout: 5
+```
+
+## {% linkable_title Configuration %}
+
+To enable this camera in your installation, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+camera:
+  - platform: push
+    name: My Push Camera
+```
+
+{% configuration %}
+name:
+  description:  The name you would like to give to the camera.
+  required: false
+  default: Push Camera
+  type: string
+buffer:
+  description: Number of images to buffer per event. Be conservative, large buffers will starve your system memory.
+  required: false
+  default: 1
+  type: string
+timeout:
+  description: Amount of time after which the event is considered to have finished.
+  required: false
+  default: 5 seconds
+  type: time
+field:
+  description: HTTP POST field containing the image file
+  required: false
+  default: image
+  type: string
+{% endconfiguration %}

source/_components/cloudflare.markdown

@@ -0,0 +1,58 @@
+---
+layout: page
+title: "Cloudflare"
+description: "Automatically update your Cloudflare DNS records."
+date: 2018-07-10 20:08
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: cloudflare.png
+ha_category: Utility
+featured: false
+ha_release: 0.74
+---
+
+With the `cloudflare` component can you keep your Cloudflare records up to date.
+
+The component will run every hour, but can also be started manually by using the service `cloudflare.update_records` under services.
+
+## {% linkable_title Setup %}
+
+You will find your global API key in your Cloudflare account settings.
+
+## {% linkable_title Configuration %}
+
+To use the component in your installation, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+cloudflare:
+  email: user@example.com
+  api_key: c2547eb745079dac9320b638f5e225cf483cc5cfdda41
+  zone: example.com
+  records:
+    - bin
+    - www
+```
+
+{% configuration cloudflare %}
+email:
+  description: The email address for your Cloudflare account.
+  required: true
+  type: string
+api_key:
+  description: The global API key for your Cloudflare account.
+  required: true
+  type: string
+zone:
+  description: The DNS zone you want to update.
+  required: true
+  type: string
+records:
+  description: A list of records you want to update.
+  required: true
+  type: list
+{% endconfiguration %}
+
+This platform uses the API from [ipify.org](https://www.ipify.org/) to set the public IP address.

source/_components/image_processing.facebox.markdown

@@ -87,6 +87,47 @@ Use the `image_processing.detect_face` events to trigger automations, and breako
 ```
 {% endraw %}
 
+## {% linkable_title Service `facebox_teach_face` %}
+
+The service `facebox_teach_face` can be used to teach Facebox faces.  
+
+| Service data attribute | Optional | Description |
+| ---------------------- | -------- | ----------- |
+| `entity_id` | no | Entity ID of Facebox entity.
+| `name` | no | The name to associate with a face.
+| `file_path` | no | The path to the image file.
+
+A valid service data example:
+
+{% raw %}
+```yaml
+{
+  "entity_id": "image_processing.facebox_local_file",
+  "name": "superman",
+  "file_path": "/images/superman_1.jpeg"
+}
+```
+{% 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:
+
+```yaml
+- id: '11200961111'
+  alias: Send facebox teaching result
+  trigger:
+    platform: event
+    event_type: image_processing.teach_classifier
+    event_data:
+      classifier: facebox
+  action:
+    service: notify.platform
+    data_template:
+      title: Facebox teaching
+      message: Name {{ trigger.event.data.name }} teaching was successful? {{ trigger.event.data.success }}
+      data:
+        file: ' {{trigger.event.data.file_path}} '
+```
+
 ## {% linkable_title Optimising resources %}
 
-[Image processing components](https://www.home-assistant.io/components/image_processing/) process the image from a camera at a fixed period given by the `scan_interval`. This leads to excessive processing if the image on the camera hasn't changed, as the default `scan_interval` is 10 seconds. You can override this by adding to your config `scan_interval: 10000` (setting the interval to 10,000 seconds), and then call the `image_processing.scan` service when you actually want to perform processing. 
+[Image processing components](https://www.home-assistant.io/components/image_processing/) process the image from a camera at a fixed period given by the `scan_interval`. This leads to excessive processing if the image on the camera hasn't changed, as the default `scan_interval` is 10 seconds. You can override this by adding to your config `scan_interval: 10000` (setting the interval to 10,000 seconds), and then call the `image_processing.scan` service when you actually want to perform processing.

source/_components/light.tuya.markdown

@@ -0,0 +1,23 @@
+---
+layout: page
+title: "Tuya Light"
+description: "Instructions on how to setup the Tuya lights within Home Assistant."
+date: 2018-07-16 09:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: tuya.png
+ha_category: Light
+ha_iot_class: "Cloud Polling"
+ha_release: 0.74
+---
+
+
+The `tuya` light platform allows you to control your [Tuya Smart](https://www.tuya.com) lights.
+
+The platform supports most kinds of Tuya light.
+
+<p class='note'>
+Full configuration details can be found on the main [Tuya component](/components/tuya/) page.
+</p>

source/_components/media_player.denonavr.markdown

@@ -13,7 +13,6 @@ ha_iot_class: "Local Polling"
 ha_release: 0.7.2
 ---
 
-
 The `denonavr` platform allows you to control a [Denon Network Receivers](http://www.denon.co.uk/chg/product/compactsystems/networkmusicsystems/ceolpiccolo) from Home Assistant. It might be that your device is supported by the [Denon] platform.
 
 Supported devices:
@@ -56,18 +55,19 @@ media_player:
 
 Configuration variables:
 
-- **host** (*Optional*): IP address of the device. Example: 192.168.1.32. If not set, auto discovery is used.
-- **name** (*Optional*): Name of the device. If not set, friendlyName of receiver is used.
-- **show_all_sources** (*Optional*): If True all sources are displayed in sources list even if they are marked as deleted in the receiver. If False deleted sources are not displayed (default). Some receivers have a bug that marks all sources as deleted in the interface. In this case this option could help.
+- **host** (*Optional*): IP address of the device. Example: 192.168.1.32. If not set, auto-discovery is used.
+- **name** (*Optional*): Name of the device. If not set, friendlyName of the receiver is used.
+- **show_all_sources** (*Optional*): If True all sources are displayed in sources list even if they are marked as deleted in the receiver. If False deleted sources are not displayed (default). Some receivers have a bug that marks all sources as deleted in the interface. In this case, this option could help.
 - **timeout** (*Optional*): Timeout for HTTP requests to the receiver. Defaults to 2 seconds if not provided.
 - **zones** (*Optional*): List of additional zones to be activated. They are displayed as additional media players with the same functionality Main Zone of the device supports
   - **zone**: Zone which should be activated. Valid options are Zone2 and Zone3
-  - **name** (*Optional*): Name of the zone. If not set the name of the main device + zone as suffix is taken.
+  - **name** (*Optional*): Name of the zone. If not set the name of the main device + zone as a suffix is taken.
 
 A few notes:
 
-- Additional option the control Denon AVR receivers with a builtin web server is using the HTTP interface with denonavr platform.
-- denonavr platform supports some additional functionalities like album covers, custom input source names and auto discovery.
-- Marantz receivers seem to a have quite similar interface. Thus if you own one, give it a try.
+- An additional option for the control of Denon AVR receivers with a built-in web server is using the HTTP interface with `denonavr` platform.
+- The `denonavr` platform supports some additional functionalities like album covers, custom input source names and auto discovery.
+- Marantz receivers seem to a have quite a similar interface. Thus if you own one, give it a try.
+- Sound mode: The command to set a specific sound mode is different from the value of the current sound mode reported by the receiver (sound_mode_raw). There is a key-value structure (sound_mode_dict) that matches the raw sound mode to one of the possible commands to set a sound mode (for instance {'MUSIC':['PLII MUSIC']}. If you get a "Not able to match sound mode" warning, please open an issue on the [denonavr library](https://github.com/scarface-4711/denonavr), stating which raw sound mode could not be matched so it can be added to the matching dictionary. You can find the current raw sound mode under "Development Tools/States" in the front panel.
 
 [Denon]: /components/media_player.denon/

source/_components/sensor.arlo.markdown

@@ -33,6 +33,20 @@ sensor:
       - signal_strength
 ```
 
+Additionally, for Arlo Baby cameras that have additional sensors, you can add them to the `monitored_conditions` collection:
+
+```yaml
+# Additional sensors available for Arlo Baby cameras
+sensor:
+  - platform: arlo
+    monitored_conditions:
+      # ...
+      - temperature
+      - humidity
+      - air_quality
+```
+
+
 Configuration variables:
 
 - **monitored_conditions** array (*Optional*): Conditions to display in the frontend. The following conditions can be monitored.
@@ -41,5 +55,8 @@ Configuration variables:
   - **total_cameras**: Return the number of recognized and active cameras linked on your Arlo account.
   - **battery_level**: Return the battery level of your Arlo camera.
   - **signal_strength**: Return the wireless signal strength of your Arlo camera.
+  - **temperature**: Return the ambient temperature detected by your Arlo Baby camera.
+  - **humidity**: Return the ambient relative humidity detected by your Arlo Baby camera.
+  - **air_quality**: Return the ambient air quality (a reading of volatile organic compounds (VOCs) in parts per million) detected by your Arlo Baby camera.
 
 If no **monitored_conditions** are specified, all of above will be enabled by default.

source/_components/sensor.duke_energy.markdown

@@ -0,0 +1,48 @@
+---
+layout: page
+title: "Duke Energy"
+description: "Instructions on how to set Duke Energy smart meter sensors within Home Assistant."
+date: 2018-07-01 09:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: duke_energy.png
+ha_category: Sensor
+ha_release: "0.73"
+ha_iot_class: "Cloud Polling"
+---
+
+The `duke_energy` sensor platform allows you get the previous days usage for all of your Duke Energy smart meters.
+
+You will only have access to meters listed in your account at [Duke Energy Usage](https://www.duke-energy.com/my-account/usage-analysis).
+
+This supports both electric and gas meters. Along with previous days usage, each sensor will have attributes for the previous bills total usage and average usage.
+
+## {% linkable_title Configuration %}
+
+To enable the sensor, add the following lines to your `configuration.yaml`:
+
+```yaml
+# Example configuration.yaml entry
+sensor:
+  - platform: duke_energy
+    username: YOUR_DUKE_USERNAME
+    password: YOUR_DUKE_PASSWORD
+```
+
+{% configuration %}
+username:
+  description: Your Duke Energy username
+  required: true
+  type: string
+password:
+  description: Your Duke Energy password
+  required: true
+  type: string
+{% endconfiguration %}
+
+
+<p class='note'>
+Meter usage isn't updated until mid-morning. Prior to updating your meter will report 0 for usage starting at midnight. The API is only called to update every 2 hours from startup time.
+</p>

source/_components/sensor.filter.markdown

@@ -68,7 +68,7 @@ filters:
   type: list
   keys:
     filter:
-      description: Algorithm to be used to filter data. Available filters are `lowpass`, `outlier`, `throttle` and `time_simple_moving_average`.
+      description: Algorithm to be used to filter data. Available filters are  `lowpass`, `outlier`, `range`, `throttle` and `time_simple_moving_average`.
       required: true
       type: string
     window_size:
@@ -96,6 +96,16 @@ filters:
       required: false
       type: string
       default: last
+    lower_bound: 
+      description: See [_range_](#range) filter. Lower bound for filter range.
+      required: false
+      type: float
+      default: negative infinity
+    upper_bound: 
+      description: See [_range_](#range) filter. Upper bound for filter range.
+      required: false
+      type: float
+      default: positive infinity
 {% endconfiguration %}
 
 ## {% linkable_title Filters %}
@@ -144,3 +154,19 @@ The Time SMA filter (`time_simple_moving_average`) is based on the paper [Algori
 The paper defines three types/versions of the Simple Moving Average (SMA): *last*, *next* and *linear*. Currently only *last* is implemented.
 
 Theta, as described in the paper, is the `window_size` parameter, and can be expressed using time notation (e.g., 00:05 for a five minutes time window).
+
+### {% linkable_title Range %}
+
+
+The Range filter (`range`) restricts incoming data to a range specified by a lower and upper bound.
+
+All values greater then the upper bound are replaced by the upper bound and all values lower than the lower bound are replaced by the lower bound.
+Per default there are neither upper nor lower bound.
+
+```python
+if new_state > upper_bound:
+    upper_bound
+if new_state < lower_bound:
+    lower_bound
+new_state
+```

source/_components/sensor.fixer.markdown

@@ -18,16 +18,27 @@ The `fixer` sensor will show you the current exchange rate from [Fixer.io](http:
 
 To get an overview about the available [currencies](http://api.fixer.io/latest).
 
+## {% linkable_title Setup %}
+
+You need to create an [API key](https://fixer.io/product). There is a rate limit of 1000 calls per month.
+
+## {% linkable_title Configuration %}
+
 To enable this sensor, add the following lines to your `configuration.yaml` file:
 
 ```yaml
 # Example configuration.yaml entry
 sensor:
   - platform: fixer
+    api_key: YOUR_API_KEY
     target: CHF
 ```
 
 {% configuration %}
+api_key:
+  description: Your API key for [Fixer.io](http://fixer.io/).
+  required: true
+  type: string
 target:
   description: The symbol of the target currency.
   required: true
@@ -37,9 +48,6 @@ name:
   required: false
   type: string
   default: Exchange rate
-base:
-  description: The symbol of the base currency.
-  required: false
-  type: string
-  default: USD
 {% endconfiguration %}
+
+Details about the API are available in the [Fixer.io documentation](https://fixer.io/documentation).

source/_components/sensor.nut.markdown

@@ -65,46 +65,51 @@ sensor:
     type: list
 {% endconfiguration %}
 
-### {% linkable_title Example  %}
+### {% linkable_title Example %}
 
 Given the following example output from NUT (your variables may differ):
 
 ```yaml
-'ups.timer.reboot': '0'
-'battery.voltage': '27.0'
-'ups.firmware.aux': 'L3 -P '
-'ups.mfr': 'American Power Conversion'
-'battery.runtime.low': '120'
-'ups.delay.shutdown': '20'
-'ups.load': '19'
-'ups.realpower.nominal': '600'
-'battery.charge.warning': '50'
-'battery.charge.low': '10'
-'ups.vendorid': '051d'
-'ups.timer.shutdown': '-1'
-'ups.test.result': 'No test initiated'
-'ups.firmware': '868.L3 -P.D'
-'battery.mfr.date': '2015/05/08'
-'ups.serial': '3B1519X19994  '
-'ups.productid': '0002'
-'battery.runtime': '2552'
-'battery.date': '2001/09/25'
-'battery.voltage.nominal': '24.0'
-'battery.type': 'PbAc'
-'ups.mfr.date': '2015/05/08'
-'ups.status': 'OL'
-'ups.model': 'Back-UPS RS1000G'
-'ups.beeper.status': 'disabled'
-'battery.charge': '100'
-'input.sensitivity': 'medium'
-'input.transfer.low': '88'
-'input.transfer.high': '147'
-'input.voltage': '121.0'
-'input.voltage.nominal': '120'
-'input.transfer.reason': 'input voltage out of range'
+$ upsc ups_name@192.168.11.5
+ups.timer.reboot: 0
+battery.voltage: 27.0
+ups.firmware.aux: L3 -P
+ups.mfr: American Power Conversion
+battery.runtime.low: 120
+ups.delay.shutdown: 20
+ups.load: 19
+ups.realpower.nominal: 600
+battery.charge.warning: 50
+battery.charge.low: 10
+ups.vendorid: 051d
+ups.timer.shutdown: -1
+ups.test.result: No test initiated
+ups.firmware: 868.L3 -P.D
+battery.mfr.date: 2015/05/08
+ups.serial: 3B1519X19994
+ups.productid: 0002
+battery.runtime: 2552
+battery.date: 2001/09/25
+battery.voltage.nominal: 24.0
+battery.type: PbAc
+ups.mfr.date: 2015/05/08
+ups.status: OL
+ups.model: Back-UPS RS1000G
+ups.beeper.status: disabled
+battery.charge: 100
+input.sensitivity: medium
+input.transfer.low: 88
+input.transfer.high: 147
+input.voltage: 121.0
+input.voltage.nominal: 120
+input.transfer.reason: input voltage out of range
+output.current: 1.10
+output.frequency: 60.20
+output.voltage: 121.50
+output.voltage.nominal: 120
 ```
 
-Use the values from the left hand column. Support is included for most values with 'ups', 'battery', and 'input' prefixes.
+Use the values from the left hand column. Support is included for most values with 'ups', 'battery', 'input' and 'output' prefixes.
 
 ```yaml
 sensor:

source/_components/sensor.synologydsm.markdown

@@ -36,9 +36,10 @@ sensor:
 Configuration variables:
 
 - **host** (*Required*): The IP address of the Synology NAS to monitor.
-- **port** (*Optional*): The port number on which the Synology NAS is reachable. Defaults to `5000`.
+- **port** (*Optional*): The port number on which the Synology NAS is reachable. Defaults to `5001`.
 - **username** (*Required*): An user to connect to the Synology NAS (a separate account is advised, see the Separate User Configuration section below for details).
 - **password** (*Required*): The password of the user to connect to the Synology NAS.
+- **ssl** (*Optional*): Determine if HTTPS should be used. Defaults to `True` which by default runs on port `5001`.
 - **volumes** (*Optional*): Array of volumes to monitor. Defaults to all volumes.
 - **disks** (*Optional*): Array of disks to monitor. Defaults to all disks.
 - **monitored_conditions** (*Required*): Defines a [template](/topics/templating/) to extract a value from the payload.

source/_components/switch.enocean.markdown

@@ -13,8 +13,7 @@ ha_release: 0.21
 ha_iot_class: "Local Push"
 ---
 
-An EnOcean switch can take many forms. Currently only one type has been tested: Permundo PSC234
-
+An EnOcean switch can take many forms. Currently, only a few types have been tested: Permundo PSC234 and Nod On SIN-2-1-01.
 
 To use your EnOcean device, you first have to set up your [EnOcean hub](/components/enocean/) and then add the following to your `configuration.yaml` file:
 
@@ -29,3 +28,19 @@ Configuration variables:
 
 - **id** (*Required*): The ID of the device. This is a 4 bytes long number.
 - **name** (*Optional*): An identifier for the switch. Default to `EnOcean Switch`.
+- **channel** (*Optional*): The number of the channel (typically 0 or 1) for the output channel to switch. Default to `0`.
+
+```yaml
+# Example entries for a switch with 2 outputs (channels), e.g., the Nod On SIN-2-1-01
+switch nodon01_0:
+  - platform: enocean
+    id: [0x05,0x04,0x03,0x02]
+    name: enocean_nodon01_0
+    channel: 0
+
+switch nodon01_1:
+  - platform: enocean
+    id: [0x05,0x04,0x03,0x02]
+    name: enocean_nodon01_1
+    channel: 1
+```

source/_components/switch.tuya.markdown

@@ -0,0 +1,23 @@
+---
+layout: page
+title: "Tuya Switch"
+description: "Instructions on how to setup the Tuya switch within Home Assistant."
+date: 2018-07-09 09:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: tuya.png
+ha_category: Switch
+ha_iot_class: "Cloud Polling"
+ha_release: 0.74
+---
+
+
+The `tuya` switch platform allows you to control your [Tuya Smart](https://www.tuya.com) switch.
+
+The platform supports switch and socket.
+
+<p class='note'>
+Full configuration details can be found on the main [Tuya component](/components/tuya/) page.
+</p>

source/_components/tuya.markdown

@@ -0,0 +1,51 @@
+---
+layout: page
+title: "Tuya"
+description: "Instructions on how to setup the Tuya hub within Home Assistant."
+date: 2018-07-09 09:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: tuya.png
+ha_category: Hub
+ha_iot_class: "Cloud Polling"
+ha_release: 0.74
+---
+
+The `tuya` component is the main component to integrate all [Tuya Smart](https://www.tuya.com) related platforms. You will need your Tuya account information (username, password and account country code) to discover and control devices which related to your account.
+
+## {% linkable_title Configuration %}
+
+To add your Tuya devices into your Home Assistant installation, add the following to your `configuration.yaml` file:
+
+```yaml
+tuya:
+  username: YOUR_TUYA_USERNAME
+  password: YOUR_TUYA_PASSWORD
+  country_code: YOUR_ACCOUNT_COUNTRYCODE
+```
+
+{% configuration %}
+username:
+  description: Your username to login to Tuya.
+  required: true
+  type: string
+password:
+  description: Your password to login to Tuya.
+  required: true
+  type: string
+country_code:
+  description: Your account country code (i.e.,1 for USA and 86 for China).
+  required: true
+  type: string
+{% endconfiguration %}
+
+## {% linkable_title Service %}
+
+These services are available for the `tuya` component:
+
+- force_update
+- pull_devices
+
+Devices state data and new devices will refresh automatically. If you want to refresh all devices information or get new devices related to your account manually, you can call the `force_update` or `pull_devices` service.

source/_lovelace/entities.markdown

@@ -49,6 +49,10 @@ name:
   required: false
   description: Overwrites friendly name.
   type: string
+secondary_info:
+  required: false
+  description: "Show additional info. Values: `entity-id`, `last-changed`."
+  type: string
 {% endconfiguration %}
 
 ## {% linkable_title Example %}

source/_lovelace/glance.markdown

@@ -30,6 +30,21 @@ title:
   required: false
   description: Card title
   type: string
+show_name:
+  required: false
+  description: Show entity names.
+  type: boolean
+  default: "true"
+show_state:
+  required: false
+  description: Show entity state-text.
+  type: boolean
+  default: "true"
+column_width:
+  required: false
+  description: "Column width as CSS length like `100px` or `calc(100% / 7)`."
+  type: string
+  default: 20%
 {% endconfiguration %}
 
 ## {% linkable_title Options For Entities %}
@@ -45,6 +60,11 @@ name:
   required: false
   description: Overwrites friendly name.
   type: string
+tap_action:
+  required: false
+  description: "Set to `toggle` or `turn-on` for direct actions."
+  type: string
+  default: more-info
 {% endconfiguration %}
 
 ## {% linkable_title Examples %}

source/_lovelace/history-graph.markdown

@@ -24,7 +24,7 @@ type:
   type: string
 entities:
   required: true
-  description: List of entities to graph.
+  description: "A list of entity IDs or `entity` objects, see below."
   type: list
 hours_to_show:
   required: false
@@ -42,6 +42,21 @@ title:
   type: string
 {% endconfiguration %}
 
+## {% linkable_title Options For Entities %}
+
+If you define entities as objects instead of strings, you can add more customization and configuration:
+
+{% configuration %}
+entity:
+  required: true
+  description: Home Assistant entity ID.
+  type: string
+name:
+  required: false
+  description: Overwrites friendly name.
+  type: string
+{% endconfiguration %}
+
 ## {% linkable_title Example %}
 
 ```yaml
@@ -49,5 +64,6 @@ title:
   title: 'My Graph'
   entities:
     - sensor.outside_temperature
-    - media_player.lounge_room
+    - entity: media_player.lounge_room
+      name: Main player
 ```

source/_lovelace/picture-elements.markdown

@@ -40,23 +40,6 @@ title:
 
 ## {% linkable_title Elements %}
 
-### {% linkable_title Navigate to other views %}
-
-{% configuration %}
-type:
-  required: true
-  description: navigation
-  type: string
-navigation_path:
-  required: true
-  description: URL path to another view.
-  type: string
-icon:
-  required: false
-  description: Material Design Icon.
-  type: string
-{% endconfiguration %}
-
 ### {% linkable_title State Badge %}
 
 {% configuration %}
@@ -87,9 +70,21 @@ entity:
   type: string
 tap_action:
   required: false
-  description: "Set to `toggle` to change state"
+  description: more-info, toggle, navigate, call-service
   type: string
   default: more-info
+navigation_path:
+  required: false
+  description: Url path to navigate to (e.g. `/lovelace/1`)
+  type: string
+service:
+  required: false
+  description: "Service to call (e.g. `light.turn_on`)"
+  type: string
+service_data:
+  required: false
+  description: The service data to use.
+  type: object
 style:
   required: true
   description: Position and style the element using CSS.
@@ -107,6 +102,23 @@ entity:
   required: true
   description: Entity id
   type: string
+tap_action:
+  required: false
+  description: more-info, toggle, navigate, call-service
+  type: string
+  default: more-info
+navigation_path:
+  required: false
+  description: Url path to navigate to (e.g. `/lovelace/1`)
+  type: string
+service:
+  required: false
+  description: "Service to call (e.g. `light.turn_on`)"
+  type: string
+service_data:
+  required: false
+  description: The service data to use.
+  type: object
 style:
   required: true
   description: Position and style the element using CSS.
@@ -130,7 +142,7 @@ service:
   type: string
 service_data:
   required: false
-  description: The service data to use."
+  description: The service data to use.
   type: object
 style:
   required: true
@@ -138,7 +150,103 @@ style:
   type: object
 {% endconfiguration %}
 
-## {% linkable_title How-to use the style object %}
+### {% linkable_title Icon Element %}
+
+{% configuration %}
+type:
+  required: true
+  description: icon
+  type: string
+icon:
+  required: true
+  description: Icon to display (e.g. `mdi:home`)
+  type: string
+title:
+  required: false
+  description: Icon tooltip.
+  type: string
+entity:
+  required: false
+  description: Entity to use for more-info/toggle
+  type: string
+tap_action:
+  required: false
+  description: more-info, toggle, navigate, call-service
+  type: string
+  default: more-info
+navigation_path:
+  required: false
+  description: Url path to navigate to (e.g. `/lovelace/1`)
+  type: string
+service:
+  required: false
+  description: "Service to call (e.g. `light.turn_on`)"
+  type: string
+service_data:
+  required: false
+  description: The service data to use.
+  type: object
+style:
+  required: true
+  description: Position and style the element using CSS.
+  type: object
+{% endconfiguration %}
+
+### {% linkable_title Image Element %}
+
+{% configuration %}
+type:
+  required: true
+  description: image
+  type: string
+entity:
+  required: false
+  description: Entity to use for state_image and state_filter and also target for actions. 
+  type: string
+tap_action:
+  required: false
+  description: none, more-info, toggle, navigate, call-service
+  type: string
+  default: more-info
+navigation_path:
+  required: false
+  description: Url path to navigate to (e.g. `/lovelace/1`)
+  type: string
+service:
+  required: false
+  description: "Service to call (e.g. `light.turn_on`)"
+  type: string
+service_data:
+  required: false
+  description: The service data to use.
+  type: object
+image:
+  required: false
+  description: The image to display.
+  type: string
+camera_image:
+  required: false
+  description: A camera entity.
+  type: string
+state_image:
+  required: false
+  description: '[State-based images](#how-to-use-state_image)'
+  type: object
+filter: 
+  required: false
+  description: Default CSS filter
+  type: string
+state_filter:
+  required: false
+  description: '[State-based CSS filters](#how-to-use-state_filter)'
+  type: object
+style:
+  required: true
+  description: Position and style the element using CSS.
+  type: object
+{% endconfiguration %}
+
+## {% linkable_title How to use the style object %}
 
 Position and style your elements using [CSS](https://en.wikipedia.org/wiki/Cascading_Style_Sheets). More/other keys are also possible.
 
@@ -151,6 +259,26 @@ style:
   "--paper-item-icon-color": pink
 ```
 
+## {% linkable_title How to use state_image %}
+
+Specify a different image to display based on the state of the entity.
+
+```yaml
+state_image:
+  "on": /local/living_room_on.jpg
+  "off": /local/living_room_off.jpg
+```
+
+## {% linkable_title How to use state_filter %}
+
+Specify different [CSS filters](https://developer.mozilla.org/en-US/docs/Web/CSS/filter)
+
+```yaml
+state_filter: 
+  'on': brightness(110%) saturate(1.2)
+  'off': brightness(50%) hue-rotate(45deg)
+```
+
 ## {% linkable_title Example %}
 
 ```yaml
@@ -181,5 +309,59 @@ style:
         left: 60%
       service: light.turn_off
       service_data:
-          entity_id: group.all_lights
+        entity_id: group.all_lights
+    - type: icon
+      icon: mdi:home
+      tap_action: navigate
+      navigation_path: /lovelace/0
+      style:
+        top: 10%
+        left: 10%
+      
+       
+```
+
+## {% linkable_title Images Example %}
+
+```yaml
+- type: picture-elements
+  image: /local/floorplan.png
+  elements:
+    # state_image & state_filter - toggle on click
+    - type: image
+      entity: light.living_room
+      tap_action: toggle
+      image: /local/living_room.png
+      state_image: 
+        'off': /local/living_room_off.png
+      filter: saturate(.8)
+      state_filter:
+        'on': brightness(120%) saturate(1.2)
+       style: 
+         top: 25%
+         left: 75%
+         width: 15%
+    # Camera, red border, rounded-rectangle - show more-info on click
+    - type: image
+      entity: camera.driveway_camera
+      camera_image: camera.driveway_camera
+      style: 
+        top: 5%
+        left: 10%
+        width: 10%
+        border: 2px solid red
+        border-radius: 10%
+    # Single image, state_filter - call-service on click
+    - type: image
+      entity: media_player.living_room
+      tap_action: call-service
+      service: media_player.media_play_pause
+      image: /local/television.jpg
+      filter: brightness(5%)
+      state_filter:
+        playing: brightness(100%)
+      style:
+        top: 40%
+        left: 75%
+        width: 5%
 ```

source/_posts/2018-07-21-release-74.markdown

@@ -0,0 +1,401 @@
+---
+layout: post
+title: "0.74: Tuya, Cloudflare DNS, Push Camera and Users UI"
+description: "This release builds on top of the previous release, as that is how releases work."
+date: 2018-07-20 00:01:00
+date_formatted: "July 20, 2018"
+author: Paulus Schoutsen
+author_twitter: balloob
+comments: true
+categories: Release-Notes
+og_image: /images/blog/2018-07-0.74/components.png
+---
+
+It's time for Home Assistant 0.74! 🎉
+
+This week we heard that Guido van Rossum, the founder of Python, is taking a permanent vacation as the leader of Python after being at the helm for almost 30 years. Guido has not been directly involved with Home Assistant. However he created Python and was part of the team that built asyncio, technologies that power the foundation of Home Assistant and what makes us so fast and robust. Under Guido's guidance, the Python community has grown out to be very friendly and open. A great inspiration for us and other tech communities out there. Thanks for all you have done Guido!
+
+<p class='img'>
+<img src='/images/blog/2018-07-0.74/paulus_guido.jpg' alt='Photo of Paulus, founder of Home Assistant, and Guido, founder of Python.'>
+Paulus &amp; Guido at PyCon US 2018
+</p>
+
+All right, back to Home Assistant. The last release introduced a tech preview of the new user system. The initial preview still required creating users via the command line. In the last two weeks, we've worked hard on adding support for an onboarding wizard and a user management interface. A walkthrough of the new features can be found below. Thanks to [@awarecan] and [@jeradM] for all their work!
+
+To try it out today, [read these instructions](https://developers.home-assistant.io/blog/2018/07/02/trying-new-auth.html). The user system is still in tech preview. We've moved fast to get where we are today. The next step is that we need to take a step back and look at the system as a whole to make sure it's robust and ready for prime time.
+
+<div class='videoWrapper'>
+<iframe width="560" height="315" src="https://www.youtube.com/embed/x0VzrizyEmM" frameborder="0" allowfullscreen></iframe>
+</div>
+
+We keep seeing [great examples](https://twitter.com/home_assistant/status/1019579208622845953) of UIs built with Lovelace. Follow us on social media ([FB](https://www.facebook.com/homeassistantio/?ref=bookmarks), [Twitter](https://twitter.com/home_assistant), [G+](https://plus.google.com/+HomeAssistantHomeAutomation)) where we will keep sharing great examples.
+
+For the Lovelace changes in this release, check out the [changelog](/lovelace/changelog/). To help our development and design teams, we've also introduced a [Lovelace card gallery](https://home-assistant-lovelace-gallery.netlify.com/).
+
+Thanks to [@c727], [@jeradM] and [@ciotlosm] for leading this effort ❤️
+
+I'm happy to announce that this release introduces support for Tuya thanks to [@huangyupeng]. Tuya produces cheap cloud-enabled devices that are sold under a wide variety of brand names across the globe, and now they work with Home Assistant too!
+
+## {% linkable_title New Platforms %}
+
+- Add Tuya component and switch support ([@huangyupeng] - [#15399]) ([tuya docs]) ([switch.tuya docs]) (new-platform)
+- Add Tuya light platform ([@huangyupeng] - [#15444]) ([tuya docs]) ([light.tuya docs]) (new-platform)
+- Added support for Duke Energy smart meters ([@w1ll1am23] - [#15165]) ([sensor.duke_energy docs]) (new-platform)
+- Added Push Camera ([@dgomes] - [#15151]) ([camera.push docs]) (new-platform)
+- Add Cloudflare DNS component. ([@ludeeus] - [#15388]) ([cloudflare docs]) (new-platform)
+- Add HomematicIP alarm control panel ([@mxworm] - [#15342]) ([alarm_control_panel docs]) ([homematicip_cloud docs]) ([alarm_control_panel.homematicip_cloud docs]) (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.
+
+<!--more-->
+## {% linkable_title Breaking Changes %}
+
+- Fixer.io has changed their API and now requires an API key. (fixes #14911) ([@fabaff] - [#15279]) ([sensor.fixer docs]) (breaking change)
+- Add support to use HTTPS URLs to SynologyDSM and make it the default ([@tchellomello] - [#15270]) ([sensor.synologydsm docs]) (breaking change)
+- HomeKit Controller: Ignore discovering the HomeKit component and HomeKit devices which offer native local API ([@mjg59] - [#15316]) ([homekit_controller docs]) (breaking change)
+- LimitlessLED will no longer report `hs_color`/`rgb_color` and `color_temp` simultaneously. ([@amelchio] - [#15298]) ([light.limitlessled docs]) (breaking change)
+- IP Ban: Reset failed login attempts counter when login success ([@awarecan] - [#15564]) ([http docs]) ([websocket_api docs]) (breaking change) (beta fix)
+
+## {% linkable_title Beta Fixes %}
+
+- Add current user WS command ([@balloob] - [#15485]) ([auth docs]) ([frontend docs]) (beta fix)
+- Add onboarding support ([@balloob] - [#15492]) ([frontend docs]) ([onboarding docs]) (beta fix)
+- Update HomeKit module code ([@mjg59] - [#15502]) ([homekit_controller docs]) (beta fix)
+- Disallow use insecure_example auth provider in configuration.yml ([@awarecan] - [#15504]) (beta fix)
+- Added WS endpoint for changing homeassistant password. ([@jeradM] - [#15527]) ([config docs]) (beta fix)
+- Don't be so strict client-side ([@balloob] - [#15546]) (beta fix)
+- Decouple emulated hue from http server ([@balloob] - [#15530]) ([emulated_hue docs]) (beta fix)
+- Allow CORS requests to token endpoint ([@balloob] - [#15519]) ([auth docs]) ([http docs]) (beta fix)
+- Upgrade pymysensors to 0.16.0 ([@MartinHjelmare] - [#15554]) ([mysensors docs]) (beta fix)
+- Allow auth providers to influence is_active ([@balloob] - [#15557]) (beta fix)
+- Remove relative time from state machine ([@balloob] - [#15560]) ([sensor.netatmo docs]) (beta fix)
+- Reset failed login attempts counter when login success ([@awarecan] - [#15564]) ([http docs]) ([websocket_api docs]) (breaking change) (beta fix)
+
+## {% linkable_title All changes %}
+
+- deconz: fix light.turn_off with transition ([@lbschenkel] - [#15222]) ([light.deconz docs])
+- Add new RTS device ([@pepeEL] - [#15116]) ([tahoma docs])
+- Add additional parameters to NUT UPS sensor ([@carlchan] - [#15066]) ([sensor.nut docs])
+- Fix typos ([@fabaff] - [#15233]) ([watson_iot docs])
+- Use async syntax for cover platforms ([@cdce8p] - [#15230]) ([cover.lutron_caseta docs]) ([cover.mqtt docs]) ([cover.rflink docs]) ([cover.template docs]) ([cover.wink docs])
+- Upgrade pytest to 3.6.2 ([@scop] - [#15241])
+- Add precipitations to Openweathermap daily forecast mode ([@sgttrs] - [#15240]) ([weather.openweathermap docs])
+- deconz: proper fix light.turn_off with transition ([@lbschenkel] - [#15227]) ([light.deconz docs])
+- allow extra slot values in intents ([@dthulke] - [#15246])
+- Lint cleanups ([@scop] - [#15243]) ([google_assistant docs]) ([sensor.tibber docs])
+- Upgrade sqlalchemy to 1.2.9 ([@fabaff] - [#15250]) ([sensor.sql docs])
+- Upgrade WazeRouteCalculator to 0.6 ([@fabaff] - [#15251]) ([sensor.waze_travel_time docs])
+- Fix typo in Docker files ([@SConaway] - [#15256])
+- Switch to own packaged version of pylgnetcast ([@andrey-git] - [#15042]) ([media_player.lg_netcast docs])
+- Added setting cover tilt position in scene ([@kstaniek] - [#15255])
+- Pass tox posargs to pylint ([@scop] - [#15226])
+- Fix Roomba exception ([@arbreng] - [#15262]) ([vacuum.roomba docs])
+- Added support for Duke Energy smart meters ([@w1ll1am23] - [#15165]) ([sensor.duke_energy docs]) (new-platform)
+- Update image_processing async ([@dgomes] - [#15082]) ([image_processing docs])
+- Fix python-miio 0.4 compatibility of the xiaomi miio device tracker ([@serhtt] - [#15244]) ([device_tracker docs])
+- Upgrade keyring to 13.1.0 ([@fabaff] - [#15268])
+- deCONZ - new sensor attribute 'on' and new sensor GenericFlag ([@Kane610] - [#15247]) ([deconz docs]) ([binary_sensor.deconz docs]) ([sensor.deconz docs])
+- expose climate current temperature in prometeus metrics ([@stenius] - [#15232]) ([prometheus docs])
+- New device to support option MY in somfy ([@pepeEL] - [#15272]) ([cover.tahoma docs])
+- Add isort configuration ([@fabaff] - [#15278])
+- Add support for new API (fixes #14911) ([@fabaff] - [#15279]) ([sensor.fixer docs]) (breaking change)
+- Switch to own packaged version of suds-passworddigest ([@andrey-git] - [#15261]) ([camera.onvif docs])
+- Added Push Camera ([@dgomes] - [#15151]) ([camera.push docs]) (new-platform)
+- Added support to HTTPS URLs on SynologyDSM ([@tchellomello] - [#15270]) ([sensor.synologydsm docs]) (breaking change)
+- Add system generated users ([@balloob] - [#15291]) ([auth docs])
+- Add additional sensors for Arlo Baby camera ([@lukiffer] - [#15074]) ([sensor.arlo docs])
+- Add HomematicIP Cloud Config Flow and Entries loading ([@mxworm] - [#14861]) ([homematicip_cloud docs])
+- Upgrade youtube_dl to 2018.07.04 ([@fabaff] - [#15323]) ([media_extractor docs])
+- Upgrade keyring to 13.2.0 ([@fabaff] - [#15322])
+- Upgrade pytest to 3.6.3 ([@scop] - [#15332])
+- Add original message as dialogflow_query parameter ([@quazzie] - [#15304]) ([dialogflow docs])
+- Add python 3.7 to travis and tox ([@andrey-git] - [#14523])
+- Frontend: Allow overriding default url when added to home screen ([@sjabby] - [#15368]) ([frontend docs])
+- Add HomematicIP Cloud light power consumption and energie attributes ([@mxworm] - [#15343]) ([light.homematicip_cloud docs])
+- fix camera.push API overwrite ([@dgomes] - [#15334]) ([camera.push docs])
+- Add support for multi-channel enocean switches (D2-01-12 profile) ([@NoUsername] - [#14548]) ([enocean docs]) ([switch.enocean docs])
+- Add sound mode support ([@starkillerOG] - [#14910]) ([media_player.denonavr docs])
+- Fixed issue 15340. alexa/smart_home module can now skip properties that aren't supported in the current state, eg lowerSetpoint in Heat mode or targetSetpoint in Eco mode for Nest devices. ([@iliketoprogram14] - [#15352]) ([alexa docs])
+- Efergy ([@fabaff] - [#15380]) ([sensor.efergy docs])
+- Use IndieAuth for client ID ([@balloob] - [#15369]) ([auth docs]) ([frontend docs])
+- Add httplib2 to h.c.google requirements ([@scop] - [#15385]) ([calendar.google docs])
+- Remove some unneeded pylint import-error disables ([@scop] - [#15386]) ([device_tracker docs]) ([eufy docs]) ([light.eufy docs]) ([switch.eufy docs])
+- Update ha-philipsjs to 0.0.5 ([@danielperna84] - [#15378]) ([media_player.philips_js docs])
+- Add new voices to Amazon Polly ([@hanzoh] - [#15320]) ([tts docs])
+- Add Cloudflare DNS component. ([@ludeeus] - [#15388]) ([cloudflare docs]) (new-platform)
+- Add Facebox teach service ([@robmarkcole] - [#14998]) ([image_processing.facebox docs])
+- Expire auth code after 10 minutes ([@balloob] - [#15381]) ([auth docs])
+- Improve NetAtmo sensors update logic ([@glpatcern] - [#14866]) ([sensor.netatmo docs])
+- removed unused return ([@ludeeus] - [#15402]) ([cloudflare docs])
+- Fix confused brightness of xiaomi_aqara gateway light ([@amelchio] - [#15314]) ([light.xiaomi_aqara docs])
+- Fix liveboxplaytv empty channel list ([@pschmitt] - [#15404]) ([media_player.liveboxplaytv docs])
+- Fix credentials lookup ([@balloob] - [#15409])
+- Change Ring binary_sensor frequency polling to avoid rate limit exceeded errors ([@tchellomello] - [#15414]) ([binary_sensor.ring docs])
+- Add Tuya component and switch support ([@huangyupeng] - [#15399]) ([tuya docs]) ([switch.tuya docs]) (new-platform)
+- Fix HomeMatic variables ([@danielperna84] - [#15417]) ([homematic docs])
+- Ignore some HomeKit devices ([@mjg59] - [#15316]) ([homekit_controller docs]) (breaking change)
+- Make LimitlessLED color/temperature attributes mutually exclusive ([@amelchio] - [#15298]) ([light.limitlessled docs]) (breaking change)
+- Add HomematicIP alarm control panel ([@mxworm] - [#15342]) ([alarm_control_panel docs]) ([homematicip_cloud docs]) ([alarm_control_panel.homematicip_cloud docs]) (new-platform)
+- Include request.path in legacy api password warning message ([@awarecan] - [#15438]) ([http docs])
+- Add python 3.8-dev to travis and tox ([@andrey-git] - [#15347])
+- Reorg auth ([@balloob] - [#15443])
+- Make typing checks more strict ([@andrey-git] - [#14429])
+- upgrade-mypy ([@scop] - [#14904])
+- Fix comment formatting ([@balloob] - [#15447]) ([device_tracker docs])
+- User management ([@balloob] - [#15420]) ([auth docs]) ([config docs]) ([http docs]) ([websocket_api docs])
+- More typing ([@andrey-git] - [#15449])
+- Catch the ValueError if the bulb was in the wrong mode ([@fabaff] - [#15434]) ([light.mystrom docs])
+- Upgrade keyring to 13.2.1 ([@fabaff] - [#15453])
+- Fix formatting pylint comments in test ([@balloob] - [#15450])
+- Add HomematicIP Cloud dimmer light device ([@mxworm] - [#15456]) ([light.homematicip_cloud docs])
+- Fix ZWave RGBW lights not producing color without explicit white_value ([@jantman] - [#15412]) ([light.zwave docs])
+- Add IPPassageSensor (HmIP-SPDR) ([@danielperna84] - [#15458]) ([homematic docs])
+- Implement is_on ([@teharris1] - [#15459]) ([switch.insteon_plm docs])
+- Remove unnecessary executable permissions ([@scop] - [#15469]) ([fritzbox docs]) ([climate.fritzbox docs]) ([cover.group docs]) ([sensor.wirelesstag docs]) ([switch.amcrest docs]) ([switch.fritzbox docs])
+- Add Tuya light platform ([@huangyupeng] - [#15444]) ([tuya docs]) ([light.tuya docs]) (new-platform)
+- Update homematicip_cloud with enum states ([@mxworm] - [#15460]) ([homematicip_cloud docs]) ([binary_sensor.homematicip_cloud docs]) ([light.homematicip_cloud docs]) ([sensor.homematicip_cloud docs])
+- Add user via cmd line creates owner ([@balloob] - [#15470]) ([auth docs]) ([http docs])
+- Switch to own packaged version of pygtfs ([@andrey-git] - [#15040]) ([sensor.gtfs docs])
+- Aware comments ([@balloob] - [#15480]) ([auth docs])
+- Fix flux_led turning on with color or effect ([@amelchio] - [#15472]) ([light.flux_led docs])
+- Update limitlessled to 1.1.2 ([@amelchio] - [#15481]) ([light.limitlessled docs])
+- Add current user WS command ([@balloob] - [#15485]) ([auth docs]) ([frontend docs]) (beta fix)
+- Add onboarding support ([@balloob] - [#15492]) ([frontend docs]) ([onboarding docs]) (beta fix)
+- Update HomeKit module code ([@mjg59] - [#15502]) ([homekit_controller docs]) (beta fix)
+- Disallow use insecure_example auth provider in configuration.yml ([@awarecan] - [#15504]) (beta fix)
+- Added WS endpoint for changing homeassistant password. ([@jeradM] - [#15527]) ([config docs]) (beta fix)
+- Don't be so strict client-side ([@balloob] - [#15546]) (beta fix)
+- Decouple emulated hue from http server ([@balloob] - [#15530]) ([emulated_hue docs]) (beta fix)
+- Allow CORS requests to token endpoint ([@balloob] - [#15519]) ([auth docs]) ([http docs]) (beta fix)
+- Upgrade pymysensors to 0.16.0 ([@MartinHjelmare] - [#15554]) ([mysensors docs]) (beta fix)
+- Allow auth providers to influence is_active ([@balloob] - [#15557]) (beta fix)
+- Remove relative time from state machine ([@balloob] - [#15560]) ([sensor.netatmo docs]) (beta fix)
+- Reset failed login attempts counter when login success ([@awarecan] - [#15564]) ([http docs]) ([websocket_api docs]) (breaking change) (beta fix)
+
+[#14429]: https://github.com/home-assistant/home-assistant/pull/14429
+[#14523]: https://github.com/home-assistant/home-assistant/pull/14523
+[#14548]: https://github.com/home-assistant/home-assistant/pull/14548
+[#14861]: https://github.com/home-assistant/home-assistant/pull/14861
+[#14866]: https://github.com/home-assistant/home-assistant/pull/14866
+[#14904]: https://github.com/home-assistant/home-assistant/pull/14904
+[#14910]: https://github.com/home-assistant/home-assistant/pull/14910
+[#14998]: https://github.com/home-assistant/home-assistant/pull/14998
+[#15040]: https://github.com/home-assistant/home-assistant/pull/15040
+[#15042]: https://github.com/home-assistant/home-assistant/pull/15042
+[#15066]: https://github.com/home-assistant/home-assistant/pull/15066
+[#15074]: https://github.com/home-assistant/home-assistant/pull/15074
+[#15082]: https://github.com/home-assistant/home-assistant/pull/15082
+[#15116]: https://github.com/home-assistant/home-assistant/pull/15116
+[#15151]: https://github.com/home-assistant/home-assistant/pull/15151
+[#15165]: https://github.com/home-assistant/home-assistant/pull/15165
+[#15222]: https://github.com/home-assistant/home-assistant/pull/15222
+[#15226]: https://github.com/home-assistant/home-assistant/pull/15226
+[#15227]: https://github.com/home-assistant/home-assistant/pull/15227
+[#15230]: https://github.com/home-assistant/home-assistant/pull/15230
+[#15232]: https://github.com/home-assistant/home-assistant/pull/15232
+[#15233]: https://github.com/home-assistant/home-assistant/pull/15233
+[#15240]: https://github.com/home-assistant/home-assistant/pull/15240
+[#15241]: https://github.com/home-assistant/home-assistant/pull/15241
+[#15243]: https://github.com/home-assistant/home-assistant/pull/15243
+[#15244]: https://github.com/home-assistant/home-assistant/pull/15244
+[#15246]: https://github.com/home-assistant/home-assistant/pull/15246
+[#15247]: https://github.com/home-assistant/home-assistant/pull/15247
+[#15250]: https://github.com/home-assistant/home-assistant/pull/15250
+[#15251]: https://github.com/home-assistant/home-assistant/pull/15251
+[#15255]: https://github.com/home-assistant/home-assistant/pull/15255
+[#15256]: https://github.com/home-assistant/home-assistant/pull/15256
+[#15261]: https://github.com/home-assistant/home-assistant/pull/15261
+[#15262]: https://github.com/home-assistant/home-assistant/pull/15262
+[#15268]: https://github.com/home-assistant/home-assistant/pull/15268
+[#15270]: https://github.com/home-assistant/home-assistant/pull/15270
+[#15272]: https://github.com/home-assistant/home-assistant/pull/15272
+[#15278]: https://github.com/home-assistant/home-assistant/pull/15278
+[#15279]: https://github.com/home-assistant/home-assistant/pull/15279
+[#15291]: https://github.com/home-assistant/home-assistant/pull/15291
+[#15298]: https://github.com/home-assistant/home-assistant/pull/15298
+[#15304]: https://github.com/home-assistant/home-assistant/pull/15304
+[#15314]: https://github.com/home-assistant/home-assistant/pull/15314
+[#15316]: https://github.com/home-assistant/home-assistant/pull/15316
+[#15320]: https://github.com/home-assistant/home-assistant/pull/15320
+[#15322]: https://github.com/home-assistant/home-assistant/pull/15322
+[#15323]: https://github.com/home-assistant/home-assistant/pull/15323
+[#15332]: https://github.com/home-assistant/home-assistant/pull/15332
+[#15334]: https://github.com/home-assistant/home-assistant/pull/15334
+[#15342]: https://github.com/home-assistant/home-assistant/pull/15342
+[#15343]: https://github.com/home-assistant/home-assistant/pull/15343
+[#15347]: https://github.com/home-assistant/home-assistant/pull/15347
+[#15352]: https://github.com/home-assistant/home-assistant/pull/15352
+[#15368]: https://github.com/home-assistant/home-assistant/pull/15368
+[#15369]: https://github.com/home-assistant/home-assistant/pull/15369
+[#15378]: https://github.com/home-assistant/home-assistant/pull/15378
+[#15380]: https://github.com/home-assistant/home-assistant/pull/15380
+[#15381]: https://github.com/home-assistant/home-assistant/pull/15381
+[#15385]: https://github.com/home-assistant/home-assistant/pull/15385
+[#15386]: https://github.com/home-assistant/home-assistant/pull/15386
+[#15388]: https://github.com/home-assistant/home-assistant/pull/15388
+[#15399]: https://github.com/home-assistant/home-assistant/pull/15399
+[#15402]: https://github.com/home-assistant/home-assistant/pull/15402
+[#15404]: https://github.com/home-assistant/home-assistant/pull/15404
+[#15409]: https://github.com/home-assistant/home-assistant/pull/15409
+[#15412]: https://github.com/home-assistant/home-assistant/pull/15412
+[#15414]: https://github.com/home-assistant/home-assistant/pull/15414
+[#15417]: https://github.com/home-assistant/home-assistant/pull/15417
+[#15420]: https://github.com/home-assistant/home-assistant/pull/15420
+[#15434]: https://github.com/home-assistant/home-assistant/pull/15434
+[#15438]: https://github.com/home-assistant/home-assistant/pull/15438
+[#15443]: https://github.com/home-assistant/home-assistant/pull/15443
+[#15444]: https://github.com/home-assistant/home-assistant/pull/15444
+[#15447]: https://github.com/home-assistant/home-assistant/pull/15447
+[#15449]: https://github.com/home-assistant/home-assistant/pull/15449
+[#15450]: https://github.com/home-assistant/home-assistant/pull/15450
+[#15453]: https://github.com/home-assistant/home-assistant/pull/15453
+[#15456]: https://github.com/home-assistant/home-assistant/pull/15456
+[#15458]: https://github.com/home-assistant/home-assistant/pull/15458
+[#15459]: https://github.com/home-assistant/home-assistant/pull/15459
+[#15460]: https://github.com/home-assistant/home-assistant/pull/15460
+[#15469]: https://github.com/home-assistant/home-assistant/pull/15469
+[#15470]: https://github.com/home-assistant/home-assistant/pull/15470
+[#15472]: https://github.com/home-assistant/home-assistant/pull/15472
+[#15480]: https://github.com/home-assistant/home-assistant/pull/15480
+[#15481]: https://github.com/home-assistant/home-assistant/pull/15481
+[#15485]: https://github.com/home-assistant/home-assistant/pull/15485
+[#15492]: https://github.com/home-assistant/home-assistant/pull/15492
+[#15502]: https://github.com/home-assistant/home-assistant/pull/15502
+[#15504]: https://github.com/home-assistant/home-assistant/pull/15504
+[#15519]: https://github.com/home-assistant/home-assistant/pull/15519
+[#15527]: https://github.com/home-assistant/home-assistant/pull/15527
+[#15530]: https://github.com/home-assistant/home-assistant/pull/15530
+[#15546]: https://github.com/home-assistant/home-assistant/pull/15546
+[#15554]: https://github.com/home-assistant/home-assistant/pull/15554
+[#15557]: https://github.com/home-assistant/home-assistant/pull/15557
+[#15560]: https://github.com/home-assistant/home-assistant/pull/15560
+[#15564]: https://github.com/home-assistant/home-assistant/pull/15564
+[@Kane610]: https://github.com/Kane610
+[@MartinHjelmare]: https://github.com/MartinHjelmare
+[@NoUsername]: https://github.com/NoUsername
+[@SConaway]: https://github.com/SConaway
+[@amelchio]: https://github.com/amelchio
+[@andrey-git]: https://github.com/andrey-git
+[@arbreng]: https://github.com/arbreng
+[@awarecan]: https://github.com/awarecan
+[@balloob]: https://github.com/balloob
+[@carlchan]: https://github.com/carlchan
+[@cdce8p]: https://github.com/cdce8p
+[@danielperna84]: https://github.com/danielperna84
+[@dgomes]: https://github.com/dgomes
+[@dthulke]: https://github.com/dthulke
+[@fabaff]: https://github.com/fabaff
+[@glpatcern]: https://github.com/glpatcern
+[@hanzoh]: https://github.com/hanzoh
+[@huangyupeng]: https://github.com/huangyupeng
+[@iliketoprogram14]: https://github.com/iliketoprogram14
+[@jantman]: https://github.com/jantman
+[@jeradM]: https://github.com/jeradM
+[@c727]: https://github.com/c727
+[@ciotlosm]: https://github.com/ciotlosm
+[@kstaniek]: https://github.com/kstaniek
+[@lbschenkel]: https://github.com/lbschenkel
+[@ludeeus]: https://github.com/ludeeus
+[@lukiffer]: https://github.com/lukiffer
+[@mjg59]: https://github.com/mjg59
+[@mxworm]: https://github.com/mxworm
+[@pepeEL]: https://github.com/pepeEL
+[@pschmitt]: https://github.com/pschmitt
+[@quazzie]: https://github.com/quazzie
+[@robmarkcole]: https://github.com/robmarkcole
+[@scop]: https://github.com/scop
+[@serhtt]: https://github.com/serhtt
+[@sgttrs]: https://github.com/sgttrs
+[@sjabby]: https://github.com/sjabby
+[@starkillerOG]: https://github.com/starkillerOG
+[@stenius]: https://github.com/stenius
+[@tchellomello]: https://github.com/tchellomello
+[@teharris1]: https://github.com/teharris1
+[@w1ll1am23]: https://github.com/w1ll1am23
+[alarm_control_panel docs]: /components/alarm_control_panel/
+[alarm_control_panel.homematicip_cloud docs]: /components/alarm_control_panel.homematicip_cloud/
+[alexa docs]: /components/alexa/
+[auth docs]: /components/auth/
+[binary_sensor.deconz docs]: /components/binary_sensor.deconz/
+[binary_sensor.homematicip_cloud docs]: /components/binary_sensor.homematicip_cloud/
+[binary_sensor.ring docs]: /components/binary_sensor.ring/
+[calendar.google docs]: /components/calendar.google/
+[camera.onvif docs]: /components/camera.onvif/
+[camera.push docs]: /components/camera.push/
+[climate.fritzbox docs]: /components/climate.fritzbox/
+[cloudflare docs]: /components/cloudflare/
+[config docs]: /components/config/
+[cover.group docs]: /components/cover.group/
+[cover.lutron_caseta docs]: /components/cover.lutron_caseta/
+[cover.mqtt docs]: /components/cover.mqtt/
+[cover.rflink docs]: /components/cover.rflink/
+[cover.tahoma docs]: /components/cover.tahoma/
+[cover.template docs]: /components/cover.template/
+[cover.velbus docs]: /components/cover.velbus/
+[cover.wink docs]: /components/cover.wink/
+[deconz docs]: /components/deconz/
+[device_tracker docs]: /components/device_tracker/
+[dialogflow docs]: /components/dialogflow/
+[emulated_hue docs]: /components/emulated_hue/
+[enocean docs]: /components/enocean/
+[eufy docs]: /components/eufy/
+[fritzbox docs]: /components/fritzbox/
+[frontend docs]: /components/frontend/
+[google docs]: /components/google/
+[google_assistant docs]: /components/google_assistant/
+[homekit_controller docs]: /components/homekit_controller/
+[homematic docs]: /components/homematic/
+[homematicip_cloud docs]: /components/homematicip_cloud/
+[http docs]: /components/http/
+[image_processing docs]: /components/image_processing/
+[image_processing.facebox docs]: /components/image_processing.facebox/
+[light.deconz docs]: /components/light.deconz/
+[light.eufy docs]: /components/light.eufy/
+[light.flux_led docs]: /components/light.flux_led/
+[light.homematicip_cloud docs]: /components/light.homematicip_cloud/
+[light.limitlessled docs]: /components/light.limitlessled/
+[light.mystrom docs]: /components/light.mystrom/
+[light.tuya docs]: /components/light.tuya/
+[light.xiaomi_aqara docs]: /components/light.xiaomi_aqara/
+[light.zwave docs]: /components/light.zwave/
+[media_extractor docs]: /components/media_extractor/
+[media_player.denonavr docs]: /components/media_player.denonavr/
+[media_player.lg_netcast docs]: /components/media_player.lg_netcast/
+[media_player.liveboxplaytv docs]: /components/media_player.liveboxplaytv/
+[media_player.philips_js docs]: /components/media_player.philips_js/
+[mysensors docs]: /components/mysensors/
+[onboarding docs]: /components/onboarding/
+[prometheus docs]: /components/prometheus/
+[sensor.arlo docs]: /components/sensor.arlo/
+[sensor.deconz docs]: /components/sensor.deconz/
+[sensor.duke_energy docs]: /components/sensor.duke_energy/
+[sensor.efergy docs]: /components/sensor.efergy/
+[sensor.fixer docs]: /components/sensor.fixer/
+[sensor.gtfs docs]: /components/sensor.gtfs/
+[sensor.homematicip_cloud docs]: /components/sensor.homematicip_cloud/
+[sensor.netatmo docs]: /components/sensor.netatmo/
+[sensor.nut docs]: /components/sensor.nut/
+[sensor.sql docs]: /components/sensor.sql/
+[sensor.synologydsm docs]: /components/sensor.synologydsm/
+[sensor.tibber docs]: /components/sensor.tibber/
+[sensor.waze_travel_time docs]: /components/sensor.waze_travel_time/
+[sensor.wirelesstag docs]: /components/sensor.wirelesstag/
+[switch.amcrest docs]: /components/switch.amcrest/
+[switch.enocean docs]: /components/switch.enocean/
+[switch.eufy docs]: /components/switch.eufy/
+[switch.fritzbox docs]: /components/switch.fritzbox/
+[switch.insteon_plm docs]: /components/switch.insteon_plm/
+[switch.tuya docs]: /components/switch.tuya/
+[tahoma docs]: /components/tahoma/
+[tts docs]: /components/tts/
+[tuya docs]: /components/tuya/
+[vacuum.roomba docs]: /components/vacuum.roomba/
+[watson_iot docs]: /components/watson_iot/
+[weather.openweathermap docs]: /components/weather.openweathermap/
+[websocket_api docs]: /components/websocket_api/

source/lovelace/changelog.markdown

@@ -9,6 +9,22 @@ sharing: true
 footer: true
 ---
 
+## {% linkable_title Changes in 0.74.0b0 %}
+
+### Views
+- Add basic support for `badges` like in old view style
+- Custom cards now work with `panel: true`
+
+### Cards
+- 📣 [glance card]: Entity `tap_action` can now be `toggle` and `turn-on` besides the default of showing the more info dialog
+- 📣 [glance card]: Support added to hide `name` or `state`
+- 📣 [history graph card]: Support added to override entity names
+- 📣 [picture glance card]: Support added to open the more info dialog for cameras and media players.
+- 📣 [picture elements card]: Support new element type `image`
+- 📣 [picture elements card]: Support new element type `service-icon`
+- 🔧 [entity filter card]: Fix edge cases that could make it crash ([supports this new use case](https://github.com/home-assistant/ui-schema/issues/82))
+- 🔧 [picture glance card]: Fix crash when the state of entity was unavailable
+
 ## {% linkable_title Changes in 0.73.1 %}
 
 - Setting Lovelace as default now updates `Overview` button to point to `/lovelace`
@@ -111,3 +127,9 @@ footer: true
 ## {% linkable_title Changes in 0.72 %}
 
 - Initial release of the Lovelace UI
+
+[glance card]: /lovelace/glance/
+[history graph card]: /lovelace/history-graph/
+[picture glance card]: /lovelace/picture-glance/
+[picture elements card]: /lovelace/picture-elements/
+[entity filter card]: /lovelace/entity-filter/

source/lovelace/index.markdown

@@ -45,6 +45,8 @@ Create a new file `<config>/ui-lovelace.yaml` and add the following content. Adj
 
 ```yaml
 title: My Awesome Home
+# Optional background for all views. Check https://developer.mozilla.org/en-US/docs/Web/CSS/background for more examples.
+background: center / cover no-repeat url("/background.png") fixed
 # Exclude entities from "Unused entities" view
 excluded_entities:
   - weblink.router
@@ -53,7 +55,9 @@ views:
   - title: Example
     # Optional unique id for direct access /lovelace/${id}
     id: example
-    # Each view can have a different theme applied.
+    # Optional background (overwrites the global background).
+    background: radial-gradient(crimson, skyblue)
+    # Each view can have a different theme applied. Theme should be defined in the frontend.
     theme: dark-mode
     # The cards to show on this view.
     cards:

source/lovelace/views.markdown

@@ -26,8 +26,12 @@ views:
       required: true
       description: The title or name.
       type: string
+    badges:
+      required: false
+      description: List of entities IDs to display as badge.
+      type: list
     cards:
-      required: true
+      required: false
       description: Cards to display in this view.
       type: list
     id: