forked from home-assistant/home-assistant.io
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Frontend release notes for 0.106 (home-assistant#12122)
* Add frontend release notes 0.106 * Update 2020-02-26-release-106.markdown * Update
- Loading branch information
1 parent
9b8dbc3
commit 019d684
Showing
4 changed files
with
145 additions
and
81 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -15,6 +15,56 @@ og_image: /images/blog/2020-02-0.105/components.png | |
| - Icons for scene/script. | ||
| - brightness_step and brightness_step_pct added to light.turn_on. Also part of device actions. | ||
|
|
||
| ## All entities in entities config panel | ||
|
|
||
| The entities config panel previously only contained entities which had unique ID's because these were the entities that could have their names and id's edited within the UI. In this version we now include all entities in the config panel. You are still only able to change those that have a unique ID, but now you have a clear overview of all the available entities and can also make use of the "related items" feature introduced in release 0.105.0 to see where they are being used! | ||
|
|
||
| You can recognize the entities that can not be edited by the striked through pencil icon. | ||
|
|
||
| <p class='img'> | ||
| <img src='/images/blog/2020-02-0.106/entities.png' alt='Screenshot of uneditable entities in the config panel'></a> | ||
| Screenshot of uneditable entities in the config panel. | ||
| </p> | ||
|
|
||
| ## Change the home zone location in the zone editor | ||
|
|
||
| In the zone editor that was introduced in the previous release, you could not change the location of your home zone. In this version you can! | ||
| You still can not change the radius from the UI (we will work on that!), but you can drag the home zone on the map. | ||
|
|
||
| ## State color option | ||
|
|
||
| Also an improvement on a feature introduced in the previous release, the `state_color` option is now also available for other cards, so you can override the defaults of the cards. | ||
|
|
||
| ## Sensor card | ||
|
|
||
| Our sensor card has had a style update. We initially got the design from [mini graph card](https://github.com/kalkih/mini-graph-card) and now updated to match the improved new look of that card. | ||
|
|
||
| <p class='img'> | ||
| <img src='/images/blog/2020-02-0.106/sensor-card.png' alt='Screenshot of the updated sensor card'></a> | ||
| Screenshot of the updated sensor card. | ||
| </p> | ||
|
|
||
| ## Person more info | ||
|
|
||
| Persons have a new more info dialog. They now show the location of the person on the map and if the person is not in a zone, you can create a zone with the current location of that person with one click. | ||
|
|
||
| <p class='img'> | ||
| <img src='/images/blog/2020-02-0.106/more-info-person.png' alt='Screenshot of the new more info for a person'></a> | ||
| Screenshot of the new more info for a person. | ||
| </p> | ||
|
|
||
| ## Automations default to device | ||
|
|
||
| New automations now default to device automations instead if state triggers en service calls. Device automations are so much easier and clearer to create from the UI. You can ofcourse still use the old triggers and actions like you are used to. | ||
|
|
||
| ## Automations and battery no longer on generated UI | ||
|
|
||
| In generate Lovelace we no longer include automations and battery entities. You can find these in the automation config panel and the battery in the device config page. | ||
| If you want to have your automations and/or battery in your Lovelace UI, you can always take control and add them. | ||
|
|
||
| ## Custom cards | ||
|
|
||
| For custom card developers some thing have chnaged as well, read the [blog post](https://developers.home-assistant.io/blog/2020/02/18/106-custom-card-changes.html) on the developers site about this. | ||
|
|
||
| ## New Integrations | ||
|
|
||
|
|
@@ -44,20 +94,23 @@ Experiencing issues introduced by this release? Please report them in our [issue | |
|
|
||
| ## Breaking Changes | ||
|
|
||
| - __Tesla__ - Tesla default SCAN_INTERVAL has been raised to 660 seconds from 300 seconds. This is the result of new testing showing the prior default would not allow Tesla vehicles to fall asleep. You should reevaluate your SCAN_INTERVAL if you have changed it to avoid battery drain. The SCAN_INTERVAL has had the minimum lowered to 60. - ([@alandtse] - [#31194]) ([tesla docs]) | ||
| - **Tesla** - Tesla default SCAN_INTERVAL has been raised to 660 seconds from 300 seconds. This is the result of new testing showing the prior default would not allow Tesla vehicles to fall asleep. You should reevaluate your SCAN_INTERVAL if you have changed it to avoid battery drain. The SCAN_INTERVAL has had the minimum lowered to 60. - ([@alandtse] - [#31194]) ([tesla docs]) | ||
|
|
||
| - __Insteon__ - The Insteon entity device state attributes were changed to conform to naming standards. Insteon Address is now `insteon_address` and Insteon Group is now `insteon_group`. You may need to update automations and scripts that rely on these attributes. - ([@teharris1] - [#31183]) ([insteon docs]) | ||
| - **Insteon** - The Insteon entity device state attributes were changed to conform to naming standards. Insteon Address is now `insteon_address` and Insteon Group is now `insteon_group`. You may need to update automations and scripts that rely on these attributes. - ([@teharris1] - [#31183]) ([insteon docs]) | ||
|
|
||
| - __AVM FRITZ!DECT__ *(Removed)* - Fritzdect is being removed and you should use the Fritzbox integration instead which offers more features. - ([@escoand] - [#31359]) ([fritzbox docs]) | ||
| - **AVM FRITZ!DECT** _(Removed)_ - Fritzdect is being removed and you should use the Fritzbox integration instead which offers more features. - ([@escoand] - [#31359]) ([fritzbox docs]) | ||
|
|
||
| Example Configuration yaml: | ||
|
|
||
| ```yaml | ||
| switch: | ||
| - platform: fritzdect | ||
| username: YOUR_USERNAME | ||
| password: YOUR_PASSWORD | ||
| - platform: fritzdect | ||
| username: YOUR_USERNAME | ||
| password: YOUR_PASSWORD | ||
| ``` | ||
| should change to | ||
| ```yaml | ||
| fritzbox: | ||
| devices: | ||
|
|
@@ -66,29 +119,32 @@ Experiencing issues introduced by this release? Please report them in our [issue | |
| password: YOUR_PASSWORD | ||
| ``` | ||
| - __Danfoss Air__ - The names of some danfoss_air sensors include a misspelling of the word danfoss. This typo has been corrected and you will need to adjust all occurrences respectively. - ([@KasperLK] - [#31344]) ([danfoss_air docs]) | ||
| - **Danfoss Air** - The names of some danfoss_air sensors include a misspelling of the word danfoss. This typo has been corrected and you will need to adjust all occurrences respectively. - ([@KasperLK] - [#31344]) ([danfoss_air docs]) | ||
| The following sensors are affected: | ||
| * `dandoss_air_dial_battery` -> `danfoss_air_dial_battery` | ||
| * `dandoss_air_exhaust_fan_speed` -> `danfoss_air_exhaust_fan_speed` | ||
| * `dandoss_air_supply_fan_speed` -> `danfoss_air_supply_fan_speed` | ||
| - __Météo-France__ - Météo-France supports config flow and is now available to be added as an integration from the integrations UI! There are no more `monitored_conditions` and all sensors will be added. - ([@Quentame] - [#29927]) ([meteo_france docs]) | ||
| - `dandoss_air_dial_battery` -> `danfoss_air_dial_battery` | ||
| - `dandoss_air_exhaust_fan_speed` -> `danfoss_air_exhaust_fan_speed` | ||
| - `dandoss_air_supply_fan_speed` -> `danfoss_air_supply_fan_speed` | ||
|
|
||
| - __Service Calls__ - Service calls that reference non-existing entities will now log a warning instead of silently being omitted. If you are using a template and want to select no entities, you need to pass `none` instead. The TTS integration will no longer target all media players if no entity ID passed in. You need to specify `all` instead. - ([@balloob] - [#31427]) | ||
| - **Météo-France** - Météo-France supports config flow and is now available to be added as an integration from the integrations UI! There are no more `monitored_conditions` and all sensors will be added. - ([@Quentame] - [#29927]) ([meteo_france docs]) | ||
|
|
||
| - __Light__ - It is no longer allowed to pass both `brightness` and `brightness_pct` to `light.turn_on` service. Previously passing both would have used `brightness_pct`. - ([@balloob] - [#31452]) ([light docs]) | ||
| - **Service Calls** - Service calls that reference non-existing entities will now log a warning instead of silently being omitted. If you are using a template and want to select no entities, you need to pass `none` instead. The TTS integration will no longer target all media players if no entity ID passed in. You need to specify `all` instead. - ([@balloob] - [#31427]) | ||
|
|
||
| - __DSMR__ - Added Belgian meter. Some DSMR sensors have been renamed to align with DSMR specifications. "Power" sensors are now properly "Energy" sensors and those which were previously using "low" and "normal" descriptions now use "tarif 1" and "tarif 2", respectively. - ([@dupondje] - [#30121]) ([dsmr docs]) | ||
| - **Light** - It is no longer allowed to pass both `brightness` and `brightness_pct` to `light.turn_on` service. Previously passing both would have used `brightness_pct`. - ([@balloob] - [#31452]) ([light docs]) | ||
|
|
||
| - **DSMR** - Added Belgian meter. Some DSMR sensors have been renamed to align with DSMR specifications. "Power" sensors are now properly "Energy" sensors and those which were previously using "low" and "normal" descriptions now use "tarif 1" and "tarif 2", respectively. - ([@dupondje] - [#30121]) ([dsmr docs]) | ||
|
|
||
| Example of sensor changes: | ||
| * `Power Consumption (low)` -> `Energy Consumption (tarif 1)` | ||
| * `Power Consumption (normal)` -> `Energy Consumption (tarif 2)` | ||
|
|
||
| - __Group__ - Only administrator users can stop or restart Home Assistant. - ([@balloob] - [#31509]) ([group docs]) ([homeassistant docs]) ([intent docs]) | ||
| - __Sure Petcare__ - Sure Petcare supports new features and has improved existing features. As a result, you will want to note that `household_id` has been removed from configuration options as it is now longer needed. - ([@benleb] - [#31437]) ([surepetcare docs]) | ||
| - `Power Consumption (low)` -> `Energy Consumption (tarif 1)` | ||
| - `Power Consumption (normal)` -> `Energy Consumption (tarif 2)` | ||
|
|
||
| - **Group** - Only administrator users can stop or restart Home Assistant. - ([@balloob] - [#31509]) ([group docs]) ([homeassistant docs]) ([intent docs]) | ||
| - **Sure Petcare** - Sure Petcare supports new features and has improved existing features. As a result, you will want to note that `household_id` has been removed from configuration options as it is now longer needed. - ([@benleb] - [#31437]) ([surepetcare docs]) | ||
|
|
||
| Example configuration yaml: | ||
|
|
||
| ```yaml | ||
| surepetcare: | ||
| username: YOUR_SURE_PETCARE_LOGIN | ||
|
|
@@ -98,70 +154,78 @@ Experiencing issues introduced by this release? Please report them in our [issue | |
| pets: [24680] | ||
| ``` | ||
|
|
||
| - __Frontend__ - `frontend.set_theme` and `frontend.reload_themes` now require admin access. This will not break automations that set themes because those are run with admin access. Also, a `themes_updated event` no longer contains all theme data - ([@balloob] - [#31654]) ([frontend docs]) | ||
| - __Modbus__ - The Modbus Binary Sensor can now read data from discrete inputs. A new variable __input_type__ type was added to define if you want to read from coil or discrete_input. Coil is the default option. - ([@vzahradnik] - [#30004]) ([modbus docs]) | ||
| - **Frontend** - `frontend.set_theme` and `frontend.reload_themes` now require admin access. This will not break automations that set themes because those are run with admin access. Also, a `themes_updated event` no longer contains all theme data - ([@balloob] - [#31654]) ([frontend docs]) | ||
|
|
||
| - **Modbus** - The Modbus Binary Sensor can now read data from discrete inputs. A new variable **input_type** type was added to define if you want to read from coil or discrete_input. Coil is the default option. - ([@vzahradnik] - [#30004]) ([modbus docs]) | ||
|
|
||
| Example configuration yaml: | ||
|
|
||
| ```yaml | ||
| binary_sensor: | ||
| - platform: modbus | ||
| scan_interval: 10 | ||
| inputs: | ||
| - name: Sensor1 | ||
| hub: hub1 | ||
| slave: 1 | ||
| address: 100 | ||
| input_type: discrete_input | ||
| - platform: modbus | ||
| scan_interval: 10 | ||
| inputs: | ||
| - name: Sensor1 | ||
| hub: hub1 | ||
| slave: 1 | ||
| address: 100 | ||
| input_type: discrete_input | ||
| ``` | ||
| - __Tado__ - Adding support of multiple Tado accounts has changed the unique id generation of sensor and climate, and now includes the id of the home. In addition, support for water heater zones has been added. Tado hot water zones with temperature control previously created an climate entity, e.g. `climate.hot_water`, and these will be replaced by a `water_heater.hot_water` entity. This change is not breaking for hot water zones without temperature control as they do not have a climate zone. - ([@gorynychzmey] - [#31527]) ([@michaelarnauts] - [#30095]) ([tado docs]) | ||
|
|
||
| - **Tado** - Adding support of multiple Tado accounts has changed the unique id generation of sensor and climate, and now includes the id of the home. In addition, support for water heater zones has been added. Tado hot water zones with temperature control previously created an climate entity, e.g. `climate.hot_water`, and these will be replaced by a `water_heater.hot_water` entity. This change is not breaking for hot water zones without temperature control as they do not have a climate zone. - ([@gorynychzmey] - [#31527]) ([@michaelarnauts] - [#30095]) ([tado docs]) | ||
|
|
||
| Example configuration yaml: | ||
|
|
||
| ```yaml | ||
| tado: | ||
| - username: [email protected] | ||
| password: !secret tado_pwd1 | ||
| - username: [email protected] | ||
| password: !secret tado_pwd2 | ||
| ``` | ||
|
|
||
| If you have only one account this configuration will also work: | ||
|
|
||
| ```yaml | ||
| tado: | ||
| username: [email protected] | ||
| password: !secret tado_pwd | ||
| username: [email protected] | ||
| password: !secret tado_pwd | ||
| ``` | ||
| - __UniFi__ - Changing tracking settings will no longer disable entities but will remove them completely from the state machine and entity registry. The SSID filter will now mark all wireless clients as `not_home` if they are connected to SSIDs that are not a part of the filter. - ([@Kane610] - [#31762]) ([unifi docs]) | ||
| - __Rest__ - Many devices continue to use XML for RESTful APIs. This change implements converting XML output to JSON via xmltojson so it can work with the existing rest sensor component. As the attributes that usually need to be scraped are deeper in the document, support for passing in a template to find the JSON attributes has been added. JSON APIs that do not have their attributes at the top level can also benefit from this change. - ([@bdraco] - [#31809]) ([rest docs]) | ||
|
|
||
|
|
||
| - **UniFi** - Changing tracking settings will no longer disable entities but will remove them completely from the state machine and entity registry. The SSID filter will now mark all wireless clients as `not_home` if they are connected to SSIDs that are not a part of the filter. - ([@Kane610] - [#31762]) ([unifi docs]) | ||
| - **Rest** - Many devices continue to use XML for RESTful APIs. This change implements converting XML output to JSON via xmltojson so it can work with the existing rest sensor component. As the attributes that usually need to be scraped are deeper in the document, support for passing in a template to find the JSON attributes has been added. JSON APIs that do not have their attributes at the top level can also benefit from this change. - ([@bdraco] - [#31809]) ([rest docs]) | ||
|
|
||
| Example configuration yaml: | ||
|
|
||
| ```yaml | ||
| sensor: | ||
| - platform: rest | ||
| resource: http://192.168.1.20/status.xml | ||
| authentication: basic | ||
| username: username | ||
| password: password | ||
| json_attributes: | ||
| - "htstatus" | ||
| - "poolsp" | ||
| - "spasp" | ||
| - "pooltemp" | ||
| - "spatemp" | ||
| - "airtemp" | ||
| json_attributes_path: "$.response.temp" | ||
| value_template: '{{ value_json.response.temp.poolsp }}' | ||
| - platform: rest | ||
| resource: http://192.168.1.5/status.xml | ||
| json_attributes: | ||
| - "led0" | ||
| - "led1" | ||
| - "user0" | ||
| - "temp0" | ||
| - "btn0" | ||
| json_attributes_path: "$.response" | ||
| value_template: "OK" | ||
| - platform: rest | ||
| resource: http://192.168.1.20/status.xml | ||
| authentication: basic | ||
| username: username | ||
| password: password | ||
| json_attributes: | ||
| - "htstatus" | ||
| - "poolsp" | ||
| - "spasp" | ||
| - "pooltemp" | ||
| - "spatemp" | ||
| - "airtemp" | ||
| json_attributes_path: "$.response.temp" | ||
| value_template: "{{ value_json.response.temp.poolsp }}" | ||
| - platform: rest | ||
| resource: http://192.168.1.5/status.xml | ||
| json_attributes: | ||
| - "led0" | ||
| - "led1" | ||
| - "user0" | ||
| - "temp0" | ||
| - "btn0" | ||
| json_attributes_path: "$.response" | ||
| value_template: "OK" | ||
| ``` | ||
| - __GreenEye Monitor (GEM)__ - Greeneye Monitor temperature readings are now correct (previously they would report as twice the actual value). If you've compensated for this in your dashboards or displays, you'll need to undo that compensation with this release. - ([@jkeljo] - [#31896]) ([greeneye_monitor docs]) | ||
|
|
||
| - **GreenEye Monitor (GEM)** - Greeneye Monitor temperature readings are now correct (previously they would report as twice the actual value). If you've compensated for this in your dashboards or displays, you'll need to undo that compensation with this release. - ([@jkeljo] - [#31896]) ([greeneye_monitor docs]) | ||
|
|
||
| ## Beta Fixes | ||
|
|
||
|
|
@@ -582,27 +646,27 @@ Experiencing issues introduced by this release? Please report them in our [issue | |
| [#31920]: https://github.com/home-assistant/home-assistant/pull/31920 | ||
| [#31921]: https://github.com/home-assistant/home-assistant/pull/31921 | ||
| [#31922]: https://github.com/home-assistant/home-assistant/pull/31922 | ||
| [@Adminiuga]: https://github.com/Adminiuga | ||
| [@BKPepe]: https://github.com/BKPepe | ||
| [@CHAZICLE]: https://github.com/CHAZICLE | ||
| [@Cereal2nd]: https://github.com/Cereal2nd | ||
| [@Cloudenius]: https://github.com/Cloudenius | ||
| [@Danielhiversen]: https://github.com/Danielhiversen | ||
| [@Kane610]: https://github.com/Kane610 | ||
| [@KasperLK]: https://github.com/KasperLK | ||
| [@Konsts]: https://github.com/Konsts | ||
| [@ManneW]: https://github.com/ManneW | ||
| [@Marco98]: https://github.com/Marco98 | ||
| [@MartinHjelmare]: https://github.com/MartinHjelmare | ||
| [@MrDadoo]: https://github.com/MrDadoo | ||
| [@P-Verbrugge]: https://github.com/P-Verbrugge | ||
| [@PhilRW]: https://github.com/PhilRW | ||
| [@Quentame]: https://github.com/Quentame | ||
| [@SoftXperience]: https://github.com/SoftXperience | ||
| [@Squixx]: https://github.com/Squixx | ||
| [@SukramJ]: https://github.com/SukramJ | ||
| [@TechnicallyJoe]: https://github.com/TechnicallyJoe | ||
| [@YarmoM]: https://github.com/YarmoM | ||
| [@adminiuga]: https://github.com/Adminiuga | ||
| [@bkpepe]: https://github.com/BKPepe | ||
| [@chazicle]: https://github.com/CHAZICLE | ||
| [@cereal2nd]: https://github.com/Cereal2nd | ||
| [@cloudenius]: https://github.com/Cloudenius | ||
| [@danielhiversen]: https://github.com/Danielhiversen | ||
| [@kane610]: https://github.com/Kane610 | ||
| [@kasperlk]: https://github.com/KasperLK | ||
| [@konsts]: https://github.com/Konsts | ||
| [@mannew]: https://github.com/ManneW | ||
| [@marco98]: https://github.com/Marco98 | ||
| [@martinhjelmare]: https://github.com/MartinHjelmare | ||
| [@mrdadoo]: https://github.com/MrDadoo | ||
| [@p-verbrugge]: https://github.com/P-Verbrugge | ||
| [@philrw]: https://github.com/PhilRW | ||
| [@quentame]: https://github.com/Quentame | ||
| [@softxperience]: https://github.com/SoftXperience | ||
| [@squixx]: https://github.com/Squixx | ||
| [@sukramj]: https://github.com/SukramJ | ||
| [@technicallyjoe]: https://github.com/TechnicallyJoe | ||
| [@yarmom]: https://github.com/YarmoM | ||
| [@abmantis]: https://github.com/abmantis | ||
| [@alandtse]: https://github.com/alandtse | ||
| [@andersonshatch]: https://github.com/andersonshatch | ||
|
|
||
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.