From 14f0228a96e74d98533a52c74fe39c7ffd887797 Mon Sep 17 00:00:00 2001 From: DubhAd Date: Sun, 10 Dec 2017 11:27:16 +0000 Subject: [PATCH 01/13] Added note about hop limit (#4165) Just found out about the 4 hop limit, update to reflect this --- source/_docs/z-wave.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/z-wave.markdown b/source/_docs/z-wave.markdown index 98c9ffc9008..c6a68fb3c65 100644 --- a/source/_docs/z-wave.markdown +++ b/source/_docs/z-wave.markdown @@ -20,7 +20,7 @@ Before configuring the Z-Wave setup, please take a moment and read [this article Z-Wave is a wireless communication protocol designed for home automation. It uses a low power, and low bandwidth, mesh network that allows devices that aren't within direct range of each other to communicate indirectly, via other nodes. Any device that's permanently powered (not battery powered) will help build the mesh, if you don't have enough powered devices, or you locate these poorly, your mesh will be unreliable. -There is a limit of 232 devices in a single Z-Wave network. If you need more devices then you could set up a second Home Assistant system with its own Z-Wave network and connect these with the [MQTT Eventstream](/components/mqtt_eventstream/) or [MQTT Statestream](/components/mqtt_statestream) components. +There is a limit of 232 devices in a single Z-Wave network. If you need more devices then you could set up a second Home Assistant system with its own Z-Wave network and connect these with the [MQTT Eventstream](/components/mqtt_eventstream/) or [MQTT Statestream](/components/mqtt_statestream) components. There is also a limit of 4 hops for Z-Wave, so placing the controller as centrally as you can is important. The Z-Wave standard was improved with Z-Wave Plus, and if you only use Z-Wave plus devices then you will gain the full benefits. From 664900cd140f6915bfa8dda9ff6ba78175755d7c Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sun, 10 Dec 2017 12:38:16 +0100 Subject: [PATCH 02/13] Update type --- source/_components/sensor.coinmarketcap.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_components/sensor.coinmarketcap.markdown b/source/_components/sensor.coinmarketcap.markdown index f0d20afb171..63fde6b5ea5 100644 --- a/source/_components/sensor.coinmarketcap.markdown +++ b/source/_components/sensor.coinmarketcap.markdown @@ -28,12 +28,12 @@ sensor: currency: description: The cryptocurrency to use. required: false - type: string, list + type: string default: Bitcoin display_currency: description: The currency to display. required: false - type: string, list + type: string default: USD {% endconfiguration %} From 9eaa558af2d24210d85e90d93df4cbb38541e13e Mon Sep 17 00:00:00 2001 From: Roy <1826350+twoez@users.noreply.github.com> Date: Sun, 10 Dec 2017 18:13:49 +0100 Subject: [PATCH 03/13] Update nest.markdown (#4184) Firebase requests to the Nest API uses outgoing port 9553 instead of 8553. --- source/_components/nest.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/nest.markdown b/source/_components/nest.markdown index b3d376c50fc..7aa5adfb9c9 100644 --- a/source/_components/nest.markdown +++ b/source/_components/nest.markdown @@ -34,7 +34,7 @@ The Nest component is the main component to integrate all [Nest](https://nest.co 9. Once the new product page opens the "Product ID" and "Product Secret" are located on the right side. These will be used as `client_id` and `client_secret` below. 10. Once Home Assistant is started, a configurator will pop up asking you to log into your Nest account and copy a PIN code into Home Assistant. -Connecting to the Nest Developer API requires outbound port 8553 on your firewall. The configuration will fail if this is not accessible. +Connecting to the Nest Developer API requires outbound port 9553 on your firewall. The configuration will fail if this is not accessible. ### {% linkable_title Configuration %} From 81882e8995f597aadd2255e9e480802d0ffef46a Mon Sep 17 00:00:00 2001 From: Mahasri Kalavala Date: Mon, 11 Dec 2017 04:00:48 -0500 Subject: [PATCH 04/13] Added supported model (#4188) Tested the component with Sharp Aquos TV (LC-60SQ15U), and works great! Added that model to the supported TVs list. --- source/_components/media_player.aquostv.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_components/media_player.aquostv.markdown b/source/_components/media_player.aquostv.markdown index c9d7d2124d3..0e3dbcba7e0 100644 --- a/source/_components/media_player.aquostv.markdown +++ b/source/_components/media_player.aquostv.markdown @@ -53,5 +53,6 @@ Currently known supported models: - LC-60LE925UN - LC-60LE857U - LC-60EQ10U +- LC-60SQ15U If your model is not on the list then give it a test, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.github.io/tree/current/source/_components/media_player.aquostv.markdown). From d40dd5e6bb89a521825563a337014686a20a6de2 Mon Sep 17 00:00:00 2001 From: Jeremy Date: Mon, 11 Dec 2017 04:04:38 -0500 Subject: [PATCH 05/13] Update systemd.markdown (#4185) Correct spelling of Home Assistant on line 131. --- source/_docs/autostart/systemd.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/autostart/systemd.markdown b/source/_docs/autostart/systemd.markdown index 4ea709440f8..e1e1b6b4669 100644 --- a/source/_docs/autostart/systemd.markdown +++ b/source/_docs/autostart/systemd.markdown @@ -128,7 +128,7 @@ Because the log can scroll quite quickly, you can select to view only the error $ sudo journalctl -f -u home-assistant@[your user] | grep -i 'error' ``` -When working on Home Assitant, you can easily restart the system and then watch the log output by combining the above commands using `&&` +When working on Home Assistant, you can easily restart the system and then watch the log output by combining the above commands using `&&` ```bash $ sudo systemctl restart home-assistant@[your user] && sudo journalctl -f -u home-assistant@[your user] From 7599ef8726fe4ecd795e64e9d5c17976a20dafb2 Mon Sep 17 00:00:00 2001 From: tringler Date: Mon, 11 Dec 2017 10:21:21 +0100 Subject: [PATCH 06/13] Recommendation of Linux subsystem (#4187) * Recommendation of Linux subsystem * Minor changes --- .../development_environment.markdown | 32 +++++++++++++++---- 1 file changed, 26 insertions(+), 6 deletions(-) diff --git a/source/developers/development_environment.markdown b/source/developers/development_environment.markdown index 21d7651f031..d6779d701e6 100644 --- a/source/developers/development_environment.markdown +++ b/source/developers/development_environment.markdown @@ -16,11 +16,13 @@ You'll need to set up a development environment if you want to develop a new fea #### {% linkable_title Developing on Linux %} Install the core dependencies. + ```bash $ sudo apt-get install python3-pip python3-dev python3-venv ``` In order to run `script/setup` below you will need some more dependencies. + ```bash $ sudo apt-get install libssl-dev libxml2-dev libxslt1-dev libjpeg-dev libffi-dev libudev-dev zlib1g-dev ``` @@ -33,7 +35,28 @@ Additional dependencies exist if you plan to perform Frontend Development, pleas #### {% linkable_title Developing on Windows %} -If you are using Windows as a development platform, make sure that you have the correct Microsoft Visual C++ build tools installed. Check the [Windows Compilers](https://wiki.python.org/moin/WindowsCompilers) section on the [Python website](https://www.python.org/) for details. Validation using `tox` will fail if this is not done correctly. +Due to Home Assistant is mainly designed and developed on Linux distributions it is not recommended to develop on Windows machines. However on Windows 10 machines you should decide to set up a [Linux subsystem](https://docs.microsoft.com/de-de/windows/wsl/install-win10). + +Setup Linux subsystem. + +```bash +$ apt-get update +$ apt-get upgrade +$ echo 'export DISPLAY=:0' >> ~/.bashrc && . ~/.bashrc +$ sudo apt-get install xubuntu-desktop -y +``` + +Download and start PyCharm. + +```bash +$ wget https://download.jetbrains.com/python/pycharm-community-20XX.X.tar.gz +$ tar -xzf pycharm-community-20XX.X +$ ./pycharm.sh +``` + +In order to display the PyCharm GUI on Windows you need to run a X-Server like [VcXserv](https://sourceforge.net/projects/vcxsrv/). + +If you decide using Windows as a development platform, make sure that you have the correct Microsoft Visual C++ build tools installed. Check the [Windows Compilers](https://wiki.python.org/moin/WindowsCompilers) section on the [Python website](https://www.python.org/) for details. Validation using `tox` will fail if this is not done correctly. Also, make sure to install or upgrade the `setuptools` Python package. It contains compatibility improvements and adds automatic use of compilers: @@ -80,9 +103,6 @@ $ script/setup ### {% linkable_title Logging %} -By default logging in home-assistant is tuned for operating in -production (set to INFO by default, with some modules set to even less -verbose logging levels). +By default logging in home-assistant is tuned for operating in production (set to INFO by default, with some modules set to even less verbose logging levels). -You can use the [logger](/components/logger/) component to adjust -logging to DEBUG to see even more details about what is going on. +You can use the [logger](/components/logger/) component to adjust logging to DEBUG to see even more details about what is going on. From 9271f5aeef6a0215cc34b76339fe838d19b1deae Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Mon, 11 Dec 2017 12:26:03 +0100 Subject: [PATCH 07/13] Fix link --- source/_docs/installation/windows.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_docs/installation/windows.markdown b/source/_docs/installation/windows.markdown index 899040bc125..3554d44737a 100644 --- a/source/_docs/installation/windows.markdown +++ b/source/_docs/installation/windows.markdown @@ -9,7 +9,7 @@ sharing: true footer: true --- -To run Home Assistant on Microsoft Windows installation you need to install Python first. Download Python for https://www.python.org/downloads/windows/ and follow the instructions of the installer. +To run Home Assistant on Microsoft Windows installation you need to install Python first. Download Python for [https://www.python.org/downloads/windows/](https://www.python.org/downloads/windows/) and follow the instructions of the installer. Start @@ -23,5 +23,5 @@ For autostarting Home Assistant please refer to this [guide](https://community.h Check this [video](https://www.youtube.com/watch?v=X27eVvuqwnY) for the installation on Windows 10.

-The Microsoft Windows platform is not a primary target to install home Assistant. Also, not all tools and third-party modules will work. +The Microsoft Windows platform is not a primary target to install Home Assistant. Also, not all tools and third-party modules will work.

From bfbc71554c1bf27afeec9ade7a1a9ee2156b3909 Mon Sep 17 00:00:00 2001 From: Chris Kacerguis Date: Tue, 12 Dec 2017 09:50:19 -0600 Subject: [PATCH 08/13] Create configuration_yaml_by_chriskacerguis.markdown (#4204) --- .../configuration_yaml_by_chriskacerguis.markdown | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 source/_cookbook/configuration_yaml_by_chriskacerguis.markdown diff --git a/source/_cookbook/configuration_yaml_by_chriskacerguis.markdown b/source/_cookbook/configuration_yaml_by_chriskacerguis.markdown new file mode 100644 index 00000000000..6c873a0808e --- /dev/null +++ b/source/_cookbook/configuration_yaml_by_chriskacerguis.markdown @@ -0,0 +1,12 @@ +--- +layout: page +title: "Configuration.yaml by chriskacerguis" +description: "" +date: 2017-12-12 09:14 +sidebar: true +comments: false +sharing: true +footer: true +ha_category: Example configuration.yaml +ha_external_link: https://github.com/chriskacerguis/Home-AssistantConfig +--- From 81ab944c86e90b3ccc333a1a01f52f7f9e0c8533 Mon Sep 17 00:00:00 2001 From: tortfeaser Date: Wed, 13 Dec 2017 20:13:31 +1100 Subject: [PATCH 09/13] Fix apostrophe error. (#4208) --- source/_components/camera.generic.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/camera.generic.markdown b/source/_components/camera.generic.markdown index 69637387a44..32fa4917481 100644 --- a/source/_components/camera.generic.markdown +++ b/source/_components/camera.generic.markdown @@ -16,7 +16,7 @@ ha_iot_class: "depends" The `generic` camera platform allows you to integrate any IP camera or other URL into Home Assistant. Templates can be used to generate the URLs on the fly. -Home Assistant will serve the images via its server, making it possible to view your IP camera's while outside of your network. The endpoint is `/api/camera_proxy/camera.[name]`. +Home Assistant will serve the images via its server, making it possible to view your IP cameras while outside of your network. The endpoint is `/api/camera_proxy/camera.[name]`. To enable this camera in your installation, add the following to your `configuration.yaml` file: From 0c5d0bb5222a0e2c013668fc351a9f4e8d995520 Mon Sep 17 00:00:00 2001 From: sveip Date: Wed, 13 Dec 2017 10:16:53 +0100 Subject: [PATCH 10/13] Specify the correct device name for hass.io (#4206) The doc might be misleading and make people believe they will have to add it manually with the curl command, which does not work. --- 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 513028a96f0..15b87957cb0 100644 --- a/source/_docs/z-wave/installation.markdown +++ b/source/_docs/z-wave/installation.markdown @@ -159,7 +159,7 @@ To enable Z-Wave, plug your Z-Wave USB stick into your Raspberry Pi 3 and add th ```yaml zwave: - usb_path: /dev/ttyACM0 + usb_path: /dev/ttyAMA0 ``` For some devices the `/dev/ttyAMA0` device is not detected by udev and is therefore not mapped by Docker. To explicitly set this device for mapping to Home-Assistant, execute the following command using the ssh add-on: From 24d71bcc961b70a631856aa3e10ffde44b653523 Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Wed, 13 Dec 2017 10:18:01 +0100 Subject: [PATCH 11/13] Update addon_config.markdown --- source/developers/hassio/addon_config.markdown | 3 +++ 1 file changed, 3 insertions(+) diff --git a/source/developers/hassio/addon_config.markdown b/source/developers/hassio/addon_config.markdown index 9ec5bae332f..43cf11f7869 100644 --- a/source/developers/hassio/addon_config.markdown +++ b/source/developers/hassio/addon_config.markdown @@ -114,7 +114,10 @@ The config for an add-on is stored in `config.json`. | boot | yes | `auto` by system and manual or only `manual` | ports | no | Network ports to expose from the container. Format is `"container-port/type": host-port`. | host_network | no | If that is True, the add-on run on host network. +| host_ipc | no | Default False. Allow to share the IPC namespace with others. +| host_dbus | no | Default False. Map Host dbus service into add-on. | devices | no | Device list to map into the add-on. Format is: `::`. i.e. `/dev/ttyAMA0:/dev/ttyAMA0:rwm` +| auto_uart | no | Default False. Auto mapping all UART/Serial device from host into add-on. | hassio_api | no | This add-on can access to Hass.io REST API. It set the host alias `hassio`. | homeassistant_api | no | This add-on can access to Hass.io Home-Assistant REST API proxy. Use `http://hassio/homeassistant/api`. | privileged | no | Privilege for access to hardware/system. Available access: `NET_ADMIN`, `SYS_ADMIN`, `SYS_RAWIO` From 9222e98e423d07b45ef91ead6c79570b73b93bbf Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Wed, 13 Dec 2017 22:01:30 +0100 Subject: [PATCH 12/13] Update netatmo.markdown --- source/_components/netatmo.markdown | 3 --- 1 file changed, 3 deletions(-) diff --git a/source/_components/netatmo.markdown b/source/_components/netatmo.markdown index a7b6a30a0c0..ebb254a3109 100644 --- a/source/_components/netatmo.markdown +++ b/source/_components/netatmo.markdown @@ -55,6 +55,3 @@ That's it. You can copy and paste your new `client id` and `client secret` in yo

-

-The Home Assistant Netatmo platform has only be tested with the classic indoor, outdoor module and rain meter. There is no support for the wind meter module at this time because developers does not own these modules. -

From f0bf5c57958e861578a30d746fc657e247ff18f0 Mon Sep 17 00:00:00 2001 From: Igor Shults Date: Thu, 14 Dec 2017 12:02:41 -0600 Subject: [PATCH 13/13] Fix typo (#4210) --- source/_components/sensor.openweathermap.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/sensor.openweathermap.markdown b/source/_components/sensor.openweathermap.markdown index 9dc0e763c1c..f672ff07291 100644 --- a/source/_components/sensor.openweathermap.markdown +++ b/source/_components/sensor.openweathermap.markdown @@ -30,7 +30,7 @@ sensor: ``` {% configuration %} - apk_key: + api_key: description: Your API key for OpenWeatherMap. required: true type: string