From cc28670203004d96e31b4ad7729431fe2b6bb8d6 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sun, 11 Feb 2018 11:05:29 +0100 Subject: [PATCH 01/26] Add link --- source/getting-started/index.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/getting-started/index.markdown b/source/getting-started/index.markdown index 472503ae24c..d70ee636624 100644 --- a/source/getting-started/index.markdown +++ b/source/getting-started/index.markdown @@ -9,9 +9,9 @@ sharing: true footer: true --- -The goal of this getting started guide is to install Hass.io on a Raspberry Pi 3. Hass.io is our own all in one solution that turns your Raspberry Pi into the ultimate home automation hub. +The goal of this getting started guide is to install [Hass.io](/hassio/) on a Raspberry Pi 3. Hass.io is our own all in one solution that turns your Raspberry Pi into the ultimate home automation hub. -Follow this guide if you want to easily get started with Home Assistant, or if you have no or little Linux experience. For advanced users, check our [alternative installation methods](/docs/installation/). +Follow this guide if you want to easily get started with Home Assistant, or if you have no or little Linux experience. For advanced users or if you have no Raspberry Pi at hand, check our [alternative installation methods](/docs/installation/). ### {% linkable_title Hardware requirements %} @@ -31,7 +31,7 @@ We will need a few things to get started with installing Home Assistant. Links b [Etcher]: https://etcher.io/ [pi3]: https://github.com/home-assistant/hassio-build/releases/download/1.1/resinos-hassio-1.1-raspberrypi3.img.bz2 -### Installing Hass.io +### {% linkable_title Installing Hass.io %} 1. Put the SD card in your SD card reader. 1. Open Etcher, select the Hass.io image and flash it to the SD card. From 3de6e038f1899fec56254504ba4b15a288c6c1c9 Mon Sep 17 00:00:00 2001 From: themanieldaniel Date: Sun, 11 Feb 2018 05:07:21 -0500 Subject: [PATCH 02/26] Update samba.markdown (#4631) --- source/_addons/samba.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_addons/samba.markdown b/source/_addons/samba.markdown index 33e573ec377..ee591117311 100644 --- a/source/_addons/samba.markdown +++ b/source/_addons/samba.markdown @@ -22,7 +22,7 @@ This addon allows you to set up a [Samba](https://samba.org/) server to access h "addons": true, "share": true, "backup": true, - "ssl": false, + "ssl": false }, "username": "", "password": "", From 4bd6d7c4b6983e9fc21bed776f11840ccf4a2c23 Mon Sep 17 00:00:00 2001 From: themanieldaniel Date: Sun, 11 Feb 2018 05:08:40 -0500 Subject: [PATCH 03/26] Update history.markdown (#4633) --- source/_components/history.markdown | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/source/_components/history.markdown b/source/_components/history.markdown index b252d3b205f..76affbecc65 100644 --- a/source/_components/history.markdown +++ b/source/_components/history.markdown @@ -13,7 +13,7 @@ ha_release: pre 0.7 --- -The `history` component will track everything that is going on within Home Assistant and allows the user to browse through it. It depends on the `recorder` component for storing the data and uses the same database setting. If any entities are excluded from being recorded, no history will be available for these entities as well. +The `history` component will track everything that is going on within Home Assistant and allows the user to browse through it. It depends on the `recorder` component for storing the data and uses the same database setting. If any entities are excluded from being recorded, no history will be available for these entities. To enable the history option in your installation, add the following to your `configuration.yaml` file: @@ -42,9 +42,9 @@ Configuration variables: - **entities** (*Optional*): The list of entity ids to be included to the history. - **domains** (*Optional*): The list of domains to be included to the history. -Without any `include` or `exclude` configuration the history displays graphs for every entity (well that's not exactly true - for instance `hidden` entities or `scenes` are never shown) on a given date. If you are only interested in some of the entities you several options: +Without any `include` or `exclude` configuration the history displays graphs for every entity (well that's not exactly true - for instance `hidden` entities or `scenes` are never shown) on a given date. If you are only interested in some of the entities you have several options: -Define domains and entities to `exclude` (aka. blacklist). This is convenient when you are basically happy with the information displayed, but just want to remove some entities or domains. Usually these are entities/domains which do not change (like `weblink`) or rarely change (`updater` or `automation`). +Define domains and entities to `exclude` (aka. blacklist). This is convenient when you are basically happy with the information displayed, but just want to remove some entities or domains. Usually these are entities/domains which do not change (like `weblink`) or rarely change (like `updater` or `automation`). ```yaml # Example configuration.yaml entry with exclude @@ -59,7 +59,7 @@ history: - sensor.date ``` -Define domains and entities to display by using the `include` configuration (aka. whitelist). If you have a lot of entities in your system and your `exclude` lists possibly get very large, it might be better just to define the entities or domains to display. +Define domains and entities to display by using the `include` configuration (aka. whitelist). If you have a lot of entities in your system and your `exclude` list is getting too large, it might be better just to define the entities or domains to `include`. ```yaml # Example configuration.yaml entry with include @@ -104,7 +104,7 @@ history: #### {% linkable_title Implementation details %} -The history is stored in a SQLite database `home-assistant_v2.db` within your configuration directory if the `recorder` component is not set up differently. +The history is stored in a SQLite database `home-assistant_v2.db` within your configuration directory unless the `recorder` component is set up differently. - events table is all events except `time_changed` that happened while recorder component was running. - states table contains all the `new_state` values of `state_changed` events. @@ -129,4 +129,4 @@ datetime.fromtimestamp(1422830502) #### {% linkable_title API %} -The history information are also available through the [RESTful API](/developers/rest_api/#get-apihistory). +The history information is also available through the [RESTful API](/developers/rest_api/#get-apihistory). From 58eb051d55939e6f090f190e9552d0db7d4d2b89 Mon Sep 17 00:00:00 2001 From: themanieldaniel Date: Sun, 11 Feb 2018 05:18:28 -0500 Subject: [PATCH 04/26] Update sensor.steam_online.markdown (#4632) --- source/_components/sensor.steam_online.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_components/sensor.steam_online.markdown b/source/_components/sensor.steam_online.markdown index 6cf46388770..e49bef70cb5 100644 --- a/source/_components/sensor.steam_online.markdown +++ b/source/_components/sensor.steam_online.markdown @@ -16,9 +16,9 @@ ha_release: 0.14 The Steam component will allow you to track the online status of public [Steam](https://steamcommunity.com) accounts. -You need an API key which is [free](https://steamcommunity.com/dev/apikey) to use the component +You need a [free API key](https://steamcommunity.com/dev/apikey) to use the component -To find an account's 64-bit SteamID you can check the URL of the profile page, if it ends with a long string on numbers then that's the 64-bit SteamID. However, if the profile has a custom URL you will have to copy the it and enter it into [STEAMID I/O](https://steamid.io/) to find the 64-bit SteamID. +To find an account's 64-bit SteamID on profiles without a custom URL you can check the URL of the profile page, the long string of numbers at the end is the 64-bit SteamID. If the profile has a custom URL you will have to copy the URL into [STEAMID I/O](https://steamid.io/) to find the 64-bit SteamID. To use Steam in your installation, add the following to your `configuration.yaml` file: From 9d6e015466be4b66c98769711c5e1139c82457bb Mon Sep 17 00:00:00 2001 From: Touliloup Date: Sun, 11 Feb 2018 11:19:17 +0100 Subject: [PATCH 05/26] Fix URL in Mercedes me binary sensor documentation (#4625) Fix a broken link in the Mercedes Me binary sensor documentation. Link should redirect to the main Mercedes Me component. --- source/_components/binary_sensor.mercedesme.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/binary_sensor.mercedesme.markdown b/source/_components/binary_sensor.mercedesme.markdown index 932574774f8..e1df898d498 100644 --- a/source/_components/binary_sensor.mercedesme.markdown +++ b/source/_components/binary_sensor.mercedesme.markdown @@ -17,4 +17,4 @@ The `Mercedes me` platform allows you to get data from your [Mercedes me connect They will be automatically discovered if the Mercedes me component is loaded. -For more configuration information see the [Mercedes me component](/components/mercedes me/) documentation. +For more configuration information see the [Mercedes me component](/components/mercedesme/) documentation. From 6f90763a26e82160420ed2e50010346a3cbfece5 Mon Sep 17 00:00:00 2001 From: themanieldaniel Date: Sun, 11 Feb 2018 06:07:48 -0500 Subject: [PATCH 06/26] Update samba.markdown (#4627) Cleaned up some of the grammar and formatting. --- source/_addons/samba.markdown | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/source/_addons/samba.markdown b/source/_addons/samba.markdown index ee591117311..a8cd931cbee 100644 --- a/source/_addons/samba.markdown +++ b/source/_addons/samba.markdown @@ -32,10 +32,10 @@ This addon allows you to set up a [Samba](https://samba.org/) server to access h Configuration variables: -- **name** (*Optional*): default `hassio`. Set NetBIOS name of hassio device. -- **workgroup** (*Optional*): default `WORKGROUP`. Set network workgroup. -- **guest** (*Optional*): Allow login without a username or password. Defaults to `true`. -- **map** (*Optional*): Control which folder will be exposed. `config` is for Home Assistant configuration folder. `addons` for a local custom repository. `share` is a folder that can access from add-ons and Home Assistant too. `backup` for access to snapshot files. `ssl` for certificate storage, be careful with this option! Defaults all to `true`, except for `ssl`. -- **username** (*Optional*): The username for logging in if guest login is not used. +- **name** (*Optional*): Set netbios name of Hass.io device. Default is `hassio`. +- **workgroup** (*Optional*): Set network workgroup name. Default is `WORKGROUP`. +- **guest** (*Optional*): Allow login without a username or password. Default is `true`. +- **map** (*Optional*): Control which folders will be exposed. `config` shares the Home Assistant configuration folder. `addons` shares the local custom repositiory. `share` shares a folder that can be accessed by add-ons and Home Assistant. `backup` shares access to snapshot files. `ssl` shares certificate storage. Be careful with the `ssl` option! Defaults are all set to `true`, except for `ssl`. +- **username** (*Optional*): Username for logging in if guest login is not used. - **password** (*Optional*): Password for `username`. An empty password is not supported. -- **interface** (*Optional*): Interface on that will start the share. Normally is `eth0` for ethernet wired connection and `wlan0` for wireless connection. +- **interface** (*Optional*): Interface that will start the share. Normally this is `eth0` for ethernet wired connection and `wlan0` for wireless connection. From 5eff43736b7c7e8e952eb481140babeaf5f47533 Mon Sep 17 00:00:00 2001 From: themanieldaniel Date: Sun, 11 Feb 2018 06:07:58 -0500 Subject: [PATCH 07/26] Update input_number.markdown (#4628) * Update input_number.markdown * Minor changes --- source/_components/input_number.markdown | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/source/_components/input_number.markdown b/source/_components/input_number.markdown index 348053d8eec..7afaaa255e0 100644 --- a/source/_components/input_number.markdown +++ b/source/_components/input_number.markdown @@ -14,7 +14,7 @@ redirect_from: /components/input_slider/ ---

-Before version 0.55 this component was known as `input_slider` and did not have the `mode` configuration option. +Before version 0.55 this component was known as `input_slider` and did not have the `mode` configuration option. Also, service `select_value` is now `set_value`.

The `input_number` component allows the user to define values that can be controlled via the frontend and can be used within conditions of automation. The frontend can display a slider, or a numeric input box. Changes to the slider or numeric input box generate state events. These state events can be utilized as `automation` triggers as well. @@ -39,7 +39,6 @@ input_number: mode: box ``` - {% configuration %} input_number: description: Alias for the input. Multiple entries are allowed. From 3ce0f0981a1ff268138a4d8439fe1da27b3a9e6a Mon Sep 17 00:00:00 2001 From: Eu Date: Sun, 11 Feb 2018 18:34:35 +0100 Subject: [PATCH 08/26] Added documentation for password mode in input_text (#4489) * Added password mode * Added password mode * Added password mode --- source/_components/input_text.markdown | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/source/_components/input_text.markdown b/source/_components/input_text.markdown index 2fa07711af3..d0afd0ff097 100644 --- a/source/_components/input_text.markdown +++ b/source/_components/input_text.markdown @@ -12,7 +12,7 @@ ha_category: Automation ha_release: 0.53 --- -The `input_text` component allows the user to define values that can be controlled via the frontend and can be used within conditions of automation. Changes to the value stored in the text box generate state events. These state events can be utilized as `automation` triggers as well. +The `input_text` component allows the user to define values that can be controlled via the frontend and can be used within conditions of automation. Changes to the value stored in the text box generate state events. These state events can be utilized as `automation` triggers as well. It can also be configured in password mode (obscured text). ```yaml # Example configuration.yaml entries @@ -27,6 +27,9 @@ input_text: text3: name: Text 3 pattern: '[a-fA-F0-9]*' + text4: + name: Text 4 + mode: password ``` {% configuration %} @@ -59,6 +62,11 @@ input_text: required: false type: String default: empty + mode: + description: Can specify `text` or `password`. Elements of type "password" provide a way for the user to securely enter a value. + required: false + type: String + default: text {% endconfiguration %} ### {% linkable_title Restore State %} From ddf522bb7b01b4296e64a19e84a79f5abc957c07 Mon Sep 17 00:00:00 2001 From: Louis Laureys Date: Sun, 11 Feb 2018 19:57:40 +0100 Subject: [PATCH 09/26] Update dead links (#4637) Links were moved. --- source/_docs/ecosystem/hass-configurator.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_docs/ecosystem/hass-configurator.markdown b/source/_docs/ecosystem/hass-configurator.markdown index c9fac261ec8..1d07bf163d1 100644 --- a/source/_docs/ecosystem/hass-configurator.markdown +++ b/source/_docs/ecosystem/hass-configurator.markdown @@ -109,8 +109,8 @@ Since the configurator script on its own is no service, you will have to take so 1. Fork the process into the background with the command: `nohup sudo ./configurator.py &` -2. If your system is using systemd (that's usually what you'll find on a Raspberry Pi), there's a [template file](https://github.com/danielperna84/hass-configurator/blob/master/hass-poc-configurator.systemd) you can use and then apply the same process to integrate it as mentioned in the [Home Assistant documentation](https://home-assistant.io/docs/autostart/systemd/). If you use this method you have to set the `BASEPATH` variable according to your environment. -3. If you have [supervisor](http://supervisord.org/) running on your system, [hass-poc-configurator.supervisor](https://github.com/danielperna84/hass-configurator/blob/master/hass-poc-configurator.supervisor) would be an example configuration you could use to control the configurator. +2. If your system is using systemd (that's usually what you'll find on a Raspberry Pi), there's a [template file](https://github.com/danielperna84/hass-configurator/blob/master/hass-configurator.systemd) you can use and then apply the same process to integrate it as mentioned in the [Home Assistant documentation](https://home-assistant.io/docs/autostart/systemd/). If you use this method you have to set the `BASEPATH` variable according to your environment. +3. If you have [supervisor](http://supervisord.org/) running on your system, [hass-poc-configurator.supervisor](https://github.com/danielperna84/hass-configurator/blob/master/hass-configurator.supervisor) would be an example configuration you could use to control the configurator. 4. A tool called [tmux](https://tmux.github.io/), which should be pre-installed with [HASSbian](https://home-assistant.io/docs/hassbian/). 5. A tool called [screen](http://ss64.com/bash/screen.html) (alternative to tmux). If it's not already installed on your system, you can do `sudo apt-get install screen` or `sudo yum install screen` to get it. When it's installed, start a screen session by executing `screen`. Then navigate to your Home Assistant directory and start the configurator like described above. Put the screen session into the background by pressing `CTRL+A` and then `CTRL+D`. It is now safe to disconnect from your SSH session. To resume the screen session, log in to your machine and execute `screen -r`. From 88d890aa465c89e4771432abf92f7579f99895d8 Mon Sep 17 00:00:00 2001 From: Nicholas Amadori Date: Mon, 12 Feb 2018 08:46:34 +0100 Subject: [PATCH 10/26] Update Postgresql example (#4642) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The query with pg_size_pretty returns the value as a string, that way you can’t have a nice chart or make value comparison. Inserted new query to return value as number. --- source/_components/sensor.sql.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/source/_components/sensor.sql.md b/source/_components/sensor.sql.md index a1a0c40fc14..28ec3797881 100644 --- a/source/_components/sensor.sql.md +++ b/source/_components/sensor.sql.md @@ -90,6 +90,12 @@ SELECT * FROM states WHERE entity_id='binary_sensor.xyz789' GROUP BY state ORDER ### {% linkable_title Database size in Postgres %} -```sql -SELECT pg_size_pretty(pg_database_size('Database Name')); +```yaml +- platform: sql + db_url: postgresql://user:password@host/dbname + queries: + - name: db_size + query: "SELECT (pg_database_size('dsmrreader')/1024/1024) as db_size;" + column: "db_size" + unit_of_measurement: MB ``` From fffa4c48c7d008c710af529673b2f619e3b635ac Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Mon, 12 Feb 2018 08:58:18 -0800 Subject: [PATCH 11/26] Release 0.63.1 --- _config.yml | 6 ++--- source/_posts/2018-02-10-release-63.markdown | 23 ++++++++++++++++++++ 2 files changed, 26 insertions(+), 3 deletions(-) diff --git a/_config.yml b/_config.yml index 173458ad062..7b69f8bc2e3 100644 --- a/_config.yml +++ b/_config.yml @@ -140,13 +140,13 @@ social: # Home Assistant release details current_major_version: 0 current_minor_version: 63 -current_patch_version: 0 -date_released: 2018-02-10 +current_patch_version: 1 +date_released: 2018-02-12 # 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: "#" +patch_version_notes: "#release-0631---february-12" # Minor release (Example #release-0431---april-25): # Date we moved to Discourse for comments diff --git a/source/_posts/2018-02-10-release-63.markdown b/source/_posts/2018-02-10-release-63.markdown index e9fb47b45a8..2f91e77a447 100644 --- a/source/_posts/2018-02-10-release-63.markdown +++ b/source/_posts/2018-02-10-release-63.markdown @@ -41,6 +41,16 @@ We're planning a lot of cool stuff around the entity registry. Stay tuned! - SQL sensor ([@dgomes] - [#12142]) ([sensor.sql docs]) (new-platform) - Add Mercedes me component ([@ReneNulschDE] - [#11743]) (new-platform) +## {% linkable_title Release 0.63.1 - February 12 %} + +- Fix Alexa Step Volume ([@lucasweb78] - [#12314]) ([alexa docs]) +- Remove unique ID from netatmo ([@balloob] - [#12317]) ([binary_sensor.netatmo docs]) ([camera.netatmo docs]) ([sensor.netatmo docs]) +- Allow overriding name via entity registry ([@balloob] - [#12292]) +- Respect entity namespace for entity registry ([@balloob] - [#12313]) +- Fix Report State for Alexa Brightness Controller ([@lucasweb78] - [#12318]) ([alexa docs]) +- Always return lockState == LOCKED when handling Alexa.LockController ([@lucasweb78] - [#12328]) ([alexa docs]) +- Fix platform dependencies ([@balloob] - [#12330]) + ## {% 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). The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks. @@ -602,3 +612,16 @@ Experiencing issues introduced by this release? Please report them in our [issue [zha docs]: https://home-assistant.io/components/zha/ [zha.const docs]: https://home-assistant.io/components/zha.const/ [zwave docs]: https://home-assistant.io/components/zwave/ +[#12292]: https://github.com/home-assistant/home-assistant/pull/12292 +[#12313]: https://github.com/home-assistant/home-assistant/pull/12313 +[#12314]: https://github.com/home-assistant/home-assistant/pull/12314 +[#12317]: https://github.com/home-assistant/home-assistant/pull/12317 +[#12318]: https://github.com/home-assistant/home-assistant/pull/12318 +[#12328]: https://github.com/home-assistant/home-assistant/pull/12328 +[#12330]: https://github.com/home-assistant/home-assistant/pull/12330 +[@balloob]: https://github.com/balloob +[@lucasweb78]: https://github.com/lucasweb78 +[alexa docs]: https://home-assistant.io/components/alexa/ +[binary_sensor.netatmo docs]: https://home-assistant.io/components/binary_sensor.netatmo/ +[camera.netatmo docs]: https://home-assistant.io/components/camera.netatmo/ +[sensor.netatmo docs]: https://home-assistant.io/components/sensor.netatmo/ From cee61653450c8056c23d801a775da68572b5cd90 Mon Sep 17 00:00:00 2001 From: Philip Rosenberg-Watt Date: Mon, 12 Feb 2018 14:47:50 -0700 Subject: [PATCH 12/26] Fix typo (#4655) --- source/_docs/scripts/conditions.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/scripts/conditions.markdown b/source/_docs/scripts/conditions.markdown index 3314e0f4273..167b2737649 100644 --- a/source/_docs/scripts/conditions.markdown +++ b/source/_docs/scripts/conditions.markdown @@ -30,7 +30,7 @@ condition: ### {% linkable_title OR condition %} -Test multiple conditions in 1 condition statement. Passes if any embedded conditions is valid. +Test multiple conditions in 1 condition statement. Passes if any embedded condition is valid. ```yaml condition: From 178175fbf47c6fa03d7d2e3fe7901230cd2504eb Mon Sep 17 00:00:00 2001 From: Diogo Gomes Date: Mon, 12 Feb 2018 21:50:16 +0000 Subject: [PATCH 13/26] Added Example for 2 STB (#4649) --- .../_components/media_player.mediaroom.markdown | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/source/_components/media_player.mediaroom.markdown b/source/_components/media_player.mediaroom.markdown index 17724f0d763..828656b7e9f 100644 --- a/source/_components/media_player.mediaroom.markdown +++ b/source/_components/media_player.mediaroom.markdown @@ -47,6 +47,19 @@ Notice that all parameters are optional, and discovery should configure everythi The component has been developed for Portuguese TV operators currently using the Mediaroom platform, but should also work in other deployments in which the STB can be controlled remotely through a socket on port 8082. -In most cases (single STB) you just need to setup the *name* and discovery will do the rest. In case you have more than one STB you are required to set the *host* in each one of the entries. +In most cases (single STB) you just need to setup the *platform* and discovery will do the rest. In case you have more than one STB you are required to set the *host* in each one of the entries. If the STB is on the same network segment as Home Assistant, it can determine whether the device is turned on or off. Without this, the component will fail to determine the Set-top box status, and you are required to add the *optimistic* configuration variable. + +### {% linkable_title Example configuration with 2 STB %} + +```yaml +# Example configuration.yaml entry for 2 STB +media_player: + - platform: mediaroom + host: 192.168.1.64 + name: Living Room STB + - platform: mediaroom + host: 192.168.1.65 + name: Bedroom STB +``` From ea164a47d8c97066aa6f60f7b647edd604067e07 Mon Sep 17 00:00:00 2001 From: Philip Rosenberg-Watt Date: Mon, 12 Feb 2018 14:50:56 -0700 Subject: [PATCH 14/26] Fix typo (#4656) --- source/_docs/ecosystem/appdaemon.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/ecosystem/appdaemon.markdown b/source/_docs/ecosystem/appdaemon.markdown index 76edbc1dd54..f327433108d 100755 --- a/source/_docs/ecosystem/appdaemon.markdown +++ b/source/_docs/ecosystem/appdaemon.markdown @@ -76,7 +76,7 @@ class FlashyMotionLights(appapi.AppDaemon): This is starting to get a little more complex in Home Assistant automations, requiring an automation rule and two separate scripts. -Now let's extend this with a somewhat artificial example to show something that is simple in AppDaemon but very difficult if not impossible using automations. Let's warn someone inside the house that there has been motion outside by flashing a lamp on and off ten times. We are reacting to the motion as before by turning on the light and setting a timer to turn it off again, but in addition, we set a 1-second timer to run `flash_warning()`, which, when called, toggles the inside light and sets another timer to call itself a second later. To avoid re-triggering forever, it keeps a count of how many times it has been activated and bales out after ten iterations. +Now let's extend this with a somewhat artificial example to show something that is simple in AppDaemon but very difficult if not impossible using automations. Let's warn someone inside the house that there has been motion outside by flashing a lamp on and off ten times. We are reacting to the motion as before by turning on the light and setting a timer to turn it off again, but in addition, we set a 1-second timer to run `flash_warning()`, which, when called, toggles the inside light and sets another timer to call itself a second later. To avoid re-triggering forever, it keeps a count of how many times it has been activated and bails out after ten iterations. ```python import appdaemon.appapi as appapi From c0b944d21d8064a016cce9b490a5ac27d8c366b0 Mon Sep 17 00:00:00 2001 From: David Date: Tue, 13 Feb 2018 02:49:56 +0100 Subject: [PATCH 15/26] Remove note about differing entity_ids for System Monitor component (#4564) * Update example entity_id for System Monitor component Required update if/when home-assistant/home-assistant#12124 gets merged. * Update entity_id Update entity_id to reflect changes in PR * Remove note Remove note about differing entity_ids: after home-assistant/home-assistant#12124 is merged, all entity_ids will match the resource name. --- source/_components/sensor.systemmonitor.markdown | 9 --------- 1 file changed, 9 deletions(-) diff --git a/source/_components/sensor.systemmonitor.markdown b/source/_components/sensor.systemmonitor.markdown index 0cc01b8ade6..9ae17d80ba0 100644 --- a/source/_components/sensor.systemmonitor.markdown +++ b/source/_components/sensor.systemmonitor.markdown @@ -60,15 +60,6 @@ The table contains types and their argument to use in your `configuration.yaml` | last_boot | | | since_last_boot | | -**Note**: Some `type:` names used in the `configuration.yaml` file differ from the entity names. - -| Sensor type | Entity ID | -| :------------------ |:-------------------------| -| memory_free | sensor.ram_available | -| memory_use_percent | sensor.ram_used | -| processor_use | sensor.cpu_used | -| disk_use | sensor.disk_used | - ## {% linkable_title Linux specific %} To retrieve all available network interfaces on a Linux System, execute the `ifconfig` command. From 9a1489230e85d2a8d532c62bc7f22c24773c9c48 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Tue, 13 Feb 2018 09:46:16 +0100 Subject: [PATCH 16/26] Add Home Assistant vs. Hass.io entry (#4657) * Add link to glossary * Add ha vs. hass.io --- source/_faq/ha-vs-hassio.markdown | 16 ++++++++++++++++ source/faq/index.markdown | 2 +- 2 files changed, 17 insertions(+), 1 deletion(-) create mode 100644 source/_faq/ha-vs-hassio.markdown diff --git a/source/_faq/ha-vs-hassio.markdown b/source/_faq/ha-vs-hassio.markdown new file mode 100644 index 00000000000..a331e034aa2 --- /dev/null +++ b/source/_faq/ha-vs-hassio.markdown @@ -0,0 +1,16 @@ +--- +layout: page +title: "Home Assistant vs. Hass.io" +description: "Home Assistant vs. Hass.io" +date: 2018-02-12 09:00 +sidebar: true +comments: false +sharing: true +footer: true +ha_category: Installation +--- + +Home Assistant is a Python program, in simple words. It can be run various operating system and provide the ability to track, control and automate your devices. When people talking about Home Assistant they usually refer to a standalone [installation method](/docs/installation/). + +[Hass.io](/hassio/) is a combination of Home Assistant and tools which allows one to run it easily on a Raspberry Pi and other platforms without setting up an operating system first. Hass.io is an all-in one-solution and has a management user interface that can be used from the Home Assistant frontend. This interface is not present in a standalone setup of Home Assistant. + diff --git a/source/faq/index.markdown b/source/faq/index.markdown index f3af719ffb5..9dc9352fcf6 100644 --- a/source/faq/index.markdown +++ b/source/faq/index.markdown @@ -11,7 +11,7 @@ regenerate: true hide_github_edit: true --- -This is a community curated list of frequently asked questions (FAQ) about the installation, setup, and usage of Home Assistant. +This is a community curated list of frequently asked questions (FAQ) about the installation, setup, and usage of Home Assistant. If you want to get details about a term, please check the [glossary](/docs/glossary/). {% assign faq = site.faq | sort: 'title' %} {% assign categories = faq | map: 'ha_category' | uniq | sort %} From 347604383e9c5afce22089b1834eea002b7e14b9 Mon Sep 17 00:00:00 2001 From: xander2 <1768338+xander2@users.noreply.github.com> Date: Tue, 13 Feb 2018 17:03:29 +0100 Subject: [PATCH 17/26] Various spelling, wording and grammar fixes (#4659) Corrections to enhance readability of documentation. --- source/hassio/run_local.markdown | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/source/hassio/run_local.markdown b/source/hassio/run_local.markdown index 311098aa413..8085f77f1f3 100644 --- a/source/hassio/run_local.markdown +++ b/source/hassio/run_local.markdown @@ -9,15 +9,15 @@ sharing: true footer: true --- -Hass.io is a managed environment, which means that you can't install applications that can be embedded into Home Assistant using the `command_line` sensor/switch. +Hass.io is a managed environment, which means you can't install applications that can be embedded into Home Assistant using the `command_line` sensor/switch. -There are three options if you need to run a script to read data from a sensor or send commands to other devices on Hass.io. +There are three options if you need to run a script which reads data from a sensor or sends commands to other devices on Hass.io. -The first option is to write a custom component for Home Assistant. Using Python, you can communicate with your device. For more information about developing a custom component, take a look at the [developer documentation][custom-component]. +The first option is to write a custom component for Home Assistant. This implies that you can communicate with your device using Python. For more information about developing a custom component, take a look at [custom-component development][custom-component]. -The second option is to use STDIN inside add-on and use the service `hassio.addon_stdin` to send data. More about this options look into [developer documentation][communication] for internal add-on communication. There is also describe how do you can easy access to Home-Assistant Rest API. +The second option is to use STDIN inside an add-on and use the service `hassio.addon_stdin` to send data. For more information, have a look at [internal add-on communication][communication]. Here you will also find how you can easily access the Home Assistant Rest API. -The third option is to make a local add-on for Hass.io that sends the data to Home Assistant via MQTT. Before we dive into this, read up on [Hass.io add-on development][addons-tutorial] first. +The third option is to create a local add-on for Hass.io that sends the data to Home Assistant via MQTT. Before we dive into this, read up on [Hass.io add-on development][addons-tutorial] first. For security and speed, Hass.io does not provide a way for containers to communicate directly. So the first step is to set up a communication channel. We're going to use MQTT for this using the [MQTT broker add-on][mqtt-addon]. @@ -25,7 +25,7 @@ For security and speed, Hass.io does not provide a way for containers to communi We loop in our script to fetch data and push it to MQTT and wait until the next process is ready. Here is a basic example and structure for that process. -Our Dockerfile need to install: +In our Dockerfile we need to install: ``` RUN apk --no-cache add jq mosquitto-clients @@ -65,7 +65,7 @@ done We wait for incoming data from the MQTT broker. We can also use an `input_boolean` that triggers an automation to publish a custom command to MQTT topic that can process multiple things in one add-on. -Our Dockerfile need to install: +In our Dockerfile we need to install: ``` RUN apk --no-cache add jq mosquitto-clients From fb2236f70e96bd03bfdb9f90c200edc9e7ab2539 Mon Sep 17 00:00:00 2001 From: CupricReki Date: Tue, 13 Feb 2018 09:04:25 -0700 Subject: [PATCH 18/26] Update installation.markdown (#4661) `raspbi-config` changed to `raspi-config` --- source/_docs/z-wave/installation.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/z-wave/installation.markdown b/source/_docs/z-wave/installation.markdown index b110e34863e..7b40c12bb4a 100644 --- a/source/_docs/z-wave/installation.markdown +++ b/source/_docs/z-wave/installation.markdown @@ -36,7 +36,7 @@ $ sudo /Applications/Python\ x.x/Install\ Certificates.command ### {% linkable_title Raspberry Pi %} -On Raspberry Pi you will need to enable the serial interface in the `raspbi-config` tool before you can add Z-Wave to Home Assistant. +On Raspberry Pi you will need to enable the serial interface in the `raspi-config` tool before you can add Z-Wave to Home Assistant. ## {% linkable_title Configuration %} From 8226c05682aaab7b1d9d62bd97ac3c6a5c72581a Mon Sep 17 00:00:00 2001 From: Rene Nulsch <33263735+ReneNulschDE@users.noreply.github.com> Date: Tue, 13 Feb 2018 17:05:15 +0100 Subject: [PATCH 19/26] Add lxml requirement note (#4651) --- source/_components/mercedesme.markdown | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/source/_components/mercedesme.markdown b/source/_components/mercedesme.markdown index e84e87c6124..c85b54cd78e 100644 --- a/source/_components/mercedesme.markdown +++ b/source/_components/mercedesme.markdown @@ -48,4 +48,8 @@ scan_interval: required: true default: 30 type: int -{% endconfiguration %} \ No newline at end of file +{% endconfiguration %} + +

+The requirement `lxml` has to be [installed](http://lxml.de/installation.html) manually `pip install lxml` on some devices. +

From f97d5189e9c76f73761b881d1223a46f3b7fbcea Mon Sep 17 00:00:00 2001 From: Bob Igo Date: Tue, 13 Feb 2018 11:10:53 -0500 Subject: [PATCH 20/26] Provide an example of how to make a 'when dark' condition by ORing sunrise and sunset conditions. (#4652) See issue#12308 at https://github.com/home-assistant/home-assistant/issues/12308 --- source/_docs/scripts/conditions.markdown | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/source/_docs/scripts/conditions.markdown b/source/_docs/scripts/conditions.markdown index 167b2737649..d2dc0638d80 100644 --- a/source/_docs/scripts/conditions.markdown +++ b/source/_docs/scripts/conditions.markdown @@ -114,6 +114,16 @@ condition: after_offset: "-1:00:00" ``` +```yaml +condition: + condition: or # 'when dark' condition: either after sunset or before sunrise + conditions: + - condition: sun + after: sunset + - condition: sun + before: sunrise +``` + Here is a truth table to clarify the parameters with and without offset: | command | night | at sunrise | daytime | at sunset | From 97c3b418f5f31cb6b61f452e216033d36750926d Mon Sep 17 00:00:00 2001 From: poldim Date: Tue, 13 Feb 2018 09:56:05 -0800 Subject: [PATCH 21/26] Update discovery.markdown (#4662) --- source/_docs/mqtt/discovery.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_docs/mqtt/discovery.markdown b/source/_docs/mqtt/discovery.markdown index 0fa7a45c040..a0f3737cbce 100644 --- a/source/_docs/mqtt/discovery.markdown +++ b/source/_docs/mqtt/discovery.markdown @@ -58,6 +58,7 @@ The following firmware for ESP8266, ESP32 and Sonoff unit has built-in support f - [Sonoff-Tasmota](https://github.com/arendst/Sonoff-Tasmota) (starting with 5.11.1e) - [esphomelib](https://github.com/OttoWinter/esphomelib) - [ESPurna](https://github.com/xoseperez/espurna) +- [Arilux AL-LC0X LED controllers](https://github.com/mertenats/Arilux_AL-LC0X) ### {% linkable_title Examples %} From 653b4bae0330ce4b1404d6c033ead898faa25261 Mon Sep 17 00:00:00 2001 From: Tabakhase Date: Tue, 13 Feb 2018 19:40:34 +0100 Subject: [PATCH 22/26] clearify rpi_gpio sharing + revert #4608 (#4660) * Revert "add documentation for "shared_gpio" flag to component switch.rpi_gpio" This reverts commit f2dba1f614af51f84eadbdeab5ca2f566f334ad6. * clearify that rpi_gpio pins are exclusive to HASS-ussage when assigned --- source/_components/switch.rpi_gpio.markdown | 15 ++++----------- 1 file changed, 4 insertions(+), 11 deletions(-) diff --git a/source/_components/switch.rpi_gpio.markdown b/source/_components/switch.rpi_gpio.markdown index ad4079a433d..9f50d12987f 100644 --- a/source/_components/switch.rpi_gpio.markdown +++ b/source/_components/switch.rpi_gpio.markdown @@ -32,10 +32,13 @@ Configuration variables: - **ports** array (*Required*): Array of used ports. - **port: name** (*Required*): Port numbers and corresponding names (GPIO #). - **invert_logic** (*Optional*): If true, inverts the output logic to ACTIVE LOW. Default is false (ACTIVE HIGH). -- **shared_gpio** (*Optional*): If true, forces a GPIO.setup() before each write. Default is false. For more details about the GPIO layout, visit the Wikipedia [article](https://en.wikipedia.org/wiki/Raspberry_Pi#GPIO_connector) about the Raspberry Pi. +

+Note that a pin managed by HASS is expected to be exclusive to HASS. +

+ A common question is what does Port refer to, this number is the actual GPIO # not the pin #. For example, if you have a relay connected to pin 11 its GPIO # is 17. @@ -47,14 +50,4 @@ switch: 17: Speaker Relay ``` -In case you have any other python scripts running that use RPi.GPIO no values will be written after the initial HASS-start. -Setting **shared_gpio** to true will reinit the pin before each write, working around this issue. -```yaml -# Example configuration.yaml entry -switch: - - platform: rpi_gpio - shared_gpio: true - ports: - 19: LED-Red -``` From db727639c829bfc75d02d24f5432cfe882145a5c Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Tue, 13 Feb 2018 23:02:39 -0800 Subject: [PATCH 23/26] Release 0.63.2 --- _config.yml | 6 ++--- source/_posts/2018-02-10-release-63.markdown | 26 ++++++++++++++++++++ 2 files changed, 29 insertions(+), 3 deletions(-) diff --git a/_config.yml b/_config.yml index 7b69f8bc2e3..6ee6d3f537a 100644 --- a/_config.yml +++ b/_config.yml @@ -140,13 +140,13 @@ social: # Home Assistant release details current_major_version: 0 current_minor_version: 63 -current_patch_version: 1 -date_released: 2018-02-12 +current_patch_version: 2 +date_released: 2018-02-14 # 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-0631---february-12" +patch_version_notes: "#release-0632---february-14" # Minor release (Example #release-0431---april-25): # Date we moved to Discourse for comments diff --git a/source/_posts/2018-02-10-release-63.markdown b/source/_posts/2018-02-10-release-63.markdown index 2f91e77a447..cd07acf26df 100644 --- a/source/_posts/2018-02-10-release-63.markdown +++ b/source/_posts/2018-02-10-release-63.markdown @@ -51,6 +51,14 @@ We're planning a lot of cool stuff around the entity registry. Stay tuned! - Always return lockState == LOCKED when handling Alexa.LockController ([@lucasweb78] - [#12328]) ([alexa docs]) - Fix platform dependencies ([@balloob] - [#12330]) +## {% linkable_title Release 0.63.2 - February 14 %} + +- Fix MercedesMe - add check for unsupported features ([@ReneNulschDE] - [#12342]) ([mercedesme docs]) ([binary_sensor.mercedesme docs]) ([device_tracker.mercedesme docs]) ([sensor.mercedesme docs]) +- Fix WUnderground names ([@OttoWinter] - [#12346]) ([sensor.wunderground docs]) +- Updated beacontools ([@citruz] - [#12368]) ([sensor.eddystone_temperature docs]) +- Introduce zone_id to identify player+zone ([@sdague] - [#12382]) ([media_player.yamaha docs]) +- Downgrade limitlessled to 1.0.8 ([@amelchio] - [#12403]) ([light.limitlessled docs]) + ## {% 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). The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks. @@ -625,3 +633,21 @@ Experiencing issues introduced by this release? Please report them in our [issue [binary_sensor.netatmo docs]: https://home-assistant.io/components/binary_sensor.netatmo/ [camera.netatmo docs]: https://home-assistant.io/components/camera.netatmo/ [sensor.netatmo docs]: https://home-assistant.io/components/sensor.netatmo/ +[#12342]: https://github.com/home-assistant/home-assistant/pull/12342 +[#12346]: https://github.com/home-assistant/home-assistant/pull/12346 +[#12368]: https://github.com/home-assistant/home-assistant/pull/12368 +[#12382]: https://github.com/home-assistant/home-assistant/pull/12382 +[#12403]: https://github.com/home-assistant/home-assistant/pull/12403 +[@OttoWinter]: https://github.com/OttoWinter +[@ReneNulschDE]: https://github.com/ReneNulschDE +[@amelchio]: https://github.com/amelchio +[@citruz]: https://github.com/citruz +[@sdague]: https://github.com/sdague +[binary_sensor.mercedesme docs]: https://home-assistant.io/components/binary_sensor.mercedesme/ +[device_tracker.mercedesme docs]: https://home-assistant.io/components/device_tracker.mercedesme/ +[light.limitlessled docs]: https://home-assistant.io/components/light.limitlessled/ +[media_player.yamaha docs]: https://home-assistant.io/components/media_player.yamaha/ +[mercedesme docs]: https://home-assistant.io/components/mercedesme/ +[sensor.eddystone_temperature docs]: https://home-assistant.io/components/sensor.eddystone_temperature/ +[sensor.mercedesme docs]: https://home-assistant.io/components/sensor.mercedesme/ +[sensor.wunderground docs]: https://home-assistant.io/components/sensor.wunderground/ From 2d532d1147be4a9988d9207cba049c41d3a09157 Mon Sep 17 00:00:00 2001 From: David Date: Wed, 14 Feb 2018 08:22:18 +0100 Subject: [PATCH 24/26] Update 2018-02-10-release-63.markdown (#4667) Add the 3 original breaking changes from home-assistant/home-assistant#12124 --- source/_posts/2018-02-10-release-63.markdown | 3 +++ 1 file changed, 3 insertions(+) diff --git a/source/_posts/2018-02-10-release-63.markdown b/source/_posts/2018-02-10-release-63.markdown index cd07acf26df..b58560e3ad6 100644 --- a/source/_posts/2018-02-10-release-63.markdown +++ b/source/_posts/2018-02-10-release-63.markdown @@ -96,17 +96,20 @@ Experiencing issues introduced by this release? Please report them in our [issue | Resource | Old Entity ID | New Entity ID | | :------------------ | :------------------ |:-------------------------| | disk_use | sensor.disk_used | sensor.disk_use | + | disk_use_percent | sensor.disk_used | sensor.disk_use_percent | | load_15m | sensor.average_load_15m | sensor.load_15m | | load_1m | sensor.average_load_1m | sensor.load_1m | | load_5m | sensor.average_load_5m | sensor.load_5m | | memory_free | sensor.ram_available | sensor.memory_free | | memory_use | sensor.ram_used | sensor.memory_use | + | memory_use_percent | sensor.ram_used | sensor.memory_use_percent | | network_in | sensor.received | sensor.network_in | | network_out | sensor.sent | sensor.network_out | | packets_in | sensor.packets_received | sensor.packets_in | | packets_out | sensor.packets_sent | sensor.packets_out | | processor_use | sensor.cpu_used | sensor.processor_use | | swap_use | sensor.swap_used | sensor.swap_use | + | swap_use_percent | sensor.swap_used | sensor.swap_use_percent | - Developers only: Following EntityComponent methods have been removed: `extract_from_service`, `async_update_group`, `async_reset`, `prepare_reload` ([@balloob] - [#12237]) (breaking change) From 65c442f92a9bb2be8d98404a19c94eaa383eeeac Mon Sep 17 00:00:00 2001 From: drogfild <35920772+drogfild@users.noreply.github.com> Date: Wed, 14 Feb 2018 21:27:12 +0200 Subject: [PATCH 25/26] Update how to save proper authorized_keys Saving private key straight from puttygen didn't work. Text from text-box must be saved to SD. --- source/developers/hassio/debugging.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/developers/hassio/debugging.markdown b/source/developers/hassio/debugging.markdown index 01a92c98ea8..3b5354e310f 100644 --- a/source/developers/hassio/debugging.markdown +++ b/source/developers/hassio/debugging.markdown @@ -28,7 +28,7 @@ Alternative instructions, for Mac, Windows and Linux can be found [here](https:/ Follow steps 1-4 under 'Generating a new SSH key' (The other sections are not applicable to Hass.io and can be ignored.) -Step 3 in the link above, shows the path to the private key file `id_rsa` for your chosen operating system. Your public key, `id_rsa.pub`, is saved in the same folder. Next, copy your public key file to the root of your SD card as `authorized_keys`. +Step 3 in the link above, shows the path to the private key file `id_rsa` for your chosen operating system. Your public key, `id_rsa.pub`, is saved in the same folder. Next, select all text from text box "Public key for pasting into OpenSSH authorized_keys file" and save it to to the root of your SD card as `authorized_keys`.

Make sure when you are copying the public key to the root of the /resin-boot partition of the SD card that you rename the file correctly to `authorized_keys` with no `.pub` file extension. From d08159983615020bd3e22f6eca7eb8669878745d Mon Sep 17 00:00:00 2001 From: drogfild <35920772+drogfild@users.noreply.github.com> Date: Thu, 15 Feb 2018 00:21:24 +0200 Subject: [PATCH 26/26] Removed extra word 'to' --- source/developers/hassio/debugging.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/developers/hassio/debugging.markdown b/source/developers/hassio/debugging.markdown index 3b5354e310f..d9030069a87 100644 --- a/source/developers/hassio/debugging.markdown +++ b/source/developers/hassio/debugging.markdown @@ -28,7 +28,7 @@ Alternative instructions, for Mac, Windows and Linux can be found [here](https:/ Follow steps 1-4 under 'Generating a new SSH key' (The other sections are not applicable to Hass.io and can be ignored.) -Step 3 in the link above, shows the path to the private key file `id_rsa` for your chosen operating system. Your public key, `id_rsa.pub`, is saved in the same folder. Next, select all text from text box "Public key for pasting into OpenSSH authorized_keys file" and save it to to the root of your SD card as `authorized_keys`. +Step 3 in the link above, shows the path to the private key file `id_rsa` for your chosen operating system. Your public key, `id_rsa.pub`, is saved in the same folder. Next, select all text from text box "Public key for pasting into OpenSSH authorized_keys file" and save it to the root of your SD card as `authorized_keys`.

Make sure when you are copying the public key to the root of the /resin-boot partition of the SD card that you rename the file correctly to `authorized_keys` with no `.pub` file extension.