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-19 15:26:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'rc' into current

Browse Source
This commit is contained in:
Paulus Schoutsen 2018-08-29 12:13:23 +02:00
commit 7b3961d127
53 changed files with 1647 additions and 539 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
_config.yml
View File

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

2
source/_components/binary_sensor.deconz.markdown
View File

@ -22,7 +22,7 @@ The following sensor types are supported:
* Presence detection
* Water leakage detection
Entity ids will be binary_sensor.device_name, where device_name is defined in deCONZ.
The `entity_id` name will be `binary_sensor.device_name`, where `device_name` is defined in deCONZ.
#### {% linkable_title Verified to be supported binary sensors %}

21
source/_components/binary_sensor.insteon.markdown Normal file
View File

@ -0,0 +1,21 @@
---
layout: page
title: "Insteon Binary Sensor"
description: "Instructions on how to setup the Insteon binary sensors locally within Home Assistant."
date: 2018-08-20 16:00
sidebar: true
comments: false
sharing: true
footer: true
logo: insteon.png
ha_category: Binary Sensor
ha_iot_class: "Local Push"
ha_version: 0.77
---
The `insteon` binary sensor platform lets you control your sensors through
an INSTEON Modem (PLM and Hub) device connected directly to your system on a
USB, serial port or TCPIP connection. To add support, set up the primary
[insteon] component.
[insteon]: /components/insteon/

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

@ -1,21 +0,0 @@
---
layout: page
title: "Insteon PLM Binary Sensor"
description: "Instructions on how to setup the Insteon PLM binary sensors locally within Home Assistant."
date: 2017-02-19 17:00
sidebar: true
comments: false
sharing: true
footer: true
logo: insteon.png
ha_category: Binary Sensor
ha_iot_class: "Local Push"
ha_release: 0.39
---
The `insteon_plm` binary sensor platform lets you control your sensors through
an INSTEON PowerLinc Modem (PLM) device connected directly to your system on a
USB or serial port. To add support, set up the primary [insteon_plm]
component.
[insteon_plm]: /components/insteon_plm/

20
source/_components/binary_sensor.wemo.markdown Normal file
View File

@ -0,0 +1,20 @@
---
layout: page
title: "Belkin WeMo Binary Sensors"
description: "Instructions on how to integrate Belkin WeMo binary sensors into Home Assistant."
date: 2016-02-20 00:45
sidebar: true
comments: false
sharing: true
footer: true
logo: belkin_wemo.png
ha_category: Binary Sensor
ha_iot_class: "Local Push"
ha_release: 0.14
---
The `wemo` platform allows you to integrate your Belkin WeMo Binary Sensor from within Home Assistant.
They will be automatically discovered if the discovery component is enabled.
For more configuration information see the [WeMo component](/components/wemo/) documentation.

5
source/_components/bmw_connected_drive.markdown
View File

@ -50,6 +50,11 @@ bmw_connected_drive:
description: "The region of your Connected Drive account. Please use of these values: `north_america`, `china`, `rest_of_world`"
required: true
type: string
read_only:
description: In read only mode, all services including the lock of the vehicle are disabled.
required: false
type: boolean
default: false
{% endconfiguration %}
## {% linkable_title Services %}

18
source/_components/climate.ephember.markdown
View File

@ -1,7 +1,7 @@
---
layout: page
title: "EPH Controls Ember Thermostat"
description: "Instructions on how to integrate EPH Controls Ember thermostats within Home Assistant."
title: "EPH Controls EMBER Thermostat"
description: "Instructions on how to integrate EPH Controls EMBER thermostats within Home Assistant."
date: 2017-10-07 12:40
sidebar: true
comments: false
@ -14,7 +14,7 @@ ha_iot_class: "Local Polling"
---
The `ephember` climate platform lets you control [EPH Controls](http://emberapp.ephcontrols.com/) thermostats. The module only works if you have a WiFi gateway to control your EPH system and an account on the ember app.
The `ephember` climate platform lets you control [EPH Controls](http://emberapp.ephcontrols.com/) thermostats. The module only works if you have a WiFi gateway to control your EPH system and an account on the EMBER app.
To set it up, add the following information to your `configuration.yaml` file:
@ -29,5 +29,13 @@ A single interface can handle up to 32 connected devices.
Configuration variables:
- **username** (*Required*): The email address you used to sign up to the ember app
- **password** (*Required*): The password you used to sign up to the ember app
- **username** (*Required*): The email address you used to sign up to the EMBER app
- **password** (*Required*): The password you used to sign up to the EMBER app
The supported operation modes map to the ON/OFF period selection of your timeswitch / EMBER app. These include:
- **Auto** The timeswitch operates 3 on / off periods per day.
- **On** The timeswitch is permanently on.
- **Off** The timeswitch is permanently off.
If **All Day** is selected in the EMBER app it will show as **Auto** in Home Assistant.

61
source/_components/device_tracker.unifi.markdown
View File

@ -67,6 +67,11 @@ ssid_filter:
type: list of strings
required: false
default: None
monitored_conditions:
description: A list of extra attributes to pull from the Unifi controller.
type: list
required: false
default: None
{% endconfiguration %}
@ -78,7 +83,7 @@ The Unifi controller allows you to create multiple users on it besides the main
### {% linkable_title Conflicts with MQTT %}
The Unifi controller can either be a dedicated hardware device (Unifi's cloud key), or as software any Linux system. If you run the the Unifi controller on the same operating system as Home Assistant there may be conflicts in ports if you have the MQTT component as well.
The Unifi controller can either be a dedicated hardware device (Unifi's cloud key), or as software any Linux system. If you run the Unifi controller on the same operating system as Home Assistant there may be conflicts in ports if you have the MQTT component as well.
It is recommended that you run the Unifi controller in a dedicated virtual machine to avoid that situation.
@ -86,6 +91,58 @@ It is recommended that you run the Unifi controller in a dedicated virtual machi
Presence detection depends on accurate time configuration between Home Assistant and the Unifi controller.
If Home Assistant and the Unifi controller are running on separate machines or VMs ensure that all clocks are syncronized. Failing to have syncronized clocks will lead to Home Assistant failing to mark a device as home.
If Home Assistant and the Unifi controller are running on separate machines or VMs ensure that all clocks are synchronized. Failing to have synchronized clocks will lead to Home Assistant failing to mark a device as home.
[Related Issue](https://github.com/home-assistant/home-assistant/issues/10507)
### {% linkable_title Monitored Conditions %}
The Unifi controller returns a number of additional attributes that can be used for tracking devices, including signal strength, rx/tx rates, and which AP it is connected to. The list of possible options may vary depending on your Unifi controller version and if a device is wired or wireless.
Unifi Controller version 5.6.29 has the following options:
- _id
- _is_guest_by_uap
- _last_seen_by_uap
- _uptime_by_uap
- ap_mac
- assoc_time
- authorized
- bssid
- bytes-r
- ccq
- channel
- essid
- first_seen
- hostname
- idletime
- ip
- is_11r
- is_guest
- is_wired
- last_seen
- latest_assoc_time
- mac
- name
- noise
- noted
- oui
- powersave_enabled
- qos_policy_applied
- radio
- radio_proto
- rssi
- rx_bytes
- rx_bytes-r
- rx_packets
- rx_rate
- signal
- site_id
- tx_bytes
- tx_bytes-r
- tx_packets
- tx_power
- tx_rate
- uptime
- user_id
- usergroup_id
- vlan

69
source/_components/ecovacs.markdown Normal file
View File

@ -0,0 +1,69 @@
---
layout: page
title: "Ecovacs"
description: "Instructions on how to integrate Ecovacs vacuums within Home Assistant."
date: 2018-07-29 09:00
sidebar: true
comments: false
sharing: true
footer: true
logo: ecovacs.png
ha_category: Hub
ha_iot_class: "Cloud Push"
ha_release: 0.77
---
The `ecovacs` component is the main component to integrate all [Ecovacs](https://www.ecovacs.com) (Deebot) vacuums. You will need your Ecovacs account information (username, password) to discover and control vacuums in your account.
Please see the [Ecovacs Vacuum](/components/vacuum.ecovacs/) documentation for more information about using the vacuum entity.
## {% linkable_title Configuration %}
To add your Ecovacs devices into your Home Assistant installation, add the following to your `configuration.yaml` file:
```yaml
ecovacs:
username: YOUR_ECOVACS_USERNAME
password: YOUR_ECOVACS_PASSWORD
country: YOUR_TWO_LETTER_COUNTRY_CODE
continent: YOUR_TWO_LETTER_CONTINENT_CODE
```
{% configuration %}
username:
description: Your username to login to your Ecovacs account.
required: true
type: string
password:
description: Your password to login to your Ecovacs account.
required: true
type: string
country:
description: Your two-letter country code (us, uk, etc).
required: true
type: string
continent:
description: Your two-letter continent code (na, eu, etc).
required: true
type: string
{% endconfiguration %}
Note: For some countries, you will need to set `continent` to `ww` (meaning worldwide.) There is unfortunately no way to know the correct settings other than guessing and checking. See the [sucks library protocol documentation](https://github.com/wpietri/sucks/blob/master/protocol.md) for more information about what has been figured out about the Ecovacs servers.
### {% linkable_title Stability and Reporting Bugs %}
The library that talks to the Ecovacs servers is in a very early state and still under development. As such, it is likely that not all regions and devices will work at the current time.
Please see the [sucks library documentation](https://github.com/wpietri/sucks) for some more information about what has been tested, and check out the GitHub issues to see if the issue you're having is known or being worked on.
If you have an issue with the Ecovacs component, please file a [GitHub Issue](https://github.com/home-assistant/home-assistant/issues) and include your Home Assistant logs in the report. To get full debug output from both the Ecovacs component and the underlying `sucks` library, place this in your `configuration.yaml` file:
```yaml
logger:
logs:
homeassistant.components.ecovacs: debug
homeassistant.components.vacuum.ecovacs: debug
sucks: debug
```
Warning: doing this will cause your authentication token to visible in your log files. Be sure to remove any tokens and other authentication details from your log before posting them in an issue.

24
source/_components/fan.insteon.markdown Normal file
View File

@ -0,0 +1,24 @@
---
layout: page
title: "Insteon Fan"
description: "Instructions on how to setup the Insteon fan locally within Home Assistant."
date: 2018-08-20 16:00
sidebar: true
comments: false
sharing: true
footer: true
logo: insteon.png
ha_category: Fan
ha_iot_class: "Local Push"
ha_version: 0.77
---
The `insteon` fan platform lets you control your [FanLinc] through
an INSTEON Modem (PLM and Hub) device connected directly to your system on a
USB, serial port or TCPIP connection. To add support, set up the primary
[insteon] component.
[insteon]: /components/insteon/
[FanLinc]: https://www.smarthome.com/fanlinc-insteon-2475f-ceiling-fan-and-light-controller-fixture-module-dual-band.html

18
source/_components/fan.insteon_local.markdown
View File

@ -1,18 +0,0 @@
---
layout: page
title: "Insteon (local) Fan"
description: "Instructions on how to setup the Insteon Hub Fans locally within Home Assistant."
date: 2017-04-06 11:00
sidebar: true
comments: false
sharing: true
footer: true
logo: insteon.png
ha_category: Fan
ha_release: 0.48
redirect_from: /components/fan.insteon_hub/
---
The `insteon_local` fan component lets you control your fans connected to an [Insteon Hub](http://www.insteon.com/insteon-hub/) with Home Assistant.
To get your Insteon fans working with Home Assistant, follow the instructions for the general [Insteon local component](/components/insteon_local/). The fans will be automatically discovered and added to Home Assistant. The device names will be the Insteon address of the fans.

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

@ -1,16 +0,0 @@
---
layout: page
title: "Insteon PLM Fan"
description: "Instructions on how to setup the Insteon PLM Fans locally within Home Assistant."
date: 2017-02-19 17:00
sidebar: true
comments: false
sharing: true
footer: true
logo: insteon.png
ha_category: Fan
ha_iot_class: "Local Push"
ha_release: 0.65
---
The `insteon_plm` fan platform lets you control your [FanLinc](https://www.smarthome.com/fanlinc-insteon-2475f-ceiling-fan-and-light-controller-fixture-module-dual-band.html) through an INSTEON PowerLinc Modem (PLM) device connected directly to your system on a USB or serial port. To add support, set up the primary [insteon_plm](/components/insteon_plm/) component.

169
source/_components/hangouts.markdown Normal file
View File

@ -0,0 +1,169 @@
---
layout: page
title: "Google Hangouts"
description: "Hangouts chatbot support"
date: 2018-08-18 20:00
sidebar: true
comments: false
sharing: true
footer: true
logo: hangouts.png
ha_category: Hub
ha_release: 0.77
---
This component allows you to send messages to [Google Hangouts](http://hangouts.google.com) conversations, as well as to react to messages in conversations. Reacting to commands is accomplished by firing an event when one of the configured commands is triggered.
## {% linkable_title Setup the component via the frontend %}
Menu: *Configuration* -> *Integrations*
Fill the form:
* Your **Google Mail Address** and **Password**
* If needed, you will be asked for a 2-factor authorization token
**BEST PRACTICE:** You can't write messages to yourself or get notifications in a group, if "you" write the message. The best way is to create a own google account for your hangouts bot.
**IMPORTANT:** If you secured your account with 2 factor authorization: Only verification by app or SMS are supported. There is no support for verification by prompt on your phone.
**IMPORTANT 2:** If you are sure your email and password is correct, but the component says the login is invalid. Wait a few hours and try it again, it might be, that google asks for a captcha which we can't support. Google official don't support bots at hangouts, that's why we have to work around this.
The authentication token will be generated and stored internally.
```yaml
# Example configuration.yaml entry
hangouts:
intents:
LivingRoomTemperature:
sentences:
- What is the temperature in the living room
conversations:
- id: CONVERSATION_ID1
- id: CONVERSATION_ID2
error_suppressed_conversations:
- id: CONVERSATION_ID2
```
{% configuration %}
intents:
description: "Intents that the hangouts component should understand."
required: false
type: map
default: empty
keys:
'`<INTENT NAME>`':
description: "Single intent entry."
required: true
type: map
keys:
sentences:
description: "Sentences that should trigger this intent."
required: true
type: list
conversations:
description: "A list of conversations that triggers this intent. If no conversation are given, every conversations triggers the intent."
required: false
type: [map]
default: empty
keys:
id:
description: "Specifies the id of the conversation. *The conversation id can be obtained from the `hangouts.conversations` entity.*"
required: true
type: string
error_suppressed_conversations:
description: "A list of conversations that won't get a message if the intent is not known."
required: false
type: [map]
default: empty
keys:
id:
description: "Specifies the id of the conversation. *The conversation id can be obtained from the `hangouts.conversations` entity.*"
required: true
type: string
{% endconfiguration %}
The conversations has to be precreated, the conversation id can be obtained from the `hangouts.conversations` entity. Make sure to use quotes around the conversation id or alias to escape special characters (`!`, and `#`) in YAML.
## {% linkable_title Adding sentences %}
```yaml
# The Hangouts component
hangouts:
intents:
HassLightSet:
sentences:
- Toggle {name}.
conversations:
- id: CONVERSATION_ID1
Ping:
sentences:
- How many Conversation do you know
error_suppressed_conversations:
- id: CONVERSATION_ID2
intent_script:
Ping:
speech:
text: I know {% raw %}{{ states.hangouts.conversations.state }}{% endraw %} conversations
```
This configuration will:
- Toggle the light in the given location in a specific conversation.
- Return the conversations the bot know.
## {% linkable_title Adding advanced custom sentences %}
Sentences can contain slots (marked with curly braces: `{name}`) and optional words (marked with square brackets: `[the]`). The values of slots will be passed on to the intent and are available inside the templates.
The following configuration can handle the following sentences:
- Change the lights to red
- Change the lights to green
- Change the lights to blue
- Change the lights to the color red
- Change the lights to the color green
- Change the lights to the color blue
```yaml
# Example configuration.yaml entry
hangouts:
intents:
ColorLight:
sentences:
- Change the lights to [the color] {color}
{% raw %}
intent_script:
ColorLight:
speech:
text: Changed the lights to {{ color }}.
action:
service: light.turn_on
data_template:
rgb_color:
- "{% if color == 'red' %}255{% else %}0{% endif %}"
- "{% if color == 'green' %}255{% else %}0{% endif %}"
- "{% if color == 'blue' %}255{% else %}0{% endif %}"
{% endraw %}
```
## {% linkable_title Services %}
### {% linkable_title Service `hangouts.update` %}
Updates the list of conversations.
| Service data attribute | Optional | Description |
|------------------------|----------|--------------------------------------------------|
| | | |
### {% linkable_title Service `hangouts.send_message` %}
Sends a message to the given conversations.
| Service data attribute | Optional | Description |
|------------------------|----------|--------------------------------------------------|
| target | List of targets with id or name. [Required] | [{"id": "UgxrXzVrARmjx_C6AZx4AaABAagBo-6UCw"}, {"name": "Test Conversation"}] |
| message | List of message segments, only the "text" field is required in every segment. [Required] | [{"text":"test", "is_bold": false, "is_italic": false, "is_strikethrough": false, "is_underline": false, "parse_str": false, "link_target": "http://google.com"}, ...] |

15
source/_components/homematic.markdown
View File

@ -187,6 +187,7 @@ To get the `homematic.keypress` event for some HomeMatic IP devices like WRC2 /
- *homematic.reconnect*: Reconnect to CCU/Homegear without restarting Home Assistant (useful when CCU has been restarted)
- *homematic.set_variable_value*: Set the value of a system variable.
- *homematic.set_device_value*: Control a device manually (even devices without support). Equivalent to setValue-method from XML-RPC.
- *homematic.put_paramset*: Manually change a device's paramset (even devices without support). Equivalent to putParamset-method from XML-RPC.
#### {% linkable_title Examples %}
@ -257,6 +258,20 @@ action:
value: 23.0
```
Set the week program of a wall thermostat:
```yaml
...
action:
service: homematic.put_paramset
data:
interface: wireless
address: LEQ1234567
paramset_key: MASTER
paramset:
WEEK_PROGRAM_POINTER: 1
```
Manually set lock on KeyMatic devices:
```yaml

288
source/_components/insteon.markdown Normal file
View File

@ -0,0 +1,288 @@
---
layout: page
title: "Insteon"
description: "Instructions on how to setup an Insteon Modem (PLM or Hub) locally within Home Assistant."
date: 2018-08-20 16:00
sidebar: true
comments: false
sharing: true
footer: true
logo: insteon.png
ha_category: Hub
ha_iot_class: "Local Push"
ha_version: 0.77
---
This component adds "local push" support for INSTEON Modems allowing
linked INSTEON devices to be used within Home Assistant as binary sensors,
lights, fans, sensors and switches. Device support is provided by the
underlying [insteonplm] package. It is known to work with the [2413U] USB and
[2412S] RS242 flavors of PLM and the [2448A7] USB stick. It has also been
tested to work with the [2245] Hub.
[insteonplm]: https://github.com/nugget/python-insteonplm
[2413U]: https://www.insteon.com/powerlinc-modem-usb
[2412S]: https://www.insteon.com/powerlinc-modem-serial
[2448A7]: https://www.smarthome.com/insteon-2448a7-portable-usb-adapter.html
[2245]: https://www.insteon.com/insteon-hub/
### {% linkable_title INSTEON Modem configuration %}
To setup a Powerline Modem (PLM) device such as the [2413U], use the following
configuration:
```yaml
# PLM configuration variables
insteon:
port: SERIAL_PORT
```
To setup an INSTEON Hub such as the [2245], use the following configuration:
```yaml
# Hub configuration variables
insteon:
host: HOST
ip_port: IP_PORT
username: USERNAME
password: PASSWORD
```
Addtional configuration items are available:
```yaml
insteon:
<PLM or Hub configruation>
device_override:
- address: ADDRESS
cat: CATEGORY
subcat: SUBCATEGORY
firmware: FIRMWARE
product_key: PRODUCT_KEY
x10_devices:
- housecode: HOUSECODE
unitcode: UNITCODE
platform: PLATFORM
steps: STEPS
x10_all_units_off: HOUSECODE
x10_all_lights_on: HOUSECODE
x10_all_lights_off: HOUSECODE
```
Configuration variables:
- **port** (*Required for PLM setup*): The serial or USB port for your device,
e.g., `/dev/ttyUSB0`
- **host** (*Required for Hub setup*): The host name or IP address of the Hub
- **ip_port** (*Optional for Hub setup*): The IP port number of the Hub.
(default value is 25105)
- **username** (*Required for Hub setup*): The username to login to the local
Hub
- **password** (*Required for Hub setup*): The password to login to the local
Hub
- **device_override** (*Optional*): Override the default device definition
- *ADDRESS* is found on the device itself in the form 1A.2B.3C or 1a2b3c
- *CATEGORY* is found in the back of the device's User Guide in the form of
0x00 - 0xff
- *SUBCATEGORY* is found in the back of the device's User Guide in the form
of 0x00 - 0xff
- *FIRMWARE* and *PRODUCT_KEY* are more advanced options and will typically
not be used.
- **x10_devices** (*Optional*): Define X10 devices to control or respond to
- *HOUSECODE* is the X10 housecode values a - p
- *UNITCODE* is the X10 unit code values 1 - 16
- *PLATFORM* is the Home Assistant Platform to associate the device with.
The following platforms are supported
- binary_sensor: Used for on/off devices or keypad buttons that are read only.
- light: Used for dimmable X10 devices
- switch: Used for On/Off X10 devices
- *STEPS* is the number of dim/bright steps the device supports. Used for
dimmable X10 devices only. Default value is 22.
- **x10_all_units_off** (*Optional*): Creates an binary_sensor that responds
to the X10 standard command for All Units Off.
- **x10_all_lights_on** (*Optional*): Creates an binary_sensor that responds
to the X10 standard command for All Lights On
- **x10_all_lights_off** (*Optional*): Creates an binary_sensor that responds
to the X10 standard command for All Lights Off
### {% linkable_title Autodiscovery %}
The first time autodiscovery runs, the duration may require up to 20 seconds
per device. Subsequent startups will occur much quicker using cached device
information. If a device is not recognized during autodiscovery, you can add
the device to the **device_override** configuration.
In order for a device to be discovered it must be linked to the INSTEON Modem
as either a responder or a controller.
### {% linkable_title Linking Devices to the INSTEON Modem %}
In order for any two Insteon devices to talk with one another, they must be
linked. For an overview of device linking please read the Insteon page on
[understanding linking]. The Insteon Modem module supports All-Linking through
[Development Tools] service calls. The following services are available:
- **insteon.add_all_link**: Puts the Insteon Modem (IM) into All-Linking
mode. The IM can be set as as controller or a responder. If the IM is a
controler, put the IM into linking mode then press the SET button on the
device. If the IM is a responer, press the SET button on the device then
put the IM into linking mode.
- **insteon.delete_all_link**: Tells the Insteon Modem (IM) to remove an
All-Link record from the All-Link Database of the IM and a device. Once the IM
is set to delete the link, press the SET button on the corresponding device
to complete the process.
- **insteon.load_all_link_database**: Load the All-Link Database for a
device. WARNING - Loading a device All-Link database may take a LONG time and
may need to be repeated to obtain all records.
- **insteon.print_all_link_database**: Print the All-Link Database for a
device. Requires that the All-Link Database is loaded first.
- **insteon.print_im_all_link_database**: Print the All-Link Database for
the INSTEON Modem (IM).
If you are looking for more advanced options, you can use the
[insteonplm_interactive] command line tool that is distributed with the
[insteonplm] Python module. Please see the documentation on the [insteonplm]
GitHub site. Alternatively, you can download [HouseLinc] which runs on any
Windows PC, or you can use [Insteon Terminal] which is open source and runs
on most platforms. SmartHome no longer supports HouseLinc, but it still
works. Insteon Terminal is a very useful tool but please read the disclaimers
carefully, they are important.
[understanding linking]: http://www.insteon.com/support-knowledgebase/2015/1/28/understanding-linking
[Development Tools]: https://www.home-assistant.io/docs/tools/dev-tools/
[HouseLinc]: https://www.smarthome.com/houselinc.html
[Insteon Terminal]: https://github.com/pfrommerd/insteon-terminal
[insteonplm_interactive]: https://github.com/nugget/python-insteonplm#command-line-interface
### {% linkable_title Customization %}
The only configuration item that is necessary is the PLM port or Hub IP
address, username and password so that Home Assistant can connect to the
INSTEON Modem. This will expose all the supported INSTEON devices which exist
in the modem’s ALL-Link database. However, devices will only be shown by their
INSTEON hex address (e.g., “1A.2B.3C”) which can be a bit unwieldy. As you link
and unlink devices using the ‘Set’ buttons, they’ll be added and removed from
Home Assistant automatically.
You can use the normal Home Assistant [device customization] section of your
configuration to assign friendly names and special icons to your devices. This
is especially useful for setting device_class on your binary_sensor INSTEON
devices.
[device customization]: /getting-started/customizing-devices/
### {% linkable_title Device Overrides %}
INSTEON devices are added to Home Assistant using the platform(s) that make the
most sense given the model and features of the hardware. The features of the
INSTEON device are built into the Home Assistant platform. Changing the
platform is not recommended. There are two primary uses for the
**device_override** feature.
- Devices that do not respond during autodiscovery. This is common for battery
operated devices.
- Devices that have not been fully developed. This allows an unknown device to
be mapped to a device that operates similarly to another device.
### {% linkable_title Example Configuration with Options%}
```yaml
# Full example of insteon configuration with customizations and overrides
homeassistant:
customize:
light.a1b2c3:
friendly_name: Bedside Lamp
binary_sensor.a2b3c4:
friendly_name: Garage Door
device_class: opening
insteon:
port: /dev/ttyUSB0
device_override:
- address: a1b2c3 # Hidden Door Sensor [2845-222]
cat: 0x10
subcat: 0x11
```
### {% linkable_title What NOT to do %}
Insteon Modem is a top level component and device discovery will identify
the Home Assistant platform the device belongs in. As such, do not
declare Insteon devices in other platforms. For example, this configuration
will NOT work:
```yaml
light:
- platform: insteon
address: 1a2b3c
```
### {% linkable_title Events and Mini-Remotes %}
Mini-Remote devices do not appear as Home Assistant entities. They generate
events. The following events are available:
- **insteon.button_on**
- **address**: (required) The Insteon device address in lower case without
dots (e.g. 1a2b3c)
- **button**: (Optional) The button id in lower case. For an 4 button remote
the values are a to d. For an 8 button remote the values are a to g. For
a one button remote this field is not used.
- **insteon.button_of**
- **address**: (required) The Insteon device address in lower case without
dots (e.g. 1a2b3c)
- **button**: (Optional) The button id in lower case. For an 4 button remote
the values are a to d. For an 8 button remote the values are a to g. For
a one button remote this field is not used.
This allows the mini-remotes to be configured as
Here is an example of how to use these events for automations:
```
automation:
# 4 or 8 button remote with button c pressed
trigger:
platform: event
event_type: insteon.button_on
event_data:
address: 1a2b3c
button: c
condition:
- condition: state
entity_id: light.some_light
state: 'off'
action:
service: light.turn_on
entity_id: light.some_light
# single button remote
trigger:
platform: event
event_type: insteon.button_on
event_data:
address: 1a2b3c
condition:
- condition: state
entity_id: light.some_light
state: 'off'
action:
service: light.turn_on
entity_id: light.some_light
```
### {% linkable_title Known Issues with the INSTEON Hub %}
The INSTEON Hub has three known issues that are inherent to the design of the
Hub:
1. If you see multiple error messages in the log file stating the Hub
connection is closed and reconnection has failed, this generally requires
the Hub to be restarted in order to reconnect.
2. You cannot use both Home Assistant and the INSTEON app. If you do, the
changes made in the app will not appear in Home Assistant. Changes made in
Home Assistant will appear in the app after a period of time, however.
3. The Hub response times can be very slow. This is due to the Hub polling
devices frequently. Since only one INSTEON message can be broadcast at a time,
messages to and from Home Assistant can be delayed.

50
source/_components/insteon_local.markdown
View File

@ -10,53 +10,9 @@ footer: true
logo: insteon.png
ha_category: Hub
ha_iot_class: "Local Polling"
ha_release: 0.36
redirect_from: /components/insteon_hub/
ha_version: 0.36
---
The `insteon_local` component let you use your [Insteon Hub](http://www.insteon.com/insteon-hub/) with Home Assistant.
The `insteon_local` component is depreciated and has been replaced by the [Insteon] component.
## {% linkable_title Configuration %}
To integrate your Insteon Hub (local setup) with Home Assistant, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml platform entry
insteon_local:
host: YOUR_HUB_IP
username: YOUR_HUB_USERNAME
password: YOUR_HUB_PASSWORD
```
{% configuration %}
host:
description: The IP address of your hub.
required: true
type: string
username:
description: The username used to access the Insteon interface (find in your Insteon app).
required: true
type: string
password:
description: The password used to access the Insteon interface.
required: true
type: string
timeout:
description: Timeout to wait for connections.
required: false
type: time
default: 10 seconds
port:
description: The port your hub is configured to listen to.
required: false
type: string
default: 25105
{% endconfiguration %}
*Note: The username and password here are for the hub and are different than the ones used to access the app. You can usually find these on the bottom of your hub (unless you've changed them through the settings in the app)*
The `insteon_local` component currently supports lights (dimmers), switches and fans.
<p class='note'>
This component replaces the old `insteon_hub` component, which has been removed due to a complaint by Insteon.
</p>
[Insteon] /component/insteon

205
source/_components/insteon_plm.markdown
View File

@ -10,209 +10,10 @@ footer: true
logo: insteon.png
ha_category: Hub
ha_iot_class: "Local Push"
ha_release: 0.39
ha_version: 0.39
---
This component adds "local push" support for INSTEON PowerLinc Modems allowing linked INSTEON devices to be used within Home Assistant as lights, switches, and binary sensors. Device support is provided by the underlying [insteonplm] package. It is known to work with the [2413U] USB and [2412S] RS242 flavors of PLM and the [2448A7] USB stick. This component does not work with the IP-based hub products. For that, you'll want the [Insteon local component](/components/insteon_local/) instead.
The `insteon_plm` component is depreciated and has been replaced by the [Insteon] component.
[insteonplm]: https://github.com/nugget/python-insteonplm
[2413U]: https://www.insteon.com/powerlinc-modem-usb
[2412S]: https://www.insteon.com/powerlinc-modem-serial
[2448A7]: https://www.smarthome.com/insteon-2448a7-portable-usb-adapter.html
[Insteon] /component/insteon
## {% linkable_title Configuration %}
```yaml
# insteon_plm supported configuration variables
insteon_plm:
port: SERIAL_PORT
device_override:
- address: ADDRESS
cat: CATEGORY
subcat: SUBCATEGORY
firmware: FIRMWARE
product_key: PRODUCT_KEY
x10_devices:
- housecode: HOUSECODE
unitcode: UNITCODE
platform: PLATFORM
steps: STEPS
x10_all_units_off: HOUSECODE
x10_all_lights_on: HOUSECODE
x10_all_lights_off: HOUSECODE
```
{% configuration %}
port:
description: The port for your device, e.g., `/dev/ttyUSB0`
required: true
type: string
device_override:
description: Override the default device definition
required: false
type: list
keys:
ADDRESS:
description: is found on the device itself in the form 1A.2B.3C or 1a2b3c
CATEGORY:
description: is found in the back of the device's User Guide in the form of 0x00 - 0xff
SUBCATEGORY:
description: is found in the back of the device's User Guide in the form of 0x00 - 0xff
FIRMWARE:
description: is a more advanced option and will typically not be used.
PRODUCT_KEY:
description: is a more advanced option and will typically not be used.
x10_devices:
description: Define X10 devices to control or respond to
required: false
type: list
keys:
HOUSECODE:
description: is the X10 housecode values a - p
UNITCODE:
description: is the X10 unit code values 1 - 16
PLATFORM:
description: is the Home Assistant Platform to associate the device with. Choose one of the following supported platforms.
type: string
keys:
binary_sensor:
description: Used for on/off devices or keypad buttons that are read only.
light:
description: Used for dimmable X10 devices
switch:
description: Used for On/Off X10 devices
STEPS:
description: is the number of dim/bright steps the device supports. Used for dimmable X10 devices only.
default: 22
x10_all_units_off:
description: Creates an binary_sensor that responds to the X10 standard command for All Units Off.
required: false
x10_all_lights_on:
description: Creates an binary_sensor that responds to the X10 standard command for All Lights On
required: false
x10_all_lights_off:
description: Creates an binary_sensor that responds to the X10 standard command for All Lights Off
required: false
{% endconfiguration %}
### {% linkable_title Autodiscovery %}
The first time autodiscovery runs, the duration may require up to 20 seconds per device. Subsequent startups will occur much quicker using cached device information. If a device is not recognized during autodiscovery, you can add the device to the **device_override** configuration.
In order for a device to be discovered it must be linked to the PLM as either a responder or a controller.
### {% linkable_title Linking Devices to the PLM %}
In order for any two Insteon devices to talk with one another, they must be linked. For an overview of device linking, please read the Insteon page on [understanding linking]. The Insteon PLM module supports All-Linking through [Development Tools] service calls. The following services are available:
- **insteon_plm.add_all_link**: Tells the Insteon Modem (IM) start All-Linking mode. Once the IM is in All-Linking mode, press the link button on the device to complete All-Linking.
- **insteon_plm.delete_all_link**: Tells the Insteon Modem (IM) to remove an All-Link record from the All-Link Database of the IM and a device. Once the IM is set to delete the link, press the link button on the corresponding device to complete the process.
- **insteon_plm.load_all_link_database**: Load the All-Link Database for a device. WARNING - Loading a device All-Link database is very time consuming and inconsistent. This may take a LONG time and may need to be repeated to obtain all records.
- **insteon_plm.print_all_link_database**: Print the All-Link Database for a device. Requires that the All-Link Database is loaded into memory.
- **insteon_plm.print_im_all_link_database**: Print the All-Link Database for the INSTEON Modem (IM).
If you are looking for more advanced options, you can use the [insteonplm_interactive] command line tool that is distributed with the
[insteonplm] Python module. Please see the documentation on the [insteonplm] GitHub site. Alternatively, you can download [HouseLinc] which runs on any Windows PC, or you can use [Insteon Terminal] which is open source and runs on most platforms. SmartHome no longer supports HouseLinc, but it still works. Insteon Terminal is a very useful tool but please read the disclaimers carefully, they are important.
[understanding linking]: http://www.insteon.com/support-knowledgebase/2015/1/28/understanding-linking
[Development Tools]: https://www.home-assistant.io/docs/tools/dev-tools/
[HouseLinc]: https://www.smarthome.com/houselinc.html
[Insteon Terminal]: https://github.com/pfrommerd/insteon-terminal
[insteonplm_interactive]: https://github.com/nugget/python-insteonplm#command-line-interface
### {% linkable_title Customization %}
The only configuration item that is absolutely necessary is the port so that Home Assistant can connect to the PLM. This will expose all the supported INSTEON devices which exist in the modem’s ALL-Link database. However, devices will only be shown by their INSTEON hex address (e.g., “1A.2B.3C”) which can be a bit unwieldy. As you link and unlink devices using the ‘Set’ buttons, they’ll be added and removed from Home Assistant automatically.
You can use the normal Home Assistant [device customization](/getting-started/customizing-devices/) section of your configuration to assign friendly names and special icons to your devices. This is especially useful for setting device_class on your binary_sensor INSTEON devices.
### {% linkable_title Device Overrides %}
INSTEON devices are added to Home Assistant using the platform(s) that make the most sense given the model and features of the hardware. The features of the INSTEON device are built into the Home Assistant platform. Changing the platform is not recommended. There are two primary uses for the **device_override** feature.
- Devices that do not respond during autodiscovery. This is common for battery operated devices.
- Devices that have not been fully developed. This allows an unknown device to be mapped to a device that operates similarly to another device.
### {% linkable_title Example Configuration with Options%}
```yaml
# Full example of insteon_plm configuration with customizations and overrides
homeassistant:
customize:
light.a1b2c3:
friendly_name: Bedside Lamp
binary_sensor.a2b3c4:
friendly_name: Garage Door
device_class: opening
insteon_plm:
port: /dev/ttyUSB0
device_override:
- address: a1b2c3 # Hidden Door Sensor [2845-222]
cat: 0x10
subcat: 0x11
```
### {% linkable_title What NOT to do %}
Insteon PLM is a top level component and device discovery will identify the Home Assistant platform the device belongs in. As such, do not declare Insteon devices in other platforms. For example, this configuration will NOT work:
```yaml
light:
- platform: insteon_plm
address: 1a2b3c
```
### {% linkable_title Events and Mini-Remotes %}
Mini-Remote devices do not appear as Home Assistant entities. They generate
events. The following events are available:
- **insteon_plm.button_on**
- **address**: (required) The Insteon device address in lower case without
dots (e.g. 1a2b3c)
- **button**: (Optional) The button id in lower case. For an 4 button remote
the values are a to d. For an 8 button remote the values are a to g. For
a one button remote this field is not used.
- **insteon_plm.button_of**
- **address**: (required) The Insteon device address in lower case without
dots (e.g. 1a2b3c)
- **button**: (Optional) The button id in lower case. For an 4 button remote
the values are a to d. For an 8 button remote the values are a to g. For
a one button remote this field is not used.
This allows the mini-remotes to be configured as
Here is an example of how to use these events for automations:
```
automation:
# 4 or 8 button remote with button c pressed
trigger:
platform: event
event_type: insteon_plm.button_on
event_data:
address: 1a2b3c
button: c
condition:
- condition: state
entity_id: light.some_light
state: 'off'
action:
service: light.turn_on
entity_id: light.some_light
# single button remote
trigger:
platform: event
event_type: insteon_plm.button_on
event_data:
address: 1a2b3c
condition:
- condition: state
entity_id: light.some_light
state: 'off'
action:
service: light.turn_on
entity_id: light.some_light
```

33
source/_components/konnected.markdown
View File

@ -74,7 +74,7 @@ devices:
description: The number corresponding to the _IO index_ of the labeled pin on the NodeMCU dev board. See the [NodeMCU GPIO documentation](https://nodemcu.readthedocs.io/en/master/en/modules/gpio/) for more details. Valid values are 1, 2, 5, 6, 7 and 9.
required: exclusive
zone:
description: The number corresponding to the labeled zone on the [Konnected Alarm Panel](https://konnected.io) board. Valid values are 1, 2, 3, 4, 5 and 6.
description: The number corresponding to the labeled zone on the [Konnected Alarm Panel](https://konnected.io) board. Valid values are `1`, `2`, `3`, `4`, `5` and `6`.
required: exclusive
type:
description: Any [binary sensor](/components/binary_sensor/) class, typically `door`, `window`, `motion` or `smoke`.
@ -92,16 +92,25 @@ devices:
description: The number corresponding to the _IO index_ of the labeled pin on the NodeMCU dev board. See the [NodeMCU GPIO documentation](https://nodemcu.readthedocs.io/en/master/en/modules/gpio/) for more details. Valid values are 1, 2, 5, 6, 7 and 8.
required: exclusive
zone:
description: The number corresponding to the labeled zone on the [Konnected Alarm Panel](https://konnected.io) board or the word `out` to specify the dedicated ALARM/OUT terminal on the Konnected board. Valid values are 1, 2, 3, 4, 5 and out.
description: The number corresponding to the labeled zone on the [Konnected Alarm Panel](https://konnected.io) board or the word `out` to specify the dedicated ALARM/OUT terminal on the Konnected board. Valid values are `1`, `2`, `3`, `4`, `5` and `out`.
required: exclusive
name:
description: The name of the device used in the front end.
required: false
default: automatically generated
activation:
description: Either "low" or "high" to specify the state when the switch is turned on.
description: Either `low` or `high` to specify the state when the switch is turned on.
default: high
required: false
momentary:
description: Duration of the momentary pulse in milliseconds. To make a half-second momentary contact using a relay for a garage door opener, set this value to `500`.
required: false
pause:
description: Time of the pause between pulses in milliseconds when also used with _momentary_ and _repeat_. To make a door chime "beep" with piezo buzzer, set this value to `55`, set _momentary_ to `65`, and _repeat_ to `3` or `4`.
required: false
repeat:
description: Number of times to repeat a momentary pulse. Set to `-1` to make an infinite repeat. This is useful as an alarm or warning when used with a piezo buzzer.
required: false
{% endconfiguration%}
#### {% linkable_title Configuration Notes %}
@ -109,7 +118,7 @@ devices:
- Either **pin** or **zone** is required for each actuator or sensor. Do not use both in the same definition.
- Pin `D8` or the `out` zone will only work when activation is set to high (the default).
## {% linkable_title Full configuration %}
## {% linkable_title Full Configuration %}
```yaml
# Example configuration.yaml entry
@ -121,12 +130,25 @@ konnected:
- zone: 1
type: door
name: 'Front Door'
- zone: 2
type: smoke
name: 'Bedroom Smoke Detector'
- zone: 3
type: motion
name: 'Test Motion'
switches:
- zone: out
name: siren
- zone: 5
name: 'Beep Beep'
momentary: 65
pause: 55
repeat: 4
- zone: 5
name: Warning
momentary: 65
pause: 55
repeat: -1
- id: 438a38
binary_sensors:
- pin: 1
@ -139,6 +161,9 @@ konnected:
- pin: 5
name: 'Garage Door'
activation: low
momentary: 500
- pin: 8
name: LED Light
```
### {% linkable_title Pin Mapping %}

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

@ -15,7 +15,7 @@ ha_iot_class: "Local Push"
See the [deCONZ main component](/components/deconz/) for configuration instructions.
The `Entity Id` names will be `light.device_name`, where `device_name` is defined in deCONZ. Light groups created in deCONZ will be created in Home Assistant as lights named `light.group_name_in_deconz`, allowing the user to control groups of lights with only a single API call to deCONZ.
The `entity_id` names will be `light.device_name`, where `device_name` is defined in deCONZ. Light groups created in deCONZ will be created in Home Assistant as lights named `light.group_name_in_deconz`, allowing the user to control groups of lights with only a single API call to deCONZ.
#### {% linkable_title Verified supported lights %}

21
source/_components/light.insteon.markdown Normal file
View File

@ -0,0 +1,21 @@
---
layout: page
title: "Insteon Light"
description: "Instructions on how to setup Insteon lights locally within Home Assistant."
date: 2018-08-20 16:00
sidebar: true
comments: false
sharing: true
footer: true
logo: insteon.png
ha_category: Light
ha_iot_class: "Local Push"
ha_version: 0.77
---
The `insteon` light platform lets you control your lights through
an INSTEON Modem (PLM and Hub) device connected directly to your system on a
USB, serial port or TCPIP connection. To add support, set up the primary
[insteon] component.
[insteon]: /components/insteon/

19
source/_components/light.insteon_local.markdown
View File

@ -1,19 +0,0 @@
---
layout: page
title: "Insteon (local) Light"
description: "Instructions on how to setup the Insteon Hub Lights locally within Home Assistant."
date: 2016-12-18 08:00
sidebar: true
comments: false
sharing: true
footer: true
logo: insteon.png
ha_category: Light
ha_iot_class: "Local Push"
ha_release: 0.36
redirect_from: /components/light.insteon_hub/
---
The `insteon_local` light component lets you control your lights connected to an [Insteon Hub](http://www.insteon.com/insteon-hub/) with Home Assistant.
To get your Insteon lights working with Home Assistant, follow the instructions for the general [Insteon local component] (/components/insteon_local/). The lights will be automatically discovered and added to Home Assistant. The device names will be the Insteon address of the lights.

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

@ -1,16 +0,0 @@
---
layout: page
title: "Insteon PLM Light"
description: "Instructions on how to setup the Insteon PLM Lights locally within Home Assistant."
date: 2017-02-19 17:00
sidebar: true
comments: false
sharing: true
footer: true
logo: insteon.png
ha_category: Light
ha_iot_class: "Local Push"
ha_release: 0.39
---
The `insteon_plm` light platform lets you control your dimmable light switches through an INSTEON PowerLinc Modem (PLM) device connected directly to your system on an USB or serial port. To add support, set up the primary [insteon_plm](/components/insteon_plm/) component.

52
source/_components/notify.hangouts.markdown Normal file
View File

@ -0,0 +1,52 @@
---
layout: page
title: "Google Hangouts"
description: "Instructions on how to add Google Hangouts notifications to Home Assistant."
date: 2018-08-18 20:00
sidebar: true
comments: false
sharing: true
footer: true
logo: hangouts.png
ha_category: Notifications
ha_release: 0.77
---
The `hangouts` platform allows you to deliver notifications from Home Assistant to [Google Hangouts](http://hangouts.google.com) conversations. Conversations can be both direct as well as group chats.
## {% linkable_title Configuration %}
To enable Hangouts notifications in your installation, you first need to configure
the [Hangouts component](/components/hangouts/). Then, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
notify:
- name: NOTIFIER_NAME
platform: hangouts
default_conversations:
- id: CONVERSATION_ID1
- id: CONVERSATION_ID2
```
{% configuration %}
name:
description: "Setting the optional parameter `name` allows multiple notifiers to be created. The default value is `notify`. The notifier will bind to the service `notify.NOTIFIER_NAME`."
required: false
type: string
default_conversations:
description: "The conversations all messages will be sent to, when no other target is given."
required: true
type: [map]
keys:
id:
description: "Specifies the id of the conversation. *The conversation id can be obtained from the `hangouts.conversations` entity.*"
required: true
type: string
{% endconfiguration %}
The conversations has to be precreated, the conversation id can be obtained from the `hangouts.conversations` entity. Make sure to use quotes around the conversation id or alias to escape special characters (`!`, and `#`) in YAML.
To use notifications, please see the [getting started with automation page](/getting-started/automation/).

7
source/_components/openuv.markdown
View File

@ -80,7 +80,7 @@ sensors:
description: the conditions to create sensors from
required: false
type: list
default: all ( `current_ozone_level`, `current_uv_index`, `max_uv_index`, `safe_exposure_time_type_1`, `safe_exposure_time_type_2`, `safe_exposure_time_type_3`, `safe_exposure_time_type_4`, `safe_exposure_time_type_5`, `safe_exposure_time_type_6` )
default: all ( `current_ozone_index`, `current_uv_index`, `current_uv_level`, `max_uv_index`, `safe_exposure_time_type_1`, `safe_exposure_time_type_2`, `safe_exposure_time_type_3`, `safe_exposure_time_type_4`, `safe_exposure_time_type_5`, `safe_exposure_time_type_6` )
{% endconfiguration %}
## {% linkable_title Binary Sensor Types %}
@ -100,6 +100,11 @@ This sensor displays the current ozone level in du (Dobson Units).
This sensor displays the current UV index.
### {% linkable_title `current_uv_level` %}
This sensor displays the level of current UV index, which is calculated based
on [UV Index Levels & Colors](https://www.openuv.io/kb/uv-index-levels-colors).
### {% linkable_title `max_uv_index` %}
This sensor displays the maximum UV index that will be encountered that day (at

7
source/_components/panel_custom.markdown
View File

@ -38,8 +38,9 @@ Configuration variables:
- **sidebar_title** (*Optional*): Friendly title for the panel in the sidebar. Omitting it means no sidebar entry (but still accessible through the URL).
- **sidebar_icon** (*Optional*): Icon for entry. Pick an icon that you can find on [materialdesignicons.com](https://materialdesignicons.com/) to use for your input and prefix the name with `mdi:`. For example `mdi:car`, `mdi:ambulance`, or `mdi:motorbike`.
- **url_path** (*Optional*): The URL your panel will be available on in the frontend. If omitted will default to the panel name.
- **js_url** (*Required*): The URL that contains the JavaScript of your panel.
- **js_url** (*Required*): The URL that contains the JavaScript of your panel. This is exclusive to `module_url` and `webcomponent_path`.
- **module_url** (*Optional*): The URL that contains the JavaScript module of your panel. Loaded as a JavaScript module instead of a script. This is exclusive to `js_url` and `webcomponent_path`.
- **config** (*Optional*): Configuration to be passed into your web component when being instantiated.
- **embed_iframe** (*Optional*): Set to `true` to embed panel in iframe. This is necessary if the panel is panel is using the React framework or if it contains conflicting web components.
- **embed_iframe** (*Optional*): Set to `true` to embed panel in iframe. This is necessary if the panel is using the React framework or if it contains conflicting web components.
- **trust_external_script** (*Optional*): By default the user has to confirm before loading a script from an external source. Setting this to `true` will omit this confirmation.
- **webcomponent_path** (*Optional* *DEPRECATED*): The HTML path to your component. If omitted will default to `<config dir>/panels/<component name>.html`
- **webcomponent_path** (*Optional* *DEPRECATED*): The HTML path to your component. If omitted will default to `<config dir>/panels/<component name>.html` This is exclusive to `js_url` and `module_url`.

2
source/_components/scene.deconz.markdown
View File

@ -15,4 +15,4 @@ ha_iot_class: "Local Push"
See the [deCONZ main component](/components/deconz/) for configuration instructions.
Entity Ids will be scene.group_scene_name, where group is which group the scene belongs to and the name of the scene, both group and name are defined in deCONZ.
The `entity_id` name will be `scene.group_scene_name`, where `group` is which group the scene belongs to and the name of the scene, both group and name are defined in deCONZ.

2
source/_components/sensor.deconz.markdown
View File

@ -23,7 +23,7 @@ The following sensor types are supported:
* Switches
* Temperature sensor
Entity ids will be sensor.device_name, where device_name is defined in deCONZ. Switches aren't exposed as ordinary entities, see the [deCONZ main component](/components/deconz/) for more details.
The `entity_id` name will be `sensor.device_name`, where `device_name` is defined in deCONZ. Switches aren't exposed as ordinary entities, see the [deCONZ main component](/components/deconz/) for more details.
#### {% linkable_title Verified to be supported sensors %}

109
source/_components/sensor.glances.markdown
View File

@ -16,6 +16,8 @@ ha_release: 0.7.3
The `glances` sensor platform is consuming the system information provided by the [Glances](https://github.com/nicolargo/glances) API. This enables one to track remote host and display their stats in Home Assistant.
## {% linkable_title Setup %}
This sensors needs a running instance of `glances` on the host. The minimal supported version of `glances` is 2.3.
To start a Glances RESTful API server on its default port 61208, the a test the following command can be used:
@ -35,6 +37,8 @@ $ curl -X GET http://IP_ADDRESS:61208/api/2/mem/free
For details about auto-starting `glances`, please refer to [Start Glances through Systemd](https://github.com/nicolargo/glances/wiki/Start-Glances-through-Systemd).
## {% linkable_title Configuration %}
To enable the Glances sensor, add the following lines to your `configuration.yaml`:
```yaml
@ -44,48 +48,71 @@ sensor:
host: IP_ADDRESS
resources:
- 'disk_use_percent'
- 'disk_use'
- 'disk_free'
- 'memory_use_percent'
- 'memory_use'
- 'memory_free'
- 'swap_use_percent'
- 'swap_use'
- 'swap_free'
- 'processor_load'
- 'process_running'
- 'process_total'
- 'process_thread'
- 'process_sleeping'
- 'cpu_temp'
- 'docker_active'
- 'docker_cpu_use'
- 'docker_memory_use'
```
Configuration variables:
- **host** (*Required*): The IP address of your host, eg. `192.168.1.32`.
- **port** (*Option*): The network port to connect to. Default is `61208`.
- **name** (*Optional*): Name of the Glances sensor.
- **resources** (*Required*): Entries to monitor.
- **disk_use_percent**: Used disk space in percent
- **disk_use**: Used disk space
- **disk_free**: Free disk space
- **memory_use_percent**: Used memory in percent
- **memory_use**: Used memory
- **memory_free**: Free memory
- **swap_use_percent**: Used swap space in percent
- **swap_use**: Used swap space
- **swap_free**: Free swap space
- **processor_load**: Load
- **process_running**: Number of running processes
- **process_total**: Total number of processes
- **process_thread**: Number of threads
- **process_sleeping**: Number of sleeping processes
- **cpu_temp**: CPU Temperature (may not available on all platforms)
- **docker_active**: Count of active Docker containers
- **docker_cpu_use**: Total CPU usage in percent of Docker containers
- **docker_memory_use**: Total memory used of Docker containers
{% configuration %}
host:
description: IP address of the host where Glances is running.
required: false
type: string
default: localhost
port:
description: The port where Glances is listening.
required: false
type: int
default: 61208
name:
description: The prefix for the sensors.
required: false
type: string
default: Glances
version:
description: "The version of the Glances API. Supported version: `2` and `3`."
required: false
type: int
default: 2
resources:
description: Entries to monitor.
required: false
type: map
default: disk_use
keys:
disk_use_percent:
description: The used disk space in percent.
disk_use:
description: The used disk space.
disk_free:
description: The free disk space.
memory_use_percent:
description: The used memory in percent.
memory_use:
description: The used memory.
memory_free:
description: The free memory.
swap_use_percent:
description: The used swap space in percent.
swap_use:
description: The used swap space.
swap_free:
description: The free swap space.
processor_load:
description: The load.
process_running:
description: The number of running processes.
process_total:
description: The total number of processes.
process_thread:
description: The number of threads.
process_sleeping:
description: The number of sleeping processes.
cpu_temp:
description: The CPU temperature (may not be available on all platforms).
docker_active:
description: The count of active Docker containers.
docker_cpu_use:
description: The total CPU usage in percent of Docker containers.
docker_memory_use:
description: The total memory used by Docker containers.
{% endconfiguration %}
Not all platforms are able to provide all metrics. For instance `cpu_temp` is requires installing and configuring `lmsensors` in Ubuntu, and may not be available at all in other platforms.

21
source/_components/sensor.insteon.markdown Normal file
View File

@ -0,0 +1,21 @@
---
layout: page
title: "Insteon Sensor"
description: "Instructions on how to setup the Insteon sensors locally within Home Assistant."
date: 2018-08-20 16:00
sidebar: true
comments: false
sharing: true
footer: true
logo: insteon.png
ha_category: Sensor
ha_iot_class: "Local Push"
ha_version: 0.77
---
The `insteon` sensor platform lets you control your sensors through
an INSTEON Modem (PLM and Hub) device connected directly to your system on a
USB, serial port or TCPIP connection. To add support, set up the primary
[insteon] component.
[insteon]: /components/insteon/

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

@ -1,16 +0,0 @@
---
layout: page
title: "Insteon PLM Sensor"
description: "Instructions on how to setup the Insteon PLM sensors locally within Home Assistant."
date: 2017-02-19 17:00
sidebar: true
comments: false
sharing: true
footer: true
logo: insteon.png
ha_category: Sensor
ha_iot_class: "Local Push"
ha_release: 0.65
---
The `insteon_plm` sensor platform lets you control your sensors through an INSTEON PowerLinc Modem (PLM) device connected directly to your system on a USB or serial port. To add support, set up the primary [insteon_plm](/components/insteon_plm/) component.

67
source/_components/sensor.netatmo_public.markdown Normal file
View File

@ -0,0 +1,67 @@
---
layout: page
title: "Netatmo Public"
description: "Instructions on how to add sensors using Netatmo public data to Home Assistant."
date: 2018-07-22 21:18
sidebar: true
comments: false
sharing: true
footer: true
logo: netatmo.png
ha_category: Sensor
ha_iot_class: "Cloud Polling"
ha_release: 0.77
---
The `netatmo_public` sensor allows you to expose data from [Netatmo](https://weathermap.netatmo.com/) to Home Assistant, even if you don't have a Netatmo device yourself. Currently, only live rain data is supported.
To enable the Netatmo sensor, you have to set up [netatmo](/components/netatmo/).
## {% linkable_title Configuration %}
Next, enable the sensor by adding the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
sensor:
- platform: netatmo_public
areas:
- lat_ne: 40.719
lon_ne: -73.735
lat_sw: 40.552
lon_sw: -74.105
```
{% configuration %}
areas:
description: The list contains one or more areas to add as sensors.
required: true
type: map
keys:
lat_ne:
description: Latitude of north-eastern corner of area.
required: true
type: string
lon_ne:
description: Longitude of north-eastern corner of area.
required: true
type: string
lat_sw:
description: Latitude of south-western corner of area.
required: true
type: string
lon_sw:
description: Longitude of south-western corner of area.
required: true
type: string
name:
description: Name of the sensor.
required: false
type: string
default: Netatmo Public Data
type:
description: How to calculate the value of the sensor if there are multiple stations reporting data. Accepts `max` or `avg`.
required: false
type: string
default: max
{% endconfiguration %}

60
source/_components/sensor.noaa_tides.markdown Normal file
View File

@ -0,0 +1,60 @@
---
layout: page
title: "NOAA Tides"
description: "Instructions to add NOAA Tide information to Home Assistant."
date: 2018-07-24 08:00
sidebar: true
comments: false
sharing: true
footer: true
ha_category: Weather
ha_release: 0.75
logo: noaa.png
---
The `noaa_tides` sensor platform uses details from [NOAA Tides and Currents](https://tidesandcurrents.noaa.gov/api/) to provide information about the prediction for the tides for any location in the United States.
This sensor requires the use of a NOAA station ID. Search [NOAA Tide Predictions](https://tidesandcurrents.noaa.gov/tide_predictions.html) to find a location. Use the ID from the search results in your configuration. Alternatively, you can determine a station ID from a URL. For example, `8721164` in the following URL: `https://tidesandcurrents.noaa.gov/noaatidepredictions.html?id=8721164`
To use this sensor, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
sensor:
- platform: noaa_tides
station_id: 8721164
```
{% configuration %}
station_id:
description: ID of the station you'd like to track from https://tidesandcurrents.noaa.gov/tide_predictions.html.
required: true
type: string
name:
description: User-supplied sensor name.
required: false
default: NOAA Tides.
type: string
time_zone:
description: User-selected timezone.
required: false
default: Local Standard Time/Local Daylight Time.
type: list
keys:
gmt:
description: Greenwich Mean Time.
lst:
description: Local Standard Time. The time local to the requested station.
lst_ldt:
description: Local Standard/Local Daylight Time. The time local to the requested station.
unit_system:
description: Specify the unit system.
required: false
default: Defaults to `metric` or `imperial` based on the Home Assistant configuration.
type: string
keys:
metric:
description: Metric (Celsius, meters, cm/s) units.
english:
description: English (fahrenheit, feet, knots) units.
{% endconfiguration %}

3
source/_components/switch.deconz.markdown
View File

@ -19,9 +19,10 @@ Switches are devices like power plugs and sirens.
Note that devices in the switch platform identify as lights, so there is a manually curated list that defines which "lights" are switches.
The `Entity Id` names will be `switch.device_name`, where `device_name` is defined in deCONZ.
The `entity_id` name will be `switch.device_name`, where `device_name` is defined in deCONZ.
#### {% linkable_title Verified supported switches %}
- Innr SP120
- Osram Outdoor plug
- Heiman siren

21
source/_components/switch.insteon.markdown Normal file
View File

@ -0,0 +1,21 @@
---
layout: page
title: "Insteon Switch"
description: "Instructions on how to setup the Insteon switches locally within Home Assistant."
date: 2018-08-20 16:00
sidebar: true
comments: false
sharing: true
footer: true
logo: insteon.png
ha_category: Switch
ha_iot_class: "Local Push"
ha_version: 0.77
---
The `insteon` switch platform lets you control your on/off switches through
an INSTEON Modem (PLM and Hub) device connected directly to your system on a
USB, serial port or TCPIP connection. To add support, set up the primary
[insteon] component.
[insteon]: /components/insteon/

17
source/_components/switch.insteon_local.markdown
View File

@ -1,17 +0,0 @@
---
layout: page
title: "Insteon (local) Switch"
description: "Instructions on how to setup the Insteon Hub switches locally within Home Assistant."
date: 2016-12-18 08:00
sidebar: true
comments: false
sharing: true
footer: true
logo: insteon.png
ha_category: Switch
ha_release: 0.36
---
The `insteon_local` switch component lets you control your switches connected to an [Insteon Hub](http://www.insteon.com/insteon-hub/) with Home Assistant.
To get your Insteon switches working with Home Assistant, follow the instructions for the general [Insteon local component](/components/insteon_local/). The switches will be automatically discovered and added to Home Assistant. The device names will be the Insteon address of the switch.

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

@ -1,16 +0,0 @@
---
layout: page
title: "Insteon PLM Switch"
description: "Instructions on how to setup the Insteon PLM switches locally within Home Assistant."
date: 2017-02-19 17:00
sidebar: true
comments: false
sharing: true
footer: true
logo: insteon.png
ha_category: Switch
ha_iot_class: "Local Push"
ha_release: 0.39
---
The `insteon_plm` switch platform lets you control your on/off switches through an INSTEON PowerLinc Modem (PLM) device connected directly to your system on a USB or serial port. To add support, set up the primary [insteon_plm](/components/insteon_plm/) component.

69
source/_components/vacuum.ecovacs.markdown Normal file
View File

@ -0,0 +1,69 @@
---
layout: page
title: "Ecovacs Deebot Vacuum"
description: "Instructions on how to setup Ecovacs Deebot vacuums within Home Assistant."
date: 2018-07-27 09:00
sidebar: true
comments: false
sharing: true
footer: true
logo: ecovacs.png
ha_category: Vacuum
ha_iot_class: "Cloud Push"
ha_release: 0.77
---
The `ecovacs` vacuum platform allows you to monitor and control your Ecovacs Deebot vacuums.
You have first to setup the [Ecovacs component](/components/ecovacs/)
### {% linkable_title Component Lifespans %}
The remaining lifespan of components on your Deebot vacuum will be reported as attributes on the vacuum entity. The value will be a whole number representing the percentage of life remaining.
Here's an example of how to extract the filter's lifespan to its own sensor using a [template sensor](/components/sensor.template/):
{% raw %}
```yaml
# Example configuration.yaml entry
sensor:
- platform: template
sensors:
vacuum_filter:
friendly_name: "Vacuum Filter Remaining Lifespan"
unit_of_measurement: '%'
value_template: "{{ state_attr('vacuum.my_vacuum_id', 'component_filter') }}"
```
{% endraw %}
Or, if you want a simple binary sensor that becomes `On` when the filter needs to be replaced (5% or less):
{% raw %}
```yaml
# Example configuration.yaml entry
binary_sensor:
- platform: template
sensors:
vacuum_filter_replace:
friendly_name: "Vacuum Filter"
device_class: problem
value_template: "{{ state_attr('vacuum.my_vacuum_id', 'component_filter') <= 5 }}"
```
{% endraw %}
### {% linkable_title Handling Errors %}
The vacuum entity has an `error` attribute that will contain the _most recent_ error message that came from the vacuum. There is not a comprehensive list of all error messages, so you may need to do some experimentation to determine the error messages that your vacuum can send.
If the vacuum fires a "no error" event, the `error` attribute will change back to `None`. Note, however, that this does not happen for all types of errors.
Alternatively, you can use the `ecovacs_error` event to watch for errors. This event will contain a data payload that looks like:
```json
{
"entity_id": "vacuum.deebot_m80",
"error": "an_error_name"
}
```
Finally, if a vacuum becomes unavailable (usually due to being idle and off its charger long enough for it to completely power off,) the vacuum's `status` attribute will change to `offline` until it is turned back on.

4
source/_components/vacuum.neato.markdown
View File

@ -21,8 +21,8 @@ To add `neato` vacuum to your installation, please follow instructions in [Neato
Currently supported features are:
- `turn_on`
- `start`
- `pause`
- `stop`
- `return_to_home`
- `turn_off` (stop all activity and return to dock)
- `locate`

7
source/_components/vacuum.xiaomi_miio.markdown
View File

@ -17,11 +17,10 @@ The `xiaomi miio` vacuum platform allows you to control the state of your [Xiaom
Currently supported features are:
- `turn_on`
- `start`
- `pause`
- `stop`
- `return_to_home`
- `turn_off` (stop all activity and return to dock)
- `locate`
- `clean_spot`
- `set_fan_speed`
@ -49,7 +48,7 @@ Configuration variables:
## {% linkable_title Platform Services %}
In addition to all of the services provided by the `vacuum` component (`turn_on`, `turn_off`, `start_pause`, `stop`, `return_to_home`, `locate`, `set_fan_speed` and `send_command`), the `xiaomi` platform introduces specific services to access the remote control mode of the robot. These are:
In addition to all of the services provided by the `vacuum` component (`start`, `pause`, `stop`, `return_to_home`, `locate`, `set_fan_speed` and `send_command`), the `xiaomi` platform introduces specific services to access the remote control mode of the robot. These are:
- `xiaomi_remote_control_start`
- `xiaomi_remote_control_stop`
@ -97,7 +96,7 @@ Enter remote control mode, make one move, stop, and exit remote control mode.
## {% linkable_title Attributes %}
In addition to [all of the attributes provided by the `vacuum` component](/components/vacuum/#attributes),
(`battery_icon`, `cleaned_area`, `fan_speed`, `fan_speed_list`, `status`, and `params`), the `xiaomi` platform introduces specific attributes. These are:
(`battery_icon`, `cleaned_area`, `fan_speed`, `fan_speed_list`, and `params`), the `xiaomi` platform introduces specific attributes. These are:
- `cleaning_time`
- `do_not_disturb`

8
source/_docs/authentication.markdown
View File

@ -28,10 +28,12 @@ When logging in, make sure that the URL in the URL bar is showing the address of
## {% linkable_title Profile %}
Once you're logged in, you can access the profile page to change your user preferences. Here you can change your preferred language or password. You can also log out. You can access the profile page by clicking on your user badge in the sidebar.
Once you're logged in, you can access the profile page by clicking on the badge next to the Home Assistant title in the sidebar. Here you can change your preferred language or change your password. You can also log out.
<img src='/images/docs/authentication/profile.png' alt='Screenshot of the profile page' style='border: 0;box-shadow: none;'>
## {% linkable_title Multi-factor authentication %} (soon)
## {% linkable_title Multi-factor authentication %}
As a user, you can setup multi-factor authentication like time-based one-time passwords. This is an extra challenge that you have to solve after you finish your login. You will be able to set up these challenges from the profile page once you're logged in.
As a user, you can setup multi-factor authentication with time-based one-time passwords. This is an extra challenge that you have to solve after you finish your login. You will be able to set up these challenges from the profile page once you're logged in.
<img src='/images/docs/authentication/mfa.png' alt='Screenshot of setting up multi-factor authentication' style='border: 0;box-shadow: none;'>

49
source/_docs/authentication/multi-factor-auth.markdown
View File

@ -1,7 +1,7 @@
---
layout: page
title: "Multi-factor authentication"
description: "Guide on configuring different multi-factor authentication providers."
description: "Guide on configuring different multi-factor authentication modules."
date: 2018-08-23 09:40
redirect_from: /components/auth/
sidebar: true
@ -14,6 +14,49 @@ footer: true
This is an advanced feature. If misconfigured, you will not be able to access Home Assistant anymore!
</p>
Besides the normal authentication providers, it's also possible to configure multi-factor authentication providers. These authentication providers will require the user to solve a second challenge besides just logging in. The idea is that you ask the user for something they know, their username/password, and something they have, like a time-based authentication token from their phone.
Besides the authentication providers, it's also possible to configure multi-factor authentication modules. These authentication modules will require the user to solve a second challenge besides just logging in. The idea is that you ask the user for something they know, their username/password, and something they have, like a time-based authentication token from their phone.
This feature is currently a work in progress and no configurable multi-factor authentication providers are currently available.
Multi-factor authentication module can be used mixed-match with authentication providers. After normal authentication provider validation, the login flow will ask user for addional challenge if there are multi-factor authentication modules enabled for this user. If more than one mutli-factor authentication module enabled, user can select one of them during the login.
Multi-factor authentication module has to be enabled for user before it can be used in the login process, user can go to profile page enable it by himself.
## {% linkable_title Configuring mutli-factor authentication modules %}
<p class='note warning'>
By configuring your own instead of using the default configuration, you take full responsibility for the authentication of the system.
</p>
Multi-factor authentication modules are configured in your `configuration.yaml` under the `homeassistant:` block:
```yaml
homeassistant:
auth_mfa_modules:
- type: totp
```
## {% linkable_title Available mutli-factor authentication modules %}
Below is a list of currently available auth providers.
### {% linkable_title Time-based One-Time Password mutli-factor authentication module %}
[Time-based One-Time Password](https://en.wikipedia.org/wiki/Time-based_One-time_Password_algorithm) is widely adopted in modern authencation system, it combines a secret key with the current timestamp using a cryptographic hash function to generate a one-time password. Whoever possessed the secret key will get same one-time password in certain time period. By verifying that password, Home Assistant knows the user have the right secrt key.
When try to set up TOTP module, a QR code will show up, user can scan it by an authenticator app, or set it up manauly using the code showed in UI. After setup, user need to input a six digit number generate in the autendicator app to verify the setup is good. If the verificaiton keep falling, you need to check whether the clock on Home Asistant is accurate.
There are several authenctior apps on the market, we recommend either [Google Authenticator](https://support.google.com/accounts/answer/1066447) or [Authy](https://authy.com/)
<p class='note warning'>
Please treat the secret key like a password, never exposure it to others.
</p>
By default one TOTP multi-factor named "Authenticator app" will be auto loaded if no `auth_mfa_modules` config section defined in `configuration.yaml`.
Example of configuration
```yaml
homeassistant:
auth_mfa_modules:
- type: totp
```

8
source/_docs/authentication/providers.markdown
View File

@ -55,9 +55,13 @@ homeassistant:
- type: homeassistant
```
### {% linkable_title Trusted Network %}
### {% linkable_title Trusted Networks %}
With the trusted network auth provider you can whitelist an IP range for which no authentication will be required. The user will be prompted to pick a user to log in as.
With the trusted networks auth provider you can whitelist an IP range for which no authentication will be required. The user will be prompted to pick a user to log in as.
<p class='note info'>
The [multi-factor autentication module](../multi-factor-auth) will not participate in login process by using this auth provider.
</p>
```yaml
homeassistant:

48
source/_docs/configuration/entity-registry.markdown
View File

@ -1,48 +0,0 @@
---
layout: page
title: "Entity Registry"
description: "The entity registry contains."
date: 2016-04-20 06:00
sidebar: true
comments: false
sharing: true
footer: true
---
Starting with version 0.63, Home Assistant keeps a registry of known entities. The entity registry makes sure that entities get unique identifiers and allow customizing the identifiers and names of these entities.
Changes require that Home Assistant is shut down when you edit the file, otherwise Home Assistant may over-write your changes, and a restart of Home Assistant is required for your changes to take effect. Version 0.75 introduced a configuration user interface.
<p class='note'>
An entity needs to have a unique ID to be registered in the entity registry.
Not all integrations currently provide a unique id for their entities.
</p>
The entity registry is stored in `<config>/entity_registry.yaml`. As a user, you are unable to add entries, only update them. Here is an example file:
```yaml
climate.downstairs_virtual:
platform: nest
unique_id: EPoMyWkpNyoYu3pGlmGxabcdefghijkl
name: Downstairs thermostat
light.study_ceiling:
platform: hue
unique_id: f0:fe:6b:00:14:00:00:00-00
disabled_by: user
```
As a user, you can change the `entity_id` and add the `name` and `disabled_by`value to each entry.
- Changing the _first line_ of each entry will change the `entity_id` of the entity throughout Home Assistant.
- The value of `name` will override the _friendly name_ of the entity as given by the integration.
_Added in Home Assistant 0.64._
- The key `disabled_by` can either be `hass` or `user`. This functionality is even more experimental than the whole entity registry itself and might cause integrations to fail and might be removed in the future.
_Added in Home Assistant 0.64._
{% linkable_title Supported Components %}
Only components that provide a unique ID for entities will are supported.
Note that for Weather Underground, second and subsequent Personal Weather Station ID (pws_id) will have their monitored conditions suffixed with an index number.

18
source/_docs/scripts.markdown
View File

@ -81,7 +81,7 @@ Delays are useful for temporarily suspending your script and start it at a later
### {% linkable_title Wait %}
Wait until some things are complete. We support at the moment `wait_template` for waiting until a condition is `true`, see also on [Template-Trigger](/docs/automation/trigger/#template-trigger). It is possible to set a timeout after which the script will abort its execution if the condition is not satisfied. Timeout has the same syntax as `delay`.
Wait until some things are complete. We support at the moment `wait_template` for waiting until a condition is `true`, see also on [Template-Trigger](/docs/automation/trigger/#template-trigger). It is possible to set a timeout after which the script will continue its execution if the condition is not satisfied. Timeout has the same syntax as `delay`.
{% raw %}
```yaml
@ -92,9 +92,10 @@ Wait until some things are complete. We support at the moment `wait_template` fo
{% raw %}
```yaml
# wait until a valve is < 10 or abort after 1 minute.
- wait_template: "{{ states.climate.kitchen.attributes.valve|int < 10 }}"
# wait for sensor to trigger or 1 minute before continuing to execute.
- wait_template: "{{ is_state('binary_sensor.entrance', 'on') }}"
timeout: '00:01:00'
continue_on_timeout: 'true'
```
{% endraw %}
@ -120,6 +121,17 @@ It is also possible to use dummy variables, e.g., in scripts, when using `wait_t
```
{% endraw %}
You can also get the script to abort after the timeout by using `continue_on_timeout`
{% raw %}
```yaml
# wait until a valve is < 10 or continue after 1 minute.
- wait_template: "{{ states.climate.kitchen.attributes.valve|int < 10 }}"
timeout: '00:01:00'
continue_on_timeout: 'false'
```
{% endraw %}
### {% linkable_title Fire an Event %}
This action allows you to fire an event. Events can be used for many things. It could trigger an automation or indicate to another component that something is happening. For instance, in the below example it is used to create an entry in the logbook.

18
source/_docs/z-wave/control-panel.markdown
View File

@ -45,24 +45,6 @@ Here is where you [include and exclude](/docs/z-wave/adding/) Z-Wave devices fro
Battery powered devices need to be awake before you can use the Z-Wave control panel to update their settings. How to wake your device is device specific, and some devices will stay awake for only a couple of seconds. Please refer to the manual of your device for more details.
</p>
### {% linkable_title Renaming all entities of a node %}
When you change the `entity_id` of the `zwave.` entity, other entities of that node won't be changed. If you want to reset their `entity_id` too you need to remove them from `entity_registry.yaml`, and the process is like this:
1. Change the `entity_id` of the `zwave.` entity to set the base for all the other entities
2. Shut down Home Assistant and wait for it to stop
3. Delete the relevant entries from `entity_registry.yaml`
4. Start Home Assistant again
Each block you need to delete will look something like this, you need to delete all 4 lines for each entry. The first number of the `unique-id` is the Node ID of the Z-Wave node.
```yaml
sensor.fibaro_door_sensor_access_control:
name:
platform: zwave
unique_id: 5-72057594126614528
```
#### {% linkable_title Entities of this node %}
This is a dropdown where you can select all the entities of this node. Once selected you can then use:

2
source/_includes/asides/docs_navigation.html
View File

@ -12,7 +12,6 @@
<li>{% active_link /hassio/ Hass.io %}</li>
<li>{% active_link /docs/installation/virtualenv/ Python Virtual Env %}</li>
<li>{% active_link /docs/installation/hassbian/ Hassbian %}</li>
<!--<li>{% active_link /docs/installation/raspberry-pi-all-in-one/ Raspberry Pi All-in-One %}</li>-->
<li>{% active_link /docs/installation/updating/ Updating %}</li>
<li>{% active_link /docs/installation/troubleshooting/ Troubleshooting %}</li>
</ul>
@ -23,7 +22,6 @@
<li>{% active_link /docs/configuration/yaml/ YAML %}</li>
<li>{% active_link /docs/configuration/basic/ Basic information %}</li>
<li>{% active_link /docs/configuration/devices/ Setting up devices %}</li>
<li>{% active_link /docs/configuration/entity-registry/ Entity Registry %}</li>
<li>{% active_link /docs/configuration/customizing-devices/ Customizing entities %}</li>
<li>{% active_link /docs/configuration/troubleshooting/ Troubleshooting %}</li>
<li>{% active_link /docs/configuration/securing/ Security Check Points %}</li>

2
source/_posts/2018-03-30-release-66.markdown
View File

@ -55,7 +55,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
## Breaking Changes
- Refactor Hue: If you specify a bridge in your config, the `host` key is now required and needs to be a valid ip address. Option `allow_in_emulated_hue` has been removed. Exclude the lights via the emulated hue config. Due to the internal changes of how the Hue integration works, any Hue custom component will no longer work. ([@balloob] - [#13043]) ([hue docs]) ([light.hue docs]) (breaking change)
- Z-Wave: In version 0.47, the opt-in `new_entity_ids` configuration was added to Z-Wave to smooth the transition through the change. Support for old entity IDs is now removed, and the configuration is no longer necessary. If you are migrating from 0.63 or higher, your entity IDs will already be stored in the Entity Registry and no changes are required. If not, [entity IDs can now be manually configured using the Entity Registry](/docs/configuration/entity-registry/) if necessary. ([@armills] - [#12652]) ([zwave docs]) (breaking change)
- Z-Wave: In version 0.47, the opt-in `new_entity_ids` configuration was added to Z-Wave to smooth the transition through the change. Support for old entity IDs is now removed, and the configuration is no longer necessary. If you are migrating from 0.63 or higher, your entity IDs will already be stored in the Entity Registry and no changes are required. If not, entity IDs can now be manually configured using the Entity Registry if necessary. ([@armills] - [#12652]) ([zwave docs]) (breaking change)
- Spotcrime sensor: This update changes the sensor to require a user supplied API key as a configuration entry. The default key has been removed from the Spotcrime package and has also been modified to accept a user supplied API key.([@jcconnell] - [#12926]) ([sensor.spotcrime docs]) (breaking change)
- Smappee sensor: Fixed SI units for current consumption. Total consumption should be in kWh. not kW. ([@vandenberghev] - [#13190]) ([sensor.smappee docs]) (breaking change)
- System monitor sensor: Used and available swap space reported by the system monitor component is now measured in MiB instead of GiB. ([@DanNixon] - [#13148]) ([sensor.systemmonitor docs]) (breaking change)

452
source/_posts/2018-08-29-release-77.markdown Normal file
View File

@ -0,0 +1,452 @@
---
layout: post
title: "0.77: Authentication system 👮‍♂️ + Hangouts bot 🤖"
description: "The new authentication system is live! Chat on hangouts! "
date: 2018-08-29 00:01:00
date_formatted: "August 29, 2018"
author: Paulus Schoutsen
author_twitter: balloob
comments: true
categories: Release-Notes
og_image: /images/blog/2018-08-0.77/social.png
---
<div class='videoWrapper'>
<iframe width="560" height="315" src="https://www.youtube.com/embed/Xm6tsnXabcw" frameborder="0" allowfullscreen></iframe>
</div>
It's time for a great new release and it includes a big change: the new [authentication system](/docs/authentication/) has been activated! We've worked very hard on this for the last couple of months to make the transition as smooth as possible. Updating to this release is a non-breaking change (unless you had no API password configured). As can be seen in the video above, when you start Home Assistant after the update, you will be presented with our new onboarding flow. This will ask you to create a new account after which you will be able to log in to Home Assistant.
Once logged in, you will have access to the following new features:
- Change your password
- Configure multifactor authentication (TOTP)
- Manage other users (limited to account created during onboarding)
Although it's possible to configure authentication, we stronlgy recommend to stick with the default authentication configuration. If you had auth providers configured in a previous Home Assistant release, we recommend to remove the configuration and start using the default.
It will take some time before all of the Home Assistant ecosystem has been migrated over to the new auth system. Home Assistant will print a warning whenever an application connects to Home Assistant with the legacy authentication. This will help users notify the application developers to transition to use the new [OAuth2](https://developers.home-assistant.io/docs/en/auth_api.html) authentication. For non-interactive scripts or other applications that are unable to update, we are planning to introduce a migration path for components to adopt url specific auth tokens and also introduce long lived access tokens to replace API passwords. A list of impacted components can be found [here](https://github.com/home-assistant/home-assistant/issues/15376#issuecomment-415890552).
Our [iOS app](/ios) will soon be updated to work with the new auth. It's already in testing. The old app will continue to work with the legacy API password support. It will however require a second login when using the webview.
If you are using a proxy server (NGINX etc) in front of Home Assistant to provide authentication, check [this blogpost](https://blog.ceard.tech/2018/08/turbulence-ahead-fasten-your-seatbelt.html) by [@DubhAd] how to make it work.
I want to say a biiiig thank you to all the people that have been involved in the development and testing of the new authentication system. It's been a big project and it's been great to see how we, as a community, have rallied together to tackle it. Especially a big shout out to [@awarecan] who has done an amazing job on this.
#### {% linkable_title Hangouts %}
And that's not it ! [@hobbypunk90] has contributed a new integration for [Google Hangouts][hangouts docs]. You can send messages but can also configure intents to handle incoming messages from specific people. Very cool!
#### {% linkable_title Lovelace %}
You didn't think we would forget about Lovelace, did you? This release include a new notification drawer thanks to [@jeradM]. It will collect all persistent notifications and configurator entities and shows it in a new sidebar toggleable from the toolbar.
## {% linkable_title New Platforms %}
- Netatmo public ([@colinfrei] - [#15684]) ([sensor.netatmo_public docs]) (new-platform)
- Add ecovacs component ([@OverloadUT] - [#15520]) ([ecovacs docs]) ([vacuum.ecovacs docs]) (new-platform)
- Add support for NOAA tide information (new PR) ([@jcconnell] - [#15947]) ([sensor.noaa_tides docs]) (new-platform)
- Hangouts ([@hobbypunk90] - [#16049]) ([hangouts docs]) ([notify docs]) (new-platform)
## {% linkable_title If you need help... %}
...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
## {% linkable_title Reporting Issues %}
Experiencing issues introduced by this release? Please report them in our [issue tracker](https://github.com/home-assistant/home-assistant/issues). Make sure to fill in all fields of the issue template.
<!--more-->
## {% linkable_title Breaking Changes %}
- Enable auth by default 🙈. It is no longer possible to access Home Assistant without authentication ([@balloob] - [#16107]) (breaking change)
- It's no longer possible to use a trusted network to connect to the websocket API. You need to get a token and use that to connect. ([@awarecan] - [#15812]) ([auth docs]) ([http docs]) ([websocket_api docs]) (breaking change)
- Script Syntax: The wait template will now continue to run the remainder of the script on timeout, the original functionality can be gained by setting `continue_on_timeout: false`. Allow wait template to run the remainder of the script ([@lhovo] - [#15836]) (breaking change)
- Update Xiaomi Vacuum to new StateVacuumDevice changed some services: `turn_on` -> `start`, `turn_off` -> `return_to_dock`, `toggle` has been removed. States 'on' and 'off' will also no longer be used. ([@cnrd] - [#15643]) (breaking change)
- Update neato to support new StateVacuumDevice changed some services: `turn_on` -> `start`, `turn_off` -> `return_to_dock`, `toggle` has been removed. States 'on' and 'off' will also no longer be used. ([@dshokouhi] - [#16035]) ([vacuum.neato docs]) (breaking change)
- The previously deprecated package `homeassistant.remote` has been removed. ([@balloob] - [#16099]) ([api docs]) ([http docs]) ([mqtt_eventstream docs]) ([mqtt_statestream docs]) ([notify docs]) ([splunk docs]) ([websocket_api docs]) (breaking change)
- Merge `insteon_plm` and `insteon_local` components to insteon component ([@teharris1] - [#16102]) (breaking change)
- Remove unit_of_measurement from climate entities ([@jeradM] - [#16012]) ([climate docs]) ([climate.generic_thermostat docs]) ([climate.knx docs]) ([climate.maxcube docs]) ([climate.sensibo docs]) (breaking change)
- Upnp component no longer enables port mapping by default ([@dgomes] - [#16108]) ([upnp docs]) (breaking change)
- The entity registry yaml file has been removed. It is now stored inside `.storage` and should only be managed via the UI ([@balloob] - [#16018])
## {% linkable_title Beta Fixes %}
- deCONZ - Support device registry ([@Kane610] - [#16115]) ([deconz docs]) ([binary_sensor.deconz docs]) ([light.deconz docs]) ([sensor.deconz docs]) ([switch.deconz docs]) (beta fix)
- Add multi-factor auth module setup flow ([@awarecan] - [#16141]) ([auth docs]) (beta fix)
- Decouple Konnected entity setup from discovery ([@heythisisnate] - [#16146]) ([konnected docs]) ([switch.konnected docs]) (beta fix)
- Device registry store config entry ([@Kane610] - [#16152]) (beta fix)
- fix error message for cv.matches_regex ([@heythisisnate] - [#16175]) (beta fix)
- Fix hangouts ([@balloob] - [#16180]) ([hangouts docs]) (beta fix)
- Tweak log level for bearer token warning ([@awarecan] - [#16182]) ([http docs]) (beta fix)
- Default load trusted_network auth provider if configured trusted networks ([@awarecan] - [#16184]) (beta fix)
- Replace pbkdf2 with bcrypt ([@Eriner] - [#16071]) (beta fix)
- Add Time-based Onetime Password Multi-factor Authentication Module ([@awarecan] - [#16129]) (beta fix)
- Handle exception from pillow ([@PhracturedBlue] - [#16190]) ([camera.proxy docs]) (beta fix)
- remove hangouts.users state, simplifies hangouts.conversations ([@hobbypunk90] - [#16191]) ([hangouts docs]) (beta fix)
- Update aiohttp to version 3.4.0. ([@Swamp-Ig] - [#16198]) (beta fix)
- Revert changes to platforms using self.device ([@Kane610] - [#16209]) (beta fix)
- homematic: Make device avilable again when UNREACH becomes False ([@klada] - [#16202]) ([homematic docs]) (beta fix)
- Change auth warning ([@balloob] - [#16216]) ([http docs]) (beta fix)
- rewrite hangouts to use intents instead of commands ([@hobbypunk90] - [#16220]) ([conversation docs]) ([hangouts docs]) (beta fix)
- Fix device telldus ([@balloob] - [#16224]) ([tellduslive docs]) (beta fix)
- Update trusted networks flow ([@balloob] - [#16227]) (beta fix)
- Fix hangouts ([@balloob] - [#16232]) ([hangouts docs]) (beta fix)
- Warning missed a space ([@balloob] - [#16233]) ([http docs]) (beta fix)
- Package loadable: compare case insensitive ([@balloob] - [#16234]) (beta fix)
- Avoid insecure pycryptodome ([@balloob] - [#16238]) (beta fix)
- Change log level to error when auth provider failed loading ([@awarecan] - [#16235]) (beta fix)
- Blow up startup if init auth providers or modules failed ([@awarecan] - [#16240]) (beta fix)
- Tweak MFA login flow ([@awarecan] - [#16254]) (beta fix)
- def device shouldnt call it self but self._device ([@Kane610] - [#16255]) ([media_player.plex docs]) (beta fix)
## {% linkable_title All changes %}
- Eph ember support operation modes ([@ttroy50] - [#15820]) ([climate.ephember docs])
- Fixed race condition in Generic Thermostat ([@aronsky] - [#15784]) ([climate.generic_thermostat docs])
- Fix magic cube support of the Aqara LAN Protocol V2 ([@syssi] - [#15940]) ([binary_sensor.xiaomi_aqara docs])
- Upgrade beautifulsoup4 to 4.6.3 ([@fabaff] - [#15946]) ([device_tracker docs]) ([sensor.geizhals docs]) ([sensor.scrape docs]) ([sensor.sytadin docs])
- Allow wait template to run the remainder of the script ([@lhovo] - [#15836]) (breaking change)
- Add trusted networks auth provider ([@awarecan] - [#15812]) ([auth docs]) ([http docs]) ([websocket_api docs]) (breaking change)
- Add monitored conditions for Unifi device_tracker ([@cgarwood] - [#15888]) ([device_tracker docs])
- Netatmo public ([@colinfrei] - [#15684]) ([sensor.netatmo_public docs]) (new-platform)
- Update Xiaomi Vacuum to new StateVacuumDevice ([@cnrd] - [#15643]) (breaking change)
- HomeMatic: Enable entity registry ([@danielperna84] - [#15950]) ([homematic docs])
- Fix google calendar documentation link. ([@cgtobi] - [#15968]) ([calendar.google docs])
- Remove unnecessary log ([@colinfrei] - [#15966]) ([sensor.netatmo_public docs])
- Make setup fail if location is not available ([@fabaff] - [#15967]) ([sensor.worldtidesinfo docs])
- Remove warning ([@balloob] - [#15969])
- Update waterfurnace library to 0.7, add reconnect logic ([@sdague] - [#15657]) ([waterfurnace docs])
- adds support for momentary and beep/blink switches ([@heythisisnate] - [#15973]) ([konnected docs]) ([switch.konnected docs])
- Add -j$(nproc) make option to speed up build time ([@vrih] - [#15928])
- Update Glances sensor ([@fabaff] - [#15981]) ([sensor.glances docs])
- Upgrade psutil to 5.4.7 ([@fabaff] - [#15982]) ([sensor.systemmonitor docs])
- Upgrade aladdin_connect to 0.3 and provide Unique ID ([@shoejosh] - [#15986]) ([cover.aladdin_connect docs])
- Entity service ([@balloob] - [#15991])
- More entity service ([@balloob] - [#15998]) ([camera docs]) ([climate docs])
- Wemo custom ports and network errors handling ([@mcspr] - [#14516]) ([wemo docs]) ([binary_sensor.wemo docs]) ([light.wemo docs]) ([switch.wemo docs])
- Clean up input-datetime ([@balloob] - [#16000]) ([input_datetime docs])
- BMW Connected drive: option to disable the services ([@Alexxander0] - [#15993]) ([bmw_connected_drive docs]) ([lock.bmw_connected_drive docs])
- Add type hints to homeassistant.auth ([@scop] - [#15853])
- Fix check config packages key error ([@MartinHjelmare] - [#15840])
- Update SoCo to 0.16 ([@amelchio] - [#16007]) ([sonos docs]) ([media_player.sonos docs])
- Upgrade sendgrid to 5.5.0 ([@fabaff] - [#16021]) ([notify docs])
- Split out storage delay save ([@balloob] - [#16017]) ([hassio docs])
- Disable assuming Optional type for values with None default ([@scop] - [#16029])
- Update RitAssist to support maximum speed and current address ([@depl0y] - [#16037]) ([device_tracker docs])
- Handle missing mpd capabilities ([@logic] - [#15945]) ([media_player.mpd docs])
- Storage entity registry ([@balloob] - [#16018])
- Attempt to fix flaky TTS test ([@balloob] - [#16025])
- Update neato to support new StateVacuumDevice ([@dshokouhi] - [#16035]) ([vacuum.neato docs]) (breaking change)
- vacuum/xiaomi_miio: Expose "sensor_dirty_left" attribute ([@klada] - [#16003]) ([vacuum.xiaomi_miio docs])
- Grammar and spelling fixes ([@scop] - [#16065])
- Use aiohttp web.AppRunner ([@balloob] - [#16020]) ([http docs])
- Update pushsafer.py ([@appzer] - [#16060]) ([notify docs])
- Alexa: context + log events ([@balloob] - [#16023]) ([alexa docs])
- openuv: Add Current UV Level to list of conditions ([@leppa] - [#16042]) ([openuv docs]) ([sensor.openuv docs])
- TpLink Device Tracker Error ([@TimBailey-pnk] - [#15918]) ([device_tracker docs])
- Deprecated stuff ([@balloob] - [#16019]) ([device_tracker docs]) ([websocket_api docs]) ([camera.push docs])
- Add recent context ([@balloob] - [#15989])
- Add ecovacs component ([@OverloadUT] - [#15520]) ([ecovacs docs]) ([vacuum.ecovacs docs]) (new-platform)
- Bumped NDMS2 client library to 0.0.4 to get compatible with python 3.5 ([@foxel] - [#16077]) ([device_tracker docs])
- fritzdect change to current_power_w ([@Danielhiversen] - [#16079]) ([switch.fritzdect docs])
- Update pyhomematic to 0.1.47 ([@danielperna84] - [#16083]) ([homematic docs])
- Get user after login flow finished ([@awarecan] - [#16047]) ([auth docs])
- Upgrade pytest to 3.7.2 ([@scop] - [#16091])
- Add verify ssl to generic camera ([@fliphess] - [#15949]) ([camera.generic docs])
- Upgrade afsapi to 0.0.4, prevents aiohttp session close message, Fixes #13099 ([@zhelev] - [#16098]) ([media_player.frontier_silicon docs])
- Remove homeassistant.remote ([@balloob] - [#16099]) ([api docs]) ([http docs]) ([mqtt_eventstream docs]) ([mqtt_statestream docs]) ([notify docs]) ([splunk docs]) ([websocket_api docs]) (breaking change)
- Use new session when fetching remote urls ([@balloob] - [#16093]) ([auth docs])
- Allow finish_flow callback to change data entry result type ([@awarecan] - [#16100])
- Add support for revoking refresh tokens ([@balloob] - [#16095]) ([auth docs])
- Refactoring login flow ([@awarecan] - [#16104])
- Minor updates ([@fabaff] - [#16106])
- Bump python-miio version ([@syssi] - [#16110]) ([device_tracker docs]) ([fan.xiaomi_miio docs]) ([light.xiaomi_miio docs]) ([remote.xiaomi_miio docs]) ([sensor.xiaomi_miio docs]) ([switch.xiaomi_miio docs]) ([vacuum.xiaomi_miio docs])
- homematic: Add homematic.put_paramset service ([@klada] - [#16024]) ([homematic docs])
- Upgrade shodan to 1.9.1 ([@fabaff] - [#16113]) ([sensor.shodan docs])
- Upgrade sendgrid to 5.6.0 ([@fabaff] - [#16111]) ([notify docs])
- Merge insteon_plm and insteon_local to insteon component ([@teharris1] - [#16102]) (breaking change)
- Remove unit_of_measurement from climate entities ([@jeradM] - [#16012]) ([climate docs]) ([climate.generic_thermostat docs]) ([climate.knx docs]) ([climate.maxcube docs]) ([climate.sensibo docs]) (breaking change)
- Add multi-factor authentication modules ([@awarecan] - [#15489]) ([config docs])
- Device Registry ([@Kane610] - [#15980])
- Check correctly if package is loadable ([@balloob] - [#16121])
- Upgrade numpy to 1.15.1 ([@fabaff] - [#16126]) ([binary_sensor.trend docs]) ([image_processing.opencv docs])
- Upgrade youtube_dl to 2018.08.22 ([@fabaff] - [#16125]) ([media_extractor docs])
- Fix the protocol v2 data_key of several aqara devices ([@syssi] - [#16112]) ([binary_sensor.xiaomi_aqara docs])
- Upgrade brunt package ([@eavanvalkenburg] - [#16130]) ([cover.brunt docs])
- Add support for NOAA tide information (new PR) ([@jcconnell] - [#15947]) ([sensor.noaa_tides docs]) (new-platform)
- Adds support for routers implementing IGDv2 ([@dgomes] - [#16108]) ([upnp docs]) (breaking change)
- Add support for JS modules in custom panels ([@squidwardy] - [#16096]) ([panel_custom docs])
- Prevent legacy api password with empty password ([@balloob] - [#16127])
- Enable auth by default 🙈 ([@balloob] - [#16107]) (breaking change)
- Remove commented out API password from default config ([@balloob] - [#16147])
- Spelling fixes ([@scop] - [#16150]) ([insteon_local docs]) ([insteon_plm docs])
- Update pydocstyle to 2.1.1 and flake8-docstrings to 1.3.0 ([@scop] - [#14557])
- Hangouts ([@hobbypunk90] - [#16049]) ([hangouts docs]) ([notify docs]) (new-platform)
- Hangouts localization typo fix ([@armills] - [#16174]) ([hangouts docs])
- deCONZ - Allow sub second light transitions ([@Kane610] - [#16170]) ([light.deconz docs])
- add_devices -> add_entities ([@balloob] - [#16171])
- deCONZ - Support device registry ([@Kane610] - [#16115]) ([deconz docs]) ([binary_sensor.deconz docs]) ([light.deconz docs]) ([sensor.deconz docs]) ([switch.deconz docs]) (beta fix)
- Add multi-factor auth module setup flow ([@awarecan] - [#16141]) ([auth docs]) (beta fix)
- Decouple Konnected entity setup from discovery ([@heythisisnate] - [#16146]) ([konnected docs]) ([switch.konnected docs]) (beta fix)
- Device registry store config entry ([@Kane610] - [#16152]) (beta fix)
- fix error message for cv.matches_regex ([@heythisisnate] - [#16175]) (beta fix)
- Fix hangouts ([@balloob] - [#16180]) ([hangouts docs]) (beta fix)
- Tweak log level for bearer token warning ([@awarecan] - [#16182]) ([http docs]) (beta fix)
- Default load trusted_network auth provider if configured trusted networks ([@awarecan] - [#16184]) (beta fix)
- Replace pbkdf2 with bcrypt ([@Eriner] - [#16071]) (beta fix)
- Add Time-based Onetime Password Multi-factor Authentication Module ([@awarecan] - [#16129]) (beta fix)
- Handle exception from pillow ([@PhracturedBlue] - [#16190]) ([camera.proxy docs]) (beta fix)
- remove hangouts.users state, simplifies hangouts.conversations ([@hobbypunk90] - [#16191]) ([hangouts docs]) (beta fix)
- Update aiohttp to version 3.4.0. ([@Swamp-Ig] - [#16198]) (beta fix)
- Revert changes to platforms using self.device ([@Kane610] - [#16209]) (beta fix)
- homematic: Make device avilable again when UNREACH becomes False ([@klada] - [#16202]) ([homematic docs]) (beta fix)
- Change auth warning ([@balloob] - [#16216]) ([http docs]) (beta fix)
- rewrite hangouts to use intents instead of commands ([@hobbypunk90] - [#16220]) ([conversation docs]) ([hangouts docs]) (beta fix)
- Fix device telldus ([@balloob] - [#16224]) ([tellduslive docs]) (beta fix)
- Update trusted networks flow ([@balloob] - [#16227]) (beta fix)
- Fix hangouts ([@balloob] - [#16232]) ([hangouts docs]) (beta fix)
- Warning missed a space ([@balloob] - [#16233]) ([http docs]) (beta fix)
- Package loadable: compare case insensitive ([@balloob] - [#16234]) (beta fix)
- Avoid insecure pycryptodome ([@balloob] - [#16238]) (beta fix)
- Change log level to error when auth provider failed loading ([@awarecan] - [#16235]) (beta fix)
- Blow up startup if init auth providers or modules failed ([@awarecan] - [#16240]) (beta fix)
- Tweak MFA login flow ([@awarecan] - [#16254]) (beta fix)
- def device shouldnt call it self but self._device ([@Kane610] - [#16255]) ([media_player.plex docs]) (beta fix)
[#14516]: https://github.com/home-assistant/home-assistant/pull/14516
[#14557]: https://github.com/home-assistant/home-assistant/pull/14557
[#15489]: https://github.com/home-assistant/home-assistant/pull/15489
[#15520]: https://github.com/home-assistant/home-assistant/pull/15520
[#15643]: https://github.com/home-assistant/home-assistant/pull/15643
[#15657]: https://github.com/home-assistant/home-assistant/pull/15657
[#15684]: https://github.com/home-assistant/home-assistant/pull/15684
[#15784]: https://github.com/home-assistant/home-assistant/pull/15784
[#15812]: https://github.com/home-assistant/home-assistant/pull/15812
[#15820]: https://github.com/home-assistant/home-assistant/pull/15820
[#15836]: https://github.com/home-assistant/home-assistant/pull/15836
[#15840]: https://github.com/home-assistant/home-assistant/pull/15840
[#15853]: https://github.com/home-assistant/home-assistant/pull/15853
[#15888]: https://github.com/home-assistant/home-assistant/pull/15888
[#15918]: https://github.com/home-assistant/home-assistant/pull/15918
[#15928]: https://github.com/home-assistant/home-assistant/pull/15928
[#15940]: https://github.com/home-assistant/home-assistant/pull/15940
[#15945]: https://github.com/home-assistant/home-assistant/pull/15945
[#15946]: https://github.com/home-assistant/home-assistant/pull/15946
[#15947]: https://github.com/home-assistant/home-assistant/pull/15947
[#15949]: https://github.com/home-assistant/home-assistant/pull/15949
[#15950]: https://github.com/home-assistant/home-assistant/pull/15950
[#15966]: https://github.com/home-assistant/home-assistant/pull/15966
[#15967]: https://github.com/home-assistant/home-assistant/pull/15967
[#15968]: https://github.com/home-assistant/home-assistant/pull/15968
[#15969]: https://github.com/home-assistant/home-assistant/pull/15969
[#15973]: https://github.com/home-assistant/home-assistant/pull/15973
[#15980]: https://github.com/home-assistant/home-assistant/pull/15980
[#15981]: https://github.com/home-assistant/home-assistant/pull/15981
[#15982]: https://github.com/home-assistant/home-assistant/pull/15982
[#15986]: https://github.com/home-assistant/home-assistant/pull/15986
[#15989]: https://github.com/home-assistant/home-assistant/pull/15989
[#15991]: https://github.com/home-assistant/home-assistant/pull/15991
[#15993]: https://github.com/home-assistant/home-assistant/pull/15993
[#15998]: https://github.com/home-assistant/home-assistant/pull/15998
[#16000]: https://github.com/home-assistant/home-assistant/pull/16000
[#16003]: https://github.com/home-assistant/home-assistant/pull/16003
[#16007]: https://github.com/home-assistant/home-assistant/pull/16007
[#16012]: https://github.com/home-assistant/home-assistant/pull/16012
[#16017]: https://github.com/home-assistant/home-assistant/pull/16017
[#16018]: https://github.com/home-assistant/home-assistant/pull/16018
[#16019]: https://github.com/home-assistant/home-assistant/pull/16019
[#16020]: https://github.com/home-assistant/home-assistant/pull/16020
[#16021]: https://github.com/home-assistant/home-assistant/pull/16021
[#16023]: https://github.com/home-assistant/home-assistant/pull/16023
[#16024]: https://github.com/home-assistant/home-assistant/pull/16024
[#16025]: https://github.com/home-assistant/home-assistant/pull/16025
[#16029]: https://github.com/home-assistant/home-assistant/pull/16029
[#16035]: https://github.com/home-assistant/home-assistant/pull/16035
[#16037]: https://github.com/home-assistant/home-assistant/pull/16037
[#16042]: https://github.com/home-assistant/home-assistant/pull/16042
[#16047]: https://github.com/home-assistant/home-assistant/pull/16047
[#16049]: https://github.com/home-assistant/home-assistant/pull/16049
[#16060]: https://github.com/home-assistant/home-assistant/pull/16060
[#16065]: https://github.com/home-assistant/home-assistant/pull/16065
[#16071]: https://github.com/home-assistant/home-assistant/pull/16071
[#16077]: https://github.com/home-assistant/home-assistant/pull/16077
[#16079]: https://github.com/home-assistant/home-assistant/pull/16079
[#16083]: https://github.com/home-assistant/home-assistant/pull/16083
[#16091]: https://github.com/home-assistant/home-assistant/pull/16091
[#16093]: https://github.com/home-assistant/home-assistant/pull/16093
[#16095]: https://github.com/home-assistant/home-assistant/pull/16095
[#16096]: https://github.com/home-assistant/home-assistant/pull/16096
[#16098]: https://github.com/home-assistant/home-assistant/pull/16098
[#16099]: https://github.com/home-assistant/home-assistant/pull/16099
[#16100]: https://github.com/home-assistant/home-assistant/pull/16100
[#16102]: https://github.com/home-assistant/home-assistant/pull/16102
[#16104]: https://github.com/home-assistant/home-assistant/pull/16104
[#16106]: https://github.com/home-assistant/home-assistant/pull/16106
[#16107]: https://github.com/home-assistant/home-assistant/pull/16107
[#16108]: https://github.com/home-assistant/home-assistant/pull/16108
[#16110]: https://github.com/home-assistant/home-assistant/pull/16110
[#16111]: https://github.com/home-assistant/home-assistant/pull/16111
[#16112]: https://github.com/home-assistant/home-assistant/pull/16112
[#16113]: https://github.com/home-assistant/home-assistant/pull/16113
[#16115]: https://github.com/home-assistant/home-assistant/pull/16115
[#16121]: https://github.com/home-assistant/home-assistant/pull/16121
[#16125]: https://github.com/home-assistant/home-assistant/pull/16125
[#16126]: https://github.com/home-assistant/home-assistant/pull/16126
[#16127]: https://github.com/home-assistant/home-assistant/pull/16127
[#16129]: https://github.com/home-assistant/home-assistant/pull/16129
[#16130]: https://github.com/home-assistant/home-assistant/pull/16130
[#16141]: https://github.com/home-assistant/home-assistant/pull/16141
[#16146]: https://github.com/home-assistant/home-assistant/pull/16146
[#16147]: https://github.com/home-assistant/home-assistant/pull/16147
[#16150]: https://github.com/home-assistant/home-assistant/pull/16150
[#16152]: https://github.com/home-assistant/home-assistant/pull/16152
[#16170]: https://github.com/home-assistant/home-assistant/pull/16170
[#16171]: https://github.com/home-assistant/home-assistant/pull/16171
[#16174]: https://github.com/home-assistant/home-assistant/pull/16174
[#16175]: https://github.com/home-assistant/home-assistant/pull/16175
[#16180]: https://github.com/home-assistant/home-assistant/pull/16180
[#16182]: https://github.com/home-assistant/home-assistant/pull/16182
[#16184]: https://github.com/home-assistant/home-assistant/pull/16184
[#16190]: https://github.com/home-assistant/home-assistant/pull/16190
[#16191]: https://github.com/home-assistant/home-assistant/pull/16191
[#16198]: https://github.com/home-assistant/home-assistant/pull/16198
[#16202]: https://github.com/home-assistant/home-assistant/pull/16202
[#16209]: https://github.com/home-assistant/home-assistant/pull/16209
[#16216]: https://github.com/home-assistant/home-assistant/pull/16216
[#16220]: https://github.com/home-assistant/home-assistant/pull/16220
[#16224]: https://github.com/home-assistant/home-assistant/pull/16224
[#16227]: https://github.com/home-assistant/home-assistant/pull/16227
[#16232]: https://github.com/home-assistant/home-assistant/pull/16232
[#16233]: https://github.com/home-assistant/home-assistant/pull/16233
[#16234]: https://github.com/home-assistant/home-assistant/pull/16234
[#16235]: https://github.com/home-assistant/home-assistant/pull/16235
[#16238]: https://github.com/home-assistant/home-assistant/pull/16238
[#16240]: https://github.com/home-assistant/home-assistant/pull/16240
[#16254]: https://github.com/home-assistant/home-assistant/pull/16254
[#16255]: https://github.com/home-assistant/home-assistant/pull/16255
[@Alexxander0]: https://github.com/Alexxander0
[@DubhAd]: https://github.com/DubhAd
[@Danielhiversen]: https://github.com/Danielhiversen
[@Eriner]: https://github.com/Eriner
[@Kane610]: https://github.com/Kane610
[@MartinHjelmare]: https://github.com/MartinHjelmare
[@OverloadUT]: https://github.com/OverloadUT
[@PhracturedBlue]: https://github.com/PhracturedBlue
[@Swamp-Ig]: https://github.com/Swamp-Ig
[@TimBailey-pnk]: https://github.com/TimBailey-pnk
[@amelchio]: https://github.com/amelchio
[@appzer]: https://github.com/appzer
[@armills]: https://github.com/armills
[@aronsky]: https://github.com/aronsky
[@awarecan]: https://github.com/awarecan
[@balloob]: https://github.com/balloob
[@cgarwood]: https://github.com/cgarwood
[@cgtobi]: https://github.com/cgtobi
[@cnrd]: https://github.com/cnrd
[@colinfrei]: https://github.com/colinfrei
[@danielperna84]: https://github.com/danielperna84
[@depl0y]: https://github.com/depl0y
[@dgomes]: https://github.com/dgomes
[@dshokouhi]: https://github.com/dshokouhi
[@eavanvalkenburg]: https://github.com/eavanvalkenburg
[@fabaff]: https://github.com/fabaff
[@fliphess]: https://github.com/fliphess
[@foxel]: https://github.com/foxel
[@heythisisnate]: https://github.com/heythisisnate
[@hobbypunk90]: https://github.com/hobbypunk90
[@jcconnell]: https://github.com/jcconnell
[@jeradM]: https://github.com/jeradM
[@klada]: https://github.com/klada
[@leppa]: https://github.com/leppa
[@lhovo]: https://github.com/lhovo
[@logic]: https://github.com/logic
[@mcspr]: https://github.com/mcspr
[@scop]: https://github.com/scop
[@sdague]: https://github.com/sdague
[@shoejosh]: https://github.com/shoejosh
[@squidwardy]: https://github.com/squidwardy
[@syssi]: https://github.com/syssi
[@teharris1]: https://github.com/teharris1
[@ttroy50]: https://github.com/ttroy50
[@vrih]: https://github.com/vrih
[@zhelev]: https://github.com/zhelev
[alexa docs]: /components/alexa/
[api docs]: /components/api/
[auth docs]: /components/auth/
[binary_sensor.deconz docs]: /components/binary_sensor.deconz/
[binary_sensor.trend docs]: /components/binary_sensor.trend/
[binary_sensor.wemo docs]: /components/binary_sensor.wemo/
[binary_sensor.xiaomi_aqara docs]: /components/binary_sensor.xiaomi_aqara/
[bmw_connected_drive docs]: /components/bmw_connected_drive/
[calendar.google docs]: /components/calendar.google/
[camera docs]: /components/camera/
[camera.generic docs]: /components/camera.generic/
[camera.proxy docs]: /components/camera.proxy/
[camera.push docs]: /components/camera.push/
[climate docs]: /components/climate/
[climate.ephember docs]: /components/climate.ephember/
[climate.generic_thermostat docs]: /components/climate.generic_thermostat/
[climate.knx docs]: /components/climate.knx/
[climate.maxcube docs]: /components/climate.maxcube/
[climate.sensibo docs]: /components/climate.sensibo/
[config docs]: /components/config/
[conversation docs]: /components/conversation/
[cover.aladdin_connect docs]: /components/cover.aladdin_connect/
[cover.brunt docs]: /components/cover.brunt/
[deconz docs]: /components/deconz/
[device_tracker docs]: /components/device_tracker/
[ecovacs docs]: /components/ecovacs/
[fan.xiaomi_miio docs]: /components/fan.xiaomi_miio/
[hangouts docs]: /components/hangouts/
[hassio docs]: /components/hassio/
[homematic docs]: /components/homematic/
[http docs]: /components/http/
[image_processing.opencv docs]: /components/image_processing.opencv/
[input_datetime docs]: /components/input_datetime/
[insteon_local docs]: /components/insteon_local/
[insteon_plm docs]: /components/insteon_plm/
[konnected docs]: /components/konnected/
[light.deconz docs]: /components/light.deconz/
[light.wemo docs]: /components/light.wemo/
[light.xiaomi_miio docs]: /components/light.xiaomi_miio/
[lock.bmw_connected_drive docs]: /components/lock.bmw_connected_drive/
[media_extractor docs]: /components/media_extractor/
[media_player.frontier_silicon docs]: /components/media_player.frontier_silicon/
[media_player.mpd docs]: /components/media_player.mpd/
[media_player.plex docs]: /components/media_player.plex/
[media_player.sonos docs]: /components/media_player.sonos/
[mqtt_eventstream docs]: /components/mqtt_eventstream/
[mqtt_statestream docs]: /components/mqtt_statestream/
[notify docs]: /components/notify/
[openuv docs]: /components/openuv/
[panel_custom docs]: /components/panel_custom/
[remote.xiaomi_miio docs]: /components/remote.xiaomi_miio/
[sensor.deconz docs]: /components/sensor.deconz/
[sensor.geizhals docs]: /components/sensor.geizhals/
[sensor.glances docs]: /components/sensor.glances/
[sensor.netatmo_public docs]: /components/sensor.netatmo_public/
[sensor.noaa_tides docs]: /components/sensor.noaa_tides/
[sensor.openuv docs]: /components/sensor.openuv/
[sensor.scrape docs]: /components/sensor.scrape/
[sensor.shodan docs]: /components/sensor.shodan/
[sensor.systemmonitor docs]: /components/sensor.systemmonitor/
[sensor.sytadin docs]: /components/sensor.sytadin/
[sensor.worldtidesinfo docs]: /components/sensor.worldtidesinfo/
[sensor.xiaomi_miio docs]: /components/sensor.xiaomi_miio/
[sonos docs]: /components/sonos/
[splunk docs]: /components/splunk/
[switch.deconz docs]: /components/switch.deconz/
[switch.fritzdect docs]: /components/switch.fritzdect/
[switch.konnected docs]: /components/switch.konnected/
[switch.wemo docs]: /components/switch.wemo/
[switch.xiaomi_miio docs]: /components/switch.xiaomi_miio/
[tellduslive docs]: /components/tellduslive/
[upnp docs]: /components/upnp/
[vacuum.ecovacs docs]: /components/vacuum.ecovacs/
[vacuum.neato docs]: /components/vacuum.neato/
[vacuum.xiaomi_miio docs]: /components/vacuum.xiaomi_miio/
[waterfurnace docs]: /components/waterfurnace/
[websocket_api docs]: /components/websocket_api/
[wemo docs]: /components/wemo/

BIN
source/images/blog/2018-08-0.77/social.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 29 KiB

BIN
source/images/docs/authentication/login.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 37 KiB

After

Width:  |  Height:  |  Size: 22 KiB

BIN
source/images/docs/authentication/mfa.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 43 KiB

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

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 4.3 KiB

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

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 28 KiB