mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-23 17:27:19 +00:00
Merge branch 'current' into next
This commit is contained in:
Franck Nijhof
commit
110661ad19
@ -101,7 +101,7 @@ social:
|
||||
# Home Assistant release details
|
||||
current_major_version: 0
|
||||
current_minor_version: 107
|
||||
current_patch_version: 0
|
||||
current_patch_version: 1
|
||||
date_released: 2020-03-18
|
||||
|
||||
# Either # or the anchor link to latest release notes in the blog post.
|
||||
|
||||
@ -52,12 +52,6 @@ Event `service_executed` is fired by the service handler to indicate the service
|
||||
| ----------------- | ----------------------------------------------------------------------------------------- |
|
||||
| `service_call_id` | String with the unique call id of the service call that was executed. Example: `23123-4`. |
|
||||
|
||||
<div class='note warning'>
|
||||
|
||||
Starting with 0.84, it is no longer possible to listen for event `service_executed`.
|
||||
|
||||
</div>
|
||||
|
||||
### Event `platform_discovered`
|
||||
|
||||
Event `platform_discovered` is fired when a new platform has been discovered by the [`discovery`](/integrations/discovery/) component.
|
||||
|
||||
@ -108,10 +108,6 @@ headers:
|
||||
type: [list, string]
|
||||
{% endconfiguration %}
|
||||
|
||||
<div class='note warning'>
|
||||
Make sure that the URL exactly matches your endpoint or resource.
|
||||
</div>
|
||||
|
||||
## Examples
|
||||
|
||||
In this section you find some real-life examples of how to use this sensor.
|
||||
|
||||
@ -27,7 +27,7 @@ Generate a Client ID and Client Secret on
|
||||
1. Set the 'Application Name' (the name of the application asking for consent) to anything you want. We suggest "Home-Assistant".
|
||||
1. Save this page. You don't have to fill out anything else here.
|
||||
1. Click on the menu item, Credentials, then click 'Create credentials' > OAuth client ID.
|
||||
1. Set the Application type to 'Other' and give this credential set a name (like "Home Assistant Credentials") then click 'Create'.
|
||||
1. Set the Application type to 'Other' (if not present, choose 'TV and Limited Input') and give this credential set a name (like "Home Assistant Credentials") then click 'Create'.
|
||||
1. Copy the client ID and client secret from the page that follows into a text editor temporarily as you will need to put these in your `configuration.yaml` file.
|
||||
1. Click on the menu item, Library, then search for "Google Calendar API" and enable it (if it isn't already enabled automatically through this process).
|
||||
|
||||
|
||||
@ -49,7 +49,3 @@ The Certificate Expiry entities provide extra attributes to represent the state
|
||||
| ---- | ----------- |
|
||||
| `is_valid` | If the certificate is able to be validated: `True` / `False`.
|
||||
| `error` | A human-readable error description if the certificate is considered invalid, "None" otherwise.
|
||||
|
||||
<div class='note warning'>
|
||||
Make sure that the URL exactly matches your endpoint or resource.
|
||||
</div>
|
||||
|
||||
@ -13,6 +13,16 @@ ha_codeowners:
|
||||
|
||||
The DirecTV platform allows you to control a [DirecTV](https://www.directv.com) receiver and its client devices.
|
||||
|
||||
### Requirements
|
||||
|
||||
For proper integration with Home Assistant, your DirecTV device settings should allow "External Access".
|
||||
|
||||
This is done via series of settings found via "Menu > Settings & Help > Settings > Whole Home > External Device":
|
||||
|
||||
- External Access: Allow
|
||||
- Current Program: Allow
|
||||
- Recordings: Allow
|
||||
|
||||
### Configuration
|
||||
|
||||
Go to the integrations page in your configuration and click on new integration -> DirecTV.
|
||||
|
||||
@ -25,7 +25,6 @@ Home Assistant can discover and automatically configure [zeroconf](https://en.wi
|
||||
* [NETGEAR routers](/integrations/netgear)
|
||||
* [Panasonic Viera](/integrations/panasonic_viera)
|
||||
* [Philips Hue](/integrations/hue)
|
||||
* [Plex Media Server](/integrations/plex#media-player)
|
||||
* [Roku media player](/integrations/roku#media-player)
|
||||
* [SABnzbd downloader](/integrations/sabnzbd)
|
||||
* [Samsung SyncThru Printer](/integrations/syncthru)
|
||||
@ -86,7 +85,6 @@ Valid values for ignore are:
|
||||
* `openhome`: Linn / Openhome
|
||||
* `panasonic_viera`: Panasonic Viera
|
||||
* `philips_hue`: Philips Hue
|
||||
* `plex_mediaserver`: Plex Media Server
|
||||
* `roku`: Roku media player
|
||||
* `sabnzbd`: SABnzbd downloader
|
||||
* `samsung_printer`: Samsung SyncThru Printer
|
||||
|
||||
@ -13,12 +13,6 @@ The `haveibeenpwned` sensor platform creates sensors that check for breached ema
|
||||
|
||||
## Configuration
|
||||
|
||||
<div class='note warning'>
|
||||
|
||||
The HaveIBeenPwned API is no longer a free API. For more information about this change read the HIBP creator's [blogpost regarding the change](https://www.troyhunt.com/authentication-and-the-have-i-been-pwned-api/).
|
||||
|
||||
</div>
|
||||
|
||||
In order to use this integration you need to purchase an API key. Visit the [API key page](https://haveibeenpwned.com/API/Key) on the HIBP website to purchase one.
|
||||
|
||||
## Configuration
|
||||
|
||||
@ -13,33 +13,4 @@ ha_domain: met
|
||||
|
||||
The `met` platform uses the [Met.no](https://met.no/) web service as a source for meteorological data for your location. The weather forecast is delivered by the Norwegian Meteorological Institute and the NRK.
|
||||
|
||||
<div class='note warning'>
|
||||
Configuration of the Met.no platform via configuration.yaml is deprecated from version 0.95
|
||||
</div>
|
||||
|
||||
## Configuration
|
||||
|
||||
To add Met.no to your installation, go to Configuration >> Integrations in the UI and enable the Met.no integration. By default the values will be taken from the Home Assistant configuration.
|
||||
|
||||
{% configuration %}
|
||||
name:
|
||||
description: Manually specify Name.
|
||||
required: true
|
||||
type: string
|
||||
default: Provided by Home Assistant configuration
|
||||
latitude:
|
||||
description: Manually specify latitude.
|
||||
required: true
|
||||
type: float
|
||||
default: Provided by Home Assistant configuration
|
||||
longitude:
|
||||
description: Manually specify longitude.
|
||||
required: true
|
||||
type: float
|
||||
default: Provided by Home Assistant configuration
|
||||
altitude:
|
||||
description: Manually specify altitude.
|
||||
required: false
|
||||
type: integer
|
||||
default: Provided by Home Assistant configuration
|
||||
{% endconfiguration %}
|
||||
To add Met.no to your installation, go to Configuration >> Integrations in the UI and enable the Met.no integration.
|
||||
|
||||
@ -5,7 +5,6 @@ ha_category:
|
||||
- Hub
|
||||
- Environment
|
||||
- Weather
|
||||
- Binary Sensor
|
||||
- Sensor
|
||||
- Climate
|
||||
- Camera
|
||||
@ -21,7 +20,6 @@ The `netatmo` integration platform is the main integration to integrate all Neta
|
||||
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
- [Binary Sensor](#binary-sensor)
|
||||
- [Camera](#camera)
|
||||
- [Climate](#climate)
|
||||
- [Sensor](#sensor)
|
||||
@ -70,13 +68,6 @@ That's it. You can copy and paste your new `client id` and `client secret` in yo
|
||||
<img src='/images/screenshots/netatmo_api.png' />
|
||||
</p>
|
||||
|
||||
## Binary Sensor
|
||||
|
||||
This integration allows you to get the latest event seen by the camera.
|
||||
|
||||
If multiple cameras are available then each monitored condition
|
||||
will create a specific sensor for each camera
|
||||
|
||||
## Camera
|
||||
|
||||
The `netatmo` camera platform is consuming the information provided by a [Netatmo](https://www.netatmo.com) camera. This integration allows you to view the current live stream created by the Camera.
|
||||
@ -89,3 +80,11 @@ The `netatmo` thermostat platform is consuming the information provided by a [Ne
|
||||
|
||||
The `netatmo` sensor platform is consuming the information provided by a [Netatmo Weather Station](https://www.netatmo.com/en-us/weather/weatherstation) or a
|
||||
[Netatmo Home Coach](https://www.netatmo.com/en-us/aircare/homecoach) [Netatmo](https://www.netatmo.com) device.
|
||||
|
||||
## Webhooks
|
||||
|
||||
The smart indoor and outdoor cameras, as well as the smart smoke alarm, send instant events to Home Assistant by using webhooks. It is required to have your camera enabled in Home Assistant.
|
||||
|
||||
To be able to receive events from Netatmo, your Home Assistant instance needs to be accessible from the web. To achieve this you can either use your Nabu Casa account or ([Home Assistant instructions](/addons/duckdns/)) and you need to have the `base_url` configured for the HTTP integration ([documentation](/integrations/http/#base_url)).
|
||||
|
||||
Events coming in from Netatmo will be available as an event in Home Assistant and are fired as `netatmo_event`, along with their data. You can use these events to trigger automations.
|
||||
|
||||
@ -8,16 +8,10 @@ ha_iot_class: Cloud Polling
|
||||
ha_domain: pocketcasts
|
||||
---
|
||||
|
||||
The `pocketcasts` sensor platform lets you monitor how many unplayed episodes you have of your favorite podcasts at [Pocket Casts](https://play.pocketcasts.com/).
|
||||
The `pocketcasts` sensor platform lets you monitor how many unplayed episodes you have of your favorite podcasts at [Pocket Casts](https://play.pocketcasts.com/). This integration requires a [Pocket Casts + Plus](https://www.pocketcasts.com/plus/) subscription to work!
|
||||
|
||||
## Configuration
|
||||
|
||||
<div class='note warning'>
|
||||
|
||||
This integration requires a [Pocket Casts + Plus](https://www.pocketcasts.com/plus/) subscription to work!
|
||||
|
||||
</div>
|
||||
|
||||
To enable this sensor, add the following lines to your `configuration.yaml`:
|
||||
|
||||
```yaml
|
||||
|
||||
@ -35,11 +35,11 @@ host:
|
||||
required: true
|
||||
type: string
|
||||
username:
|
||||
description: The username for accessing your Ring account.
|
||||
description: The username for accessing your QVR account.
|
||||
required: true
|
||||
type: string
|
||||
password:
|
||||
description: The password for accessing your Ring account.
|
||||
description: The password for accessing your QVR account.
|
||||
required: true
|
||||
type: string
|
||||
exclude_channels:
|
||||
|
||||
@ -119,10 +119,6 @@ force_update:
|
||||
default: false
|
||||
{% endconfiguration %}
|
||||
|
||||
<div class='note warning'>
|
||||
Make sure that the URL exactly matches your endpoint or resource.
|
||||
</div>
|
||||
|
||||
<div class='note'>
|
||||
|
||||
Use either `resource` or `resource_template`.
|
||||
@ -414,7 +410,7 @@ sensor:
|
||||
value_template: '{{ states.sensor.steam_system_data.attributes["time0"] }}'
|
||||
unit_of_measurement: "minutes"
|
||||
|
||||
switch:
|
||||
switch:
|
||||
- platform: template
|
||||
switches:
|
||||
steam:
|
||||
@ -441,7 +437,7 @@ switch:
|
||||
- service: homeassistant.update_entity
|
||||
data:
|
||||
entity_id: sensor.steam_system_data
|
||||
friendly_name: Steam
|
||||
friendly_name: Steam
|
||||
|
||||
rest_command:
|
||||
set_steam_led:
|
||||
@ -454,7 +450,7 @@ For reference, the XML content of endpoint shown above example is below:
|
||||
|
||||
```xml
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
|
||||
|
||||
<response>
|
||||
<scan>0</scan>
|
||||
<ver>12556</ver>
|
||||
|
||||
@ -121,6 +121,7 @@ For example: for model `UN55NU7100`, the `UN55` would mean it's an LED, North Am
|
||||
- UE65KS8005 (On/Off, Forward/Backward, Volume are OK, but no Play button)
|
||||
- UE49KU6470 (On/Off, Forward/Backward, Volume are OK, but no Play button)
|
||||
- UE46ES5500 (partially supported, turn on doesn't work)
|
||||
- UE55NU8070
|
||||
|
||||
#### Models tested but not yet working
|
||||
|
||||
|
||||
@ -19,7 +19,7 @@ You can also add additional stations manually, referencing them via their IDs. T
|
||||
|
||||
## Setup
|
||||
|
||||
To use this sensor you need an API key from [tankerkoenig](https://creativecommons.tankerkoenig.de). Go to [api-key](https://creativecommons.tankerkoenig.de/api-key), fill out the form and request a key. The API is free, but requests should be limited to less than once every 5 minutes.
|
||||
To use this sensor you need an API key from [tankerkoenig](https://creativecommons.tankerkoenig.de). Go to [tankerkoenig API](https://creativecommons.tankerkoenig.de) and click on API-KEY in the top right, fill out the form and request a key. The API is free, but requests should be limited to less than once every 5 minutes.
|
||||
|
||||
## Configuration
|
||||
|
||||
@ -30,7 +30,7 @@ To enable this platform, add the following lines to your `configuration.yaml`:
|
||||
tankerkoenig:
|
||||
api_key: YOUR_API_KEY
|
||||
radius: 1
|
||||
fuel_type:
|
||||
fuel_types:
|
||||
- "diesel"
|
||||
```
|
||||
|
||||
|
||||
@ -19,12 +19,6 @@ ha_domain: tellduslive
|
||||
|
||||
The `tellduslive` integration let you connect to [Telldus Live](https://live.telldus.com). It's cloud platform that connects to your Tellstick Net or Tellstick ZNet connected gear at home.
|
||||
|
||||
<div class='note warning'>
|
||||
|
||||
If you are upgrading from 0.58 or older, you need to remove all Telldus configuration from your `configuration.yaml` file before continuing.
|
||||
|
||||
</div>
|
||||
|
||||
Home Assistant will automatically discover the presence of a Tellstick Net or Tellstick ZNet on your local network if the [discovery]({{site_root}}/integrations/discovery/) integration is enabled. When discovery and the key exchange with Telldus Live have been completed, you will be presented with an option to integrate with the cloud or local API for direct communication with your hardware in your LAN. Local API supports only one device at this stage. Local API is only supported with the Znet Lite products, the older hardware (such as Tellstick Net) does not support local API.
|
||||
|
||||
## Configuration
|
||||
|
||||
@ -169,7 +169,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
- The `view` and `control` configuration options for a group.
|
||||
- The `group.set_visibility` service call
|
||||
- The `control`, `visible`, `view` options on the `group.set` service call
|
||||
|
||||
|
||||
Please ensure your configuration and automations do not use these anymore. - ([@frenck] - [#32021]) ([group docs])
|
||||
|
||||
- **Input Number** - Adds an entity ID to input_number warning. Passing an out of range value to `input_number.set_value` will now raise a validation error. Incrementing/decrementing an `input_number` will no longer cause warnings. - ([@balloob] - [#32012]) ([input_number docs])
|
||||
@ -211,7 +211,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
- **Automation** - The `hide_entity` configuration option on an automation was deprecated in Home Assistant 0.105 and is removed in this release. It was used for the old states UI, which is no longer available, making this option obsolete. Please ensure your configuration is not using this option. - ([@frenck] - [#32038]) ([automation docs])
|
||||
|
||||
- **IQVIA** - When configuring IQVIA via `configuration.yaml`, the `monitored_conditions` key has been deprecated and will be removed in 0.114.0. All sensors are now created by default. (ADR-0003) - ([@bachya] - [#32223]) ([iqvia docs])
|
||||
|
||||
|
||||
Example YAML configuration:
|
||||
|
||||
```yaml
|
||||
@ -375,6 +375,20 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
- Updated frontend to 20200318.0 ([@bramkragten] - [#32931]) ([frontend docs]) (beta fix)
|
||||
- Fix flaky tests for HMIPC ([@SukramJ] - [#32806]) (beta fix)
|
||||
|
||||
## Release 0.107.1 - March 18
|
||||
|
||||
- Updated frontend to 20200318.1 ([@bramkragten] - [#32957]) ([frontend docs])
|
||||
- Add device automation as frontend dependency ([@balloob] - [#32962]) ([frontend docs])
|
||||
- Fix zone config ([@balloob] - [#32963]) ([zone docs])
|
||||
|
||||
[#32957]: https://github.com/home-assistant/core/pull/32957
|
||||
[#32962]: https://github.com/home-assistant/core/pull/32962
|
||||
[#32963]: https://github.com/home-assistant/core/pull/32963
|
||||
[@balloob]: https://github.com/balloob
|
||||
[@bramkragten]: https://github.com/bramkragten
|
||||
[frontend docs]: /integrations/frontend/
|
||||
[zone docs]: /integrations/zone/
|
||||
|
||||
## All changes
|
||||
|
||||
- Nuki: add support for unique id ([@pvizeli] - [#31824]) ([nuki docs])
|
||||
|
||||
@ -14,8 +14,9 @@ Screenshot of an entities card with a picture header and buttons footer.
|
||||
Widget to show a picture as a header or a footer. A picture can have touch actions associated with it.
|
||||
|
||||
```yaml
|
||||
type: picture
|
||||
image: 'https://www.home-assistant.io/images/lovelace/header-footer/balloons-header.png'
|
||||
header:
|
||||
type: picture
|
||||
image: 'https://www.home-assistant.io/images/lovelace/header-footer/balloons-header.png'
|
||||
```
|
||||
|
||||
{% configuration header-footer %}
|
||||
@ -37,7 +38,7 @@ hold_action:
|
||||
type: map
|
||||
double_tap_action:
|
||||
required: false
|
||||
description: Action to take on tap-and-hold. See [action documentation](/lovelace/actions/#double-tap-action).
|
||||
description: Action to take on double tap. See [action documentation](/lovelace/actions/#double-tap-action).
|
||||
type: map
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -46,13 +47,14 @@ double_tap_action:
|
||||
Widget to show entities as buttons in the header or footer.
|
||||
|
||||
```yaml
|
||||
type: buttons
|
||||
entities:
|
||||
- script.launch_confetti
|
||||
- entity: script.swirl_lights
|
||||
icon: 'mdi:track-light'
|
||||
- entity: script.run_siren
|
||||
icon: 'mdi:alarm-light'
|
||||
footer:
|
||||
type: buttons
|
||||
entities:
|
||||
- script.launch_confetti
|
||||
- entity: script.swirl_lights
|
||||
icon: 'mdi:track-light'
|
||||
- entity: script.run_siren
|
||||
icon: 'mdi:alarm-light'
|
||||
```
|
||||
|
||||
{% configuration header-footer %}
|
||||
|
||||
@ -60,7 +60,7 @@ lovelace:
|
||||
mode: storage
|
||||
# Add yaml dashboards
|
||||
dashboards:
|
||||
yaml:
|
||||
lovelace-yaml:
|
||||
mode: yaml
|
||||
title: YAML
|
||||
icon: mdi:script
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user