From 0120a99456dcadaee281a946254674872c48593f Mon Sep 17 00:00:00 2001 From: PuckStar Date: Fri, 16 Jun 2017 07:32:31 +0200 Subject: [PATCH 01/11] Create notify.group.markdown (#2822) --- source/_components/notify.group.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/notify.group.markdown b/source/_components/notify.group.markdown index f46936ac059..e68b76112e5 100644 --- a/source/_components/notify.group.markdown +++ b/source/_components/notify.group.markdown @@ -32,5 +32,5 @@ Configuration variables: - **name** (*Required*): Setting the parameter `name` sets the name of the group. - **services** (*Required*): A list of all the services to be included in the group. - - **service** (*Required*): The service part of an entity ID, i.e. if you use `notify.html5` normally, just put `html5`. + - **service** (*Required*): The service part of an entity ID, i.e. if you use `notify.html5` normally, just put `html5`. Note that you must put everything in lower case here. Although you might have capitals written in the actual notification services! - **data** (*Optional*): A dictionary containing parameters to add to all notify payloads. This can be anything that is valid to use in a payload, such as `data`, `message`, `target`, `title`. From 1c904e63b1b32699d67f4f2c6778a1d4a6fcaaa8 Mon Sep 17 00:00:00 2001 From: Anders Melchiorsen Date: Fri, 16 Jun 2017 07:34:15 +0200 Subject: [PATCH 02/11] Update light.turn_on to match current schema (#2756) --- source/_components/light.markdown | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/source/_components/light.markdown b/source/_components/light.markdown index 688cb0732f8..43706748906 100644 --- a/source/_components/light.markdown +++ b/source/_components/light.markdown @@ -24,11 +24,12 @@ Most lights do not support all attributes. You can check the platform documentat | Service data attribute | Optional | Description | | ---------------------- | -------- | ----------- | | `entity_id` | no | String or list of strings that point at `entity_id`s of lights. Else targets all. -| `transition` | yes | Integer that represents the time the light should take to transition to the new state in seconds. -| `profile` | yes | String with the name of one of the [built-in profiles](https://github.com/home-assistant/home-assistant/blob/master/homeassistant/components/light/light_profiles.csv) (relax, energize, concentrate, reading) or one of the custom profiles defined in `light_profiles.csv` in the current working directory. Light profiles define a xy color and a brightness. If a profile is given and a brightness or xy color then the profile values will be overwritten. +| `transition` | yes | Number that represents the time (in seconds) the light should take to transition to the new state. +| `profile` | yes | String with the name of one of the [built-in profiles](https://github.com/home-assistant/home-assistant/blob/master/homeassistant/components/light/light_profiles.csv) (relax, energize, concentrate, reading) or one of the custom profiles defined in `light_profiles.csv` in the current working directory. Light profiles define a xy color and a brightness. If a profile is given and a brightness then the profile brightness will be overwritten. | `xy_color` | yes | A list containing two floats representing the xy color you want the light to be. Two comma separated floats that represent the color in XY. | `rgb_color` | yes | A list containing three integers representing the rgb color you want the light to be. Three comma separated integers that represent the color in RGB. You can find a great chart here: [Hue Color Chart](http://www.developers.meethue.com/documentation/hue-xy-values) -| `color_temp` | yes | An INT in mireds representing the color temperature you want the light to be. +| `white_value` | yes | Integer between 0 and 255 for how bright a dedicated white LED should be. +| `color_temp` | yes | An integer in mireds representing the color temperature you want the light to be. | `kelvin` | yes | Alternatively, you can specify the color temperature in Kelvin. | `color_name` | yes | A human readable string of a color name, such as `blue` or `goldenrod`. All [CSS3 color names](https://www.w3.org/TR/2010/PR-css3-color-20101028/#svg-color) are supported. | `brightness` | yes | Integer between 0 and 255 for how bright the color should be. From ea3a1d428e4371012edf9e961204be086f80ed21 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Thu, 15 Jun 2017 22:55:24 -0700 Subject: [PATCH 03/11] Version bump to 0.47 --- _config.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/_config.yml b/_config.yml index c6dbb537997..d0cf0b4ca15 100644 --- a/_config.yml +++ b/_config.yml @@ -140,13 +140,13 @@ social: # Home Assistant release details current_major_version: 0 -current_minor_version: 46 -current_patch_version: 1 -date_released: 2017-06-09 +current_minor_version: 47 +current_patch_version: 0 +date_released: 2017-06-17 # Either # or the anchor link to latest release notes in the blog post. # Must be prefixed with a # and have double quotes around it. # Major release: -patch_version_notes: "#release-0461---june-9" +patch_version_notes: "#" # Minor release (Example #release-0431---april-25): From 52f2dda8645716e9cb80e30b92ee0d9976bcbc75 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Thu, 15 Jun 2017 23:17:28 -0700 Subject: [PATCH 04/11] Update updater docs --- source/_docs/backend/updater.markdown | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/source/_docs/backend/updater.markdown b/source/_docs/backend/updater.markdown index dcdb3cb5433..8551fff955e 100644 --- a/source/_docs/backend/updater.markdown +++ b/source/_docs/backend/updater.markdown @@ -12,6 +12,13 @@ redirect_from: /details/updater/ Starting with 0.31 the [updater component](/components/updater/) sends an optional report about Home Assistant instance. +If you want to opt-in to include component information, add `include_used_components` to your config. This will allow the Home Assistant developers to focus development efforts on the most popular components. + +```yaml +updater: + include_used_components: true +``` + We are only collecting this information to better understand our user base to provide better long term support and feature development. | Name | Description | Example | Data Source | @@ -49,4 +56,4 @@ The server also adds two timestamps to the data: - the original date your instance UUID was first seen - the timestamp of the last time we have seen your instance -There are currently no plans to publicly expose any of this information. If we did do such a thing in the future we would of course notify you in advance. It must also be stated that we will never sell or allow the use of this information for non-Home Assistant purposes. +We will never publicly expose individual gathered data. We might however publish aggregated stats about our user base (example: 70% of all users use Linux). We will never sell or allow the use of this information for non-Home Assistant development purposes. From 1c3d34e8ba59605fede0a47dec0783f57b9fec76 Mon Sep 17 00:00:00 2001 From: cribbstechnologies Date: Fri, 16 Jun 2017 12:13:57 -0400 Subject: [PATCH 05/11] updating docs to be inline with deployed code (#2826) --- source/_components/cover.mqtt.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/cover.mqtt.markdown b/source/_components/cover.mqtt.markdown index 665308a995d..d8d3180d874 100755 --- a/source/_components/cover.mqtt.markdown +++ b/source/_components/cover.mqtt.markdown @@ -37,7 +37,7 @@ Configuration variables: - **name** (*Optional*): The name of the sensor. Default is `MQTT Cover`. - **state_topic** (*Optional*): The MQTT topic subscribed to receive sensor values. -- **command_topic** (*Required*): The MQTT topic to publish commands to control the rollershutter. +- **command_topic** (*Optional*): The MQTT topic to publish commands to control the rollershutter. - **payload_open** (*Optional*): The payload that opens the cover. Default is `OPEN`. - **payload_close** (*Optional*): The payload that closes the cover. Default is `CLOSE`. - **payload_stop** (*Optional*): The payload that stops the rollershutter. default is `STOP`. From 69cc05d74026abb87b0835e25126cf13b7de9cb1 Mon Sep 17 00:00:00 2001 From: Adam Mills Date: Fri, 16 Jun 2017 13:29:35 -0400 Subject: [PATCH 06/11] Blog post for new zwave entity ids (#2816) --- .../2017-06-15-zwave-entity-ids.markdown | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 source/_posts/2017-06-15-zwave-entity-ids.markdown diff --git a/source/_posts/2017-06-15-zwave-entity-ids.markdown b/source/_posts/2017-06-15-zwave-entity-ids.markdown new file mode 100644 index 00000000000..48bb3a80df1 --- /dev/null +++ b/source/_posts/2017-06-15-zwave-entity-ids.markdown @@ -0,0 +1,22 @@ +--- +layout: post +title: "ZWave Entity IDs" +description: "Information on the past and future of ZWave Entity IDs." +date: 2017-06-15 08:00:00 -0400 +date_formatted: "June 15, 2017" +author: Adam Mills +comments: true +categories: Technology +--- + +ZWave entity_ids have long been a source of frustration in Home Assistant. The first problem we faced was that depending on the order of node discovery, entity_ids could be discovered with different names on each run. To solve this we added the node id as a suffix to the entity_id. This ensured that entity_ids were generated deterministically on each run, but additional suffixes had to be added to handle edge cases where there would otherwise be a conflict. The resulting entity_ids worked, but have been difficult to work with and makes ZWave a strange exception among other Home Assistant components. + +Thanks to the awesome work of [@turbokongen], a growing number of ZWave configuration options are now available from the new ZWave panel in the Home Assistant frontend. Among these new features is support for renaming of ZWave nodes and their underlying values. (These renames are persisted in zwcfg_*.xml) This is important, because these items are combined to form the Home Assistant entity name, which is used to generate the entity_id. Now that these options are available, ZWave users can rename nodes and values, influencing the entity_ids that are generated by Home Assistant. + +Now that users are able to control these names, we will be making changes to how the entity_ids are generated for ZWave entities. The ZWave entity_ids are going to switch back to using the standard entity_id generation from Home Assistant core, based on the entity names. Moving forward, if there is a conflict when generating entity_ids, a suffix will be added, and it will be the responsibility of the user to rename their nodes and values to avoid the conflict. This is the same as any other platform in Home Assistant where two devices are discovered with the same name. + +With the release of 0.47, this feature will be opt-in. Setting `new_entity_ids: true` under `zwave:` in your configuration.yaml will enable the new generation. After 0.48 this feature will become opt-out. From 0.48 onward, unless you’ve declared `new_entity_ids: false` you will switch to the new entity_id generation. At an undecided point in the future, the old entity_id generation will be removed completely. + +I’m sure all ZWave users understand that the current entity_ids aren’t easy to use. They’re annoying to type in configuration.yaml, and break if a node needs to be re-included to the network. We know that breaking changes are painful, and so we’re doing what we can to roll this change out as smoothly as possible. The end result should be a dramatic simplification of most ZWave configurations. We hope that this change will ultimately make ZWave much easier to work with, and bring ZWave configuration just a little closer to the rest of the Home Assistant platforms. + +[@turbokongen]: https://github.com/turbokongen From 05c9e5f7049c0b9d6d931616711e34d1dc1596e1 Mon Sep 17 00:00:00 2001 From: vrs01 Date: Fri, 16 Jun 2017 20:35:24 +0200 Subject: [PATCH 07/11] Update binary_sensor.template.markdown (#2825) --- source/_components/binary_sensor.template.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/binary_sensor.template.markdown b/source/_components/binary_sensor.template.markdown index 39ea85e7d22..ba69ae5c77f 100644 --- a/source/_components/binary_sensor.template.markdown +++ b/source/_components/binary_sensor.template.markdown @@ -47,7 +47,7 @@ sensor: sensors: furnace_on: value_template: {% raw %}{{ states.sensor.furnace.state > 2.5 }}{% endraw %} - friendly_name: 'Furnace Running + friendly_name: 'Furnace Running' device_class: heat ``` From f84dc25792cc1de0dfe31883a42c14743dbadfda Mon Sep 17 00:00:00 2001 From: Hamid Date: Fri, 16 Jun 2017 22:47:24 +0100 Subject: [PATCH 08/11] Add network_key configuration (#2828) * Add network_key configuration Network key can be set here rather than in the (difficult to find) configuration `options.xml`. It takes the same comma separated "0xNN" string syntax as previous. * Cleanup unneeded section Removed the options.xml information that is on longer required as per comments from @dale3h --- source/_docs/z-wave.markdown | 15 ++------------- 1 file changed, 2 insertions(+), 13 deletions(-) diff --git a/source/_docs/z-wave.markdown b/source/_docs/z-wave.markdown index cd2e9fdd74b..5b38ea21e68 100644 --- a/source/_docs/z-wave.markdown +++ b/source/_docs/z-wave.markdown @@ -35,6 +35,7 @@ zwave: Configuration variables: - **usb_path** (*Optional*): The port where your device is connected to your Home Assistant host. +- **network_key** (*Optional*): The 16 byte network key in the form `"0x01,0x02..."` used in order to connect securely to compatible devices. - **config_path** (*Optional*): The path to the Python OpenZWave configuration files. Defaults to the 'config' that is installed by python-openzwave - **autoheal** (*Optional*): Allows disabling auto Z-Wave heal at midnight. Defaults to True. - **polling_interval** (*Optional*): The time period in milliseconds between polls of a nodes value. Be careful about using polling values below 30000 (30 seconds) as polling can flood the zwave network and cause problems. @@ -88,19 +89,7 @@ To add a Z-Wave device to your system, go to the Services menu and select the `z ### {% linkable_title Adding Security Devices %} -Security Z-Wave devices require a network key before being added to the network using the `zwave.add_node_secure` service. You must edit the `options.xml` file, located in your `python-openzwave config_path` to use a network key before adding these devices. - -Edit your `options.xml` file: - -```bash - -``` -Uncomment the line: -```bash -