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-23 09:17:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'current' into next

Browse Source
This commit is contained in:
Paulus Schoutsen 2019-03-06 15:47:02 -08:00
commit 4dafc5c4f8
62 changed files with 1656 additions and 937 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
_config.yml
View File

@ -138,9 +138,9 @@ social:
# Home Assistant release details
current_major_version: 0
current_minor_version: 88
current_patch_version: 2
date_released: 2019-02-27
current_minor_version: 89
current_patch_version: 0
date_released: 2019-03-06
# Either # or the anchor link to latest release notes in the blog post.
# Must be prefixed with a # and have double quotes around it.

2
source/_addons/configurator.markdown
View File

@ -120,7 +120,7 @@ loglevel:
type: string
default: info
sesame:
description: Secret token to dynamically allow access from the IP the request originates from. Open your bookmark https://hassio.yourdomain.com:8123/somesecretnobodycanguess while `allowed_networks` is set to `[]` and your IP will get whitelisted. You can use the Network status menu to revoke IP addresses for which access has been granted. Regular authentication is still required.
description: Secret token to dynamically allow access from the IP the request originates from. Open your bookmark https://hassio.yourdomain.com:3218/somesecretnobodycanguess while `allowed_networks` is set to `[]` and your IP will get whitelisted. You can use the Network status menu to revoke IP addresses for which access has been granted. Regular authentication is still required.
required: false
type: string
sesame_totp_secret:

2
source/_addons/git_pull.markdown
View File

@ -61,7 +61,7 @@ Load and update configuration files for Home Assistant from a [Git](https://git-
* **interval** (*Required*): The interval in seconds to poll the repo for if automatic polling is enabled.
- **deployment_user** (*Optional*): Username to use when authenticating to a repository with a username and password.
- **deployment_password** (*Optional*): Password to use when authenticating to a repository. Ignored if `deployment_user` is not set.
- **deployment_key** (*Optional*): A private SSH key that will be used for communication during Git operations. This key is mandatory for ssh-accessed repositories, which are the ones with the following pattern: `<user>@<host>:<repository path>`.
- **deployment_key** (*Optional*): A private SSH key that will be used for communication during Git operations. This key is mandatory for ssh-accessed repositories, which are the ones with the following pattern: `<user>@<host>:<repository path>`. This key has to be created without a passphrase.
- **deployment_key_protocol** (*Optional*): The key protocol. Default is `rsa`. Valid protocols are:
* **dsa**

2
source/_addons/mariadb.markdown
View File

@ -83,5 +83,5 @@ Use the following configuration in Home Assistant to use the database above:
```yaml
recorder:
db_url: mysql://hass:securePassword@core-mariadb/homeassistant
db_url: mysql://hass:securePassword@core-mariadb/homeassistant?charset=utf8
```

35
source/_components/alarm_control_panel.spc.markdown
View File

@ -1,35 +0,0 @@
---
layout: page
title: "Vanderbilt SPC Alarm"
description: "Instructions on how to setup the Vanderbilt SPC Alarm control panel within Home Assistant."
date: 2017-05-18 22:01
sidebar: true
comments: false
sharing: true
footer: true
logo: vanderbilt_spc.png
ha_category: Alarm
ha_release: 0.47
ha_iot_class: "Local Push"
---
The `spc` alarm control panel platform allows you to control your [Vanderbilt SPC](https://www.spcsupportinfo.com/) alarms.
The requirement is that you have setup your [SPC hub](/components/spc/).
The `changed_by` attribute enables one to be able to take different actions depending on who armed/disarmed the alarm in [automation](/getting-started/automation/).
```yaml
automation:
- alias: Alarm status changed
trigger:
- platform: state
entity_id: alarm_control_panel.alarm_1
action:
- service: notify.notify
data_template:
message: >
{% raw %}Alarm changed from {{ trigger.from_state.state }}
to {{ trigger.to_state.state }}
by {{ trigger.to_state.attributes.changed_by }}{% endraw %}
```

2
source/_components/asterisk_mbox.markdown
View File

@ -11,6 +11,8 @@ logo: asterisk.png
ha_category: Mailbox
ha_iot_class: "Local Push"
ha_release: 0.51
redirect_from:
- /components/mailbox.asterisk_mbox/
---
The `asterisk_mbox` Asterisk Voicemail integration for Home Assistant allows you to view, listen to, and delete voicemails from an Asterisk voicemail mailbox. The component includes a panel on the frontend that provides caller-id and speech-to-text transcription (using Google's API) of messages in addition to playback and message deletion. There is also an included sensor that indicates of the number of available messages. There is no requirement that the Asterisk PBX and Home Assistant are running on the same machine.

33
source/_components/binary_sensor.gc100.markdown
View File

@ -1,33 +0,0 @@
---
layout: page
title: gc100 Binary Sensor
description: "Instructions on how to set up a gc100 binary sensor within Home Assistant."
date: 2017-10-27 17:26
sidebar: true
comments: false
sharing: true
footer: true
ha_category: Binary Sensor
ha_release: 0.57
ha_iot_class: "Local Polling"
---
To enable this sensor, you first have to set up [gc100](/components/gc100/), and add the following lines to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
binary_sensor:
- platform: gc100
ports:
- '3:1': Doorchime
- '3:2': Garage Obstruction
```
{% configuration %}
ports:
description: >
A list of module-address to name mappings in the format `'x:y': name`,
where x is module #, y is address.
required: true
type: list
{% endconfiguration %}

85
source/_components/binary_sensor.pilight.markdown
View File

@ -1,85 +0,0 @@
---
layout: page
title: "Pilight Binary Sensor"
description: "Instructions on how to integrate Pilight binary sensors within Home Assistant."
date: 2017-03-24 20:41
sidebar: true
comments: false
sharing: true
footer: true
logo: pilight.png
ha_category: DIY
ha_release: 0.44
ha_iot_class: "Local Polling"
---
The `pilight` binary sensor platform implement the
[pilight hub](/components/pilight/) binary sensor functionality.
Two type of Pilight binary sensor configuration available. A normal sensor which
send the on and off state cyclical and a trigger sensor which send only a
trigger when an event happened (for example lots of cheap PIR motion detector).
## {% linkable_title Configuration %}
To enable a Pilight binary sensor in your installation,
add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
binary_sensor:
- platform: pilight
variable: 'state'
```
{% configuration %}
variable:
description: The variable name in the data stream that defines the sensor value.
required: true
type: string
payload:
description: >
Message payload identifiers.
Only if all identifiers are matched the sensor value is set.
required: true
type: string
name:
description: Name of the sensor.
required: false
type: string
payload_on:
description: "Variable `on` value. The component will recognize this as logical '1'."
required: false
type: [string, float, integer]
payload_off:
description: "Variable `off` value. The component will recognize this as logical '0'."
required: false
type: [string, float, integer]
disarm_after_trigger:
description: Configure sensor as trigger type.
required: false
type: boolean
reset_delay_sec:
description: >
Seconds before the sensor is disarmed if
`disarm_after_trigger` is set to true.
required: false
type: integer
default: 30
{% endconfiguration %}
## {% linkable_title Full example %}
A full configuration example could look like this:
```yaml
# Example configuration.yaml entry
binary_sensor:
- platform: pilight
name: 'Motion'
variable: 'state'
payload:
unitcode: 371399
payload_on: 'closed'
disarm_after_trigger: true
reset_delay_sec: 30
```

20
source/_components/binary_sensor.spc.markdown
View File

@ -1,20 +0,0 @@
---
layout: page
title: "SPC Binary Sensor"
description: "Instructions on how to integrate Vanderbilt SPC binary sensors into Home Assistant."
date: 2017-05-18 22:05
sidebar: true
comments: false
sharing: true
footer: true
logo: vanderbilt_spc.png
ha_release: 0.47
ha_category: Binary Sensor
ha_iot_class: "Local Push"
---
The `spc` platform allows you to get data from your [Vanderbilt SPC](http://www.spc-intruder-detection.com/ssp-spc/) binary sensors from within Home Assistant.
Check the [type/class](/components/binary_sensor/) list for a possible visualization of your zone. Currently motion, smoke and door sensors are supported.
The requirement is that you have setup your [SPC hub](/components/spc/).

16
source/_components/binary_sensor.zwave.markdown
View File

@ -1,16 +0,0 @@
---
layout: page
title: "Z-Wave Binary Sensor"
description: "Instructions on how to setup the Z-Wave binary sensors within Home Assistant."
date: 2016-02-22 07:00
sidebar: true
comments: false
sharing: true
footer: true
logo: z-wave.png
ha_category: Binary Sensor
ha_release: 0.14
ha_iot_class: "Local Push"
---
To get your Z-Wave binary sensors working with Home Assistant, follow the instructions for the general [Z-Wave component](/components/zwave/).

29
source/_components/camera.mqtt.markdown
View File

@ -41,4 +41,33 @@ unique_id:
description: An ID that uniquely identifies this camera. If two cameras have the same unique ID Home Assistant will raise an exception.
required: false
type: string
device:
description: "Information about the device this camera is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set."
required: false
type: map
keys:
identifiers:
description: 'A list of IDs that uniquely identify the device. For example a serial number.'
required: false
type: list, string
connections:
description: 'A list of connections of the device to the outside world as a list of tuples `[connection_type, connection_identifier]`. For example the MAC address of a network interface: `"connections": ["mac", "02:5b:26:a8:dc:12"]`.'
required: false
type: list
manufacturer:
description: The manufacturer of the device.
required: false
type: string
model:
description: The model of the device.
required: false
type: string
name:
description: The name of the device.
required: false
type: string
sw_version:
description: The firmware version of the device.
required: false
type: string
{% endconfiguration %}

83
source/_components/climate.zwave.markdown
View File

@ -1,83 +0,0 @@
---
layout: page
title: "Z-Wave Climate"
description: "Instructions on how to set up the Z-Wave thermostat or HVAC within Home Assistant."
date: 2016-04-03 9:52
sidebar: true
comments: false
sharing: true
footer: true
logo: z-wave.png
ha_category: Climate
ha_release: 0.17
ha_iot_class: "Local Push"
---
To get your Z-Wave thermostat or HVAC unit working with Home Assistant, follow the instructions for the general [Z-Wave component](/getting-started/z-wave/).
<p class='note'>
Thermostats with support for fan modes or different operating modes, will be handled like a HVAC device and will also be detected as one.
If the thermostat supports different operating modes, you will get one thermostat entity for each mode. These can be hidden with settings using the customize setting in the `configuration.yaml` file.
</p>
To enable the climate component for your Z-Wave network, add the following to your `configuration.yaml` file.
```yaml
climate:
- platform: zwave
```
Once enabled, any Z-Wave climate devices will be available to Home Assistant. Multiple entities may be created. The following entities are created for a Remotec ZXT-120.
- `climate.remotec_zxt120_heating_1_id`: Allows you to control the connected device. See below for examples.
- `sensor.remotec_zxt120_temperature_38`: A sensor which returns the current temperature set on the attached device.
## {% linkable_title Automating Z-Wave Climate Devices %}
The following examples will instruct a Remotec ZXT-120 to turn the attached device mode to Heating, and set the temperature at 24 degrees after 8pm. Add it to `automation.yaml`.
```yaml
automation:
- alias: Turn on Heater at 8pm
trigger:
- platform: time
at: "20:00:00"
action:
- service: climate.set_operation_mode
data:
entity_id: climate.remotec_zxt120_heating_1_id
operation_mode: Heat
- service: climate.set_temperature
data:
entity_id: climate.remotec_zxt120_heating_1_39
temperature: 24
```
Generally, in Home Assistant, you can use the `homeassistant/turn_off` service to turn devices off. For the Remotec ZXT-120, you must instead make a service call like the following.
```yaml
automation:
- alias: Turn off Heater at 9pm
trigger:
- platform: time
at: "21:00:00"
action:
- service: climate.set_operation_mode
data:
entity_id: climate.remotec_zxt120_heating_1_id
operation_mode: 'Off'
```
**Note:** In the example above, the word `Off` is encased in single quotes to be valid YAML.
## {% linkable_title Test if it works %}
A simple way to test if your Z-Wave climate device is working is to use <img src='/images/screenshots/developer-tool-services-icon.png' alt='service developer tool icon' class="no-shadow" height="38" /> **Services** from the **Developer Tools**. Choose the applicable Climate service from the list of **Available services:** and enter something like the sample below into the **Service Data** field and then press **CALL SERVICE**.
```json
{
"entity_id": "climate.remotec_zxt120_heating_1_id",
"operation_mode": "Heat"
}
```

4
source/_components/cover.mqtt.markdown
View File

@ -173,6 +173,10 @@ tilt_invert_state:
required: false
type: boolean
default: false
device_class:
description: The [type/class](/components/cover/#device-class) of the cover to set the icon in the frontend.
required: false
type: string
json_attributes_topic:
description: The MQTT topic subscribed to receive a JSON dictionary payload and then set as sensor attributes. Usage example can be found in [MQTT sensor](/components/sensor.mqtt/#json-attributes-topic-configuration) documentation.
required: false

27
source/_components/cover.zwave.markdown
View File

@ -1,27 +0,0 @@
---
layout: page
title: "Z-Wave Cover"
description: "Instructions on how to setup the Z-Wave covers within Home Assistant."
date: 2016-12-18 19:41
sidebar: true
comments: false
sharing: true
footer: true
logo: z-wave.png
ha_category: Cover
ha_release: 0.23
ha_iot_class: "Local Push"
---
Z-Wave garage doors, blinds, and roller shutters are supported as cover in Home Assistant.
To get your Z-Wave covers working with Home Assistant, follow the instructions for the general [Z-Wave component](/components/zwave/).
If you discover that you need to [invert the operation](/docs/z-wave/installation/#invert_openclose_buttons) of open/close for a particular device, you may change this behavior in your Z-Wave section of your `configuration.yaml` file as follows:
```yaml
zwave:
device_config:
cover.my_cover:
invert_openclose_buttons: true
```

3
source/_components/deconz.markdown
View File

@ -46,7 +46,8 @@ There is currently support for the following device types within Home Assistant:
## {% linkable_title Recommended way of running deCONZ %}
Use [community container](https://hub.docker.com/r/marthoc/deconz/) by Marthoc for your deCONZ needs. It works both as a standalone container as well as with HASS.io.
If you are running Hass.io, an official add-on for Deconz is available in the add-on store.
Otherwise, use [community container](https://hub.docker.com/r/marthoc/deconz/) by Marthoc for your deCONZ needs.
### {% linkable_title Supported devices %}

32
source/_components/device_tracker.huawei_lte.markdown
View File

@ -1,32 +0,0 @@
---
layout: page
title: "Huawei LTE Router Device Tracker"
description: "Instructions on how to use Huawei LTE routers to track devices within Home Assistant."
date: 2018-09-08 20:00
sidebar: true
comments: false
sharing: true
footer: true
logo: huawei.svg
ha_category: Presence Detection
ha_release: 0.79
---
This platform offers presence detection by looking at connected devices to a [Huawei LTE router](https://consumer.huawei.com/en/smart-home/).
This requires you to have set up the [Huawei LTE component](/components/huawei_lte/).
## {% linkable_title Configuration %}
To enable the sensor, add the following lines to your
`configuration.yaml` file:
```yaml
# Example configuration.yaml entry
device_tracker:
- platform: huawei_lte
```
See the [device tracker component page](/components/device_tracker/)
for instructions how to configure the people to be tracked.

6
source/_components/device_tracker.icloud.markdown
View File

@ -63,11 +63,11 @@ You may receive an email from Apple stating that someone has logged into your ac
To disable the drainage of the battery, a dynamic interval is being used for each individual device instead of a fixed interval for all devices linked to one account. The dynamic interval is based on the current zone of a device, the distance towards home and the battery level of the device.
2 Steps Authentication is enabled for iCloud. The component will ask which device you want to use as Trusted Device and then you can enter the code that has been sent to that device. The duration of this authentication is determined by Apple, but is now at 2 months, so you will only need to verify your account each two months, even after restarting Home Assistant.
2 Factor Authentication is the improved version of 2 Steps Authentication, this is still not supported by the pyicloud library. Therefore it's not possible to use it with the device_tracker yet.
If 2 Step Authentication is enabled for your iCloud account. The component will ask which device you want to use as Trusted Device and component will send a prompt to that device with the code which you can enter in Home Assistant. The duration of this authentication is determined by Apple, but is now at 2 months, so you will only need to verify your account each two months.
2 Factor Authentication is the improved version of 2 Step Authentication, this is still not supported by the pyicloud library. Therefore it's not possible to use it with the device_tracker yet.
4 services are available for this component:
- **icloud_update**: This service can be used to ask for an update of a certain iDevice. The `account_name` and `device_name` are optional. Request will result in new Home Assistant [state_changed](/docs/configuration/events/#event-state_changed) event describing current iphone location. Can be used in automations when manual location update is needed, e.g., to check if anyone is home when door's been opened.
- **icloud_lost_iphone**: This service will play the Lost iPhone sound on a certain iDevice. The `account_name` and `device_name` are optional.
- **icloud_set_interval**: This service will change the dynamic interval of an iDevice. The `account_name` and `device_name` are optional. If `interval` is used in the service_data, the iDevice will be updated with that new interval. That interval will be fixed until the iDevice changes zone or if this service is called again. If `interval` isn't used in the service_data, the interval for that iDevice will revert back to its default dynamic interval based on its current zone, its distance towards home and its battery level.
- **icloud_reset_account**: This service can be used to reset an iCloud account. This is helpful when not all devices are being found by the component or if you have added a new iDevice to your account. The `account_name` is optional.
- **icloud_reset_account**: This service can be used to reset an iCloud account. This is helpful when not all devices are found by the component or if you have added a new iDevice to your account. The `account_name` is optional.

1
source/_components/esphome.markdown
View File

@ -6,6 +6,7 @@ date: 2018-12-16 14:20
sidebar: true
comments: false
sharing: true
featured: true
footer: true
logo: esphome.png
ha_category: DIY

16
source/_components/fan.zwave.markdown
View File

@ -1,16 +0,0 @@
---
layout: page
title: "Z-Wave Fan"
description: "Instructions on how to setup the Z-Wave Fans within Home Assistant."
date: 2017-05-25 17:00
sidebar: true
comments: false
sharing: true
footer: true
logo: z-wave.png
ha_release: 0.38
ha_category: Fan
ha_iot_class: "Local Push"
---
To get your Z-Wave fans working with Home Assistant, follow the instructions for the general [Z-Wave component](/components/zwave/).

65
source/_components/gc100.markdown
View File

@ -7,22 +7,35 @@ sidebar: true
comments: false
sharing: true
footer: true
ha_category: Hub
ha_category:
- Hub
- Binary Sensor
- Switch
ha_release: 0.57
ha_iot_class: "Local Polling"
redirect_from:
- /components/binary_sensor.gc100/
- /components/switch.gc100/
---
The Global Caché [GC-100](https://www.globalcache.com/products/gc-100/) can be integrated into Home Assistant. GC-100 is a TCP-controllable
hardware device which has an array of relays, RS232 serial ports, and flexible ports which can be programmed to be either digital inputs or IR blaster outputs. There are a variety of submodels of the GC-100 which have different amounts of each I/O type.
Currently, only relays and ports configured to be digital inputs are supported in Home Assistant. For IR support, please use the iTach remote platform (/components/remote.itach/), but note that it will likely not function concurrently on the same GC100 due to limitations in the TCP socket server implementation used by Global Caché.
There is currently support for the following device types within Home Assistant:
- [Binary Sensor](binary-sensor)
- [Switch](#switch)
Currently, only relays and ports configured to be digital inputs are supported in Home Assistant. For IR support, please use the [iTach remote platform](/components/remote.itach/), but note that it will likely not function concurrently on the same GC100 due to limitations in the TCP socket server implementation used by Global Caché.
## {% linkable_title Configuration %}
To enable this device, add the following lines to your `configuration.yaml`:
```yaml
# Example configuration.yaml entry
gc100:
host: 192.168.1.114
port: 4998
host: IP_ADDRESS
```
{% configuration %}
@ -36,3 +49,47 @@ port:
default: 4998
type: integer
{% endconfiguration %}
## {% linkable_title Binary Sensor %}
To enable this sensor, you first have to set up [gc100](#configuration), and add the following lines to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
binary_sensor:
- platform: gc100
ports:
- '3:1': Doorchime
- '3:2': Garage Obstruction
```
{% configuration %}
ports:
description: >
A list of module-address to name mappings in the format `'x:y': name`,
where x is module #, y is address.
required: true
type: list
{% endconfiguration %}
## {% linkable_title Switch %}
This allows you to control and monitor the relay state on your GC100.
To enable this switch, you first have to set up [gc100](#configuration), and add the following lines to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
switch:
- platform: gc100
ports:
- '4:1': Siren
- '4:2': Sprinkler
```
{% configuration %}
ports:
description: "A list of module-address to name mappings in the format 'x:y': name, where x is module #, y is address."
required: true
type: list
{% endconfiguration %}

2
source/_components/google_pubsub.markdown
View File

@ -45,7 +45,7 @@ project_id:
required: true
type: string
topic_name:
description: The Pub/Sub topic name.
description: The Pub/Sub [relative](https://cloud.google.com/pubsub/docs/admin#resource_names) topic name (looks like `hass`).
required: true
type: string
credentials_json:

2
source/_components/history_graph.markdown
View File

@ -17,7 +17,7 @@ ha_qa_scale: internal
<img src='{{site_root}}/images/screenshots/history_graph.png' />
</p>
The `history_graph` component will make the UI display a graph similar to the graphs in `more-info` popups and the [history](/components/history/) panel.
The `history_graph` component will make the UI display a graph similar to the graphs in `more-info` popups and the [history](/components/history/) panel. If you want to add history graphs to the Lovelace UI, please check the [History Graph Card](/lovelace/history-graph/) configuration as it slightly differs from the component.
To use this component in your installation, add the following to your `configuration.yaml` file:

141
source/_components/huawei_lte.markdown
View File

@ -8,17 +8,28 @@ comments: false
sharing: true
footer: true
logo: huawei.svg
ha_category: Network
ha_category:
- Network
- Presence Detection
- Notifications
- Sensor
ha_release: 0.79
ha_iot_class: "Local Polling"
redirect_from:
- /components/notify.huawei_lte/
- /components/device_tracker.huawei_lte/
- /components/sensor.huawei_lte/
---
The Huawei LTE router integration for Home Assistant allows you to observe
and control [Huawei LTE routers](https://consumer.huawei.com/en/smart-home/).
The Huawei LTE router integration for Home Assistant allows you to observe and control [Huawei LTE routers](https://consumer.huawei.com/en/smart-home/).
The integration provides:
There is currently support for the following device types within Home Assistant:
* a sensor with device, signal, and traffic information
* a device tracker for connected devices
- [Presence Detection](#presence-detection) - a device tracker for connected devices
- [Notifications](#notifications)
- [Sensor](#sensor) - with device, signal, and traffic information
All platform requires you to have set up the [Huawei LTE component](#configuration).
## {% linkable_title Configuration %}
@ -35,17 +46,17 @@ huawei_lte:
{% configuration %}
url:
description: URL of the router web interface.
required: true
type: url
description: URL of the router web interface.
required: true
type: url
username:
description: The username used for the router web interface.
required: true
type: string
description: The username used for the router web interface.
required: true
type: string
password:
description: The password used for the router web interface.
required: true
type: string
description: The password used for the router web interface.
required: true
type: string
{% endconfiguration %}
### {% linkable_title Tested routers %}
@ -58,3 +69,103 @@ Routers we know to be working with this component based on the documentation of
- Huawei B618
This is not a complete list. The component can probably connect to other Huawei LTE routers running similar firmware.
## {% linkable_title Presence Detection %}
This platform offers presence detection by looking at connected devices to a [Huawei LTE router](https://consumer.huawei.com/en/smart-home/).
To enable the sensor, add the following lines to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
device_tracker:
- platform: huawei_lte
```
See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
## {% linkable_title Notifications %}
The `huawei_lte` platform allows you to use a Huawei LTE router for notifications from Home Assistant. The messages will be sent as SMS text messages.
```yaml
# Example configuration.yaml entry
notify:
- platform: huawei_lte
recipient: "+15105550123"
```
{% configuration %}
recipient:
description: The phone number of a default recipient or a list with multiple recipients.
required: true
type: string, list
name:
description: Setting the optional parameter `name` allows multiple notifiers to be created. The notifier will bind to the service `notify.NOTIFIER_NAME`.
required: false
default: notify
type: string
url:
description: The router to use. Not needed if you only have one.
required: false
type: url
{% endconfiguration %}
To use notifications, please see the [getting started with automation page](/getting-started/automation/).
## {% linkable_title Sensor %}
The `huawei_lte` sensor platform allows you to monitor Huawei LTE routers.
The names for the item you want to monitor are dot separated paths to information returned by the router. The data set varies by router model. To see what your router provides, set logging level to debug and watch `homeassistant.components.huawei_lte` debug entries. The configuration variable description contains a few example paths just to illustrate the syntax. These may not be available on all routers or their semantics may differ, and there are quite likely many more that are not listed here.
To enable the sensor, add the following lines to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
sensor:
- platform: huawei_lte
monitored_conditions:
- device_information.SoftwareVersion
- device_signal.rssi
- traffic_statistics.CurrentDownloadRate
- traffic_statistics.TotalConnectTime
```
{% configuration %}
monitored_conditions:
description: Defines the data to monitor as sensors. Defaults to a few generally available data items expected to be available on most boxes.
required: false
default: Below is indicated which conditions are the default.
type: list
keys:
device_information.SoftwareVersion:
description: Software version.
device_information.WanIPAddress:
description: WAN interface IPv4 address.
default: default
device_information.WanIPv6Address:
description: WAN interface IPv6 address.
device_signal.rsrq:
description: The signal RSRQ value.
default: default
device_signal.rsrp:
description: The signal RSRP value.
default: default
device_signal.rssi:
description: The signal RSSI value.
default: default
device_signal.sinr:
description: The signal SINR value.
default: default
traffic_statistics.CurrentDownloadRate:
description: Current download rate, bytes/sec.
traffic_statistics.CurrentUploadRate:
description: Current upload rate, bytes/sec.
traffic_statistics.TotalUpload:
description: Total bytes uploaded since last reset.
traffic_statistics.TotalDownload:
description: Total bytes downloaded since last reset.
traffic_statistics.TotalConnectTime:
description: Total time connected since last reset.
{% endconfiguration %}

5
source/_components/lcn.markdown
View File

@ -18,6 +18,7 @@ ha_iot_class: "Local Push"
redirect_from:
- /components/light.lcn/
- /components/switch.lcn/
- /components/cover.lcn/
---
The `lcn` integration for Home Assistant allows you to connect to [LCN](http://www.lcn.eu) hardware devices.
@ -50,14 +51,14 @@ lcn:
- name: Living room cover
address: myhome.s0.m7
motor: motor1
lights:
- name: Bedroom light
address: myhome.s0.m7
output: output1
dimmable: true
transition: 5
switches:
- name: Sprinkler switch
address: myhome.s0.m7

2
source/_components/light.yeelight.markdown
View File

@ -131,6 +131,7 @@ This component is tested to work with the following models. If you have a differ
| `strip1` | YLDD02YL | Lightstrip (Color) |
| ? | YLDD04YL | Lightstrip (Color)
| `bslamp1` | MJCTD01YL | Xiaomi Mijia Bedside Lamp - WIFI Version! |
| `RGBW` | MJDP02YL | Mi Led smart Lamp - white and color WIFI Version |
| `lamp1` | MJTD01YL | Xiaomi Mijia Smart LED Desk Lamp (autodiscovery isn't possible because the device doesn't support mDNS due to the small amount of RAM) |
| `ceiling1` | YLXD01YL | Yeelight Ceiling Light |
| `ceiling2` | YLXD03YL | Yeelight Ceiling Light - Youth Version |
@ -138,6 +139,7 @@ This component is tested to work with the following models. If you have a differ
| `ceiling3` | YLXD05YL | Yeelight Ceiling Light (Jiaoyue 480) |
| `ceiling4` | YLXD02YL | Yeelight Ceiling Light (Jiaoyue 650) |
## {% linkable_title Platform Services %}
### {% linkable_title Service `light.yeelight_set_mode` %}

16
source/_components/light.zwave.markdown
View File

@ -1,16 +0,0 @@
---
layout: page
title: "Z-Wave Light"
description: "Instructions on how to setup the Z-Wave lights within Home Assistant."
date: 2015-11-11 13:00
sidebar: true
comments: false
sharing: true
footer: true
logo: z-wave.png
ha_category: Light
ha_release: pre 0.7
ha_iot_class: "Local Push"
---
To get your Z-Wave lights working with Home Assistant, follow the instructions for the general [Z-Wave component](/components/zwave/).

24
source/_components/lock.zwave.markdown
View File

@ -1,24 +0,0 @@
---
layout: page
title: "Z-Wave Lock"
description: "Instructions on how to setup the Z-Wave Locks within Home Assistant."
date: 2016-05-07 08:00
sidebar: true
comments: false
sharing: true
footer: true
logo: z-wave.png
ha_category: Lock
ha_release: 0.19
ha_iot_class: "Local Push"
---
To get your Z-Wave locks working with Home Assistant, follow the instructions for the general [Z-Wave component](/components/zwave/).
Z-Wave locks will expose three services under the lock domain to manage usercodes if the lock supports it:
| Service | Description |
| ------- | ----------- |
| clear_usercode | Clears a usercode at code_slot X. Valid code_slots are 1-254, but max is defined by the lock. |
| get_usercode | Get a usercode from the lock at code_slot. Valid code_slots are 1-254, but max is defined by the lock. |
| set_usercode | Sets usercode to X at code_slot Y. Valid usercodes are at least 4 digits, and max defined by the lock. |

15
source/_components/mailbox.asterisk_mbox.markdown
View File

@ -1,15 +0,0 @@
---
layout: page
title: "Asterisk Voicemail Mailbox"
description: "Instructions on how to integrate an Asterisk Voicemail within Home Assistant."
date: 2017-06-30 18:30
sidebar: true
comments: false
sharing: true
footer: true
logo: asterisk.png
ha_category: Mailbox
ha_release: 0.51
---
The Asterisk Voicemail Mailbox provides visual and audio access to voicemail on the Asterisk PBX server. This mailbox is enabled automatically through the [Asterisk Voicemail component](/components/asterisk_mbox/) configuration.

20
source/_components/mobile_app.markdown Normal file
View File

@ -0,0 +1,20 @@
---
layout: page
title: "Mobile App"
description: "The Mobile App component allows a generic platform for integrating with mobile apps."
date: 2019-03-06 01:30
sidebar: true
comments: false
sharing: true
footer: true
logo: home-assistant.png
ha_category: "Other"
ha_release: 0.89
ha_qa_scale: internal
---
The Mobile App component allows Home Assistant mobile apps to easily integrate with Home Assistant.
If you are planning to use a mobile application that integrates with Home Assistant, we recommend that you keep this component enabled.
If you are a mobile app developer, see the [developer documentation](https://developers.home-assistant.io/docs/en/app_integration_index.html) for instructions on how to build your app on top of the mobile app component.

2
source/_components/mysensors.markdown
View File

@ -9,7 +9,7 @@ sharing: true
footer: true
logo: mysensors.png
ha_category: DIY
featured: true
featured: false
ha_iot_class: "Local Push"
---

4
source/_components/nissan_leaf.markdown
View File

@ -11,6 +11,10 @@ logo: nissan.png
ha_category: Car
ha_release: 0.89
ha_iot_class: "Cloud Polling"
redirect_from:
- /components/binary_sensor.nissan_leaf/
- /components/sensor.nissan_leaf/
- /components/switch.nissan_leaf/
---
The `nissan_leaf` component offers integration with the [NissanConnect EV](http://youplus.nissan.co.uk/GB/en/YouPlus/ConnectedServices.html) cloud service. NissanConnect EV was previously known as Nissan Carwings. It offers:

46
source/_components/notify.huawei_lte.markdown
View File

@ -1,46 +0,0 @@
---
layout: page
title: "Huawei LTE Notify"
description: "Instructions on how to add Huawei LTE notifications to Home Assistant."
date: 2018-12-23 17:00
sidebar: true
comments: false
sharing: true
footer: true
logo: huawei.svg
ha_category: Notifications
ha_release: 0.88
---
The `huawei_lte` platform allows you to use a Huawei LTE router for
notifications from Home Assistant. The messages will be sent as SMS
text messages.
This requires you to have set up the
[Huawei LTE component](/components/huawei_lte/).
```yaml
# Example configuration.yaml entry
notify:
- platform: huawei_lte
recipient: "+15105550123"
```
{% configuration %}
recipient:
description: The phone number of a default recipient or a list with multiple recipients.
required: true
type: string, list
name:
description: Setting the optional parameter `name` allows multiple notifiers to be created. The notifier will bind to the service `notify.NOTIFIER_NAME`.
required: false
default: notify
type: string
url:
description: The router to use. Not needed if you only have one.
required: false
type: url
{% endconfiguration %}
To use notifications, please see the
[getting started with automation page](/getting-started/automation/).

3
source/_components/person.markdown
View File

@ -31,7 +31,6 @@ Lets say for example, that you have 3 trackers: 'tracker_gps', 'tracker_router'
TL;DR: When you're at home, your position is determined firstly by stationary trackers (if any) and then by GPS. When you're outside your home, your position is determined firstly by GPS and then by stationary trackers.
**Hint**: When you use multiple device trackers together, especially stationary and GPS trackers, it's advisable to set `consider_home`for stationary trackers as low as possible.
@ -68,7 +67,7 @@ person:
required: true
type: string
user_id:
description: The user id of the Home Assistant user account for the person.
description: The user id of the Home Assistant user account for the person. *`user_id` (aka `ID`) of users can be inspected in the "Users"/"Manage users" screen in the configuration panel.*
required: false
type: string
device_trackers:

247
source/_components/pilight.markdown
View File

@ -8,9 +8,17 @@ comments: false
sharing: true
footer: true
logo: pilight.png
ha_category: DIY
ha_category:
- DIY
- Binary Sensor
- Sensor
- Switch
ha_release: 0.26
ha_iot_class: "Local Push"
redirect_from:
- /components/binary_sensor.pilight/
- /components/sensor.pilight/
- /components/switch.pilight/
---
[Pilight](https://www.pilight.org/) is a modular and open source solution to communicate with 433 MHz devices and runs on various small form factor computers. A lot of common [protocols](https://manual.pilight.org/protocols/index.html) are already available.
@ -19,6 +27,12 @@ This pilight hub connects to the [pilight-daemon](https://manual.pilight.org/pro
The received and supported RF codes are put on the event bus of Home Assistant and are therefore directly usable by other components (e.g., automation). Additionally a send service is provided to send RF codes.
There is currently support for the following device types within Home Assistant:
- [Binary Sensor](#binary-sensor)
- [Sensor](#sensor)
- [Switch](#switch)
## {% linkable_title Configuration %}
To integrate pilight into Home Assistant, add the following section to your `configuration.yaml` file:
@ -68,6 +82,237 @@ pilight:
- 42
```
## {% linkable_title Binary Sensor %}
The `pilight` binary sensor platform implement the [pilight hub](#configuration) binary sensor functionality. Two type of Pilight binary sensor configuration available. A normal sensor which send the on and off state cyclical and a trigger sensor which send only a trigger when an event happened (for example lots of cheap PIR motion detector).
To enable a Pilight binary sensor in your installation, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
binary_sensor:
- platform: pilight
variable: 'state'
```
{% configuration %}
variable:
description: The variable name in the data stream that defines the sensor value.
required: true
type: string
payload:
description: >
Message payload identifiers.
Only if all identifiers are matched the sensor value is set.
required: true
type: string
name:
description: Name of the sensor.
required: false
type: string
payload_on:
description: "Variable `on` value. The component will recognize this as logical '1'."
required: false
type: [string, float, integer]
payload_off:
description: "Variable `off` value. The component will recognize this as logical '0'."
required: false
type: [string, float, integer]
disarm_after_trigger:
description: Configure sensor as trigger type.
required: false
type: boolean
reset_delay_sec:
description: >
Seconds before the sensor is disarmed if
`disarm_after_trigger` is set to true.
required: false
type: integer
default: 30
{% endconfiguration %}
### {% linkable_title Full example %}
A full configuration example could look like this:
```yaml
# Example configuration.yaml entry
binary_sensor:
- platform: pilight
name: 'Motion'
variable: 'state'
payload:
unitcode: 371399
payload_on: 'closed'
disarm_after_trigger: true
reset_delay_sec: 30
```
## {% linkable_title Sensor %}
This `pilight` sensor platform for 433 MHz devices uses a value in the message payload as the sensor value. Unique identifiers (e.g., _uuid_) can be set to distinguish between multiple pilight devices. To use a pilight sensor the pilight Home Assistant hub has to be set up.
To use your sensor via pilight, make sure it is [supported](https://wiki.pilight.org/doku.php/protocols) and add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
sensor:
- platform: pilight
variable: temperature
payload:
uuid: '0000-b8-27-eb-f447d3'
```
{% configuration %}
variable:
description: The variable name in the data stream that defines the sensor value.
required: true
type: string
payload:
description: Message payload identifiers. Only if all identifiers are matched the sensor value is set.
required: true
type: string
name:
description: Name of the sensor.
required: false
default: Pilight Sensor
type: string
unit_of_measurement:
description: Defines the units of measurement of the sensor, if any.
required: false
type: string
{% endconfiguration %}
### {% linkable_title Example: Weather station %}
This section shows a real life example how to use values of a weather station.
```yaml
# Example configuration.yaml entry
sensor:
- platform: pilight
name: 'Temperature'
variable: 'temperature'
payload:
uuid: 0000-b8-27-eb-f1f72e
unit_of_measurement: '°C'
- platform: pilight
name: 'Humidity'
variable: 'humidity'
payload:
uuid: 0000-b8-27-eb-f1f72e
unit_of_measurement: '%'
- platform: pilight
name: 'Battery'
variable: 'battery'
payload:
uuid: 0000-b8-27-eb-f1f72e
unit_of_measurement: '%'
```
## {% linkable_title Switch %}
The `pilight` switch platform is issuing 433 MHz commands using [pilight](https://www.pilight.org/) to turn a 433 MHz device on or off. The Pilight Home Assistant hub has to be set up.
Additionally, RF commands can be defined that trigger this switch to turn on and off. This allows you to also use the remote shipped with your 433 MHz switch without mixing up the Home Assistant states. You can even define several on/off commands, thus several RF remotes to toggle this switch.
To be really sure that Home Assistant knows the actual state of your device it is recommended to use the RF remote with codes unknown to any of your 433 MHz devices. Thus you use the remote to trigger this switch to send the correct RF code to the device.
To define a Pilight switch, add the following lines to your `configuration.yaml`:
```yaml
# Example configuration.yaml entry
switch:
- platform: pilight
switches:
Bed light:
on_code:
protocol: intertechno_old
'on': 1
off_code:
protocol: intertechno_old
'off': 1
```
{% configuration %}
switches:
description: The list that contains all command switches.
required: true
type: string
keys:
entry:
description: Name of the command switch. Multiple entries are possible.
required: true
type: list
keys:
on_code:
description: The code to turn the device on.
required: true
type: list
off_code:
description: The code to turn the device off.
required: true
type: list
on_code_receive:
description: If given, this command will turn the switch on if it is received by pilight.
required: false
type: list
off_code_receive:
description: If given, this command will turn the switch off if it is received by pilight.
required: false
type: list
{% endconfiguration %}
Variables for the different codes (`on_code` and `off_code`):
- **protocol** (*Required*): Protocol to use, e.g., `intertechno_old` or `daycom`.
- **systemcode** (*Optional*): The systemcode of the device.
- **unit** (*Optional*): The unit to use (is equivalent to `pilight-send --unit`).
- **unitcode** (*Optional*): The unitcode to use (is equivalent to `pilight-send --unitcode`).
- **id** (*Optional*): ID of the device
- **state** (*Optional*): `'on'` or `'off'` has to be in apostrophes to be parsed correctly.
- **'off'** (*Optional*): `1` or `0`
- **'on'** (*Optional*): `1` or `0`
For possible code entries, look at the [pilight API](https://manual.pilight.org/development/api.html). All commands allowed by [pilight-send](https://manual.pilight.org/programs/send.html) can be used. Which means that if, for a certain protocol, there are different parameters used, you should be able to replace the variables above by the proper ones required by the specific protocol. When using the `elro_800_switch` or `mumbi` protocol, for example, you will have to replace the variable `unit` with `unitcode` or there will be errors occurring.
Variables for the different receive codes (`on_code_receive` and `off_code_receive`):
- **echo** (*Optional*) Set to `true` if the on-/off-code should be sent if the given code was received.
This is useful if you have paired your sender directly with the receiver to prevent sending the signal twice.
### {% linkable_title Examples %}
```yaml
switch:
- platform: pilight
switches:
Bed light:
on_code:
protocol: intertechno_old
unit: 3
id: 4
'on': 1
off_code:
protocol: intertechno_old
unit: 3
id: 4
'off': 1
on_code_receive:
protocol: daycom
systemcode: 14462
unit: 6
id: 34
state: 'on'
off_code_receive:
protocol: daycom
systemcode: 14462
unit: 6
id: 34
state: 'off'
```
## {% linkable_title Troubleshooting %}
- A list of tested RF transceiver hardware is available [here](https://manual.pilight.org/electronics/index.html). This might be useful before buying.

0
source/_components/media_player.ps4.markdown → source/_components/ps4.markdown
View File

80
source/_components/rainbird.markdown
View File

@ -8,13 +8,24 @@ comments: false
sharing: true
footer: true
logo: rainbird.png
ha_category: Irrigation
ha_category:
- Irrigation
- Sensor
- Switch
ha_release: 0.61
ha_iot_class: "Local Polling"
redirect_from:
- /components/sensor.rainbird/
- /components/switch.rainbird/
---
This `rainbird` component allows interacting with [LNK WiFi](http://www.rainbird.com/landscape/products/controllers/LNK-WiFi.htm) module of the Rain Bird Irrigation system in Home Assistant.
There is currently support for the following device types within Home Assistant:
- [Sensor](#sensor)
- [Switch](#switch)
## {% linkable_title Configuration %}
To enable it, add the following to your `configuration.yaml` file:
@ -37,6 +48,69 @@ password:
type: string
{% endconfiguration %}
Finish its configuration by visiting the [Rain Bird sensor](/components/sensor.rainbird/) and [Rain Bird switch](/components/switch.rainbird/) documentation.
<p class='note'>
Please note that due to the implementation of the API within the LNK Module, there is a concurrency issue. For example, the Rain Bird app will give connection issues (like already a connection active).
</p>
## {% linkable_title Sensor %}
This `rainbird` sensor allows interacting with [LNK WiFi](http://www.rainbird.com/landscape/products/controllers/LNK-WiFi.htm) module of the Rain Bird Irrigation system in Home Assistant.
Add the following to your `configuration.yaml` file to enable the rain sensor:
```yaml
# Example configuration.yaml entry
sensor:
- platform: rainbird
monitored_conditions:
- rainsensor
```
{% configuration %}
monitored_conditions:
description: Conditions to be monitored.
keys:
rainsensor:
description: Returns the sensor level.
{% endconfiguration %}
## {% linkable_title Switch %}
This `rainbird` switch platform allows interacting with [LNK WiFi](http://www.rainbird.com/landscape/products/controllers/LNK-WiFi.htm) module of the Rain Bird Irrigation system in Home Assistant.
Add the following to your `configuration.yaml` file to use the switch platform:
```yaml
switch:
- platform: rainbird
switches:
sprinkler_1:
zone: 1
friendly_name: "Front sprinklers"
trigger_time: 10
scan_interval: 10
sprinkler_2:
friendly_name: "Back sprinklers"
zone: 2
trigger_time: 20
scan_interval: 10
```
{% configuration %}
zone:
description: Station zone identifier.
required: true
type: string
friendly_name:
description: Just a friendly name for the station.
required: false
type: string
trigger_time:
description: The default duration to sprinkle the zone.
required: true
type: integer
scan_interval:
description: How fast to refresh the switch.
required: false
type: integer
{% endconfiguration %}

75
source/_components/sensor.huawei_lte.markdown
View File

@ -1,75 +0,0 @@
---
layout: page
title: "Huawei LTE Router Sensor"
description: "Instructions on how to integrate Huawei LTE router sensors into Home Assistant."
date: 2018-09-08 20:00
sidebar: true
comments: false
sharing: true
footer: true
logo: huawei.svg
ha_category: Network
ha_iot_class: "Local Polling"
ha_release: 0.79
---
The `huawei_lte` sensor platform allows you to monitor Huawei LTE routers.
## {% linkable_title Configuration %}
This platform requires you to have set up the [Huawei LTE component](/components/huawei_lte/).
The names for the item you want to monitor are dot separated paths to information returned by the router. The data set varies by router model. To see what your router provides, set logging level to debug and watch `homeassistant.components.huawei_lte` debug entries. The configuration variable description contains a few example paths just to illustrate the syntax. These may not be available on all routers or their semantics may differ, and there are quite likely many more that are not listed here.
## {% linkable_title Configuration %}
To enable the sensor, add the following lines to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
sensor:
- platform: huawei_lte
monitored_conditions:
- device_information.SoftwareVersion
- device_signal.rssi
- traffic_statistics.CurrentDownloadRate
- traffic_statistics.TotalConnectTime
```
{% configuration %}
monitored_conditions:
description: Defines the data to monitor as sensors. Defaults to a few generally available data items expected to be available on most boxes.
required: false
default: Below is indicated which conditions are the default.
type: list
keys:
device_information.SoftwareVersion:
description: Software version.
device_information.WanIPAddress:
description: WAN interface IPv4 address.
default: default
device_information.WanIPv6Address:
description: WAN interface IPv6 address.
device_signal.rsrq:
description: The signal RSRQ value.
default: default
device_signal.rsrp:
description: The signal RSRP value.
default: default
device_signal.rssi:
description: The signal RSSI value.
default: default
device_signal.sinr:
description: The signal SINR value.
default: default
traffic_statistics.CurrentDownloadRate:
description: Current download rate, bytes/sec.
traffic_statistics.CurrentUploadRate:
description: Current upload rate, bytes/sec.
traffic_statistics.TotalUpload:
description: Total bytes uploaded since last reset.
traffic_statistics.TotalDownload:
description: Total bytes downloaded since last reset.
traffic_statistics.TotalConnectTime:
description: Total time connected since last reset.
{% endconfiguration %}

76
source/_components/sensor.pilight.markdown
View File

@ -1,76 +0,0 @@
---
layout: page
title: "Pilight Sensor"
description: "Instructions on how to integrate pilight sensors within Home Assistant."
date: 2016-10-08 23:21
sidebar: true
comments: false
sharing: true
footer: true
logo: pilight.png
ha_category: DIY
ha_release: 0.31
ha_iot_class: depends
---
This `pilight` sensor platform for 433 MHz devices uses a value in the message payload as the sensor value. Unique identifiers (e.g., _uuid_) can be set to distinguish between multiple pilight devices. To use a pilight sensor the pilight Home Assistant hub has to be set up.
## {% linkable_title Configuration %}
To use your sensor via pilight, make sure it is [supported](https://wiki.pilight.org/doku.php/protocols) and add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
sensor:
- platform: pilight
variable: temperature
payload:
uuid: '0000-b8-27-eb-f447d3'
```
{% configuration %}
variable:
description: The variable name in the data stream that defines the sensor value.
required: true
type: string
payload:
description: Message payload identifiers. Only if all identifiers are matched the sensor value is set.
required: true
type: string
name:
description: Name of the sensor.
required: false
default: Pilight Sensor
type: string
unit_of_measurement:
description: Defines the units of measurement of the sensor, if any.
required: false
type: string
{% endconfiguration %}
## {% linkable_title Example: Weather station %}
This section shows a real life example how to use values of a weather station.
```yaml
# Example configuration.yaml entry
sensor:
- platform: pilight
name: 'Temperature'
variable: 'temperature'
payload:
uuid: 0000-b8-27-eb-f1f72e
unit_of_measurement: '°C'
- platform: pilight
name: 'Humidity'
variable: 'humidity'
payload:
uuid: 0000-b8-27-eb-f1f72e
unit_of_measurement: '%'
- platform: pilight
name: 'Battery'
variable: 'battery'
payload:
uuid: 0000-b8-27-eb-f1f72e
unit_of_measurement: '%'
```

38
source/_components/sensor.rainbird.markdown
View File

@ -1,38 +0,0 @@
---
layout: page
title: "Rain Bird Sensor"
description: "Instructions on how to integrate your Rain Bird LNK WiFi Module rain sensor within Home Assistant."
date: 2017-08-25 12:00
sidebar: true
comments: false
sharing: true
footer: true
logo: rainbird.png
ha_category: Irrigation
ha_release: 0.61
ha_iot_class: "Local Polling"
---
This `rainbird` sensor allows interacting with [LNK WiFi](http://www.rainbird.com/landscape/products/controllers/LNK-WiFi.htm) module of the Rain Bird Irrigation system in Home Assistant.
## {% linkable_title Configuration %}
Once you have enabled the [Rain Bird component](/components/rainbird), add the following to your `configuration.yaml` file to enable the rain sensor:
```yaml
# Example configuration.yaml entry
sensor:
- platform: rainbird
monitored_conditions:
- rainsensor
```
{% configuration %}
monitored_conditions:
description: Conditions to be monitored.
keys:
rainsensor:
description: Returns the sensor level.
{% endconfiguration %}
Please note that due to the implementation of the API within the LNK Module, there is a concurrency issue. For example, the Rain Bird app will give connection issues (like already a connection active).

59
source/_components/sensor.rest.markdown
View File

@ -267,3 +267,62 @@ sensor:
entity_id: sensor.owm_report
```
{% endraw %}
This config shows how to extract multiple values from a dictionary with `json_attributes` and `template`. It helps you to avoid flooding the REST service and only ask once the results and separate them in multiple templates referring to it. (No need for a specific state on the REST sensor and it's default state will be the full JSON value which will be longer than the 255 max length. It's why we'll used a static value)
{% raw %}
```json
{
"bedroom1": {
"temperature": 15.79,
"humidity": 55.78,
"battery": 5.26,
"timestamp": "2019-02-27T22:21:37Z"
},
"bedroom2": {
"temperature": 18.99,
"humidity": 49.81,
"battery": 5.08,
"timestamp": "2019-02-27T22:23:44Z"
},
"bedroom3": {
"temperature": 18.58,
"humidity": 47.95,
"battery": 5.15,
"timestamp": "2019-02-27T22:21:22Z"
}
}
```
{% endraw %}
{% raw %}
```yaml
sensor:
- platform: rest
name: room_sensors
resource: http://<address_to_rest_service>
json_attributes:
- bedroom1
- bedroom2
- bedroom3
value_template: 'OK'
- platform: template
sensors:
bedroom1_temperature:
value_template: '{{ states.sensor.room_sensors.attributes["bedroom1"]["temperature"] }}'
device_class: temperature
unit_of_measurement: '°C'
bedroom1_humidity:
value_template: '{{ states.sensor.room_sensors.attributes["bedroom1"]["humidity"] }}'
device_class: humidity
unit_of_measurement: '%'
bedroom1_battery:
value_template: '{{ states.sensor.room_sensors.attributes["bedroom1"]["battery"] }}'
device_class: battery
unit_of_measurement: 'V'
bedroom2_temperature:
value_template: '{{ states.sensor.room_sensors.attributes["bedroom2"]["temperature"] }}'
device_class: temperature
unit_of_measurement: '°C'
```
{% endraw %}

15
source/_components/sensor.yr.markdown
View File

@ -68,6 +68,21 @@ monitored_conditions:
description: Medium cloud level.
highClouds:
description: High cloud level.
latitude:
description: Manually specify latitude.
required: false
type: float
default: Provided by Home Assistant configuration.
longitude:
description: Manually specify longitude.
required: false
type: float
default: Provided by Home Assistant configuration.
altitude:
description: Manually specify altitude.
required: false
type: float
default: Provided by Home Assistant configuration.
{% endconfiguration %}
A full configuration example can be found below:

16
source/_components/sensor.zwave.markdown
View File

@ -1,16 +0,0 @@
---
layout: page
title: "Z-Wave Sensor"
description: "Instructions on how to setup the Z-Wave sensors within Home Assistant."
date: 2015-11-15 13:00
sidebar: true
comments: false
sharing: true
footer: true
logo: z-wave.png
ha_category: Sensor
ha_release: pre 0.7
ha_iot_class: "Local Push"
---
To get your Z-Wave sensors working with Home Assistant, follow the instructions for the general [Z-Wave component](/components/zwave/).

41
source/_components/spc.markdown
View File

@ -7,15 +7,27 @@ sidebar: true
comments: false
sharing: true
footer: true
ha_category: Hub
ha_category:
- Hub
- Alarm
- Binary Sensor
ha_release: 0.47
logo: vanderbilt_spc.png
ha_iot_class: "Local Push"
redirect_from:
- /components/binary_sensor.spc/
- /components/alarm_control_panel.spc/
---
Home Assistant has support to integrate your [Vanderbilt SPC](http://www.spc-intruder-detection.com/ssp-spc/) alarm panel and any connected motion, door and smoke sensors.
Integration with SPC is done through a third-party API gateway called [SPC Web Gateway](http://www.lundix.se/smarta-losningar/) which must be installed and configured somewhere on your network.
There is currently support for the following device types within Home Assistant:
- [Alarm](#alarm)
- [Binary Sensor](#binary-sensor)
Home Assistant needs to know where to find the SPC Web Gateway API endpoints, to configure this add the following section to your `configuration.yaml` file:
```yaml
@ -37,3 +49,30 @@ ws_url:
{% endconfiguration %}
Supported sensors will be automatically discovered and added, however they will be hidden by default.
## {% linkable_title Alarm %}
The `spc` alarm control panel platform allows you to control your [Vanderbilt SPC](https://www.spcsupportinfo.com/) alarms.
The `changed_by` attribute enables one to be able to take different actions depending on who armed/disarmed the alarm in [automation](/getting-started/automation/).
```yaml
automation:
- alias: Alarm status changed
trigger:
- platform: state
entity_id: alarm_control_panel.alarm_1
action:
- service: notify.notify
data_template:
message: >
{% raw %}Alarm changed from {{ trigger.from_state.state }}
to {{ trigger.to_state.state }}
by {{ trigger.to_state.attributes.changed_by }}{% endraw %}
```
## {% linkable_title Binary Sensor %}
The `spc` platform allows you to get data from your [Vanderbilt SPC](http://www.spc-intruder-detection.com/ssp-spc/) binary sensors from within Home Assistant.
Check the [type/class](/components/binary_sensor/) list for a possible visualization of your zone. Currently motion, smoke and door sensors are supported.

33
source/_components/switch.gc100.markdown
View File

@ -1,33 +0,0 @@
---
layout: page
title: gc100 Switch
description: "Instructions on how to set up a gc100 switch within Home Assistant."
date: 2017-10-27 17:26
sidebar: true
comments: false
sharing: true
footer: true
ha_category: Switch
ha_release: 0.57
ha_iot_class: "Local Polling"
---
This allows you to control and monitor the relay state on your GC100.
To enable this switch, you first have to set up [gc100](/components/gc100/), and add the following lines to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
switch:
- platform: gc100
ports:
- '4:1': Siren
- '4:2': Sprinkler
```
{% configuration %}
ports:
description: "A list of module-address to name mappings in the format 'x:y': name, where x is module #, y is address."
required: true
type: list
{% endconfiguration %}

117
source/_components/switch.pilight.markdown
View File

@ -1,117 +0,0 @@
---
layout: page
title: "Pilight Switch"
description: "Instructions on how to have switches using 433 MHz connected to a computer running pilight."
date: 2015-06-10 22:41
sidebar: true
comments: false
sharing: true
footer: true
logo: pilight.png
ha_category: DIY
ha_release: 0.26
ha_iot_class: "Local Polling"
---
The `pilight` switch platform is issuing 433 MHz commands using [pilight](https://www.pilight.org/) to turn a 433 MHz device on or off. The Pilight Home Assistant hub has to be set up.
Additionally, RF commands can be defined that trigger this switch to turn on and off. This allows you to also use the remote shipped with your 433 MHz switch without mixing up the Home Assistant states. You can even define several on/off commands, thus several RF remotes to toggle this switch.
To be really sure that Home Assistant knows the actual state of your device it is recommended to use the RF remote with codes unknown to any of your 433 MHz devices. Thus you use the remote to trigger this switch to send the correct RF code to the device.
## {% linkable_title Configuration %}
To define a Pilight switch, add the following lines to your `configuration.yaml`:
```yaml
# Example configuration.yaml entry
switch:
- platform: pilight
switches:
Bed light:
on_code:
protocol: intertechno_old
'on': 1
off_code:
protocol: intertechno_old
'off': 1
```
{% configuration %}
switches:
description: The list that contains all command switches.
required: true
type: string
keys:
entry:
description: Name of the command switch. Multiple entries are possible.
required: true
type: list
keys:
on_code:
description: The code to turn the device on.
required: true
type: list
off_code:
description: The code to turn the device off.
required: true
type: list
on_code_receive:
description: If given, this command will turn the switch on if it is received by pilight.
required: false
type: list
off_code_receive:
description: If given, this command will turn the switch off if it is received by pilight.
required: false
type: list
{% endconfiguration %}
Variables for the different codes (`on_code` and `off_code`):
- **protocol** (*Required*): Protocol to use, e.g., `intertechno_old` or `daycom`.
- **systemcode** (*Optional*): The systemcode of the device.
- **unit** (*Optional*): The unit to use (is equivalent to `pilight-send --unit`).
- **unitcode** (*Optional*): The unitcode to use (is equivalent to `pilight-send --unitcode`).
- **id** (*Optional*): ID of the device
- **state** (*Optional*): `'on'` or `'off'` has to be in apostrophes to be parsed correctly.
- **'off'** (*Optional*): `1` or `0`
- **'on'** (*Optional*): `1` or `0`
For possible code entries, look at the [pilight API](https://manual.pilight.org/development/api.html). All commands allowed by [pilight-send](https://manual.pilight.org/programs/send.html) can be used. Which means that if, for a certain protocol, there are different parameters used, you should be able to replace the variables above by the proper ones required by the specific protocol. When using the `elro_800_switch` or `mumbi` protocol, for example, you will have to replace the variable `unit` with `unitcode` or there will be errors occurring.
Variables for the different receive codes (`on_code_receive` and `off_code_receive`):
- **echo** (*Optional*) Set to `true` if the on-/off-code should be sent if the given code was received.
This is useful if you have paired your sender directly with the receiver to prevent sending the signal twice.
## {% linkable_title Examples %}
```yaml
switch:
- platform: pilight
switches:
Bed light:
on_code:
protocol: intertechno_old
unit: 3
id: 4
'on': 1
off_code:
protocol: intertechno_old
unit: 3
id: 4
'off': 1
on_code_receive:
protocol: daycom
systemcode: 14462
unit: 6
id: 34
state: 'on'
off_code_receive:
protocol: daycom
systemcode: 14462
unit: 6
id: 34
state: 'off'
```

57
source/_components/switch.rainbird.markdown
View File

@ -1,57 +0,0 @@
---
layout: page
title: "Rain Bird Switch"
description: "Instructions on how to integrate your Rain Bird LNK WiFi Module as Switches within Home Assistant."
date: 2017-08-25 12:00
sidebar: true
comments: false
sharing: true
footer: true
logo: rainbird.png
ha_category: Irrigation
ha_release: 0.57
ha_iot_class: "Local Polling"
---
This `rainbird` switch platform allows interacting with [LNK WiFi](http://www.rainbird.com/landscape/products/controllers/LNK-WiFi.htm) module of the Rain Bird Irrigation system in Home Assistant.
## {% linkable_title Configuration %}
Once you have enabled the [Rain Bird component](/components/rainbird), add the following to your `configuration.yaml` file:
```yaml
switch:
- platform: rainbird
switches:
sprinkler_1:
zone: 1
friendly_name: "Front sprinklers"
trigger_time: 10
scan_interval: 10
sprinkler_2:
friendly_name: "Back sprinklers"
zone: 2
trigger_time: 20
scan_interval: 10
```
{% configuration %}
zone:
description: Station zone identifier.
required: true
type: string
friendly_name:
description: Just a friendly name for the station.
required: false
type: string
trigger_time:
description: The default duration to sprinkle the zone.
required: true
type: integer
scan_interval:
description: How fast to refresh the switch.
required: false
type: integer
{% endconfiguration %}
Please note that due to the implementation of the API within the LNK Module, there is a concurrency issue. For example, the Rain Bird app will give connection issues (like already a connection active).

16
source/_components/switch.zwave.markdown
View File

@ -1,16 +0,0 @@
---
layout: page
title: "Z-Wave Switch"
description: "Instructions on how to setup the Z-Wave switches within Home Assistant."
date: 2015-11-15 13:00
sidebar: true
comments: false
sharing: true
footer: true
logo: z-wave.png
ha_category: Switch
ha_release: pre 0.7
ha_iot_class: "Local Push"
---
To get your Z-Wave switches working with Home Assistant, follow the instructions for the general [Z-Wave component](/components/zwave/).

129
source/_components/zwave.markdown
View File

@ -8,13 +8,42 @@ comments: false
sharing: true
footer: true
logo: z-wave.png
ha_category: Hub
ha_category:
- Hub
- Binary Sensor
- Climate
- Cover
- Fan
- Light
- Lock
- Sensor
- Switch
featured: true
ha_iot_class: "Local Push"
redirect_from:
- /components/binary_sensor.zwave/
- /components/climate.zwave/
- /components/cover.zwave/
- /components/fan.zwave/
- /components/light.zwave/
- /components/lock.zwave/
- /components/sensor.zwave/
- /components/switch.zwave/
---
The [Z-Wave](http://www.z-wave.com/) integration for Home Assistant allows you to observe and control connected Z-Wave devices. Please see the [Z-Wave getting started section](/docs/z-wave/) for in-depth documentation on how to use and setup the Z-Wave component.
There is currently support for the following device types within Home Assistant:
- Binary Sensor
- [Climate](#climate)
- [Cover](#cover)
- Fan
- Light
- [Lock](#lock)
- Sensor
- Switch
## {% linkable_title Configuration %}
If you have setup the requirements, then add the following entry `configuration.yaml` file:
@ -23,3 +52,101 @@ If you have setup the requirements, then add the following entry `configuration.
# Example configuration.yaml entry
zwave:
```
## {% linkable_title Climate %}
To get your Z-Wave thermostat or HVAC unit working with Home Assistant, follow the instructions for the general [Z-Wave component](/getting-started/z-wave/).
<p class='note'>
Thermostats with support for fan modes or different operating modes, will be handled like a HVAC device and will also be detected as one.
If the thermostat supports different operating modes, you will get one thermostat entity for each mode. These can be hidden with settings using the customize setting in the `configuration.yaml` file.
</p>
To enable the climate component for your Z-Wave network, add the following to your `configuration.yaml` file.
```yaml
climate:
- platform: zwave
```
Once enabled, any Z-Wave climate devices will be available to Home Assistant. Multiple entities may be created. The following entities are created for a Remotec ZXT-120.
- `climate.remotec_zxt120_heating_1_id`: Allows you to control the connected device. See below for examples.
- `sensor.remotec_zxt120_temperature_38`: A sensor which returns the current temperature set on the attached device.
### {% linkable_title Automating Z-Wave Climate Devices %}
The following examples will instruct a Remotec ZXT-120 to turn the attached device mode to Heating, and set the temperature at 24 degrees after 8pm. Add it to `automation.yaml`.
```yaml
automation:
- alias: Turn on Heater at 8pm
trigger:
- platform: time
at: "20:00:00"
action:
- service: climate.set_operation_mode
data:
entity_id: climate.remotec_zxt120_heating_1_id
operation_mode: Heat
- service: climate.set_temperature
data:
entity_id: climate.remotec_zxt120_heating_1_39
temperature: 24
```
Generally, in Home Assistant, you can use the `homeassistant/turn_off` service to turn devices off. For the Remotec ZXT-120, you must instead make a service call like the following.
```yaml
automation:
- alias: Turn off Heater at 9pm
trigger:
- platform: time
at: "21:00:00"
action:
- service: climate.set_operation_mode
data:
entity_id: climate.remotec_zxt120_heating_1_id
operation_mode: 'Off'
```
**Note:** In the example above, the word `Off` is encased in single quotes to be valid YAML.
### {% linkable_title Test if it works %}
A simple way to test if your Z-Wave climate device is working is to use <img src='/images/screenshots/developer-tool-services-icon.png' alt='service developer tool icon' class="no-shadow" height="38" /> **Services** from the **Developer Tools**. Choose the applicable Climate service from the list of **Available services:** and enter something like the sample below into the **Service Data** field and then press **CALL SERVICE**.
```json
{
"entity_id": "climate.remotec_zxt120_heating_1_id",
"operation_mode": "Heat"
}
```
## {% linkable_title Cover %}
Z-Wave garage doors, blinds, and roller shutters are supported as cover in Home Assistant.
To get your Z-Wave covers working with Home Assistant, follow the instructions for the general [Z-Wave component](#configuration).
If you discover that you need to [invert the operation](/docs/z-wave/installation/#invert_openclose_buttons) of open/close for a particular device, you may change this behavior in your Z-Wave section of your `configuration.yaml` file as follows:
```yaml
zwave:
device_config:
cover.my_cover:
invert_openclose_buttons: true
```
## {% linkable_title Lock %}
To get your Z-Wave locks working with Home Assistant, follow the instructions for the general [Z-Wave component](#configuration).
Z-Wave locks will expose three services under the lock domain to manage usercodes if the lock supports it:
| Service | Description |
| ------- | ----------- |
| clear_usercode | Clears a usercode at code_slot X. Valid code_slots are 1-254, but max is defined by the lock. |
| get_usercode | Get a usercode from the lock at code_slot. Valid code_slots are 1-254, but max is defined by the lock. |
| set_usercode | Sets usercode to X at code_slot Y. Valid usercodes are at least 4 digits, and max defined by the lock. |

4
source/_docs/automation.markdown
View File

@ -49,9 +49,9 @@ Actions are all about calling services. To explore the available services open t
### {% linkable_title Automation initial state %}
If you always want your automations to be enabled or disabled upon Home Assistant restart, then you have to set an initial state in your automations. Otherwise the previous state will be restored.
When you create a new automation, it will be disabled (and therefore won't trigger) unless you explicitly add `initial_state: true` to it or turn it on manually via UI/another automation/developer tools.
If an automation is disabled (turned off) then it will never trigger. Only automations that are enabled (turned on) will trigger.
In case automations need to be enabled or disabled upon Home Assistant restart, then you have to set the `initial_state` in your automations. Otherwise, the previous state will be restored. Please note that if for some reason Home Assistant cannot restore the previous state, e.g., because of an interrupted or failed startup, it will result in the automation being disabled on the next Home Assistant startup.
```text
automation:

2
source/_docs/ecosystem/haproxy.markdown
View File

@ -18,7 +18,7 @@ This will vary depending on your OS. Check out Google for this.
### {% linkable_title Obtain an SSL certificate %}
There are multiple ways of obtaining an SSL certificate. Let’s Encrypt is one method.
Use Google for this, but a good example of using Certbot can be found [here](https://www.digitalocean.com/community/tutorials/how-to-secure-haproxy-with-let-s-encrypt-on-ubuntu-12-04).
Use Google for this, but a good example of using Certbot can be found [here](https://www.digitalocean.com/community/tutorials/how-to-secure-haproxy-with-let-s-encrypt-on-ubuntu-14-04).
### {% linkable_title HAPRoxy Configuration %}

4
source/_docs/installation.markdown
View File

@ -36,8 +36,8 @@ If you use these install methods, we assume that you know how to manage and admi
**Method**|**You have**|**Recommended for**
:-----|:-----|:-----
[Virtualenv<BR>(as another user)](/docs/installation/raspberry-pi/)|Any Linux, Python 3.5.3 or later|Those familiar with their operating system
[Virtualenv<BR>(as your user)](/docs/installation/virtualenv/)|Any Python 3.5.3 or later|Developers
[venv<BR>(as another user)](/docs/installation/raspberry-pi/)|Any Linux, Python 3.5.3 or later|Those familiar with their operating system
[venv<BR>(as your user)](/docs/installation/virtualenv/)|Any Python 3.5.3 or later|Developers
## {% linkable_title Community provided guides %}

6
source/_docs/installation/docker.markdown
View File

@ -54,11 +54,11 @@ netsh interface portproxy add v4tov4 listenaddress=192.168.1.10 listenport=8123
netsh interface portproxy add v4tov4 listenaddress=0.0.0.0 listenport=8123 connectaddress=10.0.50.2 connectport=8123
```
This will let you access your Home Assistant portal from http://localhost:8123, and if you forward port 8123 on your router to your machine IP, the traffic will be forwarded on through to the docker container.
This will let you access your Home Assistant portal from <http://localhost:8123>, and if you forward port 8123 on your router to your machine IP, the traffic will be forwarded on through to the docker container.
### {% linkable_title Synology NAS %}
As Synology within DSM now supports Docker (with a neat UI), you can simply install Home Assistant using docker without the need for command-line. For details about the package (including compatibility-information, if your NAS is supported), see https://www.synology.com/en-us/dsm/app_packages/Docker
As Synology within DSM now supports Docker (with a neat UI), you can simply install Home Assistant using docker without the need for command-line. For details about the package (including compatibility-information, if your NAS is supported), see <https://www.synology.com/en-us/dsm/app_packages/Docker>
The steps would be:
* Install "Docker" package on your Synology NAS
@ -114,7 +114,7 @@ Remark: to restart your Home Assistant within Synology NAS, you just have to do
* Right-click on it and select "Action"->"Restart".
<p class='note'>
If you want to use a USB Bluetooth adapter or Z-Wave USB Stick with Home Assistant on Synology Docker these instructions do not correctly configure the container to access the USB devices. To configure these devices on your Synology Docker Home Assistant you can follow the instructions provided [here](https://philhawthorne.com/installing-home-assistant-io-on-a-synology-diskstation-nas/) by Phil Hawthorne.
If you want to use a USB Bluetooth adapter or Z-Wave USB Stick with Home Assistant on Synology Docker these instructions do not correctly configure the container to access the USB devices. To configure these devices on your Synology Docker Home Assistant you can follow the instructions provided <a href="https://philhawthorne.com/installing-home-assistant-io-on-a-synology-diskstation-nas/">here</a> by Phil Hawthorne.
</p>
### {% linkable_title QNAP NAS %}

19
source/_docs/mqtt/discovery.markdown
View File

@ -98,6 +98,7 @@ Supported abbreviations:
'cln_tpl': 'cleaning_template',
'cmd_t': 'command_topic',
'curr_temp_t': 'current_temperature_topic',
'dev': 'device',
'dev_cla': 'device_class',
'dock_t': 'docked_topic',
'dock_tpl': 'docked_template',
@ -121,6 +122,7 @@ Supported abbreviations:
'ic': 'icon',
'init': 'initial',
'json_attr': 'json_attributes',
'json_attr_t': 'json_attributes_topic',
'max_temp': 'max_temp',
'min_temp': 'min_temp',
'mode_cmd_t': 'mode_command_topic',
@ -189,6 +191,7 @@ Supported abbreviations:
'unit_of_meas': 'unit_of_measurement',
'val_tpl': 'value_template',
'whit_val_cmd_t': 'white_value_command_topic',
'whit_val_scl': 'white_value_scale',
'whit_val_stat_t': 'white_value_state_topic',
'whit_val_tpl': 'white_value_template',
'xy_cmd_t': 'xy_command_topic',
@ -196,6 +199,16 @@ Supported abbreviations:
'xy_val_tpl': 'xy_value_template',
```
Supported abbreviations for device registry configuration:
```
'cns': 'connections',
'ids': 'identifiers',
'name': 'name',
'mf': 'manufacturer',
'mdl': 'model',
'sw': 'sw_version',
```
### {% linkable_title Support by third-party tools %}
The following software has built-in support for MQTT discovery:
@ -251,9 +264,9 @@ $ mosquitto_pub -h 127.0.0.1 -p 1883 -t "homeassistant/switch/irrigation/set" -m
Setting up a sensor with multiple measurement values requires multiple consecutive configuration topic submissions.
- Configuration topic no1: `homeassistant/sensor/sensorBedroomT/config`
- Configuration payload no1: `{"device_class": "sensor", "name": "Temperature", "state_topic": "homeassistant/sensor/sensorBedroom/state", "unit_of_measurement": "°C", "value_template": "{% raw %}{{ value_json.temperature}}{% endraw %}" }`
- Configuration payload no1: `{"device_class": "temperature", "name": "Temperature", "state_topic": "homeassistant/sensor/sensorBedroom/state", "unit_of_measurement": "°C", "value_template": "{% raw %}{{ value_json.temperature}}{% endraw %}" }`
- Configuration topic no2: `homeassistant/sensor/sensorBedroomH/config`
- Configuration payload no2: `{"device_class": "sensor", "name": "Humidity", "state_topic": "homeassistant/sensor/sensorBedroom/state", "unit_of_measurement": "%", "value_template": "{% raw %}{{ value_json.humidity}}{% endraw %}" }`
- Configuration payload no2: `{"device_class": "humidity", "name": "Humidity", "state_topic": "homeassistant/sensor/sensorBedroom/state", "unit_of_measurement": "%", "value_template": "{% raw %}{{ value_json.humidity}}{% endraw %}" }`
- Common state payload: `{ "temperature": 23.20, "humidity": 43.70 }`
Setting up a switch using topic prefix and abbreviated configuration variable names to reduce payload length.
@ -261,7 +274,7 @@ Setting up a switch using topic prefix and abbreviated configuration variable na
- Configuration topic: `homeassistant/switch/irrigation/config`
- Command topic: `homeassistant/switch/irrigation/set`
- State topic: `homeassistant/switch/irrigation/state`
- Payload: `{"~": "homeassistant/switch/irrigation", "name": "garden", "cmd_t": "~/set", , "stat_t": "~/state"}`
- Payload: `{"~": "homeassistant/switch/irrigation", "name": "garden", "cmd_t": "~/set", "stat_t": "~/state"}`
Setting up a climate component (heat only) with abbreviated configuration variable names to reduce payload length.

108
source/_docs/z-wave/device-specific.markdown
View File

@ -294,6 +294,49 @@ Button six (Triangle) release|6|7740
Press circle and plus simultaneously to wake up the device.
### {% linkable_title Aeotec NanoMote Quad %}
<!-- from https://products.z-wavealliance.org/products/2817 -->
```xml
<CommandClass id="91" name="COMMAND_CLASS_CENTRAL_SCENE" version="1" request_flags="4" innif="true" scenecount="0">
<Instance index="1" />
<Value type="int" genre="system" instance="1" index="0" label="Scene Count" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
<Value type="int" genre="system" instance="1" index="1" label="Button One" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
<Value type="int" genre="system" instance="1" index="2" label="Button Two" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
<Value type="int" genre="system" instance="1" index="3" label="Button Three" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
<Value type="int" genre="system" instance="1" index="4" label="Button Four" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
</CommandClass>
```
Below is a table of the action/scenes for the NanoMote Quad:
**Action**|**scene\_id**|**scene\_data**
:-----:|:-----:|:-----:
Button one single tap|1|7680
Button one hold|1|7800
Button one release|1|7740
Button two single tap|2|7680
Button two hold|2|7800
Button two release|2|7740
Button three single tap|3|7680
Button three hold|3|7800
Button three release|3|7740
Button four single tap|4|7680
Button four hold|4|7800
Button four release|4|7740
Example Event:
```yaml
"event_type": "zwave.scene_activated",
"data": {
"entity_id": "zwave.nanomote",
"scene_id": 2,
"scene_data": 7680
}
```
### {% linkable_title Aeotec Wallmote %}
<!-- from https://hastebin.com/esodiweduq.cs -->
@ -386,6 +429,69 @@ Button four tap|Circle with Line|4|0
Button four hold|Circle with Line|4|2
Button four release|Circle with Line|4|1
### {% linkable_title Remotec ZRC-90 Scene Master %}
To get the ZRC-90 Scene Master working in Home Assistant, you must first edit the `COMMAND_CLASS_CENTRAL_SCENE` in your `zwcfg` file.
1. Go the Z-Wave control panel in Home Assistant and make a note of the node number your ZRC-90 has been assigned.
2. *Stop* Home Assistant.
3. Make a backup of your `zwfcg` file, just in case.
4. In the `zwcfg` file, find the `Node id` that corresponds to the number you noted in the first step.
5. Within the `Node id` you identified, highlight everything between `<CommandClass id="91"` and `</CommandClass>` (inclusive) and paste in the following:
```xml
<CommandClass id="91" name="COMMAND_CLASS_CENTRAL_SCENE" version="1" request_flags="5" innif="true" scenecount="0">
<Instance index="1" />
<Value type="int" genre="system" instance="1" index="0" label="Scene Count" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
<Value type="int" genre="system" instance="1" index="1" label="Scene 1" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="3" />
<Value type="int" genre="system" instance="1" index="2" label="Scene 2" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
<Value type="int" genre="system" instance="1" index="3" label="Scene 3" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
<Value type="int" genre="system" instance="1" index="4" label="Scene 4" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="1" />
<Value type="int" genre="system" instance="1" index="5" label="Scene 5" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
<Value type="int" genre="system" instance="1" index="6" label="Scene 6" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
<Value type="int" genre="system" instance="1" index="7" label="Scene 7" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
<Value type="int" genre="system" instance="1" index="8" label="Scene 8" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
<Value type="int" genre="system" instance="1" index="9" label="Other" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
</CommandClass>
```
6. Save the changes you made the `zwcfg` file and start Home Assistant back up.
Button presses will trigger `zwave.scene_activated` with the following:
- `node_id`: the node of your Scene Master (useful if you have more than one)
- `scene_id`: the number button you press (1-8)
- `scene_data`: the type of press registered (see below)
The Scene Master has eight buttons which can send four actions.
The type of action is reflected in the `scene_data` parameter:
**Action**|**scene\_data**
:-----:|:-----:
Single press | 0
Long press (2s) | 1
Release from hold | 2
Double-press | 3
Let's see how this works in an automation for a Scene Master that's assigned as Node 7:
```yaml
- id: '1234567890'
alias: Double-press Button 2 to toggle all lights
trigger:
- platform: event
event_type: zwave.scene_activated
event_data:
node_id: 7
scene_id: 2
scene_data: 3
condition: []
action:
- data:
service: light.toggle
entity_id: group.all_lights
```
### {% linkable_title RFWDC Cooper 5-button Scene Control Keypad %}
For the RFWDC Cooper 5-button Scene Control Keypad, you may need to update the `COMMAND_CLASS_CENTRAL_SCENE` for each node in your `zwcfg` file with the following:
@ -508,4 +614,4 @@ switch:
value_id: "{{ state_attr('sensor.scene_contrl_indicator','value_id') }}"
value: "{{ states('sensor.scene_contrl_indicator')|int - 16 }}"
```
{% endraw %}
{% endraw %}

2
source/_lovelace/entities.markdown
View File

@ -38,7 +38,7 @@ theme:
## {% linkable_title Options For Entities %}
If you define entities as objects instead of strings, you can add more customization and configuration:
If you define entities as objects instead of strings (by adding `entity:` before entity ID), you can add more customization and configuration:
{% configuration %}
entity:

675
source/_posts/2019-03-13-release-89.markdown Normal file
View File

@ -0,0 +1,675 @@
---
layout: post
title: "0.89: Nissan Leaf, PlayStation 4, Point alarm control, Owlet baby monitor"
description: "Vroom vroom vrooooooooooom."
date: 2019-03-06 00:11:03
date_formatted: "March 6, 2019"
author: Paulus Schoutsen
author_twitter: balloob
comments: true
categories: Release-Notes
og_image: /images/blog/2019-03-release-89/components.png
---
<a href='/components/#version/0.89'><img src='/images/blog/2019-03-release-89/components.png' style='border: 0;box-shadow: none;'></a>
It's time for release 0.89. It's another great new release with some cool new features, bug fixes and improvements. The first cool new feature is that yet another car is integrated into Home Assistant: the Nissan Leaf. Both deConz and SmartThings integrations keep expanding to cover more devices.
This release introduces a new mobile app component. [@robbiet480], who also works on the iOS app, has taken the best parts of the Home Assistant iOS app component and turned it into a standardized API that any mobile app can build upon. This will allow any mobile apps to integrate with Home Assistant with a great user experience. If you are a mobile app developer, please check the updated [app integration docs](https://developers.home-assistant.io/docs/en/app_integration_index.html). We will be fine tuning the API in upcoming releases. Feedback is welcome.
## {% linkable_title Noteworthy Breaking Changes %}
__Custom Components file structure change:__ A significant change in how the "under the hood" of Home Assistant works has led to forcing platforms to be resolved based off the component path, if it exists.
Today, if you want, you can override the Hue light platform, but not the other parts of the Hue integration. If a future update evolves the Hue component, removing or changing internal methods that the custom platform relied upon, the custom platform will start failing ([like this report](https://github.com/home-assistant/home-assistant/issues/17943#issuecomment-462014778)).
To avoid this, we're going to __no longer allow custom components to be partial overlays__ (just a platform). Instead, if you want to override a built-in platform, __you will need to override the whole component__.
This is enforced by first resolving the platform as a component, and if it exists, limiting the lookup path to the component path.
Example: if I look up the hue component, and it is provided by a custom component, then all platform lookups will also be looked up in the custom component dir. The same works the other way around, if a user would only try to override `hue/light.py` but not` hue/__init__.py`, the custom platform will be ignored.
Paulus has written some detailed information about this change on the developers' blog, if you'd like more information. [The Great Migration by Paulus](https://developers.home-assistant.io/blog/2019/02/19/the-great-migration.html)
__Existing SmartThings configuration entries will be removed,__ including the SmartApp/Automation from the SmartThings app. Home Assistant will prompt you to configure the integration again or it can be invoked from the integrations page. The configuration process is the same as before. To prepare, have your _personal access token and a mobile device with the SmartThings Classic App handy._ This will not affect the naming of devices or entities and is a __one-time inconvenience.__ The implementation switches over to the SmartApp access token to synchronize subscriptions during setup of the config entry, which cannot be done using the personal access token.
## {% linkable_title New Platforms %}
- Météo-France platform for the weather component ([@victorcerutti] - [#18404]) ([sensor.meteo_france docs]) ([weather.meteo_france docs]) (new-platform)
- Point alarm control ([@fredrike] - [#20972]) ([point docs]) (new-platform)
- Nissan Leaf Integration (Carwings / NissanConnect EV) ([@filcole] - [#19786]) ([device_tracker docs]) ([nissan_leaf docs]) ([binary_sensor.nissan_leaf docs]) ([sensor.nissan_leaf docs]) ([switch.nissan_leaf docs]) (new-platform)
- Rewrite of Toon component ([@frenck] - [#21186]) ([toon docs]) (breaking change) (new-platform)
- Times of The Day Binary Sensor ([@kstaniek] - [#20068]) ([binary_sensor.tod docs]) (new-platform)
- Add switch platform for Danfoss Air and additional sensors. ([@JonasPed] - [#21046]) ([danfoss_air docs]) (new-platform)
- Owlet baby monitor component ([@oblogic7] - [#21108]) ([owlet docs]) (new-platform)
- deCONZ thermostat support ([@Kane610] - [#20586]) ([deconz docs]) (new-platform)
- Added device tracker support for Ubee Router ([@mzdrale] - [#19586]) ([device_tracker docs]) (new-platform)
- Add LCN cover platform ([@alengwenus] - [#20288]) ([lcn docs]) ([cover.lcn docs]) (new-platform)
- Add initial support for Sony SDCP projector control ([@alistairg] - [#20269]) ([switch.sony_projector docs]) (new-platform)
- Add SmartThings Cover platform and add cover device classes ([@andrewsayre] - [#21192]) ([cover docs]) ([smartthings docs]) (breaking change) (new-platform)
- Add SmartThings Scene platform ([@andrewsayre] - [#21405]) ([smartthings docs]) (new-platform)
- Reddit Sensor ([@ljmerza] - [#21344]) ([sensor.reddit docs]) (new-platform)
- mobile_app component ([@robbiet480] - [#21475]) ([mobile_app docs]) (beta fix) (new-platform)
- Add component media player.ps4 ([@ktnrg45] - [#21074]) ([ps4 docs])
## {% 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 %}
- __HomeMatic component's wireless actors__ are having two RSSI values. The way the component was programmed one of them was being overwritten. With this new change, the __`rssi` attribute of HomeMatic entities has been removed.__ As a replacement the attributes rssi_device and rssi_peer have been added. The attribute of `rssi` will no longer be available, you'll need to __update to `rssi_device`,__ and you can add `rssi_peer` now as well! (fixes #20900) ([@dagobert] - [#20902]) ([homematic docs]) (breaking change)
- You can now specifiy an action when calling the __yeelight_start_flow service__ on your yeelights. The __default action will be 'recover'__ if you do not specify something else. This action will be taken after the flow stops. ([@zewelor] - [#21195]) ([light.yeelight docs]) (breaking change)
- Custom platforms that override a built-in platform that has a component, should now also include the component in the custom_components/ folder. So if you want to override `hue/light.py` with a custom version, __you will also need to provide/copy over `hue/__init__.py`.__ See details in main section about this change. ([@balloob] - [#21070]) (breaking change)
- Automatic discovery of __TP-Link switches, bulbs and dimmers.__ This is a continuation of #15329 and adds support for automatic discovery of TP-Link bulbs, switches, and dimmers based on the new config flow. The integration needs to be enabled either in the __integration configuration or__ alternatively by __adding tplink component__ to the configuration file. As the devices are now configured on the component, this is a __breaking change for light.tplink and switch.tplink.__ ([@rytilahti] - [#18091]) ([tplink docs]) ([light.tplink docs]) ([switch.tplink docs]) (breaking change)
- Enhance __SmartThings component__ subscription. See details in main section about this change. ([@andrewsayre] - [#21124]) ([smartthings docs]) (breaking change) (new-feature)
- The __iperf3 sensor platform__ has been __separated__ into a component and a sensor to remove the service from the sensor platform. Configuration options have changed, __please review the documentation__ and select the correct options. ([@rohankapoorcom] - [#21138]) ([iperf3 docs]) __([sensor.iperf3 docs])__ (breaking change) (new-platform)
- The __`google_travel_time`__ platform no longer has an update service, use __homeassistant.update with the appropriate entity_id(s) instead.__ ([@rohankapoorcom] - [#21153]) ([sensor.google_travel_time docs]) (breaking change)
- Add ADB server functionality to __Fire TV.__ This change __removes the `get_source`__ configuration option. ([@JeffLIrion] - [#21221]) ([media_player.firetv docs]) (breaking change)
- With the addition of the __SmartThings Cover__ platform, the SmartThings __Sensor platform will no longer represent Door, Garage Door and Window Share attributes.__ Additionally, if the cover device reports battery status, the value will be present as a __state attribute__ (battery_level) and not a discrete sensor. ([@andrewsayre] - [#21192]) ([cover docs]) ([smartthings docs]) (breaking change) (new-platform)
- The __Toon component__ was broken some time ago, so now requires a Toon API developer account and __can be configured using the Home Assistant integrations.__ Support for Switches & Smoke detectors has been removed. ([@frenck] - [#21186]) ([toon docs]) (breaking change) (new-platform)
- Addition of config for __trusted networks auth provider.__ It is a breaking changes for users who __manually configured__ trusted network auth provider. An invalid config error will be thrown and HA won't be able to fully started. (It is NOT a breaking changes for user who didn't manual configured trusted network auth provider.) ([@awarecan] - [#21111]) (breaking change)
- For some __HomeMatic devices the `sabotage` attribute is replaced by `error`.__ The value (if not 0) is a device specific error code. ([@dagobert] - [#21009]) ([homematic docs]) (breaking change)
## {% linkable_title Beta Fixes %}
- Add PLATFORM_SCHEMA_BASE to telegram_bot component ([@veleek] - [#21155]) ([telegram_bot docs]) (beta fix)
- Add watchdog to Ambient PWS ([@bachya] - [#21507]) ([ambient_station docs]) (beta fix)
- Improve new Sonos snapshot/restore ([@amelchio] - [#21509]) ([sonos docs]) (beta fix)
- Fix lint ([@balloob] - [#21520]) ([person docs]) ([sensor.airvisual docs]) (beta fix)
- Only use a single store instance ([@balloob] - [#21521]) ([frontend docs]) (beta fix)
- Allow skip-pip applied to HA core ([@awarecan] - [#21527]) (beta fix)
- Updated variable name for readability ([@gorynychzmey] - [#21528]) ([person docs]) (beta fix)
- Add missing retain option to mqtt.climate configuration schema ([@emontnemery] - [#21536]) ([mqtt docs]) (beta fix)
- Fix warning ([@awarecan] - [#21538]) ([http docs]) (beta fix)
- Fix incorrect pyairvisual call ([@bachya] - [#21542]) ([sensor.airvisual docs]) (beta fix)
- mobile_app component ([@robbiet480] - [#21475]) ([mobile_app docs]) (beta fix) (new-platform)
- Make time trigger data trigger.now local ([@emontnemery] - [#21544]) (beta fix)
- Bump zigpy-deconz ([@damarco] - [#21566]) ([zha docs]) (beta fix)
- Re-thrown exception occurred in the blocking service call ([@awarecan] - [#21573]) ([websocket_api docs]) (beta fix)
- Upgrade PyXiaomiGateway library ([@Danielhiversen] - [#21582]) ([xiaomi_aqara docs]) (beta fix)
- Log exception occurred in WS service call command ([@awarecan] - [#21584]) ([websocket_api docs]) (beta fix)
- Word the tplink deprecation warning more strongly ([@amelchio] - [#21586]) ([tplink docs]) (beta fix)
- Handle when installed app has already been removed ([@andrewsayre] - [#21595]) ([smartthings docs]) (beta fix)
- Resolve race condition when HA auth provider is loading ([@awarecan] - [#21619]) (beta fix)
- Upgrade pysonos to 0.0.8 ([@amelchio] - [#21624]) ([sonos docs]) (beta fix)
- Fix calc next ([@balloob] - [#21630]) (beta fix)
- Cast displaytime to int for JSON RPC ([@GGeezes] - [#21649]) ([notify docs]) (beta fix)
- :shirt: Corrects unit of measurement symbol for Watt ([@frenck] - [#21654]) ([toon docs]) (beta fix)
- Rename Google Assistant evenets ([@balloob] - [#21655]) ([google_assistant docs]) (beta fix)
- :ambulance: Fixes Toon doing I/O in coroutines ([@frenck] - [#21657]) ([toon docs]) (beta fix)
- Upgrade toonapilib to 3.1.0 ([@frenck] - [#21661]) ([toon docs]) (beta fix)
- Avoid recorder thread crashing ([@balloob] - [#21668]) (beta fix)
- check we have a tb ([@dgomes] - [#21670]) ([system_log docs]) (beta fix)
- Fix ADS race condition ([@carstenschroeder] - [#21677]) ([ads docs]) (beta fix)
- resync hass that changes have occured ([@fredrike] - [#21705]) ([tellduslive docs]) (beta fix)
- Upgrade toonapilib to 3.2.1 ([@frenck] - [#21706]) ([toon docs]) (beta fix)
## {% linkable_title All changes %}
- Météo-France platform for the weather component ([@victorcerutti] - [#18404]) ([sensor.meteo_france docs]) ([weather.meteo_france docs]) (new-platform)
- Update file header ([@fabaff] - [#21061])
- Climate const.py move ([@elupus] - [#20945])
- Update file header ([@fabaff] - [#21067])
- Rename CONF_ATTRIBUTION to ATTRIBUTION ([@fabaff] - [#21069])
- Bump pyHik library to 0.2.2, improve connections, add sensors ([@mezz64] - [#21086]) ([binary_sensor.hikvision docs])
- Meteo france ([@fabaff] - [#21065]) ([meteo_france docs])
- Fix "Unable to find entity" at Waze component ([@VirtualL] - [#21087]) ([sensor.waze_travel_time docs])
- Point alarm control ([@fredrike] - [#20972]) ([point docs]) (new-platform)
- Times of The Day Binary Sensor ([@kstaniek] - [#20068]) ([binary_sensor.tod docs]) (new-platform)
- Nissan Leaf Integration (Carwings / NissanConnect EV) ([@filcole] - [#19786]) ([device_tracker docs]) ([nissan_leaf docs]) ([binary_sensor.nissan_leaf docs]) ([sensor.nissan_leaf docs]) ([switch.nissan_leaf docs]) (new-platform)
- Add switch platform for Danfoss Air and additional sensors. ([@JonasPed] - [#21046]) ([danfoss_air docs]) (new-platform)
- Config Entry migrations ([@andrewsayre] - [#20888])
- Refactor http CachingStaticResource ([@awarecan] - [#21062]) ([http docs])
- Add index parameter to scrape sensor ([@davidbb] - [#21084]) ([sensor.scrape docs])
- Owlet baby monitor component ([@oblogic7] - [#21108]) ([owlet docs]) (new-platform)
- Order imports ([@fabaff] - [#21117]) ([owlet docs])
- Add Groups to Homematic IP ([@SukramJ] - [#21076]) ([homematicip_cloud docs])
- Remove outdated url pattern match support for static file hosting ([@awarecan] - [#21109]) ([http docs])
- Upgrade pytest to 4.2.1 ([@scop] - [#21112])
- Make Netatmo able to discover both Weather station and Health Coach ([@msvinth] - [#20274])
- Add webhook support for Netatmo Cameras ([@danielperna84] - [#20755]) ([netatmo docs])
- Logging to find what deCONZ events get created ([@Kane610] - [#20551])
- Add traccar scan_interval configuration option ([@lapy] - [#21079]) ([device_tracker docs])
- Add component media player.ps4 ([@ktnrg45] - [#21074]) ([ps4 docs])
- Add traccar monitored_conditions option ([@lapy] - [#21149]) ([device_tracker docs])
- RSSI_PEER and RSSI_DEVICE are different things (fixes #20900) ([@dagobert] - [#20902]) ([homematic docs]) (breaking change)
- Upgrade voluptuous-serialize to 2.1.0 ([@fabaff] - [#21166])
- Upgrade youtube_dl to 2019.02.18 ([@fabaff] - [#21164]) ([media_extractor docs])
- Upgrade sqlalchemy to 1.2.18 ([@fabaff] - [#21162]) ([sensor.sql docs])
- Upgrade psutil to 5.5.1 ([@fabaff] - [#21171]) ([sensor.systemmonitor docs])
- Fix HomematicIP Cloud fix cover position property ([@mxworm] - [#21154]) ([homematicip_cloud docs])
- Clean up upc_connect tests ([@MartinHjelmare] - [#21150])
- deCONZ thermostat support ([@Kane610] - [#20586]) ([deconz docs]) (new-platform)
- Add context to service call event ([@balloob] - [#21181])
- Expose effect_list attribute for turned off lights ([@OleksandrBerchenko] - [#20750])
- Philips Hue: Add bridge update prompt ([@starkillerOG] - [#21119]) ([hue docs])
- Upgrade crimereports to 1.0.1 ([@fabaff] - [#21187]) ([sensor.crimereports docs])
- Netatmo, address comments from #20755 ([@danielperna84] - [#21157]) ([netatmo docs])
- Use constants from const.py ([@fabaff] - [#21068]) ([insteon docs]) ([knx docs]) ([raspihats docs]) ([light.rpi_gpio_pwm docs]) ([sensor.etherscan docs]) ([sensor.ripple docs]) ([sensor.sochain docs])
- Bump Synology SRM dependency to version 0.0.6 ([@aerialls] - [#21212]) ([device_tracker docs])
- Upgrade numpy to 1.16.1 ([@fabaff] - [#21190]) ([binary_sensor.trend docs]) ([image_processing.tensorflow docs]) ([sensor.pollen docs])
- Fix Homematic IP Cloud configuration ([@bauerj] - [#21202]) ([homematicip_cloud docs])
- Add yeelight flow action support ([@zewelor] - [#21195]) ([light.yeelight docs]) (breaking change)
- Fix the build ([@balloob] - [#21229])
- Update pyhomematic to 0.1.56 ([@danielperna84] - [#21227]) ([homematic docs])
- Add self to integration sensor and utility_meter ([@dgomes] - [#21226])
- Add zone and reps for Xiaomi vacuum ([@marcogazzola] - [#19777]) ([vacuum.xiaomi_miio docs])
- Bump zigpy ([@damarco] - [#21203]) ([zha docs])
- Support OpenWRT 18.06 in luci device tracker ([@fbradyirl] - [#21236]) ([device_tracker docs])
- Remove constraint from regex ([@balloob] - [#21239])
- Upgrade opensensemap-api to 0.1.4 ([@fabaff] - [#21240]) ([air_quality docs])
- Alarm trigger support for Point ([@fredrike] - [#21207]) ([point docs])
- Prevent partial custom component overlays ([@balloob] - [#21070]) (breaking change)
- Correctly detect devices, which went offline during HA restart ([@OleksandrBerchenko] - [#20933]) ([device_tracker docs])
- Update rova component with suffix for house number ([@GidoHakvoort] - [#21182]) ([sensor.rova docs])
- Added device tracker support for Ubee Router ([@mzdrale] - [#19586]) ([device_tracker docs]) (new-platform)
- account specific cookies file to enable multiple accounts ([@ToSa27] - [#19811]) ([device_tracker docs])
- Add support for automatic discovery of TP-Link switches, bulbs and dimmers ([@rytilahti] - [#18091]) ([tplink docs]) ([light.tplink docs]) ([switch.tplink docs]) (breaking change)
- Version bump: python-anthemav to v1.1.9 ([@nugget] - [#21273]) ([media_player.anthemav docs])
- Do not warn for internally loaded components ([@balloob] - [#21287])
- Remove index ([@fabaff] - [#21304])
- Adding myself as codeowner for Freebox component ([@SNoof85] - [#21288])
- Nissanleaf ([@filcole] - [#21145]) ([nissan_leaf docs]) (new-platform)
- Config entry options ([@Kane610] - [#18929]) ([deconz docs])
- Enhance SmartThings component subscription ([@andrewsayre] - [#21124]) ([smartthings docs]) (breaking change) (new-feature)
- Add more ads plc types ([@philipperequile] - [#19801]) ([ads docs])
- Add note to issue template regarding iOS issues ([@robbiet480] - [#21342])
- Allow google home component device tracker to be optional ([@dshokouhi] - [#21335]) ([googlehome docs])
- Add LCN cover platform ([@alengwenus] - [#20288]) ([lcn docs]) ([cover.lcn docs]) (new-platform)
- Add location to Norway airquality ([@Danielhiversen] - [#21347]) ([air_quality docs]) ([weather.met docs])
- Updated pyvlx from 0.2.8 to 0.2.9. This version has slightly improved logging ([@Julius2342] - [#21349]) ([velux docs])
- Update buienradar.py ([@hmmbob] - [#21351]) ([sensor.buienradar docs])
- Fixes the sensor.filter outlier filter (handle step-changes correctly) ([@siberx] - [#21332]) ([sensor.filter docs])
- Allows the utility_meter to net meter rather than only allow increases. ([@JBassett] - [#21204]) ([utility_meter docs])
- implementing freedaily mode ([@tmechen] - [#21314]) ([weather.openweathermap docs])
- Add voltage per phase ([@leeuwte] - [#21319]) ([sensor.dsmr docs])
- Add conf_key check for LCN platform load ([@alengwenus] - [#21354]) ([lcn docs])
- Update luci device tracker ([@fbradyirl] - [#21321]) ([device_tracker docs])
- Support the person component in Prometheus ([@mitchellrj] - [#21363]) ([prometheus docs])
- Update Starling Bank Integration to v2 API ([@Dullage] - [#21358]) ([sensor.starlingbank docs])
- Split out iperf3 into a component with a sensor platform ([@rohankapoorcom] - [#21138]) ([iperf3 docs]) ([sensor.iperf3 docs]) (breaking change) (new-platform)
- Add custom and zone cleaning to Neato Vacuums ([@RomRider] - [#20779]) ([neato docs])
- Add initial support for Sony SDCP projector control ([@alistairg] - [#20269]) ([switch.sony_projector docs]) (new-platform)
- Check for attribute existence for HS220 support ([@rytilahti] - [#21309]) ([tplink docs])
- Generate new Discogs sensors + fix scan interval ([@thibmaek] - [#19443]) ([sensor.discogs docs])
- Update panasonic_viera.py ([@Tony763] - [#21365]) ([media_player.panasonic_viera docs])
- Handle connection issue for netatmo ([@Danielhiversen] - [#21346]) ([netatmo docs])
- Refactoring. Moved LCN constants to const.py ([@alengwenus] - [#21376]) ([lcn docs]) (new-platform)
- Clean up owntracks tests ([@MartinHjelmare] - [#21378])
- Remove the google travel time update service ([@rohankapoorcom] - [#21153]) ([sensor.google_travel_time docs]) (breaking change)
- SmartThings Lock platform state attributes enhancement ([@andrewsayre] - [#21379]) ([smartthings docs]) (new-feature)
- Upgrade shodan to 1.11.0 ([@fabaff] - [#21384]) ([sensor.shodan docs])
- Update ordering ([@fabaff] - [#21377]) ([modbus docs])
- Bump nessclient version to 0.9.10 ([@nickw444] - [#21388]) ([ness_alarm docs])
- Handle capitalized HomeKit property names ([@koreth] - [#21382]) ([homekit_controller docs])
- Update WazeTravelSensor to 0.9 ([@hmmbob] - [#21130]) ([sensor.waze_travel_time docs])
- Clean up geofency test ([@MartinHjelmare] - [#21397])
- Clean up locative tests ([@MartinHjelmare] - [#21400])
- Add Sonos discovery of multiple households ([@amelchio] - [#21337]) ([sonos docs])
- Philips js state ([@elupus] - [#21407]) ([media_player.philips_js docs])
- Add ADB server functionality to Fire TV ([@JeffLIrion] - [#21221]) ([media_player.firetv docs]) (breaking change)
- Upgrade pytest to 4.3.0 ([@scop] - [#21412])
- Upgrade mypy to 0.670 ([@scop] - [#20934])
- Update pylinky ([@tiste] - [#21416]) ([sensor.linky docs])
- Mark water_heater as significant domain ([@elupus] - [#21390]) ([history docs])
- Add power and energy attributes to SmartThings switch ([@andrewsayre] - [#21375]) ([smartthings docs]) (new-feature)
- Add SmartThings Cover platform and add cover device classes ([@andrewsayre] - [#21192]) ([cover docs]) ([smartthings docs]) (breaking change) (new-platform)
- Add ESPHome User-Defined Services ([@OttoWinter] - [#21409]) ([esphome docs])
- Handle GA Disconnect intent ([@balloob] - [#21387]) ([google_assistant docs])
- Fix double events on Lutron Pico keypads ([@koreth] - [#21408]) ([lutron docs])
- Fix Sonos snapshot/restore ([@amelchio] - [#21411]) ([sonos docs])
- Increase travis timeout ([@andrewsayre] - [#21447])
- Rewrite of Toon component ([@frenck] - [#21186]) ([toon docs]) (breaking change) (new-platform)
- Check if a script requirement is available before install ([@kellerza] - [#20517])
- Add timeout option to sensor.rest and binary_sensor.rest. ([@glogiotatidis] - [#20065]) ([binary_sensor.rest docs]) ([sensor.rest docs])
- Clean up codeowners file ([@amelchio] - [#21442])
- Upgrade flake8 to 3.7.7 ([@scop] - [#21452])
- Clean up ZHA post rewrite ([@dmulcahey] - [#21448]) ([zha docs])
- Add friendly name to devices in the device registry ([@dmulcahey] - [#21318]) ([config docs])
- Fix ESPHome nodes being auto-added without user confirmation ([@OttoWinter] - [#21444]) ([esphome docs])
- Fix for Snips platform update that breaks hermes api. ([@ptc] - [#21443]) ([snips docs])
- Remove launching a server in a test ([@balloob] - [#21445])
- Add SmartThings Scene platform ([@andrewsayre] - [#21405]) ([smartthings docs]) (new-platform)
- Adjust GTFS dates when crossing midnight ([@renemarc] - [#20916]) ([sensor.gtfs docs])
- Reddit Sensor ([@ljmerza] - [#21344]) ([sensor.reddit docs]) (new-platform)
- Add config for trusted networks auth provider ([@awarecan] - [#21111]) (breaking change)
- Add HomematicIP HmIP-OC8 module ([@mxworm] - [#21401]) ([homematicip_cloud docs])
- Added new econet states ([@w1ll1am23] - [#21420]) ([water_heater docs])
- Comment out bluepy libraries from requirements_all.txt ([@Danielhiversen] - [#20856]) ([switch.switchbot docs]) ([switch.switchmate docs])
- Update sensor.nmbs to support vias better + show on map ([@thibmaek] - [#20063]) ([sensor.nmbs docs])
- Add mitemp bt sensor device class ([@blackray12] - [#20293]) ([sensor.mitemp_bt docs])
- Add Somfy IO Garage door ([@dfournie] - [#21320]) ([tahoma docs])
- Add person support for Waze Travel Time ([@Petro31] - [#21471]) ([sensor.waze_travel_time docs])
- Add cpu_use_percent as a new resource to the Glances sensor. ([@kevintuhumury] - [#21455]) ([sensor.glances docs])
- Added a digit for precipitation ([@helto4real] - [#21439]) ([smhi docs])
- Upgrade bcrypt to 3.1.6 ([@fabaff] - [#21476])
- Upgrade shodan to 1.11.1 ([@fabaff] - [#21478]) ([sensor.shodan docs])
- Upgrade astral to 1.10.1 ([@fabaff] - [#21474])
- Refactor async_turn_on() for ZHA Light. ([@Adminiuga] - [#21156]) ([zha docs])
- Add device_info to enable HA-devices for Homematic IP ([@SukramJ] - [#21241]) ([homematicip_cloud docs])
- Fire events when Google Assistant commands come in #15139 ([@Swamp-Ig] - [#20204]) ([google_assistant docs])
- pylint 2.3.0 ([@Danielhiversen] - [#21485])
- HomeMatic: Add error-attribute ([@dagobert] - [#21009]) ([homematic docs]) (breaking change)
- Avoid unnecessary commands in Vizio update function ([@JeffLIrion] - [#20867])
- Upgrade pyairvisual to 3.0.1 ([@bachya] - [#21512]) ([sensor.airvisual docs])
- Bump simplisafe-python to 3.4.1 ([@bachya] - [#21511]) ([simplisafe docs])
- Upgrade aioambient to 0.1.3 ([@bachya] - [#21510]) ([ambient_station docs])
- Upgrade tibber lib ([@Danielhiversen] - [#21486]) ([tibber docs])
- ness_alarm: Bump nessclient version to 0.9.13 ([@nickw444] - [#21466]) ([ness_alarm docs])
- Bump ihc to 2.3.0 ([@msvinth] - [#21494]) ([ihc docs])
- Changed source priority for Person ([@gorynychzmey] - [#21479])
- Add PLATFORM_SCHEMA_BASE to telegram_bot component ([@veleek] - [#21155]) ([telegram_bot docs]) (beta fix)
- Add watchdog to Ambient PWS ([@bachya] - [#21507]) ([ambient_station docs]) (beta fix)
- Improve new Sonos snapshot/restore ([@amelchio] - [#21509]) ([sonos docs]) (beta fix)
- Fix lint ([@balloob] - [#21520]) ([person docs]) ([sensor.airvisual docs]) (beta fix)
- Only use a single store instance ([@balloob] - [#21521]) ([frontend docs]) (beta fix)
- Allow skip-pip applied to HA core ([@awarecan] - [#21527]) (beta fix)
- Updated variable name for readability ([@gorynychzmey] - [#21528]) ([person docs]) (beta fix)
- Add missing retain option to mqtt.climate configuration schema ([@emontnemery] - [#21536]) ([mqtt docs]) (beta fix)
- Fix warning ([@awarecan] - [#21538]) ([http docs]) (beta fix)
- Fix incorrect pyairvisual call ([@bachya] - [#21542]) ([sensor.airvisual docs]) (beta fix)
- mobile_app component ([@robbiet480] - [#21475]) ([mobile_app docs]) (beta fix) (new-platform)
- Make time trigger data trigger.now local ([@emontnemery] - [#21544]) (beta fix)
- Bump zigpy-deconz ([@damarco] - [#21566]) ([zha docs]) (beta fix)
- Re-thrown exception occurred in the blocking service call ([@awarecan] - [#21573]) ([websocket_api docs]) (beta fix)
- Upgrade PyXiaomiGateway library ([@Danielhiversen] - [#21582]) ([xiaomi_aqara docs]) (beta fix)
- Log exception occurred in WS service call command ([@awarecan] - [#21584]) ([websocket_api docs]) (beta fix)
- Word the tplink deprecation warning more strongly ([@amelchio] - [#21586]) ([tplink docs]) (beta fix)
- Handle when installed app has already been removed ([@andrewsayre] - [#21595]) ([smartthings docs]) (beta fix)
- Resolve race condition when HA auth provider is loading ([@awarecan] - [#21619]) (beta fix)
- Upgrade pysonos to 0.0.8 ([@amelchio] - [#21624]) ([sonos docs]) (beta fix)
- Fix calc next ([@balloob] - [#21630]) (beta fix)
- Cast displaytime to int for JSON RPC ([@GGeezes] - [#21649]) ([notify docs]) (beta fix)
- :shirt: Corrects unit of measurement symbol for Watt ([@frenck] - [#21654]) ([toon docs]) (beta fix)
- Rename Google Assistant evenets ([@balloob] - [#21655]) ([google_assistant docs]) (beta fix)
- :ambulance: Fixes Toon doing I/O in coroutines ([@frenck] - [#21657]) ([toon docs]) (beta fix)
- Upgrade toonapilib to 3.1.0 ([@frenck] - [#21661]) ([toon docs]) (beta fix)
- Avoid recorder thread crashing ([@balloob] - [#21668]) (beta fix)
- check we have a tb ([@dgomes] - [#21670]) ([system_log docs]) (beta fix)
- Fix ADS race condition ([@carstenschroeder] - [#21677]) ([ads docs]) (beta fix)
- resync hass that changes have occured ([@fredrike] - [#21705]) ([tellduslive docs]) (beta fix)
- Upgrade toonapilib to 3.2.1 ([@frenck] - [#21706]) ([toon docs]) (beta fix)
[#18091]: https://github.com/home-assistant/home-assistant/pull/18091
[#18404]: https://github.com/home-assistant/home-assistant/pull/18404
[#18929]: https://github.com/home-assistant/home-assistant/pull/18929
[#19443]: https://github.com/home-assistant/home-assistant/pull/19443
[#19586]: https://github.com/home-assistant/home-assistant/pull/19586
[#19777]: https://github.com/home-assistant/home-assistant/pull/19777
[#19786]: https://github.com/home-assistant/home-assistant/pull/19786
[#19801]: https://github.com/home-assistant/home-assistant/pull/19801
[#19811]: https://github.com/home-assistant/home-assistant/pull/19811
[#20063]: https://github.com/home-assistant/home-assistant/pull/20063
[#20065]: https://github.com/home-assistant/home-assistant/pull/20065
[#20068]: https://github.com/home-assistant/home-assistant/pull/20068
[#20204]: https://github.com/home-assistant/home-assistant/pull/20204
[#20269]: https://github.com/home-assistant/home-assistant/pull/20269
[#20274]: https://github.com/home-assistant/home-assistant/pull/20274
[#20288]: https://github.com/home-assistant/home-assistant/pull/20288
[#20293]: https://github.com/home-assistant/home-assistant/pull/20293
[#20517]: https://github.com/home-assistant/home-assistant/pull/20517
[#20551]: https://github.com/home-assistant/home-assistant/pull/20551
[#20586]: https://github.com/home-assistant/home-assistant/pull/20586
[#20750]: https://github.com/home-assistant/home-assistant/pull/20750
[#20755]: https://github.com/home-assistant/home-assistant/pull/20755
[#20779]: https://github.com/home-assistant/home-assistant/pull/20779
[#20856]: https://github.com/home-assistant/home-assistant/pull/20856
[#20867]: https://github.com/home-assistant/home-assistant/pull/20867
[#20888]: https://github.com/home-assistant/home-assistant/pull/20888
[#20902]: https://github.com/home-assistant/home-assistant/pull/20902
[#20916]: https://github.com/home-assistant/home-assistant/pull/20916
[#20933]: https://github.com/home-assistant/home-assistant/pull/20933
[#20934]: https://github.com/home-assistant/home-assistant/pull/20934
[#20945]: https://github.com/home-assistant/home-assistant/pull/20945
[#20972]: https://github.com/home-assistant/home-assistant/pull/20972
[#21009]: https://github.com/home-assistant/home-assistant/pull/21009
[#21046]: https://github.com/home-assistant/home-assistant/pull/21046
[#21061]: https://github.com/home-assistant/home-assistant/pull/21061
[#21062]: https://github.com/home-assistant/home-assistant/pull/21062
[#21065]: https://github.com/home-assistant/home-assistant/pull/21065
[#21067]: https://github.com/home-assistant/home-assistant/pull/21067
[#21068]: https://github.com/home-assistant/home-assistant/pull/21068
[#21069]: https://github.com/home-assistant/home-assistant/pull/21069
[#21070]: https://github.com/home-assistant/home-assistant/pull/21070
[#21074]: https://github.com/home-assistant/home-assistant/pull/21074
[#21076]: https://github.com/home-assistant/home-assistant/pull/21076
[#21079]: https://github.com/home-assistant/home-assistant/pull/21079
[#21084]: https://github.com/home-assistant/home-assistant/pull/21084
[#21086]: https://github.com/home-assistant/home-assistant/pull/21086
[#21087]: https://github.com/home-assistant/home-assistant/pull/21087
[#21108]: https://github.com/home-assistant/home-assistant/pull/21108
[#21109]: https://github.com/home-assistant/home-assistant/pull/21109
[#21111]: https://github.com/home-assistant/home-assistant/pull/21111
[#21112]: https://github.com/home-assistant/home-assistant/pull/21112
[#21117]: https://github.com/home-assistant/home-assistant/pull/21117
[#21119]: https://github.com/home-assistant/home-assistant/pull/21119
[#21124]: https://github.com/home-assistant/home-assistant/pull/21124
[#21130]: https://github.com/home-assistant/home-assistant/pull/21130
[#21138]: https://github.com/home-assistant/home-assistant/pull/21138
[#21145]: https://github.com/home-assistant/home-assistant/pull/21145
[#21149]: https://github.com/home-assistant/home-assistant/pull/21149
[#21150]: https://github.com/home-assistant/home-assistant/pull/21150
[#21153]: https://github.com/home-assistant/home-assistant/pull/21153
[#21154]: https://github.com/home-assistant/home-assistant/pull/21154
[#21155]: https://github.com/home-assistant/home-assistant/pull/21155
[#21156]: https://github.com/home-assistant/home-assistant/pull/21156
[#21157]: https://github.com/home-assistant/home-assistant/pull/21157
[#21162]: https://github.com/home-assistant/home-assistant/pull/21162
[#21164]: https://github.com/home-assistant/home-assistant/pull/21164
[#21166]: https://github.com/home-assistant/home-assistant/pull/21166
[#21171]: https://github.com/home-assistant/home-assistant/pull/21171
[#21181]: https://github.com/home-assistant/home-assistant/pull/21181
[#21182]: https://github.com/home-assistant/home-assistant/pull/21182
[#21186]: https://github.com/home-assistant/home-assistant/pull/21186
[#21187]: https://github.com/home-assistant/home-assistant/pull/21187
[#21190]: https://github.com/home-assistant/home-assistant/pull/21190
[#21192]: https://github.com/home-assistant/home-assistant/pull/21192
[#21195]: https://github.com/home-assistant/home-assistant/pull/21195
[#21202]: https://github.com/home-assistant/home-assistant/pull/21202
[#21203]: https://github.com/home-assistant/home-assistant/pull/21203
[#21204]: https://github.com/home-assistant/home-assistant/pull/21204
[#21207]: https://github.com/home-assistant/home-assistant/pull/21207
[#21212]: https://github.com/home-assistant/home-assistant/pull/21212
[#21221]: https://github.com/home-assistant/home-assistant/pull/21221
[#21226]: https://github.com/home-assistant/home-assistant/pull/21226
[#21227]: https://github.com/home-assistant/home-assistant/pull/21227
[#21229]: https://github.com/home-assistant/home-assistant/pull/21229
[#21236]: https://github.com/home-assistant/home-assistant/pull/21236
[#21239]: https://github.com/home-assistant/home-assistant/pull/21239
[#21240]: https://github.com/home-assistant/home-assistant/pull/21240
[#21241]: https://github.com/home-assistant/home-assistant/pull/21241
[#21273]: https://github.com/home-assistant/home-assistant/pull/21273
[#21287]: https://github.com/home-assistant/home-assistant/pull/21287
[#21288]: https://github.com/home-assistant/home-assistant/pull/21288
[#21304]: https://github.com/home-assistant/home-assistant/pull/21304
[#21309]: https://github.com/home-assistant/home-assistant/pull/21309
[#21314]: https://github.com/home-assistant/home-assistant/pull/21314
[#21318]: https://github.com/home-assistant/home-assistant/pull/21318
[#21319]: https://github.com/home-assistant/home-assistant/pull/21319
[#21320]: https://github.com/home-assistant/home-assistant/pull/21320
[#21321]: https://github.com/home-assistant/home-assistant/pull/21321
[#21332]: https://github.com/home-assistant/home-assistant/pull/21332
[#21335]: https://github.com/home-assistant/home-assistant/pull/21335
[#21337]: https://github.com/home-assistant/home-assistant/pull/21337
[#21342]: https://github.com/home-assistant/home-assistant/pull/21342
[#21344]: https://github.com/home-assistant/home-assistant/pull/21344
[#21346]: https://github.com/home-assistant/home-assistant/pull/21346
[#21347]: https://github.com/home-assistant/home-assistant/pull/21347
[#21349]: https://github.com/home-assistant/home-assistant/pull/21349
[#21351]: https://github.com/home-assistant/home-assistant/pull/21351
[#21354]: https://github.com/home-assistant/home-assistant/pull/21354
[#21358]: https://github.com/home-assistant/home-assistant/pull/21358
[#21363]: https://github.com/home-assistant/home-assistant/pull/21363
[#21365]: https://github.com/home-assistant/home-assistant/pull/21365
[#21375]: https://github.com/home-assistant/home-assistant/pull/21375
[#21376]: https://github.com/home-assistant/home-assistant/pull/21376
[#21377]: https://github.com/home-assistant/home-assistant/pull/21377
[#21378]: https://github.com/home-assistant/home-assistant/pull/21378
[#21379]: https://github.com/home-assistant/home-assistant/pull/21379
[#21382]: https://github.com/home-assistant/home-assistant/pull/21382
[#21384]: https://github.com/home-assistant/home-assistant/pull/21384
[#21387]: https://github.com/home-assistant/home-assistant/pull/21387
[#21388]: https://github.com/home-assistant/home-assistant/pull/21388
[#21390]: https://github.com/home-assistant/home-assistant/pull/21390
[#21397]: https://github.com/home-assistant/home-assistant/pull/21397
[#21400]: https://github.com/home-assistant/home-assistant/pull/21400
[#21401]: https://github.com/home-assistant/home-assistant/pull/21401
[#21405]: https://github.com/home-assistant/home-assistant/pull/21405
[#21407]: https://github.com/home-assistant/home-assistant/pull/21407
[#21408]: https://github.com/home-assistant/home-assistant/pull/21408
[#21409]: https://github.com/home-assistant/home-assistant/pull/21409
[#21411]: https://github.com/home-assistant/home-assistant/pull/21411
[#21412]: https://github.com/home-assistant/home-assistant/pull/21412
[#21416]: https://github.com/home-assistant/home-assistant/pull/21416
[#21420]: https://github.com/home-assistant/home-assistant/pull/21420
[#21439]: https://github.com/home-assistant/home-assistant/pull/21439
[#21442]: https://github.com/home-assistant/home-assistant/pull/21442
[#21443]: https://github.com/home-assistant/home-assistant/pull/21443
[#21444]: https://github.com/home-assistant/home-assistant/pull/21444
[#21445]: https://github.com/home-assistant/home-assistant/pull/21445
[#21447]: https://github.com/home-assistant/home-assistant/pull/21447
[#21448]: https://github.com/home-assistant/home-assistant/pull/21448
[#21452]: https://github.com/home-assistant/home-assistant/pull/21452
[#21455]: https://github.com/home-assistant/home-assistant/pull/21455
[#21466]: https://github.com/home-assistant/home-assistant/pull/21466
[#21471]: https://github.com/home-assistant/home-assistant/pull/21471
[#21474]: https://github.com/home-assistant/home-assistant/pull/21474
[#21475]: https://github.com/home-assistant/home-assistant/pull/21475
[#21476]: https://github.com/home-assistant/home-assistant/pull/21476
[#21478]: https://github.com/home-assistant/home-assistant/pull/21478
[#21479]: https://github.com/home-assistant/home-assistant/pull/21479
[#21485]: https://github.com/home-assistant/home-assistant/pull/21485
[#21486]: https://github.com/home-assistant/home-assistant/pull/21486
[#21494]: https://github.com/home-assistant/home-assistant/pull/21494
[#21507]: https://github.com/home-assistant/home-assistant/pull/21507
[#21509]: https://github.com/home-assistant/home-assistant/pull/21509
[#21510]: https://github.com/home-assistant/home-assistant/pull/21510
[#21511]: https://github.com/home-assistant/home-assistant/pull/21511
[#21512]: https://github.com/home-assistant/home-assistant/pull/21512
[#21520]: https://github.com/home-assistant/home-assistant/pull/21520
[#21521]: https://github.com/home-assistant/home-assistant/pull/21521
[#21527]: https://github.com/home-assistant/home-assistant/pull/21527
[#21528]: https://github.com/home-assistant/home-assistant/pull/21528
[#21536]: https://github.com/home-assistant/home-assistant/pull/21536
[#21538]: https://github.com/home-assistant/home-assistant/pull/21538
[#21542]: https://github.com/home-assistant/home-assistant/pull/21542
[#21544]: https://github.com/home-assistant/home-assistant/pull/21544
[#21566]: https://github.com/home-assistant/home-assistant/pull/21566
[#21573]: https://github.com/home-assistant/home-assistant/pull/21573
[#21582]: https://github.com/home-assistant/home-assistant/pull/21582
[#21584]: https://github.com/home-assistant/home-assistant/pull/21584
[#21586]: https://github.com/home-assistant/home-assistant/pull/21586
[#21595]: https://github.com/home-assistant/home-assistant/pull/21595
[#21619]: https://github.com/home-assistant/home-assistant/pull/21619
[#21624]: https://github.com/home-assistant/home-assistant/pull/21624
[#21630]: https://github.com/home-assistant/home-assistant/pull/21630
[#21649]: https://github.com/home-assistant/home-assistant/pull/21649
[#21654]: https://github.com/home-assistant/home-assistant/pull/21654
[#21655]: https://github.com/home-assistant/home-assistant/pull/21655
[#21657]: https://github.com/home-assistant/home-assistant/pull/21657
[#21661]: https://github.com/home-assistant/home-assistant/pull/21661
[#21668]: https://github.com/home-assistant/home-assistant/pull/21668
[#21670]: https://github.com/home-assistant/home-assistant/pull/21670
[#21677]: https://github.com/home-assistant/home-assistant/pull/21677
[#21705]: https://github.com/home-assistant/home-assistant/pull/21705
[#21706]: https://github.com/home-assistant/home-assistant/pull/21706
[@Adminiuga]: https://github.com/Adminiuga
[@Danielhiversen]: https://github.com/Danielhiversen
[@Dullage]: https://github.com/Dullage
[@GGeezes]: https://github.com/GGeezes
[@GidoHakvoort]: https://github.com/GidoHakvoort
[@JBassett]: https://github.com/JBassett
[@JeffLIrion]: https://github.com/JeffLIrion
[@JonasPed]: https://github.com/JonasPed
[@Julius2342]: https://github.com/Julius2342
[@Kane610]: https://github.com/Kane610
[@MartinHjelmare]: https://github.com/MartinHjelmare
[@OleksandrBerchenko]: https://github.com/OleksandrBerchenko
[@OttoWinter]: https://github.com/OttoWinter
[@Petro31]: https://github.com/Petro31
[@RomRider]: https://github.com/RomRider
[@SNoof85]: https://github.com/SNoof85
[@SukramJ]: https://github.com/SukramJ
[@Swamp-Ig]: https://github.com/Swamp-Ig
[@ToSa27]: https://github.com/ToSa27
[@Tony763]: https://github.com/Tony763
[@VirtualL]: https://github.com/VirtualL
[@aerialls]: https://github.com/aerialls
[@alengwenus]: https://github.com/alengwenus
[@alistairg]: https://github.com/alistairg
[@amelchio]: https://github.com/amelchio
[@andrewsayre]: https://github.com/andrewsayre
[@awarecan]: https://github.com/awarecan
[@bachya]: https://github.com/bachya
[@balloob]: https://github.com/balloob
[@bauerj]: https://github.com/bauerj
[@blackray12]: https://github.com/blackray12
[@carstenschroeder]: https://github.com/carstenschroeder
[@dagobert]: https://github.com/dagobert
[@damarco]: https://github.com/damarco
[@danielperna84]: https://github.com/danielperna84
[@davidbb]: https://github.com/davidbb
[@dfournie]: https://github.com/dfournie
[@dgomes]: https://github.com/dgomes
[@dmulcahey]: https://github.com/dmulcahey
[@dshokouhi]: https://github.com/dshokouhi
[@elupus]: https://github.com/elupus
[@emontnemery]: https://github.com/emontnemery
[@fabaff]: https://github.com/fabaff
[@fbradyirl]: https://github.com/fbradyirl
[@filcole]: https://github.com/filcole
[@fredrike]: https://github.com/fredrike
[@frenck]: https://github.com/frenck
[@glogiotatidis]: https://github.com/glogiotatidis
[@gorynychzmey]: https://github.com/gorynychzmey
[@helto4real]: https://github.com/helto4real
[@hmmbob]: https://github.com/hmmbob
[@kellerza]: https://github.com/kellerza
[@kevintuhumury]: https://github.com/kevintuhumury
[@koreth]: https://github.com/koreth
[@kstaniek]: https://github.com/kstaniek
[@ktnrg45]: https://github.com/ktnrg45
[@lapy]: https://github.com/lapy
[@leeuwte]: https://github.com/leeuwte
[@ljmerza]: https://github.com/ljmerza
[@marcogazzola]: https://github.com/marcogazzola
[@mezz64]: https://github.com/mezz64
[@mitchellrj]: https://github.com/mitchellrj
[@msvinth]: https://github.com/msvinth
[@mxworm]: https://github.com/mxworm
[@mzdrale]: https://github.com/mzdrale
[@nickw444]: https://github.com/nickw444
[@nugget]: https://github.com/nugget
[@oblogic7]: https://github.com/oblogic7
[@philipperequile]: https://github.com/philipperequile
[@ptc]: https://github.com/ptc
[@renemarc]: https://github.com/renemarc
[@robbiet480]: https://github.com/robbiet480
[@rohankapoorcom]: https://github.com/rohankapoorcom
[@rytilahti]: https://github.com/rytilahti
[@scop]: https://github.com/scop
[@siberx]: https://github.com/siberx
[@starkillerOG]: https://github.com/starkillerOG
[@thibmaek]: https://github.com/thibmaek
[@tiste]: https://github.com/tiste
[@tmechen]: https://github.com/tmechen
[@veleek]: https://github.com/veleek
[@victorcerutti]: https://github.com/victorcerutti
[@w1ll1am23]: https://github.com/w1ll1am23
[@zewelor]: https://github.com/zewelor
[ads docs]: /components/ads/
[air_quality docs]: /components/air_quality/
[ambient_station docs]: /components/ambient_station/
[binary_sensor.hikvision docs]: /components/binary_sensor.hikvision/
[binary_sensor.nissan_leaf docs]: /components/binary_sensor.nissan_leaf/
[binary_sensor.rest docs]: /components/binary_sensor.rest/
[binary_sensor.tod docs]: /components/binary_sensor.tod/
[binary_sensor.trend docs]: /components/binary_sensor.trend/
[config docs]: /components/config/
[cover docs]: /components/cover/
[cover.lcn docs]: /components/cover.lcn/
[danfoss_air docs]: /components/danfoss_air/
[deconz docs]: /components/deconz/
[device_tracker docs]: /components/device_tracker/
[esphome docs]: /components/esphome/
[frontend docs]: /components/frontend/
[google_assistant docs]: /components/google_assistant/
[googlehome docs]: /components/googlehome/
[history docs]: /components/history/
[homekit_controller docs]: /components/homekit_controller/
[homematic docs]: /components/homematic/
[homematicip_cloud docs]: /components/homematicip_cloud/
[http docs]: /components/http/
[hue docs]: /components/hue/
[ihc docs]: /components/ihc/
[image_processing.tensorflow docs]: /components/image_processing.tensorflow/
[insteon docs]: /components/insteon/
[iperf3 docs]: /components/iperf3/
[knx docs]: /components/knx/
[lcn docs]: /components/lcn/
[light.rpi_gpio_pwm docs]: /components/light.rpi_gpio_pwm/
[light.tplink docs]: /components/light.tplink/
[light.yeelight docs]: /components/light.yeelight/
[lutron docs]: /components/lutron/
[media_extractor docs]: /components/media_extractor/
[media_player.anthemav docs]: /components/media_player.anthemav/
[media_player.firetv docs]: /components/media_player.firetv/
[media_player.panasonic_viera docs]: /components/media_player.panasonic_viera/
[media_player.philips_js docs]: /components/media_player.philips_js/
[meteo_france docs]: /components/meteo_france/
[mobile_app docs]: /components/mobile_app/
[modbus docs]: /components/modbus/
[mqtt docs]: /components/mqtt/
[neato docs]: /components/neato/
[ness_alarm docs]: /components/ness_alarm/
[netatmo docs]: /components/netatmo/
[nissan_leaf docs]: /components/nissan_leaf/
[notify docs]: /components/notify/
[owlet docs]: /components/owlet/
[person docs]: /components/person/
[point docs]: /components/point/
[prometheus docs]: /components/prometheus/
[ps4 docs]: /components/ps4/
[raspihats docs]: /components/raspihats/
[sensor.airvisual docs]: /components/sensor.airvisual/
[sensor.buienradar docs]: /components/sensor.buienradar/
[sensor.crimereports docs]: /components/sensor.crimereports/
[sensor.discogs docs]: /components/sensor.discogs/
[sensor.dsmr docs]: /components/sensor.dsmr/
[sensor.etherscan docs]: /components/sensor.etherscan/
[sensor.filter docs]: /components/sensor.filter/
[sensor.glances docs]: /components/sensor.glances/
[sensor.google_travel_time docs]: /components/sensor.google_travel_time/
[sensor.gtfs docs]: /components/sensor.gtfs/
[sensor.iperf3 docs]: /components/sensor.iperf3/
[sensor.linky docs]: /components/sensor.linky/
[sensor.meteo_france docs]: /components/sensor.meteo_france/
[sensor.mitemp_bt docs]: /components/sensor.mitemp_bt/
[sensor.nissan_leaf docs]: /components/sensor.nissan_leaf/
[sensor.nmbs docs]: /components/sensor.nmbs/
[sensor.pollen docs]: /components/sensor.pollen/
[sensor.reddit docs]: /components/sensor.reddit/
[sensor.rest docs]: /components/sensor.rest/
[sensor.ripple docs]: /components/sensor.ripple/
[sensor.rova docs]: /components/sensor.rova/
[sensor.scrape docs]: /components/sensor.scrape/
[sensor.shodan docs]: /components/sensor.shodan/
[sensor.sochain docs]: /components/sensor.sochain/
[sensor.sql docs]: /components/sensor.sql/
[sensor.starlingbank docs]: /components/sensor.starlingbank/
[sensor.systemmonitor docs]: /components/sensor.systemmonitor/
[sensor.waze_travel_time docs]: /components/sensor.waze_travel_time/
[simplisafe docs]: /components/simplisafe/
[smartthings docs]: /components/smartthings/
[smhi docs]: /components/smhi/
[snips docs]: /components/snips/
[sonos docs]: /components/sonos/
[switch.nissan_leaf docs]: /components/switch.nissan_leaf/
[switch.sony_projector docs]: /components/switch.sony_projector/
[switch.switchbot docs]: /components/switch.switchbot/
[switch.switchmate docs]: /components/switch.switchmate/
[switch.tplink docs]: /components/switch.tplink/
[system_log docs]: /components/system_log/
[tahoma docs]: /components/tahoma/
[telegram_bot docs]: /components/telegram_bot/
[tellduslive docs]: /components/tellduslive/
[tibber docs]: /components/tibber/
[toon docs]: /components/toon/
[tplink docs]: /components/tplink/
[utility_meter docs]: /components/utility_meter/
[vacuum.xiaomi_miio docs]: /components/vacuum.xiaomi_miio/
[velux docs]: /components/velux/
[water_heater docs]: /components/water_heater/
[weather.met docs]: /components/weather.met/
[weather.meteo_france docs]: /components/weather.meteo_france/
[weather.openweathermap docs]: /components/weather.openweathermap/
[websocket_api docs]: /components/websocket_api/
[xiaomi_aqara docs]: /components/xiaomi_aqara/
[zha docs]: /components/zha/

6
source/getting-started/configuration.markdown
View File

@ -98,11 +98,15 @@ Now that you are able to edit the configuration, it's time to set up some of you
<p class='note'>YAML can be a little daunting at first. A lot is possible! [Here is some more info.](/docs/configuration/devices/)</p>
For a sensor that is showing [random values](/components/sensor.random/), the entry would look like the sample below:
For your first integration, you'll create a virtual sensor that generates a random integer value between 0 and 20 every 30 seconds.
To create this random value sensor [random values](/components/sensor.random/), enter the following to the bottom of your `configuration.yaml` file, and restart Home Assistant (remember it may take up to a minute for the service to restart):
```yaml
sensor:
- platform: random
```
You'll know it worked when you see the new random sensor in your overview page. On the next page, we'll create an automation that uses this sensor to take an action.
### [Next step: Automate Home Assistant &raquo;](/getting-started/automation/)

7
source/getting-started/index.markdown
View File

@ -39,7 +39,12 @@ We will need a few things to get started with installing Home Assistant. For bes
1. Put the SD card in your SD card reader.
1. Open balenaEtcher, select the Hass.io image and flash it to the SD card.
1. WiFi and Static IP setup only: Format a USB-Stick with name `CONFIG`, create a folder named `network` and within that folder a file named `my-network`. Copy one of [the examples] to the `my-network` file.
1. WiFi and Static IP setup only:
- Format a USB-Stick to FAT32 with volume-name `CONFIG`.
- Create a folder named `network` in the root of the newly formatted USB-stick.
- Within that folder create a file named `my-network` without extension.
- Copy one of [the examples] to the `my-network` file.
- Plug the USB-stick into the RaspberryPi 3.
1. Unmount the SD card and remove it from your SD card reader.
1. Insert the SD card into your Raspberry Pi 3. If you are going to use an Ethernet cable, connect that too.
1. Connect your Raspberry Pi to the power supply, so it turns on.

6
source/hassio/installation.markdown
View File

@ -15,9 +15,9 @@ The following will take you through the steps required to install Hass.io.
- As an image for your device:
- [Raspberry Pi Zero][pi1]
- [Raspberry Pi Zero W][pi0-w]
- [Raspberry Pi 1 Model B][pi1]
- [Raspberry Pi Zero][pi1] (not recommended for more than testing)
- [Raspberry Pi Zero W][pi0-w] (not recommended for more than testing)
- [Raspberry Pi 1 Model B][pi1] (not recommended for more than testing)
- [Raspberry Pi 2 Model B][pi2]
- [Raspberry Pi 3 Model B and B+ 32bit][pi3-32] (recommended)
- [Raspberry Pi 3 Model B and B+ 64bit][pi3-64]

BIN
source/images/blog/2019-03-release-89/components.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 52 KiB

0
source/images/reddit.png → source/images/supported_brands/reddit.png
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 11 KiB

After

Width:  |  Height:  |  Size: 11 KiB

4
source/lovelace/changelog.markdown
View File

@ -17,6 +17,8 @@ footer: true
## {% linkable_title Changes in 0.87.0 %}
- 📣 MDI icons updated to [3.3.92](https://cdn.materialdesignicons.com/3.3.92/)
- 📣 Theming: New CSS card style `ha-card-border-radius`
- 📣 Theming: New CSS card style `ha-card-background`
- 📣 New system-health card in dev-info
- 📣 UI Editor: YAML syntax support
- 📣 UI Editor: Line numbers
@ -25,7 +27,7 @@ footer: true
- 📣 [thermostat card]: more-info button added
- 📣 [light card]: more-info button added
- 🔧 [thermostat card]: Fix slider
- 🔧 groups togglable
- 🔧 groups are now togglable
## {% linkable_title Changes in 0.86.0 %}
- 📣 Lovelace is now the default UI for Home Assistant!