mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-21 08:16:53 +00:00
Pascal Vizeli
GitHub
commit
725dca85bd
@ -138,9 +138,9 @@ social:
|
||||
|
||||
# Home Assistant release details
|
||||
current_major_version: 0
|
||||
current_minor_version: 94
|
||||
current_patch_version: 4
|
||||
date_released: 2019-06-19
|
||||
current_minor_version: 95
|
||||
current_patch_version: 0
|
||||
date_released: 2019-06-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.
|
||||
|
||||
@ -117,6 +117,8 @@ binary_sensors:
|
||||
keys:
|
||||
motion_detected:
|
||||
description: "Return `on` when a motion is detected, `off` when not."
|
||||
online:
|
||||
description: "Return `on` when camera is available (i.e., responding to commands), `off` when not."
|
||||
sensors:
|
||||
description: >
|
||||
Conditions to display in the frontend.
|
||||
@ -153,6 +155,12 @@ switches:
|
||||
description: Enable/disable motion detection setting.
|
||||
motion_recording:
|
||||
description: Enable/disable recording on motion detection setting.
|
||||
control_light:
|
||||
description: >
|
||||
Automatically control the camera's indicator light, turning it on if the audio or video streams are enabled, and turning it off if both streams are disabled.
|
||||
required: false
|
||||
type: boolean
|
||||
default: true
|
||||
{% endconfiguration %}
|
||||
|
||||
**Note:** Amcrest cameras with newer firmware no longer have the ability to
|
||||
@ -240,6 +248,7 @@ amcrest:
|
||||
password: YOUR_PASSWORD
|
||||
binary_sensors:
|
||||
- motion_detected
|
||||
- online
|
||||
sensors:
|
||||
- sdcard
|
||||
|
||||
|
||||
59
source/_components/aprs.markdown
Normal file
59
source/_components/aprs.markdown
Normal file
@ -0,0 +1,59 @@
|
||||
---
|
||||
layout: page
|
||||
title: "APRS"
|
||||
description: "Instructions on how to use APRS to track devices in Home Assistant."
|
||||
date: 2018-11-04 00:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: aprs.png
|
||||
ha_release: 0.95
|
||||
ha_category: Presence Detection
|
||||
ha_iot_class: Cloud Push
|
||||
---
|
||||
|
||||
The `aprs` [(Automatic Packet Reporting System)](https://en.wikipedia.org/wiki/Automatic_Packet_Reporting_System) device tracker component connects to the [APRS-IS](http://aprs-is.net/) network for tracking amateur radio devices.
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To enable APRS tracking in Home Assistant, add the following section to `configuration.yaml`:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
device_tracker:
|
||||
- platform: aprs
|
||||
username: FO0BAR
|
||||
callsigns:
|
||||
- 'XX0FOO*'
|
||||
- 'YY0BAR-1'
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
username:
|
||||
description: Your callsign. This is used to connect to the host.
|
||||
required: true
|
||||
type: string
|
||||
password:
|
||||
description: Your APRS password. This will verify the connection.
|
||||
required: false
|
||||
type: string
|
||||
default: -1
|
||||
callsigns:
|
||||
description: A list of callsigns you wish to track. Wildcard `*` is allowed. Any callsigns that match will be added as devices.
|
||||
required: true
|
||||
type: list
|
||||
host:
|
||||
description: The APRS server to connect to.
|
||||
required: false
|
||||
type: string
|
||||
default: rotate.aprs2.net
|
||||
timeout:
|
||||
description: The number of seconds to wait to connect to the APRS-IS network before giving up.
|
||||
required: false
|
||||
type: float
|
||||
default: 30.0
|
||||
{% endconfiguration %}
|
||||
|
||||
Verified connections are only required to send data to the APRS-IS network, which the `aprs` platform does not yet do.
|
||||
However, you are free to verify your connection if you know your APRS password.
|
||||
@ -20,6 +20,7 @@ The sensors created can trigger based on any event on the calendar or only for
|
||||
matching events. When you first setup this component it will generate a new
|
||||
configuration file `google_calendars.yaml` that will contain information about
|
||||
all of the calendars you can see.
|
||||
It also exposes a service to add an event to one of your Google Calendars.
|
||||
|
||||
## {% linkable_title Prerequisites %}
|
||||
|
||||
@ -174,6 +175,25 @@ Otherwise everything following the hash sign would be considered a YAML comment.
|
||||
- **start_time**: Start time of event.
|
||||
- **end_time**: End time of event.
|
||||
|
||||
### {% linkable_title Service `google.add_event` %}
|
||||
|
||||
You can use the service `google.add_event` to create a new calendar event in a calendar. Calendar id's can be found in the file `google_calendars.yaml`. All dates and times are in your local time, the component gets your time zone from your `configuration.yaml` file.
|
||||
|
||||
| Service data attribute | Optional | Description | Example |
|
||||
| ---------------------- | -------- | ----------- | --------|
|
||||
| `calendar_id` | no | The id of the calendar you want. | Your email
|
||||
| `summary` | no | Acts as the title of the event. | Bowling
|
||||
| `description` | yes | The description of the event. | Birthday bowling
|
||||
| `start_date_time` | yes | The date and time the event should start. | 2019-03-10 20:00:00
|
||||
| `end_date_time` | yes | The date and time the event should end. | 2019-03-10 23:00:00
|
||||
| `start_date` | yes | The date the whole day event should start. | 2019-03-10
|
||||
| `end_date` | yes | The date the whole day event should end. | 2019-03-11
|
||||
| `in` | yes | Days or weeks that you want to create the event in. | "days": 2
|
||||
|
||||
<p class='note'>
|
||||
You either use `start_date_time` and `end_date_time`, or `start_date` and `end_date`, or `in`.
|
||||
</p>
|
||||
|
||||
## {% linkable_title Using calendar in automations %}
|
||||
|
||||
A calendar can be used as an external scheduler for special events or reoccurring events instead of hardcoding them in automations.
|
||||
|
||||
@ -35,7 +35,7 @@ The way these sensors are displayed in the frontend can be modified in the [cust
|
||||
|
||||
### {% linkable_title Cover control services %}
|
||||
|
||||
Available services: `cover.open_cover`, `cover.close_cover`, `cover.stop_cover`, `cover.open_cover_tilt`, `cover.close_cover_tilt`, `cover.stop_cover_tilt`
|
||||
Available services: `cover.open_cover`, `cover.close_cover`, `cover.stop_cover`, `cover.toggle`, `cover.open_cover_tilt`, `cover.close_cover_tilt`, `cover.stop_cover_tilt`, `cover.toggle_tilt`
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
|
||||
@ -144,6 +144,10 @@ tilt_status_topic:
|
||||
description: The MQTT topic subscribed to receive tilt status update values.
|
||||
required: false
|
||||
type: string
|
||||
tilt_status_template:
|
||||
description: "Defines a [template](/topics/templating/) that can be used to extract the payload for the `tilt_status_topic` topic. "
|
||||
required: false
|
||||
type: string
|
||||
tilt_min:
|
||||
description: The minimum tilt value.
|
||||
required: false
|
||||
@ -306,6 +310,7 @@ cover:
|
||||
value_template: '{{ value.x }}'
|
||||
tilt_command_topic: 'home-assistant/cover/tilt'
|
||||
tilt_status_topic: 'home-assistant/cover/tilt-state'
|
||||
tilt_status_template: '{{ value_json["PWM"]["PWM1"] }}'
|
||||
tilt_min: 0
|
||||
tilt_max: 180
|
||||
tilt_closed_value: 70
|
||||
|
||||
@ -51,6 +51,11 @@ verify_ssl:
|
||||
required: false
|
||||
type: boolean
|
||||
default: true
|
||||
wireless_only:
|
||||
description: Whether to only list devices that are connected directly to the router via WiFi or include those connected via Ethernet or other networked access points as well.
|
||||
required: false
|
||||
type: boolean
|
||||
default: true
|
||||
{% endconfiguration %}
|
||||
|
||||
By default Home Assistant pulls information about connected devices from DD-WRT every 5 seconds.
|
||||
|
||||
@ -17,7 +17,6 @@ ha_release: 0.7
|
||||
Home Assistant can discover and automatically configure [zeroconf](https://en.wikipedia.org/wiki/Zero-configuration_networking)/[mDNS](https://en.wikipedia.org/wiki/Multicast_DNS) and [uPnP](https://en.wikipedia.org/wiki/Universal_Plug_and_Play) devices on your network. Currently the `discovery` component can detect:
|
||||
|
||||
* [Apple TV](/components/apple_tv/)
|
||||
* [Axis Communications security devices](/components/axis/)
|
||||
* [Belkin WeMo switches](/components/wemo/)
|
||||
* [Bluesound speakers](/components/media_player.bluesound/)
|
||||
* [Bose Soundtouch speakers](/components/media_player.soundtouch/)
|
||||
@ -27,8 +26,6 @@ Home Assistant can discover and automatically configure [zeroconf](https://en.wi
|
||||
* [Enigma2 media player](/components/media_player.enigma2/)
|
||||
* [Frontier Silicon internet radios](/components/media_player.frontier_silicon/)
|
||||
* [Google Cast](/components/media_player.cast/)
|
||||
* [HomeKit](/components/homekit_controller/)
|
||||
* [IKEA Trådfri (Tradfri)](/components/tradfri/)
|
||||
* [Linn / Openhome](/components/media_player.openhome/)
|
||||
* [Logitech Harmony Hub](/components/remote.harmony/)
|
||||
* [Logitech media server (Squeezebox)](/components/media_player.squeezebox/)
|
||||
@ -50,6 +47,10 @@ Home Assistant can discover and automatically configure [zeroconf](https://en.wi
|
||||
It will be able to add Google Chromecasts and Belkin WeMo switches automatically,
|
||||
for Philips Hue it will require some configuration from the user.
|
||||
|
||||
<p class='note'>
|
||||
Zeroconf discoverable integrations [Axis](/components/axis/)/[ESPHome](/components/esphome/)/[HomeKit](/components/homekit_controller/)/[Tradfri](/components/tradfri/) have been migrated to use [zeroconf](/components/zeroconf) integration to initiate discovery.
|
||||
</p>
|
||||
|
||||
To load this component, add the following lines to your `configuration.yaml`:
|
||||
|
||||
```yaml
|
||||
@ -76,7 +77,6 @@ enable:
|
||||
Valid values for ignore are:
|
||||
|
||||
* `apple_tv`: Apple TV
|
||||
* `axis`: Axis Communications security devices
|
||||
* `belkin_wemo`: Belkin WeMo switches
|
||||
* `bluesound`: Bluesound speakers
|
||||
* `bose_soundtouch`: Bose Soundtouch speakers
|
||||
@ -87,7 +87,6 @@ Valid values for ignore are:
|
||||
* `google_cast`: Google Cast
|
||||
* `harmony`: Logitech Harmony Hub
|
||||
* `igd`: Internet Gateway Device
|
||||
* `ikea_tradfri`: IKEA Trådfri (Tradfri)
|
||||
* `logitech_mediaserver`: Logitech media server (Squeezebox)
|
||||
* `netgear_router`: Netgear routers
|
||||
* `octoprint`: Octoprint
|
||||
@ -110,7 +109,6 @@ Valid values for ignore are:
|
||||
Valid values for enable are:
|
||||
|
||||
* `dlna_dmr`: DLNA DMR enabled devices
|
||||
* `homekit`: HomeKit accessories
|
||||
|
||||
## {% linkable_title Troubleshooting %}
|
||||
|
||||
@ -135,7 +133,3 @@ If you see `Not initializing discovery because could not install dependency netd
|
||||
### {% linkable_title DSM and Synology %}
|
||||
|
||||
For DSM/Synology, install via debian-chroot [see this forum post](https://community.home-assistant.io/t/error-starting-home-assistant-on-synology-for-first-time/917/15).
|
||||
|
||||
## {% linkable_title New platforms %}
|
||||
|
||||
If you are developing a new platform, please read [how to make your platform discoverable](/developers/component_discovery/) for further details.
|
||||
|
||||
@ -50,6 +50,11 @@ faces:
|
||||
description: List of faces sources.
|
||||
required: true
|
||||
type: list
|
||||
confidence:
|
||||
description: How much distance between faces to consider it a match. Using tolerance values lower than 0.6 will make the comparison more strict.
|
||||
required: false
|
||||
type: float
|
||||
default: 0.6
|
||||
{% endconfiguration %}
|
||||
|
||||
<p class='note'>
|
||||
|
||||
206
source/_components/environment_canada.markdown
Normal file
206
source/_components/environment_canada.markdown
Normal file
@ -0,0 +1,206 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Environment Canada Weather"
|
||||
description: "Weather data from Environment Canada."
|
||||
date: 2019-06-01 10:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: environment_canada.png
|
||||
ha_category:
|
||||
- Weather
|
||||
- Sensor
|
||||
- Camera
|
||||
ha_release: 0.95
|
||||
ha_iot_class: Cloud Polling
|
||||
---
|
||||
|
||||
The `environment_canada` weather platforms provide meteorological data for Canadian locations from [Environment Canada](hhttps://weather.gc.ca/index_e.html).
|
||||
|
||||
The following device types and data are supported:
|
||||
|
||||
- [Weather](#weather) - Current conditions and forecasts
|
||||
- [Sensor](#sensor) - Current conditions and alerts
|
||||
- [Camera](#camera) - Radar imagery
|
||||
|
||||
## {% linkable_title Location Selection %}
|
||||
|
||||
Each platform automatically determines which weather station's data to use. However, as station coordinates provided by Environment Canada are somewhat imprecise, in some cases you may need to override the automatic selection to use the desired station.
|
||||
|
||||
For each platform, the location to use is determined according to the following hierarchy:
|
||||
|
||||
- Location ID specified in platform configuration (optional)
|
||||
- Closest station to latitude/longitude specified in platform configuration (optional
|
||||
- Closest station to latitude/longitude specified in Home Assistant core configuration
|
||||
|
||||
## {% linkable_title Weather %}
|
||||
|
||||
The `environment_canada` weather platform populates a weather card with Environment Canada current conditions and forecast [data](https://weather.gc.ca/canada_e.html).
|
||||
|
||||
To add Environment Canada weather to your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
weather:
|
||||
- platform: environment_canada
|
||||
```
|
||||
|
||||
- The sensor checks for new data every 10 minutes, and the source data is typically updated hourly within 10 minutes after the hour.
|
||||
- If no name is given, the weather entity will be named `weather.<station_name>`.
|
||||
- The platform automatically determines which weather station to use based on the system's latitude/longitude settings. For greater precision, it is also possible to specify either:
|
||||
- A specific station code based on [this CSV file](http://dd.weatheroffice.ec.gc.ca/citypage_weather/docs/site_list_towns_en.csv), or
|
||||
- A specific latitude/longitude
|
||||
|
||||
{% configuration %}
|
||||
latitude:
|
||||
description: Part of a set of coordinates to use when finding the closest weather station.
|
||||
required: inclusive
|
||||
type: float
|
||||
longitude:
|
||||
description: Part of a set of coordinates to use when finding the closest weather station.
|
||||
required: inclusive
|
||||
type: float
|
||||
station:
|
||||
description: The station code of a specific weather station to use. Station codes must be in the form `AB/s0000123`, where `AB`is a provincial abbreviation and `s0000123` is a numeric station code. If provided, this station will be used and any latitude/longitude coordinates provided will be ignored.
|
||||
required: false
|
||||
type: string
|
||||
name:
|
||||
description: Name to be used for the weather entity.
|
||||
required: false
|
||||
type: string
|
||||
forecast:
|
||||
description: Specify hourly or daily forecasts. Valid values are 'daily' and 'hourly'.
|
||||
required: false
|
||||
type: string
|
||||
default: daily
|
||||
{% endconfiguration %}
|
||||
|
||||
## {% linkable_title Sensor %}
|
||||
|
||||
The `environment_canada` sensor platform creates sensors based on Environment Canada [current conditions](https://weather.gc.ca/canada_e.html) and [alerts](https://weather.gc.ca/warnings/index_e.html).
|
||||
|
||||
To add Environment Canada sensors to your installation, add the desired lines from the following example to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: environment_canada
|
||||
```
|
||||
|
||||
- By default, a sensor entity is created for each monitored condition and each category of alert. Each sensor entity will be given the `device_id` of `sensor.<optional-name_><condition>`.
|
||||
- The sensor checks for new data every 10 minutes, and the source data is typically updated hourly within 10 minutes after the hour.
|
||||
- The platform automatically determines which weather station to use based on the system's latitude/longitude settings. For greater precision, it is also possible to specify either:
|
||||
- A specific station code based on [this CSV file](http://dd.weatheroffice.ec.gc.ca/citypage_weather/docs/site_list_towns_en.csv), or
|
||||
- A specific latitude/longitude
|
||||
|
||||
{% configuration %}
|
||||
latitude:
|
||||
description: Part of a set of coordinates to use when finding the closest weather station.
|
||||
required: inclusive
|
||||
type: float
|
||||
longitude:
|
||||
description: Part of a set of coordinates to use when finding the closest weather station.
|
||||
required: inclusive
|
||||
type: float
|
||||
station:
|
||||
description: The station code of a specific weather station to use. If provided, this station will be used and any latitude/longitude coordinates provided will be ignored. Station codes must be in the form of `AB/s0000123`, where `AB`is a provincial abbreviation and `s0000123` is a numeric station code.
|
||||
required: false
|
||||
type: string
|
||||
name:
|
||||
description: Name to be used for the sensor entities.
|
||||
required: false
|
||||
type: string
|
||||
monitored_conditions:
|
||||
description: The conditions to monitor. A sensor will be created for each condition.
|
||||
required: true
|
||||
type: list
|
||||
default: All keys
|
||||
keys:
|
||||
temperature:
|
||||
description: The current temperature, in ºC.
|
||||
dewpoint:
|
||||
description: The current dewpoint, in ºC.
|
||||
wind_chill:
|
||||
description: The current wind chill, in ºC.
|
||||
humidex:
|
||||
description: The current humidex, in ºC.
|
||||
pressure:
|
||||
description: The current air pressure, in kPa.
|
||||
tendency:
|
||||
description: The current air pressure tendency, e.g. "Rising" or "Falling".
|
||||
humidity:
|
||||
description: The current humidity, in %.
|
||||
visibility:
|
||||
description: The current visibility, in km.
|
||||
condition:
|
||||
description: A brief text statement of the current weather conditions, e.g. "Sunny".
|
||||
wind_speed:
|
||||
description: The current sustained wind speed, in km/h.
|
||||
wind_gust:
|
||||
description: The current wind gust, in km/h.
|
||||
wind_dir:
|
||||
description: The current cardinal wind direction, e.g. "SSW".
|
||||
high_temp:
|
||||
description: The next forecast high temperature, in ºC.
|
||||
low_temp:
|
||||
description: The next forecast low temperature, in ºC.
|
||||
pop:
|
||||
description: The next forecast probability of precipitation, in %.
|
||||
warnings:
|
||||
description: Current warning alerts.
|
||||
watches:
|
||||
description: Current watch alerts.
|
||||
advisories:
|
||||
description: Current advisory alerts.
|
||||
statements:
|
||||
description: Current special weather statements.
|
||||
endings:
|
||||
description: Alerts that have recently ended.
|
||||
{% endconfiguration %}
|
||||
|
||||
## {% linkable_title Camera %}
|
||||
|
||||
The `environment_canada` camera platform displays Environment Canada meteorological [radar imagery](https://weather.gc.ca/radar/index_e.html).
|
||||
|
||||
To add Environment Canada radar imagery to your installation, add the desired lines from the following example to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
camera:
|
||||
- platform: environment_canada
|
||||
```
|
||||
|
||||
- If no name is given, the camera entity will be named `camera.<station_name>_radar`.
|
||||
- The platform automatically determines which radar station to use based on the system's latitude/longitude settings. For greater precision, it is also possible to specify either:
|
||||
- A specific station ID from [this table](https://en.wikipedia.org/wiki/Canadian_weather_radar_network#List_of_radars) (remove the leading `C`, e.g. `XFT` or `ASBV`), or
|
||||
- A specific latitude/longitude
|
||||
|
||||
{% configuration %}
|
||||
latitude:
|
||||
description: Part of a set of coordinates to use when finding the closest radar station.
|
||||
required: inclusive
|
||||
type: float
|
||||
longitude:
|
||||
description: Part of a set of coordinates to use when finding the closest radar station.
|
||||
required: inclusive
|
||||
type: float
|
||||
station:
|
||||
description: The station code of a specific radar station to use. If provided, this station will be used and any latitude/longitude coordinates provided will be ignored.
|
||||
required: false
|
||||
type: string
|
||||
name:
|
||||
description: Name to be used for the camera entity.
|
||||
required: false
|
||||
type: string
|
||||
loop:
|
||||
description: Boolean setting to determine whether to display an animated GIF of images from the last 2 hours. If `false`, the latest still image will be displayed.
|
||||
required: false
|
||||
default: true
|
||||
type: boolean
|
||||
precip_type:
|
||||
description: Determines whether to use the intensity bands for rain or snow. Valid values are RAIN and SNOW.
|
||||
required: false
|
||||
type: string
|
||||
default: RAIN from April to October, SNOW from November to March
|
||||
{% endconfiguration %}
|
||||
@ -45,8 +45,12 @@ frontend:
|
||||
description: "List of additional [resources](/developers/frontend_creating_custom_ui/) to load in `latest` javascript mode."
|
||||
required: false
|
||||
type: list
|
||||
extra_html_url_es5:
|
||||
description: "List of additional [resources](/developers/frontend_creating_custom_ui/) to load in `es5` javascript mode."
|
||||
extra_module_url:
|
||||
description: "List of additional javascript modules to load."
|
||||
required: false
|
||||
type: list
|
||||
extra_js_url_es5:
|
||||
description: "List of additional javascript code to load in `es5` javascript mode."
|
||||
required: false
|
||||
type: list
|
||||
development_repo:
|
||||
|
||||
@ -17,7 +17,7 @@ ha_release: 0.92
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `geniushub` integration links Home Assistant with your Genius Hub for controlling its Zones and Devices. Currently, there is no support for Zone schedules.
|
||||
The `geniushub` integration links Home Assistant with your Genius Hub for controlling its Zones and Devices, and visibility of any Issues. Currently, there is no support for Zone schedules.
|
||||
|
||||
It uses the [geniushub-client](https://pypi.org/project/geniushub-client/) library.
|
||||
|
||||
@ -47,7 +47,24 @@ Each such entity will report back its primary state; in addition, `assigned_zone
|
||||
|
||||
There are three `Sensor` entities that will indicate the number of **Errors**, **Warnings** and **Information** issues.
|
||||
|
||||
Each such entity has a state attribute that will contain a list of any such issues. For example, `error_list`.
|
||||
Each such entity has a state attribute that will contain a list of any such issues which can be used in automations, etc. For example:
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
- alias: GeniusHub Error Alerts
|
||||
trigger:
|
||||
platform: numeric_state
|
||||
entity_id: sensor.errors
|
||||
above: 0
|
||||
action:
|
||||
- service: notify.pushbullet_notifier
|
||||
data_template:
|
||||
title: "Genius Hub has errors"
|
||||
message: >-
|
||||
Genius Hub has the following {{ states('sensor.errors') }} errors:
|
||||
{{ state_attr('sensor.errors', 'error_list') }}
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
### {% linkable_title State Attributes %}
|
||||
|
||||
@ -70,7 +87,7 @@ Other properties are available via each entity's state attributes. For example,
|
||||
This data can be accessed in automations, etc. via a value template. For example:
|
||||
|
||||
{% raw %}
|
||||
```
|
||||
```yaml
|
||||
value_template: "{{ state_attr('water_heater.boiler_h_w', 'status').override.setpoint }}"
|
||||
```
|
||||
{% endraw %}
|
||||
@ -78,7 +95,7 @@ value_template: "{{ state_attr('water_heater.boiler_h_w', 'status').override.set
|
||||
In the specific case of **Radiator** zones with room sensors:
|
||||
|
||||
{% raw %}
|
||||
```
|
||||
```yaml
|
||||
value_template: "{{ state_attr('climate.main_room', 'status').occupied }}"
|
||||
```
|
||||
{% endraw %}
|
||||
@ -91,7 +108,7 @@ To add your Genius Hub into your Home Assistant installation, add one of the fol
|
||||
|
||||
- requires a **hub token** obtained from [my.geniushub.co.uk/tokens](https://my.geniushub.co.uk/tokens)
|
||||
- uses the v1 API - which is well-documented
|
||||
- polls Heat Genius' own servers (so is slower, say 5-10s response time)
|
||||
- polls Heat Genius' own servers (so is slower, say ~5-10s response time)
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry, using a Hub Token
|
||||
@ -102,8 +119,8 @@ geniushub:
|
||||
### {% linkable_title Option 2: hub hostname/address with user credentials %}
|
||||
|
||||
- requires your **username** & **password**, as used with [www.geniushub.co.uk/app](https://www.geniushub.co.uk/app)
|
||||
- uses the v3 API - results are WIP and may not be what you expect
|
||||
- polls the hub directly (so is faster, say 1s response time)
|
||||
- uses the v3 API - unofficial, but there are additional features (e.g., battery levels)
|
||||
- polls the hub directly (so is faster, say ~1s response time)
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry, directly polling the Hub
|
||||
@ -117,19 +134,19 @@ Note that if a `host` is used instead of `token`, then the `username` and `passw
|
||||
|
||||
{% configuration %}
|
||||
token:
|
||||
description: The Hub Token of the Genius Hub
|
||||
description: The Hub Token of the Genius Hub.
|
||||
required: true
|
||||
type: string
|
||||
host:
|
||||
description: The hostname/IP address of the Genius Hub
|
||||
description: The hostname/IP address of the Genius Hub.
|
||||
required: true
|
||||
type: string
|
||||
username:
|
||||
description: Your Genius Hub username
|
||||
description: Your Genius Hub username.
|
||||
required: false
|
||||
type: string
|
||||
password:
|
||||
description: Your Genius Hub password
|
||||
description: Your Genius Hub password.
|
||||
required: false
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -24,6 +24,7 @@ The [Geolocation trigger](/docs/automation/trigger/#geolocation-trigger) can be
|
||||
| GeoJSON Events | `geo_json_events` |
|
||||
| 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` |
|
||||
|
||||
Conditions can be used to further filter entities, for example by inspecting their state attributes.
|
||||
|
||||
140
source/_components/google_cloud.markdown
Normal file
140
source/_components/google_cloud.markdown
Normal file
@ -0,0 +1,140 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Google Cloud Platform"
|
||||
description: "Google Cloud Platform integration."
|
||||
date: 2019-05-02 12:08
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: google_cloud.png
|
||||
ha_category: Text-to-speech
|
||||
ha_release: 0.95
|
||||
---
|
||||
|
||||
The `google_cloud` platform allows you to use [Google Cloud Platform](https://cloud.google.com/) API and integrate them into Home Assistant.
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To use Google Cloud Platform, you need to provide `config` directory relative path of [`API key`](#obtaining-api-key) file you are going to use. Place it under `config` folder and set `key_file` parameter in `configuration.yaml`:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
tts:
|
||||
- platform: google_cloud
|
||||
key_file: googlecloud.json
|
||||
```
|
||||
|
||||
## {% linkable_title Obtaining an API key %}
|
||||
|
||||
API key obtaining process described in corresponding documentation:
|
||||
|
||||
* [Text-to-Speach](https://cloud.google.com/text-to-speech/docs/quickstart-protocol)
|
||||
* [Speach-to-Text](https://cloud.google.com/speech-to-text/docs/quickstart-protocol)
|
||||
* [Geocoding](https://developers.google.com/maps/documentation/geocoding/start)
|
||||
|
||||
Basic instruction for all APIs:
|
||||
|
||||
1. Visit [Cloud Resource Manager](https://console.cloud.google.com/cloud-resource-manager).
|
||||
2. Click `CREATE PROJECT` button at the top.
|
||||
3. Specify convenient `Project name` and click `CREATE` button.
|
||||
4. [Make sure that billing is enabled for your Google Cloud Platform project](https://cloud.google.com/billing/docs/how-to/modify-project).
|
||||
5. Enable needed Cloud API visiting one of the links below or [APIs library](https://console.cloud.google.com/apis/library), selecting your `Project` from the dropdown list and clicking the `Continue` button:
|
||||
|
||||
* [Text-to-Speech](https://console.cloud.google.com/flows/enableapi?apiid=texttospeech.googleapis.com)
|
||||
* [Speech-to-Text](https://console.cloud.google.com/flows/enableapi?apiid=speech.googleapis.com)
|
||||
* [Geocoding](https://console.cloud.google.com/flows/enableapi?apiid=geocoding-backend.googleapis.com)
|
||||
|
||||
6. Set up authentication:
|
||||
|
||||
1. Visit [this link](https://console.cloud.google.com/apis/credentials/serviceaccountkey)
|
||||
2. From the `Service account` list, select `New service account`.
|
||||
3. In the `Service account name` field, enter any name.
|
||||
|
||||
If you are requesting Text-to-Speech API key:
|
||||
|
||||
4. Don't select a value from the Role list. **No role is required to access this service**.
|
||||
5. Click `Create`. A note appears, warning that this service account has no role.
|
||||
6. Click `Create without role`. A JSON file that contains your `API key` downloads to your computer.
|
||||
|
||||
## {% linkable_title Google Cloud Text-to-Speech %}
|
||||
|
||||
[Google Cloud Text-to-Speech](https://cloud.google.com/text-to-speech/) converts text into human-like speech in more than 100 voices across 20+ languages and variants. It applies groundbreaking research in speech synthesis (WaveNet) and Google's powerful neural networks to deliver high-fidelity audio. With this easy-to-use API, you can create lifelike interactions with your users that transform customer service, device interaction, and other applications.
|
||||
|
||||
### {% linkable_title Pricing %}
|
||||
|
||||
The Cloud Text-to-Speech API is priced monthly based on the amount of characters to synthesize into audio sent to the service.
|
||||
|
||||
| Feature | Monthly free tier | Paid usage |
|
||||
|-------------------------------|---------------------------|-----------------------------------|
|
||||
| Standard (non-WaveNet) voices | 0 to 4 million characters | $4.00 USD / 1 million characters |
|
||||
| WaveNet voices | 0 to 1 million characters | $16.00 USD / 1 million characters |
|
||||
|
||||
### {% linkable_title Text-to-Speach configuration %}
|
||||
|
||||
{% configuration %}
|
||||
key_file:
|
||||
description: "The [`API key`](#obtaining-api-key) file to use with Google Cloud Platform. If not specified `os.environ['GOOGLE_APPLICATION_CREDENTIALS']` path will be used."
|
||||
required: false
|
||||
type: string
|
||||
language:
|
||||
description: "Default language of the voice, e.g. `en-US`. Supported languages, genders and voices listed [here](https://cloud.google.com/text-to-speech/docs/voices)."
|
||||
required: false
|
||||
type: string
|
||||
default: en-US
|
||||
gender:
|
||||
description: "Default gender of the voice, e.g. `male`. Supported languages, genders and voices listed [here](https://cloud.google.com/text-to-speech/docs/voices)."
|
||||
required: false
|
||||
type: string
|
||||
default: neutral
|
||||
voice:
|
||||
description: "Default voice name, e.g. `en-US-Wavenet-F`. Supported languages, genders and voices listed [here](https://cloud.google.com/text-to-speech/docs/voices). **Important! This parameter will override `language` and `gender` parameters if set**."
|
||||
required: false
|
||||
type: string
|
||||
encoding:
|
||||
description: "Default audio encoder. Supported encodings are `ogg_opus`, `mp3` and `linear16`."
|
||||
required: false
|
||||
type: string
|
||||
default: ogg_opus
|
||||
speed:
|
||||
description: "Default rate/speed of the voice, in the range [0.25, 4.0]. 1.0 is the normal native speed supported by the specific voice. 2.0 is twice as fast, and 0.5 is half as fast. If unset(0.0), defaults to the native 1.0 speed."
|
||||
required: false
|
||||
type: float
|
||||
default: 1.0
|
||||
pitch:
|
||||
description: "Default pitch of the voice, in the range [-20.0, 20.0]. 20 means increase of 20 semitones from the original pitch. -20 means decrease of 20 semitones from the original pitch."
|
||||
required: false
|
||||
type: float
|
||||
default: 0.0
|
||||
gain:
|
||||
description: "Default volume gain (in dB) of the voice, in the range [-96.0, 16.0]. If unset, or set to a value of 0.0 (dB), will play at normal native signal amplitude. A value of -6.0 (dB) will play at approximately half the amplitude of the normal native signal amplitude. A value of +6.0 (dB) will play at approximately twice the amplitude of the normal native signal amplitude. Strongly recommend not to exceed +10 (dB) as there's usually no effective increase in loudness for any value greater than that."
|
||||
required: false
|
||||
type: float
|
||||
default: 0.0
|
||||
profiles:
|
||||
description: "An identifier which selects 'audio effects' profiles that are applied on (post synthesized) text to speech. Effects are applied on top of each other in the order they are given. Supported profile ids listed [here](https: //cloud.google.com/text-to-speech/docs/audio-profiles)."
|
||||
required: false
|
||||
type: list
|
||||
default: "[]"
|
||||
{% endconfiguration %}
|
||||
|
||||
### {% linkable_title Full configuration example %}
|
||||
|
||||
The Google Cloud Text-to-Speech configuration can look like:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
tts:
|
||||
- platform: google_cloud
|
||||
key_file: googlecloud.json
|
||||
language: en-US
|
||||
gender: male
|
||||
voice: en-US-Wavenet-F
|
||||
encoding: linear16
|
||||
speed: 0.9
|
||||
pitch: -2.5
|
||||
gain: -5.0
|
||||
profiles:
|
||||
- telephony-class-application
|
||||
- wearable-class-device
|
||||
```
|
||||
@ -88,7 +88,7 @@ authtoken:
|
||||
## {% linkable_title Implemented and tested devices %}
|
||||
|
||||
* homematicip_cloud.alarm_control_panel
|
||||
* Security zones (*HmIP-SecurityZone*)
|
||||
* Combined Alarm Control Panal with INTERNAL and EXTERNAL Security zones (*HmIP-SecurityZone*)
|
||||
|
||||
* homematicip_cloud.binary_sensor
|
||||
* Window and door contact (*HmIP-SWDO, -I*)
|
||||
|
||||
@ -16,54 +16,67 @@ redirect_from:
|
||||
- /components/climate.honeywell/
|
||||
---
|
||||
|
||||
The `honeywell` climate platform lets you control Honeywell TCC (Total Connect Comfort) climate systems from Home Assistant. It does not integrate with Honeywell TCC alarm systems.
|
||||
|
||||
The `honeywell` climate platform let you control Honeywell Connected thermostats from Home Assistant.
|
||||
<p class='note'>
|
||||
There is some potential confusion over this integration because it is currently implemented as a combination of two _distinct_ climate systems, one being US-based, the other is EU-based.
|
||||
|
||||
To set it up, add the following information to your `configuration.yaml` file:
|
||||
These two regions are _not_ interchangeable, so you must be clear which applies to your climate system.
|
||||
</p>
|
||||
|
||||
## {% linkable_title US-based Systems %}
|
||||
|
||||
These systems are based in North America, and temperatures are usually in Fahrenheit. They would likely be HVAC systems. They always use the [somecomfort](https://github.com/kk7ds/somecomfort) client library. In this integration, this is called the `us` region.
|
||||
|
||||
If your system is US-based, then you can access your system via [https://mytotalconnectcomfort.com/portal/](https://mytotalconnectcomfort.com/portal/) (note the `/portal/`).
|
||||
|
||||
## {% linkable_title EU-based Systems %}
|
||||
|
||||
These systems are based in Europe (including the UK & Ireland), and temperatures are usually in Celsius. They would likely be heating-only systems. They always use the [evohome-client](https://github.com/watchforstock/evohome-client) client library. In this integration, this is called the `eu` region.
|
||||
|
||||
If your system is US-based, then you can access it via [https://international.mytotalconnectcomfort.com/](https://international.mytotalconnectcomfort.com/) (note the `international`).
|
||||
|
||||
The `eu` region is soon to be deprecated, and ongoing support for such systems is available via the [evohome](/components/evohome/) integration.
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To set up this integration, first confirm your region, then add the following information to your **configuration.yaml** file (the below example is for US-based systems):
|
||||
|
||||
```yaml
|
||||
climate:
|
||||
- platform: honeywell
|
||||
username: YOUR_USERNAME
|
||||
password: YOUR_PASSWORD
|
||||
scan_interval: 600
|
||||
region: us
|
||||
```
|
||||
<p class='note'>
|
||||
Scan interval is expressed in seconds. Omitting or mis-configuring `scan_interval` may result in too-frequent polling and cause you to be rate-limited by Honeywell.
|
||||
</p>
|
||||
|
||||
{% configuration %}
|
||||
username:
|
||||
description: The username of an user with access.
|
||||
description: Email address of an account with access the TCC website for your region.
|
||||
required: true
|
||||
type: string
|
||||
password:
|
||||
description: The password for your given admin account.
|
||||
description: Password for the account.
|
||||
required: true
|
||||
type: string
|
||||
region:
|
||||
description: Region identifier (either 'eu' or 'us'). Use the `somecomfort` client library for `us`, and evohome-client for `eu`.
|
||||
description: Region identifier, either 'eu' or 'us'.
|
||||
required: false
|
||||
default: eu
|
||||
type: string
|
||||
scan_interval:
|
||||
description: Scan interval is expressed in seconds. Recommended value of 600 seconds. Omitting scan_interval may result in too-frequent polling and cause you to rate-limited by Honeywell.
|
||||
required: false
|
||||
default: 120
|
||||
type: integer
|
||||
away_temperature:
|
||||
description: "(*only for eu region*) Heating setpoint when away mode is on, in deg C."
|
||||
description: "(*only for the EU region*) Heating setpoint when away mode is on, in degrees Celsius."
|
||||
required: false
|
||||
default: 16.0
|
||||
type: float
|
||||
away_cool_temperature:
|
||||
description: "(*only for us region*) Cooling setpoint when away mode is on, in deg C."
|
||||
description: "(*only for the US region*) Cooling setpoint when away mode is on, in degrees Fahrenheit."
|
||||
required: false
|
||||
default: 30.0
|
||||
type: float
|
||||
default: 88
|
||||
type: integer
|
||||
away_heat_temperature:
|
||||
description: "(*only for us region*) Heating setpoint when away mode is on, in deg C."
|
||||
description: "(*only for the US region*) Heating setpoint when away mode is on, in degrees Fahrenheit."
|
||||
required: false
|
||||
default: 16.0
|
||||
type: float
|
||||
default: 61
|
||||
type: integer
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -10,25 +10,56 @@ footer: true
|
||||
logo: incomfort.png
|
||||
ha_category:
|
||||
- Water heater
|
||||
- Climate
|
||||
- Sensor
|
||||
- Binary sensor
|
||||
ha_release: 0.93
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `incomfort` integration links Home Assistant with your Intergas Lan2RF gateway for controlling water_heater devices (the hub does not have to be in the same network as HA).
|
||||
The `incomfort` integration links Home Assistant with your Intergas Lan2RF gateway for integrating the boiler and any room thermostats attached to it.
|
||||
|
||||
The **Water Heater** device will report back the `state` and `temperature`. Other properties are available via the device's attributes.
|
||||
The boiler is represented as a **Water Heater** device. It will report the boiler's `state` and `temperature` (current temperature). The gateway does not expose any means to directly control the boiler or change its configuration.
|
||||
|
||||
In the future, other entities will be added to this integration (e.g. a **Sensor** for CV pressure, and a **Climate** device for room temperature).
|
||||
Note that the `temperature` will switch between the CV and Tap temperatures according to the current operating mode of the boiler. If the boiler is neither pumping nor tapping, it will be reported as the higher of the two.
|
||||
|
||||
Any room thermostats (there can be 0, 1 or 2) are represented as **Climate** devices. They will report the thermostat's `target_temperature` (setpoint) and `current_temperature` and the setpoint can be changed.
|
||||
|
||||
In addition, there is a **Sensor** for CV pressure, CV temperature, and Tap temperature, and a **Binary Sensor** that will be `on` if there is a fault with the boiler (the fault code will be a state attribute).
|
||||
|
||||
To send an alert if the CV pressure is too low or too high, consider the following automation:
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
- alias: Low CV Pressure Alert
|
||||
trigger:
|
||||
platform: numeric_state
|
||||
entity_id: sensor.cv_pressure
|
||||
below: 1.0
|
||||
action:
|
||||
- service: notify.pushbullet_notifier
|
||||
data_template:
|
||||
title: "Warning: Low CH Pressure"
|
||||
message: >-
|
||||
{{ trigger.to_state.attributes.friendly_name }}
|
||||
is low, {{ trigger.to_state.state }} bar.
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
Other properties are available via each device's attributes.
|
||||
|
||||
### {% linkable_title Configuration %}
|
||||
|
||||
To add your Lan2RF gateway into your Home Assistant installation, add one of the following to your `configuration.yaml` file.
|
||||
|
||||
Older gateways do not require user authentication:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry, older firmware with no user credentials
|
||||
incomfort:
|
||||
host: IP_ADDRESS
|
||||
```
|
||||
|
||||
Alternatively, if a **username** & **password** is printed on the back of the gateway:
|
||||
|
||||
```yaml
|
||||
@ -39,17 +70,19 @@ incomfort:
|
||||
password: PASSWORD
|
||||
```
|
||||
|
||||
The hub does not have to be in the same network as HA.
|
||||
|
||||
{% configuration %}
|
||||
host:
|
||||
description: The hostname/IP address of the Lan2RF gateway
|
||||
description: The hostname/IP address of the Lan2RF gateway.
|
||||
required: true
|
||||
type: string
|
||||
username:
|
||||
description: The username of the Lan2RF gateway
|
||||
description: The username of the Lan2RF gateway, if any.
|
||||
required: inclusive
|
||||
type: string
|
||||
password:
|
||||
description: The password of the Lan2RF gateway
|
||||
description: The password of the Lan2RF gateway, if any.
|
||||
required: inclusive
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -14,6 +14,7 @@ ha_category:
|
||||
- Climate
|
||||
- Cover
|
||||
- Light
|
||||
- Scene
|
||||
- Sensor
|
||||
- Switch
|
||||
ha_release: 0.85
|
||||
@ -35,6 +36,7 @@ There is currently support for the following device types within Home Assistant:
|
||||
- [Climate](#climate)
|
||||
- [Cover](#cover)
|
||||
- [Light](#light)
|
||||
- [Scene](#scene)
|
||||
- [Sensor](#sensor)
|
||||
- [Switch](#switch)
|
||||
|
||||
@ -86,6 +88,14 @@ lcn:
|
||||
dimmable: true
|
||||
transition: 5
|
||||
|
||||
scenes:
|
||||
- name: Romantic
|
||||
address: myhome.s0.m7
|
||||
register: 1
|
||||
scene: 4
|
||||
outputs: [output1, output2, relais1, relais3, relais4]
|
||||
transition: 5
|
||||
|
||||
sensors:
|
||||
- name: Temperature
|
||||
address: myhome.s0.m7
|
||||
@ -242,6 +252,37 @@ lights:
|
||||
type: int
|
||||
default: 0
|
||||
|
||||
scenes:
|
||||
description: List of your scenes.
|
||||
required: false
|
||||
type: map
|
||||
keys:
|
||||
name:
|
||||
description: "Name of the scene."
|
||||
required: true
|
||||
type: string
|
||||
address:
|
||||
description: "[Address](#lcn-addresses) of the module/group."
|
||||
required: true
|
||||
type: string
|
||||
register:
|
||||
description: Number of scene register (0..9).
|
||||
required: true
|
||||
type: int
|
||||
scene:
|
||||
description: Number of scene (0..9).
|
||||
required: true
|
||||
type: int
|
||||
outputs:
|
||||
description: "List of ports ([OUTPUT_PORT](#ports), [RELAY_PORT](#ports))."
|
||||
required: false
|
||||
type: list
|
||||
transition:
|
||||
description: Transition (ramp) time in seconds.
|
||||
required: false
|
||||
type: int
|
||||
default: None
|
||||
|
||||
sensors:
|
||||
description: List of your sensors.
|
||||
required: false
|
||||
@ -398,6 +439,10 @@ The `lcn` light platform allows the control of the following [LCN](http://www.lc
|
||||
- (Dimmable) output ports
|
||||
- Relays
|
||||
|
||||
### {% linkable_title Scene %}
|
||||
|
||||
The `lcn` scene platform allows the activation of previously programmed [LCN](http://www.lcn.eu) scenes.
|
||||
|
||||
### {% linkable_title Sensor %}
|
||||
|
||||
The `lcn` sensor platform allows the monitoring of the following [LCN](http://www.lcn.eu) data sources:
|
||||
|
||||
246
source/_components/life360.markdown
Normal file
246
source/_components/life360.markdown
Normal file
@ -0,0 +1,246 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Life360"
|
||||
description: "Instructions how to use Life360 to track devices in Home Assistant."
|
||||
date: 2019-04-24 16:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: life360.png
|
||||
ha_release: 0.95
|
||||
ha_category:
|
||||
- Presence Detection
|
||||
ha_iot_class: Cloud Polling
|
||||
---
|
||||
|
||||
The `life360` integration allows you to detect presence using the [unofficial API](#disclaimer) of [Life360](https://www.life360.com/).
|
||||
|
||||
## {% linkable_title Life360 Account %}
|
||||
|
||||
You must first [create a Life360 account](https://www.life360.com/websignup).
|
||||
|
||||
Then in the Home Assistant user interface (UI), click on Configuration in the left pane, then on Integrations and then on the yellow circle in the lower-right corner to "Set up a new integration." Scroll through the list and click on Life360. Enter your Life360 username and password and click SUBMIT. You can add as many Life360 accounts as you like.
|
||||
|
||||
If you would like to set any advanced options, see the following section. You may want to do this before entering your Life360 account information in the UI, or you can change it at any time. You can also enter your account information in the configuration file (in addition to, or instead of, the UI) if you prefer.
|
||||
|
||||
{% configuration %}
|
||||
accounts:
|
||||
description: Your Life360 account information.
|
||||
required: false
|
||||
type: [list, map]
|
||||
default: None
|
||||
keys:
|
||||
username:
|
||||
description: Your Life360 username.
|
||||
required: true
|
||||
type: string
|
||||
password:
|
||||
description: Your Life360 password.
|
||||
required: true
|
||||
type: string
|
||||
circles:
|
||||
description: See [Filtering](#filtering) for a detailed description. Must specify **include** or **exclude**, but not both.
|
||||
required: false
|
||||
type: map
|
||||
default: Include all Circles.
|
||||
keys:
|
||||
include:
|
||||
description: Circles to include.
|
||||
required: false
|
||||
type: [string, list]
|
||||
exclude:
|
||||
description: Circles to exclude.
|
||||
required: false
|
||||
type: [string, list]
|
||||
driving_speed:
|
||||
description: The minimum speed at which the device is considered to be "driving" (which can also set the `driving` [attribute](#additional-attributes) to `true`.) MPH or KPH, depending on Home Assistant's unit system configuration.
|
||||
required: false
|
||||
type: float
|
||||
default: "\"Driving\" determined strictly by Life360."
|
||||
error_threshold:
|
||||
description: See [Communication Errors](#communication-errors) for a detailed description.
|
||||
required: false
|
||||
type: integer
|
||||
interval_seconds:
|
||||
description: This defines how often the Life360 server will be queried (in seconds.) The resulting device_tracker entities will actually only be updated when the Life360 server provides new location information for each member.
|
||||
required: false
|
||||
type: integer
|
||||
default: 12
|
||||
max_gps_accuracy:
|
||||
description: If specified, and the reported GPS accuracy is larger (i.e., *less* accurate), then update is ignored.
|
||||
required: false
|
||||
type: float
|
||||
max_update_wait:
|
||||
description: If specified and Life360 does not provide an update for a member within that maximum time window, an event named `life360_update_overdue` will be fired with the `entity_id` of the corresponding member's device_tracker entity. Once an update does come, an event named `life360_update_restored` will be fired with the `entity_id` of the corresponding member's device_tracker entity and another data item named `wait` that will indicate the amount of time spent waiting for the update. You can use these events in automations to be notified when they occur. See [example automations](#example-overdue-update-automations) below.
|
||||
required: false
|
||||
type: time
|
||||
members:
|
||||
description: See [Filtering](#filtering) for a detailed description. Must specify **include** or **exclude**, but not both.
|
||||
required: false
|
||||
type: map
|
||||
default: Include all Members from all included Circles.
|
||||
keys:
|
||||
include:
|
||||
description: Members to include.
|
||||
required: false
|
||||
type: [string, list]
|
||||
exclude:
|
||||
description: Members to exclude.
|
||||
required: false
|
||||
type: [string, list]
|
||||
prefix:
|
||||
description: Device ID prefix. Entity IDs will be in the form of `device_tracker.PREFIX_FIRST_LAST`, or `device_tracker.PREFIX_NAME` if the Member has only one name. To use no prefix, specify `''`.
|
||||
required: false
|
||||
type: string
|
||||
default: life360
|
||||
show_as_state:
|
||||
description: If device is not in a Home Assistant zone, it is determined to be driving (see attribute of same name) and `driving` is specified, the state of entity will be set to `driving`. If device is not in a zone, it is determined to be moving and `moving` is specified, then state of entity will be set to `moving`.
|
||||
required: false
|
||||
type: [string, list]
|
||||
warning_threshold:
|
||||
description: See [Communication Errors](#communication-errors) for a detailed description.
|
||||
required: false
|
||||
type: integer
|
||||
{% endconfiguration %}
|
||||
|
||||
## {% linkable_title Additional attributes %}
|
||||
|
||||
Attribute | Description
|
||||
-|-
|
||||
address | Address of the current location, or `none`.
|
||||
at_loc_since | Date and time when first at current location (in UTC.)
|
||||
battery_charging | Device is charging (`true`/`false`.)
|
||||
driving | Device movement indicates driving (`true`/`false`.)
|
||||
last_seen | Date and time when Life360 last updated device location (in UTC.)
|
||||
moving | Device is moving (`true`/`false`.)
|
||||
place | Name of Life360 Place where the device is located, or `none` if not located within one.
|
||||
raw_speed | "Raw" speed value provided by Life360 server. (Units unknown.)
|
||||
speed | Estimated speed of device (in MPH or KPH depending on Home Assistant's unit system configuration.)
|
||||
wifi_on | Device WiFi is turned on (`true`/`false`.)
|
||||
|
||||
## {% linkable_title Filtering %}
|
||||
|
||||
For most users, filtering is not needed, and in such cases, the corresponding configuration variables should not be used.
|
||||
|
||||
However, in some circumstances, it might be helpful to limit which Life360 Circles and/or Members are used. For these cases [**circles**](#circles) and/or [**members**](#members) can be used.
|
||||
|
||||
**circles** can limit which Life360 Circles are used.
|
||||
|
||||
**members** can limit which Life360 Members will be tracked.
|
||||
|
||||
For a particular Member to be tracked, they must be included (or at least not excluded), and must be in at least one of the included Circles. See [example configuration](#circle-and-member-filtering-example) below.
|
||||
|
||||
Note that Life360's app and website typically only show Members' first names. However, you must use their _full_ names here. If you're not sure what a Member's full name (i.e., first and last) is in Life360, ask them. Alternatively, you can set the [`logger`](https://www.home-assistant.io/components/logger/) to `debug` and look in `home-assistant.log`. The full names of all Life360 Circles & Members will be logged.
|
||||
|
||||
## {% linkable_title Home - Home Assistant vs. Life360 %}
|
||||
|
||||
Normally Home Assistant device trackers are "Home" when they enter `zone.home`. Also, Life360 normally considers your device "Home" when it enters the Place that coincides with your home. Since the definitions of these areas can be different, this can lead to a disagreement between Home Assistant and Life360 as to whether or not you're "Home." To avoid this, make sure these two areas are defined the same -- i.e., same location and radius. (See next section.)
|
||||
|
||||
## {% linkable_title Home Assistant Zones & Life360 Places %}
|
||||
|
||||
See [Zone documentation](https://www.home-assistant.io/components/zone/#home-zone) for details about how HA zones are defined. If you'd like to create HA zones from Life360 Places (e.g., to make HA's `zone.home` be identical to Life360's "Home Place"), make sure `logger` is set to `debug`. Then when HA starts the details of all the Places defined in the included Circles will be written to `home-assistant.log` in a format that can be copied into your configuration under `zone:`. E.g., you would see something like this:
|
||||
|
||||
```text
|
||||
2019-05-31 12:16:58 DEBUG (SyncWorker_3) [homeassistant.components.life360.device_tracker] My Family Circle: will be included, id=xxxxx
|
||||
2019-05-31 12:16:58 DEBUG (SyncWorker_3) [homeassistant.components.life360.device_tracker] Circle's Places:
|
||||
- name: Home
|
||||
latitude: XX.XXX
|
||||
longitude: YY.YYY
|
||||
radius: ZZZ
|
||||
```
|
||||
|
||||
## {% linkable_title Communication Errors %}
|
||||
|
||||
It is not uncommon for communication errors to occur between Home Assistant and the Life360 server. This can happen for many reasons, including Internet connection issues, Life360 server load, etc. However, in most cases, they are temporary and do not significantly affect the ability to keep device_tracker entities up to date.
|
||||
|
||||
Therefore, an optional filtering mechanism has been implemented to prevent inconsequential communication errors from filling the log, while still logging unusual error activity. Two thresholds are defined: [**warning_threshold**](#warning_threshold) and [**error_threshold**](#error_threshold). When a particular type of communication error happens on consecutive update cycles, it will not be logged until the number of occurrences reaches these thresholds. When the number reaches **warning_threshold** (but does not exceed **error_threshold**, and only if **warning_threshold** is defined), it will be logged as a WARNING. Once the number reaches **error_threshold**, it will be logged as an ERROR. Only two consecutive communication errors of a particular type will be logged as an ERROR, after which it will no longer be logged until it stops occurring and then happens again.
|
||||
|
||||
## {% linkable_title Examples %}
|
||||
|
||||
### {% linkable_title Typical configuration %}
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
life360:
|
||||
# MPH, assuming imperial units.
|
||||
# If using metric (KPH), the equivalent would be 29.
|
||||
driving_speed: 18
|
||||
interval_seconds: 10
|
||||
max_gps_accuracy: 200
|
||||
max_update_wait:
|
||||
minutes: 45
|
||||
show_as_state:
|
||||
- driving
|
||||
- moving
|
||||
# Set comm error thresholds so first is not logged,
|
||||
# second is logged as a WARNING, and third and fourth
|
||||
# are logged as ERRORs.
|
||||
warning_threshold: 2
|
||||
error_threshold: 3
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
### {% linkable_title Circle and Member Filtering Example %}
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
life360:
|
||||
# Only track Members that are in these Circles.
|
||||
circles:
|
||||
include: [My Family, Friends]
|
||||
# But do not track this Member.
|
||||
members:
|
||||
exclude: John Doe
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
### {% linkable_title Entering accounts in configuration %}
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
life360:
|
||||
accounts:
|
||||
- username: LIFE360_USERNAME
|
||||
password: LIFE360_PASSWORD
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
### {% linkable_title Example overdue update automations %}
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
automation:
|
||||
- alias: Life360 Overdue Update
|
||||
trigger:
|
||||
platform: event
|
||||
event_type: life360_update_overdue
|
||||
action:
|
||||
service: notify.email_me
|
||||
data_template:
|
||||
title: Life360 update overdue
|
||||
message: >
|
||||
Update for {{
|
||||
state_attr(trigger.event.data.entity_id, 'friendly_name') or
|
||||
trigger.event.data.entity_id
|
||||
}} is overdue.
|
||||
|
||||
- alias: Life360 Update Restored
|
||||
trigger:
|
||||
platform: event
|
||||
event_type: life360_update_restored
|
||||
action:
|
||||
service: notify.email_me
|
||||
data_template:
|
||||
title: Life360 update restored
|
||||
message: >
|
||||
Update for {{
|
||||
state_attr(trigger.event.data.entity_id, 'friendly_name') or
|
||||
trigger.event.data.entity_id
|
||||
}} restored after {{ trigger.event.data.wait }}.
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
## {% linkable_title Disclaimer %}
|
||||
|
||||
It does not appear that Life360 officially supports its REST API for use with other than its own apps. This integration is based on reverse engineering that has been done by the open source community, and an API token that was somehow discovered by the same community. At any time Life360 could disable that token or otherwise change its REST API such that this component would no longer work.
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Linky Sensor"
|
||||
description: "Instructions on how to integrate Linky daily data within Home Assistant."
|
||||
description: "Instructions on how to integrate Linky consumption data within Home Assistant."
|
||||
date: 2018-09-06 08:35
|
||||
sidebar: true
|
||||
comments: false
|
||||
@ -11,16 +11,19 @@ logo: enedis.png
|
||||
ha_release: 0.79
|
||||
ha_category:
|
||||
- Energy
|
||||
- Sensor
|
||||
ha_iot_class: Cloud Polling
|
||||
redirect_from:
|
||||
- /components/sensor.linky/
|
||||
---
|
||||
|
||||
The `linky` sensor platform is showing the last day consumption of your home from the [Linky electric meter](https://www.enedis.fr/english).
|
||||
The `linky` sensor platform is retrieving the consumption of your home from the [Linky electric meter](https://www.enedis.fr/linky-compteur-communicant).
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To add the Linky sensor to your installation, add your Enedis account credentials to your `configuration.yaml` file:
|
||||
First, you need to create an Enedis account [here](https://espace-client-connexion.enedis.fr/auth/UI/Login?realm=particuliers), if you don't have already one.
|
||||
|
||||
And then, add the Linky sensor to your `configuration.yaml` file like below:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
@ -39,4 +42,9 @@ password:
|
||||
description: The Enedis account password.
|
||||
required: true
|
||||
type: string
|
||||
timeout:
|
||||
description: Timeout to wait for the Enedis API connection.
|
||||
required: false
|
||||
type: integer
|
||||
default: 10
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -47,6 +47,11 @@ code_template:
|
||||
Only one of **code** and **code_template** can be specified.
|
||||
required: exclusive
|
||||
type: string
|
||||
code_arm_required:
|
||||
description: If true, the code is required to arm the alarm.
|
||||
required: false
|
||||
type: boolean
|
||||
default: true
|
||||
delay_time:
|
||||
description: The time in seconds of the pending time before triggering the alarm.
|
||||
required: false
|
||||
|
||||
@ -69,6 +69,12 @@ code_template:
|
||||
Only one of **code** and **code_template** can be specified.
|
||||
required: exclusive
|
||||
type: string
|
||||
code_arm_required:
|
||||
description: >
|
||||
If true, the code is required to arm the alarm. If false, the code is not validated.
|
||||
required: false
|
||||
type: boolean
|
||||
default: true
|
||||
delay_time:
|
||||
description: The time in seconds of delay added to the triggered state's **pending_time** before triggering the alarm.
|
||||
required: false
|
||||
|
||||
@ -26,7 +26,7 @@ There is currently support for the following device types within Home Assistant:
|
||||
- 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.
|
||||
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](http://vigilance.meteofrance.com)
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
@ -66,6 +66,8 @@ meteo_france:
|
||||
description: Probability of snow for the day.
|
||||
thunder_chance:
|
||||
description: Probability of thunderstorm for the day.
|
||||
weather_alert:
|
||||
description: Weather alert status.
|
||||
{% endconfiguration %}
|
||||
|
||||
### {% linkable_title About `city` configuration %}
|
||||
@ -103,6 +105,16 @@ Possible value for each intervals attributes are:
|
||||
- 3 Moderate rain
|
||||
- 4 Heavy rain
|
||||
|
||||
### {% linkable_title About `weather_alert` sensor %}
|
||||
|
||||
<p class='note warning'>
|
||||
The weather alert is available for the metropolitan France.
|
||||
</p>
|
||||
|
||||
The `weather_alert` sensor value give the current weather alert status for the department linked to the city. Data is retrieve from [Météo-France vigilance website](http://vigilance.meteofrance.com/).
|
||||
|
||||
The sensor attributes give access to each type of alerts and date of the bulletin emitted by Météo-France.
|
||||
|
||||
### {% linkable_title Complete example %}
|
||||
|
||||
This is an example for 3 cities forecast with different monitored conditions:
|
||||
@ -121,6 +133,7 @@ meteo_france:
|
||||
- wind_speed
|
||||
- temperature
|
||||
- uv
|
||||
- weather_alert
|
||||
- city: 'Oslo, norvege'
|
||||
monitored_conditions:
|
||||
- temperature
|
||||
|
||||
28
source/_components/plaato.markdown
Normal file
28
source/_components/plaato.markdown
Normal file
@ -0,0 +1,28 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Plaato Airlock"
|
||||
description: "Instructions on how to integrate Plaato Airlock sensors within Home Assistant."
|
||||
date: 2019-05-07 01:15
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: plaato.png
|
||||
ha_release: 0.95
|
||||
ha_category:
|
||||
- Sensor
|
||||
ha_iot_class: Cloud Push
|
||||
---
|
||||
|
||||
This component sets up integration with [Plaato Airlock](https://www.plaato.io/).
|
||||
Plaato Airlock is a tool for beer brewers that wants a unique insight into the fermentation process.
|
||||
With this integration, you get all your fermentation data available in Home Assistant!
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To configure Plaato Airlock, you must set it up via the integrations panel in the Home Assistant frontend.
|
||||
|
||||
This will give you the webhook URL to use in the PLAATO mobile app configuration on the tab "Webhook".
|
||||
More information can be found [here](https://plaato.io/apps/help-center#!hc-general).
|
||||
|
||||
This sensor platform was not made by Plaato. It is not official, not developed, and not supported by Plaato.
|
||||
102
source/_components/qld_bushfire.markdown
Normal file
102
source/_components/qld_bushfire.markdown
Normal file
@ -0,0 +1,102 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Queensland Bushfire Alert"
|
||||
description: "Instructions on how to integrate the Queensland Bushfire Alert feed into Home Assistant."
|
||||
date: 2019-06-11 08:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: geo_location.png
|
||||
ha_category: Geolocation
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_release: 0.95
|
||||
---
|
||||
|
||||
The `qld_bushfire` platform lets you integrate a
|
||||
[GeoRSS feed](https://www.ruralfire.qld.gov.au/map/Pages/default.aspx)
|
||||
containing bushfire alerts for Queensland. 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
|
||||
`qld_bushfire`. The distance in kilometers is available as the state
|
||||
of each entity.
|
||||
|
||||
<p class='img'>
|
||||
<img src='{{site_root}}/images/screenshots/qld-bushfire-feed-map.png' />
|
||||
</p>
|
||||
|
||||
The data is updated every 5 minutes.
|
||||
|
||||
<p class='note'>
|
||||
The material used by this integration is provided under the [Creative Commons Attribution 4.0 license](https://creativecommons.org/licenses/by/4.0/legalcode).
|
||||
It has only been modified for the purpose of presenting the material in Home Assistant.
|
||||
Please refer to the [creator's copyright notice](https://www.qfes.qld.gov.au/Pages/copyright.aspx) for more information.
|
||||
</p>
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To integrate the Queensland Bushfire Alert feed, add the following lines to
|
||||
your `configuration.yaml`.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
geo_location:
|
||||
- platform: qld_bushfire
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
categories:
|
||||
description: List of category names found in the feed. Only alerts from the feed that match any of these categories are included. Valid categories are 'Emergency Warning', 'Watch and Act', 'Advice', 'Notification' and 'Information'.
|
||||
required: false
|
||||
type: list
|
||||
radius:
|
||||
description: The distance in kilometers around Home Assistant's coordinates in which bushfire alerts are included.
|
||||
required: false
|
||||
type: float
|
||||
default: 20.0
|
||||
latitude:
|
||||
description: Latitude of the coordinates around which events are considered.
|
||||
required: false
|
||||
type: string
|
||||
default: Latitude defined in your configuration
|
||||
longitude:
|
||||
description: Longitude of the coordinates around which events are considered.
|
||||
required: false
|
||||
type: string
|
||||
default: Longitude defined in your configuration
|
||||
{% endconfiguration %}
|
||||
|
||||
|
||||
## {% linkable_title State Attributes %}
|
||||
|
||||
The following state attributes are available for each entity in addition to
|
||||
the standard ones:
|
||||
|
||||
| Attribute | Description |
|
||||
|------------------|-------------|
|
||||
| latitude | Latitude of the bushfire alert. |
|
||||
| longitude | Longitude of the bushfire alert. |
|
||||
| source | `qld_bushfire` to be used in conjunction with `geo_location` automation trigger. |
|
||||
| external_id | The external ID used in the feed to identify the bushfire alert in the feed. |
|
||||
| title | Original title from the feed. |
|
||||
| publication_date | Date and time when this alert was first published. |
|
||||
| updated_date | Date and time when this alert was last updated. |
|
||||
| status | Status of the alert, for example, "Patrolled", "Going", "Contained" |
|
||||
|
||||
## {% linkable_title Full Configuration %}
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
geo_location:
|
||||
- platform: qld_bushfire
|
||||
radius: 30
|
||||
categories:
|
||||
- 'Emergency Warning'
|
||||
- 'Watch and Act'
|
||||
latitude: -24.85
|
||||
longitude: 152.35
|
||||
```
|
||||
55
source/_components/smarty.markdown
Normal file
55
source/_components/smarty.markdown
Normal file
@ -0,0 +1,55 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Salda Smarty 2X/3X/4X P/V Ventilation"
|
||||
description: "Instructions on how to integrate Salda Smarty 2X/3X/4X P/V ventilation systems into Home Assistant."
|
||||
date: 2019-02-25 20:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: salda.png
|
||||
ha_category:
|
||||
- Hub
|
||||
- Fan
|
||||
- Sensor
|
||||
ha_release: 0.95
|
||||
---
|
||||
|
||||
The `smarty` component lets you control Salda [Smarty](http://www.salda.lt/en/products/category/compact-counter-flow-units) ventilation units from Home Assistant. You need a [MB-GATEWAY](http://www.salda.lt/en/products/item/5637227077) or something similar to connect to your local network.
|
||||
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
- Fan
|
||||
- Sensor
|
||||
|
||||
The component has a fan platform to view and control the ventilation speed, and a sensors platform to read:
|
||||
|
||||
- Outdoor air temperature
|
||||
- Extract air temperature
|
||||
- Supply air temperature
|
||||
- Extract fan speed rpm
|
||||
- Supply fan speed rpm
|
||||
- Alarm
|
||||
- Warning
|
||||
- Filter Change Timer
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To set it up, add the following information to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
smarty:
|
||||
host: 192.168.0.10
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
host:
|
||||
description: The IP Address of the unit.
|
||||
required: true
|
||||
type: string
|
||||
name:
|
||||
description: The name of this device as you want to see it in Home Assistant.
|
||||
required: false
|
||||
default: Smarty
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
74
source/_components/solaredge_local.markdown
Normal file
74
source/_components/solaredge_local.markdown
Normal file
@ -0,0 +1,74 @@
|
||||
---
|
||||
layout: page
|
||||
title: "SolarEdge Local Sensor"
|
||||
description: "Instructions on how to integrate SolarEdge sensor within Home Assistant via Local API."
|
||||
date: 2018-12-04 14:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: solaredge.png
|
||||
ha_category:
|
||||
- Sensor
|
||||
- Energy
|
||||
ha_release: 0.95
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `solaredge_local` platform uses the local API available on some SolarEdge Inverters to allow you to get details from your SolarEdge solar power setup and integrate these into your Home Assistant installation.
|
||||
|
||||
Only specific models support the local API. The local API is available on the SExxxxH-US models with SetApp as well as European three-phase inverters SEXXK-XXXTXBXX4 models with SetApp like SE3K-E10K, SE12.5K-SE27.6K and SE33.3K. Please check the datasheets carefully if in the section "Additional Features", sub-section "Inverter Commissioning" is present the following line "With the SetApp mobile application using built-in Wi-Fi access point for local connection".
|
||||
|
||||
You can check by finding the IP address of your inverter and visiting it in a browser. If it supports the local API, you'll see the SolarEdge logo and a "Commissioning" menu.
|
||||
|
||||
<p class='note'>
|
||||
If your inveter does not support the local API, you can use the [cloud based version](/components/solaredge/) instead.
|
||||
</p>
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To use the SolarEdge sensors in your installation, add the following to your configuration.yaml file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
platform: solaredge_local
|
||||
ip_address: IP_ADDRESS
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
ip_address:
|
||||
description: The IP Address of your SolarEdge inverter.
|
||||
required: true
|
||||
type: string
|
||||
name:
|
||||
description: Let you overwrite the name of the device in the frontend.
|
||||
required: false
|
||||
default: SolarEdge
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
### {% linkable_title Full configuration sample %}
|
||||
|
||||
A full configuration entry would look like the sample below.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: solaredge_local
|
||||
name: SolarEdge
|
||||
ip_address: 192.168.1.123
|
||||
```
|
||||
|
||||
In case you would like to convert the values for example to kWh instead of the default Wh, you can use the [template platform](/components/sensor.template/).
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
# Example configuration.yaml entry for template platform
|
||||
sensors:
|
||||
platform: template
|
||||
sensors:
|
||||
solaredge_energy_this_year_template:
|
||||
value_template: '{{(states.sensor.solaredge_energy_this_year.state | float / 1000) | round(2)}}'
|
||||
```
|
||||
{% endraw %}
|
||||
64
source/_components/somfy.markdown
Normal file
64
source/_components/somfy.markdown
Normal file
@ -0,0 +1,64 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Somfy"
|
||||
description: "Instructions on how to set up the Somfy hub within Home Assistant."
|
||||
date: 2019-06-07 12:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: somfy.png
|
||||
ha_category:
|
||||
- Hub
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_release: 0.95
|
||||
---
|
||||
|
||||
The Somfy component will allow users to integrate their Somfy devices into Home Assistant using the [official API](https://developer.somfy.com/somfy-open-api/apis), unlike the [tahoma](/components/tahoma/) component.
|
||||
|
||||
### {% linkable_title Setting up developer account %}
|
||||
|
||||
To connect Somfy, you need to set up a developer account.
|
||||
|
||||
1. Visit [https://developer.somfy.com](https://developer.somfy.com).
|
||||
2. Log in using your Somfy credentials.
|
||||
3. Open the *My Apps* menu.
|
||||
4. Add a new App:
|
||||
- App Name: Home Assistant
|
||||
- Callback URL: `<YOUR_HOME_ASSISTANT_URL>/auth/somfy/callback`
|
||||
- Description: Home Assistant instance
|
||||
- Product: Somfy Open API
|
||||
5. Once Home Assistant restarted, go to Configuration>Integrations.
|
||||
6. Select the Somfy integration.
|
||||
|
||||
### {% linkable_title Configuration %}
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
somfy:
|
||||
client_id: CONSUMER_KEY
|
||||
client_secret: CONSUMER_SECRET
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
client_id:
|
||||
description: Your Somfy consumer key.
|
||||
required: true
|
||||
type: string
|
||||
client_secret:
|
||||
description: Your Somfy consumer secret.
|
||||
required: true
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
### {% linkable_title Potential duplicate with the Tahoma component %}
|
||||
|
||||
If you use the [tahoma](/component/tahoma) component, you will have to exclude the covers added by this one. Otherwise, they will be added twice.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
tahoma:
|
||||
username: YOUR_USERNAME
|
||||
password: YOUR_PASSWORD
|
||||
exclude: ['rts:RollerShutterRTSComponent','rts:CurtainRTSComponent','rts:BlindRTSComponent','rts:VenetianBlindRTSComponent','rts:DualCurtainRTSComponent','rts:ExteriorVenetianBlindRTSComponent','io:ExteriorVenetianBlindIOComponent','io:RollerShutterUnoIOComponent','io:RollerShutterWithLowSpeedManagementIOComponent','io:RollerShutterVeluxIOComponent','io:RollerShutterGenericIOComponent','io:WindowOpenerVeluxIOComponent','io:VerticalExteriorAwningIOComponent','io:HorizontalAwningIOComponent']
|
||||
```
|
||||
54
source/_components/streamlabswater.markdown
Normal file
54
source/_components/streamlabswater.markdown
Normal file
@ -0,0 +1,54 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Streamlabs Water"
|
||||
description: "Instructions on how to integrate Streamlabs Water devices with Home Assistant."
|
||||
date: 2019-02-25 12:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: streamlabswater.png
|
||||
ha_category:
|
||||
- Binary Sensor
|
||||
- Sensor
|
||||
ha_release: "0.95"
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `Streamlabs Water` component platform is used to interact with [Streamlabs water monitoring devices](https://www.streamlabswater.com/) in order to retrieve usage information and manage the away mode of the device. The [Streamlabs Water API](https://developer.streamlabswater.com) is used to retrieve daily, monthly, and yearly water usage along with the current away mode.
|
||||
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
- Binary Sensor
|
||||
- Sensor
|
||||
|
||||
In preparation for using this component you will need to request an API key following the instructions in the [Streamlabs API Getting Started Section](https://developer.streamlabswater.com/docs/getting-started.html). Be sure to request an API key and not an OAuth token.
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
Add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
streamlabswater:
|
||||
api_key: YOUR_API_KEY
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
api_key:
|
||||
description: Your api_key for the Streamlabs API.
|
||||
required: true
|
||||
type: string
|
||||
location_id:
|
||||
description: A specific monitor to use if you have multiple. By default the first found will be used.
|
||||
required: false
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
## {% linkable_title Service `set_away_mode` %}
|
||||
|
||||
You can use the service `streamlabswater.set_away_mode` to set the mode to `home` or `away`. The away mode will only be changed for the configured location.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `away_mode` | no | String, must be `away` or `home`.
|
||||
40
source/_components/switch.pca.markdown
Normal file
40
source/_components/switch.pca.markdown
Normal file
@ -0,0 +1,40 @@
|
||||
---
|
||||
layout: page
|
||||
title: "ELV PCA 301 Switch"
|
||||
description: "Instructions on how to integrate ELV PCA 301 switches into Home Assistant."
|
||||
date: 2019-02-24 18:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: elv.png
|
||||
ha_category: Switch
|
||||
ha_iot_class: Local Polling
|
||||
ha_release: 0.95
|
||||
---
|
||||
|
||||
The `pca` switch platform allows you to control the state of your [ELV PCA 301 smart switch](https://www.elv.de/funkschaltsteckdose-fuer-energiekostenmonitor-pca-301.html). You need an 868 MHz interface like the [JeeLink](https://www.digitalsmarties.net/products/jeelink) flashed with the [pca-hex firmware](https://github.com/mhop/fhem-mirror/blob/master/fhem/FHEM/firmware/JeeLink_PCA301.hex).
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To use your PCA 301 switch or socket in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
switch:
|
||||
- platform: pca
|
||||
device: SERIAL_PORT
|
||||
```
|
||||
|
||||
This platform will add all PCA 301 switches which are in range. You can read the total used energy in KWh and the current power in Watt.
|
||||
|
||||
{% configuration %}
|
||||
device:
|
||||
description: "The path to you serial console. Get it via: `ls /dev/tty*`."
|
||||
required: true
|
||||
type: string
|
||||
name:
|
||||
description: Default name for the plugs.
|
||||
required: false
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
@ -57,14 +57,27 @@ device_password:
|
||||
|
||||
## {% linkable_title Switch State Attributes %}
|
||||
|
||||
| Attribute | Type | Description | Example |
|
||||
| --------- | ---- | ----------- | ------- |
|
||||
| `friendly_name` | string | Defaults to the device's configured name. | "Switcher Boiler" |
|
||||
| `auto_off_set` | string | The auto shutdown time limit configured on the device. | "01:30:00" |
|
||||
| `remaining_time` | string | Time remaining to shutdown (auto or timer). | "01:29:41" |
|
||||
| `electric_current` | float | The electric current in amps. | 12.5 |
|
||||
| `current_power_w` | integer | The current power used in watts. | 2756 |
|
||||
| Attribute | Type | Description | Example |
|
||||
| ------------------ | ------- | ------------------------------------------------------ | ----------------- |
|
||||
| `friendly_name` | string | Defaults to the device's configured name. | "Switcher Boiler" |
|
||||
| `auto_off_set` | string | The auto shutdown time limit configured on the device. | "01:30:00" |
|
||||
| `remaining_time` | string | Time remaining to shutdown (auto or timer). | "01:29:41" |
|
||||
| `electric_current` | float | The electric current in amps. | 12.5 |
|
||||
| `current_power_w` | integer | The current power used in watts. | 2756 |
|
||||
|
||||
<p class='note warning'>
|
||||
Please note, the following attributes are not eligible when the device is off and therefore will not appear as state attributes: `remaining_time`, `electric_current`, `current_power_w`.
|
||||
</p>
|
||||
|
||||
## {% linkable_title Services %}
|
||||
|
||||
### {% linkable_title Service: `switcher_kis.set_auto_off` %}
|
||||
|
||||
You can use the `switcher_kis.set_auto_off` service to set the auto-off configuration setting for the device.
|
||||
|
||||
Meaning the device will turn itself off when reaching the auto-off configuration limit.
|
||||
|
||||
| Service Field | Mandatory | Description | Example |
|
||||
| ------------- | --------- | -------------------------------------------------------------------------------------- | -------------------------- |
|
||||
| `entity_id` | Yes | Name of the entity id associated with the integration, used for permission validation. | switch.switcher_kis_boiler |
|
||||
| `auto_off` | Yes | Time period string containing hours and minutes. | "02:30" |
|
||||
|
||||
@ -36,6 +36,11 @@ sensor:
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
name:
|
||||
description: The name of your device
|
||||
required: false
|
||||
default: Synology DSM
|
||||
type: string
|
||||
host:
|
||||
description: The IP address of the Synology NAS to monitor.
|
||||
required: true
|
||||
|
||||
@ -63,6 +63,15 @@ verify_ssl:
|
||||
required: false
|
||||
type: boolean
|
||||
default: true
|
||||
max_accuracy:
|
||||
description: Filter positions with higher accuracy than specified.
|
||||
required: false
|
||||
type: integer
|
||||
default: 0
|
||||
skip_accuracy_filter_on:
|
||||
description: Skip filter positon by "max_accuracy filter" if any of specified attributes are pressent on the traccar message.
|
||||
required: false
|
||||
type: list
|
||||
monitored_conditions:
|
||||
description: Additional traccar computed attributes or device-related attributes to include in the scan.
|
||||
required: false
|
||||
|
||||
@ -51,6 +51,7 @@ password:
|
||||
Supported models:
|
||||
- EVW3200-Wifi
|
||||
- EVW320B
|
||||
- EVW321B
|
||||
- EVW32C-0N
|
||||
- EVW3226@UPC
|
||||
|
||||
|
||||
@ -1,78 +0,0 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Uber"
|
||||
description: "How to integrate Uber in Home Assistant"
|
||||
date: 2016-03-24 23:04
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: uber.png
|
||||
ha_category:
|
||||
- Transport
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_release: 0.16
|
||||
redirect_from:
|
||||
- /components/sensor.uber/
|
||||
---
|
||||
|
||||
The `uber` sensor will give you time and price estimates for all available [Uber](https://uber.com) products at the given location. The `ATTRIBUTES` are used to provide extra information about products, such as estimated trip duration, distance and vehicle capacity. By default, 2 sensors will be created for each product at the given `start` location, one for pickup time and one for current price. The sensor is powered by the official Uber [API](https://developer.uber.com/).
|
||||
|
||||
## {% linkable_title Setup %}
|
||||
|
||||
You must [create an application](https://developer.uber.com/dashboard/create) in the [Uber developer Dashboard](https://developer.uber.com) to obtain a `server_token`.
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To enable this sensor, add the following lines to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: uber
|
||||
server_token: YOUR_UBER_SERVER_TOKEN
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
server_token:
|
||||
description: The Server API token.
|
||||
required: true
|
||||
type: string
|
||||
start_latitude:
|
||||
description: The starting latitude for a trip.
|
||||
required: false
|
||||
default: to the latitude in your `configuration.yaml` file.
|
||||
type: float
|
||||
start_longitude:
|
||||
description: The starting longitude for a trip.
|
||||
required: false
|
||||
default: to the longitude in your `configuration.yaml` file.
|
||||
type: float
|
||||
end_latitude:
|
||||
description: The ending latitude for a trip. While `end_latitude` is optional, it is strongly recommended to provide an `end_latitude`/`end_longitude` when possible as you will get more accurate price and time estimates.
|
||||
required: false
|
||||
type: float
|
||||
end_longitude:
|
||||
description: The ending longitude for a trip. While `end_longitude` is optional, it is strongly recommended to provide an `end_latitude`/`end_longitude` when possible as you will get more accurate price and time estimates.
|
||||
required: false
|
||||
type: float
|
||||
product_ids:
|
||||
description: A list of Uber product UUIDs. If provided, sensors will only be created for the given product IDs. Please note that product IDs are region and some times even more specific geographies based. The easiest way to find a UUID is to click on a sensor in the Home Assistant frontend and look for "Product ID" in the attributes.
|
||||
required: false
|
||||
type: list
|
||||
{% endconfiguration %}
|
||||
|
||||
A full configuration entry could look like the sample below:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: uber
|
||||
start_latitude: 37.8116380
|
||||
start_longitude: -122.2648050
|
||||
end_latitude: 37.7768520
|
||||
end_longitude: -122.4155500
|
||||
server_token: 'BeAPPTDsWZSHLf7fd9OWjZkIezweRw18Q8NltY27'
|
||||
product_ids:
|
||||
- '04a497f5-380d-47f2-bf1b-ad4cfdcb51f2'
|
||||
```
|
||||
@ -35,11 +35,11 @@ sensor:
|
||||
|
||||
{% configuration %}
|
||||
origin:
|
||||
description: Enter the starting address or the GPS coordinates of the location (GPS coordinates has to be separated by a comma). You can also enter the entity id of a sensor, device_tracker, person, or zone, which provides this information in its state.
|
||||
description: Enter the starting address or the GPS coordinates of the location (GPS coordinates has to be separated by a comma). You can also enter an entity id which provides this information in its state, a entity id with latitude and longitude attributes, or zone friendly name.
|
||||
required: true
|
||||
type: string
|
||||
destination:
|
||||
description: Enter the destination address or the GPS coordinates of the location (GPS coordinates has to be separated by a comma). You can also enter the entity id of a sensor, device_tracker, person, or zone, which provides this information in its state.
|
||||
description: Enter the destination address or the GPS coordinates of the location (GPS coordinates has to be separated by a comma). You can also enter an entity id which provides this information in its state, a entity id with latitude and longitude attributes, or zone friendly name.
|
||||
required: true
|
||||
type: string
|
||||
region:
|
||||
@ -63,6 +63,14 @@ realtime:
|
||||
description: If this is set to false, Waze returns the time estimate, not including current conditions, but rather the average travel time for the current time of day. The parameter defaults to true, meaning Waze will return real-time travel time.
|
||||
required: false
|
||||
type: boolean
|
||||
units:
|
||||
description: "Set the unit for the sensor in metric or imperial, otherwise the default unit the same as the unit set in `unit_system:`."
|
||||
required: false
|
||||
type: string
|
||||
vehicle_type:
|
||||
description: "Set the vehicle type for the sensor: car, taxi, or motorcycle, otherwise the default is car."
|
||||
required: false
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
## {% linkable_title Example using dynamic destination %}
|
||||
@ -95,11 +103,27 @@ sensor:
|
||||
{%- else -%}
|
||||
Unknown
|
||||
{%- endif %}
|
||||
|
||||
|
||||
# Tracking entity to entity
|
||||
- platform: waze_travel_time
|
||||
name: "Me to destination"
|
||||
origin: device_tracker.myphone
|
||||
destination: sensor.dest_address
|
||||
region: 'US'
|
||||
|
||||
# Tracking entity to zone friendly name
|
||||
- platform: waze_travel_time
|
||||
name: Home To Eddie's House
|
||||
origin: zone.home
|
||||
destination: Eddies House # Friendly name of a zone
|
||||
region: 'US'
|
||||
|
||||
# Tracking entity in imperial unit
|
||||
- platform: waze_travel_time
|
||||
origin: person.paulus
|
||||
destination: "725 5th Ave, New York, NY 10022, USA"
|
||||
region: 'US'
|
||||
units: imperial # 'metric' for Metric, 'imperial' for Imperial
|
||||
vehicle_type: motorcycle # vehicle type used for route
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
ha_category:
|
||||
- Network
|
||||
ha_qa_scale: internal
|
||||
ha_release: 0.18
|
||||
---
|
||||
|
||||
@ -18,19 +19,9 @@ Integrations can opt-in to be found by adding either [a Zeroconf section](https:
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To integrate this into Home Assistant, add the following section to your `configuration.yaml` file:
|
||||
To have Home Assistant scan for integrations using zeroconf and HomeKit, add the following section to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
zeroconf:
|
||||
```
|
||||
|
||||
## {% linkable_title Discovered Integrations %}
|
||||
|
||||
The following integrations are automatically discovered by the Zeroconf integration:
|
||||
|
||||
- Axis
|
||||
- ESPHome
|
||||
- HomeKit Controller
|
||||
- LIFX
|
||||
- Trådfri
|
||||
|
||||
@ -13,6 +13,7 @@ ha_category:
|
||||
- Binary Sensor
|
||||
- Fan
|
||||
- Light
|
||||
- Lock
|
||||
- Sensor
|
||||
- Switch
|
||||
ha_release: 0.44
|
||||
@ -34,6 +35,7 @@ There is currently support for the following device types within Home Assistant:
|
||||
- Binary Sensor
|
||||
- Sensor
|
||||
- Light
|
||||
- Lock
|
||||
- Switch
|
||||
- Fan
|
||||
|
||||
|
||||
@ -131,13 +131,14 @@ Z-Wave garage doors, blinds, and roller shutters are supported as cover in Home
|
||||
|
||||
To get your Z-Wave covers working with Home Assistant, follow the instructions for the general [Z-Wave component](#configuration).
|
||||
|
||||
If you discover that you need to [invert the operation](/docs/z-wave/installation/#invert_openclose_buttons) of open/close for a particular device, you may change this behavior in your Z-Wave section of your `configuration.yaml` file as follows:
|
||||
If you discover that you need to [invert the operation](/docs/z-wave/installation/#invert_openclose_buttons) of open/close for a particular device, you may change this behavior in your Z-Wave section of your `configuration.yaml` file as follows, in addition you can also [invert percent position](/docs/z-wave/installation/#invert_percent):
|
||||
|
||||
```yaml
|
||||
zwave:
|
||||
device_config:
|
||||
cover.my_cover:
|
||||
invert_openclose_buttons: true
|
||||
invert_percent: true
|
||||
```
|
||||
|
||||
## {% linkable_title Lock %}
|
||||
|
||||
@ -186,7 +186,7 @@ A very thorough explanation of this is available in the Wikipedia article about
|
||||
|
||||
### {% linkable_title Template trigger %}
|
||||
|
||||
Template triggers work by evaluating a [template](/docs/configuration/templating/) on every state change for all of the recognized entities. The trigger will fire if the state change caused the template to render 'true'. This is achieved by having the template result in a true boolean expression (`{% raw %}{{ is_state('device_tracker.paulus', 'home') }}{% endraw %}`) or by having the template render 'true' (example below). Being a boolean expression the template must evaluate to false before it will fire again.
|
||||
Template triggers work by evaluating a [template](/docs/configuration/templating/) on every state change for all of the recognized entities. The trigger will fire if the state change caused the template to render 'true'. This is achieved by having the template result in a true boolean expression (`{% raw %}{{ is_state('device_tracker.paulus', 'home') }}{% endraw %}`) or by having the template render 'true' (example below). Being a boolean expression the template must evaluate to false (or anything other than true) before it will fire again.
|
||||
With template triggers you can also evaluate attribute changes by using is_state_attr (`{% raw %}{{ is_state_attr('climate.living_room', 'away_mode', 'off') }}{% endraw %}`)
|
||||
|
||||
{% raw %}
|
||||
@ -195,6 +195,9 @@ automation:
|
||||
trigger:
|
||||
platform: template
|
||||
value_template: "{% if is_state('device_tracker.paulus', 'home') %}true{% endif %}"
|
||||
|
||||
# If given, will trigger when template remains true for X time.
|
||||
for: '00:01:00'
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
|
||||
@ -84,9 +84,11 @@ Supported abbreviations:
|
||||
'away_mode_cmd_t': 'away_mode_command_topic',
|
||||
'away_mode_stat_tpl': 'away_mode_state_template',
|
||||
'away_mode_stat_t': 'away_mode_state_topic',
|
||||
'b_tpl': 'blue_template',
|
||||
'bri_cmd_t': 'brightness_command_topic',
|
||||
'bri_scl': 'brightness_scale',
|
||||
'bri_stat_t': 'brightness_state_topic',
|
||||
'bri_tpl': 'brightness_template',
|
||||
'bri_val_tpl': 'brightness_value_template',
|
||||
'bat_lev_t': 'battery_level_topic',
|
||||
'bat_lev_tpl': 'battery_level_template',
|
||||
@ -97,6 +99,8 @@ Supported abbreviations:
|
||||
'clr_temp_val_tpl': 'color_temp_value_template',
|
||||
'cln_t': 'cleaning_topic',
|
||||
'cln_tpl': 'cleaning_template',
|
||||
'cmd_off_tpl': 'command_off_template',
|
||||
'cmd_on_tpl': 'command_on_template',
|
||||
'cmd_t': 'command_topic',
|
||||
'curr_temp_t': 'current_temperature_topic',
|
||||
'curr_temp_tpl': 'current_temperature_template',
|
||||
@ -112,12 +116,14 @@ Supported abbreviations:
|
||||
'fx_cmd_t': 'effect_command_topic',
|
||||
'fx_list': 'effect_list',
|
||||
'fx_stat_t': 'effect_state_topic',
|
||||
'fx_tpl': 'effect_template',
|
||||
'fx_val_tpl': 'effect_value_template',
|
||||
'exp_aft': 'expire_after',
|
||||
'fan_mode_cmd_t': 'fan_mode_command_topic',
|
||||
'fan_mode_stat_tpl': 'fan_mode_state_template',
|
||||
'fan_mode_stat_t': 'fan_mode_state_topic',
|
||||
'frc_upd': 'force_update',
|
||||
'g_tpl': 'green_template',
|
||||
'hold_cmd_t': 'hold_command_topic',
|
||||
'hold_stat_tpl': 'hold_state_template',
|
||||
'hold_stat_t': 'hold_state_topic',
|
||||
@ -154,6 +160,7 @@ Supported abbreviations:
|
||||
'pl_stop': 'payload_stop',
|
||||
'pl_unlk': 'payload_unlock',
|
||||
'pow_cmd_t': 'power_command_topic',
|
||||
'r_tpl': 'red_template',
|
||||
'ret': 'retain',
|
||||
'rgb_cmd_tpl': 'rgb_command_template',
|
||||
'rgb_cmd_t': 'rgb_command_topic',
|
||||
@ -173,6 +180,7 @@ Supported abbreviations:
|
||||
'stat_on': 'state_on',
|
||||
'stat_open': 'state_open',
|
||||
'stat_t': 'state_topic',
|
||||
'stat_tpl': 'state_template',
|
||||
'stat_val_tpl': 'state_value_template',
|
||||
'sup_feat': 'supported_features',
|
||||
'swing_mode_cmd_t': 'swing_mode_command_topic',
|
||||
|
||||
@ -82,6 +82,11 @@ device_config / device_config_domain / device_config_glob:
|
||||
required: false
|
||||
type: boolean
|
||||
default: false
|
||||
invert_percent:
|
||||
description: Inverts the percentage of the position for the cover domain. This will invert the position and state reporting.
|
||||
required: false
|
||||
type: boolean
|
||||
default: false
|
||||
{% endconfiguration %}
|
||||
|
||||
### {% linkable_title Network Key %}
|
||||
|
||||
736
source/_posts/2019-06-26-release-95.markdown
Normal file
736
source/_posts/2019-06-26-release-95.markdown
Normal file
@ -0,0 +1,736 @@
|
||||
---
|
||||
layout: post
|
||||
title: "0.95: AdGuard, Life360, Plaato Airlock"
|
||||
description: "Manage Alexa UI, improved RV support, even more icons available."
|
||||
date: 2019-06-26 04:11:03
|
||||
date_formatted: "June 26, 2019"
|
||||
author: Paulus Schoutsen
|
||||
author_twitter: balloob
|
||||
comments: true
|
||||
categories: Release-Notes
|
||||
og_image: /images/blog/2019-06-release-95/social.png
|
||||
---
|
||||
|
||||
<a href='/components/#version/0.95'><img src='/images/blog/2019-06-release-95/components.png' style='border: 0;box-shadow: none;'></a>
|
||||
|
||||
It is time for release 0.95, and guess what? It's good! First things first, did you see [the new Raspberry Pi 4](https://www.raspberrypi.org/blog/raspberry-pi-4-on-sale-now-from-35/)? 3x as fast as the model 3, gigabit ethernet port actually supports gigabit speeds now, faster memory read/write, oh well, faster everything! [The benchmarks are impressive.](https://www.raspberrypi.org/magpi/raspberry-pi-4-specs-benchmarks/) Best of all? The base price stayed the same. However, you can now also pay more for upgraded models with more memory, which is great if you like to install all the hass.io add-ons.
|
||||
|
||||
Talking about Hass.io support, we've received ours and work to add support will start shortly 🚀. Since we're discussing Raspberry Pi's, can we talk SD cards really quick? Quality matters. When you buy SD Cards get the pro variants, preferably the ones that are [class A1](https://amzn.to/2WYUVtm) or, even better, [class A2](https://amzn.to/2X0Z2di). The A stands for application and they are optimized for running apps, like Home Assistant.
|
||||
|
||||
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">LOOK WHAT WE HAVE HERE 😍 <a href="https://t.co/HrEu1a272Y">pic.twitter.com/HrEu1a272Y</a></p>— Pascal Vizeli (@pvizeli) <a href="https://twitter.com/pvizeli/status/1143808786983006208?ref_src=twsrc%5Etfw">June 26, 2019</a>
|
||||
</blockquote>
|
||||
|
||||
## {% linkable_title RV Assistant %}
|
||||
|
||||
Home Assistant is not just limited to homes. Recently we had a boat owner on [Home Assistant podcast episode 48](https://hasspodcast.io/ha048/), and Home Assistant also powers recreational vehicles (RV) ([like this schoolbus](https://thisisthebus.com/our-tech-stack.html)).
|
||||
|
||||
With this release, we're making integrating Home Assistant into moving vehicles so much easier. In the last release, we introduced support for the core config to be updated without restarting Home Assistant. This release brings it a step further and introduces a new service `homeassistant.set_location`. With this service, you can automatically change the location that Home Assistant is located. Once updated, it automatically updates all the things that rely on the location, like your sunset triggers and your current weather (only [Met][met docs] supported now).
|
||||
|
||||
## {% linkable_title AdGuard Home - local ad-and-tracker blocking %}
|
||||
|
||||
Here at Home Assistant, we're big fans of privacy and we're always working on improving it. So this brings us to [AdGuard](https://adguard.com/). AdGuard Home is a local DNS server that automatically blocks any device looking up a domain that is used to serve ads, spreads malware, or isn't appropriate for your kids. Thanks to [@frenck], starting release 0.95, it has a top-notch integration with Home Assistant:
|
||||
|
||||
- One-click install the AdGuard add-on from the [Community Hass.io Add-ons](https://github.com/hassio-addons/repository/blob/master/README.md).
|
||||
- Home Assistant automatically detects the Hass.io add-on and offers to set it up. (It works with standalone installs too, see the [AdGuard integration documentation][adguard docs] on how to configure it.)
|
||||
- DONE!
|
||||
|
||||
One cool new feature: because parental control is now available as a switch, you can control AdGuard via Alexa and Google: "Hey Google, turn on parental control" 😲.
|
||||
|
||||
<p class='img'>
|
||||
<a href="https://youtu.be/IyoHpU8JxSs?t=6324">
|
||||
<img src='/images/blog/2019-06-release-95/frenck.png' alt='Screenshot of Frenck during his stream demoing AdGuard.'>
|
||||
</a>
|
||||
Frenck shows a demo of the AdGuard integration during his stream. <a href="https://youtu.be/IyoHpU8JxSs?t=6324">See the full stream.</a>
|
||||
</p>
|
||||
|
||||
## {% linkable_title Life360 %}
|
||||
|
||||
More goodies. Keep paying attention as we're not done yet. Also new in 0.95 is the [Life360 integration][life360 docs] thanks to the hard work by [@pnbruckner]. This integration started its life a little over 360 days ago [on the forums as a custom integration](https://community.home-assistant.io/t/life360-device-tracker-platform/52406) and has now become part of Home Assistant. Life360 is an app to allow friends or family members to share location with each other.
|
||||
|
||||
If you are migrating from the custom integration, [please read the instructions](https://community.home-assistant.io/t/life360-device-tracker-platform/52406/1077).
|
||||
|
||||
## {% linkable_title Improved Alexa integration %}
|
||||
|
||||
One more thing… This release improves the Home Assistant Cloud Alexa integration. Just like Google Assistant, it is now possible to manage which entities are exposed to Amazon via the user interface. Alexa actually offers some cool features around this. Any change you make is reflected instantly inside Alexa. Add an entity? Control it instantly via Alexa.
|
||||
|
||||
However, we didn't stop there. The [manual installations of Alexa](https://www.home-assistant.io/components/alexa.smart_home/#alexa-component-configuration) has had optional proactive state reporting since earlier this year, and this is now available for Home Assistant Cloud users too. If you choose to opt-in to this, every state change of your exposed entities is sent to Amazon as soon as they happen. It allows Amazon Echos with displays, to instantly reflect the state and allows you to create routines inside Amazon powered by your Home Assistant entities.
|
||||
|
||||
<div class="videoWrapper">
|
||||
<iframe width="853" height="480" src="https://www.youtube-nocookie.com/embed/8NfDr5lBcmQ" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
|
||||
</div>
|
||||
|
||||
## {% linkable_title More icons available %}
|
||||
|
||||
[Austin Andrews](https://twitter.com/templarian), the lead designer of Material Design Icons, informed us that Material Design Icons 3.7.95 has been released. It includes a handful of the top requested Home Assistant icons (and a total of 100 new icons!).
|
||||
|
||||
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Released `v3.7.95` to NPM/CDN. 100 new icons! 🧙♂️ Preview: <a href="https://t.co/N02X3rnQ8N">https://t.co/N02X3rnQ8N</a> Read more: <a href="https://t.co/CHQ3TEdVM2">https://t.co/CHQ3TEdVM2</a> <a href="https://twitter.com/hashtag/MaterialDesign?src=hash&ref_src=twsrc%5Etfw">#MaterialDesign</a> <a href="https://twitter.com/hashtag/OpenSource?src=hash&ref_src=twsrc%5Etfw">#OpenSource</a> <a href="https://t.co/LlWy8RfFVu">pic.twitter.com/LlWy8RfFVu</a></p>— Material Icons (@MaterialIcons) <a href="https://twitter.com/MaterialIcons/status/1142474126004760576?ref_src=twsrc%5Etfw">June 22, 2019</a>
|
||||
</blockquote>
|
||||
|
||||
## {% linkable_title Noteworthy breaking changes %}
|
||||
|
||||
For the last couple of releases, we've been printing warnings if your configuration contained invalid slugs or extra keys. Starting with this release, these warnings are now errors. No procrastination anymore, you'll need to fix it now.
|
||||
|
||||
We have also realized that the default database clean up task never automatically ran as intended. Instead of running every night, cleaning up your history so that it only contains the last 10 days, it never ran. Oopsie. We've fixed it in this release, so now the defaults kick in. Want to adjust how much history you want to retain? Check [the docs][recorder docs].
|
||||
|
||||
## {% linkable_title New Integrations %}
|
||||
|
||||
- Adds AdGuard Home integration ([@frenck] - [#24219]) ([adguard docs]) (new-integration)
|
||||
- SolarEdge Local Component ([@drobtravels] - [#23996]) ([solaredge_local docs]) (new-integration)
|
||||
- Google Cloud Platform component (TTS) ([@lufton] - [#23629]) ([google_cloud docs]) (new-integration)
|
||||
- Life360 integration ([@pnbruckner] - [#24227]) ([life360 docs]) (new-integration)
|
||||
- Adds integration for Plaato Airlock ([@JohNan] - [#23727]) ([plaato docs]) (new-integration)
|
||||
- Queensland bushfire alert feed platform ([@exxamalte] - [#24473]) ([qld_bushfire docs]) (new-integration)
|
||||
- Vlc telnet ([@rodripf] - [#24290]) ([vlc_telnet docs]) (beta fix) (new-integration)
|
||||
|
||||
## {% linkable_title New Platforms %}
|
||||
|
||||
- Add LCN scene platform ([@alengwenus] - [#24242]) ([lcn docs]) (new-platform)
|
||||
- Add Environment Canada weather, sensor, and camera platforms ([@michaeldavie] - [#21110]) ([environment_canada docs]) (new-platform)
|
||||
- Support for Salda Smarty XV/XP Ventilation Unit ([@z0mbieprocess] - [#21491]) ([smarty docs]) (new-platform)
|
||||
- Add support for ZHA door locks #2 ([@presslab-us] - [#24344]) ([zha docs]) (new-platform)
|
||||
- Somfy open api ([@tetienne] - [#19548]) ([somfy docs]) (new-platform)
|
||||
- Add APRS device tracker component ([@PhilRW] - [#22469]) ([aprs docs]) (new-platform)
|
||||
- Camera platform for buienradar imagery ([@ties] - [#23358]) ([buienradar docs]) (new-platform)
|
||||
- Add incomfort sensor and binary_sensor ([@zxdavb] - [#23812]) ([incomfort docs]) (new-platform)
|
||||
- Added ELV PCA 301 smart emeter switch ([@majuss] - [#23300]) ([elv docs]) (new-platform)
|
||||
|
||||
## {% linkable_title If you need help... %}
|
||||
|
||||
...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e).
|
||||
|
||||
## {% linkable_title Reporting Issues %}
|
||||
|
||||
Experiencing issues introduced by this release? Please report them in our [issue tracker](https://github.com/home-assistant/home-assistant/issues). Make sure to fill in all fields of the issue template.
|
||||
|
||||
<!--more-->
|
||||
|
||||
## {% linkable_title Breaking Changes %}
|
||||
|
||||
- No longer allow invalid slugs or extra keys ([@balloob] - [#24176]) (breaking change)
|
||||
- Add service for adding event to google component ([@isabellaalstrom] - [#22473]) ([google docs]) (breaking change)
|
||||
- Remove deprecated AlarmControlPanel ([@SukramJ] - [#24322]) ([homematicip_cloud docs]) (breaking change)
|
||||
- Remove attribute lowBat ([@SukramJ] - [#24323]) ([homematicip_cloud docs]) (breaking change)
|
||||
- Remove binary sensors for ZHA remotes and controllers ([@dmulcahey] - [#24370]) ([zha docs]) (breaking change)
|
||||
- Restore automation last_triggered with initial_state override ([@frenck] - [#24400]) ([automation docs]) (breaking change)
|
||||
- Fix recorder defaults ([@balloob] - [#24399]) ([recorder docs]) (breaking change)
|
||||
- Uber API is going away on June 13, 2019, remove component ([@robbiet480] - [#24468]) ([uber docs]) (breaking change)
|
||||
- Add Linky sensors : yesterday + months + years ([@Quentame] - [#23726]) ([linky docs]) (breaking change)
|
||||
- Position is reversed for horizontal awnings ([@kbickar] - [#23257]) ([tahoma docs]) (breaking change)
|
||||
- Remove conversation from default config ([@balloob] - [#24515]) ([default_config docs]) (breaking change)
|
||||
- Added name to sensors ([@cliffordwhansen] - [#24525]) ([synologydsm docs]) (breaking change)
|
||||
- Battery attribute & accuracy filter ([@GoNzCiD] - [#24277]) ([traccar docs]) (breaking change)
|
||||
- Added percent to the disk,memory and swap percent labels ([@cliffordwhansen] - [#24575]) ([glances docs]) (breaking change)
|
||||
- Save cached logi_circle tokens in config folder ([@evanjd] - [#24726]) ([logi_circle docs]) (breaking change) (beta fix)
|
||||
|
||||
## {% linkable_title Beta Fixes %}
|
||||
|
||||
- Vlc telnet ([@rodripf] - [#24290]) ([vlc_telnet docs]) (beta fix) (new-integration)
|
||||
- Fix device tracker see for entity registry entities ([@MartinHjelmare] - [#24633]) ([device_tracker docs]) (beta fix)
|
||||
- Bump ZHA dependencies. ([@Adminiuga] - [#24637]) ([zha docs]) (beta fix)
|
||||
- Update LIFX brightness during long transitions ([@amelchio] - [#24653]) ([lifx docs]) (beta fix)
|
||||
- Upgrade blinkpy==0.14.1 for startup bugfix ([@fronzbot] - [#24656]) ([blink docs]) (beta fix)
|
||||
- Warn when user tries run custom config flow ([@balloob] - [#24657]) (beta fix)
|
||||
- Bump pysmartthings ([@andrewsayre] - [#24659]) ([smartthings docs]) (beta fix)
|
||||
- Prefere binary with wheels ([@pvizeli] - [#24669]) (beta fix)
|
||||
- Allow extra js modules to be included in frontend ([@thomasloven] - [#24675]) ([frontend docs]) (beta fix)
|
||||
- Fix time expression parsing ([@amelchio] - [#24696]) (beta fix)
|
||||
- ZHA fix device type mappings ([@dmulcahey] - [#24699]) ([zha docs]) (beta fix)
|
||||
- Bump version pyatmo to 2.0.1 ([@cgtobi] - [#24703]) ([netatmo docs]) (beta fix)
|
||||
- Extend websocket method usage to port 8002 in Samsung TV media player ([@2sheds] - [#24716]) ([samsungtv docs]) (beta fix)
|
||||
- Update ZHA dependencies ([@dmulcahey] - [#24718]) ([zha docs]) (beta fix)
|
||||
- Add show_as_state options to Life360 ([@pnbruckner] - [#24725]) ([life360 docs]) (beta fix)
|
||||
- Save cached logi_circle tokens in config folder ([@evanjd] - [#24726]) ([logi_circle docs]) (breaking change) (beta fix)
|
||||
- Update ZHA dependencies. ([@Adminiuga] - [#24736]) ([zha docs]) (beta fix)
|
||||
- AdGuard to update entry ([@balloob] - [#24737]) ([adguard docs]) (beta fix)
|
||||
- Update pysonos to 0.0.17 ([@amelchio] - [#24740]) ([sonos docs]) (beta fix)
|
||||
- Clean up Google Config ([@balloob] - [#24663]) ([cloud docs]) ([google_assistant docs]) (beta fix)
|
||||
- Fix locative device update ([@MartinHjelmare] - [#24744]) ([locative docs]) (beta fix)
|
||||
- Improve Alexa error handling ([@balloob] - [#24745]) ([alexa docs]) ([cloud docs]) ([websocket_api docs]) (beta fix)
|
||||
- Bump pyatmo to v2.1.0 ([@cgtobi] - [#24724]) ([netatmo docs]) (beta fix)
|
||||
- Handle timeouts gracefully ([@cgtobi] - [#24752]) ([netatmo docs]) (beta fix)
|
||||
- Update Waze route dependency to 0.10 ([@johntdyer] - [#24754]) ([waze_travel_time docs]) (beta fix)
|
||||
- Ignore duplicate tradfri discovery ([@balloob] - [#24759]) ([tradfri docs]) (beta fix)
|
||||
- Return correct name for met.no ([@Danielhiversen] - [#24763]) ([met docs]) (beta fix)
|
||||
|
||||
## {% linkable_title All changes %}
|
||||
|
||||
- Update pysonos to 0.0.14 ([@amelchio] - [#24185]) ([sonos docs])
|
||||
- upgrade broadlink library, Use cryptography instead of pycryptodome ([@Danielhiversen] - [#24186]) ([broadlink docs])
|
||||
- danielhiversen as codeowner for yr ([@Danielhiversen] - [#24189]) ([yr docs])
|
||||
- No longer allow invalid slugs or extra keys ([@balloob] - [#24176]) (breaking change)
|
||||
- Update azure-pipelines.yml for check version ([@pvizeli] - [#24194])
|
||||
- Update Tibber library ([@Danielhiversen] - [#24192]) ([tibber docs])
|
||||
- :pencil2: Corrects incorrect command in hassfest ([@frenck] - [#24188])
|
||||
- Fix ESPHome config flow with invalid config entry ([@OttoWinter] - [#24213]) ([esphome docs])
|
||||
- Add control of Amcrest indicator light ([@pnbruckner] - [#23986]) ([amcrest docs])
|
||||
- ZHA requirements version bump. ([@Adminiuga] - [#24228]) ([zha docs])
|
||||
- Bump pychromecast ([@soldag] - [#24234]) ([cast docs])
|
||||
- Round Awair sensor values ([@danielsjf] - [#24093]) ([awair docs])
|
||||
- Sense update ([@kbickar] - [#24220]) ([sense docs])
|
||||
- fix gitlab_ci sad icon ([@Emilv2] - [#24241]) ([gitlab_ci docs])
|
||||
- Add details to triggered state for total connect alarms ([@austinmroczek] - [#24106]) ([totalconnect docs])
|
||||
- Bump python-velbus version for velbus component ([@Cereal2nd] - [#24226]) ([velbus docs])
|
||||
- Adds AdGuard Home integration ([@frenck] - [#24219]) ([adguard docs]) (new-integration)
|
||||
- Fix typo in integration component ([@Emilv2] - [#24250]) ([integration docs])
|
||||
- Replace pyunifi with aiounifi in UniFi device tracker ([@Kane610] - [#24149]) ([unifi docs])
|
||||
- Add service for adding event to google component ([@isabellaalstrom] - [#22473]) ([google docs]) (breaking change)
|
||||
- Remove icon() ([@fabaff] - [#24280]) ([meteoalarm docs])
|
||||
- Split devices of nodes with multiple instances ([@Swamp-Ig] - [#24032]) ([zwave docs])
|
||||
- Update pyvera to 0.3.1 for alert support ([@brandond] - [#24289]) ([vera docs])
|
||||
- Expose specific device_class for Velux covers ([@gibman] - [#24279]) ([velux docs])
|
||||
- Change meteoalertapi to version 0.1.3 ([@rolfberkenbosch] - [#24307]) ([meteoalarm docs])
|
||||
- Upgrade pytest and -cov ([@scop] - [#24258])
|
||||
- Add LCN scene platform ([@alengwenus] - [#24242]) ([lcn docs]) (new-platform)
|
||||
- Add support for learning new commands ([@felipediel] - [#23888]) ([remote docs])
|
||||
- Upgrade to newer version of rflink with improve error handling on incoming data. ([@aequitas] - [#24263]) ([rflink docs])
|
||||
- SolarEdge Local Component ([@drobtravels] - [#23996]) ([solaredge_local docs]) (new-integration)
|
||||
- Push to version 0.7.9 of denonavr ([@scarface-4711] - [#24260]) ([denonavr docs])
|
||||
- Bump simplipy to 3.4.2 ([@bachya] - [#24326]) ([simplisafe docs])
|
||||
- Meteofrance fix 24244 ([@victorcerutti] - [#24315]) ([meteo_france docs])
|
||||
- Only update media icon when necessary ([@jjlawren] - [#24324]) ([webostv docs])
|
||||
- components/cover: Typo in docstring. ([@andre-richter] - [#24329]) ([cover docs])
|
||||
- Add exception handling for Netatmo climate ([@cgtobi] - [#24311]) ([netatmo docs])
|
||||
- Remove deprecated AlarmControlPanel ([@SukramJ] - [#24322]) ([homematicip_cloud docs]) (breaking change)
|
||||
- Use node descriptor from Zigpy for ZHA ([@dmulcahey] - [#24316]) ([zha docs])
|
||||
- Add abbreviation for light template variable names ([@bieniu] - [#24336]) ([mqtt docs])
|
||||
- Remove attribute lowBat ([@SukramJ] - [#24323]) ([homematicip_cloud docs]) (breaking change)
|
||||
- Don't load last_checkpoint if shipment is pending ([@davidbb] - [#24301]) ([aftership docs])
|
||||
- UPgrade youtube_dl to 2019.05.20 ([@fabaff] - [#24347]) ([media_extractor docs])
|
||||
- Add new movement type "actively" of the Xiaomi Vibration Sensor ([@syssi] - [#24334]) ([xiaomi_aqara docs])
|
||||
- Fix set_cover_position of the xiaomi_aqara cover for LAN protocol v2 ([@syssi] - [#24333]) ([xiaomi_aqara docs])
|
||||
- Add Environment Canada weather, sensor, and camera platforms ([@michaeldavie] - [#21110]) ([environment_canada docs]) (new-platform)
|
||||
- Google Cloud Platform component (TTS) ([@lufton] - [#23629]) ([google_cloud docs]) (new-integration)
|
||||
- Add Streamlabs Water Monitor ([@cpopp] - [#21205]) ([streamlabswater docs])
|
||||
- ebusd: added check for monitored conditions validity within correct circuit ([@danielkucera] - [#22461]) ([ebusd docs])
|
||||
- Bring the Sisyphus integration to silver quality ([@jkeljo] - [#22457]) ([sisyphus docs])
|
||||
- Support for Salda Smarty XV/XP Ventilation Unit ([@z0mbieprocess] - [#21491]) ([smarty docs]) (new-platform)
|
||||
- Bump to pypck==0.6.1 ([@alengwenus] - [#24356]) ([lcn docs])
|
||||
- Add templating to MQTT Cover tilt_status ([@tommyjlong] - [#24355]) ([mqtt docs])
|
||||
- Upgrade ruamel.yaml to 0.15.97 ([@fabaff] - [#24350])
|
||||
- Bump regenmaschine to 1.5.1 ([@bachya] - [#24358]) ([rainmachine docs])
|
||||
- Life360 integration ([@pnbruckner] - [#24227]) ([life360 docs]) (new-integration)
|
||||
- Refactor Waze Travel Time & Update Requirements ([@Petro31] - [#22428]) ([waze_travel_time docs])
|
||||
- Update pyhomematic ([@danielperna84] - [#24368]) ([homematic docs])
|
||||
- Add service to update core location ([@balloob] - [#24328]) ([homeassistant docs])
|
||||
- Fix ZHA battery level when value is reported via signal ([@dmulcahey] - [#24371]) ([zha docs])
|
||||
- Remove binary sensors for ZHA remotes and controllers ([@dmulcahey] - [#24370]) ([zha docs]) (breaking change)
|
||||
- Add support for ZHA door locks #2 ([@presslab-us] - [#24344]) ([zha docs]) (new-platform)
|
||||
- Upgrade discord.py to 1.1.1 ([@fabaff] - [#24375]) ([discord docs])
|
||||
- Upgrade Mastodon.py to 1.4.3 ([@fabaff] - [#24374]) ([mastodon docs])
|
||||
- Add shuffle support for itunes component ([@kvanhoorn] - [#24319]) ([itunes docs])
|
||||
- Fixed wrong setpoint value on startup when climate was previously turned off ([@alengwenus] - [#24377]) ([lcn docs])
|
||||
- Add ATTR_FORECAST_PRECIPITATION option ([@rolfberkenbosch] - [#24308]) ([buienradar docs])
|
||||
- Provide an option for the DD-WRT device tracker to include non-wireless devices ([@Klikini] - [#24259]) ([ddwrt docs])
|
||||
- Add for option for template triggers ([@pnbruckner] - [#24330]) ([automation docs])
|
||||
- Improve amcrest error handling and bump amcrest package to 1.5.3 ([@pnbruckner] - [#24262]) ([amcrest docs])
|
||||
- Improve boolean validator ([@Swamp-Ig] - [#24294])
|
||||
- add device class to sensors ([@dmulcahey] - [#24373]) ([zha docs])
|
||||
- Fixes linter warning in ZHA sensor ([@frenck] - [#24406]) ([zha docs])
|
||||
- Use loose version ([@balloob] - [#24394])
|
||||
- Restore automation last_triggered with initial_state override ([@frenck] - [#24400]) ([automation docs]) (breaking change)
|
||||
- Fix recorder defaults ([@balloob] - [#24399]) ([recorder docs]) (breaking change)
|
||||
- Minor improvements to automation test suite ([@frenck] - [#24424])
|
||||
- Upgrade broadlink library ([@Danielhiversen] - [#24450]) ([broadlink docs])
|
||||
- Upgrade ambiclimate library ([@Danielhiversen] - [#24449]) ([ambiclimate docs])
|
||||
- Rename via_hub to via_device ([@Swamp-Ig] - [#24360])
|
||||
- Remove frequest asuswrt log spam ([@jwater7] - [#24448]) ([asuswrt docs])
|
||||
- Publish test results ([@pvizeli] - [#24460])
|
||||
- Life360: Fix config entry handling for accounts imported from configuration ([@pnbruckner] - [#24455]) ([life360 docs])
|
||||
- Add default config to constaint file ([@balloob] - [#24423])
|
||||
- Add websock command to query device for triggers ([@emontnemery] - [#24044]) ([automation docs]) ([light docs])
|
||||
- Uber API is going away on June 13, 2019, remove component ([@robbiet480] - [#24468]) ([uber docs]) (breaking change)
|
||||
- Use met.no instead of yr.no in default config ([@thomasloven] - [#24470])
|
||||
- Bump pyubee to 0.7 to support more models ([@mzdrale] - [#24477]) ([ubee docs])
|
||||
- Somfy open api ([@tetienne] - [#19548]) ([somfy docs]) (new-platform)
|
||||
- Add APRS device tracker component ([@PhilRW] - [#22469]) ([aprs docs]) (new-platform)
|
||||
- Add Linky sensors : yesterday + months + years ([@Quentame] - [#23726]) ([linky docs]) (breaking change)
|
||||
- Add attributs and fix lightlevel inconsistency for LightLevel sensor ([@Cyr-ius] - [#24439]) ([hue docs])
|
||||
- Support ZLO device types to support newer Zigbee devices in ZHA ([@jurriaan] - [#24429]) ([zha docs])
|
||||
- Camera platform for buienradar imagery ([@ties] - [#23358]) ([buienradar docs]) (new-platform)
|
||||
- Position is reversed for horizontal awnings ([@kbickar] - [#23257]) ([tahoma docs]) (breaking change)
|
||||
- Fix aprs imports ([@amelchio] - [#24485]) ([aprs docs])
|
||||
- Version bump for toonapilib to include new API call for fetching thermostat states, which was sometimes missing causing errors in the library ([@reinder83] - [#24459]) ([toon docs])
|
||||
- remove docs from config entries file [skip ci] ([@balloob] - [#24488])
|
||||
- Bump adguardhome to 0.2.1 ([@frenck] - [#24486]) ([adguard docs])
|
||||
- Add Cast discovery to manifest ([@balloob] - [#24504]) ([cast docs]) ([discovery docs])
|
||||
- Bump pyatmo to 2.00 ([@cgtobi] - [#24505]) ([netatmo docs])
|
||||
- Migrate HEOS discovery to manifest ([@balloob] - [#24508]) ([discovery docs]) ([heos docs])
|
||||
- Bumping Keenetic NDMS2 client to 0.0.8 ([@foxel] - [#24469]) ([keenetic_ndms2 docs])
|
||||
- Update DelugeClient to 1.7.1 ([@GuyKh] - [#24518]) ([deluge docs])
|
||||
- Clean up Alexa smart home code ([@balloob] - [#24514]) ([alexa docs]) ([cloud docs])
|
||||
- Remove conversation from default config ([@balloob] - [#24515]) ([default_config docs]) (breaking change)
|
||||
- Refactor yeelight code ([@zewelor] - [#22547]) ([yeelight docs])
|
||||
- Migrate Sonos discovery to manifest ([@balloob] - [#24507]) ([discovery docs]) ([sonos docs])
|
||||
- Cloud: allow managing Alexa entities via UI ([@balloob] - [#24522]) ([alexa docs]) ([cloud docs])
|
||||
- WIP Ps4 Convert entity to Async / Fix entity name changing ([@ktnrg45] - [#24101]) ([ps4 docs])
|
||||
- deCONZ - Change attribute Watts to W ([@Kane610] - [#24535]) ([deconz docs])
|
||||
- Improve stability of netatmo sensor ([@Danielhiversen] - [#24190]) ([netatmo docs])
|
||||
- Update meteoalertapi to 0.1.5 ([@rolfberkenbosch] - [#24528]) ([meteoalarm docs])
|
||||
- PS4 bump to 0.8.3 ([@ktnrg45] - [#24527]) ([ps4 docs])
|
||||
- Pyyaml5.1 ([@BackSlasher] - [#24529])
|
||||
- Added name to sensors ([@cliffordwhansen] - [#24525]) ([synologydsm docs]) (breaking change)
|
||||
- Update requirement version and add switcher_kis services ([@TomerFi] - [#23477]) ([switcher_kis docs])
|
||||
- Flux switch ([@Swamp-Ig] - [#24542])
|
||||
- UniFi simplify update ([@Kane610] - [#24304]) ([unifi docs])
|
||||
- Fix incomfort issue #24478 & bump client ([@zxdavb] - [#24548]) ([incomfort docs])
|
||||
- Handle stacktrace when rtorrent host is unreachable ([@mafrosis] - [#24541]) ([rtorrent docs])
|
||||
- Fix a bug with Ambient PWS reconnection ([@bachya] - [#24540]) ([ambient_station docs])
|
||||
- Update __init__.py ([@lundan] - [#24553]) ([nissan_leaf docs])
|
||||
- Update ambiclimate library ([@Danielhiversen] - [#24562]) ([ambiclimate docs])
|
||||
- Misc. ZHA enhancements ([@dmulcahey] - [#24559]) ([zha docs])
|
||||
- Update pysonos to 0.0.15 ([@amelchio] - [#24565]) ([sonos docs])
|
||||
- Whitelist yeelight predefined effects per device type ([@zewelor] - [#24544]) ([yeelight docs])
|
||||
- Battery attribute & accuracy filter ([@GoNzCiD] - [#24277]) ([traccar docs]) (breaking change)
|
||||
- Bump androidtv to 0.0.16 ([@JeffLIrion] - [#24576]) ([androidtv docs])
|
||||
- Added percent to the disk,memory and swap percent labels ([@cliffordwhansen] - [#24575]) ([glances docs]) (breaking change)
|
||||
- SMA sensor: Add optional path ([@kellerza] - [#24558]) ([sma docs])
|
||||
- Fix geniushub issue #24530 (via a client bump) & handle edge cases ([@zxdavb] - [#24546]) ([geniushub docs])
|
||||
- Add sensitivity and sensitvity_max attributs for binary sensor ([@Cyr-ius] - [#24438]) ([hue docs])
|
||||
- Cloud: Add Alexa report state ([@balloob] - [#24536]) ([alexa docs]) ([cloud docs])
|
||||
- Added toggle service to covers ([@kbickar] - [#23198]) ([cover docs])
|
||||
- Added invert_percent configuration for zwave rollershutter ([@tommasomarchionni] - [#23101]) ([zwave docs])
|
||||
- Add code_arm_required to manual alarm with MQTT ([@JumpMaster] - [#22641]) ([manual_mqtt docs])
|
||||
- Add code_arm_required to manual alarm ([@JumpMaster] - [#22618]) ([demo docs]) ([manual docs])
|
||||
- Add source selection to Samsung TV media player ([@escoand] - [#22612]) ([samsungtv docs])
|
||||
- Fix alarm control panel tests ([@balloob] - [#24586])
|
||||
- Adds integration for Plaato Airlock ([@JohNan] - [#23727]) ([plaato docs]) (new-integration)
|
||||
- Fix honeywell issue #18932 ([@zxdavb] - [#24402]) ([honeywell docs])
|
||||
- Bump base Somfy MyLink library version ([@bendews] - [#24587]) ([somfy_mylink docs])
|
||||
- Better pairing for Xiaomi devices in ZHA ([@dmulcahey] - [#24564]) ([zha docs])
|
||||
- ESPHome config flow only connect when needed ([@OttoWinter] - [#24593]) ([esphome docs])
|
||||
- ESPHome load platforms lazily ([@OttoWinter] - [#24594]) ([esphome docs])
|
||||
- Add ESPHome event generation and user-defined service array support ([@OttoWinter] - [#24595]) ([esphome docs])
|
||||
- Fix validator for lcn.send_keys service ([@alengwenus] - [#24580]) ([lcn docs])
|
||||
- Cloud: Make sure on_connect forwards platform only once ([@balloob] - [#24582]) ([cloud docs])
|
||||
- Add config entry for Met.no ([@bachya] - [#24608]) ([met docs])
|
||||
- Notify Alexa when exposed entities change ([@balloob] - [#24609]) ([alexa docs]) ([cloud docs])
|
||||
- Update pysonos to 0.0.16 ([@amelchio] - [#24607]) ([sonos docs])
|
||||
- check for None state in broadlink ([@Danielhiversen] - [#24589]) ([broadlink docs])
|
||||
- Queensland bushfire alert feed platform ([@exxamalte] - [#24473]) ([qld_bushfire docs]) (new-integration)
|
||||
- Add incomfort sensor and binary_sensor ([@zxdavb] - [#23812]) ([incomfort docs]) (new-platform)
|
||||
- Add support for opencv wheels ([@pvizeli] - [#24620]) ([opencv docs])
|
||||
- tellstick: Add socat to package dependencies ([@torarnv] - [#24531])
|
||||
- Tolerance configuration for dlib_face_identify ([@gonzalezcalleja] - [#24497]) ([dlib_face_identify docs])
|
||||
- Fix sending update when not logged in ([@balloob] - [#24624]) ([cloud docs])
|
||||
- Uses signal dispatcher to invoke state update ([@JohNan] - [#24627]) ([plaato docs])
|
||||
- Add weather alert sensor to meteo france component ([@oncleben31] - [#23128]) ([meteo_france docs])
|
||||
- Set up Met during onboarding ([@balloob] - [#24622]) ([met docs]) ([onboarding docs])
|
||||
- Added ELV PCA 301 smart emeter switch ([@majuss] - [#23300]) ([elv docs]) (new-platform)
|
||||
- Vlc telnet ([@rodripf] - [#24290]) ([vlc_telnet docs]) (beta fix) (new-integration)
|
||||
- Fix device tracker see for entity registry entities ([@MartinHjelmare] - [#24633]) ([device_tracker docs]) (beta fix)
|
||||
- Bump ZHA dependencies. ([@Adminiuga] - [#24637]) ([zha docs]) (beta fix)
|
||||
- Update LIFX brightness during long transitions ([@amelchio] - [#24653]) ([lifx docs]) (beta fix)
|
||||
- Upgrade blinkpy==0.14.1 for startup bugfix ([@fronzbot] - [#24656]) ([blink docs]) (beta fix)
|
||||
- Warn when user tries run custom config flow ([@balloob] - [#24657]) (beta fix)
|
||||
- Bump pysmartthings ([@andrewsayre] - [#24659]) ([smartthings docs]) (beta fix)
|
||||
- Prefere binary with wheels ([@pvizeli] - [#24669]) (beta fix)
|
||||
- Allow extra js modules to be included in frontend ([@thomasloven] - [#24675]) ([frontend docs]) (beta fix)
|
||||
- Fix time expression parsing ([@amelchio] - [#24696]) (beta fix)
|
||||
- ZHA fix device type mappings ([@dmulcahey] - [#24699]) ([zha docs]) (beta fix)
|
||||
- Bump version pyatmo to 2.0.1 ([@cgtobi] - [#24703]) ([netatmo docs]) (beta fix)
|
||||
- Extend websocket method usage to port 8002 in Samsung TV media player ([@2sheds] - [#24716]) ([samsungtv docs]) (beta fix)
|
||||
- Update ZHA dependencies ([@dmulcahey] - [#24718]) ([zha docs]) (beta fix)
|
||||
- Add show_as_state options to Life360 ([@pnbruckner] - [#24725]) ([life360 docs]) (beta fix)
|
||||
- Save cached logi_circle tokens in config folder ([@evanjd] - [#24726]) ([logi_circle docs]) (breaking change) (beta fix)
|
||||
- Update ZHA dependencies. ([@Adminiuga] - [#24736]) ([zha docs]) (beta fix)
|
||||
- AdGuard to update entry ([@balloob] - [#24737]) ([adguard docs]) (beta fix)
|
||||
- Update pysonos to 0.0.17 ([@amelchio] - [#24740]) ([sonos docs]) (beta fix)
|
||||
- Clean up Google Config ([@balloob] - [#24663]) ([cloud docs]) ([google_assistant docs]) (beta fix)
|
||||
- Fix locative device update ([@MartinHjelmare] - [#24744]) ([locative docs]) (beta fix)
|
||||
- Improve Alexa error handling ([@balloob] - [#24745]) ([alexa docs]) ([cloud docs]) ([websocket_api docs]) (beta fix)
|
||||
- Bump pyatmo to v2.1.0 ([@cgtobi] - [#24724]) ([netatmo docs]) (beta fix)
|
||||
- Handle timeouts gracefully ([@cgtobi] - [#24752]) ([netatmo docs]) (beta fix)
|
||||
- Update Waze route dependency to 0.10 ([@johntdyer] - [#24754]) ([waze_travel_time docs]) (beta fix)
|
||||
- Ignore duplicate tradfri discovery ([@balloob] - [#24759]) ([tradfri docs]) (beta fix)
|
||||
- Return correct name for met.no ([@Danielhiversen] - [#24763]) ([met docs]) (beta fix)
|
||||
|
||||
[#19548]: https://github.com/home-assistant/home-assistant/pull/19548
|
||||
[#21110]: https://github.com/home-assistant/home-assistant/pull/21110
|
||||
[#21205]: https://github.com/home-assistant/home-assistant/pull/21205
|
||||
[#21491]: https://github.com/home-assistant/home-assistant/pull/21491
|
||||
[#22428]: https://github.com/home-assistant/home-assistant/pull/22428
|
||||
[#22457]: https://github.com/home-assistant/home-assistant/pull/22457
|
||||
[#22461]: https://github.com/home-assistant/home-assistant/pull/22461
|
||||
[#22469]: https://github.com/home-assistant/home-assistant/pull/22469
|
||||
[#22473]: https://github.com/home-assistant/home-assistant/pull/22473
|
||||
[#22547]: https://github.com/home-assistant/home-assistant/pull/22547
|
||||
[#22612]: https://github.com/home-assistant/home-assistant/pull/22612
|
||||
[#22618]: https://github.com/home-assistant/home-assistant/pull/22618
|
||||
[#22641]: https://github.com/home-assistant/home-assistant/pull/22641
|
||||
[#23101]: https://github.com/home-assistant/home-assistant/pull/23101
|
||||
[#23128]: https://github.com/home-assistant/home-assistant/pull/23128
|
||||
[#23198]: https://github.com/home-assistant/home-assistant/pull/23198
|
||||
[#23257]: https://github.com/home-assistant/home-assistant/pull/23257
|
||||
[#23300]: https://github.com/home-assistant/home-assistant/pull/23300
|
||||
[#23358]: https://github.com/home-assistant/home-assistant/pull/23358
|
||||
[#23477]: https://github.com/home-assistant/home-assistant/pull/23477
|
||||
[#23629]: https://github.com/home-assistant/home-assistant/pull/23629
|
||||
[#23726]: https://github.com/home-assistant/home-assistant/pull/23726
|
||||
[#23727]: https://github.com/home-assistant/home-assistant/pull/23727
|
||||
[#23812]: https://github.com/home-assistant/home-assistant/pull/23812
|
||||
[#23888]: https://github.com/home-assistant/home-assistant/pull/23888
|
||||
[#23986]: https://github.com/home-assistant/home-assistant/pull/23986
|
||||
[#23996]: https://github.com/home-assistant/home-assistant/pull/23996
|
||||
[#24032]: https://github.com/home-assistant/home-assistant/pull/24032
|
||||
[#24044]: https://github.com/home-assistant/home-assistant/pull/24044
|
||||
[#24093]: https://github.com/home-assistant/home-assistant/pull/24093
|
||||
[#24101]: https://github.com/home-assistant/home-assistant/pull/24101
|
||||
[#24106]: https://github.com/home-assistant/home-assistant/pull/24106
|
||||
[#24149]: https://github.com/home-assistant/home-assistant/pull/24149
|
||||
[#24176]: https://github.com/home-assistant/home-assistant/pull/24176
|
||||
[#24185]: https://github.com/home-assistant/home-assistant/pull/24185
|
||||
[#24186]: https://github.com/home-assistant/home-assistant/pull/24186
|
||||
[#24188]: https://github.com/home-assistant/home-assistant/pull/24188
|
||||
[#24189]: https://github.com/home-assistant/home-assistant/pull/24189
|
||||
[#24190]: https://github.com/home-assistant/home-assistant/pull/24190
|
||||
[#24192]: https://github.com/home-assistant/home-assistant/pull/24192
|
||||
[#24194]: https://github.com/home-assistant/home-assistant/pull/24194
|
||||
[#24213]: https://github.com/home-assistant/home-assistant/pull/24213
|
||||
[#24219]: https://github.com/home-assistant/home-assistant/pull/24219
|
||||
[#24220]: https://github.com/home-assistant/home-assistant/pull/24220
|
||||
[#24226]: https://github.com/home-assistant/home-assistant/pull/24226
|
||||
[#24227]: https://github.com/home-assistant/home-assistant/pull/24227
|
||||
[#24228]: https://github.com/home-assistant/home-assistant/pull/24228
|
||||
[#24234]: https://github.com/home-assistant/home-assistant/pull/24234
|
||||
[#24241]: https://github.com/home-assistant/home-assistant/pull/24241
|
||||
[#24242]: https://github.com/home-assistant/home-assistant/pull/24242
|
||||
[#24250]: https://github.com/home-assistant/home-assistant/pull/24250
|
||||
[#24258]: https://github.com/home-assistant/home-assistant/pull/24258
|
||||
[#24259]: https://github.com/home-assistant/home-assistant/pull/24259
|
||||
[#24260]: https://github.com/home-assistant/home-assistant/pull/24260
|
||||
[#24262]: https://github.com/home-assistant/home-assistant/pull/24262
|
||||
[#24263]: https://github.com/home-assistant/home-assistant/pull/24263
|
||||
[#24277]: https://github.com/home-assistant/home-assistant/pull/24277
|
||||
[#24279]: https://github.com/home-assistant/home-assistant/pull/24279
|
||||
[#24280]: https://github.com/home-assistant/home-assistant/pull/24280
|
||||
[#24289]: https://github.com/home-assistant/home-assistant/pull/24289
|
||||
[#24290]: https://github.com/home-assistant/home-assistant/pull/24290
|
||||
[#24294]: https://github.com/home-assistant/home-assistant/pull/24294
|
||||
[#24301]: https://github.com/home-assistant/home-assistant/pull/24301
|
||||
[#24304]: https://github.com/home-assistant/home-assistant/pull/24304
|
||||
[#24307]: https://github.com/home-assistant/home-assistant/pull/24307
|
||||
[#24308]: https://github.com/home-assistant/home-assistant/pull/24308
|
||||
[#24311]: https://github.com/home-assistant/home-assistant/pull/24311
|
||||
[#24315]: https://github.com/home-assistant/home-assistant/pull/24315
|
||||
[#24316]: https://github.com/home-assistant/home-assistant/pull/24316
|
||||
[#24319]: https://github.com/home-assistant/home-assistant/pull/24319
|
||||
[#24322]: https://github.com/home-assistant/home-assistant/pull/24322
|
||||
[#24323]: https://github.com/home-assistant/home-assistant/pull/24323
|
||||
[#24324]: https://github.com/home-assistant/home-assistant/pull/24324
|
||||
[#24326]: https://github.com/home-assistant/home-assistant/pull/24326
|
||||
[#24328]: https://github.com/home-assistant/home-assistant/pull/24328
|
||||
[#24329]: https://github.com/home-assistant/home-assistant/pull/24329
|
||||
[#24330]: https://github.com/home-assistant/home-assistant/pull/24330
|
||||
[#24333]: https://github.com/home-assistant/home-assistant/pull/24333
|
||||
[#24334]: https://github.com/home-assistant/home-assistant/pull/24334
|
||||
[#24336]: https://github.com/home-assistant/home-assistant/pull/24336
|
||||
[#24344]: https://github.com/home-assistant/home-assistant/pull/24344
|
||||
[#24347]: https://github.com/home-assistant/home-assistant/pull/24347
|
||||
[#24350]: https://github.com/home-assistant/home-assistant/pull/24350
|
||||
[#24355]: https://github.com/home-assistant/home-assistant/pull/24355
|
||||
[#24356]: https://github.com/home-assistant/home-assistant/pull/24356
|
||||
[#24358]: https://github.com/home-assistant/home-assistant/pull/24358
|
||||
[#24360]: https://github.com/home-assistant/home-assistant/pull/24360
|
||||
[#24368]: https://github.com/home-assistant/home-assistant/pull/24368
|
||||
[#24370]: https://github.com/home-assistant/home-assistant/pull/24370
|
||||
[#24371]: https://github.com/home-assistant/home-assistant/pull/24371
|
||||
[#24373]: https://github.com/home-assistant/home-assistant/pull/24373
|
||||
[#24374]: https://github.com/home-assistant/home-assistant/pull/24374
|
||||
[#24375]: https://github.com/home-assistant/home-assistant/pull/24375
|
||||
[#24377]: https://github.com/home-assistant/home-assistant/pull/24377
|
||||
[#24394]: https://github.com/home-assistant/home-assistant/pull/24394
|
||||
[#24399]: https://github.com/home-assistant/home-assistant/pull/24399
|
||||
[#24400]: https://github.com/home-assistant/home-assistant/pull/24400
|
||||
[#24402]: https://github.com/home-assistant/home-assistant/pull/24402
|
||||
[#24406]: https://github.com/home-assistant/home-assistant/pull/24406
|
||||
[#24423]: https://github.com/home-assistant/home-assistant/pull/24423
|
||||
[#24424]: https://github.com/home-assistant/home-assistant/pull/24424
|
||||
[#24429]: https://github.com/home-assistant/home-assistant/pull/24429
|
||||
[#24438]: https://github.com/home-assistant/home-assistant/pull/24438
|
||||
[#24439]: https://github.com/home-assistant/home-assistant/pull/24439
|
||||
[#24448]: https://github.com/home-assistant/home-assistant/pull/24448
|
||||
[#24449]: https://github.com/home-assistant/home-assistant/pull/24449
|
||||
[#24450]: https://github.com/home-assistant/home-assistant/pull/24450
|
||||
[#24455]: https://github.com/home-assistant/home-assistant/pull/24455
|
||||
[#24459]: https://github.com/home-assistant/home-assistant/pull/24459
|
||||
[#24460]: https://github.com/home-assistant/home-assistant/pull/24460
|
||||
[#24468]: https://github.com/home-assistant/home-assistant/pull/24468
|
||||
[#24469]: https://github.com/home-assistant/home-assistant/pull/24469
|
||||
[#24470]: https://github.com/home-assistant/home-assistant/pull/24470
|
||||
[#24473]: https://github.com/home-assistant/home-assistant/pull/24473
|
||||
[#24477]: https://github.com/home-assistant/home-assistant/pull/24477
|
||||
[#24485]: https://github.com/home-assistant/home-assistant/pull/24485
|
||||
[#24486]: https://github.com/home-assistant/home-assistant/pull/24486
|
||||
[#24488]: https://github.com/home-assistant/home-assistant/pull/24488
|
||||
[#24497]: https://github.com/home-assistant/home-assistant/pull/24497
|
||||
[#24504]: https://github.com/home-assistant/home-assistant/pull/24504
|
||||
[#24505]: https://github.com/home-assistant/home-assistant/pull/24505
|
||||
[#24507]: https://github.com/home-assistant/home-assistant/pull/24507
|
||||
[#24508]: https://github.com/home-assistant/home-assistant/pull/24508
|
||||
[#24514]: https://github.com/home-assistant/home-assistant/pull/24514
|
||||
[#24515]: https://github.com/home-assistant/home-assistant/pull/24515
|
||||
[#24518]: https://github.com/home-assistant/home-assistant/pull/24518
|
||||
[#24522]: https://github.com/home-assistant/home-assistant/pull/24522
|
||||
[#24525]: https://github.com/home-assistant/home-assistant/pull/24525
|
||||
[#24527]: https://github.com/home-assistant/home-assistant/pull/24527
|
||||
[#24528]: https://github.com/home-assistant/home-assistant/pull/24528
|
||||
[#24529]: https://github.com/home-assistant/home-assistant/pull/24529
|
||||
[#24531]: https://github.com/home-assistant/home-assistant/pull/24531
|
||||
[#24535]: https://github.com/home-assistant/home-assistant/pull/24535
|
||||
[#24536]: https://github.com/home-assistant/home-assistant/pull/24536
|
||||
[#24540]: https://github.com/home-assistant/home-assistant/pull/24540
|
||||
[#24541]: https://github.com/home-assistant/home-assistant/pull/24541
|
||||
[#24542]: https://github.com/home-assistant/home-assistant/pull/24542
|
||||
[#24544]: https://github.com/home-assistant/home-assistant/pull/24544
|
||||
[#24546]: https://github.com/home-assistant/home-assistant/pull/24546
|
||||
[#24548]: https://github.com/home-assistant/home-assistant/pull/24548
|
||||
[#24553]: https://github.com/home-assistant/home-assistant/pull/24553
|
||||
[#24558]: https://github.com/home-assistant/home-assistant/pull/24558
|
||||
[#24559]: https://github.com/home-assistant/home-assistant/pull/24559
|
||||
[#24562]: https://github.com/home-assistant/home-assistant/pull/24562
|
||||
[#24564]: https://github.com/home-assistant/home-assistant/pull/24564
|
||||
[#24565]: https://github.com/home-assistant/home-assistant/pull/24565
|
||||
[#24575]: https://github.com/home-assistant/home-assistant/pull/24575
|
||||
[#24576]: https://github.com/home-assistant/home-assistant/pull/24576
|
||||
[#24580]: https://github.com/home-assistant/home-assistant/pull/24580
|
||||
[#24582]: https://github.com/home-assistant/home-assistant/pull/24582
|
||||
[#24586]: https://github.com/home-assistant/home-assistant/pull/24586
|
||||
[#24587]: https://github.com/home-assistant/home-assistant/pull/24587
|
||||
[#24589]: https://github.com/home-assistant/home-assistant/pull/24589
|
||||
[#24593]: https://github.com/home-assistant/home-assistant/pull/24593
|
||||
[#24594]: https://github.com/home-assistant/home-assistant/pull/24594
|
||||
[#24595]: https://github.com/home-assistant/home-assistant/pull/24595
|
||||
[#24607]: https://github.com/home-assistant/home-assistant/pull/24607
|
||||
[#24608]: https://github.com/home-assistant/home-assistant/pull/24608
|
||||
[#24609]: https://github.com/home-assistant/home-assistant/pull/24609
|
||||
[#24620]: https://github.com/home-assistant/home-assistant/pull/24620
|
||||
[#24622]: https://github.com/home-assistant/home-assistant/pull/24622
|
||||
[#24624]: https://github.com/home-assistant/home-assistant/pull/24624
|
||||
[#24627]: https://github.com/home-assistant/home-assistant/pull/24627
|
||||
[#24633]: https://github.com/home-assistant/home-assistant/pull/24633
|
||||
[#24637]: https://github.com/home-assistant/home-assistant/pull/24637
|
||||
[#24653]: https://github.com/home-assistant/home-assistant/pull/24653
|
||||
[#24656]: https://github.com/home-assistant/home-assistant/pull/24656
|
||||
[#24657]: https://github.com/home-assistant/home-assistant/pull/24657
|
||||
[#24659]: https://github.com/home-assistant/home-assistant/pull/24659
|
||||
[#24663]: https://github.com/home-assistant/home-assistant/pull/24663
|
||||
[#24669]: https://github.com/home-assistant/home-assistant/pull/24669
|
||||
[#24675]: https://github.com/home-assistant/home-assistant/pull/24675
|
||||
[#24696]: https://github.com/home-assistant/home-assistant/pull/24696
|
||||
[#24699]: https://github.com/home-assistant/home-assistant/pull/24699
|
||||
[#24703]: https://github.com/home-assistant/home-assistant/pull/24703
|
||||
[#24716]: https://github.com/home-assistant/home-assistant/pull/24716
|
||||
[#24718]: https://github.com/home-assistant/home-assistant/pull/24718
|
||||
[#24724]: https://github.com/home-assistant/home-assistant/pull/24724
|
||||
[#24725]: https://github.com/home-assistant/home-assistant/pull/24725
|
||||
[#24726]: https://github.com/home-assistant/home-assistant/pull/24726
|
||||
[#24736]: https://github.com/home-assistant/home-assistant/pull/24736
|
||||
[#24737]: https://github.com/home-assistant/home-assistant/pull/24737
|
||||
[#24740]: https://github.com/home-assistant/home-assistant/pull/24740
|
||||
[#24744]: https://github.com/home-assistant/home-assistant/pull/24744
|
||||
[#24745]: https://github.com/home-assistant/home-assistant/pull/24745
|
||||
[#24752]: https://github.com/home-assistant/home-assistant/pull/24752
|
||||
[#24754]: https://github.com/home-assistant/home-assistant/pull/24754
|
||||
[#24759]: https://github.com/home-assistant/home-assistant/pull/24759
|
||||
[#24763]: https://github.com/home-assistant/home-assistant/pull/24763
|
||||
[@2sheds]: https://github.com/2sheds
|
||||
[@Adminiuga]: https://github.com/Adminiuga
|
||||
[@BackSlasher]: https://github.com/BackSlasher
|
||||
[@Cereal2nd]: https://github.com/Cereal2nd
|
||||
[@Cyr-ius]: https://github.com/Cyr-ius
|
||||
[@Danielhiversen]: https://github.com/Danielhiversen
|
||||
[@Emilv2]: https://github.com/Emilv2
|
||||
[@GoNzCiD]: https://github.com/GoNzCiD
|
||||
[@GuyKh]: https://github.com/GuyKh
|
||||
[@JeffLIrion]: https://github.com/JeffLIrion
|
||||
[@JohNan]: https://github.com/JohNan
|
||||
[@JumpMaster]: https://github.com/JumpMaster
|
||||
[@Kane610]: https://github.com/Kane610
|
||||
[@Klikini]: https://github.com/Klikini
|
||||
[@MartinHjelmare]: https://github.com/MartinHjelmare
|
||||
[@OttoWinter]: https://github.com/OttoWinter
|
||||
[@Petro31]: https://github.com/Petro31
|
||||
[@PhilRW]: https://github.com/PhilRW
|
||||
[@Quentame]: https://github.com/Quentame
|
||||
[@SukramJ]: https://github.com/SukramJ
|
||||
[@Swamp-Ig]: https://github.com/Swamp-Ig
|
||||
[@TomerFi]: https://github.com/TomerFi
|
||||
[@aequitas]: https://github.com/aequitas
|
||||
[@alengwenus]: https://github.com/alengwenus
|
||||
[@amelchio]: https://github.com/amelchio
|
||||
[@andre-richter]: https://github.com/andre-richter
|
||||
[@andrewsayre]: https://github.com/andrewsayre
|
||||
[@austinmroczek]: https://github.com/austinmroczek
|
||||
[@bachya]: https://github.com/bachya
|
||||
[@balloob]: https://github.com/balloob
|
||||
[@bendews]: https://github.com/bendews
|
||||
[@bieniu]: https://github.com/bieniu
|
||||
[@brandond]: https://github.com/brandond
|
||||
[@cgtobi]: https://github.com/cgtobi
|
||||
[@cliffordwhansen]: https://github.com/cliffordwhansen
|
||||
[@cpopp]: https://github.com/cpopp
|
||||
[@danielkucera]: https://github.com/danielkucera
|
||||
[@danielperna84]: https://github.com/danielperna84
|
||||
[@danielsjf]: https://github.com/danielsjf
|
||||
[@davidbb]: https://github.com/davidbb
|
||||
[@dmulcahey]: https://github.com/dmulcahey
|
||||
[@drobtravels]: https://github.com/drobtravels
|
||||
[@emontnemery]: https://github.com/emontnemery
|
||||
[@escoand]: https://github.com/escoand
|
||||
[@evanjd]: https://github.com/evanjd
|
||||
[@exxamalte]: https://github.com/exxamalte
|
||||
[@fabaff]: https://github.com/fabaff
|
||||
[@felipediel]: https://github.com/felipediel
|
||||
[@foxel]: https://github.com/foxel
|
||||
[@frenck]: https://github.com/frenck
|
||||
[@fronzbot]: https://github.com/fronzbot
|
||||
[@gibman]: https://github.com/gibman
|
||||
[@gonzalezcalleja]: https://github.com/gonzalezcalleja
|
||||
[@isabellaalstrom]: https://github.com/isabellaalstrom
|
||||
[@jjlawren]: https://github.com/jjlawren
|
||||
[@jkeljo]: https://github.com/jkeljo
|
||||
[@johntdyer]: https://github.com/johntdyer
|
||||
[@jurriaan]: https://github.com/jurriaan
|
||||
[@jwater7]: https://github.com/jwater7
|
||||
[@kbickar]: https://github.com/kbickar
|
||||
[@kellerza]: https://github.com/kellerza
|
||||
[@ktnrg45]: https://github.com/ktnrg45
|
||||
[@kvanhoorn]: https://github.com/kvanhoorn
|
||||
[@lufton]: https://github.com/lufton
|
||||
[@lundan]: https://github.com/lundan
|
||||
[@mafrosis]: https://github.com/mafrosis
|
||||
[@majuss]: https://github.com/majuss
|
||||
[@michaeldavie]: https://github.com/michaeldavie
|
||||
[@mzdrale]: https://github.com/mzdrale
|
||||
[@oncleben31]: https://github.com/oncleben31
|
||||
[@pnbruckner]: https://github.com/pnbruckner
|
||||
[@presslab-us]: https://github.com/presslab-us
|
||||
[@pvizeli]: https://github.com/pvizeli
|
||||
[@reinder83]: https://github.com/reinder83
|
||||
[@robbiet480]: https://github.com/robbiet480
|
||||
[@rodripf]: https://github.com/rodripf
|
||||
[@rolfberkenbosch]: https://github.com/rolfberkenbosch
|
||||
[@scarface-4711]: https://github.com/scarface-4711
|
||||
[@scop]: https://github.com/scop
|
||||
[@soldag]: https://github.com/soldag
|
||||
[@syssi]: https://github.com/syssi
|
||||
[@tetienne]: https://github.com/tetienne
|
||||
[@thomasloven]: https://github.com/thomasloven
|
||||
[@ties]: https://github.com/ties
|
||||
[@tommasomarchionni]: https://github.com/tommasomarchionni
|
||||
[@tommyjlong]: https://github.com/tommyjlong
|
||||
[@torarnv]: https://github.com/torarnv
|
||||
[@victorcerutti]: https://github.com/victorcerutti
|
||||
[@z0mbieprocess]: https://github.com/z0mbieprocess
|
||||
[@zewelor]: https://github.com/zewelor
|
||||
[@zxdavb]: https://github.com/zxdavb
|
||||
[adguard docs]: /components/adguard/
|
||||
[aftership docs]: /components/aftership/
|
||||
[alexa docs]: /components/alexa/
|
||||
[ambiclimate docs]: /components/ambiclimate/
|
||||
[ambient_station docs]: /components/ambient_station/
|
||||
[amcrest docs]: /components/amcrest/
|
||||
[androidtv docs]: /components/androidtv/
|
||||
[aprs docs]: /components/aprs/
|
||||
[asuswrt docs]: /components/asuswrt/
|
||||
[automation docs]: /components/automation/
|
||||
[awair docs]: /components/awair/
|
||||
[blink docs]: /components/blink/
|
||||
[broadlink docs]: /components/broadlink/
|
||||
[buienradar docs]: /components/buienradar/
|
||||
[cast docs]: /components/cast/
|
||||
[cloud docs]: /components/cloud/
|
||||
[cover docs]: /components/cover/
|
||||
[ddwrt docs]: /components/ddwrt/
|
||||
[deconz docs]: /components/deconz/
|
||||
[default_config docs]: /components/default_config/
|
||||
[deluge docs]: /components/deluge/
|
||||
[demo docs]: /components/demo/
|
||||
[denonavr docs]: /components/denonavr/
|
||||
[device_tracker docs]: /components/device_tracker/
|
||||
[discord docs]: /components/discord/
|
||||
[discovery docs]: /components/discovery/
|
||||
[dlib_face_identify docs]: /components/dlib_face_identify/
|
||||
[ebusd docs]: /components/ebusd/
|
||||
[elv docs]: /components/elv/
|
||||
[environment_canada docs]: /components/environment_canada/
|
||||
[esphome docs]: /components/esphome/
|
||||
[frontend docs]: /components/frontend/
|
||||
[geniushub docs]: /components/geniushub/
|
||||
[gitlab_ci docs]: /components/gitlab_ci/
|
||||
[glances docs]: /components/glances/
|
||||
[google docs]: /components/google/
|
||||
[google_assistant docs]: /components/google_assistant/
|
||||
[google_cloud docs]: /components/google_cloud/
|
||||
[heos docs]: /components/heos/
|
||||
[homeassistant docs]: /components/homeassistant/
|
||||
[homematic docs]: /components/homematic/
|
||||
[homematicip_cloud docs]: /components/homematicip_cloud/
|
||||
[honeywell docs]: /components/honeywell/
|
||||
[hue docs]: /components/hue/
|
||||
[incomfort docs]: /components/incomfort/
|
||||
[integration docs]: /components/integration/
|
||||
[itunes docs]: /components/itunes/
|
||||
[keenetic_ndms2 docs]: /components/keenetic_ndms2/
|
||||
[lcn docs]: /components/lcn/
|
||||
[life360 docs]: /components/life360/
|
||||
[lifx docs]: /components/lifx/
|
||||
[light docs]: /components/light/
|
||||
[linky docs]: /components/linky/
|
||||
[locative docs]: /components/locative/
|
||||
[logi_circle docs]: /components/logi_circle/
|
||||
[manual docs]: /components/manual/
|
||||
[manual_mqtt docs]: /components/manual_mqtt/
|
||||
[mastodon docs]: /components/mastodon/
|
||||
[media_extractor docs]: /components/media_extractor/
|
||||
[met docs]: /components/met/
|
||||
[meteo_france docs]: /components/meteo_france/
|
||||
[meteoalarm docs]: /components/meteoalarm/
|
||||
[mqtt docs]: /components/mqtt/
|
||||
[netatmo docs]: /components/netatmo/
|
||||
[nissan_leaf docs]: /components/nissan_leaf/
|
||||
[onboarding docs]: /components/onboarding/
|
||||
[opencv docs]: /components/opencv/
|
||||
[plaato docs]: /components/plaato/
|
||||
[ps4 docs]: /components/ps4/
|
||||
[qld_bushfire docs]: /components/qld_bushfire/
|
||||
[rainmachine docs]: /components/rainmachine/
|
||||
[recorder docs]: /components/recorder/
|
||||
[remote docs]: /components/remote/
|
||||
[rflink docs]: /components/rflink/
|
||||
[rtorrent docs]: /components/rtorrent/
|
||||
[samsungtv docs]: /components/samsungtv/
|
||||
[sense docs]: /components/sense/
|
||||
[simplisafe docs]: /components/simplisafe/
|
||||
[sisyphus docs]: /components/sisyphus/
|
||||
[sma docs]: /components/sma/
|
||||
[smartthings docs]: /components/smartthings/
|
||||
[smarty docs]: /components/smarty/
|
||||
[solaredge_local docs]: /components/solaredge_local/
|
||||
[somfy docs]: /components/somfy/
|
||||
[somfy_mylink docs]: /components/somfy_mylink/
|
||||
[sonos docs]: /components/sonos/
|
||||
[streamlabswater docs]: /components/streamlabswater/
|
||||
[switcher_kis docs]: /components/switcher_kis/
|
||||
[synologydsm docs]: /components/synologydsm/
|
||||
[tahoma docs]: /components/tahoma/
|
||||
[tibber docs]: /components/tibber/
|
||||
[toon docs]: /components/toon/
|
||||
[totalconnect docs]: /components/totalconnect/
|
||||
[traccar docs]: /components/traccar/
|
||||
[tradfri docs]: /components/tradfri/
|
||||
[ubee docs]: /components/ubee/
|
||||
[uber docs]: /components/uber/
|
||||
[unifi docs]: /components/unifi/
|
||||
[velbus docs]: /components/velbus/
|
||||
[velux docs]: /components/velux/
|
||||
[vera docs]: /components/vera/
|
||||
[vlc_telnet docs]: /components/vlc_telnet/
|
||||
[waze_travel_time docs]: /components/waze_travel_time/
|
||||
[webostv docs]: /components/webostv/
|
||||
[websocket_api docs]: /components/websocket_api/
|
||||
[xiaomi_aqara docs]: /components/xiaomi_aqara/
|
||||
[yeelight docs]: /components/yeelight/
|
||||
[yr docs]: /components/yr/
|
||||
[zha docs]: /components/zha/
|
||||
[zwave docs]: /components/zwave/
|
||||
BIN
source/images/blog/2019-06-release-95/components.png
Normal file
BIN
source/images/blog/2019-06-release-95/components.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 85 KiB |
BIN
source/images/blog/2019-06-release-95/frenck.png
Normal file
BIN
source/images/blog/2019-06-release-95/frenck.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 110 KiB |
BIN
source/images/blog/2019-06-release-95/social.png
Normal file
BIN
source/images/blog/2019-06-release-95/social.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 268 KiB |
BIN
source/images/screenshots/qld-bushfire-feed-map.png
Normal file
BIN
source/images/screenshots/qld-bushfire-feed-map.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 109 KiB |
BIN
source/images/supported_brands/aprs.png
Normal file
BIN
source/images/supported_brands/aprs.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 15 KiB |
BIN
source/images/supported_brands/elv.png
Normal file
BIN
source/images/supported_brands/elv.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 45 KiB |
BIN
source/images/supported_brands/environment_canada.png
Normal file
BIN
source/images/supported_brands/environment_canada.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 10 KiB |
BIN
source/images/supported_brands/google_cloud.png
Normal file
BIN
source/images/supported_brands/google_cloud.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 20 KiB |
BIN
source/images/supported_brands/life360.png
Normal file
BIN
source/images/supported_brands/life360.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 14 KiB |
BIN
source/images/supported_brands/plaato.png
Normal file
BIN
source/images/supported_brands/plaato.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 37 KiB |
BIN
source/images/supported_brands/salda.png
Normal file
BIN
source/images/supported_brands/salda.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 14 KiB |
BIN
source/images/supported_brands/somfy.png
Normal file
BIN
source/images/supported_brands/somfy.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 18 KiB |
BIN
source/images/supported_brands/streamlabswater.png
Normal file
BIN
source/images/supported_brands/streamlabswater.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 16 KiB |
Loading…
x
Reference in New Issue
Block a user