jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-15 13:26:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'rc' into current

Browse Source
This commit is contained in:
Paulus Schoutsen 2018-08-03 17:40:39 +02:00
commit 4f491d350c
67 changed files with 1502 additions and 195 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
_config.yml
View File

@ -141,14 +141,14 @@ social:
# Home Assistant release details
current_major_version: 0
current_minor_version: 74
current_patch_version: 1
date_released: 2018-07-24
current_minor_version: 75
current_patch_version: 0
date_released: 2018-08-03
# 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-0741---july-24"
patch_version_notes: "#"
# Minor release (Example #release-0431---april-25):
# Date we moved to Discourse for comments

4
source/_components/alarmdecoder.markdown
View File

@ -54,4 +54,6 @@ Configuration variables:
- **baudrate** (*Optional*): The baud rate of the AlarmDecoder device, if using serial type. Default: `115200`
- **panel_display** (*Optional*): Create a sensor called sensor.alarm_display to match the Alarm Keypad display. Default: `off`
- **zones** (*Optional*): AlarmDecoder has no way to tell us which zones are actually in use, so each zone must be configured in Home Assistant. For each zone, at least a name must be given. For more information on the available zone types, take a look at the [Binary Sensor](/components/binary_sensor.alarmdecoder/) docs. *Note: If no zones are specified, Home Assistant will not load any binary_sensor components.*
- **rfid** (*Optional*): The RF serial-number associated with RF zones. Providing this field allows Home Assistant to associate raw sensor data to a given zone, allowing direct monitoring of the state, battery, and supervision status.
- **rfid** (*Optional*): The RF serial-number associated with RF zones. Providing this field allows Home Assistant to associate raw sensor data to a given zone, allowing direct monitoring of the state, battery, and supervision status.
- **relayaddr** (*Optional*): Address of the relay expander board to associate with the zone. (ex: 12, 13, 14, or 15). Typically used in cases where a panel will not send bypassed zones such as motion during an armed home state, the Vista 20P is an example of this. Alarmdecoder can emulate a zone expander board and the panel can be programmed to push zone events to this virtual expander. This allows the bypassed zone binary sensors to be utilized. One example is using bypassed motion sensors at night for motion-based automated lights while the system is armed with the motion sensor bypassed.
- **relaychan** (*Optional*): Channel of the relay expander board to associate with the zone. (ex: 1, 2, 3, or 4)

9
source/_components/binary_sensor.command_line.markdown
View File

@ -33,7 +33,8 @@ Configuration variables:
- **payload_on** (*Optional*): The payload that represents enabled state. Default is "ON".
- **payload_off** (*Optional*): The payload that represents disabled state. Default is "OFF".
- **value_template** (*Optional*): Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract a value from the payload.
- **scan_interval** (*Optional*): Defines number of seconds for polling interval (defaults to 60 seconds).
- **scan_interval** (*Optional*): Defines number of seconds for polling interval (defaults to 60 seconds).
- **command_timeout** (*Optional*): Defines number of seconds for command timeout (defaults to 15 seconds).
## {% linkable_title Examples %}
@ -87,10 +88,10 @@ Consider to use the [`ping` sensor ](/components/binary_sensor.ping/) as an alte
The services running is listed in `/etc/systemd/system` and can be checked with the `systemctl` command:
```
$ systemctl is-active home-assistant@rock64.service
$ systemctl is-active home-assistant@rock64.service
active
$ sudo service home-assistant@rock64.service stop
$ systemctl is-active home-assistant@rock64.service
$ systemctl is-active home-assistant@rock64.service
inactive
```
@ -104,4 +105,4 @@ binary_sensor:
payload_off: 'inactive'
```
Note: Use single quotes!
Note: Use single quotes!

7
source/_components/binary_sensor.insteon_plm.markdown
View File

@ -13,4 +13,9 @@ ha_iot_class: "Local Push"
ha_release: 0.39
---
The `insteon_plm` binary sensor platform lets you control your sensors through an INSTEON PowerLinc Modem (PLM) device connected directly to your system on a USB or serial port. To add support, set up the primary [insteon_plm](/components/insteon_plm/) component.
The `insteon_plm` binary sensor platform lets you control your sensors through
an INSTEON PowerLinc Modem (PLM) device connected directly to your system on a
USB or serial port. To add support, set up the primary [insteon_plm]
component.
[insteon_plm]: /components/insteon_plm/

17
source/_components/binary_sensor.tahoma.markdown Normal file
View File

@ -0,0 +1,17 @@
---
layout: page
title: "Tahoma Binary Sensor"
description: "Instructions on how to integrate Tahoma binary sensors into Home Assistant."
date: 2018-06-14 21:57
sidebar: true
comments: false
sharing: true
footer: true
logo: tahoma.png
ha_category: Binary Sensor
ha_release: 0.73
---
The `tahoma` binary sensor platform lets you see binary sensors added to your Tahoma Box in Home Assistant. For example smoke detectors.
Binary sensors will be added automatically. Please refer to the [component](/components/tahoma/) configuration on how to setup Tahoma.

22
source/_components/camera.markdown
View File

@ -16,7 +16,23 @@ The camera component allows you to use IP cameras with Home Assistant. With a li
Once loaded, the `camera` platform will expose services that can be called to perform various actions.
Available services: `enable_motion_detection`, `disable_motion_detection`, and `snapshot`.
Available services: `turn_on`, `turn_off`, `enable_motion_detection`, `disable_motion_detection`, and `snapshot`.
#### {% linkable_title Service `turn_on` %}
Turn on camera. Not all camera models support this service, please consult individual camera page.
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
| `entity_id` | yes | Name(s) of entities to turn on, e.g., `camera.living_room_camera`. |
#### {% linkable_title Service `turn_off` %}
Turn off camera. Not all camera models support this service, please consult individual camera page.
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
| `entity_id` | yes | Name(s) of entities to turn off, e.g., `camera.living_room_camera`. |
#### {% linkable_title Service `enable_motion_detection` %}
@ -24,7 +40,7 @@ Enable the motion detection in a camera.
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
| `entity_id` | no | Name(s) of entities to enable motion detection, e.g., `camera.living_room_camera`. |
| `entity_id` | yes | Name(s) of entities to enable motion detection, e.g., `camera.living_room_camera`. |
#### {% linkable_title Service `disable_motion_detection` %}
@ -32,7 +48,7 @@ Disable the motion detection in a camera.
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
| `entity_id` | no | Name(s) of entities to disable motion detection, e.g., `camera.living_room_camera`. |
| `entity_id` | yes | Name(s) of entities to disable motion detection, e.g., `camera.living_room_camera`. |
#### {% linkable_title Service `snapshot` %}

2
source/_components/camera.nest.markdown
View File

@ -18,3 +18,5 @@ The `nest` platform allows you to watch still frames from a video stream (not li
<p class='note'>
You must have the [Nest component](/components/nest/) configured to use this camera. The `nest` camera will automatically be setup when you do.
</p>
Nest Camera supports `camera.turn_on` and `camera.turn_off` service since 0.75 release.

172
source/_components/camera.xiaofang.markdown
View File

@ -1,86 +1,86 @@
---
layout: page
title: "Xiaomi Cameras"
description: "Instructions on how to integrate a video feed (via FFmpeg) as a camera within Home Assistant."
date: 2018-06-20 13:00
sidebar: true
comments: false
sharing: true
footer: true
logo: xiaomi.png
ha_category: Camera
ha_release: 0.72
ha_iot_class: "Local Polling"
---
The `Xiaomi` camera platform allows you to utilize Xiaomi Cameras within Home Assistant.
To successfully implement this platform, the Home Assistant host should be capable of multiple simultaneous reads. For every concurrent Home Assistant user, a connection will be made to the camera every 10 seconds. This should normally not be a problem.
## {% linkable_title Preparing the Device %}
### {% linkable_title Installing Alternative Firmware %}
In order to integrate the camera with Home Assistant, it is necessary to install a custom firmware on the device. Instructions for doing so can be found for each models.
* [Yi 720p](https://github.com/fritz-smh/yi-hack)
* [Yi Home 17CN / 27US / 47US / 1080p Home / Dome / 1080p Dome](https://github.com/shadow-1/yi-hack-v3)
* [Xiaofang 1080p Camera](https://github.com/samtap/fang-hacks)
Once installed, please ensure that you have enabled FTP.
<p class='note warning'>
Currently, version 0.1.4-beta2 of the custom firmware is the highest supported. Firmwares higher than this version use [Pure-FTPd](https://www.pureftpd.org/project/pure-ftpd), which has a bug that prevents FFmpeg from correctly rendering video files.
</p>
<p class='note warning'>
Hassbian users: don't forget to install ffmpeg support on your platform, otherwise, you'll not see video.
</p>
<p class='note warning'>
The live stream writing by the camera is not an supported format when the hass reads through FTP for Yi 720p and Xiaofang Cameras, so this component retrives the video which was saved 1 minute earlier.
</p>
<p class='note warning'>
If you enabled RTSP server, you can connect to your camera via other Home Assistant camera platforms. However, this RTSP server disables the ability to use the supremely-useful Mi Home app. In order to maintain both Home Assistant compatibility _and_ the native app, this platform retrieves videos via FTP.
</p>
## {% linkable_title Configuring the Platform %}
To enable the platform, add the following lines to your`configuration.yaml` file:
```yaml
camera:
- platform: xiaomi
name: Camera
host: '192.168.1.100'
model: 'yi'
password: my_password_123
```
Configuration variables:
- **name** (*Required*): A human-friendly name for the camera.
- **host** (*Required*): The IP address or hostname of the camera.
- **model** (*Required*): The model of Xiaomi Camera, currently supporting yi and xiaofang.
- **password** (*Required*): The password to the FTP server on the camera (from above), can be any string as the current firmware doesn't allow setting ftp passwords.
- **path** (*Optional*): The path to the raw MP4 files. Defaults to `/tmp/sd/record`.
- **username** (*Optional*): The user that can access the FTP server. Defaults to `root`.
- **ffmpeg_arguments** (*Optional*): Extra options to pass to `ffmpeg` (e.g., image quality or video filter options).
## {% linkable_title Image quality %}
Any option supported by [`ffmpeg` camera](/components/camera.ffmpeg/) can be utilized via the `ffmpeg_arguments` configuration parameter.
One particularly useful adjustment deals with video size. Since Yi videos are fairly large (especially on the 1080p cameras), the following configuration will bring them down to a manageable size:
```yaml
camera:
- platform: xiaomi
name: My Camera
host: '192.168.1.100'
model: 'xiaofang'
password: my_password_123
path: /home/camera/feed
ffmpeg_arguments: '-vf scale=800:450'
```
---
layout: page
title: "Xiaomi Cameras"
description: "Instructions on how to integrate a video feed (via FFmpeg) as a camera within Home Assistant."
date: 2018-06-20 13:00
sidebar: true
comments: false
sharing: true
footer: true
logo: xiaomi.png
ha_category: Camera
ha_release: 0.72
ha_iot_class: "Local Polling"
---
The `Xiaomi` camera platform allows you to utilize Xiaomi Cameras within Home Assistant.
To successfully implement this platform, the Home Assistant host should be capable of multiple simultaneous reads. For every concurrent Home Assistant user, a connection will be made to the camera every 10 seconds. This should normally not be a problem.
## {% linkable_title Preparing the Device %}
### {% linkable_title Installing Alternative Firmware %}
In order to integrate the camera with Home Assistant, it is necessary to install a custom firmware on the device. Instructions for doing so can be found for each models.
* [Yi 720p](https://github.com/fritz-smh/yi-hack)
* [Yi Home 17CN / 27US / 47US / 1080p Home / Dome / 1080p Dome](https://github.com/shadow-1/yi-hack-v3)
* [Xiaofang 1080p Camera](https://github.com/samtap/fang-hacks)
Once installed, please ensure that you have enabled FTP.
<p class='note warning'>
Currently, version 0.1.4-beta2 of the custom firmware is the highest supported. Firmwares higher than this version use [Pure-FTPd](https://www.pureftpd.org/project/pure-ftpd), which has a bug that prevents FFmpeg from correctly rendering video files.
</p>
<p class='note warning'>
Hassbian users: don't forget to install ffmpeg support on your platform, otherwise, you'll not see video.
</p>
<p class='note warning'>
The live stream writing by the camera is not an supported format when the hass reads through FTP for Yi 720p and Xiaofang Cameras, so this component retrives the video which was saved 1 minute earlier.
</p>
<p class='note warning'>
If you enabled RTSP server, you can connect to your camera via other Home Assistant camera platforms. However, this RTSP server disables the ability to use the supremely-useful Mi Home app. In order to maintain both Home Assistant compatibility _and_ the native app, this platform retrieves videos via FTP.
</p>
## {% linkable_title Configuring the Platform %}
To enable the platform, add the following lines to your`configuration.yaml` file:
```yaml
camera:
- platform: xiaomi
name: Camera
host: '192.168.1.100'
model: 'yi'
password: my_password_123
```
Configuration variables:
- **name** (*Required*): A human-friendly name for the camera.
- **host** (*Required*): The IP address or hostname of the camera.
- **model** (*Required*): The model of Xiaomi Camera, currently supporting yi and xiaofang.
- **password** (*Required*): The password to the FTP server on the camera (from above), can be any string as the current firmware doesn't allow setting ftp passwords.
- **path** (*Optional*): The path to the raw MP4 files. Defaults to `/tmp/sd/record`.
- **username** (*Optional*): The user that can access the FTP server. Defaults to `root`.
- **ffmpeg_arguments** (*Optional*): Extra options to pass to `ffmpeg` (e.g., image quality or video filter options).
## {% linkable_title Image quality %}
Any option supported by [`ffmpeg` camera](/components/camera.ffmpeg/) can be utilized via the `ffmpeg_arguments` configuration parameter.
One particularly useful adjustment deals with video size. Since Yi videos are fairly large (especially on the 1080p cameras), the following configuration will bring them down to a manageable size:
```yaml
camera:
- platform: xiaomi
name: My Camera
host: '192.168.1.100'
model: 'xiaofang'
password: my_password_123
path: /home/camera/feed
ffmpeg_arguments: '-vf scale=800:450'
```

176
source/_components/camera.xiaomi.markdown
View File

@ -1,88 +1,88 @@
---
layout: page
title: "Xiaomi Cameras"
description: "Instructions on how to integrate a video feed (via FFmpeg) as a camera within Home Assistant."
date: 2018-06-20 13:00
sidebar: true
comments: false
sharing: true
footer: true
logo: xiaomi.png
ha_category: Camera
ha_release: 0.72
ha_iot_class: "Local Polling"
---
The `Xiaomi` camera platform allows you to utilize Xiaomi Cameras within Home Assistant.
To successfully implement this platform, the Home Assistant host should be capable of multiple simultaneous reads. For every concurrent Home Assistant user, a connection will be made to the camera every 10 seconds. This should normally not be a problem.
## {% linkable_title Preparing the Device %}
In order to integrate the camera with Home Assistant, it is necessary to install a custom firmware on the device. Instructions for doing so can be found for each models.
* [Yi 720p](https://github.com/fritz-smh/yi-hack)
* [Yi Home 17CN / 27US / 47US / 1080p Home / Dome / 1080p Dome](https://github.com/shadow-1/yi-hack-v3)
* [Xiaofang 1080p Camera](https://github.com/samtap/fang-hacks)
Once installed, please ensure that you have enabled FTP.
<p class='note warning'>
Currently, version 0.1.4-beta2 of the custom firmware is the highest supported. Firmwares higher than this version use [Pure-FTPd](https://www.pureftpd.org/project/pure-ftpd), which has a bug that prevents FFmpeg from correctly rendering video files.
</p>
<p class='note warning'>
Hassbian users: Don't forget to install `ffmpeg` support on your platform, otherwise, you'll not see video.
</p>
<p class='note warning'>
The live stream writing by the camera is not an supported format when the hass reads through FTP for Yi 720p and Xiaofang Cameras, so this platform retrives the video which was saved 1 minute earlier.
</p>
<p class='note warning'>
If you enabled RTSP server, you can connect to your camera via other Home Assistant camera platforms. However, this RTSP server disables the ability to use the supremely-useful Mi Home app. In order to maintain both Home Assistant compatibility _and_ the native app, this platform retrieves videos via FTP.
</p>
## {% linkable_title Configuring the Platform %}
To enable the platform, add the following lines to your`configuration.yaml` file:
```yaml
camera:
- platform: xiaomi
name: Camera
host: '192.168.1.100'
model: 'yi'
password: my_password_123
```
Configuration variables:
- **name** (*Required*): A human-friendly name for the camera.
- **host** (*Required*): The IP address or hostname of the camera.
- **model** (*Required*): The model of Xiaomi Camera, currently supporting yi and xiaofang.
- **password** (*Required*): The password to the FTP server on the camera (from above), can be any string as the current firmware doesn't allow setting ftp passwords.
- **path** (*Optional*): The path to the raw MP4 files. Defaults to `/tmp/sd/record`.
- **username** (*Optional*): The user that can access the FTP server. Defaults to `root`.
- **ffmpeg_arguments** (*Optional*): Extra options to pass to `ffmpeg` (e.g., image quality or video filter options).
<p class='note'>
The default for `path:` will not work with all cameras. It may be needed that you add that key with the exact path for your device.
</p>
## {% linkable_title Image quality %}
Any option supported by [`ffmpeg` camera](/components/camera.ffmpeg/) can be utilized via the `ffmpeg_arguments` configuration parameter.
One particularly useful adjustment deals with video size. Since Yi videos are fairly large (especially on the 1080p cameras), the following configuration will bring them down to a manageable size:
```yaml
camera:
- platform: xiaomi
name: My Camera
host: '192.168.1.100'
model: 'xiaofang'
password: my_password_123
path: /home/camera/feed
ffmpeg_arguments: '-vf scale=800:450'
```
---
layout: page
title: "Xiaomi Cameras"
description: "Instructions on how to integrate a video feed (via FFmpeg) as a camera within Home Assistant."
date: 2018-06-20 13:00
sidebar: true
comments: false
sharing: true
footer: true
logo: xiaomi.png
ha_category: Camera
ha_release: 0.72
ha_iot_class: "Local Polling"
---
The `Xiaomi` camera platform allows you to utilize Xiaomi Cameras within Home Assistant.
To successfully implement this platform, the Home Assistant host should be capable of multiple simultaneous reads. For every concurrent Home Assistant user, a connection will be made to the camera every 10 seconds. This should normally not be a problem.
## {% linkable_title Preparing the Device %}
In order to integrate the camera with Home Assistant, it is necessary to install a custom firmware on the device. Instructions for doing so can be found for each models.
* [Yi 720p](https://github.com/fritz-smh/yi-hack)
* [Yi Home 17CN / 27US / 47US / 1080p Home / Dome / 1080p Dome](https://github.com/shadow-1/yi-hack-v3)
* [Xiaofang 1080p Camera](https://github.com/samtap/fang-hacks)
Once installed, please ensure that you have enabled FTP.
<p class='note warning'>
Currently, version 0.1.4-beta2 of the custom firmware is the highest supported. Firmwares higher than this version use [Pure-FTPd](https://www.pureftpd.org/project/pure-ftpd), which has a bug that prevents FFmpeg from correctly rendering video files.
</p>
<p class='note warning'>
Hassbian users: Don't forget to install `ffmpeg` support on your platform, otherwise, you'll not see video.
</p>
<p class='note warning'>
The live stream writing by the camera is not an supported format when the hass reads through FTP for Yi 720p and Xiaofang Cameras, so this platform retrives the video which was saved 1 minute earlier.
</p>
<p class='note warning'>
If you enabled RTSP server, you can connect to your camera via other Home Assistant camera platforms. However, this RTSP server disables the ability to use the supremely-useful Mi Home app. In order to maintain both Home Assistant compatibility _and_ the native app, this platform retrieves videos via FTP.
</p>
## {% linkable_title Configuring the Platform %}
To enable the platform, add the following lines to your`configuration.yaml` file:
```yaml
camera:
- platform: xiaomi
name: Camera
host: '192.168.1.100'
model: 'yi'
password: my_password_123
```
Configuration variables:
- **name** (*Required*): A human-friendly name for the camera.
- **host** (*Required*): The IP address or hostname of the camera.
- **model** (*Required*): The model of Xiaomi Camera, currently supporting yi and xiaofang.
- **password** (*Required*): The password to the FTP server on the camera (from above), can be any string as the current firmware doesn't allow setting ftp passwords.
- **path** (*Optional*): The path to the raw MP4 files. Defaults to `/tmp/sd/record`.
- **username** (*Optional*): The user that can access the FTP server. Defaults to `root`.
- **ffmpeg_arguments** (*Optional*): Extra options to pass to `ffmpeg` (e.g., image quality or video filter options).
<p class='note'>
The default for `path:` will not work with all cameras. It may be needed that you add that key with the exact path for your device.
</p>
## {% linkable_title Image quality %}
Any option supported by [`ffmpeg` camera](/components/camera.ffmpeg/) can be utilized via the `ffmpeg_arguments` configuration parameter.
One particularly useful adjustment deals with video size. Since Yi videos are fairly large (especially on the 1080p cameras), the following configuration will bring them down to a manageable size:
```yaml
camera:
- platform: xiaomi
name: My Camera
host: '192.168.1.100'
model: 'xiaofang'
password: my_password_123
path: /home/camera/feed
ffmpeg_arguments: '-vf scale=800:450'
```

28
source/_components/climate.spider.markdown Normal file
View File

@ -0,0 +1,28 @@
---
layout: page
title: "Spider Thermostat"
description: "Instructions on how to integrate Spider thermostats within Home Assistant."
date: 2018-07-17 22:01
sidebar: true
comments: false
sharing: true
footer: true
logo: spider.png
ha_category: Climate
ha_iot_class: "Cloud Polling"
ha_release: 0.75
---
The `spider` climate platform allows you to control your temperature settings as well as if you want to cool or heat.
<p class='note'>
Full configuration details can be found on the main [Spider component](/components/spider/) page.
</p>
<p class='note'>
Although this component lets you change the operation mode to heating or cooling, it doesn't necessarily mean your boiler can. Spider is not aware of your current situation.
</p>
<p class='note warning'>
This component is not affiliated with Itho Daalderop Spider and retrieves data from the endpoints of the mobile application. Use at your own risk.
</p>

22
source/_components/climate.tuya.markdown Normal file
View File

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

41
source/_components/cover.aladdin_connect.markdown Normal file
View File

@ -0,0 +1,41 @@
---
layout: page
title: "Genie Aladdin Connect Cover"
description: "Instructions how to integrate Genie Aladdin Connect garage door covers into Home Assistant."
date: 2018-07-26 22:00
sidebar: true
comments: false
sharing: true
footer: true
logo: aladdin_connect.png
ha_category: Cover
ha_release: 0.75
ha_iot_class: "Cloud Polling"
---
The `aladdin_connect` cover platform lets you control Genie Aladdin Connect garage doors through Home Assistant.
<p class='note'>
Only doors that are owned by your Aladdin Connect account will be available. Doors that your account has been granted shared access to are not yet supported.
</p>
To use your Aladdin Connect cover in your installation, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yml entry
cover:
- platform: aladdin_connect
username: user@email.com
password: password
```
{% configuration %}
username:
description: Your Aladdin Connect account username.
required: true
type: string
password:
description: Your Aladdin Connect account password.
required: true
type: string
{% endconfiguration %}

47
source/_components/cover.brunt.markdown Normal file
View File

@ -0,0 +1,47 @@
---
layout: page
title: Brunt Cover
description: "Instructions on how to set up Brunt Blind Engine within Home Assistant."
date: 2018-06-24 14:36
sidebar: true
comments: false
sharing: true
footer: true
logo: brunt.png
ha_category: Cover
ha_release: 0.75
ha_iot_class: "Cloud Polling"
---
The `brunt` platform allows one to control Blind Engines by [Brunt](https://www.brunt.co). To use this sensor, you need a Brunt App Account. All Brunt Blind devices registered to your account are automatically added to your Home Assistant with the names given them through the Brunt app.
## {% linkable_title Configuration %}
To enable this integration, add the following lines to your `configuration.yaml`:
```yaml
cover:
- platform: brunt
username: BRUNT_USERNAME
password: BRUNT_PASSWORD
```
{% configuration %}
name:
description: Cover name
required: false
default: "brunt blind engine"
type: string
username:
description: Account username of your Brunt app
required: true
type: string
password:
description: Account password of your Brunt app
required: true
type: string
{% endconfiguration %}
<p class='note warning'>
This component is not affiliated with Brunt and retrieves data from the endpoints of the mobile application. Use at your own risk.
</p>

23
source/_components/cover.tuya.markdown Normal file
View File

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

23
source/_components/fan.tuya.markdown Normal file
View File

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

5
source/_components/homekit.markdown
View File

@ -64,6 +64,11 @@ homekit:
required: false
type: int
default: 51827
name:
description: Need to be individual for each instance of Home Assistant using the component on the same local network. Between `3` and `25` characters. Alphanumeric and spaces allowed.
required: false
type: string
default: '`Home Assistant Bridge`'
ip_address:
description: The local network IP address. Only necessary if the default from Home Assistant does not work.
required: false

54
source/_components/insteon_plm.markdown
View File

@ -162,3 +162,57 @@ light:
- platform: insteon_plm
address: 1a2b3c
```
### {% linkable_title Events and Mini-Remotes %}
Mini-Remote devices do not appear as Home Assistant entities. They generate
events. The following events are available:
- **insteon_plm.button_on**
- **address**: (required) The Insteon device address in lower case without
dots (e.g. 1a2b3c)
- **button**: (Optional) The button id in lower case. For an 4 button remote
the values are a to d. For an 8 button remote the values are a to g. For
a one button remote this field is not used.
- **insteon_plm.button_of**
- **address**: (required) The Insteon device address in lower case without
dots (e.g. 1a2b3c)
- **button**: (Optional) The button id in lower case. For an 4 button remote
the values are a to d. For an 8 button remote the values are a to g. For
a one button remote this field is not used.
This allows the mini-remotes to be configured as
Here is an example of how to use these events for automations:
```
automation:
# 4 or 8 button remote with button c pressed
trigger:
platform: event
event_type: insteon_plm.button_on
event_data:
address: 1a2b3c
button: c
condition:
- condition: state
entity_id: light.some_light
state: 'off'
action:
service: light.turn_on
entity_id: light.some_light
# single button remote
trigger:
platform: event
event_type: insteon_plm.button_on
event_data:
address: 1a2b3c
condition:
- condition: state
entity_id: light.some_light
state: 'off'
action:
service: light.turn_on
entity_id: light.some_light
```

97
source/_components/light.futurenow.markdown Normal file
View File

@ -0,0 +1,97 @@
---
layout: page
title: "P5 FutureNow Lights"
description: "Instructions on how to set up P5 FutureNow relay/dimmer units as lights within Home Assistant."
date: 2018-07-24 15:00
sidebar: true
comments: false
sharing: true
footer: true
logo: p5.png
ha_category: Light
ha_release: 0.75
---
The `futurenow` light platform allows you to use [P5](http://www.p5.hu) FutureNow relay/dimmer units as lights. Currently supported units:
* [FutureNow FNIP-6x2AD](http://www.p5.hu/index.php/products/ethernet-modules/265-fnip-6x2ad) dimmer unit (outputs only)
* [FutureNow FNIP-8x10A](http://www.p5.hu/index.php/products/ethernet-modules/263-fnip-8x10a) relay unit (outputs only)
### {% linkable_title Configuration Sample %}
To use your FutureNow units, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
light:
- platform: futurenow
driver: FNIP6x10ad
host: 192.168.1.101
port: 7078
devices:
5:
name: Dimmer Channel 5
dimmable: true
```
{% configuration %}
driver:
description: "Type of the device. Currently `FNIP6x10ad` or `FNIP8x10a`."
required: true
type: string
host:
description: "The IP address or hostname of your unit, e.g., `192.168.1.101`."
required: true
type: string
port:
description: "The TCP port, as set in the unit's settings. Default is `7078`."
required: true
type: string
devices:
description: "List of output channels to set up as lights."
required: true
type: map
keys:
channel_number:
description: "Output's (light) properties."
required: true
type: map
keys:
name:
description: "The name of the light."
required: true
type: string
dimmable:
description: "Set to `true` to enable dimming (FNIP6x10ad only)."
required: false
type: boolean
default: false
{% endconfiguration %}
### {% linkable_title Extended Configuration Sample %}
The following example `configuration.yaml` has two different FutureNow units with multiple channels:
```yaml
# Example configuration.yaml entry
light:
- platform: futurenow
driver: FNIP6x10ad
host: 192.168.1.101
port: 7078
devices:
5:
name: Dimmer Channel 5
6:
name: Dimmer Channel 6
dimmable: true
- platform: futurenow
driver: FNIP8x10a
host: 192.168.1.102
port: 7078
devices:
1:
name: Relay Channel 1
2:
name: Relay Channel 2
```

6
source/_components/light.markdown
View File

@ -15,6 +15,12 @@ This component allows you to track and control various light bulbs. Read the pla
The light component supports multiple entries in <code>configuration.yaml</code> by appending a sequential number to the section: <code>light 2:</code>, <code>light 3:</code> etc.
</p>
### {% linkable_title Default turn-on values %}
To set the default color and brightness values when the light is turned on, create a custom `light_profiles.csv` (as described below in the `profile` attribute of `light.turn_on`).
The `.default` suffix should be added to the entity identifier of each light to define a default value, e.g. for `light.ceiling_2` the `id` field is `light.ceiling_2.default`. To define a default for all lights, the identifier `group.all_lights.default` can be used. Individual settings always supercede the `all_lights` default setting.
### {% linkable_title Service `light.turn_on` %}
Turns one light on or multiple lights on using [groups]({{site_root}}/components/group/).

20
source/_components/light.sisyphus.markdown Normal file
View File

@ -0,0 +1,20 @@
---
layout: page
title: "Sisyphus Light"
description: "Instructions on how to integrate the light in your Sisyphus Kinetic Art Table into Home Assistant."
date: 2018-05-06 22:26
sidebar: true
comments: false
sharing: true
footer: true
logo: sisyphus.png
ha_category: Light
ha_iot_class: "Local Push"
ha_release: 0.75
---
The [Sisyphus](https://sisyphus-industries.com/) integration for Home Assistant allows you to observe and control your Sisyphus Kinetic Art Table.
Lights will be automatically added for each of your Sisyphus tables if the Sisyphus component is configured.
For more configuration information see the [Sisyphus component](/components/sisyphus/) documentation.

20
source/_components/media_player.sisyphus.markdown Normal file
View File

@ -0,0 +1,20 @@
---
layout: page
title: "Sisyphus Media Player"
description: "Instructions on how to integrate media playing on your Sisyphus Kinetic Art Table into Home Assistant."
date: 2018-05-06 22:26
sidebar: true
comments: false
sharing: true
footer: true
logo: sisyphus.png
ha_category: Media Player
ha_iot_class: "Local Push"
ha_release: 0.75
---
The [Sisyphus](https://sisyphus-industries.com/) integration for Home Assistant allows you to observe and control your Sisyphus Kinetic Art Table.
Media players will be automatically added for each of your Sisyphus tables if the Sisyphus component is configured.
For more configuration information see the [Sisyphus component](/components/sisyphus/) documentation.

24
source/_components/scene.tuya.markdown Normal file
View File

@ -0,0 +1,24 @@
---
layout: page
title: "Tuya Scene"
description: "Instructions on how to setup the Tuya scene within Home Assistant."
date: 2018-07-20 09:00
sidebar: true
comments: false
sharing: true
footer: true
logo: tuya.png
ha_category: Scene
ha_release: 0.75
---
The `tuya` scene platform allows you to activate your [Tuya Smart](https://www.tuya.com) scenes.
The platform supports scenes.
The device state in frontend panel will not change immediately after you activate a scene.
<p class='note'>
Full configuration details can be found on the main [Tuya component](/components/tuya/) page.
</p>

21
source/_components/sensor.command_line.markdown
View File

@ -32,6 +32,8 @@ Configuration variables:
- **unit_of_measurement** (*Optional*): Defines the unit of measurement of the sensor, if any.
- **value_template** (*Optional*): Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract a value from the payload.
- **scan_interval** (*Optional*): Defines number of seconds for polling interval (defaults to 60 seconds).
- **command_timeout** (*Optional*): Defines number of seconds for command timeout (defaults to 15 seconds).
- **json_attributes** (*Optional*): Defines a list of keys to extract values from a JSON dictionary result and then set as sensor attributes.
## {% linkable_title Examples %}
@ -161,3 +163,22 @@ sensor:
unit_of_measurement: "Direction"
```
{% endraw %}
### {% linkable_title Usage of JSON attributes in command output %}
The example shows how you can retrieve multiple values with one sensor (where the additional are attributes) by using `value_json` and `json_attributes`.
{% raw %}
```yaml
# Example configuration.yaml entry
sensor:
- platform: command_line
name: JSON time
json_attributes:
- date
- milliseconds_since_epoch
command: 'python3 /home/pi/.homeassistant/scripts/datetime.py'
value_template: '{{ value_json.time }}'
```
{% endraw %}

95
source/_components/sensor.magicseaweed.markdown Normal file
View File

@ -0,0 +1,95 @@
---
layout: page
title: "Magicseaweed Sensor"
description: "How to integrate Magicseaweed within Home Assistant."
date: 2018-06-24 21:00
sidebar: true
comments: false
sharing: true
footer: true
logo: magicseaweed.png
ha_category: Sensor
featured: false
ha_release: "0.75"
ha_iot_class: "Cloud Polling"
---
The 'magicseaweed' platform uses the [Magicseaweed Forecast API](https://magicseaweed.com/developer/forecast-api) as a source for surf forecasting data for the surf spots of your choice.
You need an API key which is free but requires [registration](https://magicseaweed.com/developer/sign-up). Magicseaweed is limiting users of the API to 2 spots for the free plan.
To add Magicseaweed forecasts to your installation, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
sensor:
- platform: magicseaweed
api_key: YOUR_API_KEY
spot_id: 1092
monitored_conditions:
- max_breaking_swell
```
{% configuration %}
api_key:
description: The API key to access the service.
required: true
type: string
name:
description: Spot nickname for the sensors.
required: false
default: MSW.
type: string
hour:
description: List of hours you would like to receive data for.
required: false
default: Defaults to current forecast.
type: list
keys:
3AM:
description: Display forecast for 3AM.
6AM:
description: Display forecast for 6AM.
9AM:
description: Display forecast for 9AM.
12PM:
description: Display forecast for 12PM.
3PM:
description: Display forecast for 3PM.
6PM:
description: Display forecast for 6PM.
9PM:
description: Display forecast for 9PM.
12AM:
description: Display forecast for 12AM.
spot_id:
description: ID of the surf spot. Details for getting spot id available at [Magicseaweed](https://magicseaweed.com/developer/forecast-api)
required: true
type: string
monitored_conditions:
description: Type of data to display.
required: true
type: list
keys:
swell_forecast:
description: List of forecast summaries as attributes with current summary as state.
min_breaking_swell:
description: The minimum wave height as the state with a detailed list of forecast attributes.
max_breaking_swell:
description: The maximum wave height as the state with a detailed list of forecast attributes.
units:
description: Specify the unit system.
required: false
default: Default to `uk` or `us` based on the temperature preference in Home Assistant.
type: string
keys:
uk:
description: Use UK units.
eu:
description: Use EU units.
us:
description: Use US units.
{% endconfiguration %}
Details about the API are available in the [Magicseaweed documentation](https://magicseaweed.com/developer/forecast-api).

9
source/_components/sensor.mvglive.markdown
View File

@ -13,7 +13,6 @@ ha_release: 0.42
ha_iot_class: "Cloud Polling"
---
The `mvglive` sensor will give you the departure time of the next bus, tram, subway, or train at the next station or stop in the Munich public transport network. Additional details such as the line number and destination are present in the attributes.
## {% linkable_title Configuration %}
@ -36,7 +35,9 @@ Configuration variables:
- **lines** (*Optional*): One or more line numbers, e.g., 'U2' or ['U2','U8','N41']
- **products** (*Optional*): One or more modes of transport, defaults to all 4 modes ['U-Bahn', 'Tram', 'Bus', 'S-Bahn'].
- **timeoffset** (*Optional*): Do not display departures leaving sooner than this number of minutes (defaults to 0). Useful if you are a couple of minutes away from the stop.
- **number** (*Optional*): Store a list of departures in the attribute "departures", defaults to 1. If you set this parameter to 3, the next three departures will be stored.
- **name** (*Optional*): You can customize the name of the sensor, which defaults to the station name.
## {% linkable_title Examples %}
### {% linkable_title Full configuration %}
@ -55,8 +56,12 @@ sensor:
timeoffset: 2
- station: Sendlinger Tor
lines: ['U2','U8']
number: 5
- station: Scheidplatz
products: ['U-Bahn']
directions: '1'
```
The first sensor will return S-Bahn departures to Munich Airport or Markt Schwaben that are at least 2 minutes away. The second sensor returns U2 and U8 departures from Sendlinger Tor while the third sensor returns all south-bound U-Bahn trains from Scheidplatz.
The first sensor will return S-Bahn departures to Munich Airport or Markt Schwaben that are at least 2 minutes away.
The second sensor returns U2 and U8 departures from Sendlinger Tor and stores a total of 5 departures in attributes. To retrieve the time until the second departure, you would use states.sensor.ENTITY_NAME.attributes.departures[1].time.
The third sensor returns all south-bound U-Bahn trains from Scheidplatz.

52
source/_components/sisyphus.markdown Normal file
View File

@ -0,0 +1,52 @@
---
layout: page
title: "Sisyphus"
description: "Instructions on how to integrate your Sisyphus Kinetic Art Table within Home Assistant."
date: 2018-05-06 22:26
sidebar: true
comments: false
sharing: true
footer: true
logo: sisyphus.png
ha_category: Hub
featured: false
ha_release: 0.75
ha_iot_class: "Local Push"
---
The [Sisyphus](https://sisyphus-industries.com/) integration for Home Assistant allows you to observe and control your Sisyphus Kinetic Art Table.
Each table appears in Home Assistant as a Light and a Media Player.
The light can be used to sleep/wake the table or adjust the brightness of the table light.
The media player can be used to sleep/wake the table, play/pause, move between tracks, or toggle shuffle on and off. The "volume" control adjusts the table's speed.
There are two ways to configure this component. For the automatic discovery of your table(s), simply add the following to your `configuration.yaml`:
```yaml
# This will auto-detect all Sisyphus tables on your local network.
sisyphus:
```
Auto-detection can be a little slow, so if your table has a fixed IP address or hostname, you may add a list of tables in your `configuration.yaml`. For example:
```yaml
# This will skip auto-detection and add only the listed tables
sisyphus:
- name: 'TABLE_NAME'
host: 'TABLE_IP_OR_HOSTNAME'
- name: 'ANOTHER_TABLE_NAME'
host: 'ANOTHER_TABLE_IP_OR_HOSTNAME'
```
{% configuration %}
name:
description: The name by which the table should appear in Home Assistant
required: true
type: string
host:
description: The hostname or IP address of the table
required: true
type: string
{% endconfiguration %}

45
source/_components/spider.markdown Normal file
View File

@ -0,0 +1,45 @@
---
layout: page
title: "Spider"
description: "Instructions on how to setup the Spider hub within Home Assistant."
date: 2018-07-17 22:01
sidebar: true
comments: false
sharing: true
footer: true
logo: spider.png
ha_category: Hub
ha_iot_class: "Cloud Polling"
ha_release: 0.75
---
The `spider` component is the main component to integrate all [Itho Daalderop Spider](https://www.ithodaalderop.nl/spider-thermostaat) related platforms. You will need your Spider account information (username, password) to discover and control devices which are related to your account.
## {% linkable_title Configuration %}
To add your Spider devices into your Home Assistant installation, add the following to your `configuration.yaml` file:
```yaml
spider:
username: YOUR_USERNAME
password: YOUR_PASSWORD
```
{% configuration %}
username:
description: Account username of mijn.ithodaalderop.nl
required: true
type: string
password:
description: Account password of mijn.ithodaalderop.nl
required: true
type: string
scan_interval:
description: How frequently to query for new data. Defaults to 120 seconds.
required: false
type: int
{% endconfiguration %}
<p class='note warning'>
This component is not affiliated with Itho Daalderop Spider and retrieves data from the endpoints of the mobile application. Use at your own risk.
</p>

12
source/_components/switch.mqtt.markdown
View File

@ -46,6 +46,16 @@ state_topic:
description: The MQTT topic subscribed to receive state updates.
required: false
type: string
state_on:
description: The payload that represents the on state.
required: false
type: string
default: ON
state_off:
description: The payload that represents the off state.
required: false
type: string
default: OFF
command_topic:
description: The MQTT topic to publish commands to change the switch state.
required: false
@ -117,6 +127,8 @@ switch:
availability_topic: "home/bedroom/switch1/available"
payload_on: "ON"
payload_off: "OFF"
state_on: "ON"
state_off: "OFF"
optimistic: false
qos: 0
retain: true

24
source/_components/switch.spider.markdown Normal file
View File

@ -0,0 +1,24 @@
---
layout: page
title: "Spider Power Plug"
description: "Instructions on how to integrate Spider power plugs within Home Assistant."
date: 2018-07-26 22:01
sidebar: true
comments: false
sharing: true
footer: true
logo: spider.png
ha_category: Switch
ha_iot_class: "Cloud Polling"
ha_release: 0.75
---
The `spider` power plug platform allows you to control your power plugs. It also shows you your current and daily energy usage by the power plug.
<p class='note'>
Full configuration details can be found on the main [Spider component](/components/spider/) page.
</p>
<p class='note warning'>
This component is not affiliated with Itho Daalderop Spider and retrieves data from the endpoints of the mobile application. Use at your own risk.
</p>

2
source/_docs/configuration/secrets.markdown
View File

@ -10,7 +10,7 @@ footer: true
redirect_from: /topics/secrets/
---
The `configuration.yaml` file is a plain-text file, thus it is readable by anyone who has access to the file. The file contains passwords and API tokens which need to be redacted if you want to share your configuration. By using `!secrets` you can remove any private information from you configuration files. This separation can also help you to keep easier track of your passwords and API keys. As they are all stored at one place and no longer spread across the `configuration.yaml` file or even multiple yaml files if you [split up your configuration](/docs/configuration/splitting_configuration/).
The `configuration.yaml` file is a plain-text file, thus it is readable by anyone who has access to the file. The file contains passwords and API tokens which need to be redacted if you want to share your configuration. By using `!secret` you can remove any private information from you configuration files. This separation can also help you to keep easier track of your passwords and API keys. As they are all stored at one place and no longer spread across the `configuration.yaml` file or even multiple yaml files if you [split up your configuration](/docs/configuration/splitting_configuration/).
### {% linkable_title Using secrets.yaml %}

62
source/_lovelace/conditional.markdown Normal file
View File

@ -0,0 +1,62 @@
---
layout: page
title: Conditional Card
sidebar_label: Conditional
description: Displays another card based on entity states.
date: 2018-07-26 10:28 +00:00
sidebar: true
comments: false
sharing: true
footer: true
---
Displays another card based on entity states.
{% configuration %}
type:
required: true
description: conditional
type: string
conditions:
required: true
description: List of entity IDs and matching states.
type: list
keys:
entity:
required: true
description: HA entity ID.
type: string
state:
required: false
description: Entity state is equal to this value.*
type: string
state_not:
required: false
description: Entity state is unequal to this value.*
type: string
card:
required: true
description: Card to display if all conditions match.
type: object
{% endconfiguration %}
*one is required (`state` or `state_not`)
### {% linkable_title Examples %}
```yaml
- type: conditional
conditions:
- entity: light.bed_light
state: "on"
- entity: switch.decorative_lights
state_not: "off"
card:
type: entities
entities:
- device_tracker.demo_paulus
- cover.kitchen_window
- group.kitchen
- lock.kitchen_door
- light.bed_light
```

93
source/_lovelace/entities.markdown
View File

@ -49,14 +49,86 @@ name:
required: false
description: Overwrites friendly name.
type: string
icon:
required: false
description: Overwrites icon or entity picture.
type: string
secondary_info:
required: false
description: "Show additional info. Values: `entity-id`, `last-changed`."
type: string
{% endconfiguration %}
## {% linkable_title Secial Row Elements %}
### {% linkable_title Call Service %}
{% configuration %}
type:
required: true
description: call-service
type: string
name:
required: true
description: Main Label.
type: string
icon:
required: true
description: "Icon to display (e.g. `mdi:home`)"
type: string
action_name:
required: true
description: Button label.
type: string
service:
required: true
description: "Service like `media_player.media_play_pause`"
type: string
service_data:
required: true
description: The service data to use.
type: object
{% endconfiguration %}
### {% linkable_title Weblink %}
{% configuration %}
type:
required: true
description: weblink
type: string
name:
required: true
description: Link label.
type: string
icon:
required: true
description: "Icon to display (e.g. `mdi:home`)"
type: string
url:
required: true
description: "Website URL."
type: string
{% endconfiguration %}
### {% linkable_title Divider %}
{% configuration %}
type:
required: true
description: divider
type: string
style:
required: false
description: Style the element using CSS.
type: object
default: "height: 1px, background-color: var(--secondary-text-color)"
{% endconfiguration %}
## {% linkable_title Example %}
Entity rows:
```yaml
- type: entities
title: Entities card sample
@ -69,3 +141,24 @@ secondary_info:
- group.all_lights
- group.all_locks
```
Special rows:
```yaml
- type: entities
title: Entities card sample
show_header_toggle: true
entities:
- type: call-service
icon: mdi:power
name: Bed light
action_name: Toggle light
service: light.toggle
service_data:
entity_id: light.bed_light
- type: divider
- type: weblink
name: Home Assistant
url: https://www.home-assistant.io/
icon: mdi:home-assistant
```

15
source/_lovelace/glance.markdown
View File

@ -60,11 +60,24 @@ name:
required: false
description: Overwrites friendly name.
type: string
icon:
required: false
description: Overwrites icon or entity picture.
type: string
tap_action:
required: false
description: "Set to `toggle` or `turn-on` for direct actions."
description: "Set to `toggle` or `call-service` for direct actions."
type: string
default: more-info
service:
required: false
description: "For `call-service`, e.g. `media_player.media_play_pause`"
type: string
service_data:
required: false
description: The service data to use.
type: object
default: "entity_id: entity_id"
{% endconfiguration %}
## {% linkable_title Examples %}

8
source/_lovelace/picture-elements.markdown
View File

@ -104,6 +104,14 @@ entity:
required: true
description: Entity id
type: string
prefix:
required: false
description: Text before entity state.
type: string
suffix:
required: false
description: Text after entity state.
type: string
tap_action:
required: false
description: more-info, toggle, navigate, call-service

9
source/_lovelace/picture-entity.markdown
View File

@ -42,9 +42,14 @@ name:
required: false
description: Overwrite entity name.
type: string
show_info:
show_name:
required: false
description: Shows the footer box.
description: Shows name in footer.
type: boolean
default: true
show_state:
required: false
description: Shows state in footer.
type: boolean
default: true
tap_action:

17
source/_lovelace/picture-glance.markdown
View File

@ -24,7 +24,7 @@ type:
type: string
entities:
required: true
description: List of entities.
description: List of entities or entity objects.
type: list
title:
required: false
@ -57,6 +57,21 @@ entity:
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
icon:
required: false
description: Overwrites default icon.
type: string
{% endconfiguration %}
## {% linkable_title Examples %}
```yaml

397
source/_posts/2018-08-03-release-75.markdown Normal file
View File

@ -0,0 +1,397 @@
---
layout: post
title: "0.75: Spider, Tuya, Brunt, Magicseaweed API"
description: "You're now able to change entity IDs on the fly."
date: 2018-07-31 00:01:00
date_formatted: "August 3, 2018"
author: Paulus Schoutsen
author_twitter: balloob
comments: true
categories: Release-Notes
og_image: /images/blog/2018-08-0.75/components.png
---
<a href='/components/#version/0.75'><img src='/images/blog/2018-08-0.75/components.png' style='border: 0;box-shadow: none;'></a>
And just like that, it's August. Time is flying by. People all over the world have been busy to create this release for you. This release again a ton of cool new stuff.
First, let's talk entity IDs. Entity IDs are how we identify entities in automations and scripts. They start with the domain and end with an object id, for example: `light.kitchen`. Or, if you're unlucky `light.node_2_2_abc`. With this release, it will now be possible to manage entity IDs of entities via the UI! Just as with changing the name, it requires that the integration is able to supply a unique ID for each entity.
<p class='img'>
<img src='/images/blog/2018-08-0.75/change-entity.png' alt='Screenshot of the user interface to change entity identifiers.'>
Screenshot of the new user interface to change entity IDs.
</p>
This release also includes a bunch more Tuya integrations thanks to [@huangyupeng]. And thanks to [@peternijssen] we're now also able to talk with Spider thermostats and plugs.
## {% linkable_title New Platforms %}
- Add Tuya climate platform ([@huangyupeng] - [#15500]) ([tuya docs]) ([climate.tuya docs]) (new-platform)
- Add Tuya fan support ([@huangyupeng] - [#15525]) ([tuya docs]) ([fan.tuya docs]) (new-platform)
- Add Tuya cover and scene platform ([@huangyupeng] - [#15587]) ([tuya docs]) ([cover.tuya docs]) ([scene.tuya docs]) (new-platform)
- Add support for Tahoma Smoke Sensor ([@fucm] - [#15441]) ([tahoma docs]) ([binary_sensor.tahoma docs]) (new-platform)
- Add Brunt Cover Device ([@eavanvalkenburg] - [#15653]) ([cover.brunt docs]) (new-platform)
- Add spider thermostat ([@peternijssen] - [#15499]) ([climate.spider docs]) (new-platform)
- Add spider power plug component ([@peternijssen] - [#15682]) ([spider docs]) ([switch.spider docs]) (new-platform)
- Add support for P5 FutureNow light platform ([@juhaniemi] - [#15662]) ([light.futurenow docs]) (new-platform)
- Add Magicseaweed API support ([@jcconnell] - [#15132]) ([sensor.magicseaweed docs]) (new-platform)
- Add a component for Sisyphus Kinetic Art Tables ([@jkeljo] - [#14472]) ([sisyphus docs]) ([light.sisyphus docs]) ([media_player.sisyphus docs]) (new-platform)
- Add Genie Aladdin Connect cover component ([@shoejosh] - [#15699]) ([cover.aladdin_connect 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 %}
- Moon sensor states are now lowercase with underscores instead of spaces, allowing it to be translated in the frontend. ([@pvizeli] - [#15498]) ([sensor.moon docs]) (breaking change)
- Insteon Mini-Remote now emit events instead of show as a binary sensor ([@teharris1] - [#15523]) ([insteon_plm docs]) ([binary_sensor.insteon_plm docs]) ([switch.insteon_plm docs]) (breaking change)
- Simplisafe to use new API: co, fire, flood, and last_event are no longer part of the SimpliSafe alarm object in the new API and are not available in this upgrade, making this a breaking change for anyone using those. They will be added back in some fashion at a later date (probably exposed as individual sensors) ([@w1ll1am23] - [#15542]) ([alarm_control_panel.simplisafe docs]) (breaking change)
- Smappee: The updated library shows the temperature as degrees Celsius instead of centi degrees Celsius. ([@visibilityspots] - [#15636]) ([smappee docs]) (breaking change)
## {% linkable_title Beta Fixes %}
- Fix Min/Max Kelvin color temp attribute for Google ([@bryanyork] - [#15697]) ([google_assistant docs]) (beta fix)
- Only report color temp when in the correct color mode ([@Kane610] - [#15791]) ([light.deconz docs]) (beta fix)
- Allow Nest to setup without configuration.yaml entry ([@balloob] - [#15797]) ([nest docs]) (beta fix)
## {% linkable_title All changes %}
- Delay setup of waze travel time component ([@squirtbrnr] - [#15455]) ([sensor.waze_travel_time docs])
- Bump pyarlo==0.2.0, fixes #15486 ([@lukiffer] - [#15503]) ([arlo docs])
- Pylint 2 fixes ([@scop] - [#15487])
- Add Tuya climate platform ([@huangyupeng] - [#15500]) ([tuya docs]) ([climate.tuya docs]) (new-platform)
- Support latest tplink Archer D9 Firmware version / Device Scanner ([@JackNova] - [#15356]) ([device_tracker docs])
- Customizable command timeout ([@mu4yu3] - [#15442]) ([sensor.command_line docs])
- Add check_untyped_defs ([@andrey-git] - [#15510])
- Remove some unused imports ([@scop] - [#15529])
- Moon translate ([@pvizeli] - [#15498]) ([sensor.moon docs]) (breaking change)
- More pylint 2 fixes ([@scop] - [#15516])
- Make sure that only pypi dependencies are used ([@andrey-git] - [#15490])
- RFC: Only use supported light properties ([@amelchio] - [#15484]) ([light docs]) ([light.mqtt docs])
- Cleanup of HomematicIP Cloud code ([@mxworm] - [#15475]) ([homematicip_cloud docs])
- Implement locate service for neato ([@dshokouhi] - [#15467]) ([neato docs]) ([vacuum.neato docs])
- Make RS room thermostat discoverable ([@turbokongen] - [#15451]) ([zwave docs])
- Add support for Tahoma Smoke Sensor ([@fucm] - [#15441]) ([tahoma docs]) ([binary_sensor.tahoma docs]) (new-platform)
- Mini-Remote events ([@teharris1] - [#15523]) ([insteon_plm docs]) ([binary_sensor.insteon_plm docs]) ([switch.insteon_plm docs]) (breaking change)
- Update pyatmo ([@gieljnssns] - [#15540]) ([netatmo docs])
- Update reading when device is added ([@quthla] - [#15548]) ([sensor.bme280 docs])
- Update config entry id in entity registry ([@balloob] - [#15531])
- Upgrade to simplisafe-python v2 to use new SimpliSafe API ([@w1ll1am23] - [#15542]) ([alarm_control_panel.simplisafe docs]) (breaking change)
- More pylint 2 fixes ([@scop] - [#15565])
- Add Tuya fan support ([@huangyupeng] - [#15525]) ([tuya docs]) ([fan.tuya docs]) (new-platform)
- fix aiohttp InvalidURL exception when fetching media player image ([@azogue] - [#15572]) ([media_player docs])
- Allow MQTT Switch to have an optional state configuration ([@PrimusNZ] - [#15430]) ([switch.mqtt docs])
- Add unique_id to netgear_lte sensors ([@amelchio] - [#15584]) ([netgear_lte docs]) ([sensor.netgear_lte docs])
- Add relay addr & chan config to alarmdecoder zones ([@digiblur] - [#15242]) ([alarmdecoder docs]) ([binary_sensor.alarmdecoder docs])
- Update pyhomematic, fixes #15054, #15190 ([@danielperna84] - [#15603]) ([homematic docs])
- Throttle unavailability warnings for tplink light/switch ([@amelchio] - [#15591]) ([light.tplink docs]) ([switch.tplink docs])
- Remove entity picture of Tuya entity ([@balloob] - [#15611]) ([tuya docs])
- Upgrade mypy to 0.620 ([@scop] - [#15612])
- Pylint cleanups ([@scop] - [#15626])
- Add typing to homeassistant/*.py and homeassistant/util/ ([@andrey-git] - [#15569]) ([rachio docs])
- Refresh Sonos source list on changes ([@amelchio] - [#15605]) ([media_player.sonos docs])
- The tense is wrong ([@sherazlodhi] - [#15614])
- Suppress error between 00:00 and 01:00 ([@starkillerOG] - [#15555]) ([sensor.buienradar docs])
- Use async_create_task ([@balloob] - [#15633])
- Allow system users to refresh tokens ([@balloob] - [#15574]) ([auth docs])
- WIP: Hass.io sent token to supervisor ([@balloob] - [#15536]) ([hassio docs])
- Fix aiohttp connection reset errors ([@pvizeli] - [#15577])
- Add ability to set Zwave protection commandclass ([@turbokongen] - [#15390]) ([config docs])
- Update Neato library to allow for dynamic endpoints ([@dshokouhi] - [#15639]) ([neato docs])
- Fix typo `asayn_init` instead of `async_init` ([@wingy3181] - [#15645]) ([device_tracker.tile docs])
- Add ipban for failed login attempt in new login flow ([@awarecan] - [#15551]) ([auth docs])
- Add Tuya cover and scene platform ([@huangyupeng] - [#15587]) ([tuya docs]) ([cover.tuya docs]) ([scene.tuya docs]) (new-platform)
- Update smappy library version ([@visibilityspots] - [#15636]) ([smappee docs]) (breaking change)
- Allow changing entity ID ([@balloob] - [#15637])
- Downgrade netatmo warning log to info ([@glpatcern] - [#15652]) ([sensor.netatmo docs])
- Add turn_on/off service to camera ([@awarecan] - [#15051]) ([camera docs])
- Allow defining default turn-on values for lights in the profiles file. ([@kalimaul] - [#15493]) ([light docs])
- Added user credentials to current_user ws endpoint. ([@jeradM] - [#15558]) ([auth docs])
- Import collections abstract base classes from collections.abc ([@scop] - [#15649]) ([google_assistant docs]) ([notify docs])
- Auth typing improvements ([@scop] - [#15640])
- Add spider thermostat ([@peternijssen] - [#15499]) ([climate.spider docs]) (new-platform)
- Add Brunt Cover Device ([@eavanvalkenburg] - [#15653]) ([cover.brunt docs]) (new-platform)
- Pylint 2 useless-return fixes ([@scop] - [#15677]) ([cloud docs]) ([mailgun docs]) ([notify docs]) ([climate.heatmiser docs]) ([fan.comfoconnect docs]) ([sensor.fritzbox_callmonitor docs]) ([sensor.modem_callerid docs])
- Allow Nest Cam turn on/off ([@awarecan] - [#15681]) ([camera.nest docs])
- Upgrade pylint to 2.0.1 ([@scop] - [#15683]) ([apple_tv docs]) ([light docs]) ([calendar.todoist docs]) ([media_player.bluesound docs]) ([media_player.pandora docs]) ([sensor.citybikes docs]) ([sensor.nzbget docs]) ([sensor.pyload docs])
- Fixes a bug with showing a subset of Pollen index conditions ([@bachya] - [#15694]) ([sensor.pollen docs])
- Add spider power plug component ([@peternijssen] - [#15682]) ([spider docs]) ([switch.spider docs]) (new-platform)
- Add support for P5 FutureNow light platform ([@juhaniemi] - [#15662]) ([light.futurenow docs]) (new-platform)
- Only log change to use access token warning once ([@awarecan] - [#15690]) ([http docs])
- Add support for alarm_control_panel to MQTT Discovery. ([@rorr73] - [#15689]) ([mqtt docs]) ([alarm_control_panel.mqtt docs])
- Add Magicseaweed API support ([@jcconnell] - [#15132]) ([sensor.magicseaweed docs]) (new-platform)
- Upgrade pyvera to 0.2.44 ([@alanfischer] - [#15708]) ([vera docs])
- Remove IHC XML Element from discovery data ([@dingusdk] - [#15719]) ([ihc docs]) ([binary_sensor.ihc docs]) ([light.ihc docs]) ([sensor.ihc docs]) ([switch.ihc docs])
- Context ([@balloob] - [#15674]) ([api docs]) ([http docs]) ([light docs]) ([switch docs]) ([websocket_api docs])
- Break up components/auth ([@awarecan] - [#15713]) ([auth docs])
- Add a component for Sisyphus Kinetic Art Tables ([@jkeljo] - [#14472]) ([sisyphus docs]) ([light.sisyphus docs]) ([media_player.sisyphus docs]) (new-platform)
- Command Line Sensor - json_attributes ([@alexhardwicke] - [#15679]) ([sensor.command_line docs])
- Upgrade youtube_dl to 2018.07.21 ([@fabaff] - [#15718]) ([media_extractor docs])
- Upgrade numpy to 1.15.0 ([@fabaff] - [#15722]) ([binary_sensor.trend docs]) ([image_processing.opencv docs])
- Upgrade spiderpy to 1.2.0 ([@peternijssen] - [#15729]) ([spider docs])
- Upgrade beautifulsoup4 to 4.6.1 ([@fabaff] - [#15727]) ([device_tracker docs]) ([sensor.geizhals docs]) ([sensor.scrape docs]) ([sensor.sytadin docs])
- Upgrade mutagen to 1.41.0 ([@fabaff] - [#15739]) ([tts docs])
- Upgrade sqlalchemy to 1.2.10 ([@fabaff] - [#15737]) ([sensor.sql docs])
- Upgrade voluptuous to 0.11.3 ([@fabaff] - [#15735])
- Upgrade youtube_dl to 2018.07.29 ([@fabaff] - [#15734]) ([media_extractor docs])
- Upgrade pyowm to 2.9.0 ([@fabaff] - [#15736]) ([sensor.openweathermap docs]) ([weather.openweathermap docs])
- Various updates ([@fabaff] - [#15738]) ([camera.proxy docs])
- Denonavr version push to 0.7.5 ([@starkillerOG] - [#15743]) ([media_player.denonavr docs])
- Make FutureNow light remember last brightness when turning on ([@juhaniemi] - [#15733]) ([light.futurenow docs])
- Add Genie Aladdin Connect cover component ([@shoejosh] - [#15699]) ([cover.aladdin_connect docs]) (new-platform)
- Add mvglive option to store multiple departures in attributes ([@DavidMStraub] - [#15454]) ([sensor.mvglive docs])
- Add other wemo motion sensor identifier ([@danielfaulknor] - [#15627]) ([wemo docs])
- Remove self type hints ([@awarecan] - [#15732]) ([fan docs]) ([climate.honeywell docs]) ([fan.dyson docs]) ([fan.insteon_local docs]) ([fan.template docs]) ([fan.wink docs]) ([fan.zha docs])
- Fix Min/Max Kelvin color temp attribute for Google ([@bryanyork] - [#15697]) ([google_assistant docs]) (beta fix)
- Only report color temp when in the correct color mode ([@Kane610] - [#15791]) ([light.deconz docs]) (beta fix)
- Return True from Nest setup ([@balloob] - [#15797]) ([nest docs]) (beta fix)
[#14472]: https://github.com/home-assistant/home-assistant/pull/14472
[#15051]: https://github.com/home-assistant/home-assistant/pull/15051
[#15132]: https://github.com/home-assistant/home-assistant/pull/15132
[#15242]: https://github.com/home-assistant/home-assistant/pull/15242
[#15356]: https://github.com/home-assistant/home-assistant/pull/15356
[#15390]: https://github.com/home-assistant/home-assistant/pull/15390
[#15430]: https://github.com/home-assistant/home-assistant/pull/15430
[#15441]: https://github.com/home-assistant/home-assistant/pull/15441
[#15442]: https://github.com/home-assistant/home-assistant/pull/15442
[#15451]: https://github.com/home-assistant/home-assistant/pull/15451
[#15454]: https://github.com/home-assistant/home-assistant/pull/15454
[#15455]: https://github.com/home-assistant/home-assistant/pull/15455
[#15467]: https://github.com/home-assistant/home-assistant/pull/15467
[#15475]: https://github.com/home-assistant/home-assistant/pull/15475
[#15484]: https://github.com/home-assistant/home-assistant/pull/15484
[#15487]: https://github.com/home-assistant/home-assistant/pull/15487
[#15490]: https://github.com/home-assistant/home-assistant/pull/15490
[#15493]: https://github.com/home-assistant/home-assistant/pull/15493
[#15498]: https://github.com/home-assistant/home-assistant/pull/15498
[#15499]: https://github.com/home-assistant/home-assistant/pull/15499
[#15500]: https://github.com/home-assistant/home-assistant/pull/15500
[#15503]: https://github.com/home-assistant/home-assistant/pull/15503
[#15510]: https://github.com/home-assistant/home-assistant/pull/15510
[#15516]: https://github.com/home-assistant/home-assistant/pull/15516
[#15523]: https://github.com/home-assistant/home-assistant/pull/15523
[#15525]: https://github.com/home-assistant/home-assistant/pull/15525
[#15529]: https://github.com/home-assistant/home-assistant/pull/15529
[#15531]: https://github.com/home-assistant/home-assistant/pull/15531
[#15536]: https://github.com/home-assistant/home-assistant/pull/15536
[#15540]: https://github.com/home-assistant/home-assistant/pull/15540
[#15542]: https://github.com/home-assistant/home-assistant/pull/15542
[#15548]: https://github.com/home-assistant/home-assistant/pull/15548
[#15551]: https://github.com/home-assistant/home-assistant/pull/15551
[#15555]: https://github.com/home-assistant/home-assistant/pull/15555
[#15558]: https://github.com/home-assistant/home-assistant/pull/15558
[#15565]: https://github.com/home-assistant/home-assistant/pull/15565
[#15569]: https://github.com/home-assistant/home-assistant/pull/15569
[#15572]: https://github.com/home-assistant/home-assistant/pull/15572
[#15574]: https://github.com/home-assistant/home-assistant/pull/15574
[#15577]: https://github.com/home-assistant/home-assistant/pull/15577
[#15584]: https://github.com/home-assistant/home-assistant/pull/15584
[#15587]: https://github.com/home-assistant/home-assistant/pull/15587
[#15591]: https://github.com/home-assistant/home-assistant/pull/15591
[#15603]: https://github.com/home-assistant/home-assistant/pull/15603
[#15605]: https://github.com/home-assistant/home-assistant/pull/15605
[#15611]: https://github.com/home-assistant/home-assistant/pull/15611
[#15612]: https://github.com/home-assistant/home-assistant/pull/15612
[#15614]: https://github.com/home-assistant/home-assistant/pull/15614
[#15626]: https://github.com/home-assistant/home-assistant/pull/15626
[#15627]: https://github.com/home-assistant/home-assistant/pull/15627
[#15633]: https://github.com/home-assistant/home-assistant/pull/15633
[#15636]: https://github.com/home-assistant/home-assistant/pull/15636
[#15637]: https://github.com/home-assistant/home-assistant/pull/15637
[#15639]: https://github.com/home-assistant/home-assistant/pull/15639
[#15640]: https://github.com/home-assistant/home-assistant/pull/15640
[#15645]: https://github.com/home-assistant/home-assistant/pull/15645
[#15649]: https://github.com/home-assistant/home-assistant/pull/15649
[#15652]: https://github.com/home-assistant/home-assistant/pull/15652
[#15653]: https://github.com/home-assistant/home-assistant/pull/15653
[#15662]: https://github.com/home-assistant/home-assistant/pull/15662
[#15674]: https://github.com/home-assistant/home-assistant/pull/15674
[#15677]: https://github.com/home-assistant/home-assistant/pull/15677
[#15679]: https://github.com/home-assistant/home-assistant/pull/15679
[#15681]: https://github.com/home-assistant/home-assistant/pull/15681
[#15682]: https://github.com/home-assistant/home-assistant/pull/15682
[#15683]: https://github.com/home-assistant/home-assistant/pull/15683
[#15689]: https://github.com/home-assistant/home-assistant/pull/15689
[#15690]: https://github.com/home-assistant/home-assistant/pull/15690
[#15694]: https://github.com/home-assistant/home-assistant/pull/15694
[#15697]: https://github.com/home-assistant/home-assistant/pull/15697
[#15699]: https://github.com/home-assistant/home-assistant/pull/15699
[#15708]: https://github.com/home-assistant/home-assistant/pull/15708
[#15713]: https://github.com/home-assistant/home-assistant/pull/15713
[#15718]: https://github.com/home-assistant/home-assistant/pull/15718
[#15719]: https://github.com/home-assistant/home-assistant/pull/15719
[#15722]: https://github.com/home-assistant/home-assistant/pull/15722
[#15727]: https://github.com/home-assistant/home-assistant/pull/15727
[#15729]: https://github.com/home-assistant/home-assistant/pull/15729
[#15732]: https://github.com/home-assistant/home-assistant/pull/15732
[#15733]: https://github.com/home-assistant/home-assistant/pull/15733
[#15734]: https://github.com/home-assistant/home-assistant/pull/15734
[#15735]: https://github.com/home-assistant/home-assistant/pull/15735
[#15736]: https://github.com/home-assistant/home-assistant/pull/15736
[#15737]: https://github.com/home-assistant/home-assistant/pull/15737
[#15738]: https://github.com/home-assistant/home-assistant/pull/15738
[#15739]: https://github.com/home-assistant/home-assistant/pull/15739
[#15743]: https://github.com/home-assistant/home-assistant/pull/15743
[#15791]: https://github.com/home-assistant/home-assistant/pull/15791
[#15797]: https://github.com/home-assistant/home-assistant/pull/15797
[@DavidMStraub]: https://github.com/DavidMStraub
[@JackNova]: https://github.com/JackNova
[@Kane610]: https://github.com/Kane610
[@PrimusNZ]: https://github.com/PrimusNZ
[@alanfischer]: https://github.com/alanfischer
[@alexhardwicke]: https://github.com/alexhardwicke
[@amelchio]: https://github.com/amelchio
[@andrey-git]: https://github.com/andrey-git
[@awarecan]: https://github.com/awarecan
[@azogue]: https://github.com/azogue
[@bachya]: https://github.com/bachya
[@balloob]: https://github.com/balloob
[@bryanyork]: https://github.com/bryanyork
[@danielfaulknor]: https://github.com/danielfaulknor
[@danielperna84]: https://github.com/danielperna84
[@digiblur]: https://github.com/digiblur
[@dingusdk]: https://github.com/dingusdk
[@dshokouhi]: https://github.com/dshokouhi
[@eavanvalkenburg]: https://github.com/eavanvalkenburg
[@fabaff]: https://github.com/fabaff
[@fucm]: https://github.com/fucm
[@gieljnssns]: https://github.com/gieljnssns
[@glpatcern]: https://github.com/glpatcern
[@huangyupeng]: https://github.com/huangyupeng
[@jcconnell]: https://github.com/jcconnell
[@jeradM]: https://github.com/jeradM
[@jkeljo]: https://github.com/jkeljo
[@juhaniemi]: https://github.com/juhaniemi
[@kalimaul]: https://github.com/kalimaul
[@lukiffer]: https://github.com/lukiffer
[@mu4yu3]: https://github.com/mu4yu3
[@mxworm]: https://github.com/mxworm
[@peternijssen]: https://github.com/peternijssen
[@pvizeli]: https://github.com/pvizeli
[@quthla]: https://github.com/quthla
[@rorr73]: https://github.com/rorr73
[@scop]: https://github.com/scop
[@sherazlodhi]: https://github.com/sherazlodhi
[@shoejosh]: https://github.com/shoejosh
[@squirtbrnr]: https://github.com/squirtbrnr
[@starkillerOG]: https://github.com/starkillerOG
[@teharris1]: https://github.com/teharris1
[@turbokongen]: https://github.com/turbokongen
[@visibilityspots]: https://github.com/visibilityspots
[@w1ll1am23]: https://github.com/w1ll1am23
[@wingy3181]: https://github.com/wingy3181
[alarm_control_panel.mqtt docs]: /components/alarm_control_panel.mqtt/
[alarm_control_panel.simplisafe docs]: /components/alarm_control_panel.simplisafe/
[alarmdecoder docs]: /components/alarmdecoder/
[api docs]: /components/api/
[apple_tv docs]: /components/apple_tv/
[arlo docs]: /components/arlo/
[auth docs]: /components/auth/
[binary_sensor.alarmdecoder docs]: /components/binary_sensor.alarmdecoder/
[binary_sensor.ihc docs]: /components/binary_sensor.ihc/
[binary_sensor.insteon_plm docs]: /components/binary_sensor.insteon_plm/
[binary_sensor.tahoma docs]: /components/binary_sensor.tahoma/
[binary_sensor.trend docs]: /components/binary_sensor.trend/
[calendar.todoist docs]: /components/calendar.todoist/
[camera docs]: /components/camera/
[camera.demo docs]: /components/camera.demo/
[camera.nest docs]: /components/camera.nest/
[camera.proxy docs]: /components/camera.proxy/
[climate.heatmiser docs]: /components/climate.heatmiser/
[climate.honeywell docs]: /components/climate.honeywell/
[climate.spider docs]: /components/climate.spider/
[climate.tuya docs]: /components/climate.tuya/
[cloud docs]: /components/cloud/
[config docs]: /components/config/
[cover.aladdin_connect docs]: /components/cover.aladdin_connect/
[cover.brunt docs]: /components/cover.brunt/
[cover.tuya docs]: /components/cover.tuya/
[device_tracker docs]: /components/device_tracker/
[device_tracker.tile docs]: /components/device_tracker.tile/
[fan docs]: /components/fan/
[fan.comfoconnect docs]: /components/fan.comfoconnect/
[fan.dyson docs]: /components/fan.dyson/
[fan.insteon_local docs]: /components/fan.insteon_local/
[fan.template docs]: /components/fan.template/
[fan.tuya docs]: /components/fan.tuya/
[fan.wink docs]: /components/fan.wink/
[fan.zha docs]: /components/fan.zha/
[google_assistant docs]: /components/google_assistant/
[hassio docs]: /components/hassio/
[homematic docs]: /components/homematic/
[homematicip_cloud docs]: /components/homematicip_cloud/
[http docs]: /components/http/
[ihc docs]: /components/ihc/
[image_processing.opencv docs]: /components/image_processing.opencv/
[insteon_plm docs]: /components/insteon_plm/
[light docs]: /components/light/
[light.deconz docs]: /components/light.deconz/
[light.futurenow docs]: /components/light.futurenow/
[light.ihc docs]: /components/light.ihc/
[light.mqtt docs]: /components/light.mqtt/
[light.sisyphus docs]: /components/light.sisyphus/
[light.tplink docs]: /components/light.tplink/
[mailgun docs]: /components/mailgun/
[media_extractor docs]: /components/media_extractor/
[media_player docs]: /components/media_player/
[media_player.bluesound docs]: /components/media_player.bluesound/
[media_player.denonavr docs]: /components/media_player.denonavr/
[media_player.pandora docs]: /components/media_player.pandora/
[media_player.sisyphus docs]: /components/media_player.sisyphus/
[media_player.sonos docs]: /components/media_player.sonos/
[mqtt docs]: /components/mqtt/
[neato docs]: /components/neato/
[nest docs]: /components/nest/
[netatmo docs]: /components/netatmo/
[netgear_lte docs]: /components/netgear_lte/
[notify docs]: /components/notify/
[rachio docs]: /components/rachio/
[scene.tuya docs]: /components/scene.tuya/
[sensor.bme280 docs]: /components/sensor.bme280/
[sensor.buienradar docs]: /components/sensor.buienradar/
[sensor.citybikes docs]: /components/sensor.citybikes/
[sensor.command_line docs]: /components/sensor.command_line/
[sensor.fritzbox_callmonitor docs]: /components/sensor.fritzbox_callmonitor/
[sensor.geizhals docs]: /components/sensor.geizhals/
[sensor.ihc docs]: /components/sensor.ihc/
[sensor.magicseaweed docs]: /components/sensor.magicseaweed/
[sensor.modem_callerid docs]: /components/sensor.modem_callerid/
[sensor.moon docs]: /components/sensor.moon/
[sensor.mvglive docs]: /components/sensor.mvglive/
[sensor.netatmo docs]: /components/sensor.netatmo/
[sensor.netgear_lte docs]: /components/sensor.netgear_lte/
[sensor.nzbget docs]: /components/sensor.nzbget/
[sensor.openweathermap docs]: /components/sensor.openweathermap/
[sensor.pollen docs]: /components/sensor.pollen/
[sensor.pyload docs]: /components/sensor.pyload/
[sensor.scrape docs]: /components/sensor.scrape/
[sensor.sql docs]: /components/sensor.sql/
[sensor.strings.moon.json docs]: /components/sensor.strings.moon.json/
[sensor.sytadin docs]: /components/sensor.sytadin/
[sensor.waze_travel_time docs]: /components/sensor.waze_travel_time/
[sisyphus docs]: /components/sisyphus/
[smappee docs]: /components/smappee/
[spider docs]: /components/spider/
[switch docs]: /components/switch/
[switch.ihc docs]: /components/switch.ihc/
[switch.insteon_plm docs]: /components/switch.insteon_plm/
[switch.mqtt docs]: /components/switch.mqtt/
[switch.spider docs]: /components/switch.spider/
[switch.tplink docs]: /components/switch.tplink/
[tahoma docs]: /components/tahoma/
[tts docs]: /components/tts/
[tuya docs]: /components/tuya/
[vacuum.neato docs]: /components/vacuum.neato/
[vera docs]: /components/vera/
[weather.openweathermap docs]: /components/weather.openweathermap/
[websocket_api docs]: /components/websocket_api/
[wemo docs]: /components/wemo/
[zwave docs]: /components/zwave/

BIN
source/images/blog/2018-08-0.75/change-entity.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 11 KiB

BIN
source/images/blog/2018-08-0.75/components.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 58 KiB

BIN
source/images/supported_brands/aladdin_connect.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 7.4 KiB

BIN
source/images/supported_brands/android_ip_webcam.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 28 KiB

After

Width:  |  Height:  |  Size: 11 KiB

BIN
source/images/supported_brands/anel.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 26 KiB

After

Width:  |  Height:  |  Size: 9.0 KiB

BIN
source/images/supported_brands/beaglebone-black.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 26 KiB

After

Width:  |  Height:  |  Size: 7.7 KiB

BIN
source/images/supported_brands/belkin_wemo.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 28 KiB

After

Width:  |  Height:  |  Size: 8.2 KiB

BIN
source/images/supported_brands/brunt.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 19 KiB

BIN
source/images/supported_brands/centos.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 28 KiB

After

Width:  |  Height:  |  Size: 5.6 KiB

BIN
source/images/supported_brands/citybikes.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 26 KiB

After

Width:  |  Height:  |  Size: 10 KiB

BIN
source/images/supported_brands/cpu.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 26 KiB

After

Width:  |  Height:  |  Size: 8.9 KiB

BIN
source/images/supported_brands/dte_energy.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 28 KiB

After

Width:  |  Height:  |  Size: 7.4 KiB

BIN
source/images/supported_brands/duke_energy.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 43 KiB

After

Width:  |  Height:  |  Size: 15 KiB

BIN
source/images/supported_brands/familyhub.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 28 KiB

After

Width:  |  Height:  |  Size: 9.3 KiB

BIN
source/images/supported_brands/iperf3.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 37 KiB

After

Width:  |  Height:  |  Size: 24 KiB

BIN
source/images/supported_brands/kiwi.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 34 KiB

After

Width:  |  Height:  |  Size: 8.5 KiB

BIN
source/images/supported_brands/magicseaweed.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 2.0 KiB

BIN
source/images/supported_brands/octoprint.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 26 KiB

After

Width:  |  Height:  |  Size: 7.7 KiB

BIN
source/images/supported_brands/p5.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 25 KiB

BIN
source/images/supported_brands/pocketcasts.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 28 KiB

After

Width:  |  Height:  |  Size: 9.8 KiB

BIN
source/images/supported_brands/sisyphus.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 13 KiB

BIN
source/images/supported_brands/sonarr.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 30 KiB

After

Width:  |  Height:  |  Size: 9.7 KiB

BIN
source/images/supported_brands/spider.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 14 KiB

BIN
source/images/supported_brands/tomato.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 29 KiB

After

Width:  |  Height:  |  Size: 7.3 KiB

BIN
source/images/supported_brands/universal_devices.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 27 KiB

After

Width:  |  Height:  |  Size: 8.8 KiB

BIN
source/images/supported_brands/vesync.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 28 KiB

After

Width:  |  Height:  |  Size: 13 KiB

BIN
source/images/supported_brands/wirelesstag.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 83 KiB

After

Width:  |  Height:  |  Size: 24 KiB

BIN
source/images/supported_brands/woonveilig.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 27 KiB

After

Width:  |  Height:  |  Size: 9.7 KiB

2
source/lovelace/changelog.markdown
View File

@ -108,7 +108,7 @@ footer: true
- `picture-elements` combined `service.domain` and `service.server` into `service`
- 📣 `entities` allow custom title just like `glance`
- 📣 `entity-filter` allow auto-hide if empty using `show_empty: false`
- 🔧 Fix card size calculation `horizontal-stack`/`vertical-stack`
- 🔧 Fix card size calculation `horizontal-stack`/`vertical-stack`
## {% linkable_title Changes in 0.73.0b0 %}

7
source/lovelace/index.markdown
View File

@ -45,6 +45,13 @@ Create a new file `<config>/ui-lovelace.yaml` and add the following content. Adj
```yaml
title: My Awesome Home
# Include external resources
resources:
- url: /local/my-custom-card.js
type: js
- url: /local/my-webfont.css
type: css
# 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