From 2f25d9d5972f8b1761d3dffb9d1a24eddc4294bf Mon Sep 17 00:00:00 2001 From: rosscullen <35301905+rosscullen@users.noreply.github.com> Date: Wed, 27 Feb 2019 01:28:51 +0000 Subject: [PATCH 1/8] API link updated and charge for API (#8741) Update to API Link (previous link invalid. Added details of cost introduced to use their cloud API. I was informed of this when I recently requested my client_secret. I was given the following from Smappee support but has yet to configure with local API via MQTT (Mosquitto & Node Red). If anyone knows how best to write this information into the page, would appreciate it. Here are the links they provided: How to find the UUID.pdf https://support.smappee.com/attachments/token/y7MJ5O6e9P2kzuniuNfP5glFw/?name=How+to+find+the+UUID.pdf Smappee local MQTT topics -20-09-2018.pdf https://support.smappee.com/attachments/token/o5gKlg0jqbK2mVh0B6yfHArCy/?name=Smappee+local+MQTT+topics+-20-09-2018.pdf Node Red, Smappee nodes: https://flows.nodered.org/node/@smappee/node-red-contrib-smappee --- source/_components/smappee.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/smappee.markdown b/source/_components/smappee.markdown index 042cc8be8aa..ec4c9cf372b 100644 --- a/source/_components/smappee.markdown +++ b/source/_components/smappee.markdown @@ -29,7 +29,7 @@ There is currently support for the following device types within Home Assistant: Will be automatically added when you connect to the Smappee controller. -The smappee component gets information from [Smappee API](https://smappee.atlassian.net/wiki/display/DEVAPI/API+Methods). +The smappee component gets information from [Smappee API](https://smappee.atlassian.net/wiki/spaces/DEVAPI/overview). Note: their cloud API now requires a subscription fee of €2.50 per month for Smappee Energy/Solar or €3 per month for Smappee Plus. ## {% linkable_title Configuration %} From c73525a709d59d1c11c900dee92a58f33731f247 Mon Sep 17 00:00:00 2001 From: hybridparadigm <47954342+hybridparadigm@users.noreply.github.com> Date: Tue, 26 Feb 2019 22:52:58 -0600 Subject: [PATCH 2/8] Updates for python36 and scl (#8721) * Updates for python36 and scl Latest changes to installing the scl environment don't include the scl command, scl-utils is needed along w/ the proper repository in Centos7 to be enabled via RH and then downloaded to the environment which you are building and then SCL commands will work and setting python environment for bash will work too. * Minor changes --- source/_docs/installation/centos.markdown | 27 ++++++++++++++++------- 1 file changed, 19 insertions(+), 8 deletions(-) diff --git a/source/_docs/installation/centos.markdown b/source/_docs/installation/centos.markdown index 912586e509a..4b3364ec44b 100644 --- a/source/_docs/installation/centos.markdown +++ b/source/_docs/installation/centos.markdown @@ -11,37 +11,48 @@ footer: true To run Python 3.x on [CentOS](https://www.centos.org/) or RHEL (Red Hat Enterprise Linux), [Software Collections](https://www.softwarecollections.org/en/scls/rhscl/rh-python36/) needs to be activated first. -You must install Python 3.5.3 or later. Software Collections version of Python 3.5 is 3.5.1 so this guide uses Python 3.6. - ### {% linkable_title Using Software Collections %} -First of all install the software collection repository as root. For example, on CentOS: +First of all install the software collection repository as root and [scl utils](https://access.redhat.com/documentation/en-US/Red_Hat_Developer_Toolset/1/html-single/Software_Collections_Guide/). For example, on CentOS: ```bash -$ yum install centos-release-scl +$ sudo yum install centos-release-scl +$ sudo yum-config-manager --enable centos-sclo-rh-testing +$ sudo yum install -y scl-utils ``` Install some dependencies you'll need later. ```bash -$ yum install gcc gcc-c++ systemd-devel +$ sudo yum install gcc gcc-c++ systemd-devel ``` -Then install the Python 3.6 package: +Then install the Python 3.6 package. If you are using CentOS 7 then you may have to install the packages for Python 3.6 using RHEL Methods listed here: https://www.softwarecollections.org/en/scls/rhscl/rh-python36/) for this to work as mentioned above. + +```bash +$ sudo yum install rh-python36 +``` + +This is part of the slight change when trying to install Python 3.6 and running the command `python36 --version` which will after install give you the correct version, but won't allow you to set the software collection using the `scl` command. This command downloads the RH collection of Python to allow you to run `scl` command to enable the environment in `bash` and then run the automate command using the template. ```bash $ yum install rh-python36 ``` -Once installed, switch to your `homeassistant` user (if you've set one up), enable the software collection and check that it has set up the new version of Python: +### {% linkable_title Start using software collections %} ```bash $ scl enable rh-python36 bash +``` + +Once installed, switch to your `homeassistant` user (if you've set one up), enable the software collection and check that it has set up the new version of Python: + +```bash $ python --version Python 3.6.3 ``` -You will be in a command shell set up with Python 3.6 as your default version. The virtualenv and pip commands will be correct for this version, so you can now create a virtual environment and install Home Assistant following the main [instructions](/docs/installation/virtualenv/#step-4-set-up-the-virtualenv). +You will be in a command shell set up with Python 3.6 as your default version. The `virtualenv` and `pip` commands will be correct for this version, so you can now create a virtual environment and install Home Assistant following the main [instructions](/docs/installation/virtualenv/#step-4-set-up-the-virtualenv). You will need to enable the software collection each time you log on before you activate your virtual environment. From b22c01348c9ea9789e7406f998f0ab1ac0dbb36b Mon Sep 17 00:00:00 2001 From: SNoof85 Date: Wed, 27 Feb 2019 08:22:04 +0100 Subject: [PATCH 3/8] Freebox added informations for initial setup (#8691) * Added informations for initial setup * :pencil2: Tweak --- source/_components/freebox.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_components/freebox.markdown b/source/_components/freebox.markdown index b32610b7f65..b8e3b8f1dd6 100644 --- a/source/_components/freebox.markdown +++ b/source/_components/freebox.markdown @@ -56,7 +56,7 @@ returned json should contain an api_domain (`host`) and a https_port (`port`). ### {% linkable_title Initial setup %}

-You must have set a password for your Freebox router web administration page and enabled the option "Permettre les nouvelles demandes d'associations". +You must have set a password for your Freebox router web administration page. Enable the option "Permettre les nouvelles demandes d'associations" and check that the option "Accès à distance sécurisé à Freebox OS" is active in "Gestion des ports" > "Connexions entrantes".

The first time Home Assistant will connect to your Freebox, you will need to @@ -90,4 +90,4 @@ refreshes the devices states. ## {% linkable_title Sensor %} This platform offers you sensors to monitor a Freebox router. The monitored conditions are -instant upload and download rates in KB/s. \ No newline at end of file +instant upload and download rates in KB/s. From f9198a036dfdfc5b314a8815e053755d28a8741c Mon Sep 17 00:00:00 2001 From: Anthony Carbone <47967077+ant-car@users.noreply.github.com> Date: Wed, 27 Feb 2019 19:44:44 +1100 Subject: [PATCH 4/8] Added aux and panic services description (#8758) The Aux commands work on my new D16XD. I haven't tested panic. --- source/_components/ness_alarm.markdown | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/source/_components/ness_alarm.markdown b/source/_components/ness_alarm.markdown index 7b57eb1ffcc..74d7d727aa1 100644 --- a/source/_components/ness_alarm.markdown +++ b/source/_components/ness_alarm.markdown @@ -78,3 +78,23 @@ zones: default: motion type: string {% endconfiguration %} + +## {% linkable_title Services %} + +### {% linkable_title Service `aux` %} + +Trigger an aux output. This requires PCB version 7.8 or higher. + +| Service data attribute | Optional | Description | +| ---------------------- | -------- | ----------- | +| `output_id` | No | The aux output you wish to change. A number from 1-4. +| `state` | Yes | The On/Off State, represented as true/false. Default is true. If P14xE 8E is enabled then a value of true will pulse output x for the time specified in P14(x+4)E. + +### {% linkable_title Service `panic` %} + +Trigger a panic + +| Service data attribute | Optional | Description | +| ---------------------- | -------- | ----------- | +| `code` | No | The user code to use to trigger the panic. + From 08fad39c0c32201d36b8c442af708ba76ae15b59 Mon Sep 17 00:00:00 2001 From: ctborg Date: Wed, 27 Feb 2019 04:17:03 -0500 Subject: [PATCH 5/8] Adds docs for enabling I2C on Hass.io (#8144) * Create enable_i2c.markdown * Update sensor.bme680.markdown * Update hassio_navigation.html * :pencil2: Tweaks * :pencil2: Tweaks --- source/_components/sensor.bme680.markdown | 5 +- .../_includes/asides/hassio_navigation.html | 1 + source/hassio/enable_i2c.markdown | 51 +++++++++++++++++++ 3 files changed, 56 insertions(+), 1 deletion(-) create mode 100644 source/hassio/enable_i2c.markdown diff --git a/source/_components/sensor.bme680.markdown b/source/_components/sensor.bme680.markdown index 2294195bc1b..7ae238d268e 100644 --- a/source/_components/sensor.bme680.markdown +++ b/source/_components/sensor.bme680.markdown @@ -13,7 +13,6 @@ ha_release: 0.62 ha_iot_class: "Local Push" --- - The `bme680` sensor platform allows you to read temperature, humidity, pressure and gas resistance values of a [Bosch BME680 Environmental sensor](https://cdn-shop.adafruit.com/product-files/3660/BME680.pdf) connected via an [I2C](https://en.wikipedia.org/wiki/I²C) bus (SDA, SCL pins). It allows you to use all the operation modes of the sensor described in its datasheet. In addition, it includes a basic air quality calculation that uses gas resistance and humidity measurements to calculate a percentage based air quality measurement. Tested devices: @@ -186,6 +185,10 @@ group: - sensor.bme680_sensor_air_quality ``` +## {% linkable_title Directions for enabling I2C interface on Hass.io %} + +Follow the instructions here to [enable I2C on Hass.io.](/hassio/enable_i2c/). + ## {% linkable_title Directions for installing SMBus support on Raspberry Pi %} Enable I2C interface with the Raspberry Pi configuration utility: diff --git a/source/_includes/asides/hassio_navigation.html b/source/_includes/asides/hassio_navigation.html index 6c42ff0ca6d..f8e6a3debeb 100644 --- a/source/_includes/asides/hassio_navigation.html +++ b/source/_includes/asides/hassio_navigation.html @@ -19,6 +19,7 @@
  • {% active_link /hassio/zwave/ Z-Wave %}
  • {% active_link /hassio/external_storage/ External storage %}
  • {% active_link /hassio/run_local/ Execute local things %}
    • +
  • {% active_link /hassio/enable_i2c/ Enable I2C %}
    • diff --git a/source/hassio/enable_i2c.markdown b/source/hassio/enable_i2c.markdown new file mode 100644 index 00000000000..edafad0941d --- /dev/null +++ b/source/hassio/enable_i2c.markdown @@ -0,0 +1,51 @@ +--- +layout: page +title: "Enable HassOS i2c" +description: "Instructions on how to enable I2C on a Raspberry PI for Hass.io." +date: 2018-01-11 20:08 +sidebar: true +comments: false +sharing: true +footer: true +--- + +Hass.io is a managed environment, which means you can't use existing methods to enable the I2C bus on a Raspberry Pi. + +If you're attempting to add an external sensor, you will have to [enable the I2C interface in the Hass.io configuration](https://github.com/home-assistant/hassos/blob/dev/Documentation/boards/raspberrypi.md#i2c) using a USB stick. + +## {% linkable_title Step by step instructions %} + +You will need: + +- USB drive +- A way to add files to the USB drive +- A way to connect the drive to your Raspberry Pi + +### {% linkable_title Step 1 - Prepare the USB drive %} + +Connect the USB drive to a device capable of adding and editing files to the USB drive. + +Format a USB stick with FAT32/EXT4/NTFS and name the drive `CONFIG` (uppercase). + +### {% linkable_title Step 2 - Add files to enable I2C %} + +- In the root of the USB drive add a folder called `/modules`. +- Inside that folder add a text file called `rpi-i2c.conf` with the following contents: + ``` + i2c-bcm2708 + i2c-dev + ``` +- In the root of the USB drive add a file called `config.txt` with the following contents: + ``` + dtparam=i2c1=on + dtparam=i2c_arm=on + ``` + +### {% linkable_title Step 3 - Load the new USB config %} + +- Insert the USB drive into your Raspberry PI. +- Now go to your Home Assistant web interface, in the sidebar click **Hass.io** > **System**. +- Now click `Import from USB`. +- This will restart your Hass.io instance, and load the new USB configuration. + +When the service has restarted, you will have a working I2C interface. From fc743f4f8eda79a01ba83dfe0d7a524026f2d3d7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=BCrgen=20Haas?= Date: Wed, 27 Feb 2019 10:28:30 +0100 Subject: [PATCH 6/8] Add command line argument --init (#8232) See also https://github.com/home-assistant/home-assistant/issues/20260, the --init argument makes sure that the python service does not run with PID 1 which on some host systems can not be killed, i.e. restarting the service from within the UI is unreliable without that argument. --- source/_docs/installation/docker.markdown | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/source/_docs/installation/docker.markdown b/source/_docs/installation/docker.markdown index 7f55468ffe9..655caea6b85 100644 --- a/source/_docs/installation/docker.markdown +++ b/source/_docs/installation/docker.markdown @@ -15,19 +15,19 @@ Installation with Docker is straightforward. Adjust the following command so tha ### {% linkable_title Linux %} ```bash -$ docker run -d --name="home-assistant" -v /PATH_TO_YOUR_CONFIG:/config -v /etc/localtime:/etc/localtime:ro --net=host homeassistant/home-assistant +$ docker run --init -d --name="home-assistant" -v /PATH_TO_YOUR_CONFIG:/config -v /etc/localtime:/etc/localtime:ro --net=host homeassistant/home-assistant ``` ### {% linkable_title Raspberry Pi 3 (Raspbian) %} ```bash -$ docker run -d --name="home-assistant" -v /PATH_TO_YOUR_CONFIG:/config -v /etc/localtime:/etc/localtime:ro --net=host homeassistant/raspberrypi3-homeassistant +$ docker run --init -d --name="home-assistant" -v /PATH_TO_YOUR_CONFIG:/config -v /etc/localtime:/etc/localtime:ro --net=host homeassistant/raspberrypi3-homeassistant ``` You need to replace `/PATH_TO_YOUR_CONFIG` with your path to the configuration, for example if you choose your configuration path to be `/home/pi/homeassistant`, then command would be: ```bash -$ docker run -d --name="home-assistant" -v /home/pi/homeassistant:/config -v /etc/localtime:/etc/localtime:ro --net=host homeassistant/raspberrypi3-homeassistant +$ docker run --init -d --name="home-assistant" -v /home/pi/homeassistant:/config -v /etc/localtime:/etc/localtime:ro --net=host homeassistant/raspberrypi3-homeassistant ``` ### {% linkable_title macOS %} @@ -37,7 +37,7 @@ When using `docker-ce` (or `boot2docker`) on macOS, you are unable to map the lo If you wish to browse directly to `http://localhost:8123` from your macOS host, meaning forward ports directly to the container, replace the `--net=host` switch with `-p 8123:8123`. More detail can be found in [the docker forums](https://forums.docker.com/t/should-docker-run-net-host-work/14215/10). ```bash -$ docker run -d --name="home-assistant" -v /PATH_TO_YOUR_CONFIG:/config -e "TZ=America/Los_Angeles" -p 8123:8123 homeassistant/home-assistant +$ docker run --init -d --name="home-assistant" -v /PATH_TO_YOUR_CONFIG:/config -e "TZ=America/Los_Angeles" -p 8123:8123 homeassistant/home-assistant ``` Alternatively, `docker-compose` works with any recent release of `docker-ce` on macOS. Note that (further down this page) we provide an example `docker-compose.yml` however it differs from the `docker run` example above. To make the .yml directives match, you would need to make _two_ changes: first add the equivalent `ports:` directive, then _remove_ the `network_mode: host` section. This is because `Port mapping is incompatible with network_mode: host:`. More details can be found at [Docker networking docs](https://docs.docker.com/engine/userguide/networking/#default-networks). Note also the `/dev/tty*` device name used by your Arduino etc. devices will differ from the Linux example, so the compose `mount:` may require updates. @@ -45,7 +45,7 @@ Alternatively, `docker-compose` works with any recent release of `docker-ce` on ### {% linkable_title Windows %} ```powershell -$ docker run -d --name="home-assistant" -v /PATH_TO_YOUR_CONFIG:/config -e "TZ=America/Los_Angeles" --net=host homeassistant/home-assistant +$ docker run --init -d --name="home-assistant" -v /PATH_TO_YOUR_CONFIG:/config -e "TZ=America/Los_Angeles" --net=host homeassistant/home-assistant ``` When running Home Assistant in Docker on Windows, you may have some difficulty getting ports to map for routing (since the `--net=host` switch actually applies to the hypervisor's network interface). To get around this, you will need to add port proxy ipv4 rules to your local Windows machine, like so (Replacing '192.168.1.10' with whatever your Windows IP is, and '10.0.50.2' with whatever your Docker container's IP is): @@ -150,7 +150,7 @@ If you want to use a USB Bluetooth adapter or Z-Wave USB stick with Home Assista The above command should show you any USB devices plugged into your NAS. If you have more than one, you may get multiple items returned. Like : `ttyACM0` - Run Docker command: - `docker run --name home-assistant --net=host --privileged -itd -v /share/CACHEDEV1_DATA/Public/homeassistant/config:/config -e variable=TZ -e value=Europe/London --device /dev/ttyACM0 homeassistant/home-assistant` + `docker run --init --name home-assistant --net=host --privileged -itd -v /share/CACHEDEV1_DATA/Public/homeassistant/config:/config -e variable=TZ -e value=Europe/London --device /dev/ttyACM0 homeassistant/home-assistant` `-v` is your config path `-e` is set timezone @@ -168,7 +168,7 @@ That will tell Home Assistant where to look for our Z-wave radio. - Connect to your NAS over SSH - Run Docker command: - `docker run --name home-assistant --net=host --privileged -itd -v /share/CACHEDEV1_DATA/Public/homeassistant/config:/config -e variable=TZ -e value=Europe/London -v /dev/bus/usb:/dev/bus/usb -v /var/run/dbus:/var/run/dbus homeassistant/home-assistant` + `docker run --init --name home-assistant --net=host --privileged -itd -v /share/CACHEDEV1_DATA/Public/homeassistant/config:/config -e variable=TZ -e value=Europe/London -v /dev/bus/usb:/dev/bus/usb -v /var/run/dbus:/var/run/dbus homeassistant/home-assistant` First `-v` is your config path `-e` is set timezone @@ -221,7 +221,7 @@ $ docker-compose restart In order to use Z-Wave, Zigbee or other components that require access to devices, you need to map the appropriate device into the container. Ensure the user that is running the container has the correct privileges to access the `/dev/tty*` file, then add the device mapping to your docker command: ```bash -$ docker run -d --name="home-assistant" -v /PATH_TO_YOUR_CONFIG:/config \ +$ docker run --init -d --name="home-assistant" -v /PATH_TO_YOUR_CONFIG:/config \ -v /etc/localtime:/etc/localtime:ro --device /dev/ttyUSB0:/dev/ttyUSB0 \ --net=host homeassistant/home-assistant ``` From 63d8196f8acc5c6a269e0584a4d820ea746b88e9 Mon Sep 17 00:00:00 2001 From: David Beitey Date: Wed, 27 Feb 2019 19:31:29 +1000 Subject: [PATCH 7/8] Clarify that http.base_url doesn't support paths (#8615) Explains that paths aren't supported in base_url so someone attempting to set settings doesn't expect something that isn't currently possible. Related: https://github.com/home-assistant/home-assistant/issues/21113 --- source/_components/http.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/http.markdown b/source/_components/http.markdown index 1e280f8c2be..2b452b4cb0c 100644 --- a/source/_components/http.markdown +++ b/source/_components/http.markdown @@ -41,7 +41,7 @@ server_port: type: integer default: 8123 base_url: - description: "The URL that Home Assistant is available on the internet. For example: `https://hass-example.duckdns.org:8123`. The iOS app finds local installations, if you have an outside URL use this so that you can auto-fill when discovered in the app." + description: "The URL that Home Assistant is available on the internet. For example: `https://hass-example.duckdns.org:8123`. The iOS app finds local installations, if you have an outside URL use this so that you can auto-fill when discovered in the app. Note that setting may contain protocol, hostname and port; using a path is not currently supported." required: false type: string default: Your local IP address From b6835c59af92ff3a6894828d8b3979525f6ecf93 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Wed, 27 Feb 2019 16:47:28 -0800 Subject: [PATCH 8/8] Release 0.88.2 --- _config.yml | 4 +-- source/_posts/2019-02-20-release-88.markdown | 27 ++++++++++++++++++++ 2 files changed, 29 insertions(+), 2 deletions(-) diff --git a/_config.yml b/_config.yml index 17d86541905..5c9641209ca 100644 --- a/_config.yml +++ b/_config.yml @@ -139,8 +139,8 @@ social: # Home Assistant release details current_major_version: 0 current_minor_version: 88 -current_patch_version: 1 -date_released: 2019-02-22 +current_patch_version: 2 +date_released: 2019-02-27 # Either # or the anchor link to latest release notes in the blog post. # Must be prefixed with a # and have double quotes around it. diff --git a/source/_posts/2019-02-20-release-88.markdown b/source/_posts/2019-02-20-release-88.markdown index 18503beece7..53f5c0216b0 100644 --- a/source/_posts/2019-02-20-release-88.markdown +++ b/source/_posts/2019-02-20-release-88.markdown @@ -93,6 +93,33 @@ Note for custom component developers: We are moving to a new file structure. Mor [sensor.imap_email_content docs]: /components/sensor.imap_email_content/ [zha docs]: /components/zha/ +## {% linkable_title Release 0.88.2 - February 27 %} + +- Make sure that device trackers is always a list during creation ([@balloob] - [#21193]) ([person docs]) +- Allow custom_effect to be absent from Flux configuration ([@conleydg] - [#21317]) ([light.flux_led docs]) +- Fix person update on create ([@MartinHjelmare] - [#21355]) ([person docs]) +- Scene validator fix ([@yosilevy] - [#21362]) ([scene docs]) +- Improve tolerance of SmartThings Climate platform ([@andrewsayre] - [#21383]) ([smartthings docs]) +- Bump PyXiaomiGateway version to 0.11.2 ([@syssi] - [#21453]) ([xiaomi_aqara docs]) + +[#21193]: https://github.com/home-assistant/home-assistant/pull/21193 +[#21317]: https://github.com/home-assistant/home-assistant/pull/21317 +[#21355]: https://github.com/home-assistant/home-assistant/pull/21355 +[#21362]: https://github.com/home-assistant/home-assistant/pull/21362 +[#21383]: https://github.com/home-assistant/home-assistant/pull/21383 +[#21453]: https://github.com/home-assistant/home-assistant/pull/21453 +[@MartinHjelmare]: https://github.com/MartinHjelmare +[@andrewsayre]: https://github.com/andrewsayre +[@balloob]: https://github.com/balloob +[@conleydg]: https://github.com/conleydg +[@syssi]: https://github.com/syssi +[@yosilevy]: https://github.com/yosilevy +[light.flux_led docs]: /components/light.flux_led/ +[person docs]: /components/person/ +[scene docs]: /components/scene/ +[smartthings docs]: /components/smartthings/ +[xiaomi_aqara docs]: /components/xiaomi_aqara/ + ## {% 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.