From af2e5c223d9fea7a22e6704da346365d57803130 Mon Sep 17 00:00:00 2001 From: Samuele Illuminati Date: Tue, 10 Mar 2020 19:40:30 +0100 Subject: [PATCH 1/9] =?UTF-8?q?Updated=20google=5Fassistant.markdown:=20ad?= =?UTF-8?q?ded=20`/r/YOUR=5FPROJECT=5FID`=E2=80=A6=20(#12324)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Without the `/r/YOUR_PROJECT_ID` the redirect_uri wasn't working and I wasn't successful in linking the account via the Home app. See also: https://developers.google.com/assistant/identity/oauth2 --- source/_integrations/google_assistant.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/google_assistant.markdown b/source/_integrations/google_assistant.markdown index 689d6de6b3a..365737ff32b 100644 --- a/source/_integrations/google_assistant.markdown +++ b/source/_integrations/google_assistant.markdown @@ -38,7 +38,7 @@ You will need to create a service account [Create Service account key](https://c 2. `Account linking` is required for your app to interact with Home Assistant. Set this up under the `Quick Setup` section. 1. Leave it at the default `No, I only want to allow account creation on my website` and select `Next`. 2. For the `Linking type` select `OAuth` and `Authorization Code`. Click `Next` - 3. Client ID: `https://oauth-redirect.googleusercontent.com/`, the trailing slash is important. + 3. Client ID: `https://oauth-redirect.googleusercontent.com/r/YOUR_PROJECT_ID`. 4. Client Secret: Anything you like, Home Assistant doesn't need this field. 5. Authorization URL (replace with your actual URL): `https://[YOUR HOME ASSISTANT URL:PORT]/auth/authorize`. 6. Token URL (replace with your actual URL): `https://[YOUR HOME ASSISTANT URL:PORT]/auth/token`. Click `Next` From d337bbb314693c9405982dd5e4a30a1e017eb067 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Tue, 10 Mar 2020 11:52:14 -0700 Subject: [PATCH 2/9] Release 106.6 --- _config.yml | 4 ++-- source/_posts/2020-02-26-release-106.markdown | 20 +++++++++++++++++++ 2 files changed, 22 insertions(+), 2 deletions(-) diff --git a/_config.yml b/_config.yml index 735d2b72708..be6e0715fee 100644 --- a/_config.yml +++ b/_config.yml @@ -101,8 +101,8 @@ social: # Home Assistant release details current_major_version: 0 current_minor_version: 106 -current_patch_version: 5 -date_released: 2020-03-03 +current_patch_version: 6 +date_released: 2020-03-10 # Either # or the anchor link to latest release notes in the blog post. # Must be prefixed with a # and have double quotes around it. diff --git a/source/_posts/2020-02-26-release-106.markdown b/source/_posts/2020-02-26-release-106.markdown index 362767ba7eb..2a8198f96f7 100644 --- a/source/_posts/2020-02-26-release-106.markdown +++ b/source/_posts/2020-02-26-release-106.markdown @@ -429,6 +429,26 @@ Added a Coronavirus integration to help monitor the ongoing epidemic. [More info [@balloob]: https://github.com/balloob [@bdraco]: https://github.com/bdraco +## Release 0.106.6 - March 10 + +- Get pending iCloud devices when available + request again when needs an update ([@Quentame] - [#32400]) ([icloud docs]) +- Send messages conforming new facebook policy ([@chmielowiec] - [#32516]) ([facebook docs]) +- Update python-velbus to fix a missing data file ([@Cereal2nd] - [#32580]) ([velbus docs]) +- Upgrade to coronavirus 1.1.0 ([@balloob] - [#32648]) ([coronavirus docs]) + +[#32400]: https://github.com/home-assistant/core/pull/32400 +[#32516]: https://github.com/home-assistant/core/pull/32516 +[#32580]: https://github.com/home-assistant/core/pull/32580 +[#32648]: https://github.com/home-assistant/core/pull/32648 +[@Cereal2nd]: https://github.com/Cereal2nd +[@Quentame]: https://github.com/Quentame +[@balloob]: https://github.com/balloob +[@chmielowiec]: https://github.com/chmielowiec +[coronavirus docs]: /integrations/coronavirus/ +[facebook docs]: /integrations/facebook/ +[icloud docs]: /integrations/icloud/ +[velbus docs]: /integrations/velbus/ + ## All changes - Change scan_interval defaults for Tesla ([@alandtse] - [#31194]) ([tesla docs]) (breaking change) From f84c6bdca6544aeadcb32312891bbe6db7303ded Mon Sep 17 00:00:00 2001 From: Vilppu Vuorinen Date: Tue, 10 Mar 2020 21:44:36 +0200 Subject: [PATCH 3/9] Add MELCloud Air-to-Water device documentation (#12159) --- source/_integrations/melcloud.markdown | 48 +++++++++++++++++++++++++- 1 file changed, 47 insertions(+), 1 deletion(-) diff --git a/source/_integrations/melcloud.markdown b/source/_integrations/melcloud.markdown index 578d02d1389..0b3432a16f0 100644 --- a/source/_integrations/melcloud.markdown +++ b/source/_integrations/melcloud.markdown @@ -16,7 +16,7 @@ The `melcloud` integration integrates Mitsubishi Electric's [MELCloud](https://w ## Device support - Air-to-Air heat pumps, e.g., AC units - **Supported** -- Air-to-Water heat pumps - **Work in progress** +- Air-to-Water heat pumps - **Supported** - Energy recovery ventilators - **Not supported** - Other - **Not supported** @@ -64,3 +64,49 @@ The following attributes are available for `sensor` platform entities: - Room temperature - Energy - The total consumed energy in kWh. **Not supported by all models.** + +## Air-to-Water device + +An Air-to-Water device provides `water_heater`, `climate` and `sensor` platforms. + +### Climate + +A `climate` platform entity is provided for each radiator zone in the air-to-water system. The following parameters can be controlled: + +- Target room temperature + +The radiators need to be configured to run in room temperature control mode either through the local HMI or MELCloud. Flow temperature and curve modes are not supported. + +Some air-to-water devices allow cooling using the radiator zones. This feature has not been implemented due to the lack of sample devices. + +The system cannot be turned on/off through the `climate` entities. + +#### State attributes + +|Attribute|Description|Example| +|---------|-----------|-------| +|`status` |Current operation status|`idle`| + +### Sensor + +The following attributes are available for `sensor` platform entities: + +- Room temperature for each zone +- Tank water temperature +- Outside temperature - 1°C precision, polled every 1-2 hours. + +Unlike air-to-air devices, air-to-water devices do not report energy consumption in an easily accessible manner. + +### Water heater + +The following parameters can be controlled for the `water_heater` platform entities: + +- Power - Controls the entire system. +- Target tank temperature +- Operation mode + +#### State attributes + +|Attribute|Description|Example| +|---------|-----------|-------| +|`status` |Current operation status|`heat`| From eb4c1afadce792d98985c05355ecdd7d60418fa9 Mon Sep 17 00:00:00 2001 From: Bram Kragten Date: Wed, 11 Mar 2020 09:55:27 +0100 Subject: [PATCH 4/9] Fix Hue documentation (#12329) --- source/_integrations/hue.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/hue.markdown b/source/_integrations/hue.markdown index 453d7179f52..f0d49984b4c 100644 --- a/source/_integrations/hue.markdown +++ b/source/_integrations/hue.markdown @@ -1,4 +1,4 @@ --- +--- title: Philips Hue description: Instructions on setting up Philips Hue within Home Assistant. ha_category: From 8a701f9cd7d282c8c44ea70430b849b5a498d82c Mon Sep 17 00:00:00 2001 From: "J. Nick Koston" Date: Wed, 11 Mar 2020 06:03:08 -0500 Subject: [PATCH 5/9] Add Presence Detection example to august (#12314) * Add Presence Detection example to august * mixing quotes * Try another way * Try another way * Try another way * Try another way * Try another way * Try a another way to fix build * Revert "Try a another way to fix build" This reverts commit 95f9846b1d2a9f9fc7b1274cfa657af1a793b3c1. * raw it is * :pencil2: Tweak Co-authored-by: Franck Nijhof --- source/_integrations/august.markdown | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/source/_integrations/august.markdown b/source/_integrations/august.markdown index a55fd764994..e13fc70d6eb 100644 --- a/source/_integrations/august.markdown +++ b/source/_integrations/august.markdown @@ -93,7 +93,33 @@ If you have an August Doorbell with a battery, once you have enabled the August If you have an August Smart Lock, once you have enabled the August component, you should see the following sensors: - Lock Battery +- Lock Operation If you have an August Keypad, once you have enabled the August component, you should see the following sensors: - Keypad Battery + +### Presence Detection with Lock Operation + +Using the lock operation sensors, you can detect when a user operates a lock and is physically present (not remote). The below example will trigger when the user named “John Doe” in August locks or unlocks the door from the keypad (if present), via Bluetooth from their phone, or by auto-unlock. The state of the sensor will be the name of the party operating the lock as returned by August. + +{% raw %} + +```yaml +- id: '1583706446906' + alias: joe_doe_front_door_operate + description: John Doe locks or unlocks the Front Door + trigger: + - entity_id: sensor.front_door_operator + platform: state + to: John Doe + condition: + - condition: template + value_template: "{{ not state_attr('sensor.front_door_operator', 'remote') }}" + action: + - data: {} + entity_id: camera.inside + service: camera.turn_off +``` + +{% endraw %} From 50bbd86187c5263aece2a4269fd6834faf689cf2 Mon Sep 17 00:00:00 2001 From: Diogo Gomes Date: Wed, 11 Mar 2020 11:03:46 +0000 Subject: [PATCH 6/9] add calibrate service (#12326) --- source/_integrations/utility_meter.markdown | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/source/_integrations/utility_meter.markdown b/source/_integrations/utility_meter.markdown index d64b6a80774..f7a0633776f 100644 --- a/source/_integrations/utility_meter.markdown +++ b/source/_integrations/utility_meter.markdown @@ -80,6 +80,15 @@ Reset the Utility Meter. All sensors tracking tariffs will be reset to 0. | ---------------------- | -------- | ----------- | | `entity_id` | no | String or list of strings that point at `entity_id`s of utility_meters. +### Service `utility_meter.calibrate` + +Calibrate the Utility Meter. Change the value of a given sensor. + +| Service data attribute | Optional | Description | +| ---------------------- | -------- | ----------- | +| `entity_id` | no | String or list of strings that point at `entity_id`s of utility_meters. +| `value` | no | Number | Value to calibrate the sensor with | + ### Service `utility_meter.next_tariff` Change the current tariff to the next in the list. From e7fd176fabdfb087744cb0b145bc186f60b41921 Mon Sep 17 00:00:00 2001 From: guillempages Date: Wed, 11 Mar 2020 12:04:13 +0100 Subject: [PATCH 7/9] Add attribute parameter to label-state (#12151) Add an optional parameter "attribute" to the label-state element in picture elements --- source/_lovelace/picture-elements.markdown | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/source/_lovelace/picture-elements.markdown b/source/_lovelace/picture-elements.markdown index 6de03f07d2c..deeab796057 100644 --- a/source/_lovelace/picture-elements.markdown +++ b/source/_lovelace/picture-elements.markdown @@ -165,6 +165,11 @@ entity: required: true description: Entity id type: string +attribute: + required: false + description: If present, the corresponding attribute will be shown, + instead of the entity's state + type: string prefix: required: false description: Text before entity state. @@ -456,6 +461,13 @@ elements: style: top: 82% left: 79% + - type: state-label + entity: climate.kitchen + attribute: current_temperature + suffix: "°C" + style: + top: 33% + left: 15% - type: service-button title: Turn lights off style: From 1f672bcd10a5021165101638c683d76d5e4b1644 Mon Sep 17 00:00:00 2001 From: "J. Nick Koston" Date: Wed, 11 Mar 2020 06:04:39 -0500 Subject: [PATCH 8/9] Documentation for griddy integration (#12312) * Documentation for griddy integration * Remove icon * Empty commit to force ci --- source/_integrations/griddy.markdown | 64 ++++++++++++++++++++++++++++ 1 file changed, 64 insertions(+) create mode 100644 source/_integrations/griddy.markdown diff --git a/source/_integrations/griddy.markdown b/source/_integrations/griddy.markdown new file mode 100644 index 00000000000..c01a0967d37 --- /dev/null +++ b/source/_integrations/griddy.markdown @@ -0,0 +1,64 @@ +--- +title: Griddy +description: Instructions on how to integrate griddy prices into Home Assistant. +ha_category: + - Sensor +ha_release: 0.107 +ha_iot_class: Cloud Polling +ha_config_flow: true +ha_codeowners: + - '@bdraco' +ha_domain: griddy +--- + +The `griddy` integration allows you to integrate your [Griddy](https://griddy.com/) price data into Home Assistant. + +There is currently support for the following device types within Home Assistant: + +- Sensor + +## Configuration + +You will need your Griddy Load Zone to use this module. + +To add `Griddy` to your installation, go to **Configuration** >> **Integrations** in the UI, click the button with `+` sign and from the list of integrations select **Griddy**. + +Alternatively, add the following to your `configuration.yaml` file: + +```yaml +# Example configuration.yaml entry +griddy: + loadzone: YOUR_LZ +``` + +{% configuration %} +loadzone: + description: Your Load Zone is in your Griddy account under “Account > Meter > Load Zone.” + required: true + type: string +{% endconfiguration %} + +### Sensor + +The current price for the Load Zone will appear as a sensor: + +- LZ_XXXXX Price Now + +### Example Automation + +```yaml +- id: '1572630019168' + alias: Stop Tesla Charging if Power Price Spikes + description: '' + trigger: + - above: '30' + entity_id: sensor.lz_houston_price_now + platform: numeric_state + condition: + - condition: zone + entity_id: device_tracker.my_tesla + zone: zone.home + action: + - service: switch.turn_off + entity_id: switch.my_tesla_charger_switch +``` From 625ae012248c4995cee1714b2133423d9f16cac9 Mon Sep 17 00:00:00 2001 From: Bram Kragten Date: Wed, 11 Mar 2020 14:43:20 +0100 Subject: [PATCH 9/9] Add docs for multiple dashboard and resources in yaml mode (#12332) * Add docs for multiple dashboard and resources in yaml mode * Update yaml-mode.markdown * Update yaml-mode.markdown * Update yaml-mode.markdown * Update yaml-mode.markdown * Update yaml-mode.markdown * Update yaml-mode.markdown --- source/lovelace/yaml-mode.markdown | 104 ++++++++++++++++++++++++++--- 1 file changed, 95 insertions(+), 9 deletions(-) diff --git a/source/lovelace/yaml-mode.markdown b/source/lovelace/yaml-mode.markdown index 6b772bf1e40..91a757c7f36 100644 --- a/source/lovelace/yaml-mode.markdown +++ b/source/lovelace/yaml-mode.markdown @@ -23,8 +23,101 @@ When you make changes to `ui-lovelace.yaml`, you don't have to restart Home Assi To revert back to using the UI to edit your Lovelace interface, remove the `lovelace` section from your `configuration.yaml` and copy the contents of your `ui-lovelace.yaml` into the raw configuration section of Home Assistant and restart. +### Advanced configuration -As a super minimal example, here's the bare minimum you will need for this to work: +You can define multiple dashboards that all have their own YAML file, and add custom resources that are shared by all dashboards. + +```yaml +lovelace: + mode: yaml + # Include external resources only add when mode is yaml, otherwise manage in the resources in the lovelace configuration panel. + resources: + - url: /local/my-custom-card.js + type: module + - url: /local/my-webfont.css + type: css + # Add more dashboards + dashboards: + generated: + mode: yaml + filename: notexist.yaml + title: Generated + icon: mdi:tools + show_in_sidebar: true + require_admin: true + hidden: + mode: yaml + title: hidden + show_in_sidebar: false + filename: hidden.yaml +``` + +You can also add YAML dashboards when your main dashboard is UI configurated: +```yaml +lovelace: + mode: storage + # Add yaml dashboards + dashboards: + yaml: + mode: yaml + title: YAML + icon: mdi:script + show_in_sidebar: true + filename: lovelace.yaml +``` + +{% configuration Lovelace %} +mode: + required: true + description: "In what mode should the main Lovelace panel be, `yaml` or `storage` (UI managed)." + type: string +resources: + required: false + description: "List of resources that should be loaded when you use Lovelace. Only use this when mode is `yaml`." + type: list + keys: + url: + required: true + description: The URL of the resource to load. + type: string + type: + required: true + description: "The type of resource, this should be either `module` for a JavaScript module or `css` for a StyleSheet." + type: string +dashboards: + required: false + description: Additional Lovelace YAML dashboards. + type: map + keys: + mode: + required: true + description: "The mode of the dashboard, this should always be `yaml`. Dashboards in `storage` mode can be created in the Lovelace configuration panel." + type: string + filename: + required: true + description: "The file in your `config` directory where the Lovelace configuration for this panel is." + type: string + title: + required: true + description: "The title of the dashboard, will be used in the sidebar." + type: string + icon: + required: false + description: The icon to show in the sidebar. + type: string + show_in_sidebar: + required: false + description: Should this view be shown in the sidebar. + type: boolean + default: true + require_admin: + required: false + description: Should this view be only accessible for admin users. + type: boolean + default: false +{% endconfiguration %} + +As a super minimal example of a Lovelace dashboard config, here's the bare minimum you will need for it to work: ```yaml title: My Awesome Home @@ -39,17 +132,10 @@ views: Welcome to your **Lovelace UI**. ``` -A slightly more advanced example shows additional elements which can be used to customize your frontend. +A slightly more advanced example: ```yaml title: My Awesome Home -# Include external resources -resources: - - url: /local/my-custom-card.js - type: js - - url: /local/my-webfont.css - type: css - views: # View tab title. - title: Example