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-22 16:56:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'rc' into current

Browse Source
This commit is contained in:
Franck Nijhof 2020-02-26 14:34:44 +01:00
commit 33d2d8ae37
No known key found for this signature in database
GPG Key ID: D62583BA8AB11CA3
94 changed files with 2345 additions and 419 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
CODEOWNERS
View File

@ -185,7 +185,6 @@ source/_integrations/lcn.markdown @alengwenus
source/_integrations/life360.markdown @pnbruckner
source/_integrations/linky.markdown @Quentame
source/_integrations/linux_battery.markdown @fabaff
source/_integrations/liveboxplaytv.markdown @pschmitt
source/_integrations/local_ip.markdown @issacg
source/_integrations/logger.markdown @home-assistant/core
source/_integrations/logi_circle.markdown @evanjd

6
_config.yml
View File

@ -100,9 +100,9 @@ social:
# Home Assistant release details
current_major_version: 0
current_minor_version: 105
current_patch_version: 5
date_released: 2020-02-17
current_minor_version: 106
current_patch_version: 0
date_released: 2020-02-26
# Either # or the anchor link to latest release notes in the blog post.
# Must be prefixed with a # and have double quotes around it.

2
source/_integrations/abode.markdown
View File

@ -31,7 +31,7 @@ There is currently support for the following device types within Home Assistant:
- **Cover**: Reports on `Secure Barriers` and can be used to open and close the cover.
- **Lock**: Reports on `Door Locks` and can be used to lock and unlock the door.
- [**Light**](/integrations/abode/#light): Reports on `Dimmer` lights and can be used to dim or turn the light on and off.
- [**Switch**](/integrations/abode/#switch): Reports on `Power Switch` devices and can be used to turn the power switch on and off. Also reports on `Automations` set up in the Abode system and allows you to activate or deactivate them (does not work with Abode's CUE automations).
- [**Switch**](/integrations/abode/#switch): Reports on `Power Switch` and `Water Valve` devices which can be used to turn the devices on and off. Also reports on `Automations` set up in the Abode system and allows you to activate or deactivate them (does not currently work with Abode's CUE automations).
- **Sensor**: Reports on `Temperature`, `Humidity`, and `Light` sensors.
## Configuration

2
source/_integrations/air_quality.xiaomi_miio.markdown
View File

@ -16,6 +16,8 @@ Currently, the supported features are:
- Attributes
- carbon_dioxide_equivalent
- total_volatile_organic_compounds
- temperature
- humidity
Please follow the instructions on [Retrieving the Access Token](/integrations/vacuum.xiaomi_miio/#retrieving-the-access-token) to get the API token.

19
source/_integrations/binary_sensor.modbus.markdown
View File

@ -18,20 +18,21 @@ To use your Modbus binary sensors in your installation, add the following to you
# Example configuration.yaml entry
binary_sensor:
- platform: modbus
coils:
inputs:
- name: Sensor1
hub: hub1
slave: 1
coil: 100
address: 100
- name: Sensor2
hub: hub1
slave: 1
coil: 110
address: 110
input_type: discrete_input
```
{% configuration %}
coils:
description: The array contains a list of coils to read from.
inputs:
description: The array contains a list of coils and discrete inputs to read from.
required: true
type: [map, list]
keys:
@ -48,10 +49,14 @@ coils:
description: The number of the slave (Optional for TCP and UDP Modbus).
required: true
type: integer
coil:
description: Coil number.
address:
description: Coil or discrete input Modbus address.
required: true
type: integer
input_type:
description: Modbus input type (coil, discrete_input), default coil.
required: false
type: string
device_class:
description: The [type/class](/integrations/binary_sensor/#device-class) of the binary sensor to set the icon in the frontend.
required: false

6
source/_integrations/blockchain.markdown
View File

@ -1,6 +1,6 @@
---
title: Blockchain.info
description: Instructions on how to integrate Blockchain.info data within Home Assistant.
title: Blockchain.com
description: Instructions on how to integrate Blockchain.com data within Home Assistant.
logo: blockchain.png
ha_category:
- Finance
@ -8,7 +8,7 @@ ha_release: 0.47
ha_iot_class: Cloud Polling
---
The `Blockchain` sensor platform displays Bitcoin wallet balances from [blockchain.info](https://blockchain.info).
The `Blockchain` sensor platform displays Bitcoin wallet balances from [blockchain.com](https://blockchain.com).
To add the Blockchain sensor to your installation, specify a list of bitcoin addresses to watch in the `configuration.yaml` file. The sensor state will be the sum of the balances of all addresses listed.

5
source/_integrations/climate.modbus.markdown
View File

@ -56,6 +56,11 @@ current_temp_register:
description: Register number for current temperature (Process value).
required: true
type: integer
current_temp_register_type:
description: Modbus register type (holding, input) for current temperature, default holding.
required: false
type: string
default: holding
data_type:
description: Response representation (int, uint, float, custom). If float selected, value will converted to IEEE 754 floating point format.
required: false

18
source/_integrations/cover.mqtt.markdown
View File

@ -12,8 +12,8 @@ The `mqtt` cover platform allows you to control an MQTT cover (such as blinds, a
## Configuration
The device state (`open` or `closed`) will be updated only after a new message is published on `state_topic` matching `state_open` or `state_closed`. If these messages are published with the `retain` flag set, the cover will receive an instant state update after subscription and Home Assistant will display the correct state on startup. Otherwise, the initial state displayed in Home Assistant will be `unknown`.
`state_topic` can only manage `state_open` and `state_closed`. No percentage positions etc.
The device state (`open`, `opening`, `closed` or `closing`) will be updated only after a new message is published on `state_topic` matching `state_open`, `state_opening`, `state_closed` or `state_closing`. If these messages are published with the `retain` flag set, the cover will receive an instant state update after subscription and Home Assistant will display the correct state on startup. Otherwise, the initial state displayed in Home Assistant will be `unknown`.
`state_topic` can only manage `state_open`, `state_opening`, `state_closed` and `state_closing`. No percentage positions etc.
For this purpose is `position_topic` which can set state of the cover and position.
Default setting are 0 means the device is `closed` and all other intermediate positions means the device is `open`.
@ -70,11 +70,21 @@ state_open:
required: false
type: string
default: open
state_opening:
description: The payload that represents the opening state.
required: false
type: string
default: opening
state_closed:
description: The payload that represents the closed state.
required: false
type: string
default: closed
state_closing:
description: The payload that represents the closing state.
required: false
type: string
default: closing
position_topic:
description: The MQTT topic subscribed to receive cover position messages. If `position_topic` is set `state_topic` is ignored.
required: false
@ -242,7 +252,9 @@ cover:
payload_close: "CLOSE"
payload_stop: "STOP"
state_open: "open"
state_opening: "opening"
state_closed: "closed"
state_closing: "closing"
payload_available: "online"
payload_not_available: "offline"
optimistic: false
@ -297,7 +309,9 @@ cover:
payload_close: "CLOSE"
payload_stop: "STOP"
state_open: "open"
state_opening: "opening"
state_closed: "closed"
state_closing: "closing"
payload_available: "online"
payload_not_available: "offline"
optimistic: false

28
source/_integrations/derivative.markdown
View File

@ -12,7 +12,8 @@ ha_codeowners:
- '@afaucogney'
---
The `derivative` platform provides the numerical derivative or numerical differentiation of the values provided by a source sensor. Derivative sensors are updated upon changes of the **source**. Fast sampling source sensors provide better results.
The `derivative` platform creates a sensor that estimates the derivative of the values provided by a source sensor.
Derivative sensors are updated upon changes of the **source**.
## Configuration
@ -41,7 +42,7 @@ round:
default: 3
type: integer
unit_prefix:
description: Metric unit to prefix the derivative result. Available units are k, M, G, T.
description: Metric unit to prefix the derivative result ([Wikipedia](https://en.wikipedia.org/wiki/Unit_prefix)]). Available symbols are "n" (1e-9), "µ" (1e-6), "m" (1e-3), "k" (1e3), "M" (1e6), "G" (1e9), "T" (1e12).
required: false
default: None
type: string
@ -54,6 +55,27 @@ unit:
description: Unit of Measurement to be used for the derivative.
required: false
type: string
time_window:
description: The time window in which to calculate the derivative. This is useful for sensor that output discrete values. By default the derivative is calculated between two consecutive updates.
default: 0
required: false
type: time
{% endconfiguration %}
If 'unit' is set then 'unit_prefix' and 'unit_time' are ignored.
## Temperature example
For example, you have a temperature sensor `sensor.temperature` that outputs a value every few seconds, but rounds to the nearest half number.
That means that two consecutive output values might be the same (so the derivative is `Δy/Δx=0` because `Δy=0` !)
However, the temperature might actually be changing over time.
In order to capture this, you should use a `time_window`, such that immediate jumps don't result in high derivatives and that after the next sensor update, the derivatives doesn't vanish to zero.
An example configuration that uses `time_window` is
```yaml
sensor:
- platform: derivative
source: sensor.temperature
name: Temperature change per hour
round: 1
unit_time: h
time_window: "00:30:00" # we look at the change over the last half hour
```

21
source/_integrations/dsmr.markdown
View File

@ -10,7 +10,7 @@ ha_iot_class: Local Push
A sensor platform for Dutch Smart Meters which comply to DSMR (Dutch Smart Meter Requirements), also known as 'Slimme meter' or 'P1 poort'.
- Currently support DSMR V2.2, V3, V4 and V5 through the [dsmr_parser](https://github.com/ndokter/dsmr_parser) module by Nigel Dokter.
- Currently support DSMR V2.2, V3, V4, V5 and V5 Belgian through the [dsmr_parser](https://github.com/ndokter/dsmr_parser) module by Nigel Dokter.
- For official information about DSMR refer to: [DSMR Document](https://www.netbeheernederland.nl/dossiers/slimme-meter-15)
- For official information about the P1 port refer to: <https://www.netbeheernederland.nl/_upload/Files/Slimme_meter_15_a727fce1f1.pdf>
- For unofficial hardware connection examples refer to: [Domoticx](http://domoticx.com/p1-poort-slimme-meter-hardware/)
@ -35,6 +35,7 @@ USB serial converters:
- <https://sites.google.com/site/nta8130p1smartmeter/webshop>
- <https://www.sossolutions.nl/slimme-meter-kabel>
- <https://tweakers.net/gallery/269738/aanbod/>
- <https://nl.aliexpress.com/item/32945187155.html>
Serial to network proxies:
@ -60,7 +61,7 @@ sensor:
required: false
type: string
dsmr_version:
description: "Version of DSMR used by meter. Choices: 2.2, 4, 5. Defaults to 2.2."
description: "Version of DSMR used by meter. Choices: 2.2, 4, 5, 5B (For Belgian Meter). Defaults to 2.2."
required: false
type: string
precision:
@ -83,10 +84,10 @@ group:
meter_readings:
name: Meter readings
entities:
- sensor.power_consumption_low
- sensor.power_consumption_normal
- sensor.power_production_low
- sensor.power_production_normal
- sensor.energy_consumption_tarif_1
- sensor.energy_consumption_tarif_2
- sensor.energy_production_tarif_1
- sensor.energy_production_tarif_2
- sensor.gas_consumption
```
@ -102,10 +103,10 @@ group:
meter_readings:
name: Meter readings
entities:
- sensor.power_consumption_low
- sensor.power_consumption_normal
- sensor.power_production_low
- sensor.power_production_normal
- sensor.energy_consumption_tarif_1
- sensor.energy_consumption_tarif_2
- sensor.energy_production_tarif_1
- sensor.energy_production_tarif_2
- sensor.gas_consumption
```

44
source/_integrations/duke_energy.markdown
View File

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

149
source/_integrations/dynalite.markdown Executable file
View File

@ -0,0 +1,149 @@
---
title: "Philips Dynalite"
description: "Instructions on setting up Philips Dynalite within Home Assistant."
logo: dynalite.png
ha_category:
- Hub
- Light
ha_iot_class: Local Push
ha_release: 0.106
---
Philips Dynalite support is integrated into Home Assistant as a hub that can drive the light platforms.
There is currently support for the following device types within Home Assistant:
- Lights
A Philips Dynalite hub connects to the Dynet network, which is composed of areas, channels, and preset.
A Dynalite area typically (although not necessarily) defines some physical area, such as a room.
Each area can have one or more channels that correspond to the different devices they control. A channel can relate to a dimmable light, or other devices, such as a cover.
Additionally, each area can have one or more presets that determine the behavior of all the channels, and sometimes trigger additional actions. Typically, preset 1 in an area means 'on', and preset '4' means off. Additional presets could be used for scenes and dimming.
## Configuration
Since Philips Dynalite has virtually no auto-discover capabilities, it needs to be configured via the `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
dynalite:
bridges:
- host: DEVICE_IP_ADDRESS
```
{% configuration %}
host:
description: The IP address of the bridge (e.g., 192.168.1.10).
required: true
type: string
port:
description: Port number of the bridge.
required: false
type: integer
default: 12345
name:
description: Name for the bridge.
required: false
type: string
default: dynalite
active:
description: Actively query network. When starting, it will query all devices for their current status, and also will send queries when some changes are in progress (e.g., lights dimming or covers moving). Better experience but creates more load on the Dynalite network.
required: false
type: boolean
default: false
polltimer:
description: Polling interval for devices in transition. Value in seconds. When devices are in transition (e.g., a light fading), it will ask for a new state every X seconds until it is at the target level. Only relevant when active is set.
required: false
type: float
default: 1.0
autodiscover:
description: Enable auto-discover. As Dynalite does not support autodiscovery, this tracks event on your network, so if you turn on a light, it will be added to Home Assistant.
required: false
type: boolean
default: false
default:
description: Global defaults for the system
required: false
type: map
keys:
fade:
description: Default fade
required: false
type: float
area:
description: Definition for the various Dynalite areas.
required: true
type: map
keys:
'AREA_NUMBER':
description: The Dynalite area number, 1-255.
required: true
type: map
keys:
name:
description: Name of the area.
required: true
type: string
fade:
description: Fade time for the area, in seconds.
required: false
type: float
default: 2.0
channel:
description: Map of the channels in this area.
required: false
type: map
keys:
'CHANNEL_NUMBER':
description: The Dynalite channel number in the area, 1-255.
required: true
type: map
keys:
name:
description: Name of the channel.
required: false
type: string
default: \"AREA_NAME Channel CHANNEL_NUMBER\"
fade:
description: Fade time for the channel, in seconds.
required: false
type: float
default: 2.0
{% endconfiguration %}
## Examples
```yaml
# Example configuration.yaml entry specifying optional parameters
dynalite:
bridges:
- host: DEVICE_IP_ADDRESS
port: 12345
autodiscover: true
polltimer: 1
areacreate: auto
log_level: debug
area:
'2':
name: Living Room
channel:
'2':
name: Entrance Spot
fade: 10.0
'3':
name: Dining Table
```
## Initial configuration and discovery
Maybe the most difficult thing about a Dynalite system is finding out the areas and channel mapping. If you have them or have access to the Dynalite software and your configuration files, this could be easy,
but in the likely case that your system was installed by an integrator, you will have to discover them on your own.
This is where the `autodiscover` option comes handy. If it is on, the component will track the Dynet network and every time a device is used, it will be added to Home Assistant. It will initially show as "Area 123 Channel 7", but you can then add it to your `configuration.yaml` with the correct configuration.
For example, you would go to your kitchen light and turn it on. Now you log into Home Assistant and see what the channel was. If there was more than one discovered (e.g., someone turned off the living room lights), you can try one, turn it on and off in Home Assistant and see which light it affects.
The initial process can be a bit time consuming and tedious, but it only has to be done once. Once you are done configuring, it is better to set `autodiscover` to `false`, since there are many "fake" channels and areas that the system uses for internal communication and you do not want to have visible.

11
source/_integrations/eight_sleep.markdown
View File

@ -17,11 +17,11 @@ The `eight_sleep` integration allows Home Assistant to fetch data from your [Eig
There is currently support for the following device types within Home Assistant:
- Binary Sensor - lets observe the presence state of a [Eight Sleep](https://eightsleep.com/) cover/mattress through Home Assistant.
- Sensor - This includes bed state and results of the current and previous sleep sessions.
- Sensor - This includes bed state, sleep fitness scores, and results of the current and previous sleep sessions.
## Configuration
It's setup utilizing 'Sensor' platform to convey the current state of your bed and results of your sleep sessions and a 'Binary Sensor' platform to indicate your presence in the bed. A service is also provided to set the heating level and duration of the bed.
It's setup utilizing 'Sensor' platform to convey the current state of your bed and results of your sleep sessions and a 'Binary Sensor' platform to indicate your presence in the bed. A service is also provided to set the cooling/heating level and duration of the bed (cooling is only available for the POD mattress).
You must have at least two sleep sessions recorded in the Eight Sleep app prior to setting up the Home Assistant component.
@ -55,6 +55,7 @@ partner:
Sensors:
- eight_left/right_bed_state
- eight left/right_sleep_fitness
- eight_left/right_sleep_session
- eight_left/right_previous_sleep_session
- eight_left/right_bed_temperature
@ -67,13 +68,13 @@ Binary Sensors:
### Service `heat_set`
You can use the service eight_sleep/heat_set to adjust the target heating level and heating duration of your bed.
You can use the service eight_sleep/heat_set to adjust the target cooling/heating level and heating duration of your bed (cooling is only available for the POD mattress).
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
| `entity_id` | no | Entity ID of bed state to adjust.
| `target` | no | Target heating level from 0-100.
| `duration` | no | Duration to heat at the target level in seconds.
| `target` | no | Target cooling/heating level from -100 to 100.
| `duration` | no | Duration to cool/heat at the target level in seconds.
Script Example:

53
source/_integrations/fritzdect.markdown
View File

@ -1,53 +0,0 @@
---
title: AVM FRITZ!DECT
description: Instructions on how to integrate your AVM FRITZ!DECT switches into Home Assistant.
logo: avm.png
ha_category:
- Switch
ha_iot_class: Local Polling
ha_release: 0.38
---
The `fritzdect` switch platform allows you to control the state of your [AVM FRITZ!DECT DECT-based wireless switches](https://en.avm.de/products/fritzdect/). The AVM FRITZ!DECT switches need to be paired to your FRITZ!Box and then can be monitored and controlled via Home Assistant.
Supported devices (tested):
- FRITZ!DECT 200
Supported Firmwares (tested):
- FRITZ!OS: 06.80 / FRITZ!DECT: 03.83
- FRITZ!OS: 06.98-51288 (Beta) / FRITZ!DECT: 03.87
- FRITZ!OS: 7.01 / FRITZ!DECT: 04.09
To use your AVM FRITZ!DECT switch(es) in your installation, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
switch:
- platform: fritzdect
username: YOUR_USERNAME
password: YOUR_PASSWORD
```
{% configuration %}
username:
description: The username for your Fritz!Box.
required: true
type: string
password:
description: The password for your Fritz!Box.
required: true
type: string
host:
description: The IP address/hostname of your Fritz!Box.
required: false
type: string
default: fritz.box
{% endconfiguration %}
It is recommended to create a dedicated user for Home Assistant and only allow access to "Smart Home".
<div class='note warning'>
If this integration throws an error when starting home-assistant you should check if all actors are plugged in and connected to the FritzBox. Inactive actors that are not deleted from FritzBox configuration might lead to errors.
</div>

6
source/_integrations/garmin_connect.markdown
View File

@ -65,9 +65,6 @@ Body Battery Most Recent
Average SPO2
Lowest SPO2
Latest SPO2
Highest Respiration
Lowest Respiration
Latest Respiration
```
Disabled by default:
@ -104,4 +101,7 @@ Moderate Intensity
Vigorous Intensity
Intensity Goal
Latest Respiration Update
Highest Respiration
Lowest Respiration
Latest Respiration
```

136
source/_integrations/gdacs.markdown Normal file
View File

@ -0,0 +1,136 @@
---
title: Global Disaster Alert and Coordination System (GDACS)
description: Instructions on how to integrate the Global Disaster Alert and Coordination System (GDACS) feed into Home Assistant.
logo: gdacs.jpg
ha_category:
- Geolocation
ha_iot_class: Cloud Polling
ha_release: 0.106
ha_config_flow: true
ha_quality_scale: platinum
ha_codeowners:
- '@exxamalte'
---
The `gdacs` integration lets you use a GeoRSS feed provided by
[GDACS](https://www.gdacs.org/) with information
about major droughts, earthquakes, floods, tropical cyclones, tsunamis and
volcanic activities worldwide.
It retrieves alerts from a feed and shows information of those alerts filtered
by distance to Home Assistant's location.
Entities are generated, updated and removed automatically with each update
from the feed. Each entity defines latitude and longitude and will be shown
on the default map automatically, or on a map card by defining the source
`gdacs`. The distance is available as the state of each entity, and
converted to the unit (kilometers or miles) configured in Home Assistant.
<p class='img'>
<img src='/images/screenshots/gdacs-alerts-feed-map.png' />
</p>
The data is updated every 5 minutes.
<div class='note'>
The material used by this integration is provided by the [Global Disaster
Alert and Coordination System (GDACS)](https://www.gdacs.org/) - a cooperation
framework between the United Nations and the European Commission - under the
[Creative Commons Attribution 4.0 International (CC BY 4.0) license](http://creativecommons.org/licenses/by/4.0/).
It has only been modified for the purpose of presenting the material in Home Assistant.
Please refer to the [creator's disclaimer and terms of use notice](https://www.gdacs.org/About/termofuse.aspx) for more information.
</div>
## Configuration
To integrate the GDACS feed use the "Integrations" feature
in the GUI, you find it under Configurations - Integrations, or add the
following line to your `configuration.yaml`.
```yaml
# Example configuration.yaml entry
gdacs:
```
{% configuration %}
categories:
description: The categories of alerts to be included. Valid categories are 'Drought', 'Earthquake', 'Flood', 'Tropical Cyclone', 'Tsunami', 'Volcano'.
required: false
type: list
radius:
description: The radius around your location to monitor; defaults to 500 km or mi (depending on the unit system defined in your `configuration.yaml`).
required: false
type: float
default: 500.0
latitude:
description: Latitude of the coordinates around which alerts are considered.
required: false
type: float
default: Latitude defined in your configuration.
longitude:
description: Longitude of the coordinates around which alerts are considered.
required: false
type: float
default: Longitude defined in your configuration.
{% endconfiguration %}
## State Attributes
The following state attributes are available for each entity in addition to
the standard ones:
| Attribute | Description |
|------------------|-------------|
| latitude | Latitude of the alert's location. |
| longitude | Longitude of the alert's location. |
| source | `gdacs` to be used in conjunction with `geo_location` automation trigger. |
| external_id | The external ID used in the feed to identify the alert. |
| title | Title of this entry. |
| description | Description of this entry. |
| event type | Type of event this alert is for (Drought, Earthquake, Flood, Tropical Cyclone, Tsunami, Volcano). |
| alert level | Alert level (Red, Orange, Green). |
| country | Country that the alert is applicable to. |
| duration in week | Duration of the alert in full weeks (only shown if more than one week). |
| from date | Date and time this alert started. |
| to date | Date and time this alert ended (or now if ongoing). |
| population | Exposed population. |
| severity | Severity of the alert. |
| vulnerability | Vulnerability score (textual or numerical). |
Please note that some of the attribute values depend on the context and may not
be comparable between different event types.
## Sensor
This integration automatically creates a sensor that shows how many entities
are currently managed by this integration. In addition to that the sensor has
some useful attributes that indicate the currentness of the data retrieved
from the feed.
<p class='img'>
<img src='/images/screenshots/gdacs-alerts-sensor.png' />
</p>
| Attribute | Description |
|------------------------|-------------|
| status | Status of last update from the feed ("OK" or "ERROR"). |
| last update | Timestamp of the last update from the feed. |
| last update successful | Timestamp of the last successful update from the feed. |
| last timestamp | Timestamp of the latest entry from the feed. |
| created | Number of entities that were created during last update (optional). |
| updated | Number of entities that were updated during last update (optional). |
| removed | Number of entities that were removed during last update (optional). |
## Full Configuration
```yaml
# Example configuration.yaml entry
gdacs:
categories:
- Drought
- Earthquake
radius: 1000
latitude: -41.2
longitude: 174.7
```

19
source/_integrations/geo_location.markdown
View File

@ -13,15 +13,16 @@ Entities can have associated geolocation coordinates (latitude and longitude) so
The [Geolocation trigger](/docs/automation/trigger/#geolocation-trigger) can be used in automations triggered by Geolocation entities appearing in or disappearing from zones. The following value must be used as `source` of the trigger depending on which platform is managing the entities:
| Platform | Source |
|---------------------------------------------------|-------------------------------|
| GeoJSON Events | `geo_json_events` |
| GeoNet New Zealand Quakes | `geonetnz_quakes` |
| IGN Sismología | `ign_sismologia` |
| NSW Rural Fire Service Incidents | `nsw_rural_fire_service_feed` |
| Queensland Bushfire Alert | `qld_bushfire` |
| U.S. Geological Survey Earthquake Hazards Program | `usgs_earthquakes_feed` |
| The World Wide Lightning Location Network | `wwlln` |
| Platform | Source |
|-------------------------------------------------------|-------------------------------|
| GeoJSON Events | `geo_json_events` |
| GeoNet New Zealand Quakes | `geonetnz_quakes` |
| Global Disaster Alert and Coordination System (GDACS) | `gdacs` |
| IGN Sismología | `ign_sismologia` |
| NSW Rural Fire Service Incidents | `nsw_rural_fire_service_feed` |
| Queensland Bushfire Alert | `qld_bushfire` |
| U.S. Geological Survey Earthquake Hazards Program | `usgs_earthquakes_feed` |
| The World Wide Lightning Location Network | `wwlln` |
Conditions can be used to further filter entities, for example by inspecting their state attributes.

13
source/_integrations/glances.markdown
View File

@ -90,11 +90,12 @@ version:
## Integration Entities
Glances integration will add the following sensors:
Glances integration will add the following sensors if available in the platform:
- disk_use_percent: The used disk space in percent.
- disk_use: The used disk space.
- disk_free: The free disk space.
- For each detected disk (or mount point) the following sensors will be created:
- disk_use_percent: The used disk space in percent.
- disk_use: The used disk space.
- disk_free: The free disk space.
- memory_use_percent: The used memory in percent.
- memory_use: The used memory.
- memory_free: The free memory.
@ -107,9 +108,9 @@ Glances integration will add the following sensors:
- process_thread: The number of threads.
- process_sleeping: The number of sleeping processes.
- cpu_use_percent: The used CPU in percent.
- cpu_temp: The CPU temperature (may not be available on all platforms).
- sensor_temp: A temperature sensor for each device that provides temperature (depends on platform).
- docker_active: The count of active Docker containers.
- docker_cpu_use: The total CPU usage in percent of Docker containers.
- docker_memory_use: The total memory used by Docker containers.
Not all platforms are able to provide all metrics. For instance `cpu_temp` requires installing and configuring `lmsensors` in Ubuntu, and may not be available at all in other platforms.
Not all platforms are able to provide all metrics. For instance the cpu temp sensor requires installing and configuring `lmsensors` in Ubuntu, and may not be available at all in other platforms.

22
source/_integrations/homematicip_cloud.markdown
View File

@ -90,7 +90,7 @@ Within this delay the device registration should be completed in the App, otherw
* homematicip_cloud.binary_sensor
* Acceleration Sensor (*HMIP-SAM*)
* Window and door contact (*HmIP-SWDO, -I*)
* Window and door contact (*HmIP-SWDO, HmIP-SWDO-PL, HmIP-SWDO-I, HmIP-SWDM, HmIP-SWDM-B2*)
* Contact Interface flush-mount – 1 channel (*HmIP-FCI1*)
* Contact Interface (*HmIP-SCI*)
* Window Rotary Handle Sensor (*HmIP-SRH*)
@ -111,11 +111,13 @@ Within this delay the device registration should be completed in the App, otherw
* homematicip_cloud.climate
* Climate group (*HmIP-HeatingGroup*)
* This includes temperature/humidity measures for climate devices of a room delivered by:
* Wall-mounted thermostat (*HmIP-WTH, WTH-2*)
* Brand Wall-mounted thermostat (*HmIP-BWTH, BWTH-24*)
* Radiator thermostat (*HmIP-eTRV,-2,-C*) - should also work with (*HmIP-eTRV-2-UK, -B, -B1*)
* Wall-mounted thermostat (*HmIP-WTH, HmIP-WTH-2, HmIP-WTH-B*)
* Brand Wall-mounted thermostat (*HmIP-BWTH, HmIP-BWTH-24*)
* Radiator thermostat (*HmIP-eTRV, HmIP-eTRV-2, HmIP-eTRV-C*) - should also work with (*HmIP-eTRV-2-UK, HmIP-eTRV-2-B, HmIP-eTRV-2-B1*)
* Temperature and humidity sensor (*HmIP-STH*)
* Temperature and humidity Sensor with display (*HmIP-STHD*)
* Alpha IP Wall Thermostat Display (*ALPHA-IP-RBG*)
* Alpha IP Wall Thermostat Display analog (*ALPHA-IP-RBGa*)
* There is no need to directly support the following devices by Home Assistant, because their integration is done by the required wall thermostats:
* Floor Heating Actuator – 6x channels, 230V (*HMIP-FAL230-C6*)
* Floor Heating Actuator – 10x channels, 230V (*HMIP-FAL230-C10*)
@ -138,9 +140,9 @@ Within this delay the device registration should be completed in the App, otherw
* Switch Actuator for brand switches – with signal lamp (*HmIP-BSL*)
* homematicip_cloud.sensor
* Cloud Access point duty-cycle (*HmIP-HAP, -B1*)
* Wall Mounted Thermostat Pro with Display (*HmIP-WTH, WTH2*)
* Radiator thermostat (*HmIP-eTRV,-2, -C*) - should also work with (*HmIP-eTRV-2-UK, -B, -B1*)
* Cloud Access point duty-cycle (*HmIP-HAP, HmIP-HAP-B1*)
* Wall Mounted Thermostat (*HmIP-WTH, HmIP-WTH2, HmIP-WTH-B*)
* Radiator thermostat (*HmIP-eTRV, HmIP-eTRV-2, HmIP-eTRV-C*) - should also work with (*HmIP-eTRV-2-UK, HmIP-eTRV-2-B, HmIP-eTRV-2-B1*)
* Temperature and Humidity Sensor without display - indoor (*HmIP-STH*)
* Temperature and Humidity Sensor with display - indoor (*HmIP-STHD*)
* Temperature and Humidity sensor - outdoor (*HmIP-STHO, -A*)
@ -149,11 +151,13 @@ Within this delay the device registration should be completed in the App, otherw
* Presence Sensor – indoor (*HmIP-SPI*)
* Light Sensor - outdoor (*HmIP-SLO*)
* Passage Sensor with Direction Recognition (*HmIP-SPDR*) (delta counter)
* Alpha IP Wall Thermostat Display (*ALPHA-IP-RBG*)
* Alpha IP Wall Thermostat Display analog (*ALPHA-IP-RBGa*)
* homematicip_cloud.switch
* Pluggable Switch (*HmIP-PS*)
* Pluggable Switch and Meter (*HmIP-PSM*) - should also work with (*HmIP-PSM-CH, -IT, -UK, -PE*)
* Switch Actuator and Meter – flush-mount (*HmIP-FSM, -FSM16*)
* Pluggable Switch and Meter (*HmIP-PSM*) - should also work with (*HmIP-PSM-CH, HmIP-PSM-IT, HmIP-PSM-UK, HmIP-PSM-PE*)
* Switch Actuator and Meter – flush-mount (*HmIP-FSM, HmIP-FSM16*)
* Open Collector Module Receiver - 8x (*HmIP-MOD-OC8*)
* Multi IO Box - 2x (*HmIP-MIOB*)
* Switch Circuit Board - 1x channels (*HmIP-PCBS*)

5
source/_integrations/ipma.markdown
View File

@ -40,4 +40,9 @@ longitude:
required: false
type: string
default: Home Assistant global longitude configuration
mode:
description: "The forecast type. Can be `hourly` or `daily`."
required: false
type: string
default: "`daily`"
{% endconfiguration %}

1
source/_integrations/jewish_calendar.markdown
View File

@ -60,6 +60,7 @@ havdalah_minutes_after_sunset:
- weekly_portion: Shows the weekly portion (parshat hashavu'a).
- holiday: If it is a holiday, shows the name of the holiday _(see below for more info)_.
- omer_count: An integer sensor indicating the day of the Omer (1-49) or 0 if it is not currently the Omer.
- daf_yomi: Shows the date's daf yomi page.
### Time sensors

31
source/_integrations/konnected.markdown
View File

@ -12,7 +12,7 @@ ha_codeowners:
- '@heythisisnate'
---
The `konnected` integration lets you connect wired sensors and switches to a NodeMCU ESP8226 based device running the [open source Konnected software](https://github.com/konnected-io/konnected-security). Reuse the wired sensors and siren from an old or pre-wired alarm system installation and integrate them directly into Home Assistant.
The `konnected` integration lets you connect wired sensors and switches to a Konnected Alarm Panel, or NodeMCU ESP8226 based device running the [open source Konnected software](https://github.com/konnected-io/konnected-security). Reuse the wired sensors and siren from an old or pre-wired alarm system installation and integrate them directly into Home Assistant.
Visit the [Konnected.io website](https://konnected.io) for more information about the Konnected Alarm Panel board and compatible hardware.
@ -22,7 +22,7 @@ The integration currently supports the following device types in Home Assistant:
- Switch: Actuate a siren, strobe, buzzer or relay module.
- Sensor: Periodic measurements from DHT temperature/humidity sensors and DS18B20 temperature sensors.
This integration uses the [`discovery`](/integrations/discovery) component, which must be enabled for device discovery to work. If you don't want to use discovery, set the _host_ and _port_ for each device in the description.
This integration uses the [SSDP](/integrations/ssdp) integration, which must be enabled for device discovery to work. If you don't want to use discovery, set the _host_ and _port_ for each device in the description.
<div class='note info'>
@ -32,7 +32,13 @@ Konnected devices communicate with Home Assistant over your local LAN -- there i
## Configuration
A `konnected` section must be present in the `configuration.yaml` file that specifies the Konnected devices on the network and the sensors or actuators attached to them:
Home Assistant offers Konnected integration through **Configuration** -> **Integrations** -> **Konnected.io**.
The configuration flow will guide you through a setup process that lets you connect to the panel and generate a configuration entry. You can then utilize the options flow to configure or modify the behavior of each zone.
If you prefer you can also utilize a `konnected` section in the `configuration.yaml` file that specifies the Konnected devices on the network and the sensors or actuators attached to them. If using `configuration.yaml` the configuration will automatically be imported and used to start a configuration flow. **Note that you must still complete the configuration/options flow before the configuration entry will be finalized.**
Details of the configuration fields and values can be found below - these apply to both the configuration flow and the YAML.
```yaml
# Example configuration.yaml entry
@ -69,7 +75,7 @@ devices:
type: list
keys:
id:
description: The MAC address of the NodeMCU Wi-Fi module with colons/punctuation removed, for example `68c63a8bcd53`. You can usually find the mac address in your router's client list. Or, check the home-assistant.log for log messages from automatically discovered devices.
description: The MAC address of the Konnected device with colons/punctuation removed, for example, `68c63a8bcd53`. You can usually find the mac address in your router's client list. Or, check the `home-assistant.log` for log messages from automatically discovered devices.
required: true
type: string
binary_sensors:
@ -78,10 +84,10 @@ devices:
type: list
keys:
pin:
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`.
description: See [Configuration Notes](#configuration-notes).
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: See [Configuration Notes](#configuration-notes).
required: exclusive
type:
description: Any [binary sensor](/integrations/binary_sensor/) class, typically `door`, `window`, `motion` or `smoke`.
@ -101,10 +107,10 @@ devices:
type: list
keys:
pin:
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 for sensors are `1`, `2`, `5`, `6`, `7` and `9`.
description: See [Configuration Notes](#configuration-notes).
required: exclusive
zone:
description: The number corresponding to the labeled zone on the [Konnected Alarm Panel](https://konnected.io) board. Valid values for sensors are `1`, `2`, `3`, `4`, `5` and `6`.
description: See [Configuration Notes](#configuration-notes).
required: exclusive
name:
description: The name of the device used in the front end.
@ -124,10 +130,10 @@ devices:
type: list
keys:
pin:
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.
description: See [Configuration Notes](#configuration-notes).
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: See [Configuration Notes](#configuration-notes).
required: exclusive
name:
description: The name of the device used in the front end.
@ -169,8 +175,11 @@ devices:
### Configuration Notes
- Either **pin** or **zone** is required for each actuator or sensor. Do not use both in the same definition.
- Either `pin` or `zone` is required for each actuator or sensor. Do not use both in the same definition.
- `pin` represents 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`, `8`, and `9`. Pin based configuration is only allowed with ESP8266 based devices.
- Pin `D8` or the `out` zone will only work when activation is set to high (the default).
- `zone` represents the value corresponding to the labeled zone on the [Konnected Alarm Panel](https://konnected.io) boards. Valid zone values are `1`, `2`, `3`, `4`, `5`, `6`, and `out` for the Konnected Alarm Panel (`out` represents the dedicated ALARM/OUT terminal) and `1`, `2`, `3`, `4`, `5`, `6`, `7`, `8`, `9`, `10`, `11`, `12`, `out1`, `alarm1`, and `alarm2_out2` for the Konnected Alarm Panel Pro.
- **The Konnected Alarm Panel Pro does not support configuration via `pin`.**
## Extended Configuration

25
source/_integrations/lg_netcast.markdown
View File

@ -5,7 +5,7 @@ logo: lg.png
ha_category:
- Media Player
ha_iot_class: Local Polling
ha_release: '0.20'
ha_release: 0.20
---
The `lg_netcast` platform allows you to control a LG Smart TV running NetCast 3.0 (LG Smart TV models released in 2012) and NetCast 4.0 (LG Smart TV models released in 2013). For the new LG WebOS TV's use the [webostv](/integrations/webostv#media-player) platform.
@ -16,7 +16,7 @@ To add a LG TV to your installation, add the following to your `configuration.ya
# Example configuration.yaml entry
media_player:
- platform: lg_netcast
host: 192.168.0.20
host: IP_ADDRESS
```
{% configuration %}
@ -33,6 +33,10 @@ name:
required: false
default: LG TV Remote
type: string
turn_on_action:
description: Defines an [action](/docs/automation/action/) to turn the TV on.
required: false
type: string
{% endconfiguration %}
To get the access token for your TV configure the `lg_netcast` platform in Home Assistant without the `access_token`.
@ -40,5 +44,20 @@ After starting Home Assistant the TV will display the access token on screen.
Just add the token to your configuration and restart Home Assistant and the media player integration for your LG TV will show up.
<div class='note'>
The access token will not change until you factory reset your TV.
The access token will not change until you factory reset your TV.
</div>
## Advanced configuration
The example below shows how you can use the `turn_on_action`
```yaml
# Example configuration.yaml entry
media_player:
- platform: lg_netcast
host: 192.168.0.20
turn_on_action:
service: switch.turn_on
data:
entity_id: switch.tv_switch
```

7
source/_integrations/light.markdown
View File

@ -36,6 +36,8 @@ Most lights do not support all attributes. You can check the integration documen
| `color_name` | yes | A human-readable string of a color name, such as `blue` or `goldenrod`. All [CSS3 color names](https://www.w3.org/TR/css-color-3/#svg-color) are supported.
| `brightness` | yes | Integer between 0 and 255 for how bright the light should be, where 0 means the light is off, 1 is the minimum brightness and 255 is the maximum brightness supported by the light.
| `brightness_pct`| yes | Alternatively, you can specify brightness in percent (a number between 0 and 100), where 0 means the light is off, 1 is the minimum brightness and 100 is the maximum brightness supported by the light.
| `brightness_step` | yes | Change brightness by an amount. Should be between -255..255.
| `brightness_step_pct` | yes | Change brightness by a percentage. Should be between -100..100.
| `flash` | yes | Tell light to flash, can be either value `short` or `long`.
| `effect`| yes | Applies an effect such as `colorloop` or `random`.
@ -87,7 +89,6 @@ Turns one or multiple lights off.
### Service `light.toggle`
Toggles the state of one or multiple lights using [groups]({{site_root}}/integrations/group/).
Takes the same arguments as [`turn_on`](#service-lightturn_on) service.
Toggles the state of one or multiple lights. Takes the same arguments as [`turn_on`](#service-lightturn_on) service.
*Note*: If `light.toggle` is used for a group of lights, it will toggle the individual state of each light.
*Note*: If `light.toggle` is used for a group of lights, it will toggle the individual state of each light. If you want the lights to be treated as a single light, use [Light Groups](/integrations/light.group/) instead.

19
source/_integrations/light.template.markdown
View File

@ -28,6 +28,7 @@ light:
level_template: "{{ state_attr('sensor.theater_brightness', 'lux')|int }}"
value_template: "{{ state_attr('sensor.theater_brightness', 'lux')|int > 0 }}"
temperature_template: "{{states('input_number.temperature_input') | int}}"
color_template: "({{states('input_number.h_input') | int}}, {{states('input_number.s_input') | int}})"
turn_on:
service: script.theater_lights_on
turn_off:
@ -41,6 +42,15 @@ light:
data_template:
value: "{{ color_temp }}"
entity_id: input_number.temperature_input
set_color:
- service: input_number.set_value
data_template:
value: "{{ h }}"
entity_id: input_number.h_input
- service: input_number.set_value
data_template:
value: "{{ s }}"
entity_id: input_number.s_input
```
{% endraw %}
@ -74,6 +84,11 @@ light:
required: false
type: template
default: optimistic
color_template:
description: Defines a template to get the color of the light. Must render a tuple (hue, saturation)
required: false
type: template
default: optimistic
icon_template:
description: Defines a template for an icon or picture, e.g., showing a different icon for different states.
required: false
@ -99,6 +114,10 @@ light:
description: Defines an action to run when the light is given a color temperature command.
required: false
type: action
set_color:
description: Defines an action to run when the light is given a color command.
required: false
type: action
{% endconfiguration %}
## Considerations

54
source/_integrations/liveboxplaytv.markdown
View File

@ -1,54 +0,0 @@
---
title: Orange Livebox Play TV
description: Instructions on how to integrate a Livebox Play TV appliance into Home Assistant.
logo: orange.png
ha_category:
- Media Player
ha_release: 0.38
ha_iot_class: Local Polling
ha_codeowners:
- '@pschmitt'
---
The `liveboxplaytv` platform allows you to control [Orange Livebox Play TV appliances](https://boutique.orange.fr/internet/decodeur-tv-livebox).
## Configuration
To add an Orange Livebox Play TV to your installation, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
media_player:
- platform: liveboxplaytv
host: 192.168.1.3
```
{% configuration %}
host:
description: The IP address or hostname of the Orange Livebox Play TV appliance.
required: true
type: string
name:
description: The name to use in the frontend.
required: false
default: "`Livebox Play TV`"
type: string
port:
description: The port on which the Livebox is listening on.
required: false
default: 8080
type: integer
{% endconfiguration %}
## Full configuration
A full configuration example for an Orange TV appliance can look like this:
```yaml
# Example configuration.yaml entry
media_player:
- platform: liveboxplaytv
host: 192.168.1.3
port: 8080
name: Orange Livebox Play TV
```

66
source/_integrations/melcloud.markdown Normal file
View File

@ -0,0 +1,66 @@
---
title: MELCloud
description: MELCloud integration
logo: melcloud.png
ha_category:
- Climate
ha_release: 0.106
ha_iot_class: Cloud Polling
ha_config_flow: true
ha_codeowners:
- '@vilppuvuorinen'
---
The `melcloud` integration integrates Mitsubishi Electric's [MELCloud](https://www.melcloud.com/) enabled devices into Home Assistant.
## Device support
- Air-to-Air heat pumps, e.g., AC units - **Supported**
- Air-to-Water heat pumps - **Work in progress**
- Energy recovery ventilators - **Not supported**
- Other - **Not supported**
## Configuration
The integration should be configured through the user interface ("Configurations -> Integrations") using the MELCloud login details. While not optimal, **the provided password is not stored**.
An expired token needs to be updated manually by adding the MELCloud integration again with the same email address.
Configuration is also possible through `configuration.yaml`. The required authentication token can be found in `X-MitsContextKey` header when logged into the MELCloud. The language needs to be set to English and the "Remember me" option needs to be selected.
```yaml
melcloud:
username: xxxx@xxxxxxx
token: xxxxxxxxxxxxxxxxxxx
```
{% configuration %}
username:
description: Email address used to login to MELCloud
required: true
type: string
token:
description: X-MitsContextKey access token
required: true
type: string
{% endconfiguration %}
## Air-to-Air device
An Air-to-Air heat pump provides `climate` and `sensor` platforms. Device capabilities can limit the available parameters and sensors.
### Climate
The following parameters can be controlled for the `climate` platform entities:
- Power (using HVAC mode)
- Target temperature
- Operation mode (HVAC mode)
- Fan speed
### Sensor
The following attributes are available for `sensor` platform entities:
- Room temperature
- Energy - The total consumed energy in kWh. **Not supported by all models.**

79
source/_integrations/meteo_france.markdown
View File

@ -5,24 +5,35 @@ logo: meteo-france.png
ha_release: 0.89
ha_iot_class: Cloud Polling
ha_category:
- Hub
- Sensor
- Weather
ha_codeowners:
- '@victorcerutti'
- '@oncleben31'
- '@Quentame'
ha_config_flow: true
---
The `meteo_france` integration uses the [Météo-France](http://www.meteofrance.com/) web service as a source for meteorological data for your location. The location is based on the `city` configured in your `configuration.yaml` file.
There is currently support for the following device types within Home Assistant:
There is currently support for the following platforms within Home Assistant:
- Sensor
- [Sensor](#sensor)
- Weather
It displays the current weather along with a 4 days forecast and can create sensors based on the `monitored_conditions` set in your `configuration.yaml` file, including weather alerts from [Vigilance Météo-France](https://vigilance.meteofrance.com/)
It displays the current weather along with a 4 days forecast and create sensors, including weather alerts from [Vigilance Météo-France](https://vigilance.meteofrance.com/)
## Configuration
## Setup the integration
There are two ways to integrate Météo-France in Home Assistant.
### Via the frontend
Menu: *Configuration* -> *Integrations*
Search for "Météo-France", add your city, click submit, you are done!
### Via the configuration file
To add Météo-France to your installation, add the following to your `configuration.yaml` file:
@ -34,34 +45,9 @@ meteo_france:
{% configuration %}
city:
description: Name of the city ([see below](#about-city-configuration)).
description: French postal code or name of the city ([see below](#about-city-configuration)).
required: true
type: string
monitored_conditions:
description: The conditions types to monitor.
required: true
type: list
keys:
temperature:
description: The current temperature.
weather:
description: A human-readable text summary of the current conditions.
wind_speed:
description: The wind speed.
uv:
description: The current UV index.
next_rain:
description: Time to the next rain if happening for the next hour ([see note below](#about-next_rain-condition-sensor)).
freeze_chance:
description: Probability of temperature below 0°C for the day.
rain_chance:
description: Probability of rain for the day.
snow_chance:
description: Probability of snow for the day.
thunder_chance:
description: Probability of thunderstorm for the day.
weather_alert:
description: Weather alert status.
{% endconfiguration %}
### About `city` configuration
@ -81,6 +67,20 @@ meteo_france:
- city: 'montreal,amerique'
```
## Sensor
All these sensors will be created :
- `temperature`: The current temperature.
- `weather`: A human-readable text summary of the current conditions.
- `wind_speed`: The wind speed.
- `uv`: The current UV index.
- `next_rain`: Time to the next rain if happening for the next hour ([see note below](#about-next_rain-condition-sensor)).
- `freeze_chance`: Probability of temperature below 0°C for the day.
- `rain_chance`: Probability of rain for the day.
- `snow_chance`: Probability of snow for the day.
- `thunder_chance`: Probability of thunderstorm for the day.
- `weather_alert`: Weather alert status ([see note below](#about-weather_alert-sensor)).
### About `next_rain` condition sensor
<div class='note warning'>
@ -113,25 +113,12 @@ The sensor attributes give access to each type of alerts and date of the bulleti
### Complete example
This is an example for 3 cities forecast with different monitored conditions:
This is an example for 3 cities forecast:
```yaml
# Complete example configuration.yaml entry
meteo_france:
- city: '69004'
- city: 'Rouen'
monitored_conditions:
- rain_chance
- freeze_chance
- thunder_chance
- snow_chance
- weather
- next_rain
- wind_speed
- temperature
- uv
- weather_alert
- city: 'Oslo, norvege'
monitored_conditions:
- temperature
- city: '51100'
```

41
source/_integrations/minecraft_server.markdown Normal file
View File

@ -0,0 +1,41 @@
---
title: Minecraft Server
description: Instructions on how to integrate a Minecraft server into Home Assistant.
logo: minecraft.png
ha_release: 0.106
ha_category:
- Binary Sensor
- Sensor
ha_iot_class: Local Polling
ha_quality_scale: silver
ha_config_flow: true
ha_codeowners:
- '@elmurato'
---
Minecraft servers allow players to play the sandbox video game [Minecraft](https://www.minecraft.net) by [Mojang AB](https://www.mojang.com) online or via a local area network with other players. The `Minecraft Server` integration lets you retrieve information from a Minecraft server (Java edition) within Home Assistant.
<div class='note'>
The server must be version 1.7 or higher, since older versions don't expose any information.
</div>
## Configuration via the frontend
In the settings go to `Integrations`, click on the `+` sign to add an integration and click on **Minecraft Server**.
After completing the configuration flow, the Minecraft Server integration will be available.
## Binary sensors
This integration provides a binary sensor for the following information from a Minecraft server:
- Connection status
## Sensors
This integration provides sensors for the following information from a Minecraft server:
- Latency time
- Version
- Protocol version
- Number of online players (player names are available in state attributes)
- Number of maximum players

25
source/_integrations/nederlandse_spoorwegen.markdown
View File

@ -29,6 +29,10 @@ sensor:
from: Gn
to: Mt
via: Zl
- name: 'AlmereBuiten-Duivendrecht-the-08h06m-train'
from: Almb
to: Dvd
time: '08:06:00'
```
{% configuration %}
@ -57,8 +61,27 @@ routes:
description: A station the route needs to pass through.
required: false
type: string
time:
description: Optional time to search for a specific train.
required: false
type: time
{% endconfiguration %}
The data are coming from [Nederlandse Spoorwegen](https://www.ns.nl/).
### Station codes
Station codes must be used and can be looked up [here](https://nl.wikipedia.org/wiki/Lijst_van_spoorwegstations_in_Nederland).
### Searching a specific train vs. the next train
The default behavior (without configuration variable `time`) gives you the information about the *next* train that fits the criteria (`from`, `to`, `via`).
When using the configuration variable `time`, you can search for a specific train.
This is convenient when searching for the next train doesn't give you enough time to base an automation on.
E.g., when you normally take the 08h06m train and want to get information about this train, but there is another train
that's departing just minutes before your train, your time window to warn you on a delay might be too small.
Using `time` only updates the route sensor during a time window around the chosen time.
Outside this window, the route sensor's state is `unknown`.
The window is from half an hour before the chosen time until half an hour after the chosen time.
In this way, you can have multiple routes with specific trains before hitting the FUP threshold for using NS API.
The data are coming from [Nederlandse Spoorwegen](https://www.ns.nl/).

110
source/_integrations/onewire.markdown
View File

@ -10,56 +10,60 @@ ha_codeowners:
- '@garbled1'
---
The `onewire` platform supports sensors which are using the One wire (1-wire) bus for communication.
The `onewire` platform supports sensors which that using the One wire (1-wire) bus for communication.
Supported devices:
Every 1-wire device has a (globally) unique ID that identifies the device on the bus. The first two digits identify a device family and the last 14 digits are a globally unique number given to it during manufacturing.
- [DS18B20](https://datasheets.maximintegrated.com/en/ds/DS18B20.pdf)
- [DS18S20](https://www.maximintegrated.com/en/products/sensors/DS18S20.html)
- [DS1822](https://datasheets.maximintegrated.com/en/ds/DS1822.pdf)
- [DS1825](https://datasheets.maximintegrated.com/en/ds/DS1825.pdf)
- [DS28EA00](https://datasheets.maximintegrated.com/en/ds/DS28EA00.pdf) temperature sensors
- [DS2406/TAI-8570](https://datasheets.maximintegrated.com/en/ds/DS2406.pdf) Temperature and pressure sensor made by AAG
- [DS2438/B1-R1-A](https://datasheets.maximintegrated.com/en/ds/DS2438.pdf) Temperature, pressure and humidity sensor by AAG
Different families have different functionality and can measure different quantities.
The 1-Wire bus can be connected directly to the IO pins of Raspberry Pi or using dedicated interface adapter (e.g [DS9490R](https://datasheets.maximintegrated.com/en/ds/DS9490-DS9490R.pdf)).
### Supported devices:
## Raspberry Pi setup
| Family | Device | Physical Quantity |
| -------|:-----|:-----|
| 10 | [DS18S20](https://www.maximintegrated.com/en/products/sensors/DS18S20.html) | Temperature |
| 12 | [DS2406(TAI-8570)](https://datasheets.maximintegrated.com/en/ds/DS2406.pdf) | Temperature (pressure when using TAI-8570) |
| 1D | [DS2423](https://datasheets.maximintegrated.com/en/ds/DS2423.pdf) | Counter |
| 22 | [DS1822](https://datasheets.maximintegrated.com/en/ds/DS1822.pdf) | |
| 26 | [DS2438/B1-R1-A/S2-R1-A](https://datasheets.maximintegrated.com/en/ds/DS2438.pdf)| Temperature, Voltage, Current, (pressure and humidity when using TAI-8570) |
| 28 | [DS18B20](https://datasheets.maximintegrated.com/en/ds/DS18B20.pdf) | Temperature |
| 3B | [DS1825](https://datasheets.maximintegrated.com/en/ds/DS1825.pdf) | Temperature |
| 42 | [DS28EA00](https://datasheets.maximintegrated.com/en/ds/DS28EA00.pdf) | Temperature |
| EF | [HobbyBoard](https://hobbyboards.com/) | Temperature, Humidity, Moisture |
Notes:
- The TAI-8570 Pressure Sensor is based on a 1-wire composite device by AAG Electronica. It contains, above 1-wire components, also a barometer, hygrometer and illuminance sensors. This onewire platform can read and present values from that device.
- Each 1-wire component data sheet describes the different properties the component provides. The owfs software adds some extra tools to make it easier for DIY implementers to use the component. By hobbyists, it is quite common to use DS2438 Smart Battery Monitor as a multipurpose measurement node that can place temperature, humidity and luminosity on the 1-wire bus by just adding some standard components to the DS2438. For different component types, there are ready-made algorithms implemented in owfs. Those are exposed by the owfs software and can be read by this platform. The B1-R1-A/pressure is exposed as a barometric pressure sensor. S2-R1-A/illuminance is presented as an illuminance sensor. For a more detailed description of these properties, refer to the [owfs documentation](https://owfs.org/index_php_page_ds2438.html).
For this component, the more basic quantities temperature, VAD, VDD and IAD is exported as separate sensors.
- Hobbyboards is a company that has been selling DIY boards of different kinds. The company has been away from the market for some time, so no reference to the boards can be made. This platform has an implementation for some of those.
## Interfacing with the 1-wire bus
The 1-Wire bus can be connected directly to the IO pins of Raspberry Pi or by using a dedicated interface adapter, for example
[DS9490R](https://datasheets.maximintegrated.com/en/ds/DS9490-DS9490R.pdf) or adapters based on [DS2482-100](https://datasheets.maximintegrated.com/en/ds/DS2482-100.pdf) that can be directly attached to the IO pins on the Raspberry Pi.
It is also possible for this platform to interface with a remote 1-wire host over a network connection using ofws and owserver.
## Raspberry Pi set up
In order to setup 1-Wire support on Raspberry Pi, you'll need to edit `/boot/config.txt` following [this documentation](https://www.waveshare.com/wiki/Raspberry_Pi_Tutorial_Series:_1-Wire_DS18B20_Sensor#Enable_1-Wire).
To edit `/boot/config.txt` on the Home Assistant Operating System, use [this documentation](https://developers.home-assistant.io/docs/en/hassio_debugging.html) to enable SSH and edit `/mnt/boot/config.txt` via `vi`.
When using the GPIO pins on Raspberry Pi directly as a 1-wire bus, the description above uses two kernel modules. `1w_gpio`, that implements the 1-wire protocol, and `1w_therm`, that understands the DS18B20 (family 28) components inner structure and reports temperature.
There is no support for other device types (families) and hence this onewire platform only supports temperature measurements from family 28 devices.
## Interface adapter setup
### owfs
When an interface adapter is used, sensors can be accessed on Linux hosts via [owfs 1-Wire file system](https://owfs.org/). When using an interface adapter and the owfs, the `mount_dir` option must be configured to correspond a directory, where owfs device tree has been mounted.
When an interface adapter is used, sensors can be accessed on Linux hosts via [owfs 1-Wire file system](https://owfs.org/). When using an interface adapter and the owfs, the `mount_dir` option must be configured to correspond to a directory, where owfs device tree has been mounted. On systems where Home Assistant runs in a Docker container. `owfs` cannot escape that environment and hence cannot populate the `mount_dir`. Use the owserver method on these systems instead.
### owserver
When an interface adapter is used, you can also access sensors on a remote or local Linux host that is running owserver. owserver by default runs on port 4304. Use the `host` option to specify the host or IP of the remote server, and the optional `port` option to change the port from the default.
### Units with multiple sensors
This platform works with devices with multiple sensors which will cause a discontinuity in recorded values. Existing devices will receive a new ID and therefore show up as new devices.
If you wish to maintain continuity it can be resolved in the database by renaming the old devices to the new names.
Connect to your database using the instructions from [Database section](/docs/backend/database/). Check the names of sensors:
```sql
SELECT entity_id, COUNT(*) as count FROM states GROUP BY entity_id ORDER BY count DESC LIMIT 10;
```
Alter the names of sensors using the following examples:
```sql
UPDATE states SET entity_id='sensor.<sensor_name>_temperature' WHERE entity_id LIKE 'sensor.<sensor_name>%' AND attributes LIKE '%\u00b0C%';
UPDATE states SET entity_id='sensor.<sensor_name>_pressure' WHERE entity_id LIKE 'sensor.<sensor_name>%' AND attributes LIKE '%mb%';
UPDATE states SET entity_id='sensor.<sensor_name>_humidity' WHERE entity_id LIKE 'sensor.<sensor_name>%' AND attributes LIKE '%%%' ESCAPE '';
```
Remember to replace `<sensor_name>` with the actual name of the sensor as seen in the `SELECT` query.
## Configuration
To enable One wire sensors in your installation, add the following to your `configuration.yaml` file:
@ -80,7 +84,7 @@ mount_dir:
required: false
type: string
host:
description: Remote or local host running owserver.
description: Remote or localhost running owserver.
required: false
type: string
port:
@ -101,3 +105,41 @@ sensor:
names:
GENERATED_ID: FRIENDLY_NAME
```
### Entities and attributes
Upon startup of the platform, the 1-wire bus is searched for available 1-wire devices. For each device that this platform handles (see list of supported devices above), the platform adds one sensor for each physical quantity it measures. The name of the sensor is the device ID with the physical quantity it measures appended.
`sensor.28.FF5C68521604_temperature`
Each sensor will present its value in the state variable and for presentation purposes, rounded to one decimal for analog values and as integers for counts.
Each sensor also exposes some additional attributes.
```alpha
device_file: /28.FF5C68521604/temperature << Device path in owfs file system (or on Rpi system directory)
raw_value: 31.9375 << The raw measurement numbers as red from device. Not rounded.
unit_of_measurement: °C
friendly_name: 28.FF5C68521604 Temperature
```
### Units with multiple sensors
This platform works with devices with multiple sensors, which will cause a discontinuity in recorded values. Existing devices will receive a new ID and therefore show up as new devices.
If you wish to maintain continuity, it can be resolved in the database by renaming the old devices to the new names.
Connect to your database using the instructions from [Database section](/docs/backend/database/). Check the names of sensors:
```sql
SELECT entity_id, COUNT(*) as count FROM states GROUP BY entity_id ORDER BY count DESC LIMIT 10;
```
Alter the names of sensors using the following examples:
```sql
UPDATE states SET entity_id='sensor.<sensor_name>_temperature' WHERE entity_id LIKE 'sensor.<sensor_name>%' AND attributes LIKE '%\u00b0C%';
UPDATE states SET entity_id='sensor.<sensor_name>_pressure' WHERE entity_id LIKE 'sensor.<sensor_name>%' AND attributes LIKE '%mb%';
UPDATE states SET entity_id='sensor.<sensor_name>_humidity' WHERE entity_id LIKE 'sensor.<sensor_name>%' AND attributes LIKE '%%%' ESCAPE '';
```
Remember to replace `<sensor_name>` with the actual name of the sensor, as seen in the `SELECT` query.

21
source/_integrations/pioneer.markdown
View File

@ -121,3 +121,24 @@ sources:
'MHL': '48'
'Game': '49'
```
#### VSX-528
```yaml
port: 8102
sources:
'CD': '01'
'Tuner': '02'
'DVD': '04'
'TV': '05'
'Sat/Cbl': '06'
'DVR/BDR': '15'
'iPod/USB': '17'
'HDMI/MHL': '48'
'BD': '25'
'Adapter': '33'
'Netradio': '38'
'Media Server': '44'
'Favorites': '45'
'Game': '49'
```

8
source/_integrations/plex.markdown
View File

@ -89,6 +89,11 @@ media_player:
required: false
default: false
type: boolean
ignore_new_shared_users:
description: Do not track Plex clients for newly added Plex users.
required: false
default: false
type: boolean
{% endconfiguration %}
```yaml
@ -102,12 +107,15 @@ plex:
media_player:
use_episode_art: true
show_all_controls: false
ignore_new_shared_users: false
```
## Media Player
The `plex` media_player platform will create Media Player entities for each connected client device. These entities will display media information, playback progress, and playback controls if supported by the device.
By default the Plex integration will create Media Player entities for all local, managed, and shared users on the Plex server. To choose specific users to monitor or ignore, select them via the Configuration Options (**Integrations** -> **Configured** --> **Plex** --> **Gear Icon**).
### Service `play_media`
Plays a song, playlist, TV episode, or video on a connected client.

13
source/_integrations/rainforest_eagle.markdown
View File

@ -1,6 +1,6 @@
---
title: Rainforest Eagle-200
description: Instructions on how to setup the Rainforest Eagle-200 with Home Assistant.
title: "Rainforest Eagle"
description: "Instructions on how to setup the Rainforest Eagle with Home Assistant."
logo: rainforest_automation_logo.png
ha_category:
- Energy
@ -11,7 +11,8 @@ ha_codeowners:
- '@gtdiehl'
---
A `sensor` platform for the [Rainforest Eagle-200](https://rainforestautomation.com/rfa-z114-eagle-200/) energy gateway.
A `sensor` platform for the Rainforest Automation's [Eagle-200](https://rainforestautomation.com/rfa-z114-eagle-200/)
and [Legacy Eagle](https://rainforestautomation.com/support/rfa-z109-eagle-support/) energy gateways.
## Configuration
@ -28,15 +29,15 @@ sensor:
{% configuration %}
ip_address:
description: The local IP address of your Eagle-200 device.
description: The local IP address of your Eagle device.
required: true
type: string
cloud_id:
description: The Cloud ID that is printed on the bottom of the Eagle-200
description: The Cloud ID that is printed on the bottom of the Eagle
required: true
type: string
install_code:
description: The Install Code that is printed on the bottom of the Eagle-200
description: The Install Code that is printed on the bottom of the Eagle
required: true
type: string
{% endconfiguration %}

11
source/_integrations/recorder.markdown
View File

@ -37,6 +37,16 @@ recorder:
description: The URL that points to your database.
required: false
type: string
db_max_retries:
description: The max amount of times, the recorder retries to connect to the database.
required: false
default: 10
type: integer
db_retry_wait:
description: The time in seconds, that the recorder sleeps when trying to connect to the database.
required: false
default: 3
type: integer
purge_keep_days:
description: Specify the number of history days to keep in recorder database after a purge.
required: false
@ -186,6 +196,7 @@ If you are using the default `FULL` recovery model for MS SQL Server you will ne
### Database startup
If you are running a database server instance on the same server as Home Assistant then you must ensure that this service starts before Home Assistant. For a Linux instance running Systemd (Raspberry Pi, Debian, Ubuntu and others) you should edit the service file.
To help facilitate this, db_max_retry and db_retry_wait variables have been added to ensure the recorder retries the connection to your database enough times, for your database to start up.
```bash
sudo nano /etc/systemd/system/home-assistant@homeassistant.service

133
source/_integrations/rest.markdown
View File

@ -105,12 +105,16 @@ headers:
required: false
type: [string, list]
json_attributes:
description: A list of keys to extract values from a JSON dictionary result and then set as sensor attributes.
reqired: false
description: A list of keys to extract values from a JSON dictionary result and then set as sensor attributes. If the endpoint returns XML with the "text/xml" content type, it will automatically be converted to JSON according to this [specification](https://www.xml.com/pub/a/2006/05/31/converting-between-xml-and-json.html)
required: false
type: [string, list]
json_path_attributes:
description: A [JSONPath](https://goessner.net/articles/JsonPath/) that references the location of the `json_attributes` in the JSON content.
required: false
type: string
force_update:
description: Sends update events even if the value hasn't changed. Useful if you want to have meaningful value graphs in history.
reqired: false
required: false
type: boolean
default: false
{% endconfiguration %}
@ -264,6 +268,26 @@ sensor:
```
{% endraw %}
[JSONPlaceholder](https://jsonplaceholder.typicode.com/) provides sample JSON data for testing. In the below example, JSONPath locates the attributes in the JSON document. [JSONPath Online Evaluator](https://jsonpath.com/) provides a tool to test your JSONPath. If the endpoint returns XML, it will be converted to JSON using `xmltodict` before searching for attributes. You may find the [XMLtoDict debug tool](https://xmltodict-debugger.glitch.me/) helpful for testing how your XML converts to JSON.
{% raw %}
```yaml
sensor:
- platform: rest
name: JSON users
json_attributes_path: "$.[0].address"
json_attributes:
- street
- suite
- city
- zipcode
resource: https://jsonplaceholder.typicode.com/users
value_template: '{{ value_json[0].name }}'
```
{% endraw %}
This sample fetches a weather report from [OpenWeatherMap](https://openweathermap.org/), maps the resulting data into attributes of the RESTful sensor and then creates a set of [template](/integrations/template) sensors that monitor the attributes and present the values in a usable form.
{% raw %}
@ -358,3 +382,106 @@ sensor:
unit_of_measurement: '°C'
```
{% endraw %}
The below example allows shows how to extract multiple values from a dictionary with `json_attributes` and `json_attributes_path` from the XML of a Steamist Steambath Wi-Fi interface and use them to create a switch and multiple sensors without having to poll the endpoint numerous times.
In the below example `json_attributes_path` is set to `$.response` which is the location of the `usr0`, `pot0`, ... attributes used for `json_attributes`.
{% raw %}
```yaml
sensor:
# Steam Controller
- platform: rest
name: Steam System Data
resource: http://192.168.1.105/status.xml
json_attributes_path: "$.response"
scan_interval: 15
value_template: 'OK'
json_attributes:
- "usr0"
- "pot0"
- "temp0"
- "time0"
- platform: template
sensors:
steam_temp:
friendly_name: Steam Temp
value_template: '{{ states.sensor.steam_system_data.attributes["temp0"] | regex_findall_index("([0-9]+)XF") }}'
unit_of_measurement: "°F"
steam_time_remaining:
friendly_name: "Steam Time Remaining"
value_template: '{{ states.sensor.steam_system_data.attributes["time0"] }}'
unit_of_measurement: "minutes"
switch:
- platform: template
switches:
steam:
value_template: '{{ states.sensor.steam_system_data.attributes["usr0"] | int >= 1 }}'
turn_on:
- service: rest_command.set_steam_led
data:
led: 6
- service: homeassistant.update_entity
data:
entity_id: sensor.steam_system_data
- delay: 00:00:15
- service: homeassistant.update_entity
data:
entity_id: sensor.steam_system_data
turn_off:
- service: rest_command.set_steam_led
data:
led: 7
- service: homeassistant.update_entity
data:
entity_id: sensor.steam_system_data
- delay: 00:00:15
- service: homeassistant.update_entity
data:
entity_id: sensor.steam_system_data
friendly_name: Steam
rest_command:
set_steam_led:
url: http://192.168.1.105/leds.cgi?led={{ led }}
```
{% endraw %}
For reference, the XML content of endpoint shown above example is below:
```xml
<?xml version="1.0" encoding="utf-8"?>
<response>
<scan>0</scan>
<ver>12556</ver>
<count>48</count>
<ssid>alexander</ssid>
<bss>
<valid>0</valid>
<name>0</name>
<privacy>0</privacy>
<wlan>0</wlan>
<strength>0</strength>
</bss>
<led0>0</led0>
<led1>0</led1>
<led2>0</led2>
<led3>0</led3>
<led4>0</led4>
<led5>0</led5>
<led6>0</led6>
<led7>0</led7>
<btn0>up</btn0>
<btn1>up</btn1>
<btn2>up</btn2>
<btn3>up</btn3>
<pot0>0</pot0>
<usr0>0</usr0>
<temp0>0x73XF0x73XF</temp0>
<time0> 0</time0>
</response>
```

20
source/_integrations/rpi_gpio_pwm.markdown
View File

@ -8,7 +8,7 @@ ha_release: 0.43
logo: raspberry-pi.png
---
The `rpi_gpio_pwm` platform allows to control multiple lights using pulse-width modulation, for example LED strips. It supports one-color, RGB and RGBW LEDs driven by GPIOs of a Raspberry Pi or a PCA9685 controller.
The `rpi_gpio_pwm` platform allows to control multiple lights using pulse-width modulation, for example LED strips. It supports one-color, RGB and RGBW LEDs driven by GPIOs of a Raspberry Pi (same host or remote) or a PCA9685 controller.
For controlling the GPIOs, the platform connects to the [pigpio-daemon](http://abyz.me.uk/rpi/pigpio/pigpiod.html), which must be running. On Raspbian Jessie 2016-05-10 or newer the `pigpio` library is already included. On other operating systems it needs to be installed first (see [installation instructions](https://github.com/soldag/python-pwmled#installation)).
@ -59,6 +59,10 @@ leds:
required: false
default: 0x40
type: string
host:
description: The remote host address for the GPIO driver.
required: false
type: string
{% endconfiguration %}
## Examples
@ -94,3 +98,17 @@ light:
pins: [3, 4, 5, 6] # [R, G, B, W]
type: rgbw
```
### RGB LED connected to the GPIO pins of an remote Raspberry Pi.
On the Raspberry Pi the pigpio daemon is running on the default port 6666.
```yaml
# Example configuration.yaml entry
light:
- platform: rpi_gpio_pwm
leds:
- name: Lightstrip Sideboard
driver: gpio
host: 192.168.0.66
```

47
source/_integrations/salt.markdown Normal file
View File

@ -0,0 +1,47 @@
---
title: Salt Fiber Box
description: Instructions on how to integrate Salt Fiber Box router into Home Assistant.
logo: salt.png
ha_category:
- Presence Detection
ha_iot_class: Local Polling
ha_codeowners:
- '@bjornorri'
ha_release: 0.106
---
The `salt` platform offers presence detection by looking at connected devices to a [Salt Fiber Box](https://fiber.salt.ch/en/fiber/equipment/fiber-box) router from [Salt](https://www.salt.ch), which is an internet provider in Switzerland.
<div class='note'>
The router only allows one user session at a time. If you log into the router's web interface, the platform will stop updating until you log out.
</div>
## Configuration
To use a Salt Fiber Box router in your installation, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
device_tracker:
- platform: salt
host: 192.168.1.1
username: admin
password: YOUR_PASSWORD
```
{% configuration %}
host:
description: The IP address of your router, e.g. `192.168.1.1`.
required: true
type: string
username:
description: The username used to log into the router's web interface, e.g. `admin`.
required: true
type: string
password:
description: The password used to log into the router's web interface.
required: true
type: string
{% endconfiguration %}
See the [device tracker integration page](/integrations/device_tracker/) for instructions how to configure the people to be tracked.

5
source/_integrations/scene.markdown
View File

@ -16,6 +16,7 @@ You can create scenes that capture the states you want certain entities to be. F
# Example configuration.yaml entry
scene:
- name: Romantic
icon: "mdi:flower-tulip"
entities:
light.tv_back_light: on
light.ceiling:
@ -39,6 +40,10 @@ name:
description: Friendly name of scene.
required: true
type: string
icon:
description: Icon for the scene.
required: false
type: string
entities:
description: Entities to control and their desired state.
required: true

5
source/_integrations/script.markdown
View File

@ -38,6 +38,10 @@ alias:
description: Friendly name for the script.
required: false
type: string
icon:
description: Icon for the script.
required: false
type: string
description:
description: A description of the script that will be displayed in the Services tab under Developer Tools.
required: false
@ -73,6 +77,7 @@ sequence:
script: 
wakeup:
alias: Wake Up
icon: "mdi:party-popper"
description: 'Turns on the bedroom lights and then the living room lights after a delay'
fields:
minutes:

3
source/_integrations/signal_messenger.markdown
View File

@ -80,5 +80,6 @@ action:
data:
message: "Alarm in the living room!"
data:
attachment: "/tmp/surveillance_camera.jpg"
attachments:
- "/tmp/surveillance_camera.jpg"
```

52
source/_integrations/simplisafe.markdown
View File

@ -92,3 +92,55 @@ For any property denoting a volume, the following values should be used:
| `exit_delay_home` | yes | The number of seconds to delay triggering when exiting with a "home" state |
| `light` | yes | Whether the light on the base station should display when armed |
| `voice_prompt_volume` | yes | The volume of the base station's voice prompts |
## Events
### `SIMPLISAFE_EVENT`
`SIMPLISAFE_EVENT` events represent events that appear on the timeline of the SimpliSafe
web and mobile apps. When received, they come with event data that contains the
following keys:
* `changed_by`: the PIN that triggered the event (if appropriate)
* `event_type`: the type of event
* `info`: a human-friendly string describing the event in more detail
* `sensor_name`: the sensor that triggered the event (if appropriate)
* `sensor_serial`: the serial number of the sensor that triggered the event (if appropriate)
* `sensor_type`: the type of sensor that triggered the event (if appropriate)
* `system_id`: the system ID to which the event belongs
* `timestamp`: the UTC datetime at which the event was received
For example, when the system is armed by "remote" means (via the web app, etc.), a
`SIMPLISAFE_EVENT` event will fire with the following event data:
```python
{
"changed_by": "",
"event_type": "armed_home",
"info": "System Armed (Home) by Remote Management",
"sensor_name": "",
"sensor_serial": "",
"sensor_type": "remote",
"system_id": 123456,
"timestamp": datetime.datetime(2020, 2, 13, 23, 1, 13, tzinfo=<UTC>),
}
```
`event_type`, being one of the key fields automations might be built from, can have the
following values:
* `camera_motion_detected`
* `doorbell_detected`
* `entry_detected`
* `motion_detected`
### `SIMPLISAFE_NOTIFICATION`
`SIMPLISAFE_NOTIFICATION` events represent system notifications that would appear in the
messages section of the SimpliSafe web and mobile apps. When received, they come with
event data that contains the following keys:
* `category`: The notification category (e.g., `error`)
* `code`: The SimpliSafe code for the notification
* `message`: The actual text of the notification
* `timestamp`: The UTC timestamp of the notification

3
source/_integrations/sleepiq.markdown
View File

@ -6,11 +6,12 @@ ha_category:
- Health
- Sensor
- Binary Sensor
- Light
ha_release: 0.29
ha_iot_class: Local Polling
---
The SleepIQ implementation lets you view sensor data from [SleepIQ by SleepNumber](https://www.sleepnumber.com/sleepiq-sleep-tracker). In particular, it lets you see the occupancy and current SleepNumber (ie current firmness) of each side of a SleepNumber bed.
The SleepIQ implementation lets you view sensor data from [SleepIQ by SleepNumber](https://www.sleepnumber.com/sleepiq-sleep-tracker). In particular, it lets you see the occupancy and current SleepNumber (ie current firmness) of each side of a SleepNumber bed. Control of the lights included in the FlexFit platform is available as well.
## Setup

6
source/_integrations/spc.markdown
View File

@ -10,7 +10,7 @@ logo: vanderbilt_spc.png
ha_iot_class: Local Push
---
Home Assistant has support to integrate your [Vanderbilt SPC](https://www.spcsupportinfo.com/SPCConnectPro/) alarm panel and any connected motion, door and smoke sensors.
Home Assistant has support to integrate your [Vanderbilt SPC](https://www.spcsupportinfo.com/SPCConnectPro/) alarm panel and any connected motion, door, smoke and technical sensors.
Integration with SPC is done through a third-party API gateway called [SPC Web Gateway](https://www.lundix.se/smarta-losningar/) which must be installed and configured somewhere on your network.
@ -65,4 +65,6 @@ automation:
The `spc` platform allows you to get data from your [Vanderbilt SPC](https://www.spcsupportinfo.com/SPCConnectPro/) binary sensors from within Home Assistant.
Check the [type/class](/integrations/binary_sensor/) list for a possible visualization of your zone. Currently motion, smoke and door sensors are supported.
Check the [type/class](/integrations/binary_sensor/) list for a possible visualization of your zone. Currently motion, smoke, door and technical sensors are supported.
Hint: In SPC, Technical zones can be used to track (for example) the status of an output. Virtual zones are supported in SPC firmware from 3.11. You can set up a virtual zone as technical, and link it to a mapping key that is controlling an output.

39
source/_integrations/surepetcare.markdown
View File

@ -20,11 +20,11 @@ To add a flap and pet, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
surepetcare:
username: x@y.com
password: v3rys3cr3t!
household_id: 1337
flaps: [{id: 2337, name: Flap}]
pets: [{id: 3337, name: Pet}]
username: YOUR_SURE_PETCARE_LOGIN
password: YOUR_SURE_PETCARE_PASSWORD
feeders: [12345, 67890]
flaps: [13579]
pets: [24680]
```
{% configuration %}
@ -36,10 +36,6 @@ surepetcare:
description: The Sure Petcare Password
required: true
type: string
household_id:
description: The Sure Petcare household_id
required: true
type: integer
flaps:
description: The Sure Petcare flaps
required: true
@ -53,6 +49,19 @@ surepetcare:
description: A name for the flap
required: true
type: string
feeders:
description: The Sure Petcare flaps
required: true
type: map
keys:
id:
description: The Sure Petcare id of a flap
required: true
type: integer
name:
description: A name for the flap
required: true
type: string
pets:
description: Pets managed by Sure Petcare flap(s)
required: true
@ -83,6 +92,14 @@ surepetcare:
type: device_class
{% endconfiguration %}
## Getting the IDs of your household, flaps and pets
## Getting the IDs of your flaps, feeders and pets
For now, please use the [sp_cli.py](https://github.com/rcastberg/sure_petcare/blob/master/sp_cli.py) from [@rcastberg](https://github.com/rcastberg) to fetch the IDs from the Sure Petcare API. With default setting, the IDs will be written as JSON to `~/.surepet.cache`.
There are (at least) two ways:
- Use the [sp_cli.py](https://github.com/rcastberg/sure_petcare/blob/master/sp_cli.py) from [@rcastberg](https://github.com/rcastberg) to fetch the IDs from the Sure Petcare API. With the default setting, the IDs will be written as JSON to `~/.surepet.cache`.
- Visit [surepetcare.io](https://surepetcare.io) and log in with your Sure Petcare credentials. Open the developer tools in Chrome/Firefox, switch to the "Network" tab and refresh the page. Now look for calls to `start` (`pets`, `<household id>` and others are also possible, but `start` shows you all information at once). Click on this call and in the JSON displayed you will find all the needed IDs.
<p class='img'>
<a href='/images/integrations/surepetcare/spc_ids.png' target='_blank'>
<img src='/images/integrations/surepetcare/spc_ids.png' alt='Where to find the IDs vie Browser developer console' /></a>
</p>

19
source/_integrations/tado.markdown
View File

@ -5,6 +5,7 @@ logo: tado.png
ha_category:
- Hub
- Climate
- Water Heater
- Presence Detection
- Sensor
ha_release: 0.41
@ -18,6 +19,7 @@ The `tado` integration platform is used as an interface to the [my.tado.com](htt
There is currently support for the following device types within Home Assistant:
- Climate - for every Tado zone.
- Water Heater - for water heater zones.
- [Presence Detection](#presence-detection)
- Sensor - for some additional information of the zones.
@ -26,10 +28,21 @@ There is currently support for the following device types within Home Assistant:
To use your Tado thermostats in your installation, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
# Example configuration.yaml entry with multiple accounts
tado:
username: YOUR_USERNAME
password: YOUR_PASSWORD
- username: YOUR_USERNAME1
password: YOUR_PASSWORD1
- username: YOUR_USERNAME2
password: YOUR_PASSWORD2
```
In case of single account works as well:
```yaml
# Example configuration.yaml entry with single account
tado:
username: YOUR_USERNAME
password: YOUR_PASSWORD
```
{% configuration %}

2
source/_integrations/tahoma.markdown
View File

@ -6,6 +6,7 @@ ha_category:
- Hub
- Binary Sensor
- Cover
- Lock
- Scene
- Switch
- Sensor
@ -22,6 +23,7 @@ There is currently support for the following device types within Home Assistant:
- Binary Sensor
- Sensor
- Cover
- Lock
- Switch
- Scene

3
source/_integrations/telegram_chatbot.markdown
View File

@ -48,6 +48,7 @@ Send a photo.
| `target` | yes | An array of pre-authorized chat_ids or user_ids to send the notification to. Defaults to the first allowed chat_id. |
| `disable_notification` | yes | True/false for send the message silently. iOS users and web users will not receive a notification, Android users will receive a notification with no sound. Defaults to False. |
| `verify_ssl` | yes | True/false for checking the SSL certificate of the server for HTTPS URLs. Defaults to True. |
| 'timeout' | yes | Timeout for send photo. Will help with timeout errors (poor internet connection, etc) |
| `keyboard` | yes | List of rows of commands, comma-separated, to make a custom keyboard. `[]` to reset to no custom keyboard. Example: `["/command1, /command2", "/command3"]` |
| `inline_keyboard` | yes | List of rows of commands, comma-separated, to make a custom inline keyboard with buttons with associated callback data. Example: `["/button1, /button2", "/button3"]` or `[[["Text btn1", "/button1"], ["Text btn2", "/button2"]], [["Text btn3", "/button3"]]]` |
@ -66,6 +67,7 @@ Send a video.
| `target` | yes | An array of pre-authorized chat_ids or user_ids to send the notification to. Defaults to the first allowed chat_id. |
| `disable_notification` | yes | True/false to send the message silently. iOS users and web users will not receive a notification. Android users will receive a notification with no sound. Defaults to False. |
| `verify_ssl` | yes | True/false for checking the SSL certificate of the server for HTTPS URLs. Defaults to True. |
| 'timeout' | yes | Timeout for send video. Will help with timeout errors (poor internet connection, etc) |
| `keyboard` | yes | List of rows of commands, comma-separated, to make a custom keyboard. `[]` to reset to no custom keyboard. Example: `["/command1, /command2", "/command3"]` |
| `inline_keyboard` | yes | List of rows of commands, comma-separated, to make a custom inline keyboard with buttons with associated callback data. Example: `["/button1, /button2", "/button3"]` or `[[["Text btn1", "/button1"], ["Text btn2", "/button2"]], [["Text btn3", "/button3"]]]` |
@ -84,6 +86,7 @@ Send a document.
| `target` | yes | An array of pre-authorized chat_ids or user_ids to send the notification to. Defaults to the first allowed chat_id. |
| `disable_notification` | yes | True/false for send the message silently. iOS users and web users will not receive a notification, Android users will receive a notification with no sound. Defaults to False. |
| `verify_ssl` | yes | True/false for checking the SSL certificate of the server for HTTPS URLs. Defaults to True. |
| 'timeout' | yes | Timeout for send document. Will help with timeout errors (poor internet connection, etc) |
| `keyboard` | yes | List of rows of commands, comma-separated, to make a custom keyboard. `[]` to reset to no custom keyboard. Example: `["/command1, /command2", "/command3"]` |
| `inline_keyboard` | yes | List of rows of commands, comma-separated, to make a custom inline keyboard with buttons with associated callback data. Example: `["/button1, /button2", "/button3"]` or `[[["Text btn1", "/button1"], ["Text btn2", "/button2"]], [["Text btn3", "/button3"]]]` |

4
source/_integrations/tesla.markdown
View File

@ -54,8 +54,8 @@ password:
required: true
type: string
scan_interval:
description: API polling interval in seconds. Minimum value can't be less than 300 (5 minutes). Very frequent polling can use battery.
description: API polling interval in seconds. Minimum value can't be less than 60 (1 minute). Very frequent polling can use battery.
required: false
type: integer
default: 300
default: 660
{% endconfiguration %}

19
source/_integrations/totalconnect.markdown
View File

@ -4,23 +4,34 @@ description: Instructions on how to integrate TotalConnect alarms into Home Assi
logo: honeywell-tc.png
ha_category:
- Alarm
- Binary Sensor
ha_release: 0.42
---
The `totalconnect` platform provides connectivity with the Honeywell TotalConnect alarm systems used by many alarm companies.
The `totalconnect` integration provides connectivity with the Honeywell TotalConnect alarm systems used by many alarm companies.
This platform supports the following services: `alarm_arm_away`, `alarm_arm_home`, `alarm_arm_night` and `alarm_disarm`.
If you have issues running this component, you may require `libxml2-dev` and `libxmlsec1-dev` packages. To install these on Raspbian, run the command `apt install libxml2-dev libxmlsec1-dev` with sudo.
## Alarm Control Panel
The integration provides an Alarm Control Panel for each TotalConnect location. It uses the name of your location from TotalConnect. For example, if your location name in TotalConnect is "Home", then you will get `alarm_control_panel.home` in Home Assistant.
The alarm control panel supports the following services: `alarm_arm_away`, `alarm_arm_home`, `alarm_arm_night` and `alarm_disarm`.
The `triggered` state also provides a state attribute called `triggered_source` giving more detail on what triggered the alarm:
- `Police/Medical` is when sensors detected a burglar and/or a person pushed the Police or Medical button
- `Fire/Smoke` is when fire or smoke is detected, or a person pushed the Fire button
- `Carbon Monoxide` is when carbon monoxide is detected
If you have issues running this component, you may require `libxml2-dev` and `libxmlsec1-dev` packages. To install these on Raspbian, run the command `apt install libxml2-dev libxmlsec1-dev` with sudo.
## Binary Sensor
The integration provides a Binary Sensor for each TotalConnect zone. To see zones in TotalConnect "fault" status, your TotalConnect account must have "Sensor Events" enabled. Your alarm monitoring company may charge an extra fee to enable this.
The TotalConnect API has limited zone type information. Home Assistant device class `door` is assigned to TotalConnect door, window, perimeter, motion sensor, and most alarm panel buttons. The sensor will appear as `True` if the door is open (either fault or triggered in TotalConnect) and `False` otherwise. Device class `smoke` is assigned to TotalConnect smoke detectors and buttons with physical alarm panel "Response Type" setting of "Fire No Verification". The sensor will appear as `True` if smoke is detected. Device class `gas` is assigned to TotalConnect carbon monoxide detectors. The sensor will appear as `True` if gas is detected.
## Configuration
To enable this, add the following lines to your `configuration.yaml`:
To enable TotalConnect, add the following lines to your `configuration.yaml`:
```yaml
totalconnect:

21
source/_integrations/twitch.markdown
View File

@ -10,9 +10,22 @@ ha_iot_class: Cloud Polling
The `twitch` platform will allow you to monitor [Twitch](https://www.twitch.tv/) channel status from within Home Assistant and setup automation based on the information.
## Setup
## Setup Client ID
Create a new app at "Register Your Application" in the [Twitch developer portal](https://glass.twitch.tv/console/apps). Then get the **Client ID** for the new app.
Create a new app at "Register Your Application" in the [Twitch developer portal](https://glass.twitch.tv/console/apps). Then get the __Client ID__ for the new application.
## Setup OAuth Token
To enable the follow and subscription attributes, the OAuth token is needed to get the right permissions on the Twitch API.
If you don't need those, ignore the configuration setting: `token`.
To get the OAuth token, visit the [OAuth Token Generator](https://twitchapps.com/tokengen/#), insert your __Client ID__ and `user_read user_subscriptions` inside __scopes__.
Before clicking Summit (the broken image below the form), visit the [Twitch dev console](https://dev.twitch.tv/console) and add a new application.
As __OAuth Redirect URLs__ add `https://twitchapps.com/tokengen/` and click __Create__
.
Back at the Token Generator, click the __Summit__ button, accept the consent screen and get your __OAuth Token__.
## Configuration
@ -33,6 +46,10 @@ client_id:
description: Your Twitch client ID.
required: true
type: string
token:
description: Your Twitch OAuth Token.
required: false
type: string
channels:
description: List of channels names
required: true

18
source/_integrations/utility_meter.markdown
View File

@ -46,7 +46,7 @@ offset:
description: "Cycle reset occur at the beginning of the period (0 minutes, 0h00 hours, Monday, day 1, January). This option enables the offsetting of these beginnings. Supported formats: `offset: 'HH:MM:SS'`, `offset: 'HH:MM'` and Time period dictionary (see example below)."
required: false
default: 0
type: time
type: time
type: integer
net_consumption:
description: Set this to True if you would like to treat the source as a net meter. This will allow your counter to go both positive and negative.
@ -67,7 +67,7 @@ offset:
# At least one of these must be specified:
days: 1
hours: 0
minutes: 0
minutes: 0
```
## Services
@ -153,8 +153,8 @@ When using the [DSMR component](/integrations/dsmr) to get data from the utility
If you want to create a daily and monthly sensor for each tariff, you have to track separate sensors:
- `sensor.power_consumption_low` for off-peak power
- `sensor.power_consumption_normal` for peak power
- `sensor.energy_consumption_tarif_1` for tarif 1 power (for example off-peak)
- `sensor.energy_consumption_tarif_2` for for tarif 2 power (for example peak)
- `sensor.gas_consumption` for gas consumption
So, tracking daily and monthly consumption for each sensor, will require setting up 6 entries under the `utility_meter` component.
@ -162,26 +162,26 @@ So, tracking daily and monthly consumption for each sensor, will require setting
```yaml
utility_meter:
daily_power_offpeak:
source: sensor.power_consumption_low
source: sensor.energy_consumption_tarif_1
cycle: daily
daily_power_peak:
source: sensor.power_consumption_normal
source: sensor.energy_consumption_tarif_2
cycle: daily
daily_gas:
source: sensor.gas_consumption
cycle: daily
monthly_power_offpeak:
source: sensor.power_consumption_low
source: sensor.energy_consumption_tarif_1
cycle: monthly
monthly_power_peak:
source: sensor.power_consumption_normal
source: sensor.energy_consumption_tarif_2
cycle: monthly
monthly_gas:
source: sensor.gas_consumption
cycle: monthly
```
Additionally, you can add template sensors to compute daily and monthly total usage.
Additionally, you can add template sensors to compute daily and monthly total usage.
{% raw %}
```yaml

34
source/_integrations/vilfo.markdown Normal file
View File

@ -0,0 +1,34 @@
---
title: "Vilfo Router"
description: "Instructions on how to integrate a Vilfo Router into Home Assistant."
logo: vilfo.png
ha_release: "0.106"
ha_category:
- Network
- System Monitor
- Sensor
ha_iot_class: "Local Polling"
ha_config_flow: true
ha_codeowners:
- '@ManneW'
---
The `Vilfo Router` integration allows you to observe the state of your [Vilfo Router](https://www.vilfo.com) from Home Assistant.
It currently supports reporting the current load of the device in percent and the current uptime measured in minutes.
## Configuration
The integration can be added using the UI. Go to **Configuration** >> **Integrations** and click the `+` sign button and select **Vilfo Router** from the list.
To configure the integration you will need the hostname or IP of your router (`admin.vilfo.com` is the default hostname) as well as an API access token.
### Obtaining an access token
The access token for the API can be obtained through the Vilfo web-UI in the pane named "general". Visit [the official API documentation](https://www.vilfo.com/apidocs/#header-authorization) for more information on how to find your token.
<div class="note warning">
In version 1.0.13 of the Vilfo firmware, access tokens are invalidated when a new login to the web UI is made. To prevent web UI logins from interfering with the API calls, you can create a separate user solely for API purposes and use its access token.
</div>

2
source/_integrations/vizio.markdown
View File

@ -41,7 +41,7 @@ Make sure that your device is on before continuing.
| Parameter | Description |
| :------------ | :---------------------------------------------------------------------- |
| `ip` | IP address (possibly including port) obtained from the previous section |
| `ip` | `IP Address:Port` (obtained from the previous section) |
| `device_type` | The type of device you are connecting to. Options are `tv` or `speaker` |
Enter the following command to initiate pairing:

17
source/_integrations/zha.markdown
View File

@ -41,6 +41,10 @@ The custom quirks implementations for zigpy implemented as ZHA Device Handlers f
## Known working Zigbee radio modules
- dresden elektronik deCONZ based Zigbee radios (via the [zigpy-deconz](https://github.com/zigpy/zigpy-deconz) library for zigpy)
- [ConBee II (a.k.a. ConBee 2) USB adapter from dresden elektronik](https://phoscon.de/conbee2)
- [ConBee USB adapter from dresden elektronik](https://phoscon.de/conbee)
- [RaspBee Raspberry Pi Shield from dresden elektronik](https://phoscon.de/raspbee)
- EmberZNet based radios using the EZSP protocol (via the [bellows](https://github.com/zigpy/bellows) library for zigpy)
- [Nortek GoControl QuickStick Combo Model HUSBZB-1 (Z-Wave & Zigbee USB Adapter)](https://www.nortekcontrol.com/products/2gig/husbzb-1-gocontrol-quickstick-combo/)
- [Elelabs Zigbee USB Adapter](https://elelabs.com/products/elelabs_usb_adapter.html)
@ -48,19 +52,22 @@ The custom quirks implementations for zigpy implemented as ZHA Device Handlers f
- Telegesis ETRX357USB (Note! This first have to be flashed with other EmberZNet firmware)
- Telegesis ETRX357USB-LRS (Note! This first have to be flashed with other EmberZNet firmware)
- Telegesis ETRX357USB-LRS+8M (Note! This first have to be flashed with other EmberZNet firmware)
- Texas Instruments CC253x, CC26x2R, and CC13x2 based radios (via the [zigpy-cc](https://github.com/sanyatuning/zigpy-cc) library for zigpy)
- [CC2531 USB stick hardware flashed with custom Z-Stack coordinator firmware from the Zigbee2mqtt project](https://www.zigbee2mqtt.io/getting_started/what_do_i_need.html)
- [CC2530 + CC2591 USB stick hardware flashed with custom Z-Stack coordinator firmware from the Zigbee2mqtt project](https://www.zigbee2mqtt.io/getting_started/what_do_i_need.html)
- [CC2530 + CC2592 dev board hardware flashed with custom Z-Stack coordinator firmware from the Zigbee2mqtt project](https://www.zigbee2mqtt.io/getting_started/what_do_i_need.html)
- [CC2652R dev board hardware flashed with custom Z-Stack coordinator firmware from the Zigbee2mqtt project](https://www.zigbee2mqtt.io/getting_started/what_do_i_need.html)
- [CC1352P-2 dev board hardware flashed with custom Z-Stack coordinator firmware from the Zigbee2mqtt project](https://www.zigbee2mqtt.io/getting_started/what_do_i_need.html)
- [CC2538 + CC2592 dev board hardware flashed with custom Z-Stack coordinator firmware from the Zigbee2mqtt project](https://www.zigbee2mqtt.io/getting_started/what_do_i_need.html)
- XBee Zigbee based radios (via the [zigpy-xbee](https://github.com/zigpy/zigpy-xbee) library for zigpy)
- Digi XBee Series 3 (xbee3-24) modules
- Digi XBee Series 2C (S2C) modules
- Digi XBee Series 2 (S2) modules (Note! This first have to be flashed with Zigbee Coordinator API firmware)
- dresden elektronik deCONZ based Zigbee radios (via the [zigpy-deconz](https://github.com/zigpy/zigpy-deconz) library for zigpy)
- [ConBee II (a.k.a. ConBee 2) USB adapter from dresden elektronik](https://phoscon.de/conbee2)
- [ConBee USB adapter from dresden elektronik](https://phoscon.de/conbee)
- [RaspBee Raspberry Pi Shield from dresden elektronik](https://phoscon.de/raspbee)
- ZiGate based radios (via the [zigpy-zigate](https://github.com/doudz/zigpy-zigate) library for zigpy and require firmware 3.1a or later)
- [ZiGate USB-TTL](https://zigate.fr/produit/zigate-ttl/)
- [ZiGate USB-DIN](https://zigate.fr/produit/zigate-usb-din/)
- [PiZiGate](https://zigate.fr/produit/pizigate-v1-0/)
- [Wifi ZiGate](https://zigate.fr/produit/zigate-pack-wifi-v1-3/) (work in progress)
- [Wifi ZiGate](https://zigate.fr/produit/zigate-pack-wifi-v1-3/)
## Configuration - GUI

27
source/_lovelace/entity-button.markdown → source/_lovelace/button.markdown
View File

@ -1,25 +1,25 @@
---
title: "Entity Button Card"
sidebar_label: Entity Button
description: "The Entity Button card allows you to add buttons to perform tasks"
title: "Button Card"
sidebar_label: Button
description: "The Button card allows you to add buttons to perform tasks"
---
The Entity Button card allows you to add buttons to perform tasks.
The Button card allows you to add buttons to perform tasks.
<p class='img'>
<img src='/images/lovelace/lovelace_entity_button_card.png' alt='Screenshot of the entity button card'>
Screenshot of the Entity Button card.
<img src='/images/lovelace/lovelace_entity_button_card.png' alt='Screenshot of the button card'>
Screenshot of the Button card.
</p>
```yaml
type: entity-button
type: button
entity: light.living_room
```
{% configuration %}
type:
required: true
description: entity-button
description: button
type: string
entity:
required: true
@ -50,6 +50,11 @@ icon_height:
description: Set the height for the icon. This is in pixels which is handled by the configuration UI. (Advanced users can use other CSS values if they like)
type: string
default: auto
state_color:
required: false
description: Set to `true` to have icons colored when entity is active
type: boolean
default: true
tap_action:
required: false
description: Action to take on tap
@ -189,7 +194,7 @@ user:
Title and Script Service Example:
```yaml
type: entity-button
type: button
name: Turn Off Lights
tap_action:
action: call-service
@ -200,6 +205,6 @@ entity: script.turn_off_lights
```
<p class='img'>
<img src='/images/lovelace/lovelace_entity_button_complex_card.png' alt='Screenshot of the entity button card'>
Screenshot of the Entity Button card with Title and Script Service.
<img src='/images/lovelace/lovelace_entity_button_complex_card.png' alt='Screenshot of the button card'>
Screenshot of the Button card with Title and Script Service.
</p>

5
source/_lovelace/glance.markdown
View File

@ -47,6 +47,11 @@ columns:
required: false
description: Number of columns to show. If not specified the number will be set automatically.
type: integer
state_color:
required: false
description: Set to `true` to have icons colored when entity is active
type: boolean
default: true
{% endconfiguration %}
## Options For Entities

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

@ -188,6 +188,11 @@ title:
required: false
description: Icon tooltip. Set to null to hide.
type: string
state_color:
required: false
description: Set to `true` to have icons colored when entity is active
type: boolean
default: true
tap_action:
required: false
description: Action to take on tap

6
source/_posts/2017-02-11-alert-appletv-mqtt-yeelight.markdown
View File

@ -43,9 +43,9 @@ The [`yeelight`][yeelight] component has been ported to use a more stable and fe
- [Rflink][rflink] 433Mhz gateway platform and components ([@aequitas])
- Lock: Support for [Nuki.io][nuki] smart locks ([@pschmitt])
- Sensor: [QNAP][qnap] Sensor ([@colinodell])
- Switch: Add support for [FRITZ!DECT][fritz] wireless switches based on fritzhome ([@BastianPoe])
- Switch: Add support for FRITZ!DECT wireless switches based on fritzhome ([@BastianPoe])
- Sensor: Add [moon][moon] sensor ([@fabaff])
- Media player: Support for the [Orange Livebox Play TV][orange] appliance ([@pschmitt])
- Media player: Support for the Orange Livebox Play TV appliance ([@pschmitt])
- Media player: [Apple TV][apple-tv] support ([@postlund])
- MQTT: [MQTT discovery][mqtt-discovery] support ([@balloob], [@fabaff])
- Notify: [Mailgun][mailgun] notify service ([@pschmitt])
@ -203,7 +203,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[ffmpeg-bin]: /integrations/ffmpeg_motion
[ffmpeg]: /integrations/ffmpeg/
[filters]: /topics/templating/#home-assistant-template-extensions
[fritz]: /integrations/fritzdect
[hue]: /integrations/hue
[light]: /cookbook/custom_ui_by_andrey-git
[mailgun]: /integrations/mailgun
@ -212,7 +211,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[mqtt-discovery]: /integrations/mqtt/#discovery
[nuki]: /integrations/nuki
[openevse]: /integrations/openevse
[orange]: /integrations/liveboxplaytv
[owm]: /integrations/openweathermap#sensor
[python-yeelight]: https://gitlab.com/stavros/python-yeelight
[qnap]: /integrations/qnap

5
source/_posts/2017-07-29-release-50.markdown
View File

@ -119,7 +119,7 @@ conversation:
- The kitchen is magic
```
- Switch fritzdect: attributes have been renamed to use underscores and no capital letters ([@thomasklingbeil] - [#8436]) ([switch.fritzdect docs]) (breaking change)
- Switch fritzdect: attributes have been renamed to use underscores and no capital letters ([@thomasklingbeil] - [#8436]) (breaking change)
- Yahoo Weather: no longer allow configuring forecasts but include all instead. ([@fanthos] - [#8626]) ([weather.yweather docs]) (breaking change)
- The Home Assistant Z-Wave Cover implementation has been updated to support the latest development version of OpenZWave. If you are currently applying a workaround to your OpenZWave installation to support the barrier command class, you'll need to make sure you update your workaround to the latest development version of OpenZWave. ([@firstof9] - [#8574]) ([cover docs]) ([cover.zwave docs]) (breaking change)
@ -170,7 +170,7 @@ conversation:
- bump python-mirobo version for more robust protocol handling, make the platform to update on startup ([@rytilahti] - [#8602]) ([switch.xiaomi_vacuum docs])
- Binary sensor ping fixed for hassio ([@gollo] - [#8573]) ([binary_sensor.ping docs])
- Simplified percent conversion, better logging ([@open-homeautomation] - [#8568]) ([sensor.knx docs])
- make attributes in the fritzdect module easier to process ([@thomasklingbeil] - [#8436]) ([switch.fritzdect docs]) (breaking change)
- make attributes in the fritzdect module easier to process ([@thomasklingbeil] - [#8436]) (breaking change)
- Allow set_cover_position in scenes ([@peckham] - [#8613])
- better but still not great ([@cribbstechnologies] - [#8618])
- Upgrade youtube_dl to 2017.7.23 ([@fabaff] - [#8617]) ([media_extractor docs])
@ -391,7 +391,6 @@ conversation:
[shopping_list docs]: /integrations/shopping_list/
[snips docs]: /integrations/snips/
[statsd docs]: /integrations/statsd/
[switch.fritzdect docs]: /integrations/fritzdect
[switch.mqtt docs]: /integrations/switch.mqtt/
[switch.wink docs]: /integrations/wink#switch
[switch.xiaomi docs]: /integrations/switch.xiaomi_aqara/

3
source/_posts/2017-10-07-release-55.markdown
View File

@ -49,7 +49,7 @@ This release introduces a new sensor: [Tibber][sensor.tibber docs]. The sensor p
- OwnTracks: Fix handler is None checking ([@balloob] - [#9794]) ([device_tracker.owntracks docs])
- Changed yaml.load into yaml.safe_load ([@GenericStudent] - [#9841]) ([google docs])
- Bugfix/9811 jinja autoescape ([@GenericStudent] - [#9842])
- Livebox Play TV bug: fix #9839 ([@pschmitt] - [#9880]) ([media_player.liveboxplaytv docs])
- Livebox Play TV bug: fix #9839 ([@pschmitt] - [#9880])
## If you need help...
...don't hesitate to use our very active [forums][forum] or join us for a little [chat][discord]. The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
@ -402,4 +402,3 @@ Experiencing issues introduced by this release? Please report them in our [issue
[device_tracker.owntracks docs]: /integrations/owntracks
[google docs]: /integrations/google_translate
[light.tradfri docs]: /integrations/tradfri
[media_player.liveboxplaytv docs]: /integrations/liveboxplaytv

6
source/_posts/2017-10-21-release-56.markdown
View File

@ -174,7 +174,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- OwnTracks: Fix handler is None checking ([@balloob] - [#9794]) ([device_tracker.owntracks docs])
- Changed yaml.load into yaml.safe_load ([@GenericStudent] - [#9841])
- Bugfix/9811 jinja autoescape ([@GenericStudent] - [#9842])
- Fix #9839 ([@pschmitt] - [#9880]) ([media_player.liveboxplaytv docs])
- Fix #9839 ([@pschmitt] - [#9880])
- Upgrade python-telegram-bot to 8.1.1 ([@azogue] - [#9882]) ([telegram_bot docs])
- Xknx improvements ([@Julius2342] - [#9871]) ([knx docs]) ([climate.knx docs])
- zha: Update to bellows 0.4.0 ([@rcloran] - [#9890]) ([zha docs]) ([sensor.zha docs])
@ -211,7 +211,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Update directpy to 0.2 ([@arsaboo] - [#9948])
- Update enocean to 0.40 ([@arsaboo] - [#9949]) ([enocean docs])
- Update hikvision to 1.2 ([@arsaboo] - [#9953]) ([switch.hikvisioncam docs])
- Update fritzhome to 1.0.3 ([@arsaboo] - [#9951]) ([switch.fritzdect docs])
- Update fritzhome to 1.0.3 ([@arsaboo] - [#9951])
- Update fritzconnection to 0.6.5 ([@arsaboo] - [#9950]) ([device_tracker.fritz docs]) ([sensor.fritzbox_callmonitor docs]) ([sensor.fritzbox_netmonitor docs])
- Upgraded pyhomematic ([@danielperna84] - [#9956]) ([homematic docs])
- Add emeter attributes ([@gollo] - [#9903]) ([light.tplink docs])
@ -472,7 +472,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[media_player.denon docs]: /integrations/denon
[media_player.denonavr docs]: /integrations/denonavr/
[media_player.dunehd docs]: /integrations/dunehd
[media_player.liveboxplaytv docs]: /integrations/liveboxplaytv
[media_player.monoprice docs]: /integrations/monoprice
[media_player.plex docs]: /integrations/plex#media-player
[media_player.yamaha docs]: /integrations/yamaha
@ -520,7 +519,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[shiftr docs]: /integrations/shiftr/
[skybell docs]: /integrations/skybell/
[switch.flux docs]: /integrations/flux
[switch.fritzdect docs]: /integrations/fritzdect
[switch.hikvisioncam docs]: /integrations/hikvisioncam
[switch.rainmachine docs]: /integrations/rainmachine#switch
[switch.skybell docs]: /integrations/skybell#switch

3
source/_posts/2017-11-04-release-57.markdown
View File

@ -151,7 +151,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Fix no data event triggers ([@armills] - [#10049]) ([automation.event docs])
- fixing a typo in the old library which broke hub gen2 compatibility ([@sander76] - [#9990])
- Add fail2ban sensor ([@fronzbot] - [#9975]) ([sensor.fail2ban docs]) (new-platform)
- Show current program thumbnail as media_image ([@pschmitt] - [#10033]) ([media_player.liveboxplaytv docs])
- Show current program thumbnail as media_image ([@pschmitt] - [#10033])
- Add link to docs and update ordering ([@fabaff] - [#10062]) ([duckdns docs])
- Remove STATE_UNKNOWN ([@fabaff] - [#10064]) ([sensor.glances docs])
- update library for xiaomi_aqara, change from pyCrypto to cryptography ([@danielhiversen] - [#10066]) ([xiaomi_aqara docs])
@ -577,7 +577,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[mailbox docs]: /integrations/mailbox/
[media_extractor docs]: /integrations/media_extractor/
[media_player docs]: /integrations/media_player/
[media_player.liveboxplaytv docs]: /integrations/liveboxplaytv
[media_player.monoprice docs]: /integrations/monoprice
[media_player.plex docs]: /integrations/plex#media-player
[media_player.russound_rnet docs]: /integrations/russound_rnet

3
source/_posts/2017-12-17-release-60.markdown
View File

@ -142,7 +142,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Fix incorrect comment. ([@emosenkis] - [#11111])
- Update Warrant ([@balloob] - [#11101]) ([cloud docs])
- Fixed typo in automation.py ([@ryanm101] - [#11116]) ([config.automation docs])
- Add media position properties ([@pschmitt] - [#10076]) ([media_player.liveboxplaytv docs])
- Add media position properties ([@pschmitt] - [#10076])
- update pyripple ([@nkgilley] - [#11122]) ([sensor.ripple docs])
- Skip HASS emulated Hue bridges from detection. ([@andreacampi] - [#11128]) ([hue docs])
- Always consume the no_throttle keyword argument. ([@andreacampi] - [#11126])
@ -334,7 +334,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[logbook docs]: /integrations/logbook/
[media_extractor docs]: /integrations/media_extractor/
[media_player.denonavr docs]: /integrations/denonavr/
[media_player.liveboxplaytv docs]: /integrations/liveboxplaytv
[media_player.samsungtv docs]: /integrations/samsungtv
[media_player.sonos docs]: /integrations/sonos
[media_player.ue_smart_radio docs]: /integrations/ue_smart_radio

3
source/_posts/2018-01-27-release-62.markdown
View File

@ -83,7 +83,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Enable probot move ([@fabaff] - [#11690])
- fixed not to include spaces or dots in attribute names ([@olskar] - [#11694]) ([sensor.mold_indicator docs]) (breaking change)
- Add attributes ([@fabaff] - [#11698]) ([sensor.random docs])
- Feature/fritzdect errorhandling ([@BastianPoe] - [#11490]) ([switch.fritzdect docs])
- Feature/fritzdect errorhandling ([@BastianPoe] - [#11490])
- Tesla bug fix #11598 ([@zabuldon] - [#11707])
- Update mold_indicator.py ([@olskar] - [#11715]) ([sensor.mold_indicator docs])
- Override default name for TP-Link devices ([@DanNixon] - [#11710]) ([light.tplink docs]) ([switch.tplink docs])
@ -468,7 +468,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[sensor.xiaomi_aqara docs]: /integrations/sensor.xiaomi_aqara/
[sensor.yr docs]: /integrations/yr
[snips docs]: /integrations/snips/
[switch.fritzdect docs]: /integrations/fritzdect
[switch.hive docs]: /integrations/hive#switch
[switch.ihc docs]: /integrations/ihc#switch
[switch.snmp docs]: /integrations/snmp#switch

3
source/_posts/2018-04-14-release-67.markdown
View File

@ -154,7 +154,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Update AbodePy version to 0.12.3 ([@MisterWil] - [#13709]) ([abode docs])
- Enable autodiscovery for mqtt cameras ([@jmtatsch] - [#13697]) ([mqtt docs]) ([camera.mqtt docs])
- Added ENTITY_ID_FORMAT import and set entity_id in __init__ ([@timmo001] - [#13642]) ([switch.broadlink docs]) (breaking change)
- Fix #10175 ([@pschmitt] - [#13713]) ([media_player.liveboxplaytv docs])
- Fix #10175 ([@pschmitt] - [#13713])
- Add support for Nanoleaf Aurora Light Panels ([@Oro] - [#13456]) ([light.nanoleaf_aurora docs]) (new-platform)
- Added gogogate2 cover ([@dlbroadfoot] - [#13467])
- Remove vendor lookup for mac addresses ([@balloob] - [#13788]) ([device_tracker docs])
@ -367,7 +367,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[light.yeelight docs]: /integrations/yeelight
[lock.bmw_connected_drive docs]: /integrations/bmw_connected_drive
[media_extractor docs]: /integrations/media_extractor/
[media_player.liveboxplaytv docs]: /integrations/liveboxplaytv
[media_player.philips_js docs]: /integrations/philips_js
[media_player.songpal docs]: /integrations/songpal
[media_player.webostv docs]: /integrations/webostv#media-player

8
source/_posts/2018-07-21-release-74.markdown
View File

@ -40,7 +40,7 @@ I'm happy to announce that this release introduces support for Tuya thanks to [@
- Add Tuya component and switch support ([@huangyupeng] - [#15399]) ([tuya docs]) ([switch.tuya docs]) (new-platform)
- Add Tuya light platform ([@huangyupeng] - [#15444]) ([tuya docs]) ([light.tuya docs]) (new-platform)
- Added support for Duke Energy smart meters ([@w1ll1am23] - [#15165]) ([sensor.duke_energy docs]) (new-platform)
- Added support for Duke Energy smart meters ([@w1ll1am23] - [#15165]) (new-platform)
- Added Push Camera ([@dgomes] - [#15151]) ([camera.push docs]) (new-platform)
- Add Cloudflare DNS component. ([@ludeeus] - [#15388]) ([cloudflare docs]) (new-platform)
- Add HomematicIP alarm control panel ([@mxworm] - [#15342]) ([alarm_control_panel docs]) ([homematicip_cloud docs]) ([alarm_control_panel.homematicip_cloud docs]) (new-platform)
@ -103,7 +103,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Added setting cover tilt position in scene ([@kstaniek] - [#15255])
- Pass tox posargs to pylint ([@scop] - [#15226])
- Fix Roomba exception ([@arbreng] - [#15262]) ([vacuum.roomba docs])
- Added support for Duke Energy smart meters ([@w1ll1am23] - [#15165]) ([sensor.duke_energy docs]) (new-platform)
- Added support for Duke Energy smart meters ([@w1ll1am23] - [#15165]) (new-platform)
- Update image_processing async ([@dgomes] - [#15082]) ([image_processing docs])
- Fix python-miio 0.4 compatibility of the xiaomi miio device tracker ([@serhtt] - [#15244]) ([device_tracker docs])
- Upgrade keyring to 13.1.0 ([@fabaff] - [#15268])
@ -141,7 +141,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Improve NetAtmo sensors update logic ([@glpatcern] - [#14866]) ([sensor.netatmo docs])
- removed unused return ([@ludeeus] - [#15402]) ([cloudflare docs])
- Fix confused brightness of xiaomi_aqara gateway light ([@amelchio] - [#15314]) ([light.xiaomi_aqara docs])
- Fix liveboxplaytv empty channel list ([@pschmitt] - [#15404]) ([media_player.liveboxplaytv docs])
- Fix liveboxplaytv empty channel list ([@pschmitt] - [#15404])
- Fix credentials lookup ([@balloob] - [#15409])
- Change Ring binary_sensor frequency polling to avoid rate limit exceeded errors ([@tchellomello] - [#15414]) ([binary_sensor.ring docs])
- Add Tuya component and switch support ([@huangyupeng] - [#15399]) ([tuya docs]) ([switch.tuya docs]) (new-platform)
@ -374,14 +374,12 @@ Experiencing issues introduced by this release? Please report them in our [issue
[media_extractor docs]: /integrations/media_extractor/
[media_player.denonavr docs]: /integrations/denonavr/
[media_player.lg_netcast docs]: /integrations/lg_netcast
[media_player.liveboxplaytv docs]: /integrations/liveboxplaytv
[media_player.philips_js docs]: /integrations/philips_js
[mysensors docs]: /integrations/mysensors/
[onboarding docs]: /integrations/onboarding/
[prometheus docs]: /integrations/prometheus/
[sensor.arlo docs]: /integrations/arlo#sensor
[sensor.deconz docs]: /integrations/deconz#sensor
[sensor.duke_energy docs]: /integrations/duke_energy
[sensor.efergy docs]: /integrations/efergy
[sensor.fixer docs]: /integrations/fixer
[sensor.gtfs docs]: /integrations/gtfs

3
source/_posts/2018-08-29-release-77.markdown
View File

@ -193,7 +193,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- 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])
- fritzdect change to current_power_w ([@Danielhiversen] - [#16079])
- 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])
@ -480,7 +480,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[sonos docs]: /integrations/sonos/
[splunk docs]: /integrations/splunk/
[switch.deconz docs]: /integrations/deconz#switch
[switch.fritzdect docs]: /integrations/fritzdect
[switch.konnected docs]: /integrations/konnected#switch
[switch.wemo docs]: /integrations/wemo
[switch.xiaomi_miio docs]: /integrations/switch.xiaomi_miio/

3
source/_posts/2019-05-16-release-93.markdown
View File

@ -379,7 +379,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- deCONZ - Retry on BridgeBusy errors ([@Kane610] - [#23436]) ([deconz docs])
- Added option to select photoblack cartridge ([@ThaStealth] - [#23433]) ([epsonworkforce docs]) (breaking change)
- Fix bad request for some IP ONVIF camera ([@GeertvanHorrik] - [#22972]) ([onvif docs])
- Bump pyteleloisirs version ([@SNoof85] - [#23661]) ([liveboxplaytv docs])
- Bump pyteleloisirs version ([@SNoof85] - [#23661])
- Upgrade psutil to 5.6.2 ([@fabaff] - [#23671]) ([systemmonitor docs])
- Upgrade shodan to 1.13.0 ([@fabaff] - [#23675]) ([shodan docs])
- Upgrade slacker to 0.13.0 ([@fabaff] - [#23672]) ([slack docs])
@ -799,7 +799,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[iqvia docs]: /integrations/iqvia/
[lcn docs]: /integrations/lcn/
[lifx docs]: /integrations/lifx/
[liveboxplaytv docs]: /integrations/liveboxplaytv/
[local_file docs]: /integrations/local_file/
[locative docs]: /integrations/locative/
[logi_circle docs]: /integrations/logi_circle/

6
source/_posts/2019-10-30-release-101.markdown
View File

@ -567,7 +567,7 @@ The **holiday name** sensor has been renamed to **holiday**. ([@tsvi] - [#27654]
- Move imports in keyboard component ([@Quentame] - [#27791]) ([keyboard docs])
- Move imports in linux_battery component ([@Quentame] - [#27789]) ([linux_battery docs])
- Move imports in ampio component ([@Bouni] - [#27788]) ([ampio docs])
- Move imports in liveboxplaytv component ([@Quentame] - [#27790]) ([liveboxplaytv docs])
- Move imports in liveboxplaytv component ([@Quentame] - [#27790])
- Move imports in amcrest component ([@Bouni] - [#27787]) ([amcrest docs])
- Move imports in imap + imap_email_content component ([@Quentame] - [#27793]) ([imap docs]) ([imap_email_content docs])
- Move imports in netgear_lte component ([@Quentame] - [#27777]) ([netgear_lte docs])
@ -627,7 +627,7 @@ The **holiday name** sensor has been renamed to **holiday**. ([@tsvi] - [#27654]
- Refactor the conversation integration ([@balloob] - [#27839]) ([conversation docs]) ([shopping_list docs])
- Use pre-commit in CI and tox ([@scop] - [#27743])
- Introduce new OAuth2 config flow helper ([@balloob] - [#27727]) ([somfy docs]) (breaking change)
- Move imports in fritzbox, fritz device tracker, fritzdect, fritzbox netmonitor ([@springstan] - [#27746]) ([fritz docs]) ([fritzbox docs]) ([fritzbox_netmonitor docs]) ([fritzdect docs])
- Move imports in fritzbox, fritz device tracker, fritzdect, fritzbox netmonitor ([@springstan] - [#27746]) ([fritz docs]) ([fritzbox docs]) ([fritzbox_netmonitor docs])
- Move imports in cppm_tracker component ([@Bouni] - [#27889]) ([cppm_tracker docs])
- Move imports in concord232 component ([@Bouni] - [#27887]) ([concord232 docs])
- Move imports in comfoconnect component ([@Bouni] - [#27886]) ([comfoconnect docs])
@ -1645,7 +1645,6 @@ The **holiday name** sensor has been renamed to **holiday**. ([@tsvi] - [#27654]
[fritzbox docs]: /integrations/fritzbox/
[fritzbox_callmonitor docs]: /integrations/fritzbox_callmonitor/
[fritzbox_netmonitor docs]: /integrations/fritzbox_netmonitor/
[fritzdect docs]: /integrations/fritzdect/
[frontend docs]: /integrations/frontend/
[frontier_silicon docs]: /integrations/frontier_silicon/
[futurenow docs]: /integrations/futurenow/
@ -1716,7 +1715,6 @@ The **holiday name** sensor has been renamed to **holiday**. ([@tsvi] - [#27654]
[linode docs]: /integrations/linode/
[linux_battery docs]: /integrations/linux_battery/
[lirc docs]: /integrations/lirc/
[liveboxplaytv docs]: /integrations/liveboxplaytv/
[locative docs]: /integrations/locative/
[lock docs]: /integrations/lock/
[logbook docs]: /integrations/logbook/

3
source/_posts/2019-12-11-release-103.markdown
View File

@ -842,7 +842,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Move imports to top for egardia ([@springstan] - [#29448]) ([egardia docs])
- Move imports to top for eight_sleep ([@springstan] - [#29447]) ([eight_sleep docs])
- Update eternalegypt to 0.0.11 ([@amelchio] - [#29446]) ([netgear_lte docs])
- Move imports to top for duke_energy ([@springstan] - [#29445]) ([duke_energy docs])
- Move imports to top for duke_energy ([@springstan] - [#29445])
- Move imports to top for dunehd ([@springstan] - [#29444]) ([dunehd docs])
- Move imports to top for dlink ([@springstan] - [#29443]) ([dlink docs])
- Move imports to top for doorbird ([@springstan] - [#29442]) ([doorbird docs])
@ -1495,7 +1495,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[doorbird docs]: /integrations/doorbird/
[dovado docs]: /integrations/dovado/
[dsmr_reader docs]: /integrations/dsmr_reader/
[duke_energy docs]: /integrations/duke_energy/
[dunehd docs]: /integrations/dunehd/
[dwd_weather_warnings docs]: /integrations/dwd_weather_warnings/
[dyson docs]: /integrations/dyson/

6
source/_posts/2020-01-15-release-104.markdown
View File

@ -895,7 +895,7 @@ Make sure to fill in all fields of the issue template, that is helping us a lot!
- Store capabilities and supported features in entity registry, restore registered entities on startup ([@balloob] - [#30094])
- Fix Withings leaking time zone change into other tests ([@frenck] - [#30320])
- Add local_ip component ([@issacg] - [#29973]) ([localip docs]) (new-integration)
- Update liveboxplay and pyteleloisirs ([@pschmitt] - [#30093]) ([liveboxplaytv docs])
- Update liveboxplay and pyteleloisirs ([@pschmitt] - [#30093])
- Add homematic host port config for HMIP-only CCUs ([@sbyx] - [#30077]) ([homematic docs])
- Bump dependency for HomematicIP Cloud ([@SukramJ] - [#30319]) ([homematicip_cloud docs])
- Add support for Somfy RTS power socket and Somfy io Temperature sensor ([@rhadamantys] - [#30053]) ([tahoma docs])
@ -1026,7 +1026,7 @@ Make sure to fill in all fields of the issue template, that is helping us a lot!
- Set required_features field when registering fan services ([@Jc2k] - [#30516]) ([fan docs]) ([homekit_controller docs])
- Add Brother Printer integration ([@bieniu] - [#30359]) ([brother docs]) (new-integration)
- Format all manifests with prettier ([@frenck] - [#30521])
- Fix AVM FRITZ!DECT switch total consumption ([@Alexxander0] - [#30478]) ([fritzdect docs])
- Fix AVM FRITZ!DECT switch total consumption ([@Alexxander0] - [#30478])
- Register 'androidtv.download' and 'androidtv.upload' services ([@JeffLIrion] - [#30086]) ([androidtv docs])
- Allow specific status codes while notifying mobile_app devices ([@rccoleman] - [#30496]) ([mobile_app docs])
- Correct integration names in manifests (A-B) ([@frenck] - [#30527])
@ -1886,7 +1886,6 @@ Make sure to fill in all fields of the issue template, that is helping us a lot!
[filter docs]: /integrations/filter/
[freebox docs]: /integrations/freebox/
[fritz docs]: /integrations/fritz/
[fritzdect docs]: /integrations/fritzdect/
[frontend docs]: /integrations/frontend/
[geofency docs]: /integrations/geofency/
[geonetnz_quakes docs]: /integrations/geonetnz_quakes/
@ -1938,7 +1937,6 @@ Make sure to fill in all fields of the issue template, that is helping us a lot!
[light docs]: /integrations/light/
[lightwave docs]: /integrations/lightwave/
[linky docs]: /integrations/linky/
[liveboxplaytv docs]: /integrations/liveboxplaytv/
[localip docs]: /integrations/local_ip/
[locative docs]: /integrations/locative/
[lock docs]: /integrations/lock/

1128
source/_posts/2020-02-26-release-106.markdown Normal file
View File

File diff suppressed because it is too large Load Diff

9
source/_redirects
View File

@ -521,7 +521,6 @@
/components/media_player.kodi /integrations/kodi
/components/media_player.lg_netcast /integrations/lg_netcast
/components/media_player.lg_soundbar /integrations/lg_soundbar
/components/media_player.liveboxplaytv /integrations/liveboxplaytv
/components/media_player.mediaroom /integrations/mediaroom
/components/media_player.monoprice /integrations/monoprice
/components/media_player.mpchc /integrations/mpchc
@ -685,7 +684,6 @@
/components/sensor.dsmr /integrations/dsmr
/components/sensor.dte_energy_bridge /integrations/dte_energy_bridge
/components/sensor.dublin_bus_transport /integrations/dublin_bus_transport
/components/sensor.duke_energy /integrations/duke_energy
/components/sensor.dwd_weather_warnings /integrations/dwd_weather_warnings
/components/sensor.dweet /integrations/dweet#sensor
/components/sensor.dyson /integrations/dyson#sensor
@ -978,7 +976,6 @@
/components/switch.fibaro /integrations/fibaro
/components/switch.flux /integrations/flux
/components/switch.fritzbox /integrations/fritzbox
/components/switch.fritzdect /integrations/fritzdect
/components/switch.gc100 /integrations/gc100#switch
/components/switch.hdmi_cec /integrations/hdmi_cec
/components/switch.hikvisioncam /integrations/hikvisioncam
@ -1287,7 +1284,6 @@
/components/dte_energy_bridge /integrations/dte_energy_bridge
/components/dublin_bus_transport /integrations/dublin_bus_transport
/components/duckdns /integrations/duckdns
/components/duke_energy /integrations/duke_energy
/components/dunehd /integrations/dunehd
/components/dwd_weather_warnings /integrations/dwd_weather_warnings
/components/dweet /integrations/dweet
@ -1371,7 +1367,6 @@
/components/fritzbox /integrations/fritzbox
/components/fritzbox_callmonitor /integrations/fritzbox_callmonitor
/components/fritzbox_netmonitor /integrations/fritzbox_netmonitor
/components/fritzdect /integrations/fritzdect
/components/fronius /integrations/fronius
/components/frontend /integrations/frontend
/components/frontier_silicon /integrations/frontier_silicon
@ -1525,7 +1520,6 @@
/components/linux_battery /integrations/linux_battery
/components/lirc /integrations/lirc
/components/litejet /integrations/litejet
/components/liveboxplaytv /integrations/liveboxplaytv
/components/llamalab_automate /integrations/llamalab_automate
/components/local_file /integrations/local_file
/components/locative /integrations/locative
@ -2095,3 +2089,6 @@
/addons/snips https://github.com/home-assistant/hassio-addons/blob/master/snips/README.md
/addons/ssh https://github.com/home-assistant/hassio-addons/blob/master/ssh/README.md
/addons/tellstick https://github.com/home-assistant/hassio-addons/blob/master/tellstick/README.md
# Lovelace documentation
/lovelace/entity-button /lovelace/button

BIN
source/images/blog/2020-02-0.106/brightness-step-device-automation.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 76 KiB

BIN
source/images/blog/2020-02-0.106/components.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 52 KiB

BIN
source/images/blog/2020-02-0.106/entities.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 17 KiB

BIN
source/images/blog/2020-02-0.106/integrations-list.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 72 KiB

BIN
source/images/blog/2020-02-0.106/more-info-person.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 91 KiB

BIN
source/images/blog/2020-02-0.106/safe-mode-activated.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 13 KiB

BIN
source/images/blog/2020-02-0.106/sensor-card.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 13 KiB

BIN
source/images/blog/2020-02-0.106/social.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 142 KiB

BIN
source/images/integrations/surepetcare/spc_ids.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 200 KiB

BIN
source/images/lovelace/lovelace_sensor.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 2.7 KiB

After

Width:  |  Height:  |  Size: 20 KiB

BIN
source/images/screenshots/gdacs-alerts-feed-map.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 130 KiB

BIN
source/images/screenshots/gdacs-alerts-sensor.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 14 KiB

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

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 13 KiB

BIN
source/images/supported_brands/dynalite.png Executable file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 26 KiB

BIN
source/images/supported_brands/gdacs.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 13 KiB

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

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 23 KiB

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

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 64 KiB

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

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 1.3 KiB

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

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.4 KiB

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

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 133 KiB